Database Users

[TUT] Flash your first ROM | EXT4 | Speed up GPS | Remove Music Lag *noob-proof*

so! you've just rooted your HTC Desire Z (HTC G2, HTC Vision), and you S-OFF'ed it.
now you have Clockworkmod recovery, and an old Froyo Android ROM. want to upgrade? do NOT use the normal OTA update (don't use the normal "check for system update" button), because you may risk losing root, and have to re-root your phone.
NOTE: "►" is what you should do, "►►" is a comment on what's happening.
Preparations to flash a ROM:
►first pick a ROM from the Development section
►put it on your sdcard, it should be a zip file.
►make sure PC10IMG.zip isn't on your sdcard. (delete it, or put it in a folder)​
Click to expand...
Click to collapse
Booting to recovery:
►go to settings, power, and make sure fast boot is off
►turn off your phone: by holding the power button, and choosing power off.
►press and hold the volume DOWN button, and press the power button... keep pressing the volume down button until you see a white background with text on it.
►►you are now in HBOOT, or Bootloader.
►►now to flash your first ROM, you'll have to go to recovery to make the installation
►press volume DOWN to select "RECOVERY"
►press power to select it
►►the phone will now boot to recovery (Clockworkmod)
Another way is to use ADB:
►Plug your phone to your PC
►check that USB debugging is on, in settings, applications, development.
►open cmd on PC
►type the following:
Code:
adb reboot recovery
​
Click to expand...
Click to collapse
OPTIONAL Full Backup:
►►in recovery please do NOT use the power button for selections. please use the trackpad.
►go to backup and restore.
►press the backup button.
►►this will backup EVERYTHING except sdcard, it will backup your apps and their data, your settings, and your themes/launcher customizations. just in case anything wrong happens.
►►backup will take about 5 minutes.
►►at most, this will take 1.5GB in size (i had sense, and 200 apps installed).​
Click to expand...
Click to collapse
​
Wiping, and flashing the ROM:
►now go to wipe data/factory reset, and wipe your phone
►►this will wipe the /data partition on your phone, to flash a new ROM.
►go to the first menu, and select install from sdcard
►press choose zip from sdcard
►locate your ROM, and select it
►select "yes" and click it.
►►it will start installing.
►once finished, go back to the first menu, and click reboot now.
►let the phone boot (give it about 5 minutes).
►finish the first setup.
►and reboot.​
Click to expand...
Click to collapse
Congrats you have flashed your first ROM!
Troubleshooting:
Bootlooping:
►►is your phone bootlooping?
►go to recovery as shown above, and wipe your phone.
►OPTIONAL: reflash the ROM as shown above.​
Click to expand...
Click to collapse
No Gmail, Playstore, Google account:
►find Gapps HERE
►►GB is Gingerbread (2.3.x) ICS is Ice Cream Sandwich (4.0.x) JB is JellyBean (4.1.x)
►put the Gapps zip file on sdcard
►go to recovery
►flash the Gapps zip file​
Click to expand...
Click to collapse
Converting to EXT4 file system:​
Lots of ROMs now have EXT4 support, EXT4 file system is faster that the old EXT3/2 file systems. the converting process is easy. but be aware that converting to EXT4 requires a FULL WIPE!... you have been warned
Installing 4EXT recovery:
►► To convert your file system to EXT4, you'll need 4EXT recovery, which will replace the old Clockworkmod recovery.
►►this is done by installing an app called 4ext Recovery Control.
► download, and install the app
► click "Online install | upgrade"
► press yes when the app has detected your CORRECT device (Desire Z / G2)
► install one of the RC recoveries available. don't install the ones labeled "testing" or "reference"
►► you can choose between classic, and touch recoveries... i'm using touch, so i'll be guiding you through touch recoveries.
► click "install"
►► it will download the file required (a .img file in the root of the sdcard)
►► it will flash it for you.
► now go back to the main menu, and press "Power Menu"
► press Reboot into recovery, and Do it!
Another way to flash 4EXT is to download it from HERE for free.​
Click to expand...
Click to collapse
Now you have 4EXT recovery.
Switching to EXT4:
►► now that you've booted to 4EXT, let's convert your file system to EXT4.
► OPTIONAL: Make a NANDROID Backup by going to backup | restore, and clicking "backup.
► click "Tools"
► click "wipe or format -> EXT4"
►► this will switch you to EXT4
► if you made a backup, click on "convert or change a backup -> EXT4" (may not work)
► if you didn't, just reflash, reboot and enjoy.
►► switching to EXT4 doesn't format your sdcard...​
Click to expand...
Click to collapse
Speeding up GPS/AGPS:​
►► One of the main reasons to root an Android phone is to speed up the speed of the GPS lock
►► This happens by changing some text in a file called gps.conf in /etc/ or /system/etc/
► get a file explorer with root support (root explorer, ES file explorer is good too)
► you'll have to replace your gps.conf with a new, tweaked one.
► go HERE, pick your country, and download the file inside the folder.
►► if you didn't find your country (like me), pick the country that is the closest to yours.
► put it on your sdcard
► open up your root explorer
► copy the file
► go to /system/etc/
► mount system as R/W
► paste the file, and overwrite it with the old one.
► now change it's permissions to rw-r--r-- by holding on it, and clicking permissions
► change both owners to 0-root​
Click to expand...
Click to collapse
Testing results:
►► The main purpose of the test is to make Android learn the new gps.conf file.
►► this happens by using an app that controls GPS and AGPS.
► download GPS test HERE, and install it.
► open it, go to menu-settings, and press clear AGPS.
► OPTIONAL: reboot
► after clearing AGPS, and while connected to the internet, press Update GPS.
►► you'll get a GPS lock in about 5 seconds
► leave the GPS locked for about 10 minutes for Android to learn how it works.
►►this method will get you a lock in 5-15 seconds with or without internet connection.​
Click to expand...
Click to collapse
Remove Music Lag on AOSP/MIUI/AOKP ROMs:​
Problem:
► Music hangs for about a second repeating the last syllable the singer says. even while the screen is turned on, while it's charging, or while it's overclocked to 5GHz ​
Click to expand...
Click to collapse
​
Explanation:
►► this usually happens when on AOSP/MIUI/CM/AOKP ROMs and not Sense ROMs.
►► what is happening is that the buffer size for the non-Sense ROMs are set too low, so the music player gets to a point where it has to play something, but that "thing" isn't loaded, so it'll have to wait until the buffer loads it to play.
►► all of this happens is under a second, but this lag is VERY annoying, especially if you're on a headset, and the volume is set a little high.
►► the solution is to set the buffer size a little (or a lot) higher.​
Click to expand...
Click to collapse
​
Solution:
► Download PlayerPro or PlayerPro Trial.
► Download the PlayerPro DSP Pack.
► Run PlayerPro.
► Go to Menu-Settings-Audio.
► Enable "DSP pack".
► Click "Audio buffer" and set it to Large (or Very Large).
► Click "Audio priority" and set that to Maximum.
►► Now you'll have to always use PlayerPro for music playing, because it's the only Music player that is compatible with the DSP pack... but it's worth it.​
Click to expand...
Click to collapse
​
Thanks to BlackICE Team for the GPS files.
Thanks to all the users for teaching me those things.

Good guide. Simple and straight forward.
Maybe you can add something about repartitioning to 4Ext. This is a major improvement on every ROM.

great guide for noobs,
i vote this thread for sticky, u should make a poll.
keep up the good work

Carlovn said:
Good guide. Simple and straight forward.
Maybe you can add something about repartitioning to 4Ext. This is a major improvement on every ROM.
Click to expand...
Click to collapse
thanks! i'll add it soon
usf619 said:
great guide for noobs,
i vote this thread for sticky, u should make a poll.
keep up the good work
Click to expand...
Click to collapse
what's the subject of the poll?
———————————————————
i didn't mean to mock you or to offend you in any kind of way

Riro Zizo said:
what's the subject of the poll?
Click to expand...
Click to collapse
it should be something like: "has this thread been helpful?" or "should this thread be a sticky?"
and then if you get enough votes you can ask the forum moderator to sticky the thread.

poll added

I am moving this guide to General Section, as guides belong in the general section.
Thanks
s.d.oconnor

By the way, you can't flash official HTC ROM when you got CWM. I tried it, and it refuses to install.
Sent from my Nokia 3310 using XDA App

VaderSKN said:
By the way, you can't flash official HTC ROM when you got CWM. I tried it, and it refuses to install.
Sent from my Nokia 3310 using XDA App
Click to expand...
Click to collapse
yes, but there is a stage where you flash PC10IMG.zip and u get froyo with stock recovery... so when you re-update, you'll lose everything.
———————————————————
i didn't mean to mock you or to offend you in any kind of way

added Converting to EXT4 file system guide.
enjoy

Thanks Riro! Just flashed my first ever custom ROM - ILWT CM7 thanks to your guide!
cheers

GrievousMcG said:
Thanks Riro! Just flashed my first ever custom ROM - ILWT CM7 thanks to your guide!
cheers
Click to expand...
Click to collapse
glad you liked it
———————————————————
i didn't mean to mock you or to offend you in any kind of way

One thing I don't get... When I click on wipe or format -> ext4 do I have to click on wipe system data etc... or do I leave it at that?
Thanks
Sent from my HTC Vision using xda app-developers app

IsmailOmer said:
One thing I don't get... When I click on wipe or format -> ext4 do I have to click on wipe system data etc... or do I leave it at that?
Thanks
Sent from my HTC Vision using xda app-developers app
Click to expand...
Click to collapse
"wipe or format -> ext4" wipes every partition, and converts it to ext4... so you don't have to double wipe.
EDIT: that reminds me, i should add a 'reflash' step.
———————————————————
i didn't mean to mock you or to offend you in any kind of way

added reflash step in 4EXT conversion.
added OPTIONAL Full Backup.
Added Speeding Up GPS Lock section
———————————————————
i didn't mean to mock you or to offend you in any kind of way

added Remove Music Lag on AOSP/MIUI/AOKP ROMs
now shouldn't this be a sticky?

Does anyone know how to manually set the audio buffer size higher? Or is playerpro the only way??? I'd like to see this work with other music players.

tarroyo said:
Does anyone know how to manually set the audio buffer size higher? Or is playerpro the only way??? I'd like to see this work with other music players.
Click to expand...
Click to collapse
I'm pretty sure it's possible, let me get back to you with a solution.

natabbotts said:
I'm pretty sure it's possible, let me get back to you with a solution.
Click to expand...
Click to collapse
if you ever find a solution, please pm me so i could add it to OP
———————————————————
i didn't mean to mock you or to offend you in any kind of way

hi man i follow your guide and i fix my gps and work ok at first time but now it take too long time to see satelites.
can you send me what to do all the steaps from the begin what to do to fix it.i dont understand what to do with permssions rw-r-r what is that.i use root explorer and at the permissions sey to me owner and it has tick at read,write,execute it has group and tick read write and execute and it has others to tick read,write plz say me what to do all the steps from the begin
thx

Dpi

On the original n7 lowering DPI made the status bar move to the bottom, and made it a tablet mode. How do you do this on this one. What's the DPI you need to set It to. It's 320 out of the box
Sent from my Nexus 7 using Tapatalk 2

imablackhat said:
On the original n7 lowering DPI made the status bar move to the bottom, and made it a tablet mode. How do you do this on this one. What's the DPI you need to set It to. It's 320 out of the box
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Not sure what dpi you need to modify to but you would do this in the build.prop found under /system
you will just want to look for the following line
ro.sf.lcd_density
modify the value as needed then push back to /system and set permissions to 644 or -rw-r--r--

imablackhat said:
On the original n7 lowering DPI made the status bar move to the bottom, and made it a tablet mode. How do you do this on this one. What's the DPI you need to set It to. It's 320 out of the box
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Merely setting your DPI lower will not engage the tablet mode as far as I know. I know Paranoid Android will let you do tablet mode very easily, so go check that out in the original development forums.

oh no.. i changed the dpi value as you said and now my screen just stays black after i rebootet the device.
so if someone is reading this: DON'T CHANGE THIS VALUE IN THE BUILD.PROP!!
Edit:
Well so i made a backup of the build.prop... is there any possibility to push that backup file back into the /system folder without starting android? I tried to do that by booting into the tw recovery but i don't seem to be able to perform that task by using the filemanager..
has anybody an idea how to do this? otherwise i would have to wipe everything and install the factory image and i will lose my data:/
unfortunately i did not make a nandroid backup

Upload your build.prop and I´ll create you a flashable package
Jemus said:
oh no.. i changed the dpi value as you said and now my screen just stays black after i rebootet the device.
so if someone is reading this: DON'T CHANGE THIS VALUE IN THE BUILD.PROP!!
Edit:
Well so i made a backup of the build.prop... is there any possibility to push that backup file back into the /system folder without starting android? I tried to do that by booting into the tw recovery but i don't seem to be able to perform that task by using the filemanager..
has anybody an idea how to do this? otherwise i would have to wipe everything and install the factory image and i will lose my data:/
unfortunately i did not make a nandroid backup
Click to expand...
Click to collapse

Gorgtech said:
Upload your build.prop and I´ll create you a flashable package
Click to expand...
Click to collapse
Thank you for your help but i guess it may be a problem that the backup of my build.prop is only on my nexus and not on my pc or laptop
If the Nexus 7 would have a micro sd card slot it would be manageable but without one.. i don't know.
Would the build.prop file of another nexus 7 20013 user also be okay?

I can give you my generic build.prop ( suitable for a STOCK deodexed or odexed JB 4.3 Firmware ) If you´re not on CM or another similar ROM, it may work out well for you
Jemus said:
Thank you for your help but i guess it may be a problem that the backup of my build.prop is only on my nexus and not on my pc or laptop
If the Nexus 7 would have a micro sd card slot it would be manageable but without one.. i don't know.
Would the build.prop file of another nexus 7 20013 user also be okay?
Click to expand...
Click to collapse

Gorgtech said:
I can give you my generic build.prop ( suitable for a STOCK deodexed or odexed JB 4.3 Firmware ) If you´re not on CM or another similar ROM, it may work out well for you
Click to expand...
Click to collapse
Yeah I'm on stock to! Thank you so much! That should work for me

Flash this one with your recovery
https://www.dropbox.com/sh/s2mubg7zvee3dmb/ckFFHdOF3L
Jemus said:
Yeah I'm on stock to! Thank you so much! That should work for me
Click to expand...
Click to collapse

Gorgtech said:
Flash this one with your recovery
https://www.dropbox.com/sh/s2mubg7zvee3dmb/ckFFHdOF3L
Click to expand...
Click to collapse
Once again thanks a lot!
I'll give it a try right now but i will do it via nexus root toolkit v1.7.2 because i don't know how to get the file you provided me with on my nexus without being able to boot into android
mmhm I flashed the file but it didn't work out for me. after the reboot there was the same black screen as before. but i did really not do annything else but change this ohne line in the build.prop

You can also try to wipe the Dalvik Cache & Cache Partition
Jemus said:
Once again thanks a lot!
I'll give it a try right now but i will do it via nexus root toolkit v1.7.2 because i don't know how to get the file you provided me with on my nexus without being able to boot into android
mmhm I flashed the file but it didn't work out for me. after the reboot there was the same black screen as before. but i did really not do annything else but change this ohne line in the build.prop
Click to expand...
Click to collapse

Gorgtech said:
You can also try to wipe the Dalvik Cache & Cache Partition
Click to expand...
Click to collapse
I'll give it a try! But if it doesn't work afterwards, could you use my own build.prop to create a flashable zip for me? I managed to pull the file from my Nexus via the toolkit
https://www.dropbox.com/s/7e51i7a589d6uvl/build.prop

Here you go https://www.dropbox.com/s/u2x1g4nzv26eo60/build-prop-restore-2.zip
Jemus said:
I'll give it a try! But if it doesn't work afterwards, could you use my own build.prop to create a flashable zip for me? I managed to pull the file from my Nexus via the toolkit
https://www.dropbox.com/s/7e51i7a589d6uvl/build.prop
Click to expand...
Click to collapse

Gorgtech said:
Here you go https://www.dropbox.com/s/u2x1g4nzv26eo60/build-prop-restore-2.zip
Click to expand...
Click to collapse
So now i used the zip you made from my very own build.prop backup and also wiped the cache and davlik as suggested but once again the screen stays black. Do you have any idea what i could do to restore my system or is it the only way out to flash back to stock and wipe everything?

Hopefully you didn´t brick any hardware components, there is a way to restore your system:
https://dl.google.com/dl/android/aosp/razor-jss15q-factory-4f77b811.tgz
You´ll have to first lock your bootloader again and flash this factory image after.

I'm curious as to what happened here.... Changing LCD density shouldn't cause these problems...

So now my device i running as before my try to change the dpi. i flashed back the factory image and it booting up
yeah maybe the change of dpi shouldn't end up so badly but i was sso dumb and had so less knowledge that i set the dpi value from 320 to 32. i just did that because i used this MOD earlier and so i thought, that 32dpi should be okay.
Well now i will first do a nandroid backup and afterwarsd try a different dpi but this time by using an app i think thanks for the help!

I've never gone lower than 160 or higher than 280.

The tablet combined bar was remove in android 4.2. Without a custom ROM there is no way to do this at the moment.
Sent from my Nexus 7 2013 using xda premium
---------- Post added at 04:57 PM ---------- Previous post was at 04:56 PM ----------
Gorgtech said:
Hopefully you didn´t brick any hardware components, there is a way to restore your system:
https://dl.google.com/dl/android/aosp/razor-jss15q-factory-4f77b811.tgz
You´ll have to first lock your bootloader again and flash this factory image after.
Click to expand...
Click to collapse
You do not need to lock the bootloader to flash factory images.
Sent from my Nexus 7 2013 using xda premium

RSDxml-custom recovery/restore/keep data/root/remove warning logo-AIO-4.4.4

What IS this post about?
Firmware restore of 4.4.4 using RSD Lite, but for unlocked boots, the recovery flashed is custom & the logo used is the normal M-multi color rather than the warning version. Comes in Philz & Twrp flavors. Upon rebooting, Philz or TWRP will root for you.
User data is retained, not erased.
Note: After this restore you may notice problems because you kept data-just wipe data from recovery & reboot. Keeping data like this is non standard.
The logo used is from here.
First 2 attachments are about 10 MBs. There are 3 modded files to extract: MOD...xml (RSD instructions), recovery & logo to paste into your unzipped/extracted FXZ/XML folder. You may want to rename the stock recovery & logo so they will not be overwritten. Here is the usual fxz Source, which you may have already.
Do not paste the source xml folder contents into mine.
The 2 last attachments are modded full FXZs, 900 MB.
Choose the mod xml from RSD Lite 615. Moto drivers are here. There is no getvar or erase userdata as the X firmware has-which is strange for the stock XML. So use of the modded or source FXZ will leave user data alone.
Settings/Developer Options: Enable USB debugging to use RSD.
If you want a fresh restore just wipe data from stock or custom recovery before you use get into the bootloader/apfastboot screen
Note: step 2 is ap/fastboot (RSD mode) & step 6 (recovery) is where to wipe data.
Faster Mega server full versions can be downloaded for regular use on locked xt-1080s as each modded Full fxz can be easily put back to normal. Recovery.img.orig 10.5 MB & logo.bin.orig 2.6 MB just need renaming, as well as the modded ones renamed: recovery.img.mod Philz: 10.4 MB, TWRP: 8.6 MB & logo.bin.mod 2.6 MB. Then run the original xml (included)(not the one labeled MOD). Again there is no data wipe in this original firmware.
A better backup

Full 444 xml with Philz recovery is up.
It is easily converted back to the normal fxz for locked boot users.
But why? Mega is much faster than the sbf/xml storehouse site.

So if your un Rooted this is useful how?

PILLMUZIK3600 said:
So if your un Rooted this is useful how?
Click to expand...
Click to collapse
Just a faster download of the fxz, is all. Then you must convert the xml folder to normal.

Thanx
Big thanx for this solution. Now I have fully rooted and System RW on Verizon Moto Droid Ultra. I was on OTA updated to 4.4.4, and Root was broken. And now all - OK

dschewchenko said:
Big thanx for this solution. Now I have fully rooted and System RW on Verizon Moto Droid Ultra. I was on OTA updated to 4.4.4, and Root was broken. And now all - OK
Click to expand...
Click to collapse
How did this help keep WP off?

I have not unlocked the bootloader I already have stock android 4.4.4 on my droid maxx, I do not read English well, tell me know if I can flash this rom to get root without problems?

aviwdoowks said:
How did this help keep WP off?
Click to expand...
Click to collapse
I don't know. All apps have full access to system partition, but Safestrup cann't to be installed

luisdev said:
I have not unlocked the bootloader I already have stock android 4.4.4 on my droid maxx, I do not read English well, tell me know if I can flash this rom to get root without problems?
Click to expand...
Click to collapse
No way but a boot unlock. 444 has no exploit for rooting.
This helps unlocked phones only.

dschewchenko said:
I don't know. All apps have full access to system partition, but Safestrup cann't to be installed
Click to expand...
Click to collapse
Why don't you share all the details here.

Solution
aviwdoowks said:
Why don't you share all the details here.
Click to expand...
Click to collapse
Before this thread, I have 4.4.4 with broken root after OTA update (without system RW and SuperSU crash)
My way:
-Install RSD and drivers
- do solutions from head from head
- download file from 1 attach
- replace files
- flash it and see on phone error about size of recovery
- reboot
- wipe data and cache
- reboot
- see SuperSU in Menu
- check wp and su with terminal and adb - all OK
- run Root-Explorer, all permissions apply
- can edit and write files in system folders =)

