Related
This thread was created to verify and promote the SuperOneClick rooting method that worked for me. I purchased a YP-G1 SGP 4.0 from Amazon recently and found enough hints on what to try for gaining ROOT.
All credit for this method goes to CLShortFuse and his SuperOneClick process.
There may be other steps to get this running, but below is what I did and it worked.
1. Enable USB Debugging.
2. Connect YP-G1 to PC, mount storage.
3. Locate Samsung Kies install on phone storage, install Samsung Kies.
4. Reboot after install.
5. Open Kies, run the update. (Kies never successfully connected to the YP-G1. I believe this was just to get drivers installed.)
6. Extract SuperOneClick to a folder on your PC's HD. (I chose a folder with no spaces in the name. Not sure if it matters.)
7. Unmount storage from the phone's notification bar.
8. Launch SuperOneClick.exe.
9. Click ROOT on SuperOneClick application on the PC.
10. Sit back and wait. It takes quite a while with mandatory 40s pauses.
This method may include steps that are not actually needed, but it is what I did and rooting the YP-G1 was successful. I will try to update the steps if I found a way to take out a few steps.
User etrnldrk reported that the update to Kies was not necessarily.
You don't need to update Kies to get this to work. The drivers installed just fine for me with the version included on my player.
ESET smart security says this file is loaded with trojan viruses. I wont touch it!!!!
thedjmike said:
ESET smart security says this file is loaded with trojan viruses. I wont touch it!!!!
Click to expand...
Click to collapse
Did you read the thread? It's normal that your antivirus will detect virus because many anti-virus detect exploit as virus but it's a false alarm.
Does it work with 2.3?
thanks dude worked like a charm on my 5inch yp -G70
-sandro- said:
Does it work with 2.3?
Click to expand...
Click to collapse
Sorry if I sound noobish but, what is 2.3? Is that the Android OS version?
azoller1 said:
thanks dude worked like a charm on my 5inch yp -G70
Click to expand...
Click to collapse
Good to hear this method was attempted on a 5" player. I really like this device and since I bought it for my Niece as a Christmas present, I might pick up the 5" for myself.
I've not had to process root again on the device, so I don't have much to update yet. Sounds like the Kies Update step was not needed, so thanks for reporting that.
chrisgriner said:
Sorry if I sound noobish but, what is 2.3? Is that the Android OS version?
Click to expand...
Click to collapse
Yeah, Pretty sure that's what they mean.
I also really like this device!
Best media player/mp3 player Ive ever had/used.
I have the 4.0, and a friend of mine has the 5.0,
and the 5.0's screen does not look nearly as good as the 4.0!
Also,
Ive only owned this for a couple/few weeks now,
and have not rooted it yet...
But am sorely tempted to do so..
However, I have no windows OS on any of my machines,
So what's the best route for someone on a Linux machine, with no access to windohs?
Really don't want to have to use an emulator to run a .exe file. lol
I used SuperOneClick on my UK 5.0 and it worked fine to obtain root.
I also said yes to installing busybox permanently, which was perhaps a mistake as it segfaults when I try to run it.
I believe this is because the /system partition didn't have sufficient space for the binary (it had ~650kb space remaining when mounted rw after the su binary was installed), so it has been truncated (and hence doesn't run well )
This leads to a problem when trying to install busybox from anywhere else too, and to solve this I had to grab a static busybox binary (from Debian iirc) place it in /data and create a symlink to /system/xbin/busybox (need to remount the partition rw temporarily). I didn't bother to create the symlinks, but probably should do.
*delete post*
Followed the directions & tried several times using XP and W7 machines. Both get stuck at "Running psneuter..." (See below). Anyone else have this problem?
I tried w/ Debugging on and off. Also tried mounted and unmounted. Failed.
I tried closing GO launcher (which I read on another thread), and running stock. Failed.
I tried 3 different versions of KIES (Kies_2.0.0.11034_5, Kies_2.0.0.11033_25 & Kies_2.1.1.11124_17_6). Failed.
Any ideas?
-------------
Getting OS version...
2.3.5
OK
2.3.5
Pushing psneuter...
375 KS/c (585731 bytes in 1.523s)
OK
chmod psneuter...
OK
Running psneuter...
-stuck here-
---------- Post added at 04:34 PM ---------- Previous post was at 03:53 PM ----------
--Nevermind--
I ran an updated version of superone click and it worked. I was using 1.9.5 previously. 2.3.3.0 worked!
Rasa11 said:
Yeah, Pretty sure that's what they mean.
I also really like this device!
Best media player/mp3 player Ive ever had/used.
I have the 4.0, and a friend of mine has the 5.0,
and the 5.0's screen does not look nearly as good as the 4.0!
Also,
Ive only owned this for a couple/few weeks now,
and have not rooted it yet...
But am sorely tempted to do so..
However, I have no windows OS on any of my machines,
So what's the best route for someone on a Linux machine, with no access to windohs?
Really don't want to have to use an emulator to run a .exe file. lol
Click to expand...
Click to collapse
I was in the same boat as you. I love Linux, and hate Windows. But, I needed to root my device. Try this. It worked for my 5.0, and believe it should work for the 4.0. It uses the same zergRush exploit as Super One Click does. It's built on the same stuff as doomlord's root, too.
transportguy said:
Followed the directions & tried several times using XP and W7 machines. Both get stuck at "Running psneuter..." (See below). Anyone else have this problem?
I tried w/ Debugging on and off. Also tried mounted and unmounted. Failed.
I tried closing GO launcher (which I read on another thread), and running stock. Failed.
I tried 3 different versions of KIES (Kies_2.0.0.11034_5, Kies_2.0.0.11033_25 & Kies_2.1.1.11124_17_6). Failed.
Any ideas?
-------------
Getting OS version...
2.3.5
OK
2.3.5
Pushing psneuter...
375 KS/c (585731 bytes in 1.523s)
OK
chmod psneuter...
OK
Running psneuter...
-stuck here-
Click to expand...
Click to collapse
Try doomlords easy rooting toolkit, I used that and it rooted my galaxy player 4.0 easily.
link : forum.xda-developers.com/showthread.php?t=1321582
hope I helped!
apapousek said:
I was in the same boat as you. I love Linux, and hate Windows. But, I needed to root my device. Try this. It worked for my 5.0, and believe it should work for the 4.0. It uses the same zergRush exploit as Super One Click does. It's built on the same stuff as doomlord's root, too.
Click to expand...
Click to collapse
Excellent! Thanks very much man.
I appreciate it. <3
Does anyone know if this works for Android 2.3.6 on the US Player 4.0? I've been looking everywhere and can't find anything for 2.3.6 (which apparently patches the zergRush exploit).
TheTehk17 said:
Does anyone know if this works for Android 2.3.6 on the US Player 4.0? I've been looking everywhere and can't find anything for 2.3.6 (which apparently patches the zergRush exploit).
Click to expand...
Click to collapse
Flash either a custom rom or a custom kernel and then it is supposed to work.
The OP should be updated to reflect that the root won't work on 2.3.6 until a custom rom/kernel is installed.
zaclimon said:
Flash either a custom rom or a custom kernel and then it is supposed to work.
Click to expand...
Click to collapse
Which custom rom or kernel? I've been trying to figure out how to get started rooting my US 4.0 player with 2.3.6 and it's proving incredibly confusing. Is there anywhere that lists a step by step process?? I know I need to unlock the bootloader - can't find any specific info on that for my particular player. I know I need to flash a ROM or Kernel, but can't find specific info on which one works for 2.3.6 for the YP-G1. I just can't seem to find any real useful info on how to proceed - could anyone throw me a bone?
klemmaniac said:
Which custom rom or kernel? I've been trying to figure out how to get started rooting my US 4.0 player with 2.3.6 and it's proving incredibly confusing. Is there anywhere that lists a step by step process?? I know I need to unlock the bootloader - can't find any specific info on that for my particular player. I know I need to flash a ROM or Kernel, but can't find specific info on which one works for 2.3.6 for the YP-G1. I just can't seem to find any real useful info on how to proceed - could anyone throw me a bone?
Click to expand...
Click to collapse
First, you don't have to unlock any bootloader period. As far as the custom kernel goes, the only one that works well is TerraSilent. Because mostly everybody already switched up to a custom rom, GB was pretty much left up. I would recommend that you update your device when you'll have flashed a custom kernel or rooted your device.
For the last two years I have been going back and forth between my Note 2 that was Stock Rooted on 4.1.2 and my un-Rooted Note 2 fully stock on 4.4.2. Each had their advantages
I had all but given up
Now thanks to GhettoRoot I have the best of both worlds.:highfive:
I would like to hear what is COOL about having Root on 4.4.2.
You newbies to 4.4.2 check out the Active apps widget . it only takes up one space on the home screen. It is a must have.
Because of GhettoRoot XDA will need to redo Most of the Verizon Note 2 Forum. AdamOutler's Root is obsolete, Thanks for the good times Adam
doctor-cool said:
For the last two years I have been going back and forth between my Note 2 that was Stock Rooted on 4.1.2 and my un-Rooted Note 2 fully stock on 4.4.2. Each had their advantages
I had all but given up
Now thanks to GhettoRoot I have the best of both worlds.:highfive:
I would like to hear what is COOL about having Root on 4.4.2.
You newbies to 4.4.2 check out the Active apps widget . it only takes up one space on the home screen. It is a must have.
Because of GhettoRoot XDA will need to redo Most of the Verizon Note 2 Forum. AdamOutler's Root is obsolete, Thanks for the good times Adam
Click to expand...
Click to collapse
AdamOutler's Root is obsolete, Thanks for the good times
Click to expand...
Click to collapse
Adam has done A LOT for this community especially for Samsung phone in general.. His work is NOT obsolete and he still very involved on this forum. I am not friends with him or do I know him but he was the master mind behind unlocking/exploiting Verizons bootloader.. which currently on 4.3 and 4.4.3 is still not possible. This is most likely do to him not having the phone and the phones age..
SOo I hope I got the wrong impression from your statement.. Bc that man you mentioned.. Is a LEGEND.. Hands down
Just to confirm, Ghettoroot does not work on 4.4.2 baseband ND7. Is that correct?
Sent from my Galaxy Note 2 using Tapatalk
11/9/14 Update. I successfully rooted with GhettoRoot with Note 2 running Android 4.4.2 and baseband ND7 (Verizon). Required SDK install and Note 2 Android drivers for Windows first.
jtsmall said:
11/9/14 Update. I successfully rooted with GhettoRoot with Note 2 running Android 4.4.2 and baseband ND7 (Verizon). Required SDK install and Note 2 Android drivers for Windows first.
Click to expand...
Click to collapse
I also had success using GhettoRoot from this post:
http://forum.xda-developers.com/showpost.php?p=55210343&postcount=27
ADB from this post:
http://forum.xda-developers.com/showthread.php?t=2588979
Koush's universal android drivers from here:
https://github.com/koush/UniversalAdbDriver
Yes, that's it. Samsung's drivers work for me.
Sent from my Galaxy Note 2 using Tapatalk
travisn000 said:
I also had success using GhettoRoot from this post:
http://forum.xda-developers.com/showpost.php?p=55210343&postcount=27
ADB from this post:
http://forum.xda-developers.com/showthread.php?t=2588979
Koush's universal android drivers from here:
https://github.com/koush/UniversalAdbDriver
Click to expand...
Click to collapse
crossing fingers
shissler said:
crossing fingers
Click to expand...
Click to collapse
woot woot im rooted..lol now what way to go
shissler said:
woot woot im rooted..lol now what way to go
Click to expand...
Click to collapse
I used it to replace the APN config file in my wife's phone for use on other carriers (T-Mobile & international use):
http://forum.xda-developers.com/showpost.php?p=57070787&postcount=7
It worked great for up to HSDPA+ speeds, but no LTE.. ..then she left the phone on top of her car; it fell off in traffic and got run over.. maybe this will help someone else!
Before it got smashed, I had planned on trying the following thread out next (for the VZW Note 3) to see if I could get LTE working on T-Mobile:
http://forum.xda-developers.com/showthread.php?t=2530523
travisn000 said:
I also had success using GhettoRoot from this post:
http://forum.xda-developers.com/showpost.php?p=55210343&postcount=27
ADB from this post:
http://forum.xda-developers.com/showthread.php?t=2588979
Koush's universal android drivers from here:
https://github.com/koush/UniversalAdbDriver
Click to expand...
Click to collapse
nothing works for me.
I have Verizon Note 2 with version 4.4.2 and ND7
it says "error: device not found" 6 times
samloves said:
nothing works for me.
I have Verizon Note 2 with version 4.4.2 and ND7
it says "error: device not found" 6 times
Click to expand...
Click to collapse
I followed travis's post and mine is rooted now with superuser access.
My only question now is what method do we use to install twrp or cwm on this nd7 rooted note 2 with 4.4.2?
Can we use odin and just flash the latest twrp or is there another workaround?
zbomb5610 said:
I followed travis's post and mine is rooted now with superuser access.
My only question now is what method do we use to install twrp or cwm on this nd7 rooted note 2 with 4.4.2?
Can we use odin and just flash the latest twrp or is there another workaround?
Click to expand...
Click to collapse
In order to install a custom recovery, you have to have an unlocked bootloader. At this moment, there is no do it yourself method to unlock the bootloader on factory stock 4.4.2, so you can't install CWM/PHILZ or TWRP. For about $75 I think... you can send your phone off to a company that uses special equipment to downgrade your phone to 4.1.2... then you would be able to unlock the bootloader.... Otherwise, the most you can do right now is root the device and make modifications that don't require unlocked bootloader (e.g. debloat, install Xposed modules, etc...). An XDA user named Beastmode is working on trying to get a modified version of TWRP called Safestrap working for 4.4.2 which wouldn't require an unlocked bootloader, so you may want to keep an eye on that thread here: http://forum.xda-developers.com/showthread.php?p=57190369
Thanks for the reply. I figured that was the case. I had 4.1.2 a few days ago also and figured "hey, i haven't updated in over a year" and didn't read into it enough and then upgraded to stock ota 4.4.2 so that sucks. I guess I can live with it like this for now till a fix comes out if one does.
also having trouble
I also have been having trouble rooting my note2 with 4.4.2. I followed travis' approach and I got the 6 device not found errors. Am I not installing the correct drivers? Any help or information is greatly appreciated.
UPDATE: Just got it to work. Will post soon what I was doing wrong and what I did to correct it.
I was able to get GhettoRoot to find my device once and the install failed. Now no matter what I do including removing and adding drivers it says it cannot see your Android device. Is there a trick i'm missing?
travisn000 said:
I also had success using GhettoRoot from this post:
http://forum.xda-developers.com/showpost.php?p=55210343&postcount=27
ADB from this post:
http://forum.xda-developers.com/showthread.php?t=2588979
Koush's universal android drivers from here:
https://github.com/koush/UniversalAdbDriver
Click to expand...
Click to collapse
---------- Post added at 08:43 PM ---------- Previous post was at 08:37 PM ----------
I had something similar happen to me. The very first time I ran GhettoRoot it found my device and tried to install but failed. Now, it won't find device no matter what I do.
IceCo1d said:
I also have been having trouble rooting my note2 with 4.4.2. I followed travis' approach and I got the 6 device not found errors. Am I not installing the correct drivers? Any help or information is greatly appreciated.
Click to expand...
Click to collapse
for me a message came up on my phone asking for permission and then i was able to root after installing the drivers.
I just had to accept on my phone first for it to actually work.
popdevil said:
I was able to get GhettoRoot to find my device once and the install failed. Now no matter what I do including removing and adding drivers it says it cannot see your Android device. Is there a trick i'm missing?
---------- Post added at 08:43 PM ---------- Previous post was at 08:37 PM ----------
I had something similar happen to me. The very first time I ran GhettoRoot it found my device and tried to install but failed. Now, it won't find device no matter what I do.
Click to expand...
Click to collapse
The part you are talking about does not come up until after the command prompt finds your device. Then you get the message to accept. That message came up the very first time but now it will not find the device for me to get to that part.
zbomb5610 said:
for me a message came up on my phone asking for permission and then i was able to root after installing the drivers.
I just had to accept on my phone first for it to actually work.
Click to expand...
Click to collapse
popdevil said:
I was able to get GhettoRoot to find my device once and the install failed. Now no matter what I do including removing and adding drivers it says it cannot see your Android device. Is there a trick i'm missing?
---------- Post added at 08:43 PM ---------- Previous post was at 08:37 PM ----------
I had something similar happen to me. The very first time I ran GhettoRoot it found my device and tried to install but failed. Now, it won't find device no matter what I do.
Click to expand...
Click to collapse
I had similar issues with some of my trials.. ...try turning developer mode off and on, plug in and then give the phone 30-90 seconds or so for installer mode to time out and verify the device is in MTP or PTP mode.
Just rooted my Note 2 running 4.4.2
Ok gang, so after about a week of trying every method to root my phone I finally got it to work. I'm going to tell you what I was doing wrong and what you can check to see where you are messing up. Hope this helps someone.
The issue I kept running into was that my device could not be found. I would run Ghettoroot and it would just tell me error device not found. This made no sense because I could get Kies to work and the bubble in the lower right corner that says installing device drivers would always succeed. However if I went into Device Manager (on the computer) there was a little yellow exclamation point next to my device. After looking in to the properties it said there were no drivers installed.
Also if you open a command prompt and type "adb devices" (with your phone plugged in) it should show you your device, if nothing comes up then the drivers are not properly installed.
So... First check that drivers are properly installed in your Device Manager (again this is on your computer), and then open a cmd window and type adb devices to see if your phone shows up. If it does then you are ready to use Ghettoroot.
I used this Ghettoroot:
http://forum.xda-developers.com/showpost.php?p=55210343&postcount=27
and the drivers I used were called:
SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.45.0 (I can't remember where I DLed it from, sorry)
Also, if you are interested. My method for figuring out what was wrong started by right clicking on the GhettoRoot .bat file to see the sequence cmd commands. They began with adb commands and I then googled to see how to check that the command would work. That is when I stumbled on the comman "adb devices" to make sure my phone was properly connected.
I hope this helps someone and if I can help in any other way just ask!
Heimdahl? Odin?
mattnmag said:
In order to install a custom recovery, you have to have an unlocked bootloader. At this moment, there is no do it yourself method to unlock the bootloader on factory stock 4.4.2, so you can't install CWM/PHILZ or TWRP. For about $75 I think... you can send your phone off to a company that uses special equipment to downgrade your phone to 4.1.2... then you would be able to unlock the bootloader.... Otherwise, the most you can do right now is root the device and make modifications that don't require unlocked bootloader (e.g. debloat, install Xposed modules, etc...). An XDA user named Beastmode is working on trying to get a modified version of TWRP called Safestrap working for 4.4.2 which wouldn't require an unlocked bootloader, so you may want to keep an eye on that thread here: http://forum.xda-developers.com/showthread.php?p=57190369
Click to expand...
Click to collapse
I've only had this phone a week. My vs980 fractured :crying: now I'm stuck with this "thing" which I've done nothing with as I'm still trying to figure out WHAT never mind how. There's so much bloat I'm thinking AOSP. But how?
So far, ghetto-root hasn't worked for me but have removed Kaspersky etc to see if that was the problem. Then worry abt boot loader. Am on Pageplus Carrier so there wont be any OTA updates
Is there any merrit in the "Heimdahl" (??) method shown here CYANOGENMOD
I've read some of people using Odin to load pre-rooted stock image (and have found the images... but... )
I bricked the vs980 playing too fast and not waiting for answers. (learned a thing or 2 unbricking it)
So am I correct in understanding that you can no longer "Drop" an Un****** version of the factory image into the phone? By any means?
THANKS
VW
Hi,
Try as I may. I cant unlock my Tablet Z LTE (SGP321) bootloader.
Im using FlashTool 0.9.18.4 and am currently on stock KK 4.4.4. firmware (SGP321_10.5.1.A.0.283_CE.ftf)
Everytime I try to ulock the bootloader it fails with FlashTool message that drivers need to installed
I've trird installing the drivers via the \FlashTool\Drivers directory.......but always get the following message "DPInst.exe doe not execute on your current operating system" - I'm running Windows 7 Ultimate 64bit
Any and all help would be greatly appreciated as I'm desperate to install CM KK 4.4.4 and get rid of the Sony stuff.
Thanks in advance
_____________________________
Sony Xperia Tablet Z LTE/WIFI SGP321
vybztymz said:
Hi,
Try as I may. I cant unlock my Tablet Z LTE (SGP321) bootloader.
Im using FlashTool 0.9.18.4 and am currently on stock KK 4.4.4. firmware (SGP321_10.5.1.A.0.283_CE.ftf)
Everytime I try to ulock the bootloader it fails with FlashTool message that drivers need to installed
I've trird installing the drivers via the \FlashTool\Drivers directory.......but always get the following message "DPInst.exe doe not execute on your current operating system" - I'm running Windows 7 Ultimate 64bit
Any and all help would be greatly appreciated as I'm desperate to install CM KK 4.4.4 and get rid of the Sony stuff.
Thanks in advance
_____________________________
Sony Xperia Tablet Z LTE/WIFI SGP321
Click to expand...
Click to collapse
don't use flashtool for unblocking BL (cause you can use instruction from Sony's site), or install drivers properly: look for dpinst.exe in your temp folder and set compability mode with WinVista in it's properties and it will install properly.
Rootk1t said:
don't use flashtool for unblocking BL (cause you can use instruction from Sony's site), or install drivers properly: look for dpinst.exe in your temp folder and set compability mode with WinVista in it's properties and it will install properly.
Click to expand...
Click to collapse
Thanks for your reply/suggestion. Unfortunately I do not have the "set compatibility" option in DPInst.exe properties. I have found 2 x dpinst.exe and 2 x dpinst64.exe files on my system.
I've tried using the Sony site instructions but
1. When i attch the tablet to my laptop in Fastboot mode (Vol up), and type "fastboot devices" at the cmd prompt, i dont get any indication that my tablet has been/is recognised (see scrrenshot 1)
2. When I run the unlock command using the unlock code obtained from Sony, command line sticks at "waiting for device" (screenshot 2)
i'm at a loss as to whats wrong \ what Im doing wrong
All / any suggestions welcomed as am desperate to install CM11/12.
Thanks in advance
Vybz
vybztymz said:
Thanks for your reply/suggestion. Unfortunately I do not have the "set compatibility" option in DPInst.exe properties. I have found 2 x dpinst.exe and 2 x dpinst64.exe files on my system.
I've tried using the Sony site instructions but
1. When i attch the tablet to my laptop in Fastboot mode (Vol up), and type "fastboot devices" at the cmd prompt, i dont get any indication that my tablet has been/is recognised (see scrrenshot 1)
2. When I run the unlock command using the unlock code obtained from Sony, command line sticks at "waiting for device" (screenshot 2)
i'm at a loss as to whats wrong \ what Im doing wrong
All / any suggestions welcomed as am desperate to install CM11/12.
Thanks in advance
Vybz
Click to expand...
Click to collapse
Check that your tablet's fastboot drivers are installed correctly in device manager on windows. I haven't done this on the tablet z (yet), but if you do not have the drivers installed on a nexus you wont see any device in the fastboot devices option.
So i would suggest you download the correct drivers (preferably from sony, but google drivers might also work), and check that the device manager dont have any unknown devices (tablet z) and if you do not try reinstalling the driver by uninstalling the current one and getting the correct one from sony or the google drivers.
marcusorwen said:
Check that your tablet's fastboot drivers are installed correctly in device manager on windows. I haven't done this on the tablet z (yet), but if you do not have the drivers installed on a nexus you wont see any device in the fastboot devices option.
So i would suggest you download the correct drivers (preferably from sony, but google drivers might also work), and check that the device manager dont have any unknown devices (tablet z) and if you do not try reinstalling the driver by uninstalling the current one and getting the correct one from sony or the google drivers.
Click to expand...
Click to collapse
Thanks - you were right, it was drivers. Finally managed (I think) to unlock bootloader.........but am now stuck in a bootloop .
Any suggestions welcomesed
Use flashtool and simply flash any stock version on top.
Alternatively, you can use some non stock ROM, but for that your first need to install the custom recovery via fastboot.
vybztymz said:
Any suggestions welcomesed
Click to expand...
Click to collapse
Have a look at this guide for installing a CM ROM
vybztymz said:
Thanks - you were right, it was drivers. Finally managed (I think) to unlock bootloader.........but am now stuck in a bootloop .
Any suggestions welcomesed
Click to expand...
Click to collapse
If your stuck in a bootloop i would suggest trying and flash recovery through flashtools and see if you can clear dalvik cache in the custom recovery.
it might help.
but otherwise do as the others say and flash a custom rom (CM preferably).
Lost Root after installing CN12 Nightly (Lollipop 5.0x)
marcusorwen said:
If your stuck in a bootloop i would suggest trying and flash recovery through flashtools and see if you can clear dalvik cache in the custom recovery.
it might help.
but otherwise do as the others say and flash a custom rom (CM preferably).
Click to expand...
Click to collapse
hanks for you help.
I have rooted and unlocked the boot loader of my SGP321 (WiFi/LTE).
But every time I install CM12 (flashed zip via TWRP), I lose Root......and as far as I can see, there's no way back from that, bar a complete re-install of stock (KK444)
Really frustrated as have wanted to flash CM and get rid of the Sonly bloatware (example: of 2gb internal memory, the stock firmware leaves only c.500mb free....thats just plain ridiculous. Compared to CM12 which leaves 1.7 GIGS free.
any suggestions.......?
vybztymz said:
hanks for you help.
I have rooted and unlocked the boot loader of my SGP321 (WiFi/LTE).
But every time I install CM12 (flashed zip via TWRP), I lose Root......and as far as I can see, there's no way back from that, bar a complete re-install of stock (KK444)
Really frustrated as have wanted to flash CM and get rid of the Sonly bloatware (example: of 2gb internal memory, the stock firmware leaves only c.500mb free....thats just plain ridiculous. Compared to CM12 which leaves 1.7 GIGS free.
any suggestions.......?
Click to expand...
Click to collapse
CM12 should have root built in, check developer options for it on your device.
If not then just flash SuperSU.zip from chainfire (i prefer chainfire's version of super user).
Chainfire's SuperSU is here: http://forum.xda-developers.com/showthread.php?t=1538053
please note that i have not tested this on a Tab Z but it should work.
marcusorwen said:
CM12 should have root built in, check developer options for it on your device.
If not then just flash SuperSU.zip from chainfire (i prefer chainfire's version of super user).
Chainfire's SuperSU is here: http://forum.xda-developers.com/showthread.php?t=1538053
please note that i have not tested this on a Tab Z but it should work.
Click to expand...
Click to collapse
Thanks for the speedy reply. Really appreciated. I've gone intp developer options.....but what am i looking for?
[EDIT] In Developer Options, and under "Root Access" it says "Disabled"
[EDIT 2] Downloaded a RootChecker and it tells me I'm not rooted
I'm totally frustrated.....have been trying to install CM12 for the last 6 hours!!!!
NUT (duallockedrecovery) has done a fantastic job developing the xzdr.........but i have to say that, in common with a lot of devs.... not very good at writing nstructions.
I'm an IT manager and often train staff in systems etc, including writing user guides. When writing guides/instructions, I ALWAYS assume that the end user KNOWS NOTHING......and so the guides/etc are very detailed. Yes, it takes a while to write them, but feedback shows its the right track to take.
Almost all the articles on flashing CM12/using Fastboot etc lack small, but important, details......!!! I'm still not really sure if i should be using TabZ-lockeddualrecovery or XZ-lockeddualrecovery..........!!!!!!
i've got as far as I have by pulling together numerous XDA posts in order to get a (full'ish) picture of what to do. Devs, pls make your instructions clearer for people who aren't devs. Rant over
My current position is that my Xperia Tablet Z is
1. On KitKat 444 (Firmware ver. 283)
2. Rooted
3. Bootloader unlocked
4. SuperSU & SuperSu Pro installed
How do i get from this position to a successful CM12 install?
I have CM12 Nightly (7th May), GApps 5.0x Minimal ready and waiting....
I'm not a stupid person, but trying to do this has made me feel like a complete idiot.....help!!!
vybztymz said:
Thanks for the speedy reply. Really appreciated. I've gone intp developer options.....but what am i looking for?
I'm totally frustrated.....have been trying to install CM12 for the last 6 hours!!!!
NUT (duallockedrecovery) has done a fantastic job developing the xzdr.........but i have to say that, in common with a lot of devs.... not very good at writing nstructions.
I'm an IT manager and often train staff in systems etc, including writing user guides. When writing guides/instructions, I ALWAYS assume that the end user KNOWS NOTHING......and so the guides/etc are very detailed. Yes, it takes a while to write them, but feedback shows its the right track to take.
Almost all the articles on flashing CM12/using Fastboot etc lack small, but important, details......!!! I'm still not really sure if i should be using TabZ-lockeddualrecovery or XZ-lockeddualrecovery..........!!!!!!
i've got as far as I have by pulling together numerous XDA posts in order to get a (full'ish) picture of what to do. Devs, pls make your instructions clearer for people who aren't devs. Rant over
My current position is that my Xperia Tablet Z is
1. On KitKat 444 (Firmware ver. 283)
2. Rooted
3. Bootloader unlocked
4. SuperSU & SuperSu Pro installed
How do i get from this position to a successful CM12 install?
I have CM12 Nightly (7th May), GApps 5.0x Minimal ready and waiting....
I'm not a stupid person, but trying to do this has made me feel like a complete idiot.....help!!!
Click to expand...
Click to collapse
Yea i know what you mean by guides not being written to include alot of details and missing out on small stuff that might be important, but anyway.
In the Developer Options there should be a box called Root Access, and it should be defaulted to Disabled ones you have installed CM12 for the first time, its just a matter of enabling this.
Im guessing you already know how to enable Developer Options, but if you dont here is how:
Go to About Device (or Phone/Tablet) and click on Build number a bunch of times (i think its 5-6 times), and the developer options should be visible in the settings.
If that dosent work you might want to try and flash the SuperSU binary through recovery, the zip to use is the one found in chainfires xda-thread here: http://forum.xda-developers.com/showthread.php?t=1538053
But here is the direct link for the zip https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Just put that on your device internal memory (or SD-Card) and flash it in your recovery of choice, it should work in CWM, TWRP and Odin (but you dont have a samsung so the last one dosent matter).
This should install the SuperSU app, and its basic su binary onto your CM12 rom.
In both cases i would recommend you install root checker (https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck) and see if root is available to you.
Also to note is that the Root Access option built into CM12 isnt that customizable and i would still recomend you install SuperSU, but if the Root Access option is working you can just download the SuperSU application from the play store and let it install SU binary and then you can disable CM12's built in root option ones you make sure the SuperSU was installed correctly.
Thanks so much for your help/patience......but i'm afraid im giving up (for now).
Will try again in a few days......so its back to rooted stock 444
By the way, why have CM decided to go with their own (as good as useless) recovery????
I forgot to say that you've helped fill in a few more gaps for me in respect of this i.e. flashing SU; changing Root Access in Dev. Options etc.
These are the things that all the articles ive read FAILED to mention.
Thanks so much
vybztymz said:
I forgot to say that you've helped fill in a few more gaps for me in respect of this i.e. flashing SU; changing Root Access in Dev. Options etc.
These are the things that all the articles ive read FAILED to mention.
Thanks so much
Click to expand...
Click to collapse
No problem, if you have any other questions just tell me and i might be able to help you
I have also been in the dark about this stuff before, and im still not used to other manufacturers style of rooting and unlocking the bootloader (sony is the next best after Nexus) since samsung and the others usually you have a harder time unlocking and rooting.
But good luck if you try it again :victory:
Just updated from 4.3 to 5.1 so I can get CarbonROM, and can't seem to find how to root it now. Kingo worked fine when it was on 4.3 if I'm not mistaken (I've rooted 6 devices since then, so I may be misremembering, haha). Now, it's no longer supported. KingRoot and Towelroot have also failed. I've been googling and trying to find the answer, but all I'm getting are the above methods, for 4.3. If I've completely overlooked something and am asking a dumb question here, then please forgive me. I'd appreciate at least a web link in the right direction if that's the case, or if this is a valid question then I'd love if I could get a bit of a walkthrough with this. Currently, I'm running the stock ROM, unlocked bootloader, stock recovery... which was needed because I had to update
zombunny said:
Just updated from 4.3 to 5.1 so I can get CarbonROM, and can't seem to find how to root it now. Kingo worked fine when it was on 4.3 if I'm not mistaken (I've rooted 6 devices since then, so I may be misremembering, haha). Now, it's no longer supported. KingRoot and Towelroot have also failed. I've been googling and trying to find the answer, but all I'm getting are the above methods, for 4.3. If I've completely overlooked something and am asking a dumb question here, then please forgive me. I'd appreciate at least a web link in the right direction if that's the case, or if this is a valid question then I'd love if I could get a bit of a walkthrough with this. Currently, I'm running the stock ROM, unlocked bootloader, stock recovery... which was needed because I had to update
Click to expand...
Click to collapse
Carbon is already rooted. Enablee in developer options in settings. Just flash twrp and install carbon.
Moody66 said:
Carbon is already rooted. Enablee in developer options in settings. Just flash twrp and install carbon.
Click to expand...
Click to collapse
ah, nice!! thanks dude, I'm new to the custom ROM scene and didn't know that was even a possibility. I really appreciate the help!
And to benefit others who searched and reached this thread, beside build in root in CM, for all ROM, you can always install SuperSu.zip in twrp to gain root. The detail is in the INDEX page root section.
http://forum.xda-developers.com/showthread.php?p=61682514
xordos said:
And to benefit others who searched and reached this thread, beside build in root in CM, for all ROM, you can always install SuperSu.zip in twrp to gain root. The detail is in the INDEX page root section.
http://forum.xda-developers.com/showthread.php?p=61682514
Click to expand...
Click to collapse
Good idea.
Rooting 5.1 ham2
Download the mt2 l03 twrp image to your pc's adb folder on your hard drive
open command prompt from inside the adb folder. I believe its 'shift' and 'right click' mouse
then connect your device and run the fastboot twrp commands
twrp will root your ham 2
this all presumes that you've unlocked your bootloader
This post by @ArkAngel06 should be able to help it has Pretty much everything you need to install TWRP. It can be found at http://forum.xda-developers.com/showpost.php?p=61802299&postcount=2 . Just look for the link titled TWRP for Mate2. I would suggest downloading the newest version of TWRP that's compatible with the Carbon, Cyanogen and PAC if you wanted to install them later on, Just rename the file twrp like the one in the folder and replace the one in the folder with the one that you downloaded. The new TWRP can be found at http://android.cmphys.com/twrp-mt2/ . Then just follow the instructions in the folder to install TWRP and SuperSU .
Hi. I'm new here & registered in the hopes of finding a working solution since I've been trying for days.
I'm trying to root my Kindle Fire HDX 7" that's running OS 4.5.5. I've read a lot about needing to downgrade or rollback to version 3.2.8 first to be able to root. I downloaded the Thor bin file on my Kindle, but am not sure what to do with it or where to go from here. So I haven't gotten very far in the process & am stuck. Any help would be greatly appreciated!! And when responding, please bear in mind that I know very little about doing this sort of thing.
Thank you!!!!
gr8fuldee said:
Hi. I'm new here & registered in the hopes of finding a working solution since I've been trying for days.
I'm trying to root my Kindle Fire HDX 7" that's running OS 4.5.5. I've read a lot about needing to downgrade or rollback to version 3.2.8 first to be able to root. I downloaded the Thor bin file on my Kindle, but am not sure what to do with it or where to go from here. So I haven't gotten very far in the process & am stuck. Any help would be greatly appreciated!! And when responding, please bear in mind that I know very little about doing this sort of thing.
Thank you!!!!
Click to expand...
Click to collapse
My suggestion is you keep reading through the HDX forums to increase your knowledge of techniques, procedures and potential pittfalls that can permanently cripple your device (bricking). This is exceptionally easy to do. I understand you are new and seeking guidance but everything you need to know is here. The lack of responses reflects the reluctance of experienced contributors to pen yet another custom response. Post specific questions as they arise. You'll typically get a prompt response provided you have done your homework.
Thank you for your reply. I feel like I have spent a huge amount of time trying to root my kindle by researching and dowloading this or that. So, here's where I'm currently at. I have been following the directions on gizmag. I backed everything up & am using a computer running Windows 8. I enabled the ADB & downloaded the ADB files (from this site, I believe). When I ran the .exe file, the installation wizard gave me this error: "The device driver installation wizard did not update any of your software for your hardware devices because it was not better than the software you currently have installed".
That's as far as I've gotten. I hope the additional information will help users to assist me.
Thank you!
gr8fuldee said:
Thank you for your reply. I feel like I have spent a huge amount of time trying to root my kindle by researching and dowloading this or that. So, here's where I'm currently at. I have been following the directions on gizmag. I backed everything up & am using a computer running Windows 8. I enabled the ADB & downloaded the ADB files (from this site, I believe). When I ran the .exe file, the installation wizard gave me this error: "The device driver installation wizard did not update any of your software for your hardware devices because it was not better than the software you currently have installed".
That's as far as I've gotten. I hope the additional information will help users to assist me.
Thank you!
Click to expand...
Click to collapse
Regarding adb you can obtain the highly regarded 'Minimal ADB and Fastboot here:
forum.xda-developers.com/showthread.php?t=2317790
Install and make sure you can access your device via adb before proceeding. Use Google to learn basic adb commands as needed.
Take the gizmag article with a grain of salt. While there is good content much of the material is dated and likely not applicable to your device. HDX forums on XDA are your best resource for the most current info.
I managed to get the first 2 steps done from a thread I found on here, which were to downgrade to 3.2.8, then upgrade to 4.5.2. The next step says to "use Kingroot or another method". Does Kingroot work for the kindle hdx 7, do you know? I've tried downloading it & keep getting an error that says "Failed - Network error". What are the other methods available? Thanks again!
gr8fuldee said:
I managed to get the first 2 steps done from a thread I found on here, which were to downgrade to 3.2.8, then upgrade to 4.5.2. The next step says to "use Kingroot or another method". Does Kingroot work for the kindle hdx 7, do you know? I've tried downloading it & keep getting an error that says "Failed - Network error". What are the other methods available? Thanks again!
Click to expand...
Click to collapse
Kingroot works with all HDX models running FireOS v4.5.2. You can grab it from here. A brief network connection is required during the rooting process. Be prepared to flip WiFi on; run Kingroot and then immediately disable WiFi. Leave it on too long an you will likely receive an OTA update that will plug the vulnerability that permits rooting. If that happens you'll have to redo the rollback/upgrade procedure.