I want to root my Samsung A025v but it is a USA based Snapdragon Verizon model. I have done the date and time, software update trick a bunch of times but nothing happened. Am I just not getting into it?
U.S. variants always have locked bootloaders. You're not going to be able to root it via conventional means. I think there was a paid service here in XDA but I don't know if this phone is supported.
Try this : rootingsteps.com/root-samsung-galaxy-a02s/
How To Root Samsung Galaxy A02/A02S Using Magisk
On this page, we will guide you on how to root the Samsung Galaxy A02/A02S without the TWRP Recovery. To flash the rooting file, you need to first unlock
www.getdroidtips.com
I have the us version as well and i use this guide
Related
Hello everyone!
I have a rooted galaxy s2 (I see the superuser app on my phone) running android 2.3.4. This is a Bell phone. What I would like to do is unroot the phone, then update it to 2.3.6 or wtv update is available through kies (normal update) and then root it again and unlock it using Galaxy_S unlock so I can use it with Fido.
I have a few questions:
Is it even possible to do this?
Can anyone tell me if this is a good method? how to do it properly? or any better alternative methods?
also, if I use this unlock, is it permanent? or do I have to re-unlock the phone every time I loose root/update firmware
ANY help is appreciated, i'm trying to put all of this together and it's not very easy. I bought the phone rooted...but it's not unlocked (as it doesn't work with fido), needeless to say I have no clue how it was rooted and what was used (or if it even matters).
EXTRA infro: (when I press *#1234#, I get:
PDA: I9100XXKG6
Phone:...XXKG2
CSC:...OXAKG
Tell me 2 things, why do you need 2.3.6 and do you have an app called CWM on your phone? The icon looks like a gear
1. first unlock your phone, it is permanent you do not need to unlock if you flash again.
2. you may not be able to use kies to update as the kernal which kies uses to update was changed when it was rooted.
Do you perfer stock or custom firmware ?
you can get the latest stock firmware and installation guide from this thread.
http://forum.xda-developers.com/showthread.php?t=1075278
if you want custom search in Android development forum.
3. you will lose your rooting when you update firmware. All you need to do is reroot your phone it is easy. follow instructions in this thread.
http://forum.xda-developers.com/showthread.php?t=1103399.
Hey all, I'm looking to eventually install CyanogenMod 10.1 on my verizon galaxy S4. However, being a complete novice on this type of thing makes me a bit nervous about bricking my expensive phone.
So, I thought it would be good to try and understand the process of rooting and installing the custom rom. Could you guys help me out? I'll list what I know.
First thing I want to do is backup the Android stock rom that came with the phone. I have read that rooting or installing a custom rom (like CM) will void my warranty, so that's not good. But re-flashing the stock android that came with the phone will remedy this. To do this, I found this guide on using Nandroid. I don't think the CWM way will work for Verizon galaxy S4 (read that somewhere, but correct me if that's wrong).
However, it says that I am required to have a rooted phone first before running Nandroid.
Because Verizon's Galaxy S4 comes with a locked bootloader, and an unrooted phone, I need a way to root my phone. I found this nifty all-in-one tool by bhp090808.
The way that tool works is it exploits something in verizon's pre-release kernel of the S4, so it flashes the phone with the pre-release kernel, gets root privileges, then reflashes the stock kernel. Once this is done, my phone will be rooted and I assume I can use Nandroid to backup the stock android on the phone.
This is where I'm stuck. I have a few questions regarding various parts from here on:
1) Since the phone is rooted and I run Nandroid to back up the stock android rom, wouldn't Nandroid back up the stock android rom with the root access? If I needed to return my phone to Verizon under warranty, re-flashing this stock rom would still void my warranty because it still has root access? Is there a way to completely revert to stock android with verizon's unrooted and locked bootloader status (and whatever else)?
2) Does the all-in-one tool unlock bootloader? I found a tool called loki which will unlock the bootloader so that I can install custom roms like CyanogenMod. I looked in the all-in-one tool's zip folder, and it contains a file called "loki_flash", but I am unsure if this is unlocking the bootloader or not.
3) Can I re-flash a stock android if I brick my phone? What exactly does 'bricking' the phone mean?
goodmedic said:
Hey all, I'm looking to eventually install CyanogenMod 10.1 on my verizon galaxy S4. However, being a complete novice on this type of thing makes me a bit nervous about bricking my expensive phone.
So, I thought it would be good to try and understand the process of rooting and installing the custom rom. Could you guys help me out? I'll list what I know.
First thing I want to do is backup the Android stock rom that came with the phone. I have read that rooting or installing a custom rom (like CM) will void my warranty, so that's not good. But re-flashing the stock android that came with the phone will remedy this. To do this, I found this guide on using Nandroid. I don't think the CWM way will work for Verizon galaxy S4 (read that somewhere, but correct me if that's wrong).
However, it says that I am required to have a rooted phone first before running Nandroid.
Because Verizon's Galaxy S4 comes with a locked bootloader, and an unrooted phone, I need a way to root my phone. I found this nifty all-in-one tool by bhp090808.
The way that tool works is it exploits something in verizon's pre-release kernel of the S4, so it flashes the phone with the pre-release kernel, gets root privileges, then reflashes the stock kernel. Once this is done, my phone will be rooted and I assume I can use Nandroid to backup the stock android on the phone.
This is where I'm stuck. I have a few questions regarding various parts from here on:
1) Since the phone is rooted and I run Nandroid to back up the stock android rom, wouldn't Nandroid back up the stock android rom with the root access? If I needed to return my phone to Verizon under warranty, re-flashing this stock rom would still void my warranty because it still has root access? Is there a way to completely revert to stock android with verizon's unrooted and locked bootloader status (and whatever else)?
2) Does the all-in-one tool unlock bootloader? I found a tool called loki which will unlock the bootloader so that I can install custom roms like CyanogenMod. I looked in the all-in-one tool's zip folder, and it contains a file called "loki_flash", but I am unsure if this is unlocking the bootloader or not.
3) Can I re-flash a stock android if I brick my phone? What exactly does 'bricking' the phone mean?
Click to expand...
Click to collapse
I see its been a few days and no one has replied so I will do my best to share what knowledge I have. I've been heavily flashing custom ROMs on my ASUS tablet now for the better part of a year and just got my Verizon GS4, so I have alot of the same questions as you.
1) I'm going to answer this in two parts.
Nandroid, in my experience, refers to the type of backup, not necessarily the process by which to backup. Most common recoveries, including ClockworkMod and TWRP have a feature to create a 'nandroid backup'. This can take some time and files can be quite large, as they copy pretty much every single file on your device; almost like creating a snapshot of your device in that moment in time.
To answer the later part of this question, (typically speaking) once you unlock a bootloader you cannot re-lock it, but that could be different for phones (my knowledge in phones is limited). And yes, using a nandroid backup will back up your device with root access, but using a tool such as Rom Toolbox, you can easily un-root (the program features a 'permanent unroot option'). For one, I would imagine that flashing the stock kernel would overwrite the root, as like you said earlier in the post the current root exploit works by flashing a pre-release kernel, applying root to the device, then re-flashing the current stock kernel. Another way to lose root is to get an over-the-air (OTA) update. You will see programs like OTA Rootkeeper that work to circumvent this, but in your case that may be a valid way to cover your arse in case you need to return it under VZW warranty (it is for this reason that I always buy Best Buy protection plans, because they could care less about the software state about your device [Disclaimer: I worked for Geek Squad so I have /somewhat/ intimate knowledge in this matter])
2) I just rooted my GS4 a few days ago, and nothing I read indicated that the all-in-one tool would unlock the bootloader. If you read the documentation about Loki, he explains this fact. I just found a good video (although it uses TWRP and GooManager instead of ROMManager and CWM) explaining that there isn't a bootloader "unlock" just yet; rather its a workaround to the bootloader that allows us to get custom ROMs on our devices (video is here)
3) "Bricking" a device means rendering the device useless; it won't operate to any fashion that it is useful to you, so its no better than a brick or a paper weight, etc. I would imagine you can re-flash a stock verizon ROM/kernel to restore any screw-ups, but keep in mind this device was released less than three months ago and any development is relatively new. Yes, we have had other Galaxy S series phones, but the S4 has this whole KNOX nonsense that is specifically designed to prevent the kinds of activities we do here on this forum
I really hope that helps. If I said anything that is incorrect, please please feel free to correct it so that at least we can all learn the proper information.
Thanks,
Opethfan89
goodmedic said:
Hey all, I'm looking to eventually install CyanogenMod 10.1 on my verizon galaxy S4. However, being a complete novice on this type of thing makes me a bit nervous about bricking my expensive phone.
So, I thought it would be good to try and understand the process of rooting and installing the custom rom. Could you guys help me out? I'll list what I know.
First thing I want to do is backup the Android stock rom that came with the phone. I have read that rooting or installing a custom rom (like CM) will void my warranty, so that's not good. But re-flashing the stock android that came with the phone will remedy this. To do this, I found this guide on using Nandroid. I don't think the CWM way will work for Verizon galaxy S4 (read that somewhere, but correct me if that's wrong).
However, it says that I am required to have a rooted phone first before running Nandroid.
Because Verizon's Galaxy S4 comes with a locked bootloader, and an unrooted phone, I need a way to root my phone. I found this nifty all-in-one tool by bhp090808.
The way that tool works is it exploits something in verizon's pre-release kernel of the S4, so it flashes the phone with the pre-release kernel, gets root privileges, then reflashes the stock kernel. Once this is done, my phone will be rooted and I assume I can use Nandroid to backup the stock android on the phone.
This is where I'm stuck. I have a few questions regarding various parts from here on:
1) Since the phone is rooted and I run Nandroid to back up the stock android rom, wouldn't Nandroid back up the stock android rom with the root access? If I needed to return my phone to Verizon under warranty, re-flashing this stock rom would still void my warranty because it still has root access? Is there a way to completely revert to stock android with verizon's unrooted and locked bootloader status (and whatever else)?
2) Does the all-in-one tool unlock bootloader? I found a tool called loki which will unlock the bootloader so that I can install custom roms like CyanogenMod. I looked in the all-in-one tool's zip folder, and it contains a file called "loki_flash", but I am unsure if this is unlocking the bootloader or not.
3) Can I re-flash a stock android if I brick my phone? What exactly does 'bricking' the phone mean?
Click to expand...
Click to collapse
The S4 link in my signature has a few stock images to pick from. It will restore it to the original stock Verizon software that came with your phone.
DarkMenace said:
The S4 link in my signature has a few stock images to pick from. It will restore it to the original stock Verizon software that came with your phone.
Click to expand...
Click to collapse
Does the 'Ad-Free' APK I see available on that website work better than jRummy's AdBlocker? I installed it and it detects ads (like in ASTRO, Zedge, and a few others) but doesn't block them even though I have all the settings turned ON and have rebooted when requested.
That said, thanks for the link. I've bookmarked it for future reference and its good to know there are backups available in case anything goes bad.
Are you able to elaborate on how these are flashed? Via ODIN, or can you flash it via CWM/TWRP?
Thanks,
Opethfan89
opethfan89 said:
Does the 'Ad-Free' APK I see available on that website work better than jRummy's AdBlocker? I installed it and it detects ads (like in ASTRO, Zedge, and a few others) but doesn't block them even though I have all the settings turned ON and have rebooted when requested.
That said, thanks for the link. I've bookmarked it for future reference and its good to know there are backups available in case anything goes bad.
Are you able to elaborate on how these are flashed? Via ODIN, or can you flash it via CWM/TWRP?
Thanks,
Opethfan89
Click to expand...
Click to collapse
I'm not n sure. It's the only one I ever used for banner blocking. You use the files with Odin as well after they are extracted.
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
Hi All,
Switching from a Verizon S4 to a T-Mobile S5 (switched because of Net Neutrality lobbying Verizon is doing). I found a thread on here about a root toolkit. It seemed a little confusing and I wasn't sure if it would work. What are my options for ways to root? On VZ I had to tarball an unlocked bootloader and download root binaries before installing a custom recovery. Is there something similar for T-Mobile devices?
Dolphlungegrin said:
Hi All,
Switching from a Verizon S4 to a T-Mobile S5 (switched because of Net Neutrality lobbying Verizon is doing). I found a thread on here about a root toolkit. It seemed a little confusing and I wasn't sure if it would work. What are my options for ways to root? On VZ I had to tarball an unlocked bootloader and download root binaries before installing a custom recovery. Is there something similar for T-Mobile devices?
Click to expand...
Click to collapse
The tmobile version has a unlocked bootloader. Very easy to root and install custom recovery. Its actually plastered all over the place. Weird you missed it. But here it is again. Very easy.
http://forum.xda-developers.com/showthread.php?t=2713950
To get custom recovery just download TWRP Manager from Play, and install it.
Carloskeee said:
The tmobile version has a unlocked bootloader. Very easy to root and install custom recovery. Its actually plastered all over the place. Weird you missed it. But here it is again. Very easy.
http://forum.xda-developers.com/showthread.php?t=2713950
To get custom recovery just download TWRP Manager from Play, and install it.
Click to expand...
Click to collapse
Hey thanks
Just picked up a Verizon Samsung Galaxy S4 SCH-I545. The Wifi stopped working after a factory reset. Read that the name of a config file may need changed.
Could someone help me with the best instructions for rooting this phone or any other troubleshooting to get the WiFi to work again?
hamiltonfighter said:
Just picked up a Verizon Samsung Galaxy S4 SCH-I545. The Wifi stopped working after a factory reset. Read that the name of a config file may need changed.
Could someone help me with the best instructions for rooting this phone or any other troubleshooting to get the WiFi to work again?
Click to expand...
Click to collapse
Root with kingroot. Make sure it's kingroot and not kingo root. Kingo root is a mess. You can also root with wonder share so you can use superSU right off the bat instead of kingroot. As for the Wi-Fi , the only thing I can recommend is rooting then installing stang5litre ROM which is touchwiz based due to the locked bootloader. You can use flash fire with any firmware, given it is the right version and I think safe strap recovery with an older firmware.
Hi !
I just got a brand new Mate 10 Pro, and managed to get a bootloader unlock code since I haven't updated the phone yet. I plan on unlocking it and then updating it to the latest version of Android.
I spent quite some time trying to figure out in which cases the device could brick, but since it seems that it can brick pretty easily I haven't found a complete answer.
Eventually, I would like to know if there a risk of bricking the device when updating with the official OTA after unlocking the bootloader ? I know that every bit of tinkering could potentially brick a device, but I have not found a similar case to this one. This is not totally related, but I also plan on rooting the device with Magisk once I successfully update it so feel free to tell me if there is something I should be aware of.
Thanks a lot XDA !
Unlocking
Pouni said:
Hi !
I just got a brand new Mate 10 Pro, and managed to get a bootloader unlock code since I haven't updated the phone yet. I plan on unlocking it and then updating it to the latest version of Android.
I spent quite some time trying to figure out in which cases the device could brick, but since it seems that it can brick pretty easily I haven't found a complete answer.
Eventually, I would like to know if there a risk of bricking the device when updating with the official OTA after unlocking the bootloader ? I know that every bit of tinkering could potentially brick a device, but I have not found a similar case to this one. This is not totally related, but I also plan on rooting the device with Magisk once I successfully update it so feel free to tell me if there is something I should be aware of.
Thanks a lot XDA !
Click to expand...
Click to collapse
Depends on what version of the Mate 10 you have, the US version (BLA-A09) supposedly bricks very easily. Since Huawei stopped providing unlock codes in July I'm wondering where you get a valid unlock code. Also, unlocking voids your warranty, as does any modifications to the software. Also be advised the once you root you will no longer be getting any updates OTA and will have to manually flash updated system images (drastically increasing you risk of bricking your device with every update)
revjamescarver said:
Depends on what version of the Mate 10 you have, the US version (BLA-A09) supposedly bricks very easily. Since Huawei stopped providing unlock codes in July I'm wondering where you get a valid unlock code. Also, unlocking voids your warranty, as does any modifications to the software. Also be advised the once you root you will no longer be getting any updates OTA and will have to manually flash updated system images (drastically increasing you risk of bricking your device with every update)
Click to expand...
Click to collapse
There are multiple sources for valid unlock codes, though all are paid. (OP probably used DC as he said he didn't update phone yet)
Rooting does not disable OTA. You will still receive them. Only problem is installing them... It should go fine if you flash back stock ramdisk and recovery_ramdisk, this will remove both Magisk and TWRP.
However, if you have modified any other partition it may not install anyway, in that case you can try going to menu in System Update and select Download latest full package. This would install FullOTA rather than regular OTA.
Or you can use HuRUpdater to install firmware using TWRP.
One way to hard-brick right now is to downgrade from a firmware using new bootloader to one using old bootloader. This will give you a black screen.
ante0 said:
There are multiple sources for valid unlock codes, though all are paid. (OP probably used DC as he said he didn't update phone yet)
Rooting does not disable OTA. You will still receive them. Only problem is installing them... It should go fine if you flash back stock ramdisk and recovery_ramdisk, this will remove both Magisk and TWRP.
However, if you have modified any other partition it may not install anyway, in that case you can try going to menu in System Update and select Download latest full package. This would install FullOTA rather than regular OTA.
Or you can use HuRUpdater to install firmware using TWRP.
One way to hard-brick right now is to downgrade from a firmware using new bootloader to one using old bootloader. This will give you a black screen.
Click to expand...
Click to collapse
The plan is to update to a stable and recent version using OTA (from BLA-L29 8.0.0.120(C432) to BLA-L29 8.0.0.157(C432)-FULL) and then root this version. Once I have root on this latest version, I plan on using it as long as the phone works, so updating to newer versions in the future and risking to brick the device shouldn't be a problem. I just want a functional root with a decent version of stock EMUI. Would updating from stock locked 120 to 157 and then unlocking + rooting be safe ? Thanks for the valuable info !
revjamescarver said:
Depends on what version of the Mate 10 you have, the US version (BLA-A09) supposedly bricks very easily. Since Huawei stopped providing unlock codes in July I'm wondering where you get a valid unlock code. Also, unlocking voids your warranty, as does any modifications to the software. Also be advised the once you root you will no longer be getting any updates OTA and will have to manually flash updated system images (drastically increasing you risk of bricking your device with every update)
Click to expand...
Click to collapse
I used DC Unlocker since my device was still on an old version, as Ante0 said ! I think that if I ever want to update, I'll remove root (getting back to stock) and then update with OTA. Thanks for the warning, I haven't rooted nor unlocked a device since 2 years and things have changed with the new methods (Magisk etc...).
Pouni said:
The plan is to update to a stable and recent version using OTA (from BLA-L29 8.0.0.120(C432) to BLA-L29 8.0.0.157(C432)-FULL) and then root this version. Once I have root on this latest version, I plan on using it as long as the phone works, so updating to newer versions in the future and risking to brick the device shouldn't be a problem. I just want a functional root with a decent version of stock EMUI. Would updating from stock locked 120 to 157 and then unlocking + rooting be safe ? Thanks for the valuable info !
Click to expand...
Click to collapse
Yes, that should be fine. You could just unlock bootloader right away and then update, if you wanted to.
Just be cautious, do not downgrade past B146 on C432 (if you ever plan to downgrade), that was the first build with the new bootloader so going to B145 or lower will result in a brick.
ante0 said:
Yes, that should be fine. You could just unlock bootloader right away and then update, if you wanted to.
Just be cautious, do not downgrade past B146 on C432 (if you ever plan to downgrade), that was the first build with the new bootloader so going to B145 or lower will result in a brick.
Click to expand...
Click to collapse
Thanks again for the valuable information. Now I'm debating whether I should unlock now or after the update I don't plan on downgrading, except if I have problems after updating and HAVE to downgrade. Last question if I may: I plan on using Magisk (latest version, I guess) to root once I update to BLA-L29 8.0.0.157(C432)-FULL. But I've seen that Magisk/TWRP doesn't necessarily work on the latest versions for some people when using the "basic" way of installing it, I tried to search for an up-to-date guide to rooting but didn't find anything, is the "old" way still good ?
Edit: When I said "basic/old" way of installing Magisk, I meant that it seems impossible to get it to work by installing TWRP and flashing Magisk through TWRP, but that it seems to work by finding a patched "ramdisk.img" with Magisk. Is the latest option a reliable way to get root on BLA-L29 157(C432), considering that I would not have TWRP to restore a backup if using this method ?
Edit 2: Tried the usual way (flashing Magisk zip through TWRP) and it seems to work ! Thank you !