dschewchenko said:
Before this thread, I have 4.4.4 with broken root after OTA update (without system RW and SuperSU crash)
My way:
-Install RSD and drivers
- do solutions from head from head
- download file from 1 attach
- replace files
- flash it and see on phone error about size of recovery
- reboot
- wipe data and cache
- reboot
- see SuperSU in Menu
- check wp and su with terminal and adb - all OK
- run Root-Explorer, all permissions apply
- can edit and write files in system folders =)
Click to expand...
Click to collapse
Do you have a locked or unlocked bootloader?

aviwdoowks said:
Do you have a locked or unlocked bootloader?
Click to expand...
Click to collapse
I have locked verizon moto droid ultra

dschewchenko said:
I have locked verizon moto droid ultra
Click to expand...
Click to collapse
What build did it come with? Please post all info & steps!! Did you use any exploits?

aviwdoowks said:
What build did it come with? Please post all info & steps!! Did you use any exploits?
Click to expand...
Click to collapse
I have Verizon XT1080 with Locked BL, on 4.4.2 was root and WP off, after WiFi updating to 4.4.4 all was broken, and after that I wrote upper I'm now with root and system read/write permission, but safestrap see that WP ON and crashes after tapping somewhere. After updating SuperSU root will be lost.
For system R/W you may go to Terminal and run:
- su
- mount -o rw,remount /dev/block/platform/msm_sdcc.1/by-name/system /system
and than with mount command check if /system have rw. After reboot you may to remount
P.S. Sorry for my english, I'm from Ukraine =)
Very bad that Moto with cutted language pack =(

dschewchenko said:
Before this thread, I have 4.4.4 with broken root after OTA update (without system RW and SuperSU crash)
My way:
Click to expand...
Click to collapse
-Install RSD and drivers
- do solutions from head from head
???
- download file from 1 attach
Was that the small?
- replace files
This must have been recovery, logo & the mod.XML.
- flash it and see on phone error about size of recovery
Details?
- reboot
- wipe data and cache
- reboot
- see SuperSU in Menu
In app drawer?
- check wp and su with terminal and adb - all OK
- run Root-Explorer, all permissions apply
- can edit and write files in system folders =)
I have no idea how you kept root if RSD succeeded properly.

