Straight Rooted Lollipop Method? - Xperia Z3 Compact Q&A, Help & Troubleshooting

I was wondering if this would be possible:
Use Recovery to flash a rooted stock Lollipop system partition, then flash everything else from stock FTF, but skip system. This would overwrite the (currently useless) recovery with stock content, but you'd be rooted.
Forgive me if that's what the current method does. I'm trying to avoid a compromised/non-functional/boot-looping recovery if the current method installs one, but if the recovery in that method simply overwrites itself with stock then I'm fine with that. I just don't understand what's installed in the recovery sequence when you finish following the current method on a LB device.

i dont think it will be possible since sony is really good at patching holes in their system

I've tried, it doesn't work.

Related

[Q] Sort Me out on 4.4.3 update

The more I read the more confused I get. Could someone sort me out?
<complain>I got the moto x because of the quick OTA updates. Now it seems that because I installed TWRP and froze a few apps with TB that this feature is totally borked!</complain> is that correct? I cannot update without stock recovery and all the original apps installed / unfrozen?
In my predicament would the easiest thing to do be
1. Unfreeze any system apps I've frozen.
2. Use msfastboot to reflash stock recovery?
3. Accept the OTA or somehow flash it manually (I'm not sure about this last one see below)
I accidentally accepted the OTA download and now it bugs me to install. I won't install because it just reboots into TWRP. But it does keep prompting me to set at time to install. If I simply flash stock recovery I think i will still get this prompt. Would that be the easiest way to go?
Thanks for any advice.
pairustwo said:
The more I read the more confused I get. Could someone sort me out?
<complain>I got the moto x because of the quick OTA updates. Now it seems that because I installed TWRP and froze a few apps with TB that this feature is totally borked!</complain> is that correct? I cannot update without stock recovery and all the original apps installed / unfrozen?
In my predicament would the easiest thing to do be
1. Unfreeze any system apps I've frozen.
2. Use msfastboot to reflash stock recovery?
3. Accept the OTA or somehow flash it manually (I'm not sure about this last one see below)
I accidentally accepted the OTA download and now it bugs me to install. I won't install because it just reboots into TWRP. But it does keep prompting me to set at time to install. If I simply flash stock recovery I think i will still get this prompt. Would that be the easiest way to go?
Thanks for any advice.
Click to expand...
Click to collapse
1. - You do not need to unfreeze apps. The apps are still there untouched in the file system, and in recovery the OS hasn't booted enough to know that the apps are "frozen". By the way, frozen apps are basically just tagged in the OS as not available....so with the OS not running (just recovery is), they aren't "frozen" in recovery.
2. - Yes, fastboot to flash stock recovery. Boot to bootloader mode, fastboot flash recovery recovery.img (you don't need mfastboot for recovery, though you can still use it.)
3. - Accept the OTA. Since yours is trying to install, you should be able to boot to bootloader, flash stock recovery and on reboot it will start the install of the OTA. When done and booted.....reflash TWRP if you like.
That would be the way to go, yes.
Flash stock recovery and try to upgrade. If you cannot, try to unfreeze all sys apps. That should do it. ?
OK. So maybe not such a huge PIA as I had thought. I will track down the recovery file and read the instructions for flashing.
Thanks
@pairustwo
Every time another OTA comes out, people who modify their phones ask the same question. I've written up a FAQ based on the past OTA's.. -> http://mark.cdmaforums.com/MotoX-OTA.html if you want to read it to get more info.
Part of the issues you are talking about when taking an OTA is that the OTAs want to patch and replace only SOME files on your phone, so it checks to make sure the update is for your phone and its android version by evaluating certain files on the phone, that they exist and that their check sums match what the update expects.
i.e. change/modify/delete files the OTA update checks before installing, and the OTA will refuse to install.
If it didn't do this, the wrong update could possibly flash to your phone, replacing files with incompatible versions and making a big mess.
So yeah, "getting back to stock" (or as close to it as you can) is always recommended before taking an OTA so the "check" doesn't fail and prevent the OTA from applying.
In the past, freezing apps with Ti Backup was enough of a modification to cause the OTA's to fail. So often it is still suggested to un-freeze those done with TiBackup.
The OTA zip file (as downloaded) will only flash from Stock Recovery. TWRP and CWM for example don't properly process and flash them, so if you try to install when stock recovery is NOT on your phone, you get stuck in a bootloop. Using mFastboot to flash stock recovery back on is fine for those with unlocked bootloaders. Locked Bootloader users, is another matter.
There is a way "side load" the OTA, IF you have stock recovery, your phone hasn't received the push from Moto or your Carrier yet, and the OTA Zip file has leaked. But it still requires you get back to stock, etc. just as if you were getting it OTA.
So I've tried to flash back to stock but am having an issue. Does anyone have a link to a stock recovery image? Maybe the one I have is corrupt.
pairustwo said:
So I've tried to flash back to stock but am having an issue. Does anyone have a link to a stock recovery image? Maybe the one I have is corrupt.
Click to expand...
Click to collapse
Answered here -> http://forum.xda-developers.com/moto-x/moto-x-qa/dead-android-red-exclamation-t2778189
and I made this -> http://mark.cdmaforums.com/MotoX-EnterStockRecovery.htm

OTA update

Hi guys!
I've finally received 4.4.4 notification to update my German Moto x!!
I'd like to know one thing before I proceed.. If I update, will I have to root again the phone?
My phone has unlocked bootloader so there is no problem, but right now I'm on holiday and I don't have a pc to root it again..
Thanks a lot!
I have not upgrade to 4.4.4 yet.
I don't think you need to root again
Thanks!
I've read some other user just flashed the stock recovery, installed the ota and flashed back twrp recovery..
Others instead use fwz method
I think I'll wait until I'm home just to be sure I need my phone during the holidays!
daede86 said:
Thanks!
I've read some other user just flashed the stock recovery, installed the ota and flashed back twrp recovery..
Others instead use fwz method
I think I'll wait until I'm home just to be sure I need my phone during the holidays!
Click to expand...
Click to collapse
Hi, i was wondering the same thing. Is there a method for someone to create an update for rooted phones?
Also can you link me to the threads for flashing back to stock and what this fwz is?
thank you
Here you can find some info about FXZ (sorry for my typo)
http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
In the same thread you can find the stock recovery, a user posted it. Just search stock recovery in the thread and you'll find it!
I'm not the right person to help you in detail.
I'm not an expert user
In the meantime I froze motorola OTA app to hide the update notification..
Guys, before anyone gets in trouble....there is no FXZ for the german (or any asia/european) Moto X's yet.
The only one released is the Verizon one....so DON'T flash the verizon FXZ.
You need to flash stock recovery back, and if the phone STILL won't take the OTA, also use "mfastboot" to flash system.img from the 4.4.2 FXZ (which IS released for the european/asia models). Afterwards, the OTA should install without fail.
You WILL need to re-flash TWRP no matter which method you use. You will also need to re-root IF you flash the system.img from the 4.4.2 SBF in order to be able to accept the OTA (you only flash system.img from 4.4.2 if the OTA fails after you have flashed stock recovery - it normally means you have modified /system in some way, and restoring the full system.img fixes this issue).
Good Luck - Remember: Don't flash the Verizon 4.4.4 FXZ to your non-Verizon phone. Not a good idea...
If your phone doesn't vary from Stock but rooted, you can get away with flashing stock recovery back on there and taking the OTA. (OTA wont install via custom recovery like TWRP, CWM, etc). And if that is the case, you will retain root. You can optionally flash TWRP back on there.
If you have Xposed installed, it will need to be disabled or removed for the OTA install to work.
It is when you mess with stock files in /System or other folders on the phone.. i.e. remove, rename, etc. files from them, that you may also need to flash system.img and possibly other parts. This is due to verification checks in the OTA zip itself. If you have to flash those parts, you will have to re-root. Not an issue if you have an unlocked bootloader.
Thanks a lot for your help and clarification!!
I knew I wasn't the right person
Guys just to be sure of the right process..
-download the actual sbf of my phone
-extract recovery.img from the sbf
-remove xposed
-flash the recovery with flashify
-take the ota
-flash back twrp recovery
Am I right?!
Thanks a lot
daede86 said:
Guys just to be sure of the right process..
-download the actual sbf of my phone
-extract recovery.img from the sbf
-remove xposed
-flash the recovery with flashify
-take the ota
-flash back twrp recovery
Am I right?!
Thanks a lot
Click to expand...
Click to collapse
IF you do not vary too much from Stock (i.e. didn't remove, rename or replace any "stock" files on your phone), then yes.
Oh, for Xposed, there is a disabler ZIP you can flash from custom recovery located in /storage/emulated/0/Android/data/de.robv.android.xposed.installer (or /SdCard/Android/data/de.robv.android.xposed.installer ) instead of removing it, as sometimes removing it doesn't undo all the changes.

[Q] Decrypt if I'm already rooted with unlocked boot loader??

So I have a T-mo rooted Nexus 6 running stock rom and kernel presently. I would like to decrypt the phone as I've heard/read I will see an improvement in both performance and battery life. So first question is what would be the best/easiest method to do this and second will I lose root and have to re-root after decrypting. Thanks in advance for any help.
Basically you will have to flash a different boot image that disable the encryption flag.
This will require you to completely wipe your device and start over. Yes, you would have to re-root but if you know how to flash a stock no-encrypt image then rooting is easy and simply requires you to flash the current SuperSU zip from recovery once you are all set up.
Basically follow the long version of this guide. Technically you don't need to flash completely stock and couold just follow the guide in the next section but if you have to factory reset anyway I would want to start fresh:http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
But use this no-encrypt boot image instead that matches the stock google rom you flash:http://forum.xda-developers.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715
Once that is done you can flash recovery (or simply boot into TWRP temporarily if you want to keep the stock recovery) and flash Supersu.zip from here and then you're rooted again. I think you could also flash TWRP in the first step above when you are going back to stock but I usually do it at the end for some reason:http://forum.xda-developers.com/showthread.php?t=1538053
Thank you so much

How to encrypt with TWRP recovery installed

I realised I haven't re-encrypted my Titan yet since wiping it to correct some issues but when I tried, it just reboots. I've run into this issue before, which is caused by having a custom recovery (in my case TWRP) installed as Android uses the stock recovery to do the encryption. I don't particularly want to mess around flashing back the stock recovery and then back to TWRP, so is there a way to encrypt the phone without doing that, perhaps using ADB?
Bump. If the only way to encrypt it is to flash back the stock Recovery, could someone point me to where I can find some instructions on doing this and a download link please?
EDIT: Never mind, I found this now http://forum.xda-developers.com/showthread.php?t=2635706 so I'll use that to flash stock recovery.

Do I have to flash TWRP everytime using Flashtool if I need to access it?

Newbie to the 'Dark Side of the Android World' and just curious.
well, after rooting your phone you only need to flash custom recovery once then you can access it as many times as you want
Your question is a little bit weird. Can you link me to a place of reference? Or at least explain what you are actually wanting to do?
Flashing TWRP is a one-time action, once flashed it remain on your Xperia SP. However, FlashTool doesn't offer flashing TWRP to other partitions via fastboot other than the "boot" partition. So far, the only way to correctly flash TWRP is via a recovery.
If you indeed flashed TWRP image via FlashTool, then you are actually putting TWRP into your boot partition, and this makes your device to only boot into TWRP infinitely until you flash a ROM (which will of course again override the boot partition).
The reason why I asked is because this method of accessing recovery is posted in my custom ROM guide, so I want to know if you get this kind of idea from my guide.
Thanks

Categories

Resources