Database Users

[Q] Rooting still possible after using the OTA update to froyo?

I am using an unrooted stock HTC rom (2.03) and am planning to use the OTA to upgrade to Froyo when it comes out.
From what I understand, the only way to root the legend now is to downgrade to 1.3x. Will the downgrade method still work after I use the OTA update? I don't really see the need for rooting for now, but if using the OTA update will make rooting impossible in the future, I will root it now and flash a prerooted froyo sense rom.
Anyone tried downgrading after using the OTA froyo upgrade?

Yes, Paul @ MoDaCo has already done it have a look on his legend.modaco.com forum.

- Follow this guide to the end (the last stage will appear to have failed)
- Temproot with VISIONary r13 (install the downloaded file as per a normal APK)
- Once you are temprooted, connect via 'adb' and do 'su' (to get root) then '/data/local/flash_image misc /data/local/misc1-2.img'
You should then be able to downgrade in the normal way.
Click to expand...
Click to collapse
Paul has mentioned 3 steps..I did not understand the third step..can someone explain third point?
connect via adb then su then...on that path what to do?

TheLegendaryJay said:
Yes, Paul @ MoDaCo has already done it have a look on his legend.modaco.com forum.
Click to expand...
Click to collapse
Thanks. I ended up rooting before the upgrade since I can't wait anymore for the unbranded OTA.

oh dear...
zabaknilesh said:
Paul has mentioned 3 steps..I did not understand the third step..can someone explain third point?
connect via adb then su then...on that path what to do?
Click to expand...
Click to collapse
If you don't understand, maybe you shouldn't be doing it? I'm not being nasty, it's a dangerous thing to do and there is a possibility of bricking your phone.
If your phone dies, it's not Paul's or my fault, you decided to do it
I read it as saying:
Connect your phone to your PC, where you have setup ADB and have your drivers installed etc.
Open a command prompt and CD to where you have the SDK\tools installed, for example c:\sdk\tools.
type: adb devices
You should get, to confirm ADB can talk to your phone:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT06PNX00270 device
It MUST list a device, otherwise the rest won't work.
Then type: adb shell
Which will then give you a $
Then type: su
then copy and paste the next line into notepad as to not copy any odd characters (although there shouldn't be any it's better to play it safe), then copy and paste it from there into the command prompt and press enter:
/data/local/flash_image misc /data/local/misc1-2.img
In theory that's it.

Thanks..for making a noobs guide for downgrading..now i know... ....

[Q] How can i connect adb drivers and ics 3.1 on xp?

Hi, do you know? How can i connect adb drivers and ideos x5 on xp?
I did try some drivers but in device manager, in other device "android" but all drivers not runing. I want to runing on sdk and sent log dzo.
thanks for helps,

miskiab said:
Hi, do you know? How can i connect adb drivers and ideos x5 on xp?
I did try some drivers but in device manager, in other device "android" but all drivers not runing. I want to runing on sdk and sent log dzo.
thanks for helps,
Click to expand...
Click to collapse
you have to use the adb drivers for ics, now I have the link here. But you can report an error like this:
(1) Open the Terminal Emulator
Write to SU and Enter.
(2) Write the following commands:
cat /proc/kmsg > /sdcard/dmesg.log
logcat > /sdcard/CAT.log

Aurora ICS ADB drivers: http://forum.xda-developers.com/showthread.php?t=1566393

I just it but not solved this problem
asm19 said:
Aurora ICS ADB drivers: http://forum.xda-developers.com/showthread.php?t=1566393
Click to expand...
Click to collapse
hi, thanks for answered my question. But i just tried:
AndroidDriverForPc
Adb Device for AURORA
Huawei_U8800_ICS_ADB_Driver
usb_dirver4
Universal_Naked_Driver_Beta_0.6.2
and orjinal huawei drivers with hisuite.

