Hello,
If I ask stupid questions, please, be patient with me, I just want to make sure I don't mess up things.
A long time ago I rooted my phone using https://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343, but at that time I didn't want to flash lolipop - I have been staying with 4.4.4 until now.
Now I would like to upgrade to let's say Marshmallow, stock version, and keep root. I have a very old TWRP recovery installed on the phone. I remember the original rooting process was rather complicated, but now it seems to me, that it should be much simpler, I guess this is what I should do:
On PC:
1. Install original z3c drivers
2. Install latest flashtool
3. Use flashtool to install latest TWRP recovery, like from here: https://forum.xda-developers.com/z3-compact/general/d5803-z3c-aries-twrp3-0-t3543113
4. Download pre-rooted Marshmallow image, however, I am not sure if these https://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706 are pre-rooted
5. Put the image on the sd card and install it directly from the TWRP recovery
Am I right?
Related
Hi guys,
I can't find a clear explanation of this. So I would like your help. For the time being, I'm primarily interested in rooting and not so much in a custom ROM. I'll just tell you what I do and we could take it from there. Assume an unlocked boot loader.
1. I flash the HTC recovery partition with CWM or TRWP
2. I root the phone.
3. I enjoy apps that require root.
When a HTC OTA update arrives:
1. I extract recovery.img from the OTA zip (and I use OTA-root keeper too to regain root after the OTA-update has been applied)
2. I flash HTC's recovery.img to the recovery partition (just stating the obvious)so that the phone again has the stock recovery
3. I update the phone
4. I reflash TRWP or CWM to the recovery partition
5. I use OTA-rootkeeper to regain root.
Now with Sony, I've read there is no separate recovery partition. So the bootloader does NOT load the recovery directly when asked to. Instead it loads the regular kernel which in turn loads the recovery. So it appears the kernel needs to be modified and the recovery image needs to be stored somewhere. I've picked up some terms like ELF and Ramdisk but I'm not getting the bigger picture here.
Could you please tell me what the implication are? With HTC, I can easly apply the OTA-updates using my above method and not loose any apps or data. With Sony, it appears I need to do much more?
http://forum.xda-developers.com/showthread.php?t=2439328
Basically
Download flashtool from flashtool.net
Use it to flash a .534 FW (Download any one of them from the megacollection thread in the general section)
Google Bin4ry root many android to root the phone
Let the phone update OTA
Install Dual recovery from here then update it using the package in post #321 of that thread
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.
Hello
I have unlocked BL and rooted.
I've been trying to install CM12 on my Xperia V but everytime I'm in recovery and trying to flash CM12 it just aborts in the middle of it, and if i remember it gives an error a long the lines of "device is mint, rom isn't" I tried this rom http://forum.xda-developers.com/xpe.../rom-cyanogenmod-12-neo-s-homebuilds-t2967819
Since that pretty much bricked the phone Im back on stock JB [4.3] and I actually tried it twice, and no luck. Haven't tried any other roms since re-rooting and installing cwm/twrp is such a pain with xperia V and im not interested in anything else other than CM11/12.
I tried search but no luck
So, the question is, whats the most painless way to get CM11/12 on my phone, and what do I have to keep in mind while doing it. I'm very new to the phone and haven't figured out everything that I need to know I suppose.
Heres some "about phone"
Model : LT25i
Android ver: 4.3
Kernel ver: 3.4.0
Build number: 9.2.A.2.5
Either remove the first line in my rom zip/META-INF/com/google/android/updater-script (this will disable device verification, so do so at your own responsibility), then repack the rom zip and flash - or fastboot flash my rom's boot.img before installing the zip itself.
WhiteNeo said:
Either remove the first line in my rom zip/META-INF/com/google/android/updater-script (this will disable device verification, so do so at your own responsibility), then repack the rom zip and flash - or fastboot flash my rom's boot.img before installing the zip itself.
Click to expand...
Click to collapse
Thanks for the fast answer. So I'll just root and install twrp yet again, then flash your boot.img in with flashtool and THEN wipe/factory reset from twrp and install your ROM, right ?
villur700 said:
Thanks for the fast answer. So I'll just root and install twrp yet again, then flash your boot.img in with flashtool and THEN wipe/factory reset from twrp and install your ROM, right ?
Click to expand...
Click to collapse
Actually, no need for root and twrp. Just go ahead, flash the kernel, then reboot to recovery and follow the installation steps in my CM12 thread
I just unlocked my bootloader using Sunshine and then I flashed twrp and when I went to reboot my phone twrp asked if I want to install SU so i hit yes and it went through its process and now my phone will not boot. Is there anything I can do?
Edit: Thanks for the responses TheSt33v fixed my problem.
Hopefully you unlocked the bootloader before taking the latest OTA to marshmallow?
He couldn't have used Sunshine on Marshmallow. He had to be on Lollipop.
ylevanSnavely said:
I just unlocked my bootloader using Sunshine and then I flashed twrp and when I went to reboot my phone twrp asked if I want to install SU so i hit yes and it went through its process and now my phone will not boot. Is there anything I can do?
Click to expand...
Click to collapse
Go to the development section of the Droid Turbo forum and pick out the rom you want. If you downloaded a stock lollipop rom, download SuperSU from here: https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip. If you downloaded the stock marshmallow rom, download this version of supersu in addition to the one above: https://download.chainfire.eu/751/SuperSU/. If you downloaded a CM-based rom, you don't need supersu. Boot into TWRP. Use TWRP to wipe system, cache and dalvik cache (this will not wipe any of your apps, pictures, or other user data). Plug your phone into your computer and transfer both the rom and supersu(s) that you downloaded to the phone. If you are installing a stock lollipop rom, flash the rom followed by the supersu package. If you are installing the marshmallow stock rom, flash in the order of rom, older version of supsersu, newer version of supersu. If you are installing a CM-based rom, just flash that.
The first boot can take a very long time. Be patient. Wait at least 10 minutes before you give up. Also, if you're installing a different version of android than the version that is currently on there, you'll need to wipe your data with a factory reset first. So if you need to back things up, I would recommend putting the stock lollipop on there first, backing everything up, and then installing whatever you want afterwards.
I followed this post and everything looked fine but found out that recovery isn't working.
For my first attempt I used a pre-rooted fw (23.5.A.1.291 - Unbranded - CE1 from here).
I tried again, everything from scratch, this time creating my own pre-rooted fw with dual-recovery and supersu. I was able to start recovery to flash the fw but this time the phone doesn't seem to be rooted (no sign of superSu anywhere).
Any ideas?
Install SuperSU from playstore additionally. It happens sometimes that the app was not installed or didn't show up.
Otherwise
But I would recommend this way: https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
Start from scratch:
Flash full unrooted original 291 via flashtool and then follow the linked instuctions. Note the needed kernel change.
Keep in mind to rename file extension from kernel575.zip to kernel575.ftf and kernel291.zip to kernel291.ftf (ONLY rename - no unzipping)
Afterwards flash SuperSU.zip from recovery.
Yes, I managed following this other post.
Thanks.