Database Develop

[GUIDE] How to get root on the 10.1v

BEFORE YOU BEGIN
As always, mucking with your device at this level is risky. If you follow this process, you do so entirely at your own risk. I accept no responsibility for any detrimental effects resulting from following this process, or for any problems associated with the updated files. Only if you accept these risks should you use these instructions.
PREREQUISITES
Unlocked bootloader (see my guide to do this)
Working fastboot (also see my guide )
Patience
NOTES
I developed and followed this process on Ubuntu Natty, 64bit. I see no reason why it should not work on any other platform, since the only tool used is fastboot and the syntax for fastboot is the same on any platform. if you need to know how to get fastboot working, there are already many guides for that (see my how to unlock your bootloader thread, for example)
BUTTON CONFUSION
When in landscape mode, with the camera at the top, the power button is on the left 'vertical' side of the tab. On the top is the volume rocker. In this orientation:
- The LEFT side of the volume rocker is VOLUME DOWN
- The RIGHT side of the volume rocker is VOLUME UP
This might seem obvious, but to anyone who is used to phones, this is the opposite, since they were designed to be used in Portrait mode.
PREPARE
1) With your Tab in fastboot mode (step 1 of "GETTING ROOT" below), make sure you have a working fastboot implementation:
Code:
fastboot devices
If all is well, you should see your device serial number. If there is a problem, you won't get any response.
2) Downlad View attachment skitzandroid-10-1v-root_0.2.zip and View attachment skitzandroid-stock-recovery.zip
3) Create a folder on your desktop called "root"
Code:
mkdir ~/Desktop/root
for Ubuntu or
Code:
md %userprofile%\desktop\root
for Windows
This will be referred to as the working directory throughout the rest of this guide
4) Copy skitzandroid-10-1v-root.zip to your working directory (DO NOT UNZIP!)
5) Extract the skitzandroid-recovery.img file from skitzandroid-stock-recovery.zip to your working folder. Your working folder should now have 1 IMG file and one ZIP file.
6) This was an afterthought - Make sure fastboot is somewhere in your path (ie can be executed from anywhere). To test, 'cd' to any random folder and type 'fastboot' and make sure it runs.
7) Copy the skitzandroid-10-1v-root.zip file to the root of your sdcard. You can eithe drag/drop, or run:
Code:
adb push skitzandroid-10-1v-root.zip /sdcard/
from your working directory
...now the easy part
GETTING ROOT
1) Power off your Tab and power it back on, while holding the VOLUME DOWN button.
2) When the DOWNLOAD / FASTBOOT icons appear, press VOLUME DOWN again to select FASTBOOT icon (the one with the USB logo) and press VOLUME UP to confirm selection.
3) Confirm you are now in fastboot mode and do a:
Code:
fastboot devices
If all is well, you should see your device serial number.
4) Open a terminal / CMD prompt and CD to your working folder
Code:
cd ~/Desktop/root
for Ubuntu or
Code:
cd %userprofile%\desktop\root
for Windows
5) Run the following command:
Temp Root:
Code:
fastboot boot skitzandroid-recovery.img
..and wait. It might not look like anything is happening but it is.
Permanent Root:
Code:
fastboot flash recovery skitzandroid-recovery.img
6) You should now have a recovery menu. Use the volume rocker (up/down navigates menu options) to select "Install zip from SDCARD" (or something like that - if someone can post the exact menu item wording, I will update the guide). Press (tap!) the POWER button to confirm the menu selection
7) Navigate to the root of your internal storage (/sdcard), select the skitzandroid-10-1v-root.zip file and press (tap!) the POWER button to confirm selection.
8) Once complete, use the Volume rocker to select "REBOOT" from the menu and press (tap!!!) the POWER button to confirm selection.
9) You're done! Press the thanks button on this thread to continue
TESTING
1) Once your Tab boots up, check your apps menu to confirm the existence of SuperUser app.
2) With the Tab attached to your PC via USB cable, do the following:
Code:
adb shell
su
..and watch the screen on your Tab for a SuperUser prompt. If you see this, congratulations!
If you have never rooted a phone/tablet before, go get Titanium Backup Pro and ROM Manager from the market. As soon as the custom ROMs start flowing in, you'll be all set to go.
Edit: How about thanking smaskell who was very patient and persistent in dumping the image from his Google IO 10.1 - for the good of his fellow XDA members. Without his help, this would not be possible.

Note that the above process doesn't flash the recovery, just loads it.
If you want to flash the recovery permanently, all you need to do is follow the guide above and then, in step 5, use this command instead:
Code:
fastboot flash recovery skitzandroid-recovery.img
You will then have a permanent recovery which you can get to by doing:
Code:
adb shell
su
reboot recovery
at any time.
Note that doing just
adb reboot recovery
Click to expand...
Click to collapse
...for some bizarre reason does not boot to recovery. Open up a shell first, as shown above.
I will also give you credit in the guide for having "Balls of Steel" to steal a phrase from PaulObrien
EDIT:
...and the Balls of Steel award goes to *drumroll*
Egan
...for having the balls to flash the recovery. Thanks egan. If I was in a battle, I'd definitely want you in our squad

FAQ
Does it need unlocked bootloader? Yes, see my other guide for this.
Do I need to wipe, or will it wipe my device? No and No.
Can I return my device to factory default config? Yes. This process does not flash the partition unless you follow the process in post 2 which is optional.
Changelog
0.2 - Added busybox (can be flashed over the top of 0.1 without wipe)
0.1 - Initial Relase
Factory Voda Tab Images
Recovery
Boot
System

Awesome news! Thanks to everyone who worked on this - I can't wait!

Great, great job you guys! This thing needs root so it can grow

Thanks a lot bcmobile and smaskell! Ill give it a go around launch.
Sent from my LG-P990 using XDA Premium App

Thank you guys, it's working great on my 10.1v

I'm pretty sure I know the answer to this already - but is there anyway of getting temp root on these devices so I can backup all my apps and data (properly) before unlocking / flashing recovery / rooting??

This wont make any changes to the partitions. You could undo the whole process by just deleting a few files.
The process in my second post would actually flash the image, and would be permanent if you had no 'factory' recovery image to flash back.
The 'standard' process in post 1 is normally used for testing and doesn't overwrite the recovery partition

Thanks a lot. Works like a charm
Now to make a full "original" fastboot flashable restore fileset:
Boot: dd if=/dev/block/mmcblk0p5 of=/sdcard/boot.img
System: dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img
Would this be enough to have a proper "original" image? (With the small addition of root offcourse)
(Did a dd of dd if=/dev/block/mmcblk0p1 of=/sdcard/efs.img too, just to have a backup
Will see if I can make a full nandroid back-up now
Before flashing any recovery images etc..

gjroeleveld said:
Thanks a lot. Works like a charm
Now to make a full "original" fastboot flashable restore fileset:
Boot: dd if=/dev/block/mmcblk0p5 of=/sdcard/boot.img
System: dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img
Would this be enough to have a proper "original" image? (With the small addition of root offcourse)
(Did a dd of dd if=/dev/block/mmcblk0p1 of=/sdcard/efs.img too, just to have a backup
Will see if I can make a full nandroid back-up now
Before flashing any recovery images etc..
Click to expand...
Click to collapse
That's all the backup I have done so I hope so
Just uploading a new version of the update zip (v0.2) which includes busybox

bcmobile said:
This wont make any changes to the partitions. You could undo the whole process by just deleting a few files.
The process in my second post would actually flash the image, and would be permanent if you had no 'factory' recovery image to flash back.
The 'standard' process in post 1 is normally used for testing and doesn't overwrite the recovery partition
Click to expand...
Click to collapse
Sorry, I realise that applying the root won't wipe anything, but unlocking the bootloader comes with a nice factory reset if I'm not mistaken..

gjroeleveld said:
Now to make a full "original" fastboot flashable restore fileset:
Boot: dd if=/dev/block/mmcblk0p5 of=/sdcard/boot.img
System: dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img
Click to expand...
Click to collapse
Sorry for the ignorance, but are these fastboot or a adb commands?

Good work!
You should mention that you can't unlock and flash the Root-Update in one step.
The recovery complains then that /data/media is missing
Regards
EDIT:
black beard said:
Sorry for the ignorance, but are these fastboot or a adb commands?
Click to expand...
Click to collapse
These are adb commands you need to do with su!

black beard said:
Sorry, I realise that applying the root won't wipe anything, but unlocking the bootloader comes with a nice factory reset if I'm not mistaken..
Click to expand...
Click to collapse
That is part of the recovery image, not the unlocked bootloader.
You can always put back a stock image using fastboot which is one of the really nice things about fastboot unlocking vs bootloader exploits. "fastboot oem unlock" can then be undone by "fastboot oem lock" and nobody would know the diff.

seraphimserapis said:
Good work!
You should mention that you can't unlock and flash the Root-Update in one step.
The recovery complains then that /data/media is missing
Click to expand...
Click to collapse
Thanks!
Yeah, oem unlock doesn't actually do anything until the next boot

Egan said:
Thanks a lot bcmobile and smaskell! Ill give it a go around lunch.
Sent from my LG-P990 using XDA Premium App
Click to expand...
Click to collapse
Works like a charm! Now lets backup the original recovery and then flash the stock recovery .

Egan said:
Works like a charm! Now lets backup the original recovery and then flash the stock recovery .
Click to expand...
Click to collapse
Are you going to flash it?
You will earn the official "Balls of steel" badge

Thanks,
Also remember to enable USB debugging after you have done the unlocked bootloader, took me 5 min to to realize why adb did not want to work, 5 scary min after the reboot.

I've tried to make a proper nandroid backup but haven't been able too.
Tried with romdump 0.72 but that crashes :-(
Most tutorials use Rom Manager, but that needs some work from @koush before we can use it.
I'll google on
Sent from my GT-I9000 using XDA Premium App

[Q] nandroid via adb or fastboot

hi to all!! i have a doubt....
can i do a nandroid backup of my current rom using adb or fastboot parameters??
anyone can write or leave it here?
thank´s in advance!!

No. Custom recover does it. You can issue the adb reboot recover command to get into it etc....
Sent from my Nexus One using XDA App

Yea...maybe its the reason that i dont know this parameter lol
sent from my amstrad CPC powered by LOL..(premium xda)

You sure can do it from adb. I had to find this out when I cracked my AMOLED screen and had to try and back everything up without being able to use the screen of my phone.
You need to be in recovery for it (you might be able to backup with fastboot as well, but I didn't have my bootloader unlocked at the time), so if you are full booted up, reboot into recovery and follow these commands.
Code:
adb reboot recovery
adb shell
nandroid backup
Nice and simple, right?

bassmadrigal said:
You sure can do it from adb. I had to find this out when I cracked my AMOLED screen and had to try and back everything up without being able to use the screen of my phone.
You need to be in recovery for it (you might be able to backup with fastboot as well, but I didn't have my bootloader unlocked at the time), so if you are full booted up, reboot into recovery and follow these commands.
Code:
adb reboot recovery
adb shell
nandroid backup
Nice and simple, right?
Click to expand...
Click to collapse
all rigth buddy... thank´s!!! i´ve a adb fastboot command list and this does not stay in the list...

bassmadrigal said:
You sure can do it from adb. I had to find this out when I cracked my AMOLED screen and had to try and back everything up without being able to use the screen of my phone.
You need to be in recovery for it (you might be able to backup with fastboot as well, but I didn't have my bootloader unlocked at the time), so if you are full booted up, reboot into recovery and follow these commands.
Code:
adb reboot recovery
adb shell
nandroid backup
Nice and simple, right?
Click to expand...
Click to collapse
ok i did it with the commands that you gave to me... and i obtain it when i try...
E:UNKNOWN VOLUME FOR PATH [/SDCARD]
CAN´T MOUNT SD CARD
#.
any advise????? please.......

some one can help-me please?? thanks in advance for your advises!!

SERGI.3210 said:
ok i did it with the commands that you gave to me... and i obtain it when i try...
E:UNKNOWN VOLUME FOR PATH [/SDCARD]
CAN´T MOUNT SD CARD
#.
any advise????? please.......
Click to expand...
Click to collapse
Sorry, I was out of town all day...
At what point is this failing? I assume you actually have an sdcard loaded in the phone?

bassmadrigal said:
Sorry, I was out of town all day...
At what point is this failing? I assume you actually have an sdcard loaded in the phone?
Click to expand...
Click to collapse
thanks for your continuity in this thread!!
shell shows me this when i put my device into recovery and enter the code that was provided to my above...sd card is in my device... but i think that the problem is that i don´t know what´s exactly the status that the phone need to stay.. into recovery with sd card usb mounted?(i think that not)
with the phone booted and in usb debugging mode & only chargue?

If you are booted into the phone (ie. fully loaded and able to use your phone), you need to issue the adb reboot recovery command. If the phone is off, hold down the volume down button as you are booting up. This will load the bootloader. From there, it will do a little check, and then you can use the volume keys to go to Recovery. Hit the Power button to select it. The phone will load the 'X' screen and eventually be in recovery (the text should be green or orange).
Once you are in recovery, you don't need to do anything else on the phone. Just issue
Code:
adb shell
nandroid backup
(You might have to issue the 'su' command if it shows a $ instead of a # before you run the backup.)

bassmadrigal said:
If you are booted into the phone (ie. fully loaded and able to use your phone), you need to issue the adb reboot recovery command. If the phone is off, hold down the volume down button as you are booting up. This will load the bootloader. From there, it will do a little check, and then you can use the volume keys to go to Recovery. Hit the Power button to select it. The phone will load the 'X' screen and eventually be in recovery (the text should be green or orange).
Once you are in recovery, you don't need to do anything else on the phone. Just issue
Code:
adb shell
nandroid backup
(You might have to issue the 'su' command if it shows a $ instead of a # before you run the backup.)
Click to expand...
Click to collapse
when i did it i obtained:
Code:
~#nandroid backup
E:unknown volume for path [/sdcard]
can´t mount sdcard
and if i write su i obtain it:
Code:
~#su
/sbin/sh: su: not found
~#
sorry for my ignorance mate i´m open for your help

also i know that the device is in the correct mode thank´s to you... and confirmated with command:
Code:
adb status-window
-[2j-[2hANDROID debug bridge (adb mode)
status:unknown

Which recovery do you use?

What happens when you type
Code:
adb devices
?

bassmadrigal said:
What happens when you type
Code:
adb devices
?
Click to expand...
Click to collapse
shows me that the device its connected and a big number... this part its correct

danger-rat said:
Which recovery do you use?
Click to expand...
Click to collapse
CWM recovery

SERGI.3210 said:
CWM recovery
Click to expand...
Click to collapse
CWM 3.x, or 2.x?

same problem
danger-rat said:
CWM 3.x, or 2.x?
Click to expand...
Click to collapse
I'm having the same problem with my HeroC. If you have any idea what to do I would really appreciate it! I'm running AOSP 2.3.4, Firerats MTD, and CWmod 3xxx

Don't use CWM 3.x, stick to the latest 2.x

danger-rat said:
Don't use CWM 3.x, stick to the latest 2.x
Click to expand...
Click to collapse
Should I just flash the CW2xxx over the CW3xxx and then proceed with the nandroid backup? I can't use my screen at all, so will that be a problem?

My device not getting into recovery.

My device not getting into recovery. Harwarically I can get into recovery, but I can not use adb reboot recovery or any rebooting app, it just normal reboots. Need urgent help. My buttons are almost finished cant stand more pressure.

Subhajitdas298 said:
Harwarically I can get into recovery
Click to expand...
Click to collapse
harwarically?
try changing recovery, if that doesn't solve it it's a rom problem

Rudjgaard said:
harwarically?
try changing recovery, if that doesn't solve it it's a rom problem
Click to expand...
Click to collapse
stock rom. i can get into recovery using hardware buttons and pa rom's power button menu. but can not get into using other apps.

Subhajitdas298 said:
stock rom. i can get into recovery using hardware buttons and pa rom's power button menu. but can not get into using other apps.
Click to expand...
Click to collapse
What other apps? Like some reboot app? Maybe they send the wrong argument to the bootloader. Might not be compatible with our device.
If you can get in using hardware buttons, then its mostly a problem with the other apps you are trying.

Download terminal emulator, run:
Code:
su
reboot recovery
and you're in recovery. If that doesn't work for some unknown reason, you need to switch roms.
EDIT: disregard this, per adams post below.

It doesn't work on stock rom unless you manually write recovery boot command to misc partition.
Sent from my OmniROM-powered LG Optimus 4X HD

Download from playstore rom manager and go in, in the app theres a option : *boot my device into recovery*
Sent from my LG-P880 using xda app-developers app

GalaxyVolvoZ said:
Download from playstore rom manager and go in, in the app theres a option : *boot my device into recovery*
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
As Adam posted above, none of these apps/ commands will work if it isn't defined in the misc partition. I wasnt aware of this before Adam pointed it out, ill look into the easiest way for this to be done.

JoinTheRealms said:
As Adam posted above, none of these apps/ commands will work if it isn't defined in the misc partition. I wasnt aware of this before Adam pointed it out, ill look into the easiest way for this to be done.
Click to expand...
Click to collapse
IIRC now that @GalaxyVolvoZ posted ROM Manager works, because it writes the needed command.
Otherwise this is the command needed in shell:
Code:
echo "boot-recovery" | /system/bin/dd of=/dev/block/mmcblk0p5 bs=1 count=13

Adam77Root said:
IIRC now that @GalaxyVolvoZ posted ROM Manager works, because it writes the needed command.
Otherwise this is the command needed in shell:
Code:
echo "boot-recovery" | /system/bin/dd of=/dev/block/mmcblk0p5 bs=1 count=13
Click to expand...
Click to collapse
Thanks! slightly off topic, but do you know what format the misc partition is?

JoinTheRealms said:
Thanks! slightly off topic, but do you know what format the misc partition is?
Click to expand...
Click to collapse
It's probably not formatted, just raw data.
Sent from my OmniROM-powered LG Optimus 4X HD

JoinTheRealms said:
Download terminal emulator, run:
Code:
su
reboot recovery
and you're in recovery. If that doesn't work for some unknown reason, you need to switch roms.
EDIT: disregard this, per adams post below.
Click to expand...
Click to collapse
does not work for me

i cant enter recovery on my phone. getting this everytime reboot int recovery. tried physical keys, or rom manager, even system reset also cannot do because of this. any idea how to solve this?
currently on stock rom

cruelboy86 said:
i cant enter recovery on my phone. getting this everytime reboot int recovery. tried physical keys, or rom manager, even system reset also cannot do because of this. any idea how to solve this?
currently on stock rom
Click to expand...
Click to collapse
Did you try to flash a recovery without unlocking bootloader?
Use LG mobile support tool.

adb reboot recovery not opening recovery

I can not go to recovery (stock or custom) with "adb reboot recovery" command (adb is otherwise working). It just reboots the phone.
Third party apps to reboot in recovery not working also, except ROM Manager. I recently installed AOSP (by MoltenMotherBoard) it is not rooted. Now I can not reboot in recovery with ROM Manager.
My phone buttons are dead, only software solution is needed.
How to fix this?
Need in immediate help.

$ adb shell setup-recovery
$ adb reboot

Works
csk1jw said:
$ adb shell setup-recovery
$ adb reboot
Click to expand...
Click to collapse
Thanks man.

csk1jw said:
$ adb shell setup-recovery
$ adb reboot
Click to expand...
Click to collapse
Thank you

up

Hazy p880 bootloader + spec.
ze7zez said:
up
Click to expand...
Click to collapse
"down-mare"
@kessaras @Phil_Smith
IMHO, this xda post is closest theory on "setup-recovery" p880 trick : https://forum.xda-developers.com/showpost.php?p=22212494&postcount=22
Also , only twrp is handling specific stuff : https://github.com/omnirom/android_bootable_recovery/search?utf8=✓&q=rebootrecovery.sh&type=Code
Thx to twrp300/multirom sources , looks latest Multirom Trampolinev27 (slightly modified) with both reboot options
- regular reboot to bootloader/fastboot OK
- modified/warm reboot to recovery with f2fs OK: press/power only straight to recovery, or no-press straight to primary AND 1st reboot from aosp6/7 straight to recovery; both with f2fs !
Finally there are many ways to run "setup-recovery",without PCadb & within aosp6/7, 3Ctoolsboxfree(+su) or even Kadiutor via init.d section: copy system/bin/setup-recovery to etc/init.d/ then use KAdiutor/init.d section to trigger the script + 3dots reboot...
Attached is a very old 2013 asian transcription for in-tech view (UNCONFIRMED! caution); if some have info on mmcblk0p14, let us know.

no recovery, no download mode, no micro usb, but root?

hello dears,
i have very big problem with my c6603. i installed first lollipop hongkong version to my c6603. every function works but i want to install mods and other roms but; my phones usb port doesnt let the pc recognize as "phone". it is not driver problem ; it is hardware failure definetly. the port just charging my phone. And on the phone there is no recovery and download mode. But phone has root. i tried a few things to install custom recovery but couldnt be success. unlocked bootloader but no recovery as i said. i really appreciate if there is a solution. many thanks

mca1 said:
hello dears,
i have very big problem with my c6603. i installed first lollipop hongkong version to my c6603. every function works but i want to install mods and other roms but; my phones usb port doesnt let the pc recognize as "phone". it is not driver problem ; it is hardware failure definetly. the port just charging my phone. And on the phone there is no recovery and download mode. But phone has root. i tried a few things to install custom recovery but couldnt be success. unlocked bootloader but no recovery as i said. i really appreciate if there is a solution. many thanks
Click to expand...
Click to collapse
How did you install that Hong Kong lollipop?

mca1 said:
hello dears,
i have very big problem with my c6603. i installed first lollipop hongkong version to my c6603. every function works but i want to install mods and other roms but; my phones usb port doesnt let the pc recognize as "phone". it is not driver problem ; it is hardware failure definetly. the port just charging my phone. And on the phone there is no recovery and download mode. But phone has root. i tried a few things to install custom recovery but couldnt be success. unlocked bootloader but no recovery as i said. i really appreciate if there is a solution. many thanks
Click to expand...
Click to collapse
Hi there.If you have root access and unlocked bootloader,you can install TWRP even without pc connection.
first you should download a terminal emulator app from google play.
then you should download the latest version of TWRP image file from here https://dl.twrp.me/yuga/.
Place it in the root of your /sdcard folder and rename it to twrp.img
Run the following commands in terminal app
Code:
su
and then we write recovery image file to FOTA with dd command.
Code:
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
and it's done.
press thanks if it was helpful.

i installed hk lollipop zip from my custom twrp recovery. and when rom istall has finished ; recovery gone.

mrp1375 said:
Hi there.If you have root access and unlocked bootloader,you can install TWRP even without pc connection.
first you should download a terminal emulator app from google play.
then you should download the latest version of TWRP image file from here https://dl.twrp.me/yuga/.
Place it in the root of your /sdcard folder and rename it to twrp.img
Run the following commands in terminal app
Code:
su
and then we write recovery image file to FOTA with dd command.
Code:
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
and it's done.
press thanks if it was helpful.
Click to expand...
Click to collapse
thank you mrp1375 but i tried this method and when i want to go recovery phone only restarts. because phone has no stock recovery.

mca1 said:
thank you mrp1375 but i tried this method and when i want to go recovery phone only restarts. because phone has no stock recovery.
Click to expand...
Click to collapse
Below are 2 solutions to get a properly working recovery
Preperation:
1. Download Dual recovery installer: XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip
2. Install NDRUtils
Next up we will test if the TWRP you installed works or not
-open NDRUtils and choose to boot into TWRP recovery.
Now unhide the result that you got to continue with the installation:
OK: I am now in TWRP
flash XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip and reboot.
Everything will work normally now.
Not OK: I am not in TWRP
Reboot the phone if you have to (hold power until you feel 3 vibrations and then turn the phone back on)
You need to download this: http://nut.xperia-files.com/path/XZDualRecovery/Kernel_Builder
To get the right file make sure to selec the xperia z c6603 and select the rom version you are using, you can view what you have in settings, about phone, build number.
it will be much easier for you if you install this: X-plore File Manager The reason i recommend this application is that it automatically makes sure the file rights are correct.
Go into the settings and enable superuser +mount root mode
Now you can browse to the folder where you downloaded the zip in the left pane.
go into the zip and and then into tmp
Select the boot.img
now move to the right pane and browse to the root of your SD card like the comment above
go back to the left pane and with boot.img still checked click copy.
Now follow the original instructions mrp1375 gave you, but notice the different filename
Open terminal
Type : su
Type: dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Now you can reboot and if it worked the phone will vibrate twice and show a green led meaning you can press the down button to enter TWRP recovery.
Go into the recovery and now flash XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip so you get a proper installation
Now remember this very important fact:
Whenever you flash or wipe anything you MUST reinstall recovery and root again.
This is a failsafe strategy you can NEVER ignore becaus of your usb issues.
Keep SuperSu installer and XZ-lockeddualrecovery installer on your device at all times!

thank you

mca1 said:
thank you
Click to expand...
Click to collapse
Does that mean it worked?

tetsuo55 said:
Does that mean it worked?
Click to expand...
Click to collapse
Yes it worked, thank you much. :good:

tetsuo55 said:
Below are 2 solutions to get a properly working recovery
Next up we will test if the TWRP you installed works or not
-open NDRUtils and choose to boot into TWRP recovery.
Now unhide the result that you got to continue with the installation:
OK: I am now in TWRP
flash XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip and reboot.
Everything will work normally now.
Not OK: I am not in TWRP
Reboot the phone if you have to (hold power until you feel 3 vibrations and then turn the phone back on)
You need to download this:
To get the right file make sure to selec the xperia z c6603 and select the rom version you are using, you can view what you have in settings, about phone, build number.
it will be much easier for you if you install this: The reason i recommend this application is that it automatically makes sure the file rights are correct.
Go into the settings and enable superuser +mount root mode
Now you can browse to the folder where you downloaded the zip in the left pane.
go into the zip and and then into tmp
Select the boot.img
now move to the right pane and browse to the root of your SD card like the comment above
go back to the left pane and with boot.img still checked click copy.
Now follow the original instructions mrp1375 gave you, but notice the different filename
Open terminal
Type : su
Type: dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Now you can reboot and if it worked the phone will vibrate twice and show a green led meaning you can press the down button to enter TWRP recovery.
Go into the recovery and now flash XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip so you get a proper installation
Now remember this very important fact:
Whenever you flash or wipe anything you MUST reinstall recovery and root again.
This is a failsafe strategy you can NEVER ignore becaus of your usb issues.
Keep SuperSu installer and XZ-lockeddualrecovery installer on your device at all times!
Click to expand...
Click to collapse
Hey! I have the same problem as the OP here. I followed the instructions like 5 times and still couldnt get it to work. The terminal is saying that "No space left on device" when i type "dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel"
any way to fix this? Thanks!

comcastic08 said:
Hey! I have the same problem as the OP here. I followed the instructions like 5 times and still couldnt get it to work. The terminal is saying that "No space left on device" when i type "dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel"
any way to fix this? Thanks!
Click to expand...
Click to collapse
That error sounds like either you dont have root or you have a typo, can you make a screenshot?

tetsuo55 said:
That error sounds like either you dont have root or you have a typo, can you make a screenshot?
Click to expand...
Click to collapse
snag. gy/gi8Ji. jpg
sorry i cant post links yet

comcastic08 said:
snag. gy/gi8Ji. jpg
sorry i cant post links yet
Click to expand...
Click to collapse
That doesnt look quite right it should look like this:
Code:
[email protected]:/ $
Then you type "su" (without the quotes) and press enter
The display then changes to:
Code:
[email protected]:/ #
Now you type "dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel" (without the quotes) and press enter
And then it should work properly.

tetsuo55 said:
That doesnt look quite right it should look like this:
Code:
[email protected]:/ $
Then you type "su" (without the quotes) and press enter
The display then changes to:
Code:
[email protected]:/ #
Now you type "dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel" (without the quotes) and press enter
And then it should work properly.
Click to expand...
Click to collapse
i typed su before that code and the same error occured sadly
why did my usb port had to break ugh

comcastic08 said:
i typed su before that code and the same error occured sadly
why did my usb port had to break ugh
Click to expand...
Click to collapse
Can I have another screenshot of that?

tetsuo55 said:
Can I have another screenshot of that?
Click to expand...
Click to collapse
snag .gy/AekHa. jpg

comcastic08 said:
snag .gy/AekHa. jpg
Click to expand...
Click to collapse
In that screenshot i see again the same mistake i mentioned before
please do this
Just type only su and enter
and then send me the screenshot of that.

tetsuo55 said:
In that screenshot i see again the same mistake i mentioned before
please do this
Just type only su and enter
and then send me the screenshot of that.
Click to expand...
Click to collapse
snag. gy/aWyCY .jpg

comcastic08 said:
snag. gy/aWyCY .jpg
Click to expand...
Click to collapse
All i can think of is that you have the wrong boot.img

tetsuo55 said:
All i can think of is that you have the wrong boot.img
Click to expand...
Click to collapse
i downloaded the one you said XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip and renamed it to boot.img
even the twrp.img doesnt work ugh