How can i did it?
asm19 said:
you have to use the adb drivers for ics, now I have the link here. But you can report an error like this:
(1) Open the Terminal Emulator
Write to SU and Enter.
(2) Write the following commands:
cat /proc/kmsg > /sdcard/dmesg.log
logcat > /sdcard/CAT.log
Click to expand...
Click to collapse
edit// "you have to use the adb drivers for ics" I don't have adb drivers. Just i wanting it.
I think this commands for linux, right? Can i it any linux version?
i using this commands what will happen? ( i want learn)
thanks.

any idea?
Is there no one with a different suggestion?

Please give a try to this solution.

m!xal!s said:
Please give a try to this solution.
Click to expand...
Click to collapse
Yes, its ok, adb driver seen by xp but when i can adb shell;
* deamon not runing. starting it now *
* deamon started successfully *
error: device not found
writing, what can i for it?

strange problem!!
device not found

[how to] remove your "tampered" banner

this thread is for m7. it will not work on m8. please check the general section of your device forums if you do NOT have m7
if you have recently s-off'ed using a java card,or some other exploit that did not remove your tampered banner from the bootloader screen,then this thread is for you.
you do NOT need to downgrade your hboot. this simple adb command works without any scary hboot downgrades.
*you must be s off.
*you must have superuser installed(see this thread if you need help installing superuser)
read this:
this will not work if your s on
the usual disclaimers:
i have tested this my my m7_ul t mobile variant,but use this info at your own risk. if it melts your phone into a little pile of aluminum goo,its not my fault.
credits
-beaups for giving me the echo comand,so yall didnt need to dump,edit with a hex editor,and copy back
-andybones for testing it on m7_wlv
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb
-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:
cd c:\miniadb_m7
your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)
-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,then enter this command:
adb reboot bootloader
this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.
now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot
and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Click to expand...
Click to collapse
this process,in your cmd window,should look something like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
2)reset your "tampered flag"
enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify tamered is gone
other useful threads:
how to lock/unlock your bootloader without htcdev(s-off required)
if this does not work for you
*first reread this thread in its entirety. make sure you have met the prerequisites,and double check your code and make sure you have not forgotten a step,or screwed something up trying to type it (especially if using a terminal emulator),and check that you have not gotten any errors.
if youre still confident you did things correctly,you need to PM me:
1)the results of: fastboot getvar all
2)a link to an uploaded p7.
you get fastboot getvar all by:
-place phone in fastboot
-enter in fastboot getvar all right click,click mark,highlight in white,hit enter or right click to copy
you dump p7 by:
adb shell
su (if needed to get a #)
dd if=/dev/block/mmcblk0p7 of=/sdcard/mmcblk0p7
transfer the file on internal storage to your pc and upload it
im not trying to be a ****,but its not helpful to post "didnt work" if you screwed something up,or if your not willing to help find a solution. especially if others have found it to work on their same variant.
important:
from now on,i will need a copy of your cmd window as well if we want to get to the bottom of whats happening. some folks seem to be simply writing extra bytes,wich is screwing up the flag location. please make sure this shows an entire session,not just a last part where it looks correct. we cant figure it out if you only show part of what you did.

mine

or you can use revone

zaphodbeeb said:
or you can use revone
Click to expand...
Click to collapse
it is my understanding that revone does not work on hboots greater than 1.44,so you need to downgrade hboot to have that option.
use whatever means you wish,this is another way to skin the cat.

scotty1223 said:
it is my understanding that revone does not work on hboots greater than 1.44,so you need to downgrade hboot to have that option.
use whatever means you wish,this is another way to skin the cat.
Click to expand...
Click to collapse
I can use revone to do this also on 1.54 without a problem. This method is much easier however, and leaves no tracks. Any chance of a script to do this. More Kudos 2 u.

is it possible to do the same with the "Locked" "Relocked" ?

russel5 said:
is it possible to do the same with the "Locked" "Relocked" ?
Click to expand...
Click to collapse
It should, since the lock state is also part of the misc partition. it is just a different offset.
Can someone who has unlocked or relocked state provide me with a dump of mmcblk0p7 ?

russel5 said:
is it possible to do the same with the "Locked" "Relocked" ?
Click to expand...
Click to collapse
Yes. There is a thread for that here , and in the verizon and sprint forums
Sent from my HTC One VX using Tapatalk

theq86 said:
It should, since the lock state is also part of the misc partition. it is just a different offset.
Can someone who has unlocked or relocked state provide me with a dump of mmcblk0p7 ?
Click to expand...
Click to collapse
The lock flag is in p3, not p7. Again, there is a thread for that already
Sent from my HTC One VX using Tapatalk

wooow its cool :laugh: :good:
I will do it when i get s-off
scotty1223 said:
Yes. There is a thread for that here , and in the verizon and sprint forums
Sent from my HTC One VX using Tapatalk
Click to expand...
Click to collapse
can you give me the link for this thread pleace ?

killer18 said:
wooow its cool :laugh: :good:
I will do it when i get s-off
can you give me the link fot this thread pleace ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=46301380
Sent from my HTC One VX using Tapatalk

ok i am back now after s-off my phone
and i do every thing but the tampered banner is still there !!
what the problem ?
:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\alhomoud>cd c:\miniadb_m7
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAXXXXXXXXXXXXXX device
c:\miniadb_m7>adb reboot bootloader
c:\miniadb_m7>fastboot devices
FAXXXXXXXXXXXXX fastboot
c:\miniadb_m7>fastboot reboot
rebooting...
finished. total time: 0.040s
c:\miniadb_m7>
Click to expand...
Click to collapse

Thank you. i was removed the tampered. HBOOT 1.54. Easy and fast. Thanks also for beaups!!

killer18 said:
ok i am back now after s-off my phone
and i do every thing but the tampered banner is still there !!
what the problem ?
:
Click to expand...
Click to collapse
Errr... Because you haven't execute the command to reset it yet? Read the first post carefully.
All you've done there is just checking connected device via fastboot command then reboot your phone, not resetting the tempered flag.
EDIT: quoted the first post.
scotty1223 said:
2)reset your "tampered flag"
enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify tamered is gone
Click to expand...
Click to collapse
Sent via HTC One™ using Tapatalk Pro

Is this guide somehow firmware dependatnt? - will this work for 3.57.401.500 ?
thanks

maarawoe said:
Is this guide somehow firmware dependatnt? - will this work for 3.57.401.500 ?
thanks
Click to expand...
Click to collapse
The flag location should not change,so it should work on any firmware.
Sent from my HTC One using Tapatalk

scotty1223 said:
The flag location should not change,so it should work on any firmware.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Works Thx!

I did the S OFF and was curious.
On the boot screen is some red writing about it being a development release etc etc. Is this for that also?
Thanks for any help.

zach181 said:
I did the S OFF and was curious.
On the boot screen is some red writing about it being a development release etc etc. Is this for that also?
Thanks for any help.
Click to expand...
Click to collapse
No, you need to flash a modified hboot in order to remove the red text, check the dev section

Jonny said:
No, you need to flash a modified hboot in order to remove the red text, check the dev section
Click to expand...
Click to collapse
Thanks. I'll go and have a read.

Root for Xperia Z3 Tablet Compact SGP611 *WORK IN PROGRESS*

OBSOLETE! There are now better ways to root using a proper kernel and TWRP. Please follow this guide instead
http://forum.xda-developers.com/z3-tablet-compact/general/adb-fastboot-drivers-tutorial-t2980529
I am working on root for the stock rom on SGP611 with unlocked bootloader.
So far I have managed to get R/W access to /system and make permanent changes. I have installed an su binary but it is not working properly which I believe is because of selinux restrictions. I can become root in ADB and mount /system writable but apps requiring root fails.
I have not tried to build a custom recovery so installing normal flashable zips is not possible.
This is what I did so far:
Get the firmware files using PC Companion
Extract the kernel using Flashtool and split it into kernel, ramdisk and dtb
Extract the ramdisk
Replace adbd with an insecure version
Change fstab.qcom som /system is mounted rw
Reassemble the boot.img using mkbootimg
Code:
mkbootimg --cmdline "androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0xb7 ehci-hcd.park=3 dwc3.maximum_speed=high dwc3_msm.prop_chg_detect=Y" \
--base 0x00000000 --kernel kernel_S1-SW-LIVE-9C84-PID1-0006-MMC.elf.Image --ramdisk ramdisk-insecure.img.gz \
--ramdisk_offset 0x02000000 -o boot.img --dt kernel_S1-SW-LIVE-9C84-PID1-0006-MMC.elf.3 --tags_offset 0x01E00000
Unlock bootloader (I selected Z3 on the Sony unlock web page). YOUR DATA WILL BE WIPED SO MAKE A BACKUP FIRST! DRM keys will be removed which may affect funtionality and can affect the second hand value of your tablet. You have been warned!
Boot the insecure image with fastboot
Code:
fastboot-toolkit.exe boot \temp\insecure-kernel\z3tc-sgp611-insecure.img
Tablet boots but screen is not working.
Connect with ADB with root and /system rw. Now it is possible to push files to /system
Attached is my modified kernel image. I have not tried to flash it but only booted it from fastboot.
I am now asking for help installing a proper su (su daemon?) and tips for building a custom recovery.
Please feel free to move this thread to a development forum but I am not allowed to post there.

I can only hope that you can break through and get this thing rooted. Remember that there are developer's that can give you a hand. I wish I knew how. By the way will this work with SGP621 4G LTE they are the same except for cell capability. I just want to thank you for trying

Instructions for rooting Z3TC with unlocked bootloader
Root for unlocked bootloader
Sony Z3 Tablet Compact Wifi SGP611 firmware 23.0.1.A.0.167
Step by step installation:
Make sure that you have ADB installed and it is working before you proceed. Your PC should be authorized (connect once and press ok on the tablet.)
Reboot to fastboot and unlock bootloader. Follow the instructions here
http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
and select Xperia Z3 if Tablet Compact is not available.
WARNING! YOUR DATA WILL BE WIPED WHEN UNLOCKING THE BOOTLOADER. MAKE SURE THAT YOU HAVE A BACKUP. DRM keys will be removed which may affect functionality and can affect the second hand value of your tablet. You have been warned!
Boot the included kernel image. This will not flash a new kernel, only load it to RAM and boot it
Code:
fastboot boot z3tc-sgp611-insecure.img
Wait for the tablet to boot. NOTHING WILL BE SHOWN ON SCREEN, THE DISPLAY IS
DARK.
Run the following commands to push files to the tablet:
Code:
adb push UPDATE-SuperSU-v2.16.zip /tmp
adb push busybox /tmp
adb push install-supersu.sh /tmp
Start an ADB shell. You should get a root prompt #
Code:
adb shell
In ADB shell, run the script to install supersu. A number of error messages
about missing files will be shown but it is normal.
Code:
# cd /tmp
# /system/bin/sh install-supersu.sh
Reboot tablet and enjoy root!
Code:
# reboot

When booting z3tc-sgp611-insecure.img only mass storage usb device is on USB port, no debug! How to solve?
SGP621, 23.0.1.A.0.167
Code:
C:\adt\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>fastboot boot z3tc-sgp611-insecure.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.333s]
booting...
OKAY [ 0.048s]
finished. total time: 0.385s
C:\adt\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb devices
List of devices attached
C:\adt\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb push UPDATE-SuperSU-v2.16.zip /tmp
error: device not found
error: device not found
C:\adt\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb devices
List of devices attached
C:\adt\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb devices
List of devices attached
C:\adt\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb kill-server
C:\adt\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached

alex9x said:
When booting z3tc-sgp611-insecure.img only mass storage usb device is on USB port, no debug! How to solve?
Click to expand...
Click to collapse
I have SGP611 16GB Wifi version and I do not know if SGP621 uses the exact same kernel.
It sound like a missing driver issue. Is ADB enabled in developer settings? Is ADB working ok when you boot normally?
Check Device Manager in Windows and see if there are any missing drivers (question marks). I had to replace the android_winusb.inf file for the ADB driver to get it to recognize the Z3TC (or maybe that was for Fastboot...).

