Related
I've recently acquired a Photon 4g and would like to root it. I've been using guides on XDA for a while now. Ive been rooting since the g1 and I've tied every method available for the Photon to no avail. I have the latest update so I think thats why the tordpedo method isn't working and I've tried both AIO roots with no luck as well. Can anyone give me any advice as to what I can do or point me in the right direction? Been searching the forum and google and I can find anything.
Side note, is it possible to downgrade and then root? Been searching downgrade on the Photon and again... no luck. Any help would be greatly appreciated.
You don't need to downgrade to root it. I used the one click AIO root on the latest update with no problems. And fyi you also need to unlock the boot loader on the photon, its not like how on other phones where once you root it your done.
Here's everything you need to know http://forum.xda-developers.com/showthread.php?p=20331544
Sent from my MB855 using Tapatalk
Wrong, just for this person to ROOT the phone he/she doesnt need to unlock the bootloader.
For them to root the phone you need to before running the AIO root you need to enable USB debugging on the phone.
To enable you go to settings >> Applications >>> Development >>> then enable USB Debugging..
Good luck chances are good that this was your issue.
Lancerz said:
You don't need to downgrade to root it. I used the one click AIO root on the latest update with no problems. And fyi you also need to unlock the boot loader on the photon, its not like how on other phones where once you root it your done.
Here's everything you need to know http://forum.xda-developers.com/showthread.php?p=20331544
Sent from my MB855 using Tapatalk
Click to expand...
Click to collapse
I also used shabby's AIO one click. I bought my MoPho and activated it. I think it happened during activation, but may have been right after, it updated immediately updated to the latest firmware. When I set up one of the things I did was enable USB debugging. When I rooted it worked perfectly first try.
I'm a MoPho-er
sanjuansr said:
I've recently acquired a Photon 4g and would like to root it. I've been using guides on XDA for a while now. Ive been rooting since the g1 and I've tied every method available for the Photon to no avail. I have the latest update so I think thats why the tordpedo method isn't working and I've tried both AIO roots with no luck as well. Can anyone give me any advice as to what I can do or point me in the right direction? Been searching the forum and google and I can find anything.
Side note, is it possible to downgrade and then root? Been searching downgrade on the Photon and again... no luck. Any help would be greatly appreciated.
Click to expand...
Click to collapse
I used the method described by qbking77 in his youtube video.
Go to youtube and search for "qbking77 photon" Its one of the videos that gets listed.
Hope this helps.
- Harakiri
I tried that. I've installed the proper drivers. enabled debugging and it still won't root my phone. I've been rooting for a while and I followed the instructions to the T.
sanjuansr said:
I tried that. I've installed the proper drivers. enabled debugging and it still won't root my phone. I've been rooting for a while and I followed the instructions to the T.
Click to expand...
Click to collapse
You're not giving us info to allow us to help:
- Error messages?
- Screen shots of your PC's DOS window?
- Was your Photon new out of box? If not, hard to tell what may have done to it. Maybe flash back to stock.
ScottieRotten said:
Wrong, just for this person to ROOT the phone he/she doesnt need to unlock the bootloader.
For them to root the phone you need to before running the AIO root you need to enable USB debugging on the phone.
To enable you go to settings >> Applications >>> Development >>> then enable USB Debugging..
Good luck chances are good that this was your issue.
Click to expand...
Click to collapse
I guess you don't understand what I'm saying. On other phones when you root them that's all you have to do to run custom roms. On the photon to run custom roms you have to unlock the bootloader unless its 1 of the 2 roms where you can be locked. I didn't say you had to unlock the bootloader to root the phone.
No problem, just seemed as bad advice compared to what the OP was refering to.
He was having trouble rooting, he is obviously new and it seemed that telling him to unlock his bootloader was only clouding the issue.
He/she was having trouble rooting, so what would cause that? Certaintly not the bootloader.
Im at work so i dont have my laptop to give the exact error but ill give a brief explanation from memory. I installed the 32 bit drivers on my laptop running windows 7. I ran the aio and when it says thanks to creator(i forgot who but my version doesnt say edgan) i make sure o have debugging check and proceed. It recognizes the phone and runs fine up until it says erasing all your ****. Then it reboots and says device not recognized repeatedly then says you should be rooted.
Sent from my MB855 using xda premium
Thanks guys for all your advice and help. I found my problem and I'm now rooted.
For anyone interested in the solution. I switched laptops from one with windows 7 to a xp laptop and every time the AIO said it was rebooting I unplugged my phone until it was fully booted then plugged it back in to be sure the program recognized it. Worked on first try with new machine.
I just took a look at ALLinONE and realized there are a lot of different options and I'm not sure what all of them do.
My S tablet arrives tomorrow and I want to root it safely, with the "backdoor" option in case something goes wrong.
I would really appreciate it if any of you could tell me step by step what I need to do this. I have ADB installed already.
Thanks for any assistance you can offer!
If ADB is already installed, just run the latest AIO tool and follow the on screen instrutions for root, thats it !!
from xperia PLAY
Any news on rooting the 3g model
Sent from my HTC Desire S using XDA
xperiax10.awesome said:
If ADB is already installed, just run the latest AIO tool and follow the on screen instrutions for root, thats it !!
from xperia PLAY
Click to expand...
Click to collapse
Thanks for responding!
Sadly, my Sony S is, unfortunately, build 10 ... Not sure I'm going to keep it. It pisses me off that Sony locks their devices down so tightly and I'm stuck with all the "system software" (i.e. bloatware) that they put on it ... (sigh.)
Is there a way to root my officialy updated to ICS, Xperia Mini(ST15i) without unlocking bootloader?(in order to downgrade etc...) I just want to root my xperia mini without messing up with the warranty....Any way to root it with locked bootloader? (4.1.B.0.431)
Thanks in advance
You have to downgrade to Gingerbread, root it and then upgrade to ICS using THIS tutorial.
There could be a different way: you should flash the 4.0.3 kernel (for example the Arc one), but I can't find the tutorial. Use the search button and see if you can find it
Feanor88 said:
You have to downgrade to Gingerbread, root it and then upgrade to ICS using THIS tutorial.
There could be a different way: you should flash the 4.0.3 kernel (for example the Arc one), but I can't find the tutorial. Use the search button and see if you can find it
Click to expand...
Click to collapse
downgrading needs unlocked bootloader... :/ i had bricked my mini some time ago because i tried to downgrade with locked... (( any other way?
Thanks
EDIT: flashing xperia arc's or Neo V's for example would brick my phone....wouldn't it? (and it also needs bootloader unlock...so i don't think i would do that... BUT thanks for your help mate
No, flashing a .ftf does NOT need an unlocked bootloader. You need to unlock it only if you want to flash a custom kernel, but for custom ROMs you can use flashtool.
Same for the 4.0.3 kernel. It's a stock kernel, so you can flash it via flashtool
It WILL end in bootloop, though. The tutorial says you can use DoomLord's root kit anyway, root the phone and then flash again the 4.0.4 kernel. But find it and read it carefully, cause I didn't try it and I can't assure you it will work.
I tried the first one I suggested, though, and my bootloader is locked!
Feanor88 said:
No, flashing a .ftf does NOT need an unlocked bootloader. You need to unlock it only if you want to flash a custom kernel, but for custom ROMs you can use flashtool.
Same for the 4.0.3 kernel. It's a stock kernel, so you can flash it via flashtool
It WILL end in bootloop, though. The tutorial says you can use DoomLord's root kit anyway, root the phone and then flash again the 4.0.4 kernel. But find it and read it carefully, cause I didn't try it and I can't assure you it will work.
I tried the first one I suggested, though, and my bootloader is locked!
Click to expand...
Click to collapse
man i have a problem...when i place my phone into flashmode (down key) it disconnects on its own...and that's why i bricked my phone long time ago....now i am afraid to do that i have installed the flashtool drivers from Flashtool/drivers.... but they mustn't work for my mini....any solution please give me the drivers you use for your Mini and work with it if you can i would really appreciate that!
What do you mean, it disconnects? How much time does it take for it to disconnect? Mine does the same. If I plug it and wait for a minute or so doing nothing, it disconnects. But if I start flashing a ROM it doesn't.
The drivers I installed are in \Flashtool\drivers.
Feanor88 said:
What do you mean, it disconnects? How much time does it take for it to disconnect? Mine does the same. If I plug it and wait for a minute or so doing nothing, it disconnects. But if I start flashing a ROM it doesn't.
The drivers I installed are in \Flashtool\drivers.
Click to expand...
Click to collapse
it takes about 1-2 minutes to disconnect.But, what if it disconnects while on downgrading?
It doesn't. At least, mine doesn't! And I flashed firmware twice a day in the last week
Anyway, both ways need the use of flashtool... so if you don't want to try it, you can't root ICS
Feanor88 said:
It doesn't. At least, mine doesn't! And I flashed firmware twice a day in the last week
Anyway, both ways need the use of flashtool... so if you don't want to try it, you can't root ICS
Click to expand...
Click to collapse
Pfff i'm a bit scared.....there is no hope that there will be somewhen another way to root...?
No, I'm sorry. Anyway, just follow this steps:
1) DON'T plug your phone.
2) Open flashtool
3) Click the lightning icon and select flashmode
4) Select the .ftf you want to flash: if you want to downgrade, select wipe data. If you want to flash the 4.0.3 kernel, unckeck wipe data and check "exclude" for everything apart from kernel. Which means you'll only flash the kernel
5) Start: you'll be asked to plug your phone. Plug it now in flashmode. This way you'll avoid it being unplugged.
Flashing will start, and your phone won't be unplugged. I suppose it's unplugged automatically when you're not doing anything, it's the same for me, but I repeat, whenever I flash something (kernel, whole ROM, whatever) everything just goes fine
Feanor88 said:
No, I'm sorry. Anyway, just follow this steps:
1) DON'T plug your phone.
2) Open flashtool
3) Click the lightning icon and select flashmode
4) Select the .ftf you want to flash: if you want to downgrade, select wipe data. If you want to flash the 4.0.3 kernel, unckeck wipe data and check "exclude" for everything apart from kernel. Which means you'll only flash the kernel
5) Start: you'll be asked to plug your phone. Plug it now in flashmode. This way you'll avoid it being unplugged.
Flashing will start, and your phone won't be unplugged. I suppose it's unplugged automatically when you're not doing anything, it's the same for me, but I repeat, whenever I flash something (kernel, whole ROM, whatever) everything just goes fine
Click to expand...
Click to collapse
i maybe try it later... thanks for your replies man DD i appreciate that
kwstas 13 said:
i maybe try it later... thanks for your replies man DD i appreciate that
Click to expand...
Click to collapse
Let me know if you need more help!
Feanor88 said:
Let me know if you need more help!
Click to expand...
Click to collapse
A friend of mine told me that if i try with locked bootloader is a simple suicide!!! :/ Now i am confused again :S
kwstas 13 said:
A friend of mine told me that if i try with locked bootloader is a simple suicide!!! :/ Now i am confused again :S
Click to expand...
Click to collapse
Who is that friend of you? He is trolling. Stay away from him. And learn this. Feanor here is a better friend for you than him, when it comes to rooting your phone.
Just do as in the tutorial Fenor had shared in his first post. Everything will be fine.
And you say you bricked your phone. May we know how your repaired it?
Thanks,
Rick
Sent from my SK17i using XDA
DragonClawsAreSharp said:
Feanor here is a better friend for you than him, when it comes to rooting your phone.
Click to expand...
Click to collapse
Blushing
But don't forget I'm a noob after all... I'll just keep pointing other people's tutorials, like for example yours, Rick
DragonClawsAreSharp said:
Who is that friend of you? He is trolling. Stay away from him. And learn this. Feanor here is a better friend for you than him, when it comes to rooting your phone.
Just do as in the tutorial Fenor had shared in his first post. Everything will be fine.
And you say you bricked your phone. May we know how your repaired it?
Thanks,
Rick
Sent from my SK17i using XDA
Click to expand...
Click to collapse
while i was downgrading with locked bootloader the procces stopped on its own at 43%....and my phone wouldn't turn on and didn't even worked with flashtool....i sent it to a service centre and they fixed it ( i think i hadn't installed the proper drivers....am i right?)
kwstas 13 said:
while i was downgrading with locked bootloader the procces stopped on its own at 43%....and my phone wouldn't turn on and didn't even worked with flashtool....i sent it to a service centre and they fixed it ( i think i hadn't installed the proper drivers....am i right?)
Click to expand...
Click to collapse
That's strange. Anyway, if you installed PC Companion you have adb drivers. Install flashmode drivers from Flashtool installazion folder, you find the executable in \Flashtool\drivers. If Windows prompts you that the drivers are dangerous, just install them anyway.
What I can say is that you DON'T need to unlock your bootloader to use flashmode in Flashtool. Otherwise, my phone would have exploded long ago
Now let me tell you this: if you are SURE you did everything the right way, and still your phone got bricked, then maybe you shouldn't try. you never know.
If you tried to to something you didn't know how to do, you probably made a mistake, and that's why the phone got bricked.In this case, I'd give it a try.
But we're not able to see your phone and test it, so whatever you do, unfortunately, you always do it on your own risk.
I couldn't be more sincere.
kwstas 13 said:
while i was downgrading with locked bootloader the procces stopped on its own at 43%....and my phone wouldn't turn on and didn't even worked with flashtool....i sent it to a service centre and they fixed it ( i think i hadn't installed the proper drivers....am i right?)
Click to expand...
Click to collapse
On all probability you are correct.
They (The service centre people) flashed a firmware using Flashtool. That's what they must have did. See. I will explain things a bit.
Your phone has some memory in it (this corresponds to what was known as phone memory in older phones). This memory is of Read Only type. That is ROM. Now, of all the types of ROMs, androids have EEPROM. That stands for Electronically Erasable Programmable ROM. So you can electronically erase the data stored in the ROM and write new data on it (even though it is called Read Only). This process of writing new data on the ROM is called flashing.
For flashing, the tool that is available to us as an open source, is Flashtool. Using it we can flash ROMs into our phones, erasing the earlier ones.
Now, Sony will not want us to flash Cyanogen Mod to our phones. So they have made up the concept of locking the bootloaders. With locked bootloaders custom ROMs can not be flashed to your phone. This is because most custom ROMs are designed for a specific Kernel (the intermediate between the OS and the hardware), and flashing a custom kernel requires unlocked bootloaders.
If you want, you can flash firmwares (ROMs + Kernels released by Sony) even if you are on locked bootloader, as long as the firmware files are signed by Sony.
This restriction however is against the OpenSource spirit of Android, and thus Sony gives us the scope to unlock bootloader at the cost of loosing the warranty, and the DRM keys (search google for that).
Now coming to your problem of unability to flash properly, make sure that you have installed all the drivers. For that open up /drivers folder in /flashtool and install the .exe there. Also install the adb drivers of your device. For that have PC Companion installed on your PC. Flashing will happen properly then.
Thanks,
Rick
Sent from my SK17i using XDA
DragonClawsAreSharp said:
On all probability you are correct.
They (The service centre people) flashed a firmware using Flashtool. That's what they must have did. See. I will explain things a bit.
Your phone has some memory in it (this corresponds to what was known as phone memory in older phones). This memory is of Read Only type. That is ROM. Now, of all the types of ROMs, androids have EEPROM. That stands for Electronically Erasable Programmable ROM. So you can electronically erase the data stored in the ROM and write new data on it (even though it is called Read Only). This process of writing new data on the ROM is called flashing.
For flashing, the tool that is available to us as an open source, is Flashtool. Using it we can flash ROMs into our phones, erasing the earlier ones.
Now, Sony will not want us to flash Cyanogen Mod to our phones. So they have made up the concept of locking the bootloaders. With locked bootloaders custom ROMs can not be flashed to your phone. This is because most custom ROMs are designed for a specific Kernel (the intermediate between the OS and the hardware), and flashing a custom kernel requires unlocked bootloaders.
If you want, you can flash firmwares (ROMs + Kernels released by Sony) even if you are on locked bootloader, as long as the firmware files are signed by Sony.
This restriction however is against the OpenSource spirit of Android, and thus Sony gives us the scope to unlock bootloader at the cost of loosing the warranty, and the DRM keys (search google for that).
Now coming to your problem of unability to flash properly, make sure that you have installed all the drivers. For that open up /drivers folder in /flashtool and install the .exe there. Also install the adb drivers of your device. For that have PC Companion installed on your PC. Flashing will happen properly then.
Thanks,
Rick
Sent from my SK17i using XDA
Click to expand...
Click to collapse
You, and all developers/people here, are simply awesome!.... But this sh*t with unlocking bootloader and loosing warranty is so....stupid....I think i will give it a try and i am gonna sure thank you.... Somethink else....my phone has also a problem on the screen while scrolling....do you know if that is a hardware or a firmware problem?
What do i mean when i say scroll problem:
1st example: While browsing the Internet and scroll with fast moves, links are pressed on its own and new tabs are opened,as links are pressed.
2nd example: While i scroll the app drawer,fast s make apps open without my will....
3nd exapmle and the most representative: While playing fruit ninja and do fast moves to cut the fruits, the touchscreen doesn't even fell that i touch the screen!!! I do fast moves to cut the fruits and nothing happens!! As a result i always lose! (just joking....)
My phone is fast and really smooth only when my moves are slow....any thoughts about that? :/
Thanks once again for your BRAVE help!
You have a Mini, right? That's a hardware problem. Very common, even if not everyone realizes it. Check THIS thread for a (possible?) solution.
Hi XDA. I'm an user of a veteran Xperia Play, so now I have some experience with custom roms, kernels, recoverys and such, but not with unlocking bootloaders. I unlocked my XP with the services of this page http://unlock-bootloader.com/, which is paid.
Anyway, the reason for this thread is that my girlfriend has had a Xperia Mini Pro SK17a for like one year. Until now it was fine but it suddenly started to lag and had random reboots, so she asked me to fix it. The idea is to install some rom, but the thing is: which is the most convenient method to unlock the bootloader so I can flash custom kernels on it?
The service menu says "bootloader unlock allowed = yes", so it can be done with:
1. The official method of sony page but DRM get lost and some Sony apps stop working, or
2. Through testpoint with s1tool o setool but then flashing kernels in the original formats .sin and .img is not possible anymore
As I unlocked my xplay with paid method there are none of these problems, but I'm not willing to pay for unlocking another phone that will only be flashed once or twice, so I have some questions about the other methods in order to make a desicion on what to choose :
- With the DRM certificates missing, which apps will no longer work?
- With the method of the sony page, can I flash kernels in .img and .sin format..?
- If I unlock with testpoint with no paid method, the only way to flash kernels is in .ftf format?
- The phone is no more on warranty period. If ever damaged, can I send it to a technician with no problem? (I say this because testpoints are used for repairing as well, and there may be some problem after unlocking by these methods, I suppose)
- Will it be better if I leave the BL locked and just flash a GB rom with stock kernel? My gf is looking for the best possible battery life and stability, so she doesn't care much about performance in games
Finally, what rom and kernel would you recommend me for daily use?? lol (I'm not asking for the "best rom/kernel", it's just that I don't have enough time to properly test battery life on various roms, spending a few days on each, so I'm asking you to please recommend me SOME GOOD ROM, NOT THE BEST ROM).
Sorry for so many questions and thank you all in advance
Anyone here??? Please respond or just answer the poll....
Sent from my SK17a using xda app-developers app
If I were you I'd try the stock gingerbread rom first and if she likes it it's all right
If not, unlock it using the official method. Maybe TrackID won't work any longer, but I guess apps like shazam doing the same work should still be working!
And if you unlock like that you can flash kernels in .img .elf .sin and .ftf (I guess these are the formats), but the same formats should be supported when you unlock using the testpoint method too
To find a good rom, just tell your girlfriend to look through the development threads and if she likes the design of a rom (check screenshots) she can tell you or check the bug list herself, then you flash it and she should be happy :good:
Sent from my Nexus 4 running Android 4.4
Thanks for your answer @mihahn
All this mess was just cause she's on .62 firmware. Since it can't be rooted (I even tried some chinese app called Eroot that is claimed to work on .62 but it didn't) I couldn't install CWM or titanium in order to backup her apps and things before flashing any rom.... and the ovbious solution was to flash a custom kernel and therefore unlocking BL....
She's not a tech fan, but after a lot of explaining and after she saw your answer, she finally decided to check out the devs section ( she's doing it right now ) and hopefully choose a good rom, not just a good-looking one
And again thanks for your answer, it was all she needed
Sent from my R800a using xda app-developers app
julian280 said:
Thanks for your answer @mihahn
All this mess was just cause she's on .62 firmware. Since it can't be rooted (I even tried some chinese app called Eroot that is claimed to work on .62 but it didn't) I couldn't install CWM or titanium in order to backup her apps and things before flashing any rom.... and the ovbious solution was to flash a custom kernel and therefore unlocking BL....
She's not a tech fan, but after a lot of explaining and after she saw your answer, she finally decided to check out the devs section ( she's doing it right now ) and hopefully choose a good rom, not just a good-looking one
And again thanks for your answer, it was all she needed
Sent from my R800a using xda app-developers app
Click to expand...
Click to collapse
Well e-root does work on .62 fw. You might not have follow the steps. Try again with proper steps
Cheers,
AJ
Abhinav2 said:
Well e-root does work on .62 fw. You might not have follow the steps. Try again with proper steps
Cheers,
AJ
Click to expand...
Click to collapse
Well, I tried several times even with various versions of eroot. I think there were the 1.0 and 1.2 but none work.
I dont have here the tutorials I followed but the steps are like this:
1. Open eroot
2. Connect the phone on with mass storage mode on, USB debugging on and unknown sources on.
3. Click on root button
4. Wait for it. It shows its making 4 steps
5. It says its rooted, so you just have to unplug, reboot and enjoy.
But all those is just assumptions of what it says cause I don't speak chinese.... and the text can't be selected in order to copy and translate with google. I also remember sometimes it shows an error-like screen with some red colored "x" marks but I didn't understand either what was that about.
Thanks anyways
Sent from my R800a using xda app-developers app
julian280 said:
Well, I tried several times even with various versions of eroot. I think there were the 1.0 and 1.2 but none work.
I dont have here the tutorials I followed but the steps are like this:
1. Open eroot
2. Connect the phone on with mass storage mode on, USB debugging on and unknown sources on.
3. Click on root button
4. Wait for it. It shows its making 4 steps
5. It says its rooted, so you just have to unplug, reboot and enjoy.
But all those is just assumptions of what it says cause I don't speak chinese.... and the text can't be selected in order to copy and translate with google. I also remember sometimes it shows an error-like screen with some red colored "x" marks but I didn't understand either what was that about.
Thanks anyways
Sent from my R800a using xda app-developers app
Click to expand...
Click to collapse
You can try rooting using the cydia impactor or even the other methods mentioned in my rooting guide for the build number .62. This should help you to gain root access
Sent from my Nexus 4 running Android 4.4
Just to advise - unlocking bootloader removes all user data, so leave it as a last resort after you have backed up your data.
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: