Database Users

About twrp manager...

Hello everyone. I recently got a nexus 7 and i rooted it and unlocked the bootloader,but i didn't install a custom recovery yet. Can someone tell me how to install it without a PC? I downoaded TWRP manager from google play and i see that it has options to install stuff from it. But i would like to install CWM from it. Is it possible to do that. I have android 4.2.2 btw... thanks in advance.
Sent from my Nexus 7 using xda app-developers app

Twrp and cwm are completely separate recoveries. Just download an image of cwm from the original software sub section, then download flash image gui from the play store. Then, flash cwm. All done. That is the easiest way to do it without using fastboot.
Sent from my Nexus 7 using xda premium

Thank you very much for your help.
Sent from my Nexus 7 using xda app-developers app

rebel1699 said:
Twrp and cwm are completely separate recoveries. Just download an image of cwm from the original software sub section, then download flash image gui from the play store. Then, flash cwm. All done. That is the easiest way to do it without using fastboot.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Why? Rom manager works fine for installing cwm and goo manager works fine for installing TWRP.
Dont really see a need for a completely different app that will handle that process. Dont even have to manually download anything
Sent from my Galaxy Nexus

Pirateghost said:
Why? Rom manager works fine for installing cwm and goo manager works fine for installing TWRP.
Dont really see a need for a completely different app that will handle that process. Dont even have to manually download anything
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
omg the man himself! i think the world needs a binnacle rom for the n7 :highfive: :victory:

tylercarter said:
omg the man himself! i think the world needs a binnacle rom for the n7 :highfive: :victory:
Click to expand...
Click to collapse
I LOL'd
doubt that will happen

Pirateghost said:
I LOL'd
doubt that will happen
Click to expand...
Click to collapse
Its been too long since ive run pg anything on a device. :fingers-crossed:

Pirateghost said:
Why? Rom manager works fine for installing cwm and goo manager works fine for installing TWRP.
Dont really see a need for a completely different app that will handle that process. Dont even have to manually download anything
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I usually go with flash image gui because no matter which recovery, or even which specialized version of a recovery (multirom modified twrp, landscape twrp.....) you have the tool right there handy to quickly flash it on the fly without need of fastboot and a pc. If they never intend to use anything other than the basic custom recovery, i guess the other options are fine. But honestly, flash image gui covers all bases, and makes future modification,should you choose, that much easier.
At its worst, if they do get a little more advanced and want to flash specialized in the future, maybe we avoid another "how to flash image?" post in the q&a section, because thay have already become familiar with the tool to use.
Sent from my Nexus 7 using xda premium

Attention! Recover Your HARD-Bricked TF300T With Wrong TWRP On 4.2 Bootloader!

Goooooooooooooooooooood News...
Finally Found A Way To Unbrick The Tab, Which Requires Mainboard Replacement!
As You Know, If You Have Installed Wrong TWPR Recovery On 4.2 Update, And By Accident Have Erased Recovery Partition, Then You Would Have A HARD-Bricked Tab Which Showed: "Unrecoverable Bootloader Error"
In This State, Asus Support Center Required You To Pay (As You Are Unlocked) To Replace The Mainboard!!!
Finally, One Of Our Friends Found A Solution, Here Is The Link, I Just Wanted To Spread The Word...
It Saved My TF300T, Which Has Been Turned Off For 6 Months!
Here Is The Link, Just Be Patient And You Will Recover Your Tablet
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12

wow man if this is true I'll unlock my bootloader and flash a custom rom even today!
Sent from my ASUS Transformer Pad TF300T using Tapatalk 4

it could easily recover my tab, which was supposed to be sent to Asus next week
it's a milestone, greatly helped...

wow. my post seemed to be the phoenix essence for al lot of tabs (without the need to burn something down)
After Reading it again - my solution is not only for a bad recovery partition - its for any PIT related errors (bad flash - which was my case) etc.
cheers and GL
-Buster
Sent from my GT-I9505 using xda app-developers app

Buster99 said:
wow. my post seemed to be the phoenix essence for al lot of tabs (without the need to burn something down)
After Reading it again - my solution is not only for a bad recovery partition - its for any PIT related errors (bad flash - which was my case) etc.
cheers and GL
-Buster
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
you saved hundreds of dollars for us, i wish i could donate
i just can say: "I DO APPRECIATE" <3
thanks more than a million, bro

Best fix ever.
Thanks !
:good::good:

therock3181 said:
Best fix ever.
Thanks !
:good::good:
Click to expand...
Click to collapse
press "Thanks" button if it helped