ejdan said:
I have SGP611 16GB Wifi version and I do not know if SGP621 uses the exact same kernel.
It sound like a missing driver issue. Is ADB enabled in developer settings? Is ADB working ok when you boot normally?
Check Device Manager in Windows and see if there are any missing drivers (question marks). I had to replace the android_winusb.inf file for the ADB driver to get it to recognize the Z3TC (or maybe that was for Fastboot...).
Click to expand...
Click to collapse
All drivers installed, but only SD card appear in device manager. Seems like ADB disabled in booted firmware.
When normal boot - Sony sa0111 ADB Interface Driver (USB\VID_0FCE&PID_51C0&REV_0232&MI_01 ) appear and all OK. But before connection it ask to allow my pc connection and display RSA keys. One time press allow, and then no any questions, adb devices show my serial in list.
When powering UP - Android ADB Interface (USB\VID_0FCE&PID_0DDE&REV_0100) appearing, then booting z3tc-sgp611-insecure.img -
USB Mass Storage Device (USB\VID_0FCE&PID_E1C0&REV_0232) appears in a 7-10 seconds, and no more devices.

right on guys you're getting there. thank you

alex9x said:
When powering UP - Android ADB Interface (USB\VID_0FCE&PID_0DDE&REV_0100) appearing, then booting z3tc-sgp611-insecure.img -
USB Mass Storage Device (USB\VID_0FCE&PID_E1C0&REV_0232) appears in a 7-10 seconds, and no more devices.
Click to expand...
Click to collapse
Do you have any lockscreen security enabled? Maybe ADB is disabled when the device is locked. Try disabling PIN/pattern lock before booting the insecure kernel.

ejdan said:
Do you have any lockscreen security enabled? Maybe ADB is disabled when the device is locked. Try disabling PIN/pattern lock before booting the insecure kernel.
Click to expand...
Click to collapse
no any locks... I know this...
usb sd device is the same like when charging.... seems like when insecure kernel boots - it just enter charger mode... when booting insecure image, need any pressing key?

alex9x said:
When powering UP - Android ADB Interface (USB\VID_0FCE&PID_0DDE&REV_0100) appearing, then booting z3tc-sgp611-insecure.img -
USB Mass Storage Device (USB\VID_0FCE&PID_E1C0&REV_0232) appears in a 7-10 seconds, and no more devices.
Click to expand...
Click to collapse
Also I have my tablet set to MTP mode. Maybe it makes a difference.
Settings -> Xperia connections -> USB connection -> USB connection mode (translated from Swedish so it may not be the exact wording in English.)

ejdan said:
Also I have my tablet set to MTP mode. Maybe it makes a difference.
Settings -> Xperia connections -> USB connection -> USB connection mode (translated from Swedish so it may not be the exact wording in English.)
Click to expand...
Click to collapse
Yes, mode is MTP. When booting insecure - mass storage device NOT connect SD or internal flash, just disk without any access.
Maybe you make other steps or settings? that may affect...

alex9x said:
Yes, mode is MTP. When booting insecure - mass storage device NOT connect SD or internal flash, just disk without any access.
Maybe you make other steps or settings? that may affect...
Click to expand...
Click to collapse
Ok, then I do not know. The kernel I used is for SGP611 so maybe you need a different kernel.

ejdan said:
I have SGP611 16GB Wifi version and I do not know if SGP621 uses the exact same kernel.
Click to expand...
Click to collapse
i don't understand this.
i have the 32GB wifi only version and it says model number SGP621. What exactly is the SGP611 ?

Just a thought. Make sure you have the updated version of adb.exe installed. Previous versions will not work with KK. You will get no devices when doing "adb devices". If your tab is running, and adb debugging is enabled, and you can't get it to display devices (and no security notice on the tab), update your adb.exe
Also, when you push SU and the apk, you may want to do a chmod . Here's an example I used on the A700 tabs from my bat file, note your directories may need to be changed, but you get the general idea;
Code:
adb remount
adb push su /system/xbin/
adb push Superuser.apk /system/app/
adb push busybox /system/xbin/
adb shell chmod 6755 /system/xbin/su
adb shell chmod 0755 /system/xbin/busybox
adb shell chmod 0644 /system/app/Superuser.apk
cls
echo Installing busybox
adb shell /system/xbin/busybox --install -s /system/xbin
Just some info.

