Hi guys, since I am sick of the partition in my MI2 (only 4GB for apps), I want to root my phone and use flashify to flash an image to merge the two partitions.
However, I am having a lot of trouble rooting my device, I tried flashing to the latest developer ROM (which I realise don't come with root permissions), different root apps (e.g framaroot, iroot....etc), I also tried use the recovery mode install .zip files which claimed to root my device, these methods all failed miserably. To make matters worse, a lot of methods taught on the net don't work for me because it involves the use of CMD (only available in windows) or other programs which only support windows.
Is there anyway I can root my MI2?
P.s I didn't install any custom recovery, I just got stock recovery mode
MIUI7.. Model no 2014818
I am also facing similar problem and not able to root the phone.
I tried other methods from earlier post but only the MI logo appears and than nothing happens.
http://forum.xda-developers.com/mi-2/development/how-to-root-mi2s-lolipop-5-0-t2950223
Regards,
dn
QuickGrocerySolution
Related
I have a Advent Tegra Note 7
Upgraded to kitkat and OTA 2.4.1
Used Tomsgt supertool 2.4.1 tool to root, installed TWRP (and made a backup image of my freshly installed system)
I've since added some games and apps and spent a fair bit of time customizing the system, but when I attempt to run Titanium Backup it tells freezes when "asking for root rights" so I ran "root checker basic" from playstore, which tells me I don't appear to have proper root access..
Here's a break down of what I've done, I've tried to keep it conscise...
I have tried installing a SuperSU, SuperUser and SU Update fixer, Also reinstalling the SuperSU-v1.94.zip using both cwm and twrp... Still no proper root access.
Ideally I'd like to try some other things to get root access before reflashing and having to reinstall my apps and settings, can anyone help or suggest anything else I could do.? I can't think of anything I could of accidentally done to break root access, this is still quite a clean system just setup in the past two days.
P.S.When using the supertool impacter tool and scan for usb driver I get a "no such device" error, even though the device is listed in the previous screens.. also I suspect the correct drivers are there as ADB seems to work fine
they flashing SuperSU-v1.99r4.zip from http://download.chainfire.eu/447/SuperSU/. I haven't had issues with root via either method.
If that fails you can use the n7root.img which is downloadable here: https://github.com/linux-shield/shield-root/blob/master/root_tn7.img?raw=true then go into fastboot mode and then type fastboot boot root_tn7.img. DO NOT USE FASTBOOT FLASH BOOT with this image as it will make it bootloop, just use fastboot boot command.
SOLVED
Thanks for the pointers hacktrix2006.. I tried supersu-v1.99r4.zip also v2 no luck. Had a quick look for how to get into fastboot mode.. couldn't access it from the bootloader.. so decided to take a backup image and restore to stock kitkat 4.4.2 via tomsgt latest tool 2.4.1 including doing Wipe data. then reinstalled TWRP then applied root.... AND noticed a screen saying something like ROOT ACCESS MAY BE FAULTY.. WOULD YOU LIKE TO FIX THIS.. I also think there was a warning about "be careful this action is irreversable" - I suspect the previous time I hadn't understood this properly and selected NO !! Anyway this time I said yes and now have ROOT YAY!
Now I start a re setup of the system and installation of apps etc.. I guess it's often a bit smoother 2nd (or 3rd 4th etc) time around
OK thx again for the encouragement, plus now I have a little more experience to offer someone else who may be struggling in this area.
no problem!
Hello everyone,
I am posting today to bring up the subject of the SM-G360P variant of the Samsung Galaxy Core Prime.
I am having issues with getting TWRP custom recovery to work properly on my device. I am able to flash twrp-3.0.2-0-coreprimelte.img onto my device and it works except for 2 things that i have noticed that makes me very upset and i cant figure out what to do. When i enter recovery mode the back light does not function so i have to use a bright flashlight to see any of the options and the second problem is the GUI is upside down but the button mapping is in the proper place so i have to guess on where to tap on my screen. This makes it very frustrating to use especially when i want to wipe dalvik cache and the regular cache. I accidentally factory reset my device once by tapping the wrong spot. If anyone would be willing to help me out with my problem i am willing to be a guinea pig with anything you can try for the custom recovery to make the GUI reflect the proper button mapping and the back light to work. I can re-flash my device as many times as necessary to get a working custom recovery. I have included the recovery.fstab and the stock recovery along with the version of TWRP custom recovery i have been utilizing to an extent.
I am using the BST Australian variant of SM-G360P which can be rooted with Kingo Root and KingRoot. I used Kingo Root so i could use the SuperUser app rather than just using KingRoot. I have used CROM Service to unlock my bootloader. I have also tried to use CWM custom recovery on my device but it does not register the CWM custom recovery that is available for my device it just goes to a "fake" Odin mode screen. I would really love to get TWRP custom recovery working properly. I have tried to port both TWRP and CWM custom recoveries by using Android Image Kitchen but have not had any success at creating a recovery that works without the same issues i have with TWRP custom recovery. I am running 4.4.4 KitKat OS which is the latest update for SM-G360P and have full root permissions. If you need any other dump files or any other information i will gladly give it to you. I may need directions on how to do some things though.
I will be greatly appreciative if someone would have a look at what the problem may be with TWRP custom recovery and my Variant of SM-G360P. Please help. Thank you for your time and contribution.
Hello @sosthenisRR. I just got this device, the Boost Prevail LTE American version. I was wondering if you've made any headway finding a TWRP for it. I will be trying some things myself... Gotta have TWRP... And I wanted to let you know that if you root with kingroot, super-sume (free version) works to get you supersu.
Odin TWRP 2.8.7.0 for the SM-S820L...it works, i tried V3 as well with no favorable results.
https://forum.xda-developers.com/galaxy-core-prime/development/twrp-2-8-7-0-sm-g360p-t3462592
eeriikk said:
Odin TWRP 2.8.7.0 for the SM-S820L...it works, i tried V3 as well with no favorable results.
https://forum.xda-developers.com/galaxy-core-prime/development/twrp-2-8-7-0-sm-g360p-t3462592
Click to expand...
Click to collapse
If that doesn't work, install and run this apk, this is what finally allowed me to Odin TWRP to my G360P without errors. Now if only we could get a custom ROM for this variant...
Hi, first post here so please be kind - I really need your help.
SITUATION:
I unlocked the bootloader using the tool provided under the utilities section of ASUS support page. Then, I successfully rooted my phone using one of many exploits contained in KingoRoot. Root Checker app said that root was ok, and I rebooted my phone. Something in the process caused my phone to soft brick, probably KingoRoot messed up the partition table. My phone is now stuck at Asus logo when trying to turn it on.
I can access recovery and fastboot. I also flashed TWRP recovery 2.8.5.0 (no success flashing newer versions) that is capable to put my phone in ADB sideload. I wiped cache, dalvik, data multiple times. Factory reset. Tried to update system using almost every firmware zip that ASUS support page lists (WW) through recovery and through ADB sideload unsuccessfully. Stock recovery is unable to access my SD card (since after the fatal reboot - unable to mount E: ecc, I tried three different cards), while the custom one is able to but gives me error when trying to run zip files. There are a plenty of details that I could give, but my conclusion after 24 hours of forum headaches is that the partition table is messed up.
I came across an utility called Asus Flash Tool that may fix my problem, but it only accepts .raw firmware files and I am unable to find one for my A500KL. There's a folder for it in an old rapidgator link but it's empty now, no luck contacting the original uploader (many others have the same problem). I read through every related thread here on XDA and on many other forums (even in Chinese and Russian), this is my last resort. There's anyone willing to share such .raw image? I read that it can be built out of a functional phone, can someone help me?
Hello, i was wondering do we have any TWRP recoveries for the ZTE Blade V7 (not the lite one by the way) if not how hard would it be to homebrew root access and kernel permission alterations so we can run custom kernels? i'm willing to help out in development if needed, i know we have Fastboot drivers and kingoroot, but iv'e found that doesn't work all too well anymore. I've also tried using ADB and Fastboot, but it boots to meta mode, which is fine because volume up and power button would take you to recovery mode, but my recovery doesn't show up in ether the SD card or ADB, even though its in the root of the SD card directory. this inst really a development project but i'm will to make it into one if needed. though if it does turn into that ill ask for some advice on where to start as i have never done this before , thanks in advance.
matt mods said:
Hello, i was wondering do we have any TWRP recoveries for the ZTE Blade V7 (not the lite one by the way) if not how hard would it be to homebrew root access and kernel permission alterations so we can run custom kernels? i'm willing to help out in development if needed, i know we have Fastboot drivers and kingoroot, but iv'e found that doesn't work all too well anymore. I've also tried using ADB and Fastboot, but it boots to meta mode, which is fine because volume up and power button would take you to recovery mode, but my recovery doesn't show up in ether the SD card or ADB, even though its in the root of the SD card directory. this inst really a development project but i'm will to make it into one if needed. though if it does turn into that ill ask for some advice on where to start as i have never done this before , thanks in advance.
Click to expand...
Click to collapse
For now ZTE Blade V7 has one custom recovery with TWRP 3.0.2.
Flashes with SPFlashTool and custom Scatter file
Starting from a non-rooted SM-G950W with a locked version 7 bootloader, what does it take to make a disk image backup (like with `dd` or `adb pull`) of the /data/media, without first destroying the data that's there? Is it even possible?
I ask because I did something dumb that truncated (not deleted) all files in shared storage to 0 bytes. If I could take a disk image of /data/media, I'd be able to use offline recovery programs (like PhotoRec) to restore what was on there, but I'm currently blocked from doing that since my phone isn't rooted.
I could root my phone, but it looks like most options for rooting involve wiping out /data/.
After having done some research, it appears that I may have the following options:
Install a custom recovery like TWRP, which will grant me root access in Recovery Mode that I can use to make a disk image. The problem is that my bootloader (version 7) is locked, meaning I'd need to use Safestrap, but that apparently requires root. Is it possible to install an additional custom recovery with a locked bootloader (as opposed to replacing the built-in one) without rooting first, or am I out of luck?
Install an additional custom ROM that has root, leaving the phone's original ROM intact as opposed to replacing it, if that even makes sense.
I think I've gone in circles about what the requirements are for installing a custom recovery or ROM. This post in a G950 rooting thread says it's possible to install a custom recovery image that has root access (at least on the S8+):
https://forum.xda-developers.com/showpost.php?p=81922221&postcount=9
The linked instructions are for installing a custom ROM with Safestrap:
https://forum.xda-developers.com/verizon-galaxy-s8+/development/rom-t3771206
But the link for G950W leads back to the G950 rooting thread, which requires wiping /data/:
https://forum.xda-developers.com/galaxy-s8/development/root-t4060701
Also, the Safestrap install guide says that root is a requirement:
https://forum.xda-developers.com/galaxy-s8/development/recovery-locked-nougat-7-0-safestrap-t3772760
Is there a solution here, or are all options locked out?
Thanks in advance!