this! a thousand times this!
i'm hitting the thanks button like its going out of style, will see about donating as you just saved my brick from 5 months of staying in a cabinet!
this needs to be sticked, or the original post! holy crap i am happy

This is how i unbricked mine. Try it.
Link to my thread --> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps. Try It!

How to uninstall or remove TWRP recovery from tf300?
If this works ... picture this ... ASUS is a rubish tab ... it's totally broken ... i'm lucky if my finger causes the right movements to happen ... so yeah it gets picked up tomorrow .. and without this i'm gonna have to PAY for it to be picked up haha
so lets hope i can stay up all night now and try it out .... literally i didn't find this answer for a year ... why can't i search it ...
How to uninstall or remove TWRP recovery from tf300?
Go back to stock rom tf300
willl report back with love iif it works haha
FAIL ... i thought this was for people who got locked into a bad version of TWRP ... i guess not .. still uses fastboot ... major fail

Thanks you just save my tf

interslicer said:
If this works ... picture this ... ASUS is a rubish tab ... it's totally broken ... i'm lucky if my finger causes the right movements to happen ... so yeah it gets picked up tomorrow .. and without this i'm gonna have to PAY for it to be picked up haha
so lets hope i can stay up all night now and try it out .... literally i didn't find this answer for a year ... why can't i search it ...
How to uninstall or remove TWRP recovery from tf300?
Go back to stock rom tf300
willl report back with love iif it works haha
FAIL ... i thought this was for people who got locked into a bad version of TWRP ... i guess not .. still uses fastboot ... major fail
Click to expand...
Click to collapse
wrong recovery can always be flashed with another one if fastboot works.
if only recovery is your problem no need to go back to stock. but on most cases it's the best way to get a clean start.
Sent from my GT-I9505 using XDA Premium 4 mobile app

Buster99 said:
wrong recovery can always be flashed with another one if fastboot works.
if only recovery is your problem no need to go back to stock. but on most cases it's the best way to get a clean start.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
what if you can't get into recovery and only APX?
I tried installing CWM (for CM11) over an 2.6.0.0 TWRP (4.2) with 10.6.15.3 and no go!
I'm stuck with APX only.
Any ideas? I've tried NVFLASH but can't fix 64bit drivers that work properly. Naked 0.73 didn't either. I can only get the Asus Transformer Prime APX to work properly.