aviwdoowks said:
-Install RSD and drivers
- do solutions from head
???
in head of this thread
Here is an alternate method to flash 444 "pre-recovery'ed" and thereby pre-rooted. Comes in Philz & Twrp flavors.
3 modded files: ...xml (RSD instructions), recovery & logo to paste into your unzipped FXZ/XML folder. Source.
Flash from RSD Lite 615. Moto drivers. There is no getvar or erase userdata as the X firmware has-which is strange for the stock XML. Added custom recovery & stock (boot) logo.
Settings/Developer Options: Enable USB debugging to use RSD.
If you want a fresh restore just wipe data from stock or custom recovery before you use get into the bootloader/apfastboot screen
Note: step 2 is ap/fastboot (RSD mode) & step 6 (recovery) is where to wipe data.
Paste the 3 files to your xml folder. You may want to rename the stock recovery & logo so they will not be overwritten.
Faster Mega server (but slow uploads, 1 a day. 2 Ultra & 2 X) full versions soon. 10 MB vs 900 MB.
Note for locked users: each modded Full fxz can be easily put back to normal. Recovery.img.orig & logo.bin.orig just need renaming. Then run the original xml (included). Again there is no data wipe in this original firmware.
A better backup
ATTACHED FILES
File Type: txt Philz_6.57.9_NO ERASE_user.data_stkBOOTlogo_1FF-obake_verizon-user-4.4.4-SU4.21-MEGA.xml.zip.txt - [Click for QR Code] (112 Bytes, 9 views)
File Type: txt Twrp-2.8.0.1_NO ERASE_user.data_stkBOOTlogo-1FF-obake_verizon-user-4.4.4-SU4.21-MEGA.xml.txt - [Click for QR Code] (111 Bytes, 13 views)
File Type: txt Full_Philz_6.57.9_NO ERASE_user.data_stkBOOTlogo1FF-obake_verizon-user-4.4.4-SU4.21.xml.zip.txt - [Click for QR Code] (110 Bytes, 3 views)
Click to expand...
Click to collapse
- download file from 1 attach
Was that the small?
this -> "Philz_6.57.9_NO ERASE_user.data_stkBOOTlogo_1FF-obake_verizon-user-4.4.4-SU4.21-MEGA.xml.zip.txt"
- replace files
This must have been recovery, logo & the mod.XML.
files from downloaded archive
- flash it and see on phone error about size of recovery
Details?
-standart flashing with RSD-Lite. When recovery uploading , on phone screen was error about incorrect size of recovery, and then I reboot phone to recovery(stock with VOL-DOWN and POWER), then I do full wipe, thenreboot to clean system, in menu I see SuperSU, then download and run Terminal, tap in Terminal "su", all OK, try to remount system to RW, all OK, then download Root Explorer, root permission applied and go to system for manipulate with files =)
- reboot
- wipe data and cache
- reboot
- see SuperSU in Menu
In app drawer?
- check wp and su with terminal and adb - all OK
- run Root-Explorer, all permissions apply
- can edit and write files in system folders =)
I have no idea how you kept root if RSD succeeded properly.
Click to expand...
Click to collapse
=)

