Related
Hey, I was wondering if Chainfire's autoroot would cause a factory reset or any type of wipe on the phone? I know that for some phones, when the root is an exploit it doesn't wipe anything. I'm not sure if Chainfire's method is an exploit or not though.
Secondly, he says to be on the stock recovery. Once the rooting process is completed, I can install whichever recover I wish right? I assume TWRP is the best one to do? Or are there any known issues with certain recoveries for this device?
Thanks!
Hobox10 said:
Hey, I was wondering if Chainfire's autoroot would cause a factory reset or any type of wipe on the phone? I know that for some phones, when the root is an exploit it doesn't wipe anything. I'm not sure if Chainfire's method is an exploit or not though.
Secondly, he says to be on the stock recovery. Once the rooting process is completed, I can install whichever recover I wish right? I assume TWRP is the best one to do? Or are there any known issues with certain recoveries for this device?
Thanks!
Click to expand...
Click to collapse
It won't...but make sure to make a back up of anything on your phone to your pc like picture, music and so on.
Do a factory reset before rooting to eliminate some problem. That what I did and so far everything is good.
The KNOX meter will turn from 0x0 to 0x1 because of rooting.
And finally use TWRP latest version like everyone does...
kuroy301 said:
The KNOX meter will turn from 0x0 to 0x1 because of rooting.
Click to expand...
Click to collapse
Oh yes, that was another question that I forgot to ask. Would Samsung deny insurance claims on a broken phone, or deny warranty coverage from root? I know "technically" they can but do you think they would if it's a hardware issue?
Is there a way to reverse this and unroot the phone if needed?
Hobox10 said:
Oh yes, that was another question that I forgot to ask. Would Samsung deny insurance claims on a broken phone, or deny warranty coverage from root? I know "technically" they can but do you think they would if it's a hardware issue?
Is there a way to reverse this and unroot the phone if needed?[/QUOTE)
You can go back to stock via ODIN but the KNOX will be the same at 0x1 I believed. I'm not sure if there is a way to revert back to zero maybe in the near future once the smart devs here can figure it out.
Samsung will void the warranty...but TMobile maybe NOT because some people here already exchange their phone like 2 or 3 times already due to some issue with rooting and so on...
Click to expand...
Click to collapse
kuroy301 said:
You can go back to stock via ODIN but the KNOX will be the same at 0x1 I believed. I'm not sure if there is a way to revert back to zero maybe in the near future once the smart devs here can figure it out.
Samsung will void the warranty...but TMobile maybe NOT because some people here already exchange their phone like 2 or 3 times already due to some issue with rooting and so on...
Click to expand...
Click to collapse
Alright, thanks a ton. I'll post up if I have any more questions.
re: rooting
Hobox10 said:
Hey, I was wondering if Chainfire's autoroot would cause a factory reset or any type of wipe on the phone? I know that for some phones, when the root is an exploit it doesn't wipe anything. I'm not sure if Chainfire's method is an exploit or not though.
Secondly, he says to be on the stock recovery. Once the rooting process is completed, I can install whichever recover I wish right? I assume TWRP is the best one to do? Or are there any known issues with certain recoveries for this device?
Thanks!
Click to expand...
Click to collapse
Chainfire's CF-Autoroot will not touch or delete any of your files.
Including pictures, videos. contacts, data, mms, apps or anything else.
There is absolutely no need to backup anything before rooting with
CF-Autoroot or with any other rooting method.
TWRP recovery is excellent, in fact that's what I use it all the time.
Also none of the rooting methods including CF-Autoroot" will do a "factory reset".
The only thing any of the rooting methods do is ROOT the phone and nothing else.
Good luck....
kuroy301 said:
Hobox10 said:
Oh yes, that was another question that I forgot to ask. Would Samsung deny insurance claims on a broken phone, or deny warranty coverage from root? I know "technically" they can but do you think they would if it's a hardware issue?
Is there a way to reverse this and unroot the phone if needed?[/QUOTE)
You can go back to stock via ODIN but the KNOX will be the same at 0x1 I believed. I'm not sure if there is a way to revert back to zero maybe in the near future once the smart devs here can figure it out.
Samsung will void the warranty...but TMobile maybe NOT because some people here already exchange their phone like 2 or 3 times already due to some issue with rooting and so on...
Click to expand...
Click to collapse
I'm pretty sure you can use the Triangle away method I used on my S4 to reset the counter to zero.....
Click to expand...
Click to collapse
SBERG117 said:
kuroy301 said:
I'm pretty sure you can use the Triangle away method I used on my S4 to reset the counter to zero.....
Click to expand...
Click to collapse
Nope. Triangle away is for resetting the binary flash count. Knox is an efuse built into the chipset. There is no known way to reset it.... Yet
Click to expand...
Click to collapse
Misterjunky said:
Chainfire's CF-Autoroot will not touch or delete any of your files.
Including pictures, videos. contacts, data, mms, apps or anything else.
There is absolutely no need to backup anything before rooting with
CF-Autoroot or with any other rooting method.
TWRP recovery is excellent, in fact that's what I use it all the time.
Also none of the rooting methods including CF-Autoroot" will do a "factory reset".
The only thing any of the rooting methods do is ROOT the phone and nothing else.
Good luck....
Click to expand...
Click to collapse
are you sure bro that it will not wipe any data....coz my root failed bcoz of FRP lock (Factory Reset Protection) if i turn that off nd then try root with cf auto root will it factory reset my device?????????????????
Madhifen said:
are you sure bro that it will not wipe any data....coz my root failed bcoz of FRP lock (Factory Reset Protection) if i turn that off nd then try root with cf auto root will it factory reset my device?????????????????
Click to expand...
Click to collapse
The T-Mobile Note 3 does not have FRP; however, it may have reactivation lock enabled.
Hello Everyone. First and foremost, thanks for all the helpful tips you guys have provided, been lurking here for a year or so.
Okay so heres the deal. I used skunkApes rooting method to root my phone last year. I just used the files included there and didn't do any custom roms or anything.
The last OTA update, didnt remove my root so after a few drinks and seeing that notification bar, i said why not. Well this one did. I checked SuperSU and it said no binary files found, must re-root. And my root checker says no root access. In developer menu, i dont see a tab for root to tick.
I tryed unistalling superSU, and that didnt work when i reinstalled. I can get to Download mode, but when I do recovery, it looks like its the stock android recovery.
Any help woul be much appreciated.
oh and sorry if this is in the wrong place, i wasnt sure if should had tagged this in teh "How to root" thread.
Phone infor- Spring G3, USA,
SPH-L710android version 4.3
Thanks
Use caution. If you aren't already aware, the 4.3 OTA update came with a sneaky bonus in the form of the KNOX bootloader. You're definitely going to want to familiarize yourself with it if you've got it because it looks like it's here to stay and it's got real potential for screwing you.
As for regaining root, all the resources you're likely to need are here: http://forum.xda-developers.com/showthread.php?t=2541900
I've been preaching that link all morning as my own personal Jesus Christ.
cwm
FallenZen said:
Use caution. If you aren't already aware, the 4.3 OTA update came with a sneaky bonus in the form of the KNOX bootloader. You're definitely going to want to familiarize yourself with it if you've got it because it looks like it's here to stay and it's got real potential for screwing you.
As for regaining root, all the resources you're likely to need are here: http://forum.xda-developers.com/showthread.php?t=2541900
I've been preaching that link all morning as my own personal Jesus Christ.
Click to expand...
Click to collapse
Hey Fallenzen, Thanks for the response, i see that you have been busy helping members this week!
Ok, so, when I try to go to recovery, Vol Up,menu and power, it looks like my clockwork recovery is gone and it shows the default one. No option to clear cache or make back up, just the android in surgery picture.
How do I get it back?
Thanks
Praz21 said:
Hey Fallenzen, Thanks for the response, i see that you have been busy helping members this week!
Ok, so, when I try to go to recovery, Vol Up,menu and power, it looks like my clockwork recovery is gone and it shows the default one. No option to clear cache or make back up, just the android in surgery picture.
How do I get it back?
Thanks
Click to expand...
Click to collapse
I've really just been trying to share what I learned from my recent update nightmare, I'm still just another noob. Anyhow, you should just be able to reflash CWM using ODIN. I am uncertain whether or not this will trip the KNOX warranty bit though (I don't know when I triggered mine since I wasn't even aware it existed until too late). If you haven't already triggered it, you might want to exercise patience and just keep reading what the devs are figuring out because once KNOX fires there's no going back, short of replacing the motherboard, at this time on account of the physical change it makes to your hardware.
I don't have a link handy, but I've been reading about Root De La Vega, which exploited a hash vulnerability to allow custom flashing without triggering KNOX. Samsung has patched the vulnerability, so it may or may not be an option for you but it's probably at least worth looking into.
FallenZen said:
I've really just been trying to share what I learned from my recent update nightmare, I'm still just another noob. Anyhow, you should just be able to reflash CWM using ODIN. I am uncertain whether or not this will trip the KNOX warranty bit though (I don't know when I triggered mine since I wasn't even aware it existed until too late). If you haven't already triggered it, you might want to exercise patience and just keep reading what the devs are figuring out because once KNOX fires there's no going back, short of replacing the motherboard, at this time on account of the physical change it makes to your hardware.
I don't have a link handy, but I've been reading about Root De La Vega, which exploited a hash vulnerability to allow custom flashing without triggering KNOX. Samsung has patched the vulnerability, so it may or may not be an option for you but it's probably at least worth looking into.
Click to expand...
Click to collapse
Custom recovery and custom ROMS will trip knox. If you have knox you can not flash backwards (back to 4.1.2 or lower than 4.3) because it will brick ur device. If ur not worried about tripping knox...iv got a note 3 and I tripped knox the first day I bought it...then by all means root and flash a custom recovery. If u haven't updated yet don't if you want the ROMS that are 4.1.2 or check out the 4.3 options in android development that left the knox bootloader out. If you choose to flash one of those that do not have the knox bootloader you can flash backwards. I'd suggest reading cnexus' "knox and you" in general. Lots of good info out here...keep reading and asking questions.
http://i.imgur.com/qrByUGN.jpg
same issue
I got the same issue here. Did not expect to lose root with the 4.3 OTA update, but I have! I got ODIN to flash CWM recovery and I got into recovery boot mode, and was able to install superuser. Once the phone booted up I got that bullS*it gray shield icon notice about "attempt to access secure area" (KNOX?) and now I cant get root access. WTF?! Please help, I need TrevEMod back in my life!
question
Since i am so new I cant post this reply in the following thread,
http://forum.xda-developers.com/showthread.php?t=2541900
but Ill ask here.
Will flashing this ROM work AFTER updated to 4.3 OTA with this KNOX already installed? I dont know, havent tried it yet?
onion root
bigpappags3 said:
Custom recovery and custom ROMS will trip knox. If you have knox you can not flash backwards (back to 4.1.2 or lower than 4.3) because it will brick ur device. If ur not worried about tripping knox...iv got a note 3 and I tripped knox the first day I bought it...then by all means root and flash a custom recovery. If u haven't updated yet don't if you want the ROMS that are 4.1.2 or check out the 4.3 options in android development that left the knox bootloader out. If you choose to flash one of those that do not have the knox bootloader you can flash backwards. I'd suggest reading cnexus' "knox and you" in general. Lots of good info out here...keep reading and asking questions.
Thanks for the info. Yea, my phone is already a year old so from what Ive read from that thread is that it just voids the warranty.
I guess i have to re-visit the rooting process. I just would like to get root back so I could use my wifi teather and bluput to control my ps3 again.
Any help is much appreciated.
Click to expand...
Click to collapse
Guessing I'm going to wait until a .tar file is released to flash custom recovery and root. I need a flawless phone and a lot of issues being reported in the use of cnex 4.3 rom release.
Sent from my SPH-L710 using xda app-developers app
SwellVermin said:
Since i am so new I cant post this reply in the following thread,
http://forum.xda-developers.com/showthread.php?t=2541900
but Ill ask here.
Will flashing this ROM work AFTER updated to 4.3 OTA with this KNOX already installed? I dont know, havent tried it yet?
Click to expand...
Click to collapse
Simple answer I believe is no. ... You have the knox bootloader. . That room will brick you device because ur trying to put an older bootloader on your phone.
http://i.imgur.com/qrByUGN.jpg
Got Root Back
But not all apps functioning. I used ChainFire's Auto Root method in ODIN to get root back, downloaded SuperSU from play store and used it to disable KNOX.
Now TrevEMod WifiTether not working. Help?
SwellVermin said:
But not all apps functioning. I used ChainFire's Auto Root method in ODIN to get root back, downloaded SuperSU from play store and used it to disable KNOX.
Now TrevEMod WifiTether not working. Help?
Click to expand...
Click to collapse
Out of curiosity is your SELinux status "Permissive" or "Enforcing"? Also, tethering is a known issue on 4.3 stock update, TrevEMod probably isn't going to work regardless. Is that the only app giving you problems?
We have a member who figured out a wireless tether fix on Android Forums, check out this link:
http://androidforums.com/virgin-mobile-galaxy-s3-all-things-root/800923-solved-mk5-4-3-stock-working-wireless-tether.html
It is for Virgin Mobile but should still work for Sprint or Boost for that matter since all three are SPH-L710.
SwellVermin said:
Since i am so new I cant post this reply in the following thread,
http://forum.xda-developers.com/showthread.php?t=2541900
but Ill ask here.
Will flashing this ROM work AFTER updated to 4.3 OTA with this KNOX already installed? I dont know, havent tried it yet?
Click to expand...
Click to collapse
That ROM worked for me after the OTA update to 4.3 screwed up my phone. I have the KNOX bootloader. I have tripped the Warranty Void bit, but since my phone is flashed from Sprint to Verizon I don't much care about that. My phone, with this ROM and the appropriate fixes (sprint hotspot, wifi, etc) works flawlessly. I have observed a bit of response lag on the lock screen, but it is not excessive and the lag is display-oriented as I can enter my lock code at full speed and it detects every touch just fine. I don't even notice it at this point.
Hope that helps.
Mr. Struck said:
Out of curiosity is your SELinux status "Permissive" or "Enforcing"?
Click to expand...
Click to collapse
What? lol Where is this setting found?
---------- Post added at 03:53 PM ---------- Previous post was at 03:41 PM ----------
FallenZen said:
That ROM worked for me after the OTA update to 4.3 screwed up my phone. I have the KNOX bootloader. I have tripped the Warranty Void bit, but since my phone is flashed from Sprint to Verizon I don't much care about that. My phone, with this ROM and the appropriate fixes (sprint hotspot, wifi, etc) works flawlessly. I have observed a bit of response lag on the lock screen, but it is not excessive and the lag is display-oriented as I can enter my lock code at full speed and it detects every touch just fine. I don't even notice it at this point.
Hope that helps.
Click to expand...
Click to collapse
But if this is the only way to get my wifi hot spot back, then I guess ill try it out. Theres a lot of steps to do to get this working correctly, huh? Im not that advanced and Im afraid Ill F something up!!
SwellVermin said:
What? lol Where is this setting found?
---------- Post added at 03:53 PM ---------- Previous post was at 03:41 PM ----------
But if this is the only way to get my wifi hot spot back, then I guess ill try it out. Theres a lot of steps to do to get this working correctly, huh? Im not that advanced and Im afraid Ill F something up!!
Click to expand...
Click to collapse
Well, here are my notes from my installation procedure. You can judge for yourself whether or not you're comfortable doing so, but be aware that this WILL trip your KNOX Warranty Void bit.
These notes were created for my own use in the event that I want to duplicate this procedure later since my pre-KNOX notes were rendered useless by the OTA update.
----------------------------------------
http://forum.xda-developers.com/showthread.php?t=2541900
Save all files to the phone's internal memory and remove microSD card.
Use ODIN3 to flash CWM-Recovery-LTE-SGS3-v5.tar.md5 to the phone with the PDA function.
Boot phone into the Recovery Console.
- Install SPHL710_MK3_rooted_odexed.zip
Use ODIN3 to flash CF-Auto-Root-d2spr-d2spr-sphl710.tar.md5 to the phone using the PDA function.
* Note, after this you might find you need to flash CWM Recovery to the phone again if the Android recovery console reappears.
From the CWM Recovery Console:
- Install Knox_APP_remover.zip
- Install wifi_fix_mk3.zip
- Install UPDATE-SuperSU-v1.80.zip
- (optional) Install MK3HotspotMod-odex.zip
- (optional) Install MK3_more_toggles.zip
Reboot the phone. If all goes well, it should load smooth as silk. Then all you need to do is execute the SuperSU app before attempting to operate any other apps that require root access and you should be golden.
----------------------------------------
It should be noted that I use ODIN 3.07 for this and am no longer on v1.85
Let me know if you need any clarification on the notes and I'll do my best.
Edit:
Also, do NOT use TriangleAway. I haven't tried it, but all of my reading suggests that it is a one way ticket to Bad News Blvd.
SwellVermin said:
What? lol Where is this setting found?
Click to expand...
Click to collapse
Settings/About Phone, scroll to the bottom. More of an issue for 4.4 than 4.3, as the default for 4.3 is Permissive and the default for 4.4 is Enforcing. In Enforcing mode it will sometimes block root-related apps, but it can manually be set to Permissive for 4.4 users.
FallenZen said:
Well, here are my notes from my installation procedure. You can judge for yourself whether or not you're comfortable doing so, but be aware that this WILL trip your KNOX Warranty Void bit.
These notes were created for my own use in the event that I want to duplicate this procedure later since my pre-KNOX notes were rendered useless by the OTA update.
----------------------------------------
http://forum.xda-developers.com/showthread.php?t=2541900
Save all files to the phone's internal memory and remove microSD card.
Use ODIN3 to flash CWM-Recovery-LTE-SGS3-v5.tar.md5 to the phone with the PDA function.
Boot phone into the Recovery Console.
- Install SPHL710_MK3_rooted_odexed.zip
Use ODIN3 to flash CF-Auto-Root-d2spr-d2spr-sphl710.tar.md5 to the phone using the PDA function.
* Note, after this you might find you need to flash CWM Recovery to the phone again if the Android recovery console reappears.
From the CWM Recovery Console:
- Install Knox_APP_remover.zip
- Install wifi_fix_mk3.zip
- Install UPDATE-SuperSU-v1.80.zip
- (optional) Install MK3HotspotMod-odex.zip
- (optional) Install MK3_more_toggles.zip
Reboot the phone. If all goes well, it should load smooth as silk. Then all you need to do is execute the SuperSU app before attempting to operate any other apps that require root access and you should be golden.
----------------------------------------
It should be noted that I use ODIN 3.07 for this and am no longer on v1.85
Let me know if you need any clarification on the notes and I'll do my best.
Edit:
Also, do NOT use TriangleAway. I haven't tried it, but all of my reading suggests that it is a one way ticket to Bad News Blvd.
Click to expand...
Click to collapse
Ok, tried to do the first step here. This is what ODIN says when I try to load the CWM-Recovery-LTE-SGS3-v*.tar.md5 file.
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> CWM-Recovery-LTE-SGS3-v5.tar.md5 is invalid.
<OSM> End...
Not sure what to do here. Please let me know what you think?
I just tried to boot into recovery mode and of course it's the stock android recovery. Bah!
SwellVermin said:
Ok, tried to do the first step here. This is what ODIN says when I try to load the CWM-Recovery-LTE-SGS3-v*.tar.md5 file.
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> CWM-Recovery-LTE-SGS3-v5.tar.md5 is invalid.
<OSM> End...
Not sure what to do here. Please let me know what you think?
I just tried to boot into recovery mode and of course it's the stock android recovery. Bah!
Click to expand...
Click to collapse
I'm not sure, but the first thing I'd suggest is to try redownloading the file. Possibly from another source. Sounds like a bad download. If it continues to be a problem, I'll compile the exact files from my computer and make 'em accessible on my dropbox or something so you can try to use them... But that shouldn't be necessary. Also, remember that you want to flash the file via ODIN using the PDA option and make sure that both Auto Reboot and F. Reset Time are checked but that nothing else is.
yeah I tried that
FallenZen said:
I'm not sure, but the first thing I'd suggest is to try redownloading the file. Possibly from another source. Sounds like a bad download. If it continues to be a problem, I'll compile the exact files from my computer and make 'em accessible on my dropbox or something so you can try to use them... But that shouldn't be necessary. Also, remember that you want to flash the file via ODIN using the PDA option and make sure that both Auto Reboot and F. Reset Time are checked but that nothing else is.
Click to expand...
Click to collapse
I downloaded from 3 different sources, all the same result when loading the file into ODIN via PDA function. Hmph! Is it because I am on a stock recovery and ROM?
SwellVermin said:
I downloaded from 3 different sources, all the same result when loading the file into ODIN via PDA function. Hmph! Is it because I am on a stock recovery and ROM?
Click to expand...
Click to collapse
Shouldn't be... I'm also on a stock recovery and ROM. What version of ODIN are you using?
Hi guys! This bootloader unlock version is only for ARGENTINIAN models.
You can donate me (PAYPAL LINK COMING SOON) and @cerg2010cerg2010 through paypal.
@cerg2010cerg2010 PAYPAL EMAIL: [email protected] OR QIWI: +79157840294
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
No more secure boot error!
I thank my friend @cerg2010cerg2010 for helping me out in patching the aboot.
Supported Model:
Code:
H440AR
-> Steps:
(1) Downgrade to v10a or v10d version of Android.
(2) Root your device.
(3) Download this patched aboot file. Click Here for v10a. Click Here for v10d.
(4) Connect your phone to the computer. In command prompt, type "adb shell".
(5) Transfer the aboot file into /sdcard/ folder.
(6) Type "su" to enter the root shell. Then type "dd if=/sdcard/<file_name_you_downloaded_in_3rd step> of=/dev/block/<your aboot partition>".
(7) Restart your phone by typing "reboot".
You have unlocked your bootloader!
Refer Notes for more information.
-> Notes:
1) The aboot_5120_patched.bin or aboot_10d_patched.bin is the patched version of aboot partition of your device. Secure boot validation has been patched such that secure boot is always valid, so you can flash your own TWRP and Custom ROM.
2) Don't upgrade to any updated version of Android if you get any through OTA update. It might brick your device.
I'll give it a try soon, hopefully if the guys here are correct 4g/lte should work now. Thanks a lot!
Edit: apparently this fixed the issue regarding LTE using argentinian bands, I'll keep testing it but so far it holds even after a call and a low signal area it just switches from lte to 3g and so on (which wasn't working with the other aboot)
Korelev said:
I'll give it a try soon, hopefully if the guys here are correct 4g/lte should work now. Thanks a lot!
Edit: apparently this fixed the issue regarding LTE using argentinian bands, I'll keep testing it but so far it holds even after a call and a low signal area it just switches from lte to 3g and so on (which wasn't working with the other aboot)
Click to expand...
Click to collapse
Thanks for confirming!
You did it!!!! Many Many Thanks!!!! T.T
69PerTTu69 said:
You did it!!!! Many Many Thanks!!!! T.T
Click to expand...
Click to collapse
Hey, I'm trying to download the Argentinean aboot, but the link is dead. Can anyone help me with it ?
mayankjet said:
Hey, I'm trying to download the Argentinean aboot, but the link is dead. Can anyone help me with it ?
Click to expand...
Click to collapse
They aren't broken
69PerTTu69 said:
They aren't broken
Click to expand...
Click to collapse
My bad.
links are not working for me
edit: apparently they are now
Quick question: by unlocking the bootloader I should be able to later flash a custom recovery and then root the phone, right? As the argentinian version seems to be unrootable via kingroot (which is what the general thread recommends). Do I got this right, or is there a simple version to root it? Thanks.
Kon22 said:
Quick question: by unlocking the bootloader I should be able to later flash a custom recovery and then root the phone, right? As the argentinian version seems to be unrootable via kingroot (which is what the general thread recommends). Do I got this right, or is there a simple version to root it? Thanks.
Click to expand...
Click to collapse
First you need to be on Lollipop.
Root it by using Kingroot.
Unlock the bootloader.
Flash TWRP 3.1.1.0
Flash MM v20b zip proposed by Korelev.
Flash Supersu.
Now you have a rooted MM.
walterfuster said:
First you need to be on Lollipop.
Root it by using Kingroot.
Unlock the bootloader.
Flash TWRP 3.1.1.0
Flash MM v20b zip proposed by Korelev.
Flash Supersu.
Now you have a rooted MM.
Click to expand...
Click to collapse
I tried rooting it using Kingroot with no success, both with the APK and the app on PC. Running stock lollipop, obviously. I assumed the argentinian version (H440AR) couldn't be rooted via kingroot, which is why I'm wondering if the only way is to simply unlock bootloader, flash TWRP and then flash SuperSU.
Kon22 said:
I tried rooting it using Kingroot with no success, both with the APK and the app on PC. Running stock lollipop, obviously. I assumed the argentinian version (H440AR) couldn't be rooted via kingroot, which is why I'm wondering if the only way is to simply unlock bootloader, flash TWRP and then flash SuperSU.
Click to expand...
Click to collapse
The thing is, you can't unlock the bootloader without first having su permissions.
AR device version shouldn't be a problem.
Mine is Argentinian too and I easily rooted it.
Try with an older version of Kingroot. You can easily find it around apk's sites.
If no luck, try flashing an H440N kdz (I'm on POL v10i) with LG Flash Tool 2014, and see what happens.
You can do a dirty flash if you don't want to lose your data.
P.S.: I even switched from Kingroot to SuperSU. I highly recommend this. Kingroot converts your phone in a turtle.
walterfuster said:
The thing is, you can't unlock the bootloader without first having su permissions.
AR device version shouldn't be a problem.
Mine is Argentinian too and I easily rooted it.
Try with an older version of Kingroot. You can easily find it around apk's sites.
If no luck, try flashing an H440N kdz (I'm on POL v10i) with LG Flash Tool 2014, and see what happens.
You can do a dirty flash if you don't want to lose your data.
P.S.: I even switched from Kingroot to SuperSU. I highly recommend this, Kingroot convert your phone in a turtle.
Click to expand...
Click to collapse
Huh, that's odd then, that Kingroot couldn't do it. I'll keep looking into it, then. Thanks for the help, will report back.
walterfuster said:
The thing is, you can't unlock the bootloader without first having su permissions.
AR device version shouldn't be a problem.
Mine is Argentinian too and I easily rooted it.
Try with an older version of Kingroot. You can easily find it around apk's sites.
If no luck, try flashing an H440N kdz (I'm on POL v10i) with LG Flash Tool 2014, and see what happens.
You can do a dirty flash if you don't want to lose your data.
P.S.: I even switched from Kingroot to SuperSU. I highly recommend this. Kingroot converts your phone in a turtle.
Click to expand...
Click to collapse
Hello there. I managed to use kingroot to root one of the two spirits I have (the other one still doesn't budge, for whatever reason) and indeed it turns the phone into a turtle. I was wondering, is it possible to flash superSU without flashing marshamallow before? Not that I'd mind flashing it, but without the ability to use an SD card as internal storage the main advantage is gone, and I wouldn't wanna have MM if it hurts battery time or fluidity of the phone.
Kon22 said:
Hello there. I managed to use kingroot to root one of the two spirits I have (the other one still doesn't budge, for whatever reason) and indeed it turns the phone into a turtle. I was wondering, is it possible to flash superSU without flashing marshamallow before? Not that I'd mind flashing it, but without the ability to use an SD card as internal storage the main advantage is gone, and I wouldn't wanna have MM if it hurts battery time or fluidity of the phone.
Click to expand...
Click to collapse
If I don't get wrong, you want to stay on a SuperSU rooted LP, right?
Well, you can get that, not by flashing, but by replacing Kingroot with SuperSU.
you'll have to do the following:
https://forum.xda-developers.com/a3...place-kingroot-kinguser-t3308989/post65167979
P.S.: If you decide to stay on LP for definitely, I highly recommend you apply the Tomo's tweaks.
They get the most of Spirit running LP:
https://forum.xda-developers.com/lg...formance-battery-saving-t3217133/post63121297
So if I get this right I should be able to use custom roms after doing this procedure? I've been asking about in the LOS14.1 rom thread but people talking about a bluescreen when they ran out of signal in the argentinian model scared me off. I cant get a new phone atm in case I brick this one. Nobody could give me a definitive answer about it so far.
Niku200 said:
So if I get this right I should be able to use custom roms after doing this procedure? I've been asking about in the LOS14.1 rom thread but people talking about a bluescreen when they ran out of signal in the argentinian model scared me off. I cant get a new phone atm in case I brick this one. Nobody could give me a definitive answer about it so far.
Click to expand...
Click to collapse
Yes, following this procedure can get your bootloader unlocked. Also LOS does have that blue scrren error, only if you don't have network service. However it's not that big of a issue. You can prevent blue screen by using airplane mode.
mayankjet said:
Yes, following this procedure can get your bootloader unlocked. Also LOS does have that blue scrren error, only if you don't have network service. However it's not that big of a issue. You can prevent blue screen by using airplane mode.
Click to expand...
Click to collapse
I knew about that workaround but signal is pretty unstable where I live. Specially when I travel and I like to use spotify while doing so. I'd like to avoid it as much as I can. I guess I'll give it a go and if it fails I can go back flashing a stock firmware.
Niku200 said:
I knew about that workaround but signal is pretty unstable where I live. Specially when I travel and I like to use spotify while doing so. I'd like to avoid it as much as I can. I guess I'll give it a go and if it fails I can go back flashing a stock firmware.
Click to expand...
Click to collapse
Okay.
So, I've been trying to download this several times but I'm always hit with a trafic limit from the person who shared it. Would somebody share me the files somehow?
I want to install magisk, but I still want to be able to take ota updates. I also want to keep the stock recovery if possible. Is there a good way to do this, or will I have to flash TWRP?
Edit: it looks like magisk v15 is bricking 7x's. Should I wait a bit before I try to install it?
I Could Be Dead Wrong But..
epickid37 said:
I want to install magisk, but I still want to be able to take ota updates. I also want to keep the stock recovery if possible. Is there a good way to do this, or will I have to flash TWRP?
Edit: it looks like magisk v15 is bricking 7x's. Should I wait a bit before I try to install it?
Click to expand...
Click to collapse
I Do Believe You Need To Be Rooted To Install Magisk...
And to root you have to Unlock your Bootloader.
Your device will Reject Any and All O.T.A.'s with an Unsecure (A.K.A. Unlocked) Bootloader.
That's why you get that hidious *Warning!* message everytime you reboot.. your device knows it's unsecured.
You can sideload all the upcoming O.T.A.'s when someone makes them available.. I kinda doubt that is going to be on day one though.
The Nice thing about those of you that are rooting is, you can just pay the $18.00 bucks and bring your phone back to stock with that D.C. tool that is being discussed in the Q & A.. I assume it works on all variants ?
Anyway.. good luck to you if you do decide to go ahead and unlock that Bootloader.
RaiderWill said:
I Do Believe You Need To Be Rooted To Install Magisk...
And to root you have to Unlock your Bootloader.
Your device will Reject Any and All O.T.A.'s with an Unsecure (A.K.A. Unlocked) Bootloader.
That's why you get that hidious *Warning!* message everytime you reboot.. your device knows it's unsecured.
You can sideload all the upcoming O.T.A.'s when someone makes them available.. I kinda doubt that is going to be on day one though.
The Nice thing about those of you that are rooting is, you can just pay the $18.00 bucks and bring your phone back to stock with that D.C. tool that is being discussed in the Q & A.. I assume it works on all variants ?
Anyway.. good luck to you if you do decide to go ahead and unlock that Bootloader.
Click to expand...
Click to collapse
Magisk is a rooting method, I know from experience that you don't already have to have a rooted phone. Also magisk v14 added a feature where you could patch the boot image and flash it via adb.
What's this "D.C. tool"? It sound interesting
Damn.. It's Been So Long..
epickid37 said:
Magisk is a rooting method, I know from experience that you don't already have to have a rooted phone. Also magisk v14 added a feature where you could patch the boot image and flash it via adb.
What's this "D.C. tool"? It sound interesting
Click to expand...
Click to collapse
You Are 100% Correct...
You're conversing with an old "SuperSu" guy here.. I totally forgot mag's is a rooter like Su.
But you still have to Unlock that loader to make it happen.. You are not going to get any O.T.A.'s
I know Magisk can hide root for things like netflix... But not to recieve Vendor Updates.. unless things have changed drasticly.. please correct me if I'm wrong..
But again.. sideloading is always an option.
RaiderWill said:
You Are 100% Correct...
You're conversing with an old "SuperSu" guy here.. I totally forgot mag's is a rooter like Su.
But you still have to Unlock that loader to make it happen.. You are not going to get any O.T.A.'s
I know Magisk can hide root for things like netflix... But not to recieve Vendor Updates.. unless things have changed drasticly.. please correct me if I'm wrong..
But again.. sideloading is always an option.
Click to expand...
Click to collapse
I'm probably wrong, but from what I've read, you can still take ota's with an unlocked bootloader?
A Virgin...
epickid37 said:
I'm probably wrong, but from what I've read, you can still take ota's with an unlocked bootloader?
Click to expand...
Click to collapse
When It Comes To Huawei.. I'm A Virgin...
Every other phone I've seen, the O.T.A. will notify you that your system has been "Modified" and will not attempt the update.
When you root.. Your Phone Becomes Insecure.. and is vernable to Malware, Virus, Hacks and god knows what else.
O.T.A.'s are Signed Packages.. They Ain't Going To Da Hood To Do Business...
Keep it locked if you want everything on day 1.. Then you can Root to your hearts content.
epickid37 said:
I'm probably wrong, but from what I've read, you can still take ota's with an unlocked bootloader?
Click to expand...
Click to collapse
Note u definitely can't take OTA updates with Magisk installed. What's worse is the normal recovery doesn't have a proper update option so u'll have to use Huawei's Dload method which fails if u have tampered the system. Restoring to the stock ROM with a locked bootloader is also incredibly hard on Huawei/Honor devices.
Sent from my Honor 8 using XDA Labs
ayush rao said:
Note u definitely can't take OTA updates with Magisk installed. What's worse is the normal recovery doesn't have a proper update option so u'll have to use Huawei's Dload method which fails if u have tampered the system. Restoring to the stock ROM with a locked bootloader is also incredibly hard on Huawei/Honor devices.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
Here's how to take ota updates with magisk. But what your saying is Huawei doesn't use recovery to update, they use proprietary methods that detect system modifications, right?
epickid37 said:
Here's how to take ota updates with magisk. But what your saying is Huawei doesn't use recovery to update, they use proprietary methods that detect system modifications, right?
Click to expand...
Click to collapse
Thats not what I meant, Huawei does use the recovery to update like any other phone but their recovery doesn't let the user to sideload their own OTA files. U'll have to use their Dload method which is an absolute pain.
Further, the Magisk page u posted here mentions the system and vendor must not be modded so that means you can't use any app like Titanium Backup to block or uninstall apps since it tampers the system. Thats really annoying since the whole point of rooting is to modify the system. Also if u used TWRP then u will have a hard time trying to find the right recovery file corresponding to the firmware u r on. It is really hard for Honor devices since u'll have to download a large file and, using a tool on XDA, extract the images u need. IMO rooting this phone is worth it right now especially since it is new and will constantly be recieving OTAs in the coming months.
Sent from my Honor 8 using XDA Labs
ayush rao said:
Thats not what I meant, Huawei does use the recovery to update like any other phone but their recovery doesn't let the user to sideload their own OTA files. U'll have to use their Dload method which is an absolute pain.
Further, the Magisk page u posted here mentions the system and vendor must not be modded so that means you can't use any app like Titanium Backup to block or uninstall apps since it tampers the system. Thats really annoying since the whole point of rooting is to modify the system. Also if u used TWRP then u will have a hard time trying to find the right recovery file corresponding to the firmware u r on. It is really hard for Honor devices since u'll have to download a large file and, using a tool on XDA, extract the images u need. IMO rooting this phone is worth it right now especially since it is new and will constantly be recieving OTAs in the coming months.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
Ah, ok. Thank for your help!
I rooted my a325m by patching the stock AP file with magisk, had to use FRP hijacker by hagard to be able to flash the patched file. I root uninstalled several apps for debloating. The phone worked fine for like a couple of weeks, and now, suddenly I find there's the no SIM indication, and in settings -> about phone it says IMEI: unknown, and in software information it says bandbase version: unknown.
The firmware version I used was exactly the same as when I bought it, A325MUBU2AUJ4, with the right csc (ARO in my case).
EDIT: after a couple reboots, the bandbase version now shows, but still no IMEI or SIM detected.
Can anyone help me? What happened? What can I do? Thanks in advance!
flash all the with odin the correct rom. the twrp unstable and more like shell and who knows what bugs have magisk. until why have a good recovery i would no root my phone reallly if you want to unisstall the software from samsung and google i would say to use the universal debload https://github.com/0x192/universal-android-debloater.
UPDATE: it got unknown baseband againI
I relocked the bootloader and now in download mode I have an option to "show barcodes" pressing the side button. The barcodes show the right IMEI and serial number. Maybe stuff wasn't erased, just inaccesible by the rom?
I was told by a technician to flash the original ROM (already did) then root again. Tried several versions but not an older bandbase because downgrade is forbidden by the bootloader, apparently, to no avail. Would try a newer baseband but i'm afraid it will not work and will be unable to go back to the origial baseband version.
Weird thing is, there is the EFS directory but no /data/nvram or /dev/nvram
Same happened to me.
I tried everything I could think of to get the IMEI back and couldn't.
It was still under warranty and I took it to Samsung.
Before taking it I unrooted it and locked it again.
They fixed it for me with no problem.
edukardo said:
Same happened to me.
I tried everything I could think of to get the IMEI back and couldn't.
It was still under warranty and I took it to Samsung.
Before taking it I unrooted it and locked it again.
They fixed it for me with no problem.
Click to expand...
Click to collapse
How did you root it?
as I understand, after rooting, warranty is void since it implies flashing a magisk patched boot image or AP tar. In my case I was indeed able to relock the bootloader and flash the original firmware but upon entering download mode, it shows "warranty void 0x01".
was it the same in your case?
Flashed original firmware, relocked phone, and then went to Samsung Office. I had no problem with it
edukardo said:
Flashed original firmware, relocked phone, and then went to Samsung Office. I had no problem with it
Click to expand...
Click to collapse
most likely the warranty vod bit was on (you can check it yoursef by entering odin mode) and they didn't notice
so you got it fixed for free?
did they mention what did the fix consist in? I heard they say they change the motherboard, which is a lie, they just write the nvram or efs with the right stuff
ah sos de argentina? lol where did you take it? to a samsung store? I'm from neuquen and got it at musimundo, but here's a samgung store too
myself i was thinking of waiting for an update which should be soon, lock bootloader, flash some official rom and pull off the cable so it gives an upgrade error and doesn't enter download mode, then take it to the store
Unroot before update and unlock
wipe the cache partition . then reset the phone using recovery mode . this is at you own risk .
did you fix it?
applesucksLmao said:
did you fix it?
Click to expand...
Click to collapse
nope, went to samsung, got rejected cause warranty bit on, no choice but take it to a service and I suppose they could do something with Chimera Tool, Z3X or something like that, which, as I've seen, claims to fix it in minutes (and the client gets charged handsomely, like 100 USD)
From Samsung I got the same bullsh*t I read in some threads: "this phone has been tampered with and it's a hardware problem, the board must be replaced"
For the technically savvy, I got a strange Magisk log which kind of looks like it may be the problem. It seems to try to "unlock"* some devices on bootup but gets "permission denied". One of them may be the nvram or something like that. I have an EFS directory but no NVRAM directory anywhere or /dev/nvram.
very strange, i guess we gotta not use magisk until its bug fixed.. i have seen other people have the same problem too, but anyways, i sent my phone to get probably JTagged for 54 us dollars, if they fix it well, great right, but if they dont i guess ill have to buy another motherboard from samsung or go to another city... and the best part is that while my phone is there, im using an S4 mini from 2013 with custom android 11 rom hehe
i saw that auh firmware causes empty imei in another thread and to flash aug, maybe you could try this? https://forum.xda-developers.com/t/has-anyone-successfully-rooted-this-a32-4g.4326193/post-85788523
applesucksLmao said:
very strange, i guess we gotta not use magisk until its bug fixed.. i have seen other people have the same problem too, but anyways, i sent my phone to get probably JTagged for 54 us dollars, if they fix it well, great right, but if they dont i guess ill have to buy another motherboard from samsung or go to another city... and the best part is that while my phone is there, im using an S4 mini from 2013 with custom android 11 rom hehe
Click to expand...
Click to collapse
or atleast use magisk with aug or even older firmware if you can... is your a32 A325M or A325F?
well, your firmware is A325MUB"U2"AUJ4 and that means u cant downgrade to older versions that have binary1 so maybe you could try using samsung's new version which was released past month
applesucksLmao said:
very strange, i guess we gotta not use magisk until its bug fixed.. i have seen other people have the same problem too, but anyways, i sent my phone to get probably JTagged for 54 us dollars, if they fix it well, great right, but if they dont i guess ill have to buy another motherboard from samsung or go to another city... and the best part is that while my phone is there, im using an S4 mini from 2013 with custom android 11 rom hehe
Click to expand...
Click to collapse
what's JTagged?
applesucksLmao said:
i saw that auh firmware causes empty imei in another thread and to flash aug, maybe you could try this? https://forum.xda-developers.com/t/has-anyone-successfully-rooted-this-a32-4g.4326193/post-85788523
Click to expand...
Click to collapse
I found it impossible to downgrade, download mode doesn't allow it. Couldn't find a tutorial to do it either.
applesucksLmao said:
well, your firmware is A325MUB"U2"AUJ4 and that means u cant downgrade to older versions that have binary1 so maybe you could try using samsung's new version which was released past month
Click to expand...
Click to collapse
I did, I tried all combinations rooting/unrooting with the new magisk 24.1 the new version, A325MUBS2AVA1
It's a 325m btw