snoopspecial said:
what if you can't get into recovery and only APX?
I tried installing CWM (for CM11) over an 2.6.0.0 TWRP (4.2) with 10.6.15.3 and no go!
I'm stuck with APX only.
Any ideas? I've tried NVFLASH but can't fix 64bit drivers that work properly. Naked 0.73 didn't either. I can only get the Asus Transformer Prime APX to work properly.
Click to expand...
Click to collapse
are you sure its apx?
also for cm11 based roms for the tf300t you need a special recovery (check the omnirom thread - thats the one im using, scannos twrp 2.6.3.0)
you cant run cm11 with older recovs since the PITs changed apparently (haven't read the man pages yet) but thats what i understood out of the omni thread
nvfalsh only works if you backed up your device prior bricking.
cheers & gl
Buster

Buster99 said:
are you sure its apx?
also for cm11 based roms for the tf300t you need a special recovery (check the omnirom thread - thats the one im using, scannos twrp 2.6.3.0)
you cant run cm11 with older recovs since the PITs changed apparently (haven't read the man pages yet) but thats what i understood out of the omni thread
nvfalsh only works if you backed up your device prior bricking.
cheers & gl
Buster
Click to expand...
Click to collapse
So it is a really good idea to backup your device prior to bricking it , to backup your device, use flatline (google it. sorry for not providing the link, this forum does not allow me to post links yet)

Buster99 said:
are you sure its apx?
also for cm11 based roms for the tf300t you need a special recovery (check the omnirom thread - thats the one im using, scannos twrp 2.6.3.0)
you cant run cm11 with older recovs since the PITs changed apparently (haven't read the man pages yet) but thats what i understood out of the omni thread
nvfalsh only works if you backed up your device prior bricking.
cheers & gl
Buster
Click to expand...
Click to collapse
As far as I can tell Vol+ gets me the black screen and recognized as a device in Windows 7 x64 as an ASUS APX Interface. I tried replacing the driver with every combination of NVIDIA, Google, Android SDK, Naked .72/.73 and no go. I've also tried ADB drivers and no luck there either.
Vol- doesn't bring up anything - screen just stays at ASUS logo. I dont get the recovery menu and can't get into TWRP (original) or CWM (after attempting to install). My mistake for not just sticking with TWRP (previously on 2.6.0.0) and using the scannos version.
It basically gets to the Device is Unlock, ASUS and NVIDIA logo and doesn't proceed further.
Any ideas?
Thanks in advance.

with the logos are there also 3(or 4) icons?
Sent from my GT-I9505 using XDA Premium 4 mobile app

Buster99 said:
with the logos are there also 3(or 4) icons?
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
neither - i dont ever get to that.

Same here - stuck at the first ASUS logo - in the left corner "the device is unlocked" and right corner the Nvidia logo.
Vol+ and power or Vol- and power - no effect.

I flashed an old recovery using adb commands in a newer twrp so is there any way to fix this?????
Sent from my LG-E980 using Tapatalk

Starting to develop for Xperia SP

Hi,
Some of you may recognise my name from around the forums, especially if you have had an Xperia device before. I started my first android developments on the Xperia Play and then continued onto the Xperia U. I then lost mass interest in development due to joining college and being overloaded with work due to a computing course. I was no longer able to contribute to any developments.
Now, I am in the second year of college and have dropped a subject I am finding myself with more free time so I have decided to start developing again, only this time I have an Xperia SP.
There's only one catch, the device I have is network locked to O2 and therefore I cannot unlock my boot loader, so most if not all of my work will be for those with a locked bootloader. I am mostly interested in creating custom ROMs based on stock and also creating my own applications and embedding them into the stock ROM.
And the flashy bar at the bottom, yeah I have ideas for that.
Developments for Xperia SP:
illumination app
~Keiran
Sent from my C5303 using Tapatalk

Thank you!
Sent from my C5303 using XDA Premium 4 mobile app

Thank you!
Thank you guy!
You have locked bootloader and you don't use fastboot
You should sell branded phone and buy no-branded

MrZender said:
Thank you guy!
You have locked bootloader and you don't use fastboot
You should sell branded phone and buy no-branded
Click to expand...
Click to collapse
I can't, it just means that I will only be able to developed for locked bootloader which is no problem really. All it means is that I cannot change the kernel image, using scripts I can mess about with the ramdisk though and may be able to boot CM on a locked boot loader if the stock kernel allows it.
Sent from my C5303 using Tapatalk

Glad to see you back in the game mate ! Too bad that you can't unlock your bootloader. Although I know that would not be a problem for you.
Sent from my C5303 using Tapatalk

Hi @KeiranFTW welcome to Xperia SP development!
I hope we can work together on a project I want to try when we get the Android 4.3 update, I'm not sure if it will be successful and I'm not sure if anyone else tried this on other devices, but I want to try.
Basically I want to build Android 4.3 that works with the stock Sony 4.3 bootloader. I already have my fork of CodeAurora up and running here, I call it recaf, it will 'simply' be a matter of satisfying the extra dependencies and other Sony changes.
Come chat on freenode IRC, I'm in #freexperia, or on my own at #recaf. (If I don't reply immediately it mean's I'm afk, but my irc bouncer keeps me logged in.)

adfad666 said:
Hi @KeiranFTW welcome to Xperia SP development!
I hope we can work together on a project I want to try when we get the Android 4.3 update, I'm not sure if it will be successful and I'm not sure if anyone else tried this on other devices, but I want to try.
Basically I want to build Android 4.3 that works with the stock Sony 4.3 bootloader. I already have my fork of CodeAurora up and running here, I call it recaf, it will 'simply' be a matter of satisfying the extra dependencies and other Sony changes.
Come chat on freenode IRC, I'm in #freexperia, or on my own at #recaf. (If I don't reply immediately it mean's I'm afk, but my irc bouncer keeps me logged in.)
Click to expand...
Click to collapse
I'm sure it is very possible, as there is a way that could work really, I could probably set it up as a dual boot. You would need the AOSP ramdisk in tar format somewhere on your phone and at boot time if you wish to boot AOSP then it would delete everything at / and extract that ramdisk to / and then continue boot process with that ramdisk.. as long as stock kernel is compatible.
Sent from my C5303 using Tapatalk

Welcome in SP section
Happy to see more real dev here

Well, maybe you could port kexec to our locked SP's? The main part of the module and binary is done, there is only one thing left - implementing proper hardboot and finally porting to our phones. I think some Xperia SP devs might help you. There's a thread in Z1 forums where delewer tries to get last parts of the job done. If you decide to start working on it, I want to be a alpha or beta tester
http://forum.xda-developers.com/showthread.php?t=2495152

Welcome mate, glad you are here can't wait to see your work I also had an xperia play and I'm pretty sure I had a few of your roms and mods installed at some point.
Sent from my C5303 using XDA Premium HD app

I have a few projects in mind at the moment:
1. Getting the 4.3 leak to boot on locked bootloader
2. When 4.3 is released get AOSP 4.3 to run also on locked boot loader - I will be working with @adfad666 on this - most priority
3. Maybe a stock based custom ROM - least priority.
Sent from my C5303 using Tapatalk

Maybe after booting AOSP 4.3 on locked BL you could try booting 4.4? Because it was possible in Xperia X8 "age of glory"(some devs booted 2.2 on 2.1 kernel if I'm not mistaken).

MrSteve555 said:
Maybe after booting AOSP 4.3 on locked BL you could try booting 4.4? Because it was possible in Xperia X8 "age of glory"(some devs booted 2.2 on 2.1 kernel if I'm not mistaken).
Click to expand...
Click to collapse
We could try.
The way I'm going to do it is hijack pre_hw_config.sh and then launch a script from there to determine whether to extract recovery ramdisk or AOSP ramdisk, then this will be extracted to /, and then everything will be unmounted and init will be started again to restart the boot process.
Sent from my C5303 using Tapatalk

I think I'll try to boot 4.3 today, with the method described in this thread: http://forum.xda-developers.com/showthread.php?t=2593806
I'll post my results later.

KeiranFTW said:
We could try.
The way I'm going to do it is hijack pre_hw_config.sh and then launch a script from there to determine whether to extract recovery ramdisk or AOSP ramdisk, then this will be extracted to /, and then everything will be unmounted and init will be started again to restart the boot process.
Sent from my C5303 using Tapatalk
Click to expand...
Click to collapse
Unfortunately pre_hw_config.sh doesn't exist in the 4.3 leak, so assuming that doesn't change when we receive the official update, we won't be able to use that.

adfad666 said:
Unfortunately pre_hw_config.sh doesn't exist in the 4.3 leak, so assuming that doesn't change when we receive the official update, we won't be able to use that.
Click to expand...
Click to collapse
then /system/bin/charger
Sent from my C5303 using Tapatalk

Well, pre_hw_config.sh doesn't exist even in stock 4.1.2. I think we should try with chargemon, not charger(because it's executed earlier). I tried booting DooMLord's DoomKernel ramdisk on stock kernel. Absolutely no luck. I don't even know what's wrong - after loading ramdisk, kernel panic occurs. Maybe someone more clever will figure it out.:silly:

I think I'm nearly there at hijacking the boot process to inject new ramdisk, I just have a little test that I will have to do later as I need to go out now.
What I'm going to do is use the same ramdisk as that's in the kernel but inject it again after removing anything, this way I don't need to change my ROM and I know that I can inject a new ramdisk. I'll upload my work to github later too so people can contribute
~Keiran
Sent from my C5303 using Tapatalk

Okay, so I've been successful in booting a custom RAMdisk, only problem I am experiencing is that the data partition is not being remounted when the new ramdisk is loaded, no idea why though.
Okay, done and fixed, sources are at https://github.com/keiranFTW/hijack-ramdisk-huashan
Get ready for exciting things coming now

KeiranFTW said:
Okay, so I've been successful in booting a custom RAMdisk, only problem I am experiencing is that the data partition is not being remounted when the new ramdisk is loaded, no idea why though.
Okay, done and fixed, sources are at https://github.com/keiranFTW/hijack-ramdisk-huashan
Get ready for exciting things coming now
Click to expand...
Click to collapse
I tried your method, but it has one bug - it doesn't symlink /data/media to /storage/sdcard0, so the data from internal memory isn't accesible through that path. Still amazing work, but I suggest you to change the format of ramdisk read by the script to .cpio, because it's easier to get from kernels. :good:

[Guide]Xperia KitKat 4.4.4 Rooting - Locked Bootloader/NO OTA Method

I managed to successfully root my Xperia M2 with KitKat 4.4.4 without unlocking the bootloader. Since the procedure is quite generic (and straightforward) I thought it would be useful for people with other Xperia devices if I post it here. Please take it as a guideline, since it may vary slightly between different Xperia devices. I suspect it will work also for the phones that will upgrade to Lollipop (as long as they had a Jelly Bean ROM available), maybe changing the rooting binaries in the rootkitXperia tool.
One can find the full procedure with all steps detailed and links to the SW needed in my original thread for the Xperia M2:
[Q&A][Root]Rooting with Locked Bootloader - NO OTA Method
In order to be able to apply this method the Xperia device must have an older ROM available, vulnerable to the "Towelroot" exploit .
Without it as far as I am aware no rooting is possible in a Kitkat 4.4.4 device with the locked bootloader.​
GENERAL GUIDELINES:
Be sure to have the full FTF for the stock ROM you are currently running
Flash with Flashtool only the kernel from a Jelly Bean FTF for your phone unchecking the wipe checkboxes
Reboot the phone:
The phone should bootloop, but it doesn't matter. The Linux kernel and adb are alive and thus the "Towelroot" vulnerability is exploitable by rootkitXperia
Run rootkitXperia. After the rooting it should get stuck when trying to reboot the phone(*). Interrupt it with CTRL-C
Flash back the kernel for the ROM in your phone
Reboot the phone
Manually run the command to have the RIC permanently disabled:
Code:
adb shell "su -c /data/local/tmp/install_tool.sh"
Reboot and enjoy your rooted phone!
(*) In some phones (Xperia Z?) rootkitXperia may not get stuck. If the phone reboots the rooting should be complete. Just flash back your original kernel and it should be done (untested).
Please note that this guideline covers some already known rooting methods. The difference is that it also covers the cases when the ROM bootloops and/or rootkitXperia gets stuck at the reboot, making it quite generic for all Xperia devices. It doesn't pretend to be a new guide for all Xperia, just a general one.
Xperia Phones confirmed working:
if you manage to root the phone using the kernel of a similar Xperia (like in the case of the Xperia M2 Aqua below) please report the phone name/model of your phone and of the phone you used the kernel from.
Xperia M2 D2303
Xperia M2 Aqua D2403 - With the M2 D2303 kernel
(to be expanded)

That's the well known method we are using since Xperia U.
As long as you have older fw (JB) you'll be able to root your device.
But...
I wouldn't bet on rooting L with this method.
Lollipop is new, fresh written firmware with a new kernel.
Code was updated on JB and new features were added when Google built KK...
L is something totally different...but we'll see soon..

Miche1asso said:
I managed to successfully..
Click to expand...
Click to collapse
Any help for Xperia E3 with lock bootloader..

funky0308 said:
That's the well known method we are using since Xperia U.
As long as you have older fw (JB) you'll be able to root your device.
.
Click to expand...
Click to collapse
I don't know if it was used already on Xperia U. I checked all around and I couldn't find this particular solution where the rooting is done with the hone bootlooping and one of rootkitXperia scripts must be run manually after restoring the KK kernel.
Particularly on Xperia M2 the suggested solution was to downgrade both kernel and system, root it and then upgrade via OTA. Which was something I didn't fancy at all. Still now I see people trying to apply rootkitXperia on any Xperia KK 4.4.4 (which will never work, as I discovered myself). So I made it available in the general section as well for people with less popular Xperias who are banging their heads like I did for a couple of weeks (honest):
But sure, the downgrade is a requirement. At the moment 4.4.4 seems unbreakable.
.
But...
I wouldn't bet on rooting L with this method.
Lollipop is new, fresh written firmware with a new kernel.
Code was updated on JB and new features were added when Google built KK...
L is something totally different...but we'll see soon..
Click to expand...
Click to collapse
It's still Linux. With the bleeding SELinux fully enabled, though. It may take some tampering, but I suspect it will be a matter of replacing/adding the rooting binaries in rootkitXperia. Chainfire already has them available I understood. If it will be possible to inject them flashing the JB kernel half of the job has done. Still, I'll rephrase it in my first post, it could be be too optimistic.

imElectronica said:
Any help for Xperia E3 with lock bootloader..
Click to expand...
Click to collapse
Since it came with 4.4.4 and the HW is similar to the one of the M2 (same CPU at least) you may try this method flashing the M2 kernel attached in my first thread. In case it goes all wrong you should be able to flash back the original kernel. At least so I've read people "unbricked" their phones after fashing a wrong kernel.
But I am not sure about it. I take no responsibility. Do it at your own risk

I thought that ADB wouldn't work if the phone didn't boot completely or at least it didn't go past booting the kernel. That's quite a suprise for me and I'll surely test it on the next xperia I'd have to root. You just made my concerns about rooting 5.0 Sony firmwares on LB gone, thanks a ton mate!
BTW. That's literally the fastest written news I ever seen on the xda portal, like seriously, it was posted the very same day, just a few minutes ago.

olokos said:
I thought that ADB wouldn't work if the phone didn't boot completely or at least it didn't go past booting the kernel. That's quite a suprise for me and I'll surely test it on the next xperia I'd have to root. You just made my concerns about rooting 5.0 Sony firmwares on LB gone, thanks a ton mate!
Click to expand...
Click to collapse
You're very welcome!
BTW. That's literally the fastest written news I ever seen on the xda portal, like seriously, it was posted the very same day, just a few minutes ago.
Click to expand...
Click to collapse
Why, did I make the portal? Oh, i see it now. In the bottom right section. That's cool! Now I am happy. Thanks.

Does this mean I can root my Xperia Z3 d6616 on 4.4.4? You may have just won all the internets.

Known method and it works. I used it on the Xperia NovaThor line
Also you can add this. If your phone is working weird (buggy or sudden battery drops) just wipe the cache. It is known problem when flashing older version of android (ROM/kernel) and then flashing back the new one. In this case you are doing exactly that. Right now there are no recoveries for locked bootloader but you can use the ADB command or some terminal application on your android.
Option 1. Using the ADB (easiest):
Code:
adb shell
su
cd /data/dalvik-cache
rm *
exit
adb reboot
Option 2. Using terminal
Code:
su
cd /data/dalvik-cache
rm *
exit
After that reboot your device. It will take longer than normal but it's ok
---------- Post added at 02:41 AM ---------- Previous post was at 02:39 AM ----------
HORiZUN said:
Does this mean I can root my Xperia Z3 d6616 on 4.4.4? You may have just won all the internets.
Click to expand...
Click to collapse
No because Z3 doesn't have a jellybean ROM/kernel so you can't use this on your device

Similar method when rooting Xperia Tablet Z and a bit similar when rooting my Xperia neo V before.. I don't encountered boot loop....

DavidMKD said:
Known method and it works. I used it on the Xperia NovaThor line
Also you can add this. If your phone is working weird (buggy or sudden battery drops) just wipe the cache. It is known problem when flashing older version of android (ROM/kernel) and then flashing back the new one. In this case you are doing exactly that.
Click to expand...
Click to collapse
I think the dalvik caches get modified when a new /system (with a different version of the apps in /system/app) gets installed.. Just changing the kernel shouldn't really affect the dalvik caches.
Right now there are no recoveries for locked bootloader but you can use the ADB command or some terminal application on your android.
Option 1. Using the ADB (easiest):
[...]
Option 2. Using terminal
[...]
After that reboot your device. It will take longer than normal but it's ok
Click to expand...
Click to collapse
or you can just type from the terminal:
Code:
adb shell su -c "rm -r /data/dalvik-cache; reboot"
Otherwise what I usually do is to remove the /data/dalvik-cache folder from a root file manager. /data/dalvik.-cache gets re-created at boot time. Not that I've ever really seen any benefit on doing that. Especially in Kitkat any time the system apps get modified Android should rebuild all of them at boot time. But yeah, one never knows. Hopefully ART in Lollipop will end this crap.
donedos said:
Similar method when rooting Xperia Tablet Z and a bit similar when rooting my Xperia neo V before.. I don't encountered boot loop....
Click to expand...
Click to collapse
Yeah, I know. The guide is more specific for when the ROM bootloops and/or rootkitXperia gets stuck at the reboot, like it happens in the Xperia M2. In that case people where getting stuck, or at least I couldn't find any guide telling what to do. I'll specify it in the main post.

Delete

tRippinthehead said:
Delete
Click to expand...
Click to collapse
Sorry to ask in here but its impossible to get a reply in the Z2 Tablet forum. Any idea where I can download a Jellybean FTF for my device and then the 4.4.4 FTF its running atm?
Would be greatly appreciated!
Dowloading the FTF from: http://xperiafirmware.com/8-firmware/50-sony-xperia-z2-tablet-wi-fi-sgp511, anyone know if SGP511 is compatible with SGP512 (I know they're both WiFi international versions)
I found this: http://forum.xda-developers.com/showthread.php?t=2768951 But its only a 7mb download? Is the system.img the kernal?

GalaxyWhy said:
Sorry to ask in here but its impossible to get a reply in the Z2 Tablet forum. Any idea where I can download a Jellybean FTF for my device and then the 4.4.4 FTF its running atm?
Would be greatly appreciated!
Dowloading the FTF from: http://xperiafirmware.com/8-firmware/50-sony-xperia-z2-tablet-wi-fi-sgp511, anyone know if SGP511 is compatible with SGP512 (I know they're both WiFi international versions)
I found this: http://forum.xda-developers.com/showthread.php?t=2768951 But its only a 7mb download? Is the system.img the kernal?
Click to expand...
Click to collapse
First of all, use XperiFirm (google it) and download the program. Find your device and download the necessary firmwares. The second link you posted is just a kernel

What about phones without JB roms released, ex: Xperia C3? It was released on KK 4.4.1 and I think that no kernels are available for this phone. I'm asking 'cause I want to root my phone but is almost impossible using all known methods .

Dominator_666 said:
What about phones without JB roms released, ex: Xperia C3? It was released on KK 4.4.1 and I think that no kernels are available for this phone. I'm asking 'cause I want to root my phone but is almost impossible using all known methods .
Click to expand...
Click to collapse
Ok, this is the situation: if the phone has a "brother" with the same identical SoC which came with a JB ROM flashing the kernel (and only the kernel) from the JB FTF of that ROM may do the job. It officially worked on the Xperia M2 Aqua D2403 using the D2303 kernel. As long as the phone manages to boot the kernel and abd is alive (with all relevant Unix commands) the rooting should be possible (and the phone won't be bricked at all. It just has the kernel not matching the modules, libraries and else in the ROM).
This may apply for example to the Sony Z3 using the Z2 JB kernel for the rooting (although the SoC in this case are slightly different). Or the Xperia E3 using the M2 kernel. But no one tested these scenarios yet, so I take no responsibility if anything goes wrong. It is at your own risk.
Still, my experience with the Samsung has been that after flashing the wrong kernel was always possible to recover the phone flashing back the official ROM (with Odin in that case). I have no experience of "soft bricked" phones with the Xperia, so I can't bring my personal experience on this.

Miche1asso said:
Ok, this is the situation: if the phone has a "brother" with the same identical SoC which came with a JB ROM flashing the kernel (and only the kernel) from the JB FTF of that ROM may do the job. It officially worked on the Xperia M2 Aqua D2403 using the D2303 kernel. As long as the phone manages to boot the kernel and abd is alive (with all relevant Unix commands) the rooting should be possible (and the phone won't be bricked at all. It just has the kernel not matching the modules, libraries and else in the ROM).
This may apply for example to the Sony Z3 using the Z2 JB kernel for the rooting (although the SoC in this case are slightly different). Or the Xperia E3 using the M2 kernel. But no one tested these scenarios yet, so I take no responsibility if anything goes wrong. It is at your own risk.
Still, my experience with the Samsung has been that after flashing the wrong kernel was always possible to recover the phone flashing back the official ROM (with Odin in that case). I have no experience of "soft bricked" phones with the Xperia, so I can't bring my personal experience on this.
Click to expand...
Click to collapse
Anyone willing to try this? Maybe we can set up a donation thread for someone to try it?

Dominator_666 said:
What about phones without JB roms released, ex: Xperia C3? It was released on KK 4.4.1 and I think that no kernels are available for this phone. I'm asking 'cause I want to root my phone but is almost impossible using all known methods .
Click to expand...
Click to collapse
It's not about Jelly Bean firmware availability for the device. Towel root even works directly with KitKat, provided the kernel build date should be before 3rd June, 2014.

Mmm i tried many times with towelroot but isn't working. However as you said is better to have a non rooted device than a hard bricked one hahaha

Moist said:
Anyone willing to try this? Maybe we can set up a donation thread for someone to try it?
Click to expand...
Click to collapse
Don't ever flash wrong kernels which isn't meant for your device. It might hard brick. 'No root' is better than 'hard brick'ed device.

How to root (SGP561) Z2 Tablet Verizon, new update 23.0.1.E.0.208 (4.4.4)

Hi guys, finally I've found a way to get the latest update 23.0.1.E.0.208 (4.4.4) without losing root on this tablet.
The method is the same as the method here (http://forum.xda-developers.com/xperia-z2/general/4-4-4-creating-rooted-update-package-t2933155), but we will use the files for Xperia Z2 Tablet Verizon instead of files for Xperia Z2.
First, you MUST BE on an older version (17.1.D.0.437) with root and XZDualRecovery
You need these files:
1. New 23.0.1.E.0.208 update FTF file (you can use XperiFirm to get it)
2. PRFCreator v0.5.zip (I tried the later version v0.8 but it didn't work, so better to use v0.5)
3. Latest stable SuperSU update package
4. XZDualRecovery flashable patched version (in the attachment) (note that the original version from [NUT] will not allow you to mount system rw)
Then follows step 4 to 11 in the instructions in the above thread for Xperia Z2 and replace all the files for Xperia Z2 with the files you've just got.
Good luck!

thanks for this, will try it this week...
noticed any issues with this update on the verizon tab?

Is it possible to flash back to 4.4.2, to root? Sadly, mine came with the newest update.
Sent from my SGP561 using XDA Free mobile app

https://mega.co.nz/#!VZYHRAKT!wky8U_6G9aB4XctdfKMIaJQZtdlnWTtNv0pNLlgh0AM here is the ftf file for the older version.

Worked like a charm! Thank you for posting this.

How come this cannot be posted as a flashable zip? Why do we need to create our own file? Just curious.
Sent from my SGP561 using XDA Premium HD app

smarcisin said:
How come this cannot be posted as a flashable zip? Why do we need to create our own file? Just curious.
Sent from my SGP561 using XDA Premium HD app
Click to expand...
Click to collapse
My internet connection sucks. It takes long to upload large files.

Trying to do this, however it seems we need a custom recovery already installed. Trying to install the XZDualRecovery from the installer file I downloaded but it just hangs at libdvm opened. Any other way to install a custom recovery so I can follow the rest of the guide to get my replacement tab rooted?

Varekai said:
Trying to do this, however it seems we need a custom recovery already installed. Trying to install the XZDualRecovery from the installer file I downloaded but it just hangs at libdvm opened. Any other way to install a custom recovery so I can follow the rest of the guide to get my replacement tab rooted?
Click to expand...
Click to collapse
Sounds to me like you need to flash the old ftf first, then root and then install the custom recovery. Root only works on the older firmware linked above.
Sent from my SGP561 using XDA Premium HD app

Thanks, I thought you had to have a recovery already installed for that. Downloaded everything I need plus old FTF file, can't seem to get it to work right. Think I am having driver problems even tho it works fine in fastboot mode through ADB. Can't get Sony PC companion to work either even tho I've downloaded pretty much every driver I can find for it. I'm on Windows 8.1

I never managed to get it to work on windows 8.1 by had a windows 7 laptop laying around and that worked fine. I would recommend finding a non 8.1 computer. Good luck.
Sent from my SM-G900V using XDA Premium HD app

Got it working. I didn't know I had to have the unknown sources checked. Also I didn't realize I was plugged into a 3.0 port in the back of my PC, so that didn't help.
Now that I'm on the old version and rooted, I saw some people had success with updating to the newest update for VZW and keeping root. Can anyone else confirm this? I have TWRP and everything on my HTC, but my tablet I would rather not mess with it as much. The steps in this guide are pretty involved.

Varekai said:
Got it working. I didn't know I had to have the unknown sources checked. Also I didn't realize I was plugged into a 3.0 port in the back of my PC, so that didn't help.
Now that I'm on the old version and rooted, I saw some people had success with updating to the newest update for VZW and keeping root. Can anyone else confirm this? I have TWRP and everything on my HTC, but my tablet I would rather not mess with it as much. The steps in this guide are pretty involved.
Click to expand...
Click to collapse
I am on the newest firmware and rooted, so I can confirm that it works.
It's not as bad as it seems. Just follow the steps and you will be a better human for it! Happy hacking and debloating.
Sent from my SGP561 using XDA Premium HD app

Yup just did this, everything is working great, thanks!

My camera doesn't work after updating. Every time I hit the capture button it just freezes. I'd like to just wipe and do a clean install. Can I just do it in TRWP? Will I lose root?
Sent from my SGP561 using XDA Premium HD app

smarcisin said:
My camera doesn't work after updating. Every time I hit the capture button it just freezes. I'd like to just wipe and do a clean install. Can I just do it in TRWP? Will I lose root?
Sent from my SGP561 using XDA Premium HD app
Click to expand...
Click to collapse
Should be fine, I wiped mine after the whole process and had no problems at all.
Sent from my SM-G900V using XDA Premium HD app

There was a leaked Lollipop update I saw today on XperiaBlog. Could this method be used to update?
Update: worked like a charm. Running lollipop with root and nuts dualboot

tmkhoa said:
https://mega.co.nz/#!VZYHRAKT!wky8U_6G9aB4XctdfKMIaJQZtdlnWTtNv0pNLlgh0AM here is the ftf file for the older version.
Click to expand...
Click to collapse
Is it possible to have this uploaded again since it's no longer available. ftf file for 17.1.D.0.437
Also PRFCreator v0.5.zip since the earliest one available is v0.7.
Thanks!

Anybody...

AddictedToGlass said:
Anybody...
Click to expand...
Click to collapse
How about this one:
https://mega.nz/#!lAQFQZ7R!wky8U_6G9aB4XctdfKMIaJQZtdlnWTtNv0pNLlgh0AM
Why PRFCreator v0,5?
freealta said:
Is it possible to have this uploaded again since it's no longer available. ftf file for 17.1.D.0.437
Also PRFCreator v0.5.zip since the earliest one available is v0.7.
Thanks!
Click to expand...
Click to collapse