Hi guys. Im not going to lie, im a noob when it comes to rooting, so I turned here to ask for help. Now, let me explain my whole issue. Lets start with, i cant unlock my bootloader. I also cant get into flash mode on flashtool which would allow me to downgrade, and and then root my phone from there. So yeah, I cant do anything honestly. I would love it if someone would be kind enough to help me with a step by step instruction guide, or even live assistance?. I already google'd for about 2-3 hours now, and can't find anything. Any help would be greatly appreciated!
white5pirit said:
Hi guys. Im not going to lie, im a noob when it comes to rooting, so I turned here to ask for help. Now, let me explain my whole issue. Lets start with, i cant unlock my bootloader. I also cant get into flash mode on flashtool which would allow me to downgrade, and and then root my phone from there. So yeah, I cant do anything honestly. I would love it if someone would be kind enough to help me with a step by step instruction guide, or even live assistance?. I already google'd for about 2-3 hours now, and can't find anything. Any help would be greatly appreciated!
Click to expand...
Click to collapse
Mention 'EveryThing' about your phone. You can Take a screenshot of 'About Phone' and post it here.
Thanks for the reply!
I have attached a screenshot of what the window looks like.
"prntscr DOT com/8ffqdz" Sorry for the link, but I wasnt able to post it through the img tag.
Oh I also forgot to mention, just this morning I could root my phone with Kingo Root, but reading some negative stuff about it, I would still like to root it with the standard, old method of flashing etc, and I can't do some things I could on standard root.
white5pirit said:
Thanks for the reply!
I have attached a screenshot of what the window looks like.
"prntscr DOT com/8ffqdz" Sorry for the link, but I wasnt able to post it through the img tag.
Oh I also forgot to mention, just this morning I could root my phone with Kingo Root, but reading some negative stuff about it, I would still like to root it with the standard, old method of flashing etc, and I can't do some things I could on standard root.
Click to expand...
Click to collapse
Well, it's Xperia M2.
Let me clear that,
There are two types of Rooting methods available.
1. Permanent root
(Root access is available for ever, untill you unroot manually)
2. Temporary root
(Root access is gone, when you restart phone)
So, if you have successfully rooted your phone with Kingo Root, you no need to flash rooted kernel or firmware (its same with already root access available).
After rooting, you must have seen a app SuperSU or SuperUser or anyother that manages root permissions requested by apps that needs root (you need to grant permissions to let app work). If you do not see such any app, download it from play store.
I usually suggest Xperia users to root their devices with TowelRoot app. It is smart and simple and it does not contain any preloaded app for permissions (that means you can switch with SuperSU or Superuser)
Also, what things you could not do? let me know. I'll help you out
Regards,
hitman-xda
hitman-xda said:
Well, it's Xperia M2.
Let me clear that,
There are two types of Rooting methods available.
1. Permanent root
(Root access is available for ever, untill you unroot manually)
2. Temporary root
(Root access is gone, when you restart phone)
So, if you have successfully rooted your phone with Kingo Root, you no need to flash rooted kernel or firmware (its same with already root access available).
After rooting, you must have seen a app SuperSU or SuperUser or anyother that manages root permissions requested by apps that needs root (you need to grant permissions to let app work). If you do not see such any app, download it from play store.
I usually suggest Xperia users to root their devices with TowelRoot app. It is smart and simple and it does not contain any preloaded app for permissions (that means you can switch with SuperSU or Superuser)
Also, what things you could not do? let me know. I'll help you out
Regards,
hitman-xda
Click to expand...
Click to collapse
Again, thanks for the reply. Yup, I saw the SuperUser app, and the problems I have might not be phone breaking and such, but I would like to be able to do things like, change permissions of certain folders, which i cant do with the Kingo root, as it somehow denies the access to the folder, even tho I allowed root browser/es file manager root access. Overall, i think the problem is with the permission system Kingo has. I'd also like to mention that i would love to install Cyanogenmod on my device, but I will look into that myself @edit: Also, I would prefer to have a premanent root, instead of the towelroot and such.
white5pirit said:
Again, thanks for the reply. Yup, I saw the SuperUser app, and the problems I have might not be phone breaking and such, but I would like to be able to do things like, change permissions of certain folders, which i cant do with the Kingo root, as it somehow denies the access to the folder, even tho I allowed root browser/es file manager root access. Overall, i think the problem is with the permission system Kingo has. I'd also like to mention that i would love to install Cyanogenmod on my device, but I will look into that myself @edit: Also, I would prefer to have a premanent root, instead of the towelroot and such.
Click to expand...
Click to collapse
You could just press the 'thumbs up' instead writing 'thanks' everytime.
Well, why do you want to change the permissions of the folders? You could mess-up your device if you change permissions for the root folders.
The problem looks strange. If you have rooted successfully and GRANTED permissions for ES file explorer through SuperUser, you should not get any problem changing permissions. Check in SuperUser app that you see ES file explorer.
Also try using other explorer app. I use 'Solid Explorer' and its great.
If you have temporarily rooted your device as I mentioned in above post, try using TowelRoot app for rooting your device permanently and manually download SuperSU.
If you want to use CyanogenMod (it'll be pre-rooted) you need to carry below steps;
1. Unlock your Bootloader
(Wipes everything)
2. Install recovery.
3. Take stock ROM backup.
4. Flash ROM.zip
5. Flash GApps (optional)
6. Wipe cache+dalvic+factory reset
7. Reboot
Regards,
hitman-xda
Problem is that my bootloader can't be unlocked. I guess there is literally no way in which i can unlock it then?
white5pirit said:
Problem is that my bootloader can't be unlocked. I guess there is literally no way in which i can unlock it then?
Click to expand...
Click to collapse
If your bootloader status says
'unlock bootloader allowed = NO'
Then you can't flash anything on your phone. Almost every ROM needs an unlocked bootloader. There will be some ROMs that can be flashed over locked bootloader but they will be stock based.
EDIT: You have a good Luck, you can flash recovery on Locked bootloader
http://forum.xda-developers.com/xperia-m2/development/d2303-clockworkmod-6-0-4-6-t3011821
If you flash recovery successfully, that means you can flash ROM
Check below link for ROMs Available;
http://forum.xda-developers.com/xperia-m2/development
Regards,
hitman-xda
Yup, my bootloader says it can't be unlocked. Anyways, i tried the link yo usent me, but it comes up with an error, saying "device not found". I went into recovery mode on my phone, but i assume it might be the adb driver issue? I will try to reinstall it, and get back to you.
@edit: I reinstalled the ADB drivers, and now CWM is stuck on "daemon succesfully started", but it will not do anything else. Any clue as to what could I do to fix this? @edit2: Actually, disregard what i said. It still comes up as" Device not found"
white5pirit said:
Yup, my bootloader says it can't be unlocked. Anyways, i tried the link yo usent me, but it comes up with an error, saying "device not found". I went into recovery mode on my phone, but i assume it might be the adb driver issue? I will try to reinstall it, and get back to you.
@edit: I reinstalled the ADB drivers, and now CWM is stuck on "daemon succesfully started", but it will not do anything else. Any clue as to what could I do to fix this? @edit2: Actually, disregard what i said. It still comes up as" Device not found"
Click to expand...
Click to collapse
It can be a drivers issue. Install PC companion and connect your phone, let PCC install essential drivers and after that follow the same steps for installing recovery.
If you post any screenshot, that would be better.
Mkay, it worked now after i reinstalled the device in Sony PC companion. Heres a screenshot of what the CWM cmd window looks like: "prntscr DOT com/8fth1u". I assume this is good? So, all i have to do now is just download Cyanogen Mod and flash it, right?
white5pirit said:
Mkay, it worked now after i reinstalled the device in Sony PC companion. Heres a screenshot of what the CWM cmd window looks like: "prntscr DOT com/8fth1u". I assume this is good? So, all i have to do now is just download Cyanogen Mod and flash it, right?
Click to expand...
Click to collapse
Yup! Everything looks good. Just try to enter into recovery before downloading CM.
1.Switch off your phone and wait for 10 sec
2. switch on
3. When you see LED, try pressing either of vol buttons.
Hate to rain on the parade, but CM and CM based roms don't work with locked bootloaders for that phone, despite having CWM. It should say in the title of the thread whether it'll work with locked bootloaders.
es0tericcha0s said:
Hate to rain on the parade, but CM and CM based roms don't work with locked bootloaders for that phone, despite having CWM. It should say in the title of the thread whether it'll work with locked bootloaders.
Click to expand...
Click to collapse
Yeah you are right! Purely CM doesn't work on locked bootloader. But there must be any ROM available that is based on CM or even other ROMs that has some CM features.
I went through a few threads in that forum, Omni, CM, PAC, etc and all mentioned needing unlocked bootloader. Best bet is a good stock rom and Xposed to enable other features.
es0tericcha0s said:
I went through a few threads in that forum, Omni, CM, PAC, etc and all mentioned needing unlocked bootloader. Best bet is a good stock rom and Xposed to enable other features.
Click to expand...
Click to collapse
Z4 experience looks great ;
http://forum.xda-developers.com/xperia-m2/development/rom-z4-experience-locked-unlocked-bl-t3079811
Your xposed idea is great. Plus there must be GravityBox
Related
This guide will enable you to easily root your phone in 6 steps. I've taken out the mystery and complications.
1) Go to HTC Dev site and manually unlock your bootloader. Select "register" and create your account.
1a) After you are registered select "all other supported models" in the pull down box
1b) Click "begin unlock bootloader". it will ask "are you sure" yes of course you are. acknowledge legal terms. then continue.
1c) Ignore the battery pull instructions as we can't pull the battery. hold down the power key and the volume down key until the bottom buttons stop flashing and your phone shuts off (don't worry if you take a screenshot. It happens all the time). then release ONLY THE POWER BUTTON. Keep holding the volume down key until the bootloader screen shows up.
1d) Follow "step 3" and the rest of the instructions as listed on the HTC site to unlock your bootloader manually.
2) Install android ADB/SDK on your pc. This video shows how to do it nicely:
2a) ****NEW UPDATED 03/05/13*** Alternatively if you DON'T want to install ADB/SDK you can just download the NON-FLASHABLE platform-tools.zip file located in my dropbox folder here.
Just extract this folder to your desktop using WINZIP or whatever archive tool you use and proceed to step 3.
3) Open a command line in your "platform-tools" folder by holding shift+right click anywhere within the folder and selecting the menu option "open a command window here". Then click here to install TWRP using fastboot. Follow the "Download - Fastboot Method:" instructions.
3a) If your phone isn't detected by windows please install the proper USB drivers for your operating system. Go here for 32bit. Go here for 64 bit.
4) Flash SuperSu and Busybox on your device:
4a) Click here and download the latest version of SuperSu. save it to your sdcard.
4b) Go to my dropbox and download Busybox 1.20.2 and save it to your sdcard.
5) Reboot into recovery (via the bootloader selection)
6) Flash the SuperSu zip and the Busybox zip listed in 4a and 4b
That's it!
"So now what?" you may be asking.
You are now free to flash ROMs that support s-on.
Two are my favorites are
(1) Stock with Goodies. (my personal favorite and the one I use today). This is a great ROM for beginners and people who prefer a slimmed down ROM (minus the bloat) and lots of free memory!
(2) Viper4G. This is a ROM for more experienced users and offers TONS of customization.
You can also run apps from Google play that required ROOT access!
If you're feeling slightly adventurous you can flash a custom kernel (which will allow you to overclock your phone). Two of the kernels I use are:
(1) ElementalX by flar2. Click here to take a trip over there. This one is especially important to flash as it seems HTC was up to shenanigans with the latest HBoot (2.09).
If you're unlucky enough to have HBoot 2.09 they have RESTRICTED access to your /system partition. What does this mean to you? It means that if any app writes to your /system partition (ROOTED or not) the phone will "panic" and reboot. Shady behavior if you ask me. The solution? Flash this kernel! it will give you write access so that everything works properly.
(2) The Arc-Reactor kernel! This one is for people that are s-off (see below for an explanation of s-off) only! It's the kernel I currently use and is the fastest kernel out there! Highly recommended if you decide to go s-off!!!
If and when you're feeling more adventurous you can go "s-off" (security off) which removes any security limitations of your phone. It makes flashing ROMs and updating firmware a lot easier. You can find out about s-off by taking a trip over to the DirtyRacun thread here. I will NOT walk you through this process. They will totally help you on their IRC channel. Just read post # 1 in that thread.
There's also a new method of s-off which literally takes 2 minutes. It's called facepalm and is located here But is NOT for the feint of heart, bad typers, nor people that cannot follow instructions! Why? One typo here and your phone is a brick. A paperweight. Useless. Well...you can recover...but that's not the purpose of this thread. If you DO brick your phone PM me. I'll help you out.
I take NO credit for any of this. It's all out there to learn I just put it all together. In one spot. Any questions feel free to PM me.
If I helped you out hit the THANKS button...or buy me a beer! Either way lol!
Tested and works with 3.16.651.3 (even if you took the OTA and have hboot 2.09 and are s-on)
Did you use SuperSU or Superuser for root access? Either way could you please update the binary to see if it succeeds or if you get an instant reboot?
lancemoreland said:
Did you use SuperSU or Superuser for root access? Either way could you please update the binary to see if it succeeds or if you get an instant reboot?
Click to expand...
Click to collapse
Everyone that is using supersu is experiencing that issue. The program itself will grant superuser access to your device. You don't need to open it. When you try and open it it will attempt to update the binary and then reboot the phone. You can ALWAYS reflash a new version of supersu when they update it.
To be clear: I'm up and running on my phone right now with superuser access. I'm fine unless I try to open the supersu program itself. Then I experience this issue you pointed out.
rawintellect said:
Everyone that is using supersu is experiencing that issue. The program itself will grant superuser access to your device. You don't need to open it. When you try and open it it will attempt to update the binary and then reboot the phone. You can ALWAYS reflash a new version of supersu when they update it.
To be clear: I'm up and running on my phone right now with superuser access. I'm fine unless I try to open the supersu program itself. Then I experience this issue you pointed out.
Click to expand...
Click to collapse
I agree. I am up and running also but the new hboot locks the system partition and any app that tries to write to it will cause a reboot. Ad-free is another example.
lancemoreland said:
I agree. I am up and running also but the new hboot locks the system partition and any app that tries to write to it will cause a reboot. Ad-free is another example.
Click to expand...
Click to collapse
Indeed this is a well documented problem but really not what this thread is about. Perhaps you can check out THIS thread where they are discussing this issue at length and hopefully they will come up with a solution for it?
http://forum.xda-developers.com/showthread.php?t=1538053
It also looks as though chainfire (the OP) is working on a fix if I read the last few posts correctly. and when he gets it I will update this post with it.
rawintellect said:
It also looks as though chainfire (the OP) is working on a fix if I read the last few posts correctly. and when he gets it I will update this post with it.
Click to expand...
Click to collapse
Yes I am participating in that thread. Chainfire is looking for a work around for his specific app, other apps that write to the system partition will no longer work. The point is that with Hboot 2.09 there are limitations and we will not enjoy full root as we have before when we were s-on.
Updated with an alternative superuser program.
SuperSU would ask to update binary and then just reboot. This fixed my problem for being able to access/deny and turn off messages. However it did not uninstall superSU will this cause a conflict having them both?
Edit: Okay I am dumb, I had to uninstall superSU first. Then I reflashed superuser to be able to have root privileges for my apps. When I just reflashed superuser hoping it would get ride of and superuser and keep root it did not.
Thanks it worked!
Help with rooting please.
So my phone was updated OTA without being rooted to 3.15.651.16 but now it is frozen. The touch screen will work temporarily upon a simulated battery pull and then freeze again only for me to simpull again and then it freeze again. I've gone into the bootloader and factory reset and wiped the cache but it's still messed up. So I think that maybe it's the software not installing correctly or something because this only started happening immediately after I download the new update.
I'm thinking about rooting my phone and even though I'm a pretty techy person this is new to me. I'm hoping that if I root my phone I can put it back to the stock software before the update and then just re-update OTA stock to the new update. I think that may fix it. Do y'all have any input it would be greatly appreciated as I have been dealing with this useless phone for over a week now.
Thanks.
MrSteez said:
So my phone was updated OTA without being rooted to 3.15.651.16 but now it is frozen. The touch screen will work temporarily upon a simulated battery pull and then freeze again only for me to simpull again and then it freeze again. I've gone into the bootloader and factory reset and wiped the cache but it's still messed up. So I think that maybe it's the software not installing correctly or something because this only started happening immediately after I download the new update.
I'm thinking about rooting my phone and even though I'm a pretty techy person this is new to me. I'm hoping that if I root my phone I can put it back to the stock software before the update and then just re-update OTA stock to the new update. I think that may fix it. Do y'all have any input it would be greatly appreciated as I have been dealing with this useless phone for over a week now.
Thanks.
Click to expand...
Click to collapse
Well my suggestion is to go ahead and unlock your phone, flash a recovery and root it using my instructions. Then if you want BONE stock flash the odexed version of Jellybean that Viperboy has in his thread located here: http://forum.xda-developers.com/showthread.php?t=2045929
Why am I suggesting you do this? Because the OTA was very bugged. HTC is VERY slow with fixes. Developers can fix errors in the base errors usually faster than HTC. And most importantly when you are feeling like a change you can flash a custom zip at any time. The ONLY downside to unlocking and rooting is that you void your warranty with HTC, but NOT with sprint! Sprint will still honor a replacement phone when you RELOCK your phone and use the RUU (which isn't available yet but will be) to bring it back to stock. Your bootloader will say *RELOCKED* which lets them know you unlocked it but again they will honor a replacement.
Updated thread with instructions on manually uninstalling supersu first before installing superuser 3.2
Thank you very much!
rawintellect said:
Well my suggestion is to go ahead and unlock your phone, flash a recovery and root it using my instructions. Then if you want BONE stock flash the odexed version of Jellybean that Viperboy has in his thread located here: http://forum.xda-developers.com/showthread.php?t=2045929
Why am I suggesting you do this? Because the OTA was very bugged. HTC is VERY slow with fixes. Developers can fix errors in the base errors usually faster than HTC. And most importantly when you are feeling like a change you can flash a custom zip at any time. The ONLY downside to unlocking and rooting is that you void your warranty with HTC, but NOT with sprint! Sprint will still honor a replacement phone when you RELOCK your phone and use the RUU (which isn't available yet but will be) to bring it back to stock. Your bootloader will say *RELOCKED* which lets them know you unlocked it but again they will honor a replacement.
Click to expand...
Click to collapse
Thanks I seriously appreciate it. I'm at work right now (I actually work at Sprint by the way which is why I'm not worried about having the phone replaced my tech will do it regardless) so I'm probably gonna look over your instructions carefully and then do this tomorrow. I'll let you know what happens I'm really hoping this will do it. It has to be some kind of serious installation bug in the new update because I never had this problem until literally minutes after updating.
And then after the completely stock RUU comes out (with no root or anything special) I can go back to completely locked and stock again? That's what I think I'd prefer but who knows I'm a Android and tech fanboy maybe I'll prefer the root.
MrSteez said:
Thanks I seriously appreciate it. I'm at work right now (I actually work at Sprint by the way which is why I'm not worried about having the phone replaced my tech will do it regardless) so I'm probably gonna look over your instructions carefully and then do this tomorrow. I'll let you know what happens I'm really hoping this will do it. It has to be some kind of serious installation bug in the new update because I never had this problem until literally minutes after updating.
And then after the completely stock RUU comes out (with no root or anything special) I can go back to completely locked and stock again? That's what I think I'd prefer but who knows I'm a Android and tech fanboy maybe I'll prefer the root.
Click to expand...
Click to collapse
yes. going back to stock is as simple as this:
(1) Boot your phone into the bootloader. make sure fastboot is selected. if you have the drivers installed correctly your phone will read "fastboot usb"
(2) if you followed my instructions on rooting you have ADB/SDK installed. so issue the command to relock your phone. type: fastboot oem lock
(3) run the RUU for 3.15.651.16. Done. Your bootloader will say *relocked* but it will be 100% stock.
Uh oh
I think i messed up. I did not see busy box installed and SuperSU is not updating.
The file listed in step 6 contains busybox. It also contains supersu. You want to flash the superuser file after flashing the file in step 6. It will overlay supersu with superuser 3.2. There is no need to update superuser 3.2 once you flashed it. It is the latest release.
Sent from my EVO using xda app-developers app
do i need to just flash the new superuser and it will fix the binary problema nd the titanium problem?
mobilecj said:
do i need to just flash the new superuser and it will fix the binary problema nd the titanium problem?
Click to expand...
Click to collapse
I replied to your email. But check my first post on the subject of superuser and how to uninstall supersu. if you need to that is. I tested this myself and it did uninstall supersu for me by just flashing superuser 3.2. Some people have reported this doesn't work for them.
okay sorry just got both i am going to try it now.. Its all knew to me it seemed like the information was explaining a dual process and i only had acquired one problem.. will post back in a few!
Hi, first i appriciate ure help and the work here is amazing. i wanted to put the question directly to the right threat but i couldnt (no 10 messages).
i have rooted my galaxy s4 as explained in http://forum.xda-developers.com/showthread.php?t=2364980.
i did everything exactly as mentioned from step 1 to 9 and it all worked.
When i started my phone, also as mentioned, the knox-file told me that phone has security issues... (i thought "nice, now its definitaly rooted"). SuperSU asked me if it shall block the knox, i said yes and the messages stopped.
To make it sure, i downloaded "root checker", the app asked for permission at superSU, i gave it, then message from phone that permission is given, but then nothing happened. Same for Titanium Backup. When i wanted to set permissions directly at superSU, it said that binary file needs an update. What i did was to update superSU via google play as mentioned in many forums, but still same problem. i also downloaded super user, the app said no root permission.
-> i rooted the phone already 3 times following exactly the instrucions at thread from above, every time the same problem.
I read a lot in forums, my conclusion to the problem is that i still dont have my phone rooted.
- What do you think??
- Has anyone any idea what i can do to get my phone rooted?
- Is there a possibility to unroot the phone? because now i always get questions about permissions, but it makes no difference what i press bec it doesnt work.
penqrockt said:
Hi, first i appriciate ure help and the work here is amazing. i wanted to put the question directly to the right threat but i couldnt (no 10 messages).
i have rooted my galaxy s4 as explained in http://forum.xda-developers.com/showthread.php?t=2364980.
i did everything exactly as mentioned from step 1 to 9 and it all worked.
When i started my phone, also as mentioned, the knox-file told me that phone has security issues... (i thought "nice, now its definitaly rooted"). SuperSU asked me if it shall block the knox, i said yes and the messages stopped.
To make it sure, i downloaded "root checker", the app asked for permission at superSU, i gave it, then message from phone that permission is given, but then nothing happened. Same for Titanium Backup. When i wanted to set permissions directly at superSU, it said that binary file needs an update. What i did was to update superSU via google play as mentioned in many forums, but still same problem. i also downloaded super user, the app said no root permission.
-> i rooted the phone already 3 times following exactly the instrucions at thread from above, every time the same problem.
I read a lot in forums, my conclusion to the problem is that i still dont have my phone rooted.
- What do you think??
- Has anyone any idea what i can do to get my phone rooted?
- Is there a possibility to unroot the phone? because now i always get questions about permissions, but it makes no difference what i press bec it doesnt work.
Click to expand...
Click to collapse
Try flashing this in CWM recovery:
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
Hope this helps!
Try flashing this in CWM recovery
Click to expand...
Click to collapse
It might be kind of a noobie question but i still ask it
I followed the instructions from the thread mentioned earlier, but when i go in recovery mode with the button combo i have the "normal" recovery from android and not the CWM. do i need to flash the CWM to my phone like mentioned for example here at method A?
Another thing: Do you think that my phone is rooted and i just got problems because of the SuperSU binary file?
penqrockt said:
It might be kind of a noobie question but i still ask it
I followed the instructions from the thread mentioned earlier, but when i go in recovery mode with the button combo i have the "normal" recovery from android and not the CWM. do i need to flash the CWM to my phone like mentioned for example here at method A?
Another thing: Do you think that my phone is rooted and i just got problems because of the SuperSU binary file?
Click to expand...
Click to collapse
Place the Update-SuperSUv1.86.zip (I gave you a link for it in previous post) on your sd card then repeat steps 2-7 from this thread:
http://forum.xda-developers.com/showthread.php?t=2364980
Once you are booted into CWM recovery flash the Update-SuperSUv1.86.zip file and reboot. Now go open SuperSU it should ask if you want to disable knox. Say yes and then try root checker.
If you do not have Su binary on the phone then you are not rooted.
There is a file in the phone that reflashes the stock recovery on every boot, you would need to remove it to keep CWM.
Please let me know if this works for you, good luck!
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:
Hey guys,
Just wanted to let you know that I've found a way to permanently root the latest stock KitKat ROM for our LG L9 II (D605).
Here's what I did:
Starting with fresh KDZ install of v20h (no cwm or other things necessary), you need to be on Dalvik (default). (It should work up to v20h, not just on v20h btw.)
Two important steps before proceeding: Settings/Security -> Enable 'Unkown Sources' and Disable 'Verify Apps'!
1) Download and install KingRoot, use it to root the phone (might restart, after it boots, just start the app again). Make sure you're on WiFi while running Kingroot.
2) Download and install SuperSU Me Free app, use it to delete KingUser and switch to SuperSu. Make sure to give the app root permissions.
At this point you're fully rooted with working SuperSU, although you will lose it at restart. If you just need 'temproot' to delete some stuff, go ahead, you're done.
To finalize root:
3) Put this file to the '/cache' folder. Root is required to do this step. Do it with Total Commander or some other file manager app (give it root permissions).
4) Download and install Reini Reboot from Play Store. Start the app, give it root permissions. Click 'Restart to Recovery'. Phone restarts.
5) Welcome to your stock system recovery. (Go up or down with volume keys and select with power key.)
Navigate to 'Apply update from cache', where you will find the root_v2b.zip file you put there. Click on it, it installs, then select 'reboot system now'.
You are now fully rooted, that's permanent.
(Might have to update the SU binary right after, and another time after you update SuperSU in Play Store.)
Feel free to hit 'thanks' if it helped.
Hi!
I just wanna say thanks for this easy described method of rooting my beloved LG Optimus L9 II. I tried this method about 30 minutes ago and so far so good. I appreciate your easy description of going about this method and I also appreciate that you either attached or linked all the tools that you need for this rooting. I hope that more people discoveres this method. I do hope that you know how much I really appreciate this. A BIG thanks from me!
i have cmw recovery, no Apply update from cache option. Any solution?
whirring91 said:
i have cmw recovery, no Apply update from cache option. Any solution?
Click to expand...
Click to collapse
Yes. Do this after step 2)
3) Download this file and put in on your phone (anywhere).
4) Enter CWM and flash the root_v2b.zip file with CWM.
Thanks, it works like a charm. Point 4 can be done by just using "adb reboot recovery" though.
Work on v20g?
Trevinho said:
Thanks, it works like a charm. Point 4 can be done by just using "adb reboot recovery" though.
Click to expand...
Click to collapse
Thanks for the feedback. It's easier (noob-proof) this way though. But you're right
@Famenz: I think it should work up to v20H, but feel free to try.
D60520d-260-06 - OK
It worked for D60520d-260-06, brand Play.
I am using an older version of KingRoot-4.0.0.233-release-201505071219_105001.apk
Official XDA website SuperSU Me.
Please follow there thanks to @gatesjunior.
Do I need to hard reset my phone before?
Hepita said:
Do I need to hard reset my phone before?
Click to expand...
Click to collapse
Installing the application does not require resetting the device.
root_v2b.zip is not compatible with V20H, gives me "E:footer is wrong" and cancels
Some questions.
- Why supersu me doesnt keep the root ?
- Can't I skip the step 2 and install supersume at the end ?
- Cant we just spy what method king root uses to root and make a root for us ?
- I havent tryed framaroot casue its too wierd that it ask for photocamera access permission... does it work ?
P.S. I just noticed that kingroot could be chinese ? (I see asian chars) And you know that chinese puts spyware everywhere !
(Ok, android it self is a spyware)
P.P.S. King root and framaroot doesnt work for me ! ( vodafone 20g )
xdaxuser said:
Some questions.
Click to expand...
Click to collapse
You probably haven't noticed this, but the D605 has been abandoned way before even the P71x, and that was kept alive up until somewhere in 2016. It's quite safe to assume your questions will probably never find answers here.
About the spywhere, every piece of electronics is spying on you. If you want privacy, go live in the mountains.
literally there's no file to put on the phone because media fire is gone...
Hello, there!
The precious thing is a cheap 7" allwinner a33 tablet. By apps its recognized as Astar y33.
It is a 16Gb Storage Tablet with 1 gb ram. I bought ist for 42€. :cyclops:
Unluckily i only can install apps on a 1 gb internal storage and the 16gb are only for media or movable apps. It should have 1gb ram but Aida64 said it has 512 installed.
I urgently need to give root to it, to make it work -and enjoyable. I allready tried out:
-Kingoroot (also via PC)
-Kingroot
-Iroot
-Towelroot
-SuperOneClick.exe
-and various desktop based one click rooters
and all failed.
I dont know what i can try next.
I have the ADB driver, but not a certain fastboot interface driver, which i could not find in the internet at all. I have a 64 system.
Many people with similar tablets could root them with Kingo root or Iroot, but it worked not for me and my tablet must be somehow different, it also did not had any bloat or malware on it.
Please, please, give me a hint what i could try next. :silly:
These are the specifications of the tablet:
*See attachements
Root method for recovery
Good afternoon!
To apply the patch-and for rooting you device, it is necessary to get into Recovery.
So try to load into recovery by this way: "Settings-> Recovery and reset-> Recovery Mode".
After rebooting, you see some menu where you should select drive(sd card) on which the pre-recorded file "Update.zip"
After finishing, restart your device use first point of menu.
Now you have a root, it is necessary to update the SuperSu by selecting "OK".
P.S.
I didn't test it but find it on some good forums. Send privet massage to me if you have some questions.
Root_patch
Good evening!
I tried it out right now.
It was flashable but the su binary wont let me update. How should i update the su binary? Do i need another flashable zip?
Unluckily the root checker says that root permission is not granted yet.
Update: I flashed a current Supersu update.zip with my stock recovery mode.
It says "installtion abortet".
I dunno. I ll have to use the tablet to cut vegetables. *joke
Wow, seems like suddenly root was granted.
Last thing was: I tried to root it with Iroot via PC.
It installed some adware on the tablet but the root checker still said no.
Then Kinguser detected some malware in the notification are. I fixed this and noticed that i also could remove system apps with Kinguser.
Then i retried apps that recommed root like rashr and to my surprise - root was granted suddenly!!!
:laugh:
Woah! Somehow im not so sure what rooted it now, because i already tried everything five times before already and it didnt work ^^
I think, it could be this:
Kingroot has shown me before, that my device is not supported. I could kinda request compatibility, which i did.
Maybe this magic happend unnoticed and suddenly it was rooted.
Oh ****.
Afterwards i flashed some recovery.img someone told me its for TWRP for the tablet.
Since then, its in a bootloop.
How to fix this? For now, i will just wait until the battery has run empty. (That fixed beeing stuck in fastboot mode before)
THANKS!!!
Nejix83 said:
Root method for recovery
Good afternoon!
To apply the patch-and for rooting you device, it is necessary to get into Recovery.
So try to load into recovery by this way: "Settings-> Recovery and reset-> Recovery Mode".
After rebooting, you see some menu where you should select drive(sd card) on which the pre-recorded file "Update.zip"
After finishing, restart your device use first point of menu.
Now you have a root, it is necessary to update the SuperSu by selecting "OK".
P.S.
I didn't test it but find it on some good forums. Send privet massage to me if you have some questions.
Root_patch
Click to expand...
Click to collapse
Hey dude, you are awesome! I could not find anywhere this file. At last my tablet is rooted. I have been looking for firmwares for these tablets everywhere and, as they are really old and chinese crap now, all mirrors I find are down. Where did you find this zip? maybe I can find a firmware there. I need to flash it from 0 because I did a mess with adb and deleted every system app
Hello everyone
do you have an update.zip SuperSU-v2.82
Best Regards
Great !
Nejix83 said:
Root method for recovery
Good afternoon!
To apply the patch-and for rooting you device, it is necessary to get into Recovery.
So try to load into recovery by this way: "Settings-> Recovery and reset-> Recovery Mode".
After rebooting, you see some menu where you should select drive(sd card) on which the pre-recorded file "Update.zip"
After finishing, restart your device use first point of menu.
Now you have a root, it is necessary to update the SuperSu by selecting "OK".
P.S.
I didn't test it but find it on some good forums. Send privet massage to me if you have some questions.
Root_patch
Click to expand...
Click to collapse
That's work fine.
My Tv Box is Q Plus Android 9.
Maybe it can help : You can use the rom of Vorkez 7 in Q Plus, because they have same hardware.
steleclanel1 said:
That's work fine.
My Tv Box is Q Plus Android 9.
Maybe it can help : You can use the rom of Vorkez 7 in Q Plus, because they have same hardware.
Click to expand...
Click to collapse
@steleclanel1
Hi, I have a Q Plus box too and have managed to root it but I need to bypass google play device check. I have edited build.prop successfully but can't find the global settings database to complete this. Are you able to help... does the Vorkez 7 rom allow for this? Thanks
thanks, it is work fine