dschewchenko said:
=)
Click to expand...
Click to collapse
So you flashed the mini version without system, motoboot, boot, gpt & etc.
It is still confusing so for everyone's benefit maybe, in time, your sweet time, you could be more clear about the exact steps.
Thank you.

aviwdoowks said:
So you flashed the mini version without system, motoboot, boot, gpt & etc.
It is still confusing so for everyone's benefit maybe, in time, your sweet time, you could be more clear about the exact steps.
Thank you.
Click to expand...
Click to collapse
I don't change xml, from downloaded archive I replace files with source Source (from head of thread) And in RSD check xml file that from archive Philz

dschewchenko said:
I don't change xml, from downloaded archive I replace files with source Source (from head of thread) And in RSD check xml file that from archive Philz
Click to expand...
Click to collapse
Just to be clear, I intended the attachments to overwrite the source. You overwrote the attachment with the source!! (If I read you right)
The Q is did you achieve something good by your mistake?

MM 6.0.1 [TWRP] Recovery

GOT TROUBLE WHILE INSTALLING A RECOVERY? GET A WORKING TWRP RECOVERY AFTER 2 MINUTES ON YOUR XPERIA Z2 D6503/D6502:
open any root explorer app like ES FILE MANAGER
Delete /system/etc/mm_twrp_recovery folder
Go to /system/bin/ folder
Look for the "chargemon.stock" file - If it's present, delete this one: chargemon - and now, rename the chargemon.stock to chargemon
Look for the "taimport.stock" file - If it's present, delete this one: taimport - and now, rename the taimport.stock to taimport
Reboot
download "recovery fix.zip" from mega.nz
extract the file and run "adbrecoveryfix.exe" the .exe file will install some needed files (normally into C:\Minimal ADB and Fastboot\ )
copy the files from the folder "RECOVERY FILES" into the "Minimal ADB and Fastboot" Folder
connect your xperia with the pc
open the "m a a d" folder and then SHIFT+RIGHT CLICK to open a command window
now type:
adb shell
su root
mount -o remount,rw /system
exit
exit
install.bat
Click to expand...
Click to collapse
don´t forget to press enter after "adb shell", "su root" and so on!
now your recovery will install again without any errors!
YOU HAVEN`T INSTALL ANDROID MARSHMALLOW YET BECAUSE YOU WANT TO KEEP ROOT RIGHT, XPOSED AND THE RECOVERY?
THEN CHECK OUT THIS THREAT
http://forum.xda-developers.com/xpe...03-23-5-0-570-prerooted-t3364817#post66513485
Another simple Method: thanks @meer_mortal
Deleted folders and rename chargemon etc
Plugged phone into computer with dev settings, debugging etc
Open root explorer to make / -RW
Run install.bat with CMD
Boom! MM with TWRP
To get in into recovery reboot press down after green LED
Click to expand...
Click to collapse
BUGS: none
IMPROVABLE: boot into recovery only works manually (when it vibrates and a green LED shows up press VOL DOWN till the LED is purple) "QUICK BOOT" and similiar Applications cannot boot into the recovery!

Which files are inside .exe?

Can i get Decryption key? to download

wheal said:
Which files are inside .exe?
Click to expand...
Click to collapse
Only adb and fastboot files! You can also download them from "chip.de" it's called "Minimum adb and fastboot"
Sent from my D6503 using XDA-Developers mobile app

Natur said:
Can i get Decryption key? to download
Click to expand...
Click to collapse
I am sorry that i gave you the wrong link just a minute
Sent from my D6503 using XDA-Developers mobile app

Natur said:
Can i get Decryption key? to download
Click to expand...
Click to collapse
Now the right link is in the decsription...

freaky2xd said:
Now the right link is in the decsription...
Click to expand...
Click to collapse
Thanks,

is this method works if i use Android 5.x or 4.x ?

reknew said:
is this method works if i use Android 5.x or 4.x ?
Click to expand...
Click to collapse
you can try. but if I were you, i`d better use [NUT`s] DualRecovery! its simple and i have already used it for 4.4.4 and 5.1 on the Z2!
http://nut.xperia-files.com/path/XZDualRecovery/XZDualRecovery_2.8.26
just look for the Z2 file... its a zip file! its installer and flashable zip!

thanks man.
this worked for me. I somehow lost recovery but regained it on Android M after following your steps!

pseudoheld said:
thanks man.
this worked for me. I somehow lost recovery but regained it on Android M after following your steps!
Click to expand...
Click to collapse
you are welcome the same happs why i created this threadened to me, that´s why I started this recovery fix thread

Hands health
İts works, good job thanks

Thanks for this. You can also use root explorer to make the phones file system writable before running install.bat

balabanos said:
İts works, good job thanks
Click to expand...
Click to collapse
thanks

meer_mortal said:
Thanks for this. You can also use root explorer to make the phones file system writable before running install.bat
Click to expand...
Click to collapse
try it.

meer_mortal said:
Thanks for this. You can also use root explorer to make the phones file system writable before running install.bat
Click to expand...
Click to collapse
This is a Statement not a question
freaky2xd said:
try it.
Click to expand...
Click to collapse
I did. That's how I got TWRP on MM
Following your guide
I downloaded the files from OP post
Deleted folders and rename chargemon etc
Plugged phone into computer with dev settings, debugging etc
Open root explorer to make / -RW
Run install.bat with CMD
Boom! MM with TWRP
To get in into recovery reboot press down after green LED
Win!

meer_mortal said:
This is a Statement not a question
I did. That's how I got TWRP on MM
Following your guide
I downloaded the files from OP post
Deleted folders and rename chargemon etc
Plugged phone into computer with dev settings, debugging etc
Open root explorer to make / -RW
Run install.bat with CMD
Boom! MM with TWRP
To get in into recovery reboot press down after green LED
Win!
Click to expand...
Click to collapse
oh yeah you`re right of course i thought it might be a question xD
I added your post as a quote to the description

You Want TWRP v3.0.0.2 ?
Then flash @pec0ra customKernel v8.1!
It unlocks:
Based on Sony 23.5.A.0.570 kernel sources
Compiled with linaro GCC 4.9.1 toolchain, -O3
Governors : interactive, ondemand, performance, conservative, smartassV2, intellidemand2 and intelliactive.
Fast hotplug
CPU overclock up to 2.8 GHz Thank's to Faux123 and DooMLoRD
Changed GPU frequency table to 27 - 657 MHz Thank's to Myself5
Sony RIC disabled
Undervolt
TWRP recovery included, fota partition support
Breathing notification light thank's to glocklee
Force Fast Charge
KCAL Advanced color control Thank's to savoca
Click to expand...
Click to collapse
Visit this Link:
http://forum.xda-developers.com/xperia-z2/orig-development/kernel-abricot-kernel-v3-t2965480

guys, after i open install.bat and phone rebooted. My phone didn't open. it is in bootloop now and after opening, phone try to open twrp but it can't so the phone reboot itselft over and over again.. i did hard reset. and open the phone again, same things happened. Help me please..!

Abdülcelil said:
guys, after i open install.bat and phone rebooted. My phone didn't open. it is in bootloop now and after opening, phone try to open twrp but it can't so the phone reboot itselft over and over again.. i did hard reset. and open the phone again, same things happened. Help me please..!
Click to expand...
Click to collapse
reinstall the firmware via flashtool. choose everything to wipe

Custom Rom's Mods

these are few collection of mods that do not have a settings menu to enable or disable them,...
so flash them manually until they can be part of the rom
WARNING: works only in custom roms
Update: CM added support for swapping back and menu buttons from cm-13.0-20161112-NIGHTLY-gemini.zip
==================================
Mods
==================================
1) disable finger print wakeup
2) enable finger print wakeup
3) Xiaomi keys layout(Left Button-> Menu & Right Button-> Back)
4) Android stock keys layout(Left Button-> Back & Right Button-> Menu)
==================================
Downloads: Here
==================================
==================================
Workings
==================================
Enabling/Disabling the FingerPrint Wakeup
Source: github
Mod Location: /sys/devices/soc/soc:fpc_fpc1020/enable_wakeup
Code:
[B]Values:[/B]
1 = Enable
0 = Disable
Changing The Keylayout
Source: github
Mod Location: /system/usr/keylayout/synaptics_dsx.kl
Code:
[B]Xiaomi keys layout:[/B]
key 139 APP_SWITCH VIRTUAL
key 102 HOME VIRTUAL
key 158 BACK VIRTUAL
key 143 WAKEUP
[B]Android stock keys layout:[/B]
key 139 BACK VIRTUAL
key 102 HOME VIRTUAL
key 158 APP_SWITCH VIRTUAL
key 143 WAKEUP

Thanks

Works on xiaomi.eu Roms?

alessandro_masci said:
Works on xiaomi.eu Roms?
Click to expand...
Click to collapse
Yes, but actually that mod for non-miui rom, where some Setting not available on non-miui roms
Sent from my MI 5 using Tapatalk

Uhm.. just flashed in twrp the xiaomi layout zip.... but no change. Not working for me.. cm13 here

Henkl said:
Uhm.. just flashed in twrp the xiaomi layout zip.... but no change. Not working for me.. cm13 here
Click to expand...
Click to collapse
Same here .. Error when flashing..

FrankRr said:
Same here .. Error when flashing..
Click to expand...
Click to collapse
folder structure inside .zip is flashable but there is shouldn't have a folder before /Meta-INF and /System. so that's why it give error message, just extract it and replace manually.

Henkl said:
Uhm.. just flashed in twrp the xiaomi layout zip.... but no change. Not working for me.. cm13 here
Click to expand...
Click to collapse
FrankRr said:
Same here .. Error when flashing..
Click to expand...
Click to collapse
arif_kholid said:
folder structure inside .zip is flashable but there is shouldn't have a folder before /Meta-INF and /System. so that's why it give error message, just extract it and replace manually.
Click to expand...
Click to collapse
Ohh yea my bad!!! Will change them....
EDIT: changed and uploaded new zips

chiragkrishna said:
Ohh yea my bad!!! Will change them....
EDIT: changed and uploaded new zips
Click to expand...
Click to collapse
Thanks. Now flashed (Xiaomi keyboard) and all OK. Buttons have changed as they are supposed to..

Yeah it works now. Thanks!

Update: CM added support for swapping back and menu buttons from cm-13.0-20161112-NIGHTLY-gemini.zip

chiragkrishna said:
Update: CM added support for swapping back and menu buttons from cm-13.0-20161112-NIGHTLY-gemini.zip
Click to expand...
Click to collapse
Hi.
Updated to latest nightly but can't find that option...
Where did u find it? In Settings-Buttons there isn't option to swap...
Edit: Find it...
Settings-Additional buttons

Thanks

Enable fingerprint for stock MIUI works?

thanks bro... it's perfect, i follow the instruction and do it myself with explorer

Fingerprint Wakup works for me. Using miui 8.3 from xiaomi.eu.

Evil_Kreis said:
Fingerprint Wakup works for me. Using miui 8.3 from xiaomi.eu.
Click to expand...
Click to collapse
Hi, what I need to flash to make this mod works on miui 8.3 from xiaomi.eu, too?
Odoslané z Mi5

I just changed the file but it's not permanently. I don't know if there is a way to but if you figured let me know.

Thaks for tutorial. The tutorial makes Xiaomi MI5 more fascinating :silly::silly::silly::silly:

FingerPrint Wakeup resets after reboot
chiragkrishna said:
Enabling/Disabling the FingerPrint Wakeup
Source: github
Mod Location: /sys/devices/soc/soc:fpc_fpc1020/enable_wakeup
Code:
[B]Values:[/B]
1 = Enable
0 = Disable
Click to expand...
Click to collapse
@chiragkrishna, I tried flashing the zip to enable FingerPrint Wakeup but it did not work. So I updated the file as per the instructions. I guess that's because the zip file has nothing inside the system folder. It works but the value is reset to 0 after reboot. Any permanent solutions?
Update:
Although I tried the hard way by using Init.d script to reset the value to 1 at every boot, it didn't work.
Then I tried using Tasker to set the value, it worked perfectly.
But then I found a video with an easier solution using Kernel Adiutor.
Here's the Youtube link: Tutorial How to Set Xiaomi Mi5 Fingerprint Always On