a user said:
i don't understand this.
i have the 32GB wifi only version and it says model number SGP621. What exactly is the SGP611 ?
Click to expand...
Click to collapse
SGP611 is 16GB wifi only version. I think the kernel, ramdisk and system should be the same for 16GB and 32GB versions but LTE version may be different.
According to Sony kernel docs the SGP611 and SGP612 uses the same config and SGP621/SGP641 is a different config.
Xperia Z3 Tablet Compact SGP621/SGP641 => shinano_scorpion_defconfig
Xperia Z3 Tablet Compact SGP611/SGP612 => shinano_scorpion_windy_defconfig
Click to expand...
Click to collapse
In Sweden 3 versions are available from the Sony online store:
16 GB Wi-Fi® SGP611NB
32 GB Wi-Fi® SGP612NB
LTE/4G 16 GB SGP621NB

Moscow Desire said:
Just a thought. Make sure you have the updated version of adb.exe installed. Previous versions will not work with KK. You will get no devices when doing "adb devices". If your tab is running, and adb debugging is enabled, and you can't get it to display devices (and no security notice on the tab), update your adb.exe
Also, when you push SU and the apk, you may want to do a chmod . Here's an example I used on the A700 tabs from my bat file, note your directories may need to be changed, but you get the general idea;
Code:
adb remount
adb push su /system/xbin/
adb push Superuser.apk /system/app/
adb push busybox /system/xbin/
adb shell chmod 6755 /system/xbin/su
adb shell chmod 0755 /system/xbin/busybox
adb shell chmod 0644 /system/app/Superuser.apk
cls
echo Installing busybox
adb shell /system/xbin/busybox --install -s /system/xbin
Just some info.
Click to expand...
Click to collapse
chmod is not enough for KitKat because of SELinux. Take a look at the update script from superuser 2.16 and the chcon command to change file SELinux security context.

ejdan said:
chmod is not enough for KitKat because of SELinux. Take a look at the update script from superuser 2.16 and the chcon command to change file SELinux security context.
Click to expand...
Click to collapse
Thanks for the info. KK is new for me since coming off the Iconia tabs.

Your very much welcomed Ejdan, I will try your rooting method when i get home tonight and i will report back if i have success because i have been trying to root this tablet now for nearly two weeks, I tried all the rooting methods, apks and recoveries as they all failed but now we have hope

ejdan said:
SGP611 is 16GB wifi only version. I think the kernel, ramdisk and system should be the same for 16GB and 32GB versions but LTE version may be different.
According to Sony kernel docs the SGP611 and SGP612 uses the same config and SGP621/SGP641 is a different config.
In Sweden 3 versions are available from the Sony online store:
16 GB Wi-Fi® SGP611NB
32 GB Wi-Fi® SGP612NB
LTE/4G 16 GB SGP621NB
Click to expand...
Click to collapse
I reassamble boot.img from downloaded firmware (from sony site, with flashtool) with correct kernel and dt_image from original firmware - the same result! the same usb storage unknown device.
611 have "SoMC Scorpion WINDY"
621 have "SoMC Scorpion ROW"
flashtool log while manipulations...
Code:
24/032/2014 23:32:52 - INFO - Device disconnected
24/033/2014 23:33:08 - INFO - Device connected in fastboot mode
24/033/2014 23:33:32 - INFO - Device disconnected
24/033/2014 23:33:41 - INFO - Device connected with USB debugging off
24/033/2014 23:33:41 - INFO - For 2011 devices line, be sure you are not in MTP mode
24/034/2014 23:34:06 - INFO - List of connected devices (Device Id) :
24/034/2014 23:34:06 - INFO - - USB\VID_0FCE&PID_E1C0\[my_serial] Driver installed : true
24/034/2014 23:34:06 - INFO - List of ADB devices :
24/034/2014 23:34:06 - INFO - - none
24/034/2014 23:34:06 - INFO - List of fastboot devices :
24/034/2014 23:34:06 - INFO - - none
What may be problem? Maybe another settings in tablet?

