Related
Hello everybody!
I am starting this new thread to try compile a simple to follow and reasonably written complete guide for rooting an Xperia Neo 2.3.3. I am doing this because, although there are enough information and software on this forum and on the internet in general, these are not really structured and gathered in a way that a non-experienced user (a.k.a. "noob") can easily manage, and the process of rooting 2.3.3. is a bit more complicated than 2.3.2 with Gingerbreak for instance.
This guide is for Xperia Neo running Android 2.3.3 with locked bootloader. Other devices with 2.3.3. might be rooted in a similar fashion.
Update: 2.3.4. for the Neo is out. Everything here still works as described with the difference that you get the latest 2.3.4 when updating OTA.
WARNING: some users reported that after downgrading from 2.3.4 to 2.3.2 in order to root, the battery meter showed 0%. I am not yet aware of a solution to this problem. So beware if your Neo already has the latest version.
Warning: Neither myself, nor anyone else but YOU is responsible if you damage your phone in any way or lose any information after trying to root your phone by folowing this guide! Also note that your warranty will expire when you root. However, unrooting should be possible, in principle.
--- Guide start ---
1. Back up your data. You could do this using an app called Backup Master from the Android Market. Additionally, I had my contacts and calendar synchronized with my Google account. SMS messages were not properly backed up, but I didn't care about them anyway. If you do care, you might want to save them to your SD card, using the built-in option or just use another app. Also make sure your battery is at least half charged before starting.
2. Download FlashTool from here or directly here. Install it by simply unpacking it somewhere.
3. Download the generic firmware 2.3.2 from here or directly here. You do this because Gingerbreak (will come to that) uses a security vulnerability to gain root rights in 2.3.2. that has been fixed with the new 2.3.3. Extract the .ftf file from the .rar archive you just downloaded to the sub-folder "firmwares" of your Flashtools installation from step 2. (You might need WinRar for extracting)
4. Go to your Flashtool installation to the folder "drivers" and install ggsetup-2.2.0.10.exe. Download the USB drivers for your Neo from here. Unpack the contents of the archived folder "amd64" (if on Windows 64) or "i386" (if on Windows 32) to the folder "amd64" or "x86" respectively of the installation folder of Gordons Gate. The path might be something like "c:\Program Files (x86)\Sony Ericsson\Gordons Gate\". Run DPInst.exe to install the drivers.
Alternatively to this step, I think you could install the drivers by just installing PCCompanion and plugging in your phone, but I did it the hard way.
5. Run the file X10FlashTool.exe; click Flash; you should see the firmware you downloaded in step 3 in the appearing window if you extracted it correctly; click OK (I recommend you leave the option "wipe data" checked, although some users reported that it worked for them even without wiping the data); follow the instructions (note that the back button on the Neo is on the other side as pictured); the flashing should take no more than a couple of minutes; start your phone - this will take a bit longer the first time. If after the reboot the battery meter is showing 1%, shut down and take out the battery for a minute, then boot up again.
6. Get Gingerbreak from here of directly here. This is the exploit that actually roots the phone. Copy it to your phone and install. You can do this a number of ways. For example: install ES File Explorer from the Android Market, access your PC via WLAN with it and install it directly from there. You will be prompted to change the setting to allow the installation of apps from unknown sources in case you didn't change it already. Also allow USB-debugging in the same settings menu under "developer".
7. Run Gingerbreak and tap "root device". This shouldn't take more than a couple of minutes, although some users reported it taking hours. If it is taking very long, you might want to try inserting another SD card and repeating the attempt. When it's done, it will reboot. Now you have a rooted 2.3.2. You can check this by installing the app "root checker" from the Android Market. When you start "root checker" you will be asked by an app called "superuser" if you want to grant root access to this program. This "superuser" app was installed by Gingerbreak after rooting and manages which program has root permissions.
8. Now before doing anything, go to settings>info>software update> update now and get the new Android 2.3.3 OTA (= over the air, i.e. via WLAN or 3G). Do not do this via your PC, because you will unroot the phone. There have been a lot of problems reported with this step. If right after you tap "update now" you get the message "unable to connect" try shutting down, waiting a minute and booting up again or also try setting the date and time to the correct values, in case you have something like 01 Jan 1980. Other users said, it just took a lot of attempts before it worked and that the problem might be with the SonyEricsson servers... If after the update was downloaded you get some kind of error message like "cannot update" it might be because you did some changes to system files or possibly you used a non-original firmware in step 3.
After the update was done, check again for root access with the "root checker"
9. Restore the data you backed up in step 1 and enjoy.
Update: I managed to update to 2.3.4. Unfortunately I could not simply update OTA from my rooted 2.3.3. I kept getting an error message after downloading the update, probably because I had changed system files. So I did all the above steps again, with the difference that in step 8 I got the 2.3.4. from the SE server.
--- Guide end ---
Please click the Thanks button and/or reply to this post and write your own experience or suggestions/corrections.
A similar guide/tutorial/how-to has been posted before (Here). Perhaps not as detailed as yours but nonetheless, it's been done. And do give credit to the necessary people.
But good job on taking the time and writing this up. I'm sure a lot of Neo users will appreciate it.
Cheers!
xtacy! said:
A similar guide/tutorial/how-to has been posted before (Here). Perhaps not as detailed as yours but nonetheless, it's been done. And do give credit to the necessary people.
!
Click to expand...
Click to collapse
Actually, I did link directly to the thread you wrote, because it was one of my starting points. And to be rigorous, the steps enumerated there are from here, but with the firmware for Neo. The real credit goes to the programmers of Gingerbreak, Flashtool etc.
Like I said, I was just gathering information and detailing them, I don't take credit for anything other than taking the time to write the post.
Yup, I had actually included that initially i.e. that most of us already know these steps from the original thread but then wanted to give you credit for doing what you did.
And when I said give credit where it is due, I meant the actual people behind the programs and kistigun for his tutorial.
guys after i root my neo according to this guide the ota firmware i get will be unbranded? right?
By the way thanks for the guide, i might use it one day after i gain more knowledge about those things...
If you've flashed the generic firmware, then yes, you would be unbranded BUT you will still be locked to your network until you purchase the unlock key.
Unbranding would remove all your network specific apps (part of bloatware).
marcindpol said:
guys after i root my neo according to this guide the ota firmware i get will be unbranded? right?
By the way thanks for the guide, i might use it one day after i gain more knowledge about those things...
Click to expand...
Click to collapse
An OTA update won't remove the branding, but flashing will. It's what I describe in step 5.
I was just like you a couple of days ago, but I managed to learn all this over the weekend and did all I described here. (and a few things more ) Don't rush into it. Read everything coherent and helpful you can find first.
xtacy! said:
If you've flashed the generic firmware, then yes, you would be unbranded BUT you will still be locked to your network until you purchase the unlock key.
Click to expand...
Click to collapse
Thanks for the info. I didn't have any network locks or branding on mine, but it's good to know that for future reference.
Vorsprung said:
An OTA update won't remove the branding, but flashing will. It's what I describe in step 5.
I was just like you a couple of days ago, but I managed to learn all this over the weekend and did all I described here. (and a few things more ) Don't rush into it. Read everything coherent and helpful you can find first.
Click to expand...
Click to collapse
ok i think i understand now, but just to clarify:
if i flash generic (unbranded?) and then do the OTA or Pc Companion update, the update i get will also be unbranded?.
also will all the future updates be unbranded too?
Another question: since my neo is Irish Vodafone branded phone, which generic software i should flash in step 5?
Thanks a lot for help and please do not get annoyed by my questions as i am totally noob when it comes to those things, also sorry for my poor English...
marcindpol said:
ok i think i understand now, but just to clarify:
if i flash generic (unbranded?) and then do the OTA or Pc Companion update, the update i get will also be unbranded?.
also will all the future updates be unbranded too?
Click to expand...
Click to collapse
The answer should be yes to both questions. Once you've debranded your phone, it will not get "rebranded" (except if you flash it with a branded firmware). The generic firmware linked here is of course without any branding.
marcindpol said:
Another question: since my neo is Irish Vodafone branded phone, which generic software i should flash in step 5?
Click to expand...
Click to collapse
You could use the generic one, but you will lose the branding. I'm guessing you don't have a problem with that.
marcindpol said:
Thanks a lot for help and please do not get annoyed by my questions as i am totally noob when it comes to those things, also sorry for my poor English...
Click to expand...
Click to collapse
You're welcome! I'm not exactly experienced myself, so I don't guarantee that my answers are 100% accurate and correct...
I don't think your English is bad at all. Don't you speak English in Ireland?
Can anybody give more details on the branding issue?
Vorsprung said:
The answer should be yes to both questions. Once you've debranded your phone, it will not get "rebranded" (except if you flash it with a branded firmware). The generic firmware linked here is of course without any branding.
You could use the generic one, but you will lose the branding. I'm guessing you don't have a problem with that.
You're welcome! I'm not exactly experienced myself, so I don't guarantee that my answers are 100% accurate and correct...
I don't think your English is bad at all. Don't you speak English in Ireland?
Can anybody give more details on the branding issue?
Click to expand...
Click to collapse
Thanks a lot for the answers
hehe yes people in general speak English here in Ireland but lets not forget there are thousands of emigrants from around the world living here too, i am one of them
Can you please also write which generic firmware should i flash, UK, World or any other? (perhaps there is IE one?), and will it affect the frequency of getting future official updates from SE? (yes i want to get rid of Vodafone from my phone and stay with a 100% SE official firmware).
Thanks
Once you flash a generic firmware, future updates will all be generic updates as well.
Some of the plus points that I can see of having a generic firmware is that
a) updates are rolled out faster (as compared to branded firmware).
b) you get rid of a lot of junk that network providers seem to put in i.e. bloatware.
OK I am now on generic, unbranded Global International 1247-0875_R11C , of course 2.3.3, however I did not root my phone and used SEUS instead OTA.
Thanks a lot Vorsprung and others for help
I just flashed my Xperia Neo 2.3.2 global, applied Gingerbreak, and updated OTA to the last 2.3.3 firmware (4.0.A.2.368)
I confirm I kept root!
Kalram said:
I just flashed my Xperia Neo 2.3.2 global, applied Gingerbreak, and updated OTA to the last 2.3.3 firmware (4.0.A.2.368)
I confirm I kept root!
Click to expand...
Click to collapse
Same here
I follow this guide and got my Xperia Neo rooted! Thanks Vorsprung!!!
I wanted it root to install Google Talk with video! It works very well!
Now I want a way to unlock the bootloader, as I want to run Cyanogen mod
Ask the Admin for your own forum section about the Neo, all this OTA-root with the latest firmware just making me jealous.
flashmode
Hi guys!
well I just can follow till step 5. Opening the "X10FlashTool.exe" --> Click On flash. that's it. It tells me to enter the flash mode but how? I pressed&hold the menu button before plugging the usb cable onto my PC. Instead entering the flash mode it only starts charging my battery. Can somebody help ?
thanks a lot !
i was clicking the wrong button
I have rooted 2.3.2 (checked with rootchecker) but when I try to update OTA it says "Your phone already has the latest software".. Please help!!
Edit: Even says up to date using pc companion.
I have Alcatel OT-910, but i cant find anything about root & rom for this model here on xda-developers forum. I found threads for other Alcatel models (OT-908, OT-980, OT-990) and i was wondering is anyone working on this particular model? Is it possibile to have root access? stock ROM for OT-910? Thanks.
Alcatel OT-910
CPU 600 MHz
OS Android OS, v2.2 (Froyo)
Keyboard QWERTY
root
i have tried to root my OT-910 with SuperOneClick 2.3.3, but it doesn't work.
Keeps stuck at Step #7 Waiting for Device.
also tried to unplug and replug it at this part, but no chance.
any other ideas how to get root? Some of the installed apps are useless for me and eat up my memory, want to get rid of them
rooting problem
I've got OT910 too, tried several ways to root with steps, provided for other Alcatel android phones - no luck.
Try with different versions os superoneclick. Aso you should install Pdanet on your phone and your computer to and try again with superoneclick.
Sent from my ALCATEL one touch 990
No luck still
I tried all SuperOneClick releases, z4root, GingerBreak - nothing really works. The phone is hardly operable without root - too much garbage preinstalled.
Hey, i have an Alcatel OT-909a (which is the same as Alcatel OT-910 but with a lower px camera) and i also am unable to get root access, i already know that there is a stock busybox, and have seen some files of the internal memory but still not having luck, i also flashed some CWM and RA recoveries but i just got stuck while trying to access recovery, so i have to get back to stock recovery, i think there must be a way to do at least a nandroid backup and try to root the backup and flash again, but i dont know, the CWM recovery just boot the android logo, after there is nothing in the screen, but the QWERTY keys are on like if the phone was in recovery, i had tried Super One Click 1.9.2 and 2.3.3 and got stuck in step #7 too, zergRush and GingerBreak doesnt work also, something extrange for me is that the last time i try CWM, it didnt boot into recovery but into fastboot, as far as i know internal memory is read-only except for the installation of apps and some folders (or somehow i push GingerBreak and zergRush to the internal memory isn't?), i can't push su to the xbin or bin folders, but i already saw what is inside xbin an bin (as i said memory is read-only and there are some folders that requires permissions to access), there must be a way to push su to xbin folder (or at least maybe access su in another location?) but i still seeing how?
PD: sorry for my possible bad english speaking
PD2: yes i'm a noob and i hate myself but please some of you that know of this, help us?
Edit: just curious i just push su to "/data/local/tmp" then i just tipe ./su and it appeared on the phone "shell has been granted superuser permissions"
Alcatel_OT_909a /909s /910
OS: Android Gingerbread 2.3.4 / 6180
Kernel: 2.6.35.7-perf [email protected] #3
Here an idea: Custom Rom
hey guys, if some of you (someone, anyone who might wanna help?) are still maybe reading this thread, i wonder, i have played with the phone a little (unluckly i really messed up breaking the cellphone and luckily for me, the motherboard was replaced at service center), and i have been able to pull out most of the system partition, custpack and others, (except for the recovery partition) and i was wondering if maybe there is a way to create a custom rom with those files?, maybe we could create our custom rom and flash it, after seeing around the files, i got that 909a it's using what it's looks like at least the same kernel than ot910, (actually some information is from the ot910, in the manual it refers to ot909a-s ot910 as same cellphone but with different px in camera), so maybe we could create a custom GB rom based on the files from the stock system partition, and as alcatel has relased the kernel sourcecode maybe we could even do a custom kernel?, i was just wondering if someone can try to do a custom rom with those files, as i have tried flashing some GB roms replacing files and the phone doesn't boot up to android, but in recovery you get su access and pull the other files, but when replacing files, there is a moment when the system lose adb shell access, so maybe someone with more knowleadge (as i'm new to both android and linux) can help?
Rooting -- any news?
Has anyone succeeded in rooting the device in the meantime? I had no luck with either psneuter, zergrush, or gingerbreak ...
OT-910 successfully rooted!
Hi,
thank's to the great work of giantpune over at Phandroid, the Alcatel OT-910 has been successfully rooted (see the attached screenshot)!
For instructions, cf. the thread "Optimus Elite root with an apk" at Phandroid's LG Optimus Elite forum. Put in a nutshell, you have to install the following two APK's:
1. the Poot-debug.apk tailor-made for this phone, and
2. Ministro II.apk.
Both files are linked at the end of giantpune's original post at the LG Optimus Elite forum.
Note that Superuser, but not SuperSU, will grant root access on the OT-910.
Have fun!
Any Rom for OT 910
nolda said:
Hi,
thank's to the great work of giantpune over at Phandroid, the Alcatel OT-910 has been successfully rooted (see the attached screenshot)!
For instructions, cf. the thread "Optimus Elite root with an apk" at Phandroid's LG Optimus Elite forum. Put in a nutshell, you have to install the following two APK's:
1. the Poot-debug.apk tailor-made for this phone, and
2. Ministro II.apk.
Both files are linked at the end of giantpune's original post at the LG Optimus Elite forum.
Note that Superuser, but not SuperSU, will grant root access on the OT-910.
Have fun!
Click to expand...
Click to collapse
Can you please suggest any ROM for OT 910.
Help need...
Hi guys,
I need your help man, I had just rooted successfully and I don't know what have I done now it is just stuck at TCL logo and restarting.
please please please help...
May be flashing it solve the problem I have sent email to alcatel but they didn't have the rom so some one help me and also I had flash recovery but didn't back up original one so also give me that or any working CWM recovery.
plzzzzzzzzzzzzzzzz
my last hope is xda...
smkamranqadri said:
Hi guys,
I need your help man, I had just rooted successfully and I don't know what have I done now it is just stuck at TCL logo and restarting.
please please please help...
May be flashing it solve the problem I have sent email to alcatel but they didn't have the rom so some one help me and also I had flash recovery but didn't back up original one so also give me that or any working CWM recovery.
plzzzzzzzzzzzzzzzz
my last hope is xda...
Click to expand...
Click to collapse
If your last hope is xda... then maybe you will not have that much luck, if you're stuck at TCL logo, maybe you could try using the "OTU Upgrade Tool" (by means "OTU = Alcatel/TCL Flasher") and maybe that will do the trick and then you get your phone back to stock, if not (or if you already did that), then you're a little out of luck, as far as I know, there is no stock recovery around, and also as far as I know, there is no CWM recovery, now, in case you did use OTU Tool, and failed flashing the phone, then is almost sure that your nand is bricked, if you used OTU Tool and that didn't get your phone back, then you should see if you can still flash Android Images (more accurately 2.3.3 (since 2.3.4 did brick my phone twice)), at least with a non-functional 2.3.3 image, maybe you could flash from there with OTU again, or try to modify 2.3.3 system to work with your phone, if nothing of that did result for you, then you're out of luck, because I'm almost sure that would mean that you are in a nand brick, and the only way to solve it, is sending it to Service Repair (at least for now)
now, for using OTU Upgrade Tool, you can download it from TCL/Alcatel website ( www2.alcatelonetouch.com/global-en/support/download.html ) in the download section, select your phone model, and from there download the OTU Upgrade Tool, after downloading, install it and follow the instructions for getting the phone in "Download Mode" (in OT910 = (pressing "Q" key with the phone totally off, and after pressing the "Q" key for 30sec. or a minute, then (still pressing the "Q" key) connect it to the pc and follow the onscreen steps (that means, choosing your mobile and getting in to look for the firmware and download it)
I have a kind of "backup" of the system (I mean, every file that is in /system) but sadly, it doesn't have the properly permissions set, and so, it gives also a boot loop (also I bricked my phone once again and for worse, when it was out of warranty), so if you still in warranty maybe you should send it to service :/
that's the sad of life when your mobile is not the one that is being developed by expert developers (not even a beginner one )
Hope you can fix your phone
thanks for help
thanks man you are my captain...
I recheck the upgrade tool it just say that you have latest software.
So if you have 2.3.3 then please give me that i will update it via adb shell as i can still access it as su.
smkamranqadri said:
thanks man you are my captain...
I recheck the upgrade tool it just say that you have latest software.
So if you have 2.3.3 then please give me that i will update it via adb shell as i can still access it as su.
Click to expand...
Click to collapse
I will, but before, what version of upgrade tool are you using? (mine has a kind of strange bug that the rom is never ever able to get the last update (as always download saying there is a new update (it's a fake but anyway)), that would be kind of a problem since maybe after you flash 2.3.3 the upgrade tool will state that you're still in latest firmware (even through upgrade tool is supposed to be a service tool, funny isn't?), anyway, since you have nothing to lose (since apparently you flashed a custom recovery that didn't work for you), but, there are this two things you should try before, first (and pretty much the must obvious one) if you have warranty (as long as you're in warranty and never tried to see what's inside the phone), and two, there is a little possibility that maybe you can access adb via the recovery you flashed, even, when the tcl logo appears, try to do "adb shell" or "adb devices", so maybe you can recover your phone without the need of flashing android 2.3.3.
now, if nothing of that worked, then there is nothing to loose, if you have the android sdk, from there you can download a 2.3.3 image, that will boot, but display nothing in the screen (still you can do adb shell with su, and try to properly install libraries maybe?), if not, then i'll check if I can do one system image for you, and see what it does
by the way, if somehow you can access adb , try to do "adb pull" and pull the " /system" partition
it's really sad that we can't (at least not me) figure out, how to use the files that the upgrade tool uses ( 570mb of 10 - 520kb files)
Help me... alcatel 909
Azuruw said:
I will, but before, what version of upgrade tool are you using? (mine has a kind of strange bug that the rom is never ever able to get the last update (as always download saying there is a new update (it's a fake but anyway)), that would be kind of a problem since maybe after you flash 2.3.3 the upgrade tool will state that you're still in latest firmware (even through upgrade tool is supposed to be a service tool, funny isn't?), anyway, since you have nothing to lose (since apparently you flashed a custom recovery that didn't work for you), but, there are this two things you should try before, first (and pretty much the must obvious one) if you have warranty (as long as you're in warranty and never tried to see what's inside the phone), and two, there is a little possibility that maybe you can access adb via the recovery you flashed, even, when the tcl logo appears, try to do "adb shell" or "adb devices", so maybe you can recover your phone without the need of flashing android 2.3.3.
now, if nothing of that worked, then there is nothing to loose, if you have the android sdk, from there you can download a 2.3.3 image, that will boot, but display nothing in the screen (still you can do adb shell with su, and try to properly install libraries maybe?), if not, then i'll check if I can do one system image for you, and see what it does
by the way, if somehow you can access adb , try to do "adb pull" and pull the " /system" partition
it's really sad that we can't (at least not me) figure out, how to use the files that the upgrade tool uses ( 570mb of 10 - 520kb files)
Click to expand...
Click to collapse
First of all my update tool version is 1.2.0.10.
Second i got second hand set from local market at karachi, pakistan so no warranty where i exchange some email from alcatel support for rom but said that they didn't have.
third i can access adb shell with couple of reentering su i got super user so what to do to recover.
i will pull system partition and give you the link soon also downloading sdk for image.
thanks alot...
may we could chat live for better working. find me smkamranqadri at any platform except google kami.genius.
Got ROM/ RECOVERY
smkamranqadri said:
First of all my update tool version is 1.2.0.10.
Second i got second hand set from local market at karachi, pakistan so no warranty where i exchange some email from alcatel support for rom but said that they didn't have.
third i can access adb shell with couple of reentering su i got super user so what to do to recover.
i will pull system partition and give you the link soon also downloading sdk for image.
thanks alot...
may we could chat live for better working. find me smkamranqadri at any platform except google kami.genius.
Click to expand...
Click to collapse
I had got rom & recovery and every partions so any one need have do chat with me at fb - Muhammad Kamran qadri
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:
Gentlemen,
What apk should I use to root with success a Caterpillar :laugh: CAT S31 running Android Nougat 7.1.2 ?
In a first step, I would like to throw away all the G***** ecosystem.
In second step, I also would like to replace Nougat by LineAgeOS.
As LineAgeOS doesn't provide a firmware img for this mobile, it is realistic to choose an image from another mobile using same CPU (snapdragon 210) and same GPU ( Adreno 304) ?
Thanks for your help
SolidSnake
Also interested...
As I can't create new Threads and this one fits totally my needs I would like to continue here.
I am trying to change the OS of a friends phone from his Android 7.1.2 to LineageOS. I was able to successfully change my OS to Lineage on my HTC U11 and some other phones,
but I just can't do anything with the CAT S31 and can't unlock the phone at all. Tried rooting it with KingRoot, RootKHP Pro, ZYKURoot, iRoot and many others.
And I guess that is the main reason I get the following error when I try to flash TWRP:
Code:
UNKNOWN:~$ fastboot flash recovery ~/Downloads/twrp.img
target reported max download size of 262144000 bytes
sending 'recovery' (46312 KB)...
OKAY [ 1.536s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 1.537s
Possibly working rooting method
I found this on another forum:
A set of software for obtaining ROOT privileges.
Driver_Qualcom_m.7z (9.27 MB) [link]
Enter HS QDSLoad 9008 mode from Vol + and Vol- off state and connect without releasing to USB
MiracleBox [link]
The Boot image is processed on the phone by the Magisk manager, then uploaded to the phone using Miracle again from the computer.
MagiskManager-v7.3.2.apk (2.71 MB) [link]
Just in case,
Backup firmware without / Data partition [link]
Attached files
XposedInstaller_3.1.5-Magisk.apk (2.96 MB) [link]
Click to expand...
Click to collapse
But as I don't understand much of carriers on unlocking bootloaders and stuff, could anyone post more information about this method if anyone decides to follow it? That was from a user which says he got to root the phone and that's how they did it. Also the person doesn't talk about unlocking the bootloader, for example.
Just want to make sure it can be rooted before I buy it, because I won't buy a phone that can't be rooted and I'm having a hard time finding a good rugged phone that can be rooted...
EDIT: I've uploaded everything to a folder on my MediaFire account here: http://www.mediafire.com/folder/thqmkg68l2h2r. In case anyone tries this, please say here if it worked! Also, I can't link MiracleBox... They had a "special" version of it there and I think it's better for me to not link it... But search for MiracleBox on Google. You'll find it.
EDIT 2: I'm not into this anymore - from the moment I decided not to buy the phone (not too long after this comment). I'm leaving the link because people still download from it, so maybe it's useful. If it's not useful at all, someone please tell me and I'll delete it.
Wow... its really a tumbleweed here... i have decided not to purchase or use any smartphones whatsoever until it is possible to flash a ROM in this phone... but for some reason the developers are not interested and this is the only phone im interested in.. fml
dokha said:
Wow... its really a tumbleweed here... i have decided not to purchase or use any smartphones whatsoever until it is possible to flash a ROM in this phone... but for some reason the developers are not interested and this is the only phone im interested in.. fml
Click to expand...
Click to collapse
If you really want that to happen, I think you should try another phone.... I'm done with CAT phones. Only the more expensive ones can be rooted with 100% certainty - because there are tutorials about that and not just people saying how they did it in a random post like the one I found (and not all models, I think) -, and I don't remember about ROM flashing (didn't get to that - can't buy them, anyways, too expensive).
Perhaps you could try Blackview? I'm going for them. In my case, BV9500 (not Pro or Plus - but Plus is out of question because there's no root, I think). I think from now on, I'll try to always buy a MediaTek powered phone. As long as you have a ROM and the scatter file, your phone possibly won't brick. SP Flash Tool will save you. As it did with me various times (and I did everything that wasn't supposed to be done and still always worked xD - I only read about what shouldn't be done months after changing phone and getting it to work always). BV9500 has a MediaTek chipset, and a forum has ROMs for it. In any case, even if they hadn't, I can generate my own with SP Flash Tool and have a copy of the stock ROM that came with it, so if I brick it, I can restore it completely. Root seemed to be also to be possible, so I chose it. Gonna buy it when I can.
Sum up, if you want to be possible to flash ROMs of a phone, I'd say go for MediaTek powered devices. I'll try not to go away from them again, as I did with my One Plus X (even though I can flash ROMs on it, but I still trust MediaTek with SP Flash Tool more than others, since my experience with it was "do whatever you want, you can't brick anyways" (and I never did haha)). Can't be completely sure that still happens on newer MediaTek chipsets, but I guess I'll find out by myself if I ever do such stupid things again (after reading, not sure I will haha).
EDIT: You might also want to try RockChip powered phones. I have a tablet with a chipset from them and it's possible to flash partitions with a tool like with MediaTek chipsets with SP Flash Tool. So I'd go for one of those 2. I guess I'll only go for devices where I can flash partitions whenever I want, without having to unlock the bootloader first (less safe as anyone can do whatever they want if they steal the phone, but at least I can't brick them).
Thank You!
DADi590 said:
If you really want that to happen, I think you should try another phone.... I'm done with CAT phones. Only the more expensive ones can be rooted with 100% certainty - because there are tutorials about that and not just people saying how they did it in a random post like the one I found (and not all models, I think) -, and I don't remember about ROM flashing (didn't get to that - can't buy them, anyways, too expensive).
Perhaps you could try Blackview? I'm going for them. In my case, BV9500 (not Pro or Plus - but Plus is out of question because there's no root, I think). I think from now on, I'll try to always buy a MediaTek powered phone. As long as you have a ROM and the scatter file, your phone possibly won't brick. SP Flash Tool will save you. As it did with me various times (and I did everything that wasn't supposed to be done and still always worked xD - I only read about what shouldn't be done months after changing phone and getting it to work always). BV9500 has a MediaTek chipset, and a forum has ROMs for it. In any case, even if they hadn't, I can generate my own with MTK Droid Tool and have a copy of the stock ROM that came with it, so if I brick it, I can restore it completely. Root seemed to be also to be possible, so I chose it. Gonna buy it when I can.
Sum up, if you want to be possible to flash ROMs of a phone, I'd say go for MediaTek powered devices. I'll try not to go away from them again, as I did with my One Plus X (even though I can flash ROMs on it, but I still trust MediaTek with SP Flash Tool more than others, since my experience with it was "do whatever you want, you can't brick anyways" (and I never did haha). Can't be completely sure that still happens on newer MediaTek chipsets, but I guess I'll find out by myself if I ever do such stupid things again (after reading, not sure I will haha).
Click to expand...
Click to collapse
Wow.. thanks for this info Ive never heard of Blackview, definatley going to check them out, :highfive: hopefully I can find a phone no larger than 4.7 inches.. any more than that its just cumbersome for me..
@solidsnake6 @DADi590 any update on it? I've found this:
Install Android 10 on Cat S31 | RootBox Tools
This method teaches you How to install Android 10 on Cat S31, and it's safe, secured and easy to apply update to your smartphone.
rootboxtools.com
&
Cat S31 Root with SuperSU Using TWRP Recovery
On this page, we are going to share with you a guide on how to root your Cat S31 with SuperSU using TWRP or Custom Recovery.
www.mobilewithdrivers.com
kamolinkaaa said:
@solidsnake6 @DADi590 any update on it? I've found this:
Install Android 10 on Cat S31 | RootBox Tools
This method teaches you How to install Android 10 on Cat S31, and it's safe, secured and easy to apply update to your smartphone.
rootboxtools.com
&
Cat S31 Root with SuperSU Using TWRP Recovery
On this page, we are going to share with you a guide on how to root your Cat S31 with SuperSU using TWRP or Custom Recovery.
www.mobilewithdrivers.com
Click to expand...
Click to collapse
Just to say here, I'm not into this anymore haha. I was until I decided not to buy the phone. But I still left the link in case anyone would be interested in whatever I have there which I don't remember (and various seem to be interested, so I'm leaving it there).
That is FAKE. Do not install the APK, it is a program for you to download games and programs.
Hey everyone,
So! I bought a Sony Xperia 1 (J8110-2019) phone from someone on Facebook Marketplace at a very solid price of £250 (RRP is still £850 in the UK) due to the seller describing it as 'in retail demo mode' so they lowered the price. I jumped the gun thinking I was getting a solid deal and just stupidly assumed it to be a feature I could just disable with *#*#73556673*#*#- me believing I was some insane developer with mad coding skills where in realityI had once flashed and rooted my Xperia XZ back in 2016. [Insert 'Hackerman' meme]
Yes... I am fully aware I'm a complete idiot for not doing a full assessment on the phone and am now having to learn a very important lesson from this situation!!
It seems to have a Store Front firmware installed and unsure what firmware to download and flash? I've tried some of the official stock ROMs from XperiFirm and it just continues to boot into constant 10-second cycles of demo videos making general functionality like phone calls pretty much impossible. without interruption. I've tried Customized and UK Service Provider Firmware such as EE and O2 but it always goes back into Store mode.
I was hoping if anyone would have or could elaborate on how to make an executable system flash zip for a 2019 Xperia 1? When I extract files from XperiaFirm ROMS (FTF,ZIP,SIN etc), I don't seem to get any META-INF files and thus cant make the proper .zip that TWRP needs to successfully flash a new repacked stock ROM? It always ends in a boot loop."
Here are some key points to hopefully give you some background:
I've installed TWRP successfully and have attempted to use 3 official firmware to flash whilst in recovery but have been unsuccessful each time with 'Invalid .ZIP format'. I've only a few times got booted whilst bundling together FTF files via Flashtool and doing it that way round but only ever seems to solve half the problem
I can't use the SinExtract feature in Flashtools as the SIN file errors as not being supported yet to use different file versions.
I can't use PRFCreator as it errors as the FTF file being unsupported (Due to it being new I assume)
I attempted to create my own META-INF>Updater-script but am unable to identify what partition my phone would use for mounting on "/dev/block". I only ever seem to get MANIFEST.MF from the files and nothing else. On my XZ I think I used something like:
(package_extract_file("boot.img", "/dev/block/mmcblk0");
package_extract_file("system.sin","/dev/block/platform/msm_sdcc.1/by-name/system");
Click to expand...
Click to collapse
I have been able to install Magisk for rooting and verified.
I have used Minimal ADB and Fastboot to install programs like TWRP, SuperSu, Magisk but have never attempted, nor would I even know how to wipe my phone completely and install a clean stock ROM - is this possible?
All drivers, software, and systems are correct and up to date (as far as I am aware)
Would installing the' Service Exchange Firmware' be recommended (if I ever make it that far!) due to it being StoreFront?
I checked the IMEI number to see if it was blacklisted/blocked and it's all good. Not lost or stolen.
Thank you for your time to read and wallow in my woes with me my lovelies! Any help would be GREATLY appreciated you magnificent beasts! x
Bump x
...
the last chance... :good: