[Q] [halp] Unable to root Xperia Z Tab SGP311 - Xperia Tablet Z Q&A, Help & Troubleshooting

So I have attempted the method described at http://forum.xda-developers.com/showthread.php?t=2327473
I have been unanble to make ADB see my device... I have uninstalled ADB twice and tried two different versions. both Koush & and another one.
I have used a USBDeview to remove all USB android drivers from my computer (Sony, Samsung, HTC...) and still no joy.
In my windows device manager the device SGP311 is listed under "Other Devices" rather than under "Andoid Phone" as ADB should list it...
Basically running the EasyRootingToolkitV17 it does the following;
---------------------------------------------------------------
Easy Rooting toolkit (v17.0)
created by DooMLoRD
"pref_event exploit"
Credits go to all those involved in making this possible!
---------------------------------------------------------------
Special thanks to: the_laser, Bin4ry, fi01, hiikezoe, [NUT]
and to all those who are contributing to our git tree!
Sources: https://github.com/android-rooting-tools
---------------------------------------------------------------
[*] This script will:
(1) root ur device using the pref_event exploit
(2) install Busybox
(3) install SU files
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Developer Options)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Security)
(4) connect USB cable to PHONE and then connect to PC
(5) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
The system cannot find the path specified.
--- creating temporary directory
The system cannot find the path specified.
--- cleaning
The system cannot find the path specified.
--- pushing files
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
--- cleaning
The system cannot find the path specified.
--- Please wait device is now rebooting
The system cannot find the path specified.
ALL DONE!!!
Press any key to continue . . .
This is driving me insane as I would like to root my device... I dont have a spare computer to attempt this on.
Any advice from people who are more experienced with rooting devices and the way it works would be appreciated.
I have build number 10.1.C.0.370

Did you install the appropriate Sony Xperia Table Z driver for your device on your window PC?
http://developer.sonymobile.com/downloads/drivers/

safilo said:
Did you install the appropriate Sony Xperia Table Z driver for your device on your window PC?
Click to expand...
Click to collapse
thanks - that has now gotten my device correclty identified in my device manager but running the easy root now provides no different result....
Any other thoughts?

Related

lg optimus pro (c660) guide to root

hy
how root the lg optimus pro ?
need a guide thanks
1 º Download this suite of applications that I use (I added the zip original drivers from LG, which, with no specific model for this, worked like a charm):
www.megaupload.com/?d=U3L199Z3
2 Reset the phone manufactures (who have data to backup, use the File maneger Astro, for example), to obtain a clean file system Settings \ Privacy \ Reset factory data;
3 Extract the zip to a folder on your desktop and install the USB drivers, which are in the zip, the folder "USB driver";
4 Connect the phone to pc cable and expect drivers to be installed;
5 º Go to the pc start \ programs \ accessories \ command line;
6 After you open the command line type:
cd \
cd Users
cd (user name in question)
cd Desktop
cd (name of which are powered uncompressed zip files)
cd ADB
and the result is something like: C: \ Users \ (user name) \ Desktop \ Root Maximo LG Pro \ ADB
then enter the following commands:
adb devices (pressenter)
adb shell (press enter, and then the letter of the command line will pass to $)
echo 1> / data / local / lge_adb.conf (press enter)
7 After these commands inserted, turn off and then turn on the phone (very important this step), always with the phone connected by USB;
8 After restarting the phone, go to the folder where the files are downloaded and run the SuperOneClick.exe;
9 Select the method GingerBreak and click "ROOT"
10 When the process finishes (VERY IMPORTANT) make sure you turn off and turn it on again and update the application through the superuser Market.
That's it. Phone with root access.
Credits go to: Bruno Pinto @ AndroidPT
Hi,
I've tried as you say, and i jammed on the driver installation. Why? On the pack you've posted, there's only a shortcut to the driver file: LGUnitedMobileDriver_S4981MAN32AP22_ML_WHQL_Ver_3.2 - Atalho
and when clicking it its giving me a link to something that doesn't exist:
C:\Users\"username"\Desktop\LGUnitedMobileDriver_S4981MAN32AP22_ML_WHQL_Ver_3.2.exe
Even so, i'd already had installed the LG software suite and so i've got the driver so i moved to the next steps.
when going to perform the adb shell command (error: device not found), i tried with mass storage mode on and off and msg is always the same.
can you please help me?
thanks for any answer
That guide is so complicated for n00b like me who has never before used Android. The stock rom is awfull anyway, any hope for costum roms on this one?
Hi!!
After running the adb command line and restart the mobile, i've started the super one click, it started rooting and in the end in step 7 he says "Remounting /system with read-write access .... FAILED", what went wrong?
I have the latest drivers for this smart and the latest super one click v.2.1.1
My LG has the 2.3.4 version of android and it's from TMN
Regards
is it possible to unlock it? (for free preferably)
hugoafsilva said:
Hi,
I've tried as you say, and i jammed on the driver installation. Why? On the pack you've posted, there's only a shortcut to the driver file: LGUnitedMobileDriver_S4981MAN32AP22_ML_WHQL_Ver_3.2 - Atalho
and when clicking it its giving me a link to something that doesn't exist:
C:\Users\"username"\Desktop\LGUnitedMobileDriver_S4981MAN32AP22_ML_WHQL_Ver_3.2.exe
Even so, i'd already had installed the LG software suite and so i've got the driver so i moved to the next steps.
when going to perform the adb shell command (error: device not found), i tried with mass storage mode on and off and msg is always the same.
can you please help me?
thanks for any answer
Click to expand...
Click to collapse
the drivers are here: http://www.mediafire.com/?85wvjkp5ytb816y
This is NOT complicated method and it works great. I have also tried this on Optimus Net and works fine
Help..! Help..!
I have an LG-C660 Android Gingerbread 2.3.4
1 - Does anyone has an Android version fot this device..?
2 - After Root the device, it boots but dont´s shows the Desktop. It´s stucks on Carrier Screen
3 - Please Help me..!
I tried as instructions but the adb driver can't be successfully installed. I've tried installing drivers many times but it doesn't work.
Done! I removed the SD card and it worked finally!
i have a lg C660 from TMN with v2.3.4 i've tried and tried and cant make it work. anyone got it to work?
Edit :: with superoneclick v2.1.1 i get this
SuperOneClick v2.1.1.0
Checking drivers...
Killing ADB Server...
* server not running *
OK 0,10s
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK 4,14s
Waiting for device...
OK 0,08s
2.3.4
Getting manufacturer...
LGE
OK 0,02s
Getting model...
LG-C660
OK 0,03s
Getting version...
V10c-Aug-25-2011.2ED2FC6537
OK 0,03s
Checking if rooted...
False
OK 0,06s
Installing BusyBox (temporary)... - Step #1
2039 KB/s (1062992 bytes in 0.509s)
OK 0,59s
Installing BusyBox (temporary)... - Step #2
OK 0,03s
Rooting device... - Step #1
OK 0,02s
Rooting device... - Step #2
OK 0,03s
Rooting device... - Step #3
782 KB/s (16830 bytes in 0.021s)
OK 0,10s
Rooting device... - Step #4
OK 0,04s
Rooting device... - Step #5
OK 0,02s
Rooting device... - Step #6
[**] Gingerbreak/Honeybomb -- android 2.[2,3], 3.0 softbreak
[**] (C) 2010-2011 The Android Exploid Crew. All rights reserved.
[**] Kudos to jenzi, the #brownpants-party, the Open Source folks,
[**] Zynamics for ARM skills and Onkel Budi
[**] donate to [email protected] if you like
[**] Exploit may take a while!
[+] Plain Gingerbread mode!
[+] Found PT_DYNAMIC of size 232 (29 entries)
[+] Found GOT: 0x00014354
[+] Using device /devices/platform/msm_sdcc.1/mmc_host
[*] vold: 0000 GOT start: 0x00014354 GOT end: 0x00014394
OK 80,24s
Rooting device... - Step #7
OK 8,08s
Remounting /system with read-write access...
mount: Operation not permitted
FAILED ::
When you get the #6 step you have to disable and enable debug usb on the device..in this way it should work
Sent from my LG-C660 using Tapatalk
Sir i have tried the above procedure. But after "loading gingerbreak" nothing happens. i have waited for half hour.Please tell me what went wrong?
some body know how to get in recovery mode ´cuz i can root my c660 i have gingerbread 2.3.4
i have rooted my gf's phone and made a custom ROM for her i made it for her only !
Step 5 and Step 7 problem
EDIT:
Finally Done. I used SuperOneClick v2.2 and removed the SD card (only in settings) and on step five just disable and enable usb debugging. I feel like alchymist.
And now i am looking how i can custom default rom.
simmer14 said:
i have rooted my gf's phone and made a custom ROM for her i made it for her only !
Click to expand...
Click to collapse
sir kindly make one for us too.. we are sick of Stock ROM...
unabl to root every =time it gets strucked on step 7... somebody help me
Installed at last after 3 days hardwork :/ :/

[Q] Sony Tablet S ADB support

Has anybody got a Sony Tablet S being recognised by adb?
It seems to be blocked :-(
And yes, I have done all the usual enable USB debugging etc...
I can not use it for development :-(
---------- Post added at 12:56 PM ---------- Previous post was at 12:06 PM ----------
Managed to sort it myself
you need to cd to your .android folder (on a mac, this is ~/.android) and then type
echo 0x054c > adb_usb.ini
Where 0x054c is the vendor id for Sony (I got that by looking at the attached evices in the 'About this mac' preferences)
Now adb sees the device - woohoo
would this apply if i just wanted to use it to transfer music and such? I am not incredibly savy with coding but i tried to enable debugging and all that. I am justnot sure whats the problem.
No, the Android File Transfer program still works without this
Good to know it can be used to dev on. Anyone have any information on how to send data out using the IR blaster, I dont think there is support for it in the native android libraries from what I can see?
The following procedure has confirmed that ubuntu 11.04.
The following procedure has confirmed that ubuntu 11.04.
1. Enable debug mode for sony tablet S
2. Add line /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="054c", MODE="0666", GROUP="plugdev"
3. Change file mode
sudo chmod a+r /etc/udev/rules.d/51-android.rules
4. Add line idVendor to ~/.android/adb_usb.ini
0x054C
5. adb kill-server ; sudo adb start-server
6. finish!
Kaz Taguchi said:
The following procedure has confirmed that ubuntu 11.04.
1. Enable debug mode for sony tablet S
2. Add line /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="054c", MODE="0666", GROUP="plugdev"
3. Change file mode
sudo chmod a+r /etc/udev/rules.d/51-android.rules
4. Add line idVendor to ~/.android/adb_usb.ini
0x054C
5. adb kill-server ; sudo adb start-server
6. finish!
Click to expand...
Click to collapse
I don't seem to have that file
I had done all the other steps in order to mount the tablet and copy files over (which works great).
Does anyone have issues with Sony's Music player failing to update the database? Music appears in the native Music app correctly but nothing in the Sony one
Found a way on Windows!
With the help of the vendor ID from above and the following article on generic Tegra Tablets, was able to get it to show up on Windows!
(Copied from addictivetips)
1.You must have Android SDK installed before you can proceed. If you don’t have it already, proceed to our guide on what is ADB and how to install it. Make sure you download the Google USB Driver Package as well.
2.Open the google-usb_driver folder that you will find inside your Android SDK folder.
3.Open the android_winusb.inf file in notepad or any text editor to edit it.
4.Add these lines under [Google.NTx86] or [Google.NTamd64] depending on whether you are using 32 bit or 64 bit Windows. If unsure, it is safe to add these under both these sections. ;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
Don’t edit or replace any other text that is already there; just add these new lines and save the file.
5.Open a command prompt window and enter this command: echo 0x054C >> "%USERPROFILE%\.android\adb_usb.ini"
Note: this is where you have to use 0x054C instead of what is at the link, otherwise it wont work
Now your Android SDK drivers are configured to support any Nvidia Tegra based tablet. To be able to use ADB and other SDK tools with your device, you can proceed as follows:
1.On your tablet, go to Menu > Settings > Applications > Development and enable ‘USB Debugging’.
2.Connect your tablet to your PC via USB. You will get a notification that some drivers were not installed, which is OK for now.
3.Right-click ‘Computer’ and click ‘Manage’. Identify your device from the list, right-click it and click ‘Update Driver Software..’.
4.Choose to browse your computer for driver software and then select to pick from a list device drivers on your computer.
5.Choose to view all devices and click ‘Have Disk…’.
6.Browse to the google-usb_driver folder inside your Android SDK folder and select the android_winusb.inf file.
7.If you get any warnings prompts telling you that the driver might not be compatible, just choose to continue installing.
8.Once the drivers have been installed, you should be able to use ADB with your device.
9.To confirm that your device is recognized, launch a Command Prompt window and enter these commands: adb kill-server
adb start-server
adb devices
Also, using BRKs Transformer's instructions found a way to boot Tablet S into recovery: has reboot, update from ZIP and factory reset options
a) Hold down power and volume UP button
b) when SONY logo appears, release power button but keep pressing volume UP button
c) should load into recovery
This also gives us the MTP device driver, which I have been unable in finding/installing
No luck so far with Automated rooting tools, working hard to crack this awesome tablet!
Bojanglez said:
I don't seem to have that file
I had done all the other steps in order to mount the tablet and copy files over (which works great).
Does anyone have issues with Sony's Music player failing to update the database? Music appears in the native Music app correctly but nothing in the Sony one
Click to expand...
Click to collapse
Thanks Kaz Taguchi !!
Couldn't connect to my Sony..
It made me crazy..!
I was just forgotten the:
4. Add line idVendor to ~/.android/adb_usb.ini
0x054C
So i created the file:
touch ~/.android/adb_usb.ini
and echoed the line into the file.
Works lime a charm now.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
CaptainJack87 said:
With the help of the vendor ID from above and the following article on generic Tegra Tablets, was able to get it to show up on Windows!
(Copied from addictivetips)
1.You must have Android SDK installed before you can proceed. If you don’t have it already, proceed to our guide on what is ADB and how to install it. Make sure you download the Google USB Driver Package as well.
2.Open the google-usb_driver folder that you will find inside your Android SDK folder.
3.Open the android_winusb.inf file in notepad or any text editor to edit it.
4.Add these lines under [Google.NTx86] or [Google.NTamd64] depending on whether you are using 32 bit or 64 bit Windows. If unsure, it is safe to add these under both these sections. ;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
Don’t edit or replace any other text that is already there; just add these new lines and save the file.
5.Open a command prompt window and enter this command: echo 0x054C >> "%USERPROFILE%\.android\adb_usb.ini"
Note: this is where you have to use 0x054C instead of what is at the link, otherwise it wont work
Now your Android SDK drivers are configured to support any Nvidia Tegra based tablet. To be able to use ADB and other SDK tools with your device, you can proceed as follows:
1.On your tablet, go to Menu > Settings > Applications > Development and enable ‘USB Debugging’.
2.Connect your tablet to your PC via USB. You will get a notification that some drivers were not installed, which is OK for now.
3.Right-click ‘Computer’ and click ‘Manage’. Identify your device from the list, right-click it and click ‘Update Driver Software..’.
4.Choose to browse your computer for driver software and then select to pick from a list device drivers on your computer.
5.Choose to view all devices and click ‘Have Disk…’.
6.Browse to the google-usb_driver folder inside your Android SDK folder and select the android_winusb.inf file.
7.If you get any warnings prompts telling you that the driver might not be compatible, just choose to continue installing.
8.Once the drivers have been installed, you should be able to use ADB with your device.
9.To confirm that your device is recognized, launch a Command Prompt window and enter these commands: adb kill-server
adb start-server
adb devices
Also, using BRKs Transformer's instructions found a way to boot Tablet S into recovery: has reboot, update from ZIP and factory reset options
a) Hold down power and volume UP button
b) when SONY logo appears, release power button but keep pressing volume UP button
c) should load into recovery
This also gives us the MTP device driver, which I have been unable in finding/installing
No luck so far with Automated rooting tools, working hard to crack this awesome tablet!
Click to expand...
Click to collapse
Done loading packages.
Preparing to install archives
Downloading Google USB Driver package, revision 4
File not found: C:\Program Files (x86)\Android\android-sdk\temp\usb_driver_r04-windows.zip (Access is denied)
Done. Nothing was installed.
I tried downloading and installing
(Can't post links)Download: Android USB Drivers - Original (Firmware 1.0)
But when I try to install the drivers for the tablet through device manager it says:
The folder you specified doesn't contain compatible software... ...Windows for x64-based systems.
Apparently this driver is only for x86. But after googling "download Google USB Driver Package" that's all I can find.
Got it...
At least I was able to "enable it" through the USB port,
thanks to this exercise in frustration.
Alas no root screen cap still didn't work.
It flashes wildly and does nothing.
Anyone happen to know the proper command line in system variables for win 7 for adb should be?
I haven't used adb in forever, and I think alot of peoples issues with adb is in the fact they cannot use it outside of the android/android-sdk/platform-tools directory. As in you can just type adb shell, adb start-server, adb kill-server from the root dir. I had it set up before, but with a new comp now, and I forgot what it was before.
whats going wrong
i cant seem to get the device driver on my adb at all. no matter what i do i cant get the usb driver sorted. this is where i get stuck"
Please add 0x54c into .android/adb_usb.ini file under HOME directory by using following command from command prompt.
echo 0x54c >> %HOMEPATH%\.android\adb_usb.ini
home directory???? every time i try this from home directory i get nothing.
this is my problem.... i dont have this file or entry. what is the entry?????? o notpad doc??,
adb_usb.ini file was missing the 0x54c entry! <<< what is this. a screen shot goes a loooong way.
Adb was simple with my x10 and sgs2 but man this is giving me the ****s.
can someone please post a few simple screenshots of what directory is supposed to be where please?
---------- Post added at 08:39 AM ---------- Previous post was at 08:21 AM ----------
what does this mean?
Thanks Kaz Taguchi !!
Couldn't connect to my Sony..
It made me crazy..!
I was just forgotten the:
4. Add line idVendor to ~/.android/adb_usb.ini
0x054C
So i created the file:
touch ~/.android/adb_usb.ini
and echoed the line into the file
?????????
I've created an automated ADB driver installer for the Sony tablets.
No more messy, time-consuming SDK install.
http://forum.xda-developers.com/showthread.php?t=1488822
Official Sony instructions
Looks like Sony has posted official instructions for setting up ADB with the Tablet S:
esupport.sony.com/US/perl/support-info.pl?info_id=878
After following their instructions I still had to go to Device Manager, choose to Update the driver for my tablet, and point it to the SDK/usb_driver folder. After that it works great.
debug
Hey guys i have installed the android sdk and the sony s drivers from the official site as dreadengineer posted. but after run the adb devices command i was unable to saw my device.
After that i tried the automated installations that BluechipJ posted, but the result was the same i cannot see the devices neither on eclipse or adb devices command.
i want to debug my application on this device but i could not access it. Can someone help me.
I have a windows 7 x64 OS. i'm able to debug on htc phone and also on the super slower emulator

Rooting XPU with errors Help :0 ICS

I tried rooting XPU ST25a firmware with CMD admin power.
Please advice.
Code:
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (02.10.2012) v13 =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
.
Normal Mode enabled!
Could Not Find C:\Windows\system32\build.prop
The system cannot find the path specified.
Pushing busybox....
The system cannot find the path specified.
Pushing su binary ....
The system cannot find the path specified.
Pushing Superuser app
The system cannot find the path specified.
Making busybox runable ...
The system cannot find the path specified.
The system cannot find the path specified.
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Running ...
The system cannot find the path specified.
Successful, going to reboot your device!
The system cannot find the path specified.
Waiting for device to show up again....
The system cannot find the path specified.
Going to copy files to it's place
The system cannot find the path specified.
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Press any key to continue . . .
looks like u didn't extract the zip and tried to run the bat file directly
lee480 said:
I tried rooting XPU ST25a firmware with CMD admin power.
Please advice.
Code:
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (02.10.2012) v13 =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
.
Normal Mode enabled!
Could Not Find C:\Windows\system32\build.prop
The system cannot find the path specified.
Pushing busybox....
The system cannot find the path specified.
Pushing su binary ....
The system cannot find the path specified.
Pushing Superuser app
The system cannot find the path specified.
Making busybox runable ...
The system cannot find the path specified.
The system cannot find the path specified.
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Running ...
The system cannot find the path specified.
Successful, going to reboot your device!
The system cannot find the path specified.
Waiting for device to show up again....
The system cannot find the path specified.
Going to copy files to it's place
The system cannot find the path specified.
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Press any key to continue . . .
Click to expand...
Click to collapse
Ok i have the very same problem and I have extracted the file . . . .am i missing drivers or something? and how do i get them?
chewdaniel said:
looks like u didn't extract the zip and tried to run the bat file directly
Click to expand...
Click to collapse
I did extract the zip
i have the same problem and i've solved that.
just copy the file (stuff, RunMe.bat, etc) in the folder, change the name of the folder to something else like 'root' or something you like, and copy the folder C: directory on your PC.
and then open command prompt, just type cmd start > search if u in windows 7
and in command prompt type cd C:\root
and then type RunMe.bat
and just following the instructions how to root our XU.
sorry for my bad english
Xperia Sola wont Root!
Hi!
I get the the error after the device reboots which reads something as:
mount: access denied are you root?
End result, no root and no Superuser.
Device: MT27i
Android: 4.0.4
Software Version: 6.1.1.B.1.54
I have not installed any additional drivers on my Windows 7 PC, but Sony PC Companion is installed.
Please help.
Regards,
sunshinekhan
I had same issue so simply revert back to .10 firmware.
.54 is not supported atm if I am not wrong.
Xperia Sola wont Root!
azfar said:
I had same issue so simply revert back to .10 firmware.
.54 is not supported atm if I am not wrong.
Click to expand...
Click to collapse
Thanks for the reply azfar!
Can you update to .54 after root? I believe not!
Is there a revert feature in the PC companion?
Also can you please provide your feedback here for the devs to know, because I can't with my current post count:
http://forum.xda-developers.com/showthread.php?t=1916702
You cant root .54 firmware with this or anything
You need to flash kernel of B.10 first then root and then flash .54 Kernel afain
Get C here Better than B.54
http://forum.xda-developers.com/showpost.php?p=35339192&postcount=173

[Q] Unable to root Xperia Mini Pro SK17i ICS 4.0.4 - x.587

Dear All,
Wherever i try to root my mobile through DooMLoRD_v1_Xperia-2011-ICS-ROOT-emu-busybox-su
I am getting below error:
---------------------------------------------------------------
Xperia 2011 ICS Easy Rooting toolkit (v1.0)
created by DooMLoRD
"andorid emulator" trick
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using "andorid emulator" trick
(2) install Busybox (1.18.4)
(3) install SU files (ICS specific)
(4) do some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Developer Options\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Security)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
--- symlinking tmp directory
failed on '/data/local/tmp' - Permission denied
link failed File exists
--- Rebooting
--- WAITING FOR DEVICE TO RECONNECT
--- PLEASE WAIT, THIS MAY TAKE A WHILE
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- enabling emulator hack
/system/bin/sh: cannot create /data/local.prop: Permission denied
--- Rebooting
--- WAITING FOR DEVICE TO RECONNECT
--- PLEASE WAIT, THIS MAY TAKE A WHILE
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
----------------------------------------------------------------------------------------------------------------------
It seems there is some access problem (Permission denied) please suggest me how to rectify the same.
Try this: http://forum.xda-developers.com/showthread.php?t=803682
You need 562 kernel. Use one of the sticky thread for rooting. There you will find a link to Sony mobile website and follow the instructions
Sent from Sony Xperia Live with Walkman
Follow here:
http://talk.sonymobile.com/thread/41119?start=0&tstart=0
Rooting problem
i tried all methods to root xperia mini pro ......bt stilill i cant........trying for last 1 month................help :crying:
HEMEN TALUKDAR said:
i tried all methods to root xperia mini pro ......bt stilill i cant........trying for last 1 month................help :crying:
Click to expand...
Click to collapse
Follow my guide
gb for gingerbread
and ics for ice cread sandwich
http://forum.xda-developers.com/showthread.php?p=43897224

[Q] How to fix edit of platform.xml gone wrong on Note3 SM-N9005?

I did a search and have found similar threads. However, people seem to have been intelligent and back up stuff or installed recovery apps before screwing around with their phones. I did not.
I have a Samsung Note3. Kit Kat 4.4.2 installed OTA once I had it up and running. I rooted it. However, the version of Kit-kat has a famous issue in that it would not allow apps to write to the SD card. I found a site with manual instructions to edit the platform.xml to overcome this issue. The site is as below:
winaero.com/blog/unlock-external-sd-card-writing-for-all-apps-in-android-4-4-kitkat/
However, something went awry after rebooting. I could not see anything on my SD card and I was unable to edit the platform.xml. A solution seemed to be to flash the ROM (using ODIN 3.07). I did this and currently have Baseband version N9005XXUENB1 and Build Number KOT49H.N9005XXUENB7
However, the still has lots of issues. I can stick in a password on wifi and connect to the network but it does not actually communicate with the internet. The H with up and down arrows appears for 3g connectivitiy but also does not work. Bluetooth does not work. Youtube has stopped working errors are common. I am unable to install any apps as cannot use play store, etc. I have pictures and mp3s on my SD card but gallery comes up empty as does music app. The only "file explorer" I seem to have is "my files" app. It comes up as empty (although it shows Total storage available for both SD memory and device storage as using 25/32 and 22/29 respectively.
I am guessing that flashing the ROM did not remedy the corrupt platform.xml in the permissions folder. I think the folder path was etc/permission/platform.xml although am not an expert with android. I was hoping someone might be able to give me a solution to fix the issue. Preferably a completely fresh and clean wipe type solution. Although as I am a "newbie" the greater the simplicity of the solution the better.
Apologies for the length of this issue!
T
laconical said:
I did a search and have found similar threads. However, people seem to have been intelligent and back up stuff or installed recovery apps before screwing around with their phones. I did not.
I have a Samsung Note3. Kit Kat 4.4.2 installed OTA once I had it up and running. I rooted it. However, the version of Kit-kat has a famous issue in that it would not allow apps to write to the SD card. I found a site with manual instructions to edit the platform.xml to overcome this issue. The site is as below:
winaero.com/blog/unlock-external-sd-card-writing-for-all-apps-in-android-4-4-kitkat/
However, something went awry after rebooting. I could not see anything on my SD card and I was unable to edit the platform.xml. A solution seemed to be to flash the ROM (using ODIN 3.07). I did this and currently have Baseband version N9005XXUENB1 and Build Number KOT49H.N9005XXUENB7
However, the still has lots of issues. I can stick in a password on wifi and connect to the network but it does not actually communicate with the internet. The H with up and down arrows appears for 3g connectivitiy but also does not work. Bluetooth does not work. Youtube has stopped working errors are common. I am unable to install any apps as cannot use play store, etc. I have pictures and mp3s on my SD card but gallery comes up empty as does music app. The only "file explorer" I seem to have is "my files" app. It comes up as empty (although it shows Total storage available for both SD memory and device storage as using 25/32 and 22/29 respectively.
I am guessing that flashing the ROM did not remedy the corrupt platform.xml in the permissions folder. I think the folder path was etc/permission/platform.xml although am not an expert with android. I was hoping someone might be able to give me a solution to fix the issue. Preferably a completely fresh and clean wipe type solution. Although as I am a "newbie" the greater the simplicity of the solution the better.
Apologies for the length of this issue!
T
Click to expand...
Click to collapse
Sounds like a bit of a pickle. Since you know that Odin is working and the firmware you have at least flashes correctly, I'd consider installing a custom recovery, backing up EFS folder (and the rom too, just in case there is some weird issue with Odin the 2nd time around) , then wipe everything - /system included. This will make your phone not be able to boot up at all because it will wipe the OS off. Then just boot directly to Download and redo the firmware flash. Something else to consider since you do have the international version, is that some of the firmwares you install might be more carrier or region specific, so there might be a better option to install. I know that there is a some slightly newer version that has NC2 in it as I was trying to fix one of these phones the other day that could not register on any network and ran across that build. Do you remember the build number of the software before you started modding?
Hello. Thanks for the reply.
I am going to ask what are probably very obvious questions but I am a little out of my depth.
1) What does installing a custom recovery involve?
2)How would I backup the EFS directory? When I had ES file explorer I would have been able to try and find it. However, as it is I do not know how to find the directory and back it up. I have connected the phone to a windows laptop and it shows up as note3 but there are no folders or files visible in either the phone or on the card.
3) What is the procedure to "wipe everything"?
I think the final part I know how to do with ODIN. Just go to download boot and load and run odin with the ROM.
I got the BTU ROM is that not for the UK? I tried looking up what NC2 was but did not really find anything the explained what it is.
Thanks again and sorry for the ignorance on my side.
Let's put the custom recovery and all that on the back burner for now.
Was your phone unlocked from the factory or did you get it from a carrier? If from a carrier, which, and is it unlocked now or you are still using it with the original carrier? This one is for Vodaphone http://www.sammobile.com/firmwares/3/?download=27401 but if you are unlocked, it should work anyway, I believe.
Thanks to the people for their replies. I managed to solve the issue as below.
As mentioned previously I had flashed using ODIN and BTU version of N9005XXUENB7. The only other thing that was then required was to enter the recovery (I think power + volume up + home and then release power once samsung name appears). I then selected wipe data/factory. A reboot later and everything was solved.
es0tericcha0s said:
Sounds like a bit of a pickle. Since you know that Odin is working and the firmware you have at least flashes correctly, I'd consider installing a custom recovery, backing up EFS folder (and the rom too, just in case there is some weird issue with Odin the 2nd time around) , then wipe everything - /system included. This will make your phone not be able to boot up at all because it will wipe the OS off. Then just boot directly to Download and redo the firmware flash. Something else to consider since you do have the international version, is that some of the firmwares you install might be more carrier or region specific, so there might be a better option to install. I know that there is a some slightly newer version that has NC2 in it as I was trying to fix one of these phones the other day that could not register on any network and ran across that build. Do you remember the build number of the software before you started modding?
Click to expand...
Click to collapse
Hi, The other day i tried to fix the Platform.xml. on my S5. i noticed sometime after that when i move files using the "My files" app, the phone would not refresh the files so that they would show up in gallery, videos etc.. I tried to undo the Media_rw by using SD Maid to find the Platform.xml and Axel to rewrite the Xml. In the platform.xml. i deleted the Media_rw and replaced the old xml with the old (original) one. I rebooted my phone. On swiping to open the screen i noticed alot of apps crashing one after the other. I when back to SD Maid and searched for Platform.xml and opened it with Axel but it said file not found.. i can not use the internet, i cant use most apps, i cant even use the Kies on my computer. I cant save anything to the storage either. I really need help. Odin is the only thing i can use. but i dont know how i can reset the xml files on my phone.. What exactly am i do to?
please
christaph3r said:
Hi, The other day i tried to fix the Platform.xml. on my S5. i noticed sometime after that when i move files using the "My files" app, the phone would not refresh the files so that they would show up in gallery, videos etc.. I tried to undo the Media_rw by using SD Maid to find the Platform.xml and Axel to rewrite the Xml. In the platform.xml. i deleted the Media_rw and replaced the old xml with the old (original) one. I rebooted my phone. On swiping to open the screen i noticed alot of apps crashing one after the other. I when back to SD Maid and searched for Platform.xml and opened it with Axel but it said file not found.. i can not use the internet, i cant use most apps, i cant even use the Kies on my computer. I cant save anything to the storage either. I really need help. Odin is the only thing i can use. but i dont know how i can reset the xml files on my phone.. What exactly am i do to?
please
Click to expand...
Click to collapse
Hey, I was wondering if you ever got a fix on this without factory reset. I am having the exact same issue.
Same boat here. Please someone help!
woahs said:
Hey, I was wondering if you ever got a fix on this without factory reset. I am having the exact same issue.
Click to expand...
Click to collapse
I am having exact same problem. After editing the platform.xml, my Note 3 is behaving the same way: no access to any storage area (including USB drive), no remote access/online access (even though WIFI and 4G appear to connect just fine), most apps fail with 'Unfortunately ... has stopped' error message, no Google Play...
I really don't want to do a factory reset, but really, does it even help? Is there a way to put the platform.xml back? Is there a way to access the phone via USB cable?
vbcomer said:
I am having exact same problem. After editing the platform.xml, my Note 3 is behaving the same way: no access to any storage area (including USB drive), no remote access/online access (even though WIFI and 4G appear to connect just fine), most apps fail with 'Unfortunately ... has stopped' error message, no Google Play...
I really don't want to do a factory reset, but really, does it even help? Is there a way to put the platform.xml back? Is there a way to access the phone via USB cable?
Click to expand...
Click to collapse
Update: I went ahead and successfully install the all-in-one file to the phone via Odin, but it still has the same issues. Can someone give a hint? thanks
FIX!!!
Hi I'm a god at searching(hence the Go)but an Noob(hence the obie) to Dev on Android but a computer techy(in other words I fix computers upgrade ETC.) Now if you followed EXACT instructions you SHOULD have the Backup copy of platform.xml. If not reply and I'll give those instructions.
So I did the same as this post did to get my issue as well but there's a SOLUTION I just found W/o getting rid of your loved files and its easy!
1. Download the ADB also included in The Android SDK by Google (approx. 3XX MB)
2. DOWNLOAD Root Explorer.APK
3. Extract ADB Dev kit( name should be roughly adt-bundle-windows-x86_64-20140702.zip)Note: I prefered it at C:\Android it avoided Name too long error
4. Open CMD Type: cd C:\<location ADB was extracted>\sdk\platform-tools(if you followed my note it will be "C:\Android\adt-bundle-windows-x86_64-20140702\sdk\platform-tools") and press enter... HINT TO COPY PASTE IN CMD RIGHT CLICK SAVES TIME!!!!
5. Install Root Explorer so you can backup your files(if any) I was unlucky having none on the phone but SD storage is ok!
To do this type ADB INSTALL <Location of Root explorer.exe> For standard windows users with default download locations it would be "C:\Users\<USER NAME>\Downloads\Root Explorer v3.1.9.apk" <COPY PASTE
6. Copy the original back to System>ETC>Permissions and overwrite
7. Factory reset!
Links?
sorry guys bt i have the same note 3 and i delete the platform.xml file .....i did a factory reset bt nothing happened ...can u help plz
Re:FIX!
But you have to set the permissions of platform.xml as 0777.Right?
Step 5 how should it works
Android Goobie said:
Hi I'm a god at searching(hence the Go)but an Noob(hence the obie) to Dev on Android but a computer techy(in other words I fix computers upgrade ETC.) Now if you followed EXACT instructions you SHOULD have the Backup copy of platform.xml. If not reply and I'll give those instructions.
So I did the same as this post did to get my issue as well but there's a SOLUTION I just found W/o getting rid of your loved files and its easy!
1. Download the ADB also included in The Android SDK by Google (approx. 3XX MB)
2. DOWNLOAD Root Explorer.APK
3. Extract ADB Dev kit( name should be roughly adt-bundle-windows-x86_64-20140702.zip)Note: I prefered it at C:\Android it avoided Name too long error
4. Open CMD Type: cd C:\<location ADB was extracted>\sdk\platform-tools(if you followed my note it will be "C:\Android\adt-bundle-windows-x86_64-20140702\sdk\platform-tools") and press enter... HINT TO COPY PASTE IN CMD RIGHT CLICK SAVES TIME!!!!
5. Install Root Explorer so you can backup your files(if any) I was unlucky having none on the phone but SD storage is ok!
To do this type ADB INSTALL <Location of Root explorer.exe> For standard windows users with default download locations it would be "C:\Users\<USER NAME>\Downloads\Root Explorer v3.1.9.apk" <COPY PASTE
6. Copy the original back to System>ETC>Permissions and overwrite
7. Factory reset!
Links?
Click to expand...
Click to collapse
Hi have next message in the install root step could you help me please
Android Debug Bridge version 1.0.31
-a - directs adb to listen on all interfaces for a connection
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <specific device> - directs command to the device or emulator with
the given
serial number or qualifier. Overrides ANDROID_SERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
-H - Name of adb server host (default: localhost)
-P - Port of adb server (default: 5037)
devices [-l] - list all connected devices
('-l' will also list device qualifiers)
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devices.
device commands:
adb push [-p] <local> <remote>
- copy file/dir to device
('-p' to display the transfer progress)
adb pull [-p] [-a] <remote> [<local>]
- copy file/dir from device
('-p' to display the transfer progress)
('-a' means copy timestamp and mode) adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward --list - list all forward socket connections.
the format is a list of lines with the followin
g format:
<serial> " " <local> " " <remote> "\n" adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only) adb forward --no-rebind <local> <remote>
- same as 'adb forward <local> <remote>' but fails
if <local> is already forwarded
adb forward --remove <local> - remove a specific forward socket connection
adb forward --remove-all - remove all forward socket connections
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-d] [-s] [--algo <algorithm name> --key <hex-encoded ke
y> --iv <hex-encoded iv>] <file>
- push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
('-d' means allow version code downgrade)
('-s' means install on SD card instead of inter
nal storage)
('--algo', '--key', and '--iv' mean the file is
encrypted already)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-obb|-noobb] [-shared|-noshared] [-all]
[-system|-nosystem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is written
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks themselves
in the archive; the default is noapk.)
(-obb|-noobb enable/disable backup of any installed apk expansion
(aka .obb) files associated with each application; the default is noobb.)
(-shared|-noshared enable/disable backup of the device's
shared storage / SD card contents; the default is noshared.)
(-all means to back up all installed applications)
(-system|-nosystem toggles whether -all automatically includes
system applications; the default is to include system apps)
(<packages...> is the list of applications to be backed up. If
the -all or -shared flags are passed, then the package
list is optional. Applications explicitly given on the
command line will be included even if -nosystem would
ordinarily cause them to be omitted.) adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb get-devpath - prints: <device-path>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1 [parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be updated.
- If it is "system" or "data", only the corresponding partition is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list of the following values
1 or all, adb, sockets, packets, rwx, usb, sync, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes priority over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these debug tags are printed.

Categories

Resources