Moscow Desire said:
Just a thought. Make sure you have the updated version of adb.exe installed. Previous versions will not work with KK. You will get no devices when doing "adb devices". If your tab is running, and adb debugging is enabled, and you can't get it to display devices (and no security notice on the tab), update your adb.exe
Click to expand...
Click to collapse
adb.exe downloaded from site yesterday, this is not adb error - no adb device in device manager, seems that adbd not started on tablet or just asking for permission in a black screen... but when booting normal - adb device OK and no any permission/RSAkey questions.
Normal boot:
Code:
25/035/2014 00:35:28 - INFO - List of connected devices (Device Id) :
25/035/2014 00:35:28 - INFO - - USB\VID_0FCE&PID_51C0&MI_00\7&13ECB37&0&0000 Driver installed : true
25/035/2014 00:35:28 - INFO - - USB\VID_0FCE&PID_51C0&MI_01\7&13ECB37&0&0001 Driver installed : true
25/035/2014 00:35:28 - INFO - - USB\VID_0FCE&PID_51C0\C[serial]N Driver installed : true
25/035/2014 00:35:28 - INFO - List of ADB devices :
25/035/2014 00:35:28 - INFO - - C[serial]N
25/035/2014 00:35:28 - INFO - List of fastboot devices :
25/035/2014 00:35:28 - INFO - - none

reboot disemmcwp doesnt work

Hi, "adb shell reboot disemmcwp" doesnt work for me on 2017G 7.1.1 (B05).
Some weeks ago i used a different command that worked. But i cant remember this command and cant find it anymore via google.
Does anyone know which command it is?!
thanks.

It depends on where you're doing this at. Are you using CMD or terminal on the phone?

nolimit78 said:
Are you using CMD or terminal on the phone?
Click to expand...
Click to collapse
cmd as admin and also with terminal (root).

Spillunke said:
cmd as admin and also with terminal (root).
Click to expand...
Click to collapse
I just used 'adb reboot disemmcwp' and it worked.

This command doesnt work for me.
No effect with CMD or terminal. There is an other similar command that works.
EDIT: im not sure, but is it maybe a problem of magisk? I use Magisk, not SuperSu. Would it work with SuperSu?

PUSH

Spillunke said:
PUSH
Click to expand...
Click to collapse
Did you try it? What was the error? Its very bad practise to just say "it did not work".

After booting up, i cant deinstall system apps for example.
Now i switched to an other stock rom and now i can deinstall systemapps, but there are still problems: cant delete files in system/ but this seems to be an magisk based issue.

Spillunke said:
After booting up, i cant deinstall system apps for example.
Now i switched to an other stock rom and now i can deinstall systemapps, but there are still problems: cant delete files in system/ but this seems to be an magisk based issue.
Click to expand...
Click to collapse
try mount -o rw,remount,rw /system (as root)
if that doesnt work, try this in terminal in twrp.

Zobat said:
try mount -o rw,remount,rw /system (as root)
if that doesnt work, try this in terminal in twrp.
Click to expand...
Click to collapse
All in one line or are this 3 single commands?

hi guys.
this simple process is so hard for me but somehow i managed to reboot disemmcwp
i learned that my ZTE HSUSB driver not properly installed (check through you device manager).
after properly installed it, i manage to pair with my laptop
before
C:\adb>adb shell
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: device unauthorized.
after
C:\adb>adb shell
[email protected]:/ $
so just type
C:\adb>adb shell
[email protected]:/ $ reboot disemmcwp

colmanjr said:
hi guys.
this simple process is so hard for me but somehow i managed to reboot disemmcwp
i learned that my ZTE HSUSB driver not properly installed (check through you device manager).
after properly installed it, i manage to pair with my laptop
before
C:\adb>adb shell
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: device unauthorized.
after
C:\adb>adb shell
[email protected]:/ $
so just type
C:\adb>adb shell
[email protected]:/ $ reboot disemmcwp
Click to expand...
Click to collapse
msm8974? you sure you have an axon7?