Related
So I've been reading all these articles about rooting the Samsung Captivate and they all seem to say that rooting gives you the equivalent of admin access and basically its really useful.
What I want to know is if it is safe? I'm not really good at these things and I'm afraid that if I root it I might just screw up my phone because I don't understand what I'm doing. Also I've read that rooting your phone can sometimes render your phone unusable...is that a serious issue for the captivate?
I mainly want to just be able to have a complete backup, and be able to download apps from third party websites. (I have AT&T) I think rooting lets you do all that.
Also, I see all this talk about ROM's or something and I really don't understand what that is.
If i root my phone, will it wipe any data I have stored on my phone, like contacts and apps or something? Will I still be able to receive software updates from AT&T?
Please help...Thanks sooo much!!!
Hello there,
In first place, ROMs it's the name we usually call for the OS images that you run in your phone. You have the manufacturer ROM, with (probably) operator stuff in it. You can have a very different OS image, with different layout, more options (there are beautiful things around like CyanogenMod), etc. So, installing new ROMs sometimes is like installing a new Android OS on your phone (not exactly but something like that).
Rooting your phone doesn't clean your data, but it's always a good practice to do an application/data backup. Backup software: Titanium Backup (i use it and i really like it).
By adding an Android Recovery loader, you will have the possibility to make a nandroid backup which really allows you to keep EVERYTHING! (that happens after you root the phone, of course).
Advantages of having a rooted phone:
* removing operator applications you don't like in the standard ROM
* run 'root-only' software
* installing new ROMS
* upgrading the OS version of your phone to higher than supported by the manufacturer (some features may not work in this case)
Disadvantages:
* you may void your warranty
* you may brick your phone
* you can be messing around for a long time before having your phone stable once again (if you are curious to keep trying different ROMS, and app2sd and other add-ons)
Bricking your phone may happen if in the procedure to root your phone you need to flash it. In my case, I have a LG P500 and had the Android 2.2.2 - to root it I had to flash a 2.2 version and that was the risky part (some people say that 1 in every 4 phones get bricked in this procedure which I find very exagerated!)
So read the procedures carefully and have your phone with battery full before doing any rooting procedures. Do things calmly, follow every single step and if your get unsure of something, stop, ask, and after that move forward. You will be really happy when your phone is rooted !!
thank you!
The previous responder was a little zealous with the warnings. I have a Captivate, which is rooted and running a custom ROM (CyanogenMod 7).
First, rooting will not brick your phone. In theory, you void your warranty by doing so, but it's really easy to restore to factory state.
I don't recommend a custom ROM for someone who has basic questions like you've just asked. I'd reccommend first trying to get root, and run apps like Titanium backup, SGS Tools, etc. Be careful, research what you're doing, and make lots of backups. So long as you can enter download mode, you can flash back to factory.
Sent from my SGH-I897 using XDA Premium App
I was right where you are last August. I agree with ADT who says that you should root first and then work with apps that require root. Titanium Backup has been the most valuable for me out of all of those.
The chances of bricking your phone when you only root it is minimal. I guess it's possible, but honestly, I cannot see how. There are 2 files that are required called Bootloaders. Think of these as the AT&T screen and then the Samsung screen in a stock Captivate. If you do anything that changes/replaces these, you stand a great chance of bricking your phone. You don't do this when you root, only when you do something like try a custom ROM.
When you root your phone, you won't really notice anything different at first. However, if you look at your apps you will see a new one called Superuser. It is the app that is needed to run "rooted" apps. Also, once you root your phone, you will be able to take advantage of Amazon's market which has a free app a day.
If you decide to "unroot", it can be done rather easily, and you will lose the ability to do things like run rooted apps and Amazon apps (including any you downloaded).
I would recommend that you read as many posts about rooting as possible before you finally make the plunge. Read, read and read again. Make sure you know what you are doing before you do it and the risk of damage is minimal. I have bricked my phone many times, including the power button not working and was lucky to get it back. I learned the hard way by not knowing to read, read and read again.
Good luck!!
One other quick point. If you decide to play with custom ROMs, I recommend you stick with the ones that run Froyo, not Gingerbread. The Gingerbread ROMs are just starting to come out and I believe are not for someone just starting out. The instructions are a bit more complicated and the chance of bricking your phone are much greater.
The Froyo ROMs are much easier to install. However, as said in my last post, I'd get used to rooting your stock phone first before going that way.
stick with froyo and play with custom roms. To install custom roms just flash the custom rom in the recovery mode.
You're right guys. I mean, changing the bootloader is the risky part of the process, not the rooting itself. But the risky part is flashing a ROM (if that's needed to root the phone)...
In my case I had to downgrade my phone (LG P500) before applying root, so it was risky from the start - anyway, depending on the phone model, rooting / installling bootloader can be more or less risky...
Samsung. Couldnt he always ODIN back?
Sent from my ADR6300
Hey everyone,
Pray tell: what is the easiest way to root my TF and keep existing firmware? I'd like to have the option of flashing new roms and kernels down the road. I keep hearing that rooting takes less than 10 minutes, but the guides I'm seeing require ADB (which requires JDK) and some asus crapware that I just don't want to fill my computer with.
I remember how easy rooting was on the Gtab (upload a new recovery.zip to an SD card and reboot) and I'm hoping that it can be as easy here.
Thanks!
There's two way to root
http://androidroot.mobi/2011/06/13/nvflash-on-asus-transformer/
http://androidroot.mobi/asus-eee-pad-transformer-tf101-root-cwm-recovery/
read up and see what's "easier" for you.
See here http://forum.xda-developers.com/showthread.php?t=1125714
Pure Root 3.1 in Development-section. Extremely easy, did it twice in 2 days on 2 different TF's, 100% succes (guaranteed)
Good Luck
+1
Done one on Thursday and one last Monday. Works perfectly!
Skickat från min ASUS Eee Pad TF101
Ok, I got it. Once all the pre-reqs were in place, it wasn't so bad. Now I just have to uninstall all the garbage that asus loaded onto my pc. Thanks!
Is this root it still valid for Tf with all the latest updates (3.1, 8445 build)?
http://briefmobile.com/root-asus-transformer-on-android-3-1
Please help, I am new to Tf and Android. I can do hackintosh and iOS jailbreak. But this rooting thing is all new to me. It's all very confusing. Why are there so many different out there, e.g., in the developer section of this forum? What is Prime?
Finally, what is the downside of rooting? Some seemed to suggest you may not getting a dock firmware update, or app missing from market? What happens with the next android update if rooted?
Sorry for all the questions, I couldn't find a nice intro guide on Tf rooting for dummies.
ikeny said:
Is this root it still valid for Tf with all the latest updates (3.1, 8445 build)?
http://briefmobile.com/root-asus-transformer-on-android-3-1
Please help, I am new to Tf and Android. I can do hackintosh and iOS jailbreak. But this rooting thing is all new to me. It's all very confusing. Why are there so many different out there, e.g., in the developer section of this forum? What is Prime?
Finally, what is the downside of rooting? Some seemed to suggest you may not getting a dock firmware update, or app missing from market? What happens with the next android update if rooted?
Sorry for all the questions, I couldn't find a nice intro guide on Tf rooting for dummies.
Click to expand...
Click to collapse
Think of rooting as jailbreaking on steroids. "Root" in linux parlance means superuser: a system account with permission to do anything. Jailbreaking gives you the same thing, but jailbreaking does not give you the ability to install new firmware, which rooting does.
Prime is a ROM: a custom firmware. Unlike in the iOS world, android "allows" you to load a whole new operating system that you create yourself or someone else created (referred to as a ROM) onto your device. The ROMs are still Android operating systems, but there are a few advantages:
1) Unlike iOS updates, android updates don't get pushed out to everyone at the same time. Even if an update is available for your device, there is no guarantee that your phone carrier will push it out to you or won't sit on their hands for six months before doing it, effectively crippling your phone. A custom ROM allows you to bypass your carrier and load the updates yourself. This is not as big an issue on the transformer because there's no carrier to speak of. Still, if Asus takes its sweet time releasing the next version of android, you can bet it will be up here as a ROM first;
2) Most ROMs take out crapware that you don't want on your device; and
3) Many ROMs include performance optimizations or overclocks that wouldn't otherwise be possible.
I'm actually not sure if rooting by itself disables Asus updates...I don't think it does (but someone can correct me if I'm wrong). However, if you load Prime or another custom ROM, you will not have updates because there is nothing to update: you are not running Asus firmware anymore. You will have to wait for the developers of Prime to release new versions and flash them manually. Another downside of rooting is that you can lose you warranty. But if you root and need to make use of warranty, you can just unroot (see threads on that).
Hope that helps.
I've been looking to root my eepad. Running 3.2 stock
I've been lurking the forums for a little over a week but not sure if the nvflash method will work with the new update.
I've been reading through the unbricking thread, and this looks to be the easiest way to flash the device. but I still havent seen any confirmations that someone with 3.2 has performed the root.
http://forum.xda-developers.com/showthread.php?t=1123429&page=30
Unfortunately, since i've been lurking and reading, and not posting, I can't post in that thread to ask yet, since I don't have enough posts.
Here is my current build on the TF.
3.2
GPS: v1.5.0
WiFi: v5.2.52
BT: v6.19
kernel: 2.6.36.3 [email protected] #1
Build #: 8.6.5.6-20110726
many thanks for any assistance
-Ry
just wanted to add, I did some more digging on the Dev section and found BRK's method to root.
I read through the thread and they stated was functioning with stock non-rooted 3.2 running 8.6.5.6
I tried it out and it worked without a hitch!!!
YAAHOOOO!
installed cicso's anyconnect VPN client and Boom superuser access granted!
For anyone else wanting to try, make sure to just read through the instructions, then re-read, and re-read one more time. then take your time and you'll be good to go.
all the best!
-Ry
Find a good area, with plenty of sunlight. A steady supply of water is good as well. Be sure the ground is rich in nutrients.
Greetings all and thanks for any help offered.
I come from the world of pcs. I have several android devices, however have never tried to dive into the deeper workings of them. I am used to the pc world where if you want to install a new operating system you go buy or down load it then you install in. Brand of pc did not matter nor did the model. So I guess I am having a hard time understanding the concept of hardware specific roms. Can't I just get a stock kit kat rom and install it, and if not why not.
on another note does a stock kit kat rom even exist? All I find are things like cyanogen mod, or clockwork mod. I assume that these are essentially someone taking kitkat and adding stuff to it to customize it and then naming it.
I am looking to make a kindle fire hd look and feel like a nexus 7 with nothing but android 4.2.2 (or what even the number sequence is for the lates version of kitkat).
Thanks again for your replies
Hesperian9x said:
Greetings all and thanks for any help offered.
I come from the world of pcs. I have several android devices, however have never tried to dive into the deeper workings of them. I am used to the pc world where if you want to install a new operating system you go buy or down load it then you install in. Brand of pc did not matter nor did the model. So I guess I am having a hard time understanding the concept of hardware specific roms. Can't I just get a stock kit kat rom and install it, and if not why not.
on another note does a stock kit kat rom even exist? All I find are things like cyanogen mod, or clockwork mod. I assume that these are essentially someone taking kitkat and adding stuff to it to customize it and then naming it.
I am looking to make a kindle fire hd look and feel like a nexus 7 with nothing but android 4.2.2 (or what even the number sequence is for the lates version of kitkat).
Thanks again for your replies
Click to expand...
Click to collapse
Same question i also want to ask...... they say android is open source.....where can i find the original kitkat
...and can i flash it to my device or not.......why does every phone/tab model need specific rom version.....
I think ram and cpu are enough......what is the deference between all device....
Hesperian9x said:
Greetings all and thanks for any help offered.
I come from the world of pcs. I have several android devices, however have never tried to dive into the deeper workings of them. I am used to the pc world where if you want to install a new operating system you go buy or down load it then you install in. Brand of pc did not matter nor did the model. So I guess I am having a hard time understanding the concept of hardware specific roms. Can't I just get a stock kit kat rom and install it, and if not why not.
on another note does a stock kit kat rom even exist? All I find are things like cyanogen mod, or clockwork mod. I assume that these are essentially someone taking kitkat and adding stuff to it to customize it and then naming it.
I am looking to make a kindle fire hd look and feel like a nexus 7 with nothing but android 4.2.2 (or what even the number sequence is for the lates version of kitkat).
Thanks again for your replies
Click to expand...
Click to collapse
Getting a new OS (in this case we call these OS's: ROMs) on android is a little similar to PC installation it just has a few things we have to get past. so if you know what Linux is (another OS its almost like OSX for macs) that's what android is built upon the only problem is is that we don't have Admin access or in other words, super user, rooting your Android device gives you root/admin/SuperUser Access so there are lots more things you can customize about your device in this case a New operating system. Clockworkmod is almost like booting into your Bios on a computer, its pretty much a fail-safe if we break something or want to install (our way of installing is called "Flashing") a mod or a new OS.
Now there are a few different types of ROMs its all the personal preference on what you want most roms are AOSP which is pretty much Stock android (Nexus phones/tablet look) with a few mods here and there. Cyanogenmod is one of the type of roms as well (most popular), its is basically pure android with a little here and there stuff that you wouldn't need to worry about and i would recommend if you do flash a new ROM on any device i would start with Cyanogenmod first if its available, it has the most work put into it and is stable for the most part. (not that other ROMs developers don't put hard work into their own ROMs but still Cyanogenmod is getting bigger and bigger) be advised that flashing a new rom deletes all of your data, its just what we have to do to make the rom install properly, if you bought kindle books you can still get the books back by downloading the kindle fire app on the play store when you do get a new ROM. WARNING: DO NOT Flash roms that are for other devices, it will brick your tablet making it unrecoverable.
Seeing that the kindle fire hd is a very popular tablet and does have a few kitkat roms. (Android 4.2.2 is Jelly bean, Android 4.1 - 4.3 is jelly bean as well, Android 4.4 is kitkat) so pretty much it looks like the kindle fire hd has a locked bootloader which can be a problem but seeing that there is custom roms it must have been unlocked. a locked bootloader pretty much means we cannot flash a new OS but we are still able to root it. so pretty much see herehttp://forum.xda-developers.com/kindle-fire-hd (there are two kindle fire HD's 7" and a 8.9" which is yours?) ask in the Q&A where you can start, i imagine you would need to do this stuff in this order: Unlock bootloader, Root the tablet, install a custom recovery (like Clockworkmod or TWRP) Wipe Data/Factory reset, Wipe Cache (these two actions are done in your recovery) flash a new Rom.
If you have any other questions or i left something out please ask
---------- Post added at 03:21 PM ---------- Previous post was at 03:18 PM ----------
Killwish said:
Same question i also want to ask...... they say android is open source.....where can i find the original kitkat
...and can i flash it to my device or not.......why does every phone/tab model need specific rom version.....
I think ram and cpu are enough......what is the deference between all device....
Click to expand...
Click to collapse
Do you have a kindle fire HD as well? Android is sorta open source sure we can root it and install new OS's and other mods but Google allows OEMs can lock boot-loaders and cause awful lot of mess by not letting us developers do anything. You CANNOT flash a rom that is not for your device, it has to do with the other Devices Specs.
why does every phone/tab model need specific rom version.....
Click to expand...
Click to collapse
what do you mean here?
Trozzul said:
Getting a new OS (in this case we call these OS's: ROMs) on android is a little similar to PC installation it just has a few things we have to get past. so if you know what Linux is (another OS its almost like OSX for macs) that's what android is built upon the only problem is is that we don't have Admin access or in other words, super user, rooting your Android device gives you root/admin/SuperUser Access so there are lots more things you can customize about your device in this case a New operating system. Clockworkmod is almost like booting into your Bios on a computer, its pretty much a fail-safe if we break something or want to install (our way of installing is called "Flashing") a mod or a new OS.
Now there are a few different types of ROMs its all the personal preference on what you want most roms are AOSP which is pretty much Stock android (Nexus phones/tablet look) with a few mods here and there. Cyanogenmod is one of the type of roms as well (most popular), its is basically pure android with a little here and there stuff that you wouldn't need to worry about and i would recommend if you do flash a new ROM on any device i would start with Cyanogenmod first if its available, it has the most work put into it and is stable for the most part. (not that other ROMs developers don't put hard work into their own ROMs but still Cyanogenmod is getting bigger and bigger) be advised that flashing a new rom deletes all of your data, its just what we have to do to make the rom install properly, if you bought kindle books you can still get the books back by downloading the kindle fire app on the play store when you do get a new ROM. WARNING: DO NOT Flash roms that are for other devices, it will brick your tablet making it unrecoverable.
Seeing that the kindle fire hd is a very popular tablet and does have a few kitkat roms. (Android 4.2.2 is Jelly bean, Android 4.1 - 4.3 is jelly bean as well, Android 4.4 is kitkat) so pretty much it looks like the kindle fire hd has a locked bootloader which can be a problem but seeing that there is custom roms it must have been unlocked. a locked bootloader pretty much means we cannot flash a new OS but we are still able to root it. so pretty much see herehttp://forum.xda-developers.com/kindle-fire-hd (there are two kindle fire HD's 7" and a 8.9" which is yours?) ask in the Q&A where you can start, i imagine you would need to do this stuff in this order: Unlock bootloader, Root the tablet, install a custom recovery (like Clockworkmod or TWRP) Wipe Data/Factory reset, Wipe Cache (these two actions are done in your recovery) flash a new Rom.
If you have any other questions or i left something out please ask
---------- Post added at 03:21 PM ---------- Previous post was at 03:18 PM ----------
Do you have a kindle fire HD as well? Android is sorta open source sure we can root it and install new OS's and other mods but Google allows OEMs can lock boot-loaders and cause awful lot of mess by not letting us developers do anything. You CANNOT flash a rom that is not for your device, it has to do with the other Devices Specs.
what do you mean here?
Click to expand...
Click to collapse
Sorry dude....... But I just want to say that on PCs I just need windows or Linux or any os image...... And I can install it on any brand cpu ram motherboard........ It doesn't depend on brand..... Then why they made android or phone devices like this.... I m not saying that they would have make android free but.. It should be installable on all devices with better confg than minimum requirement.... Thats all.
Killwish said:
Sorry dude....... But I just want to say that on PCs I just need windows or Linux or any os image...... And I can install it on any brand cpu ram motherboard........ It doesn't depend on brand..... Then why they made android or phone devices like this.... I m not saying that they would have make android free but.. It should be installable on all devices with better confg than minimum requirement.... Thats all.
Click to expand...
Click to collapse
that a little harder to explain, from what i think its mostly because of the CPU drivers, these ROMs are non professional, anyone can make a rom but its a harder to make your own OS for a computer. i cant explain the most part of it for you but we just cant do it right now. you sure can port roms but it has to be from a similar device with almost every spec the same.
Trozzul said:
that a little harder to explain, from what i think its mostly because of the CPU drivers, these ROMs are non professional, anyone can make a rom but its a harder to make your own OS for a computer. i cant explain the most part of it for you but we just cant do it right now. you sure can port roms but it has to be from a similar device with almost every spec the same.
Click to expand...
Click to collapse
Thank you sir......
Trozzul said:
that a little harder to explain, from what i think its mostly because of the CPU drivers, these ROMs are non professional, anyone can make a rom but its a harder to make your own OS for a computer. i cant explain the most part of it for you but we just cant do it right now. you sure can port roms but it has to be from a similar device with almost every spec the same.
Click to expand...
Click to collapse
I understand that the roms are not professional. That is why I asked for the "stock" kitkat as google released it. shouldn't the "stock google release work on any android device?? if not why not?? this is nothing like pc world ans mentioned above.
I have installed linux on pcs. It runs the installer and does its thing and a few minutes later you have a shiny new system to run. Why is this so different in the mobil environment since as you already mentioned android is essentially linux. None of this device specific ROM stuff makes any sense to me.
Hesperian9x said:
I understand that the roms are not professional. That is why I asked for the "stock" kitkat as google released it. shouldn't the "stock google release work on any android device?? if not why not?? this is nothing like pc world ans mentioned above.
I have installed linux on pcs. It runs the installer and does its thing and a few minutes later you have a shiny new system to run. Why is this so different in the mobil environment since as you already mentioned android is essentially linux. None of this device specific ROM stuff makes any sense to me.
Click to expand...
Click to collapse
as for why Roms dont work on all devices and have to be made for specific only i cannot answer, i think it has to do with specs being so different, i think its the CPU that ruins it all because today there are so many different types of partitions for each kind of CPU given out, Rockchip, mediatek, samsung exynos, TI Omap, qualcomm there is quite a lot i cant list lol.
There sorta is a "Stock Google release" for some devices but that is only for Google play edition devices like a Samsung galaxy s4/HTC one M7/M8. if you bought a Non-Google play edition S4 or m7 you are able to install a official Google rom (different process not like flashing stuff in custom recovery's) please dont think that Just because Roms are non-professional does not mean that they are broken or dont work as good as stock material because Custom Roms most of the time get the bugs worked out and everyone is happy. i would recommend a custom rom over Stock kindle firmware, its very limited plus you dont have access to the google play store which has so much more stuff.
I want to install a custom Lollipop ROM on my phone, but even after days of sifting through years and various iterations of information and methods, I'm pretty confused.
I have a Razr Maxx HD. I believe the model is XT926M. I bought my phone in December 2012 from Verizon and it's running Android 4.1.2 OTA (stock) currently. The currently installed ROM is 9.18.94.XT926.Verizon.en.US. I'm not using a custom recovery. The bootloader is UNLOCKED and the phone is rooted! I used the Motopocalypse exploit method from around April of 2013. I've been extremely happy with the stability of 4.1.2, after the lockup/freeze/crash bug was fixed, which is why I haven't been quick to upgrade to anything else until now. I've also been afraid to mess with the phone out of fear of doing something wrong and creating more trouble for myself than it is worth (such as a soft brick from a failed OTA upgrade). I've seen enough posts about something going wrong or experiencing glitches in flashing methods which required workarounds that I want to ask before taking any action.
So, now I want to install a recent ROM free of Verizon's bloatware, in this case CM12. However, I can't seem to find any solid guide targeted at my scenario. Most of the information I find is either outdated (old methods, old software), or for the XT925 rather than the XT926(M), or the wrong country/carrier. Additionally, I know the newer ROMs are only available for KKBL, but I'm pretty sure that I'm still on JJBL if I'm on 4.1.2 OTA, and I can't find any recent or relevant guide for getting me out of where I am starting. If I was already on KKBL, I know all I would need to do is install a custom recovery and then install a custom ROM, but I'm at a disadvantage because I'm not even there yet and it's probably the part that's confusing me most.
I don't care about losing any data on my phone - I want to start completely fresh. The only thing I've done is create a nandroid backup (using the Online Nandroid app) for both CWM and TWRP recoveries. What next?
I don't know where to begin. Can someone help steer me in the right direction? I'd greatly appreciate it if you could be as specific as possible with versions and/or links to files I would need. Thanks!
Ok, I'm relatively new to Android and modern mobiles, but I've learned quite a bit already on my own, without much help from others.
The fact some communities provide little to no help is why I came to XDA, but I'm afraid I'm already disappointed about this particular issue.
Ok here it is: I'm not using a custom ROM, and I don't think I want to use one. I'm using the stock ROM, but I've rooted my device with Kingroot, which seems the only one that REALLY WORKS for any device. That's what makes me mad (I don't know if mad is the exact word, but.... I don't know how else to put it).
When I try to install SuperSU, it won't work because it can't update or install its own binaries. When I try the Super-SUME solution, it also doesn't work. In Super-SUME's case (which a friend thankfully helped me test most versions):
6.0 = successfully uninstalls Kingroot, but that's it;
6.2 = same as 6.0 and installs SuperSU, but that's it, nothing works, nor are the binaries updated/installed;
any other version above 6.2, including the latest one (9.2.3): hangs/freezes in "processing, please wait..." and does nothing.
And I don't know who programmed Super-SUME, but I think it's pretty bold on their part to charge for the app when it won't even work on people's devices, as noted above.
So, forgive my rant, but even though Kingroot is infamous (because it's Chinese perhaps ?), at least its devs are capable of successfully obtaining root on all devices, whereas SuperSU's and Super-SUME's devs make it impossible because of the binaries or just because their app hangs on "processing". If a team of devs can successfully root a device, why others cannot without making the user go through extra steps ?
As for these "extra steps", there's not one tutorial on the web (that I had come across at least) with a clear, step-by-step process to install SU's binaries, or to fix Super-SUME's hanging/freezing issues. So after rooting my device and getting rid of Kingroot, all I can work with is an unrooted device with most bloatware out of the way.
I just wish these other devs would go the extra mile and make their apps successfully obtain root without complications, just like Kingroot does. The complications just make their apps useless.
Thanks for hearing me, and maybe for helping me.
Model: SM-G530H / Kitkat 4.4.4
EzioGT said:
Ok, I'm relatively new to Android and modern mobiles, but I've learned quite a bit already on my own, without much help from others.
The fact some communities provide little to no help is why I came to XDA, but I'm afraid I'm already disappointed about this particular issue.
Ok here it is: I'm not using a custom ROM, and I don't think I want to use one. I'm using the stock ROM, but I've rooted my device with Kingroot, which seems the only one that REALLY WORKS for any device. That's what makes me mad (I don't know if mad is the exact word, but.... I don't know how else to put it).
When I try to install SuperSU, it won't work because it can't update or install its own binaries. When I try the Super-SUME solution, it also doesn't work. In Super-SUME's case (which a friend thankfully helped me test most versions):
6.0 = successfully uninstalls Kingroot, but that's it;
6.2 = same as 6.0 and installs SuperSU, but that's it, nothing works, nor are the binaries updated/installed;
any other version above 6.2, including the latest one (9.2.3): hangs/freezes in "processing, please wait..." and does nothing.
And I don't know who programmed Super-SUME, but I think it's pretty bold on their part to charge for the app when it won't even work on people's devices, as noted above.
So, forgive my rant, but even though Kingroot is infamous (because it's Chinese perhaps ?), at least its devs are capable of successfully obtaining root on all devices, whereas SuperSU's and Super-SUME's devs make it impossible because of the binaries or just because their app hangs on "processing". If a team of devs can successfully root a device, why others cannot without making the user go through extra steps ?
As for these "extra steps", there's not one tutorial on the web (that I had come across at least) with a clear, step-by-step process to install SU's binaries, or to fix Super-SUME's hanging/freezing issues. So after rooting my device and getting rid of Kingroot, all I can work with is an unrooted device with most bloatware out of the way.
I just wish these other devs would go the extra mile and make their apps successfully obtain root without complications, just like Kingroot does. The complications just make their apps useless.
Thanks for hearing me, and maybe for helping me.
Model: SM-G530H / Kitkat 4.4.4
Click to expand...
Click to collapse
Hi and thank you for using XDA Assist
Kingroot is not always the best choice cause it's not fully compatible with every device.
But i suggest you to head over here
And for futher questions go ahead here: Galaxy Grand Prime Q&A, Help & Troubleshooting
Good luck!
nilac said:
Hi and thank you for using XDA Assist
Kingroot is not always the best choice cause it's not fully compatible with every device.
But i suggest you to head over here
And for futher questions go ahead here: Galaxy Grand Prime Q&A, Help & Troubleshooting
Good luck!
Click to expand...
Click to collapse
Thanks. Unfortunately, I have already tried this root solution in the past. It's the only one where I managed to get SuperSU to work, but... the phone will always boot up in recovery mode. So I gave up on this solution as well.