So I used https://forum.xda-developers.com/showpost.php?p=71457975&postcount=3 this person's guide and tried to root my device but kingroot couldn't root it, everything seemed fine till I noticed that I certain apps stop being available to me. So then I tried to use the recovery method listed and now wifi won't turn on which I need for samsung backup. I've follow all the steps of both the guide and the recovery method and I'm still at a lost.
Related
Dear Al,,
I’m providing you to root your CPN3 device without PC.
This the very easiest way to do it & its work 110%.
Keep Internet data on or connect to working WIFI & pls follow below steps.
1:- Download KingRoot v3.3.1
Follow the basic steps as usually show in the app.
Click on ROOT & the app will do its work & it will show ERROR after 3-5 steps will show.
Don’t worry, Ur device is already open for root binaries to access, KingRoot has done his job.
You can check on CPUz >Device>Root Access is Yes.
2:- Download Kinguser v3.4.8
Open the app go to setting & see Root Permission is “ON”.
3:- Download X-Plore from play store.
Go to Configuration> Root access> select (Superuser + mount writable).
Then click on ROOT, Kinguser will ask permission click on (Authorize).
You are all done.
Google it for KingRoot v3.3.1 / Kinguser v3.4.8 / X-plore apps.
Pls note:- only use KingRoot v3.3.1 only & it will work 110%, Latest version will not do I have personally try this.
If ERROR still show after 3-5 steps shown in KingRoot app pls do it again with working internet & follow 2nd steps after error.
Thank you
Regards LUKE.
Your mobile still working properly after root
Dose it work in the marshmallow beta version of coolpad note3. I tried to root with Kingroot many times but it doesn't work.
Siddhartha Roy said:
Dose it work in the marshmallow beta version of coolpad note3. I tried to root with Kingroot many times but it doesn't work.
Click to expand...
Click to collapse
does not work for marshmallow....but if you have rooted in lollipop and twrp or any custom rom installed it will be still rooted in marshmallow. I am using the same and it works great.
Hi,
I rooted my phone, but I think somewhere I did wrong. My phone status is showing rooted in Root checker but now my device is switching OFF and ON again and again. Need help. What shall I do now? Shall I unroot again or if you could provide me method of how to root again, because it isn't gonna happen with device now. As soon as I open any app, it switches OFF and then ON again..
If possible, could you please help me through mail.
Email : [email protected]
Not working
Not working for marshmallow 8.0 uI
Hello I don't know if I can ask here but I can't root my device. I have tried almost everything, from the apk's and even on my laptop. I have a Lenovo A816 running on 4.4.4. I just got this phone, I'm actually an Apple user but my iPhone is being repaired right now. It's safe to say I don't know anything about Androids. I've looked all over google for guides on this phone but nothing comes up. I really want to uninstall some of these system apps. I've tried King root, Vroot' iRoot' framaroot, oneclickroot. I've literally tried every one of them to no avail. When I switched to my laptop, I used Kingo Root and it said root was successful but when I tried root checker it said my root is not installed properly, so no root again. Is there anything I can do to root it. This phone is Chinese. I'm in the UK.
Thanks
Hello I don't know if I can ask here but I can't root my device. I have tried almost everything, from the apk's and even on my laptop. I have a Lenovo A816 running on 4.4.4. I just got this phone, I'm actually an Apple user but my iPhone is being repaired right now. It's safe to say I don't know anything about Androids. I've looked all over google for guides on this phone but nothing comes up. I really want to uninstall some of these system apps. I've tried King root, Vroot' iRoot' framaroot, oneclickroot. I've literally tried every one of them to no avail. When I switched to my laptop, I used Kingo Root and it said root was successful but when I tried root checker it said my root is not installed properly, so no root again. Is there anything I can do to root it. This phone is Chinese. I'm in the UK.
Thanks
Well today I was doing my root via Odin and used the auto root kernal that was provided for my phone, so I followed every step and it didn't work at all, besides the root not working I now got this problem on my wifi which you can solve via build.prop, the thing is that you need root to access this files as far as i'm concerned, there is no root for my phone else than the one I already tried, meaning I cannot fix my problem, I need help please!
So I've been rooting me phone for a while and have managed to never f*** up, till now, and I sincerely hope you guys can help me.
After rooting my S7 a while back, I just recently noticed SuperUser telling me that I didn't have root anymore, so I decided to follow these instructions to re-root my phone:
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
I successfully followed all the steps to get root, but when I opened Flashfire it told me I could install a new update while maintaining root, so since my android is at 6.0.1, I did that and it bricked my phone.
On boot it says "Startup Failed - Use the Verizon Software Repair Assistant . . . " and on top it also says "Custom binary blocked by SECURE BOOT." I have tried going into recovery mode and deleting the system cache, but that doesn't do it. So is there any way to get the phone to properly boot while not deleting my data? I was rooting my phone precisely so I could use Titanium Backup again, so I don't have any backups stored anywhere. I have heard that flashing a recovery image with Odin can work, but would that delete my files? Someone please lend me your expertise.
My phone is a Verizon S7.
Fixed
I am surprised that no one responded to me, but what's important is that, miraculously, I managed to un-brick the phone myself without losing any data! What I did was, as my last hope (since Odin wasn't able to flash the stock image, a la the traditional soft-brick fix), decide to follow the on-screen instructions my phone was giving me and to download and run something called the "Verizon Software Repair Assistant," which can be found in the top google results after searching for the quoted name (xda doesn't let me post the link).
After putting my phone into download mode, I plugged it in, ran the software and let it work overnight. Checking on it in the morning, I found my phone, not only completely functional and working, but updated to Android 7.0 (it was 6.0.1 previously before the failed Flashfire OTA update) and still holding all of my data intact.
So, the interesting thing that I learned is that flashing to stock via Odin to fix a soft-bricked phone should not be the default resolution for potentially most people, as the carrier's default (in my case, Verizon's) repair utility managed to completely fix my phone without any side effects or data loss.
Is there anyone who could chime in on why the Repair Utility did not wipe my phone's memory, even though it warned it would?
**Note**
Verizon links to the Windows version of the repair assistant on their site, but to get the Mac version (which I used), the only way you can get it is by changing the end of the url they mention within the thread from "Win" to "Mac."
Pleased you managed to fix it, and thanks for posting the method for others
As for replies, if you stick around XDA you'll see replies can take days sometimes, patience is the key here
*Detection* said:
Pleased you managed to fix it, and thanks for posting the method for others
As for replies, if you stick around XDA you'll see replies can take days sometimes, patience is the key here
Click to expand...
Click to collapse
I guess I am not acquainted with this forum enough then, thanks!
Most likely the cause of the fault would be updating via FlashFire and keeping root. When the update was flashed, it most likely flashed the stock kernel and patched it for root, which is not a compatible root for our devices. Flashing the root kernel with Odin probably would have made the phone boot normally.