Database Develop

[Q&A] [RECOVERY][GUIDE][i9305]--CWM/PHILZ/TWRP latest versions+Odin v3.09 Guide--14-

[Q&A] [RECOVERY][GUIDE][i9305]--CWM/PHILZ/TWRP latest versions+Odin v3.09 Guide--14-
Q&A for [RECOVERY][GUIDE][i9305]--CWM/PHILZ/TWRP latest versions+Odin v3.09 Guide--14-07-2014
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][GUIDE][i9305]--CWM/PHILZ/TWRP latest versions+Odin v3.09 Guide--14-07-2014. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

someone could build a philz recovery from the latest source with F2FS support for i9305?

Just informing you TWRP is updated to a 2.8.5.0 version for i9305 since one week: http://techerrata.com/browse/twrp2/i9305

TWRP 2.8.5.0
Hello,
TWRP 2.8.5.0 is f2fs it or not ?
Best Regards

working thanks for this

Finally.
After searching for almost 3 days (almost straight, you know school was between it) I finally found this thread.
I´ve followed all the steps, and FINALLY that whole rooting stuff worked.
Previously I tried some YouTube Tutorials, and yes, the SuperSU showed up, but wasn´t openable nor usable nor updatable and worst of all NOT removable.
But This "Noob friendly" Guide really helped me out.
I can´t say thank you often enough.
So... THANK YOU, MATE.
P.S.: I´ve only made an account to thank you for your great work. Once again, Thank you.

Today build didn't work for me, stuck on Samsung logo
Sent from my GT-I9305 using Tapatalk

TWRP 2.8.7.0 for i9305?
The new version of TWRP 2.8.7.0 for i9305 has been up on the official TWRP site for weeks but it still seems to be corrupted (causing bootloops)? Where can I verify that a proper version has been uploaded? I know that there's a thread on i9305 development trying to make a stable version but who are behind these version released on official TWRP site and shouldn't they be doing the stable version?

Kaedin said:
The new version of TWRP 2.8.7.0 for i9305 has been up on the official TWRP site for weeks but it still seems to be corrupted (causing bootloops)? Where can I verify that a proper version has been uploaded? I know that there's a thread on i9305 development trying to make a stable version but who are behind these version released on official TWRP site and shouldn't they be doing the stable version?
Click to expand...
Click to collapse
the version in development thread is by me and works fine now
twrp builds the recoverys via jenkins and upload them... as for now they use a old tree for your device and thats why the broken build exists (no ome tests those builds)
the problem is you dont have any official maitainer .... so nobody takes care of your twrp builds....
i am not allowed to upload a stable build ... only a DEV that OWNS i9305 can do it (dont must be recognized dev but must proof some skill)
Sent from my Xperia T using XDA Free mobile app

SdtBarbarossa said:
the version in development thread is by me and works fine now
twrp builds the recoverys via jenkins and upload them... as for now they use a old tree for your device and thats why the broken build exists (no ome tests those builds)
the problem is you dont have any official maitainer .... so nobody takes care of your twrp builds....
i am not allowed to upload a stable build ... only a DEV that OWNS i9305 can do it (dont must be recognized dev but must proof some skill)
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for your fast reply and it is really nice to see you giving such an effort to bring this latest TWRP working on i9305! I wish I could have dug this info out before I had flashed the recovery version from the official site as I had to go stock to get my device working again (well, better than a bricked device though)!
So the Alpha 17 is fully working at the moment? Could we get a download link placed at the main post if possible? Awesome work, man!

Sir I lost my root and recovery how to fix?

shan482 said:
Sir I lost my root and recovery how to fix?
Click to expand...
Click to collapse
You can:
1. Follow the guide for the rooting process in ODIN with CF Auto root and also the custom recovery flashing.
OR
2. Flash just the custom recovery of your choice and then install a pre-rooted custom rom using the recovery you have flashed.
Both ways you will have custom recovery and root again

philz full wipe not working :crying:
plz help~~~ I flash the recovery from 4.3 stock, and then flash the rom
http://forum.xda-developers.com/galaxy-s3/development-i9305/rom-4-4-4-t3026347
I did a full wipe and then install the ROM, the rom can be flashed and run successfully.
But I found all data, including files from internal SD card such as whatsapp data and camera still exist (not wiped)
Then I search the threads and found there is a knox bootloader at stock 4.3 which is not a good thing
After using the rom for 2 days, I notices the touchwiz always FC, and the device always reboot
I wonder if the full wipe is not working well so that I am having some issues with the new ROM...
anyone could suggest me how to do a complete full wipe? Also if possible how to remove the knox bootloader? Thanks!

Jeorainc said:
plz help~~~ I flash the recovery from 4.3 stock, and then flash the rom
http://forum.xda-developers.com/galaxy-s3/development-i9305/rom-4-4-4-t3026347
I did a full wipe and then install the ROM, the rom can be flashed and run successfully.
But I found all data, including files from internal SD card such as whatsapp data and camera still exist (not wiped)
Then I search the threads and found there is a knox bootloader at stock 4.3 which is not a good thing
After using the rom for 2 days, I notices the touchwiz always FC, and the device always reboot
I wonder if the full wipe is not working well so that I am having some issues with the new ROM...
anyone could suggest me how to do a complete full wipe? Also if possible how to remove the knox bootloader? Thanks!
Click to expand...
Click to collapse
You should flash Android 5.1 for i9305.
The difference in speed, battery usage & user friendliness is massive.... It gives our device a new lease of life..
Get rid of 4.4. Install the latest Philz Recovery & KNOX is a problem you can solve. Search Google....
Flash cm12.1 for i9305 & install the gapps aroma package so you can choose exactly which Google apps you want in your system.
I use winxuser version of CyanogenMod 12.1. (Android 5.1.1)
Btw the devs are currently adapting Android 6.0 dor i9305 & it looks like it will work in a few weeks...
Sent with Tapatalk

Pe1ican0 said:
You should flash Android 5.1 for i9305.
The difference in speed, battery usage & user friendliness is massive.... It gives our device a new lease of life..
Get rid of 4.4. Install the latest Philz Recovery & KNOX is a problem you can solve. Search Google....
Flash cm12.1 for i9305 & install the gapps aroma package so you can choose exactly which Google apps you want in your system.
I use winxuser version of CyanogenMod 12.1. (Android 5.1.1)
Btw the devs are currently adapting Android 6.0 dor i9305 & it looks like it will work in a few weeks...
Sent with Tapatalk
Click to expand...
Click to collapse
Hi,
Lets talk about the behavior after full wipe using Philz,
as I know all data should be cleared right? But after I full wipe using philz and flash a rom, after that all data remains including all photos, whatsapp data etc.... is that a normal scenario?

Jeorainc said:
Hi,
Lets talk about the behavior after full wipe using Philz,
as I know all data should be cleared right? But after I full wipe using philz and flash a rom, after that all data remains including all photos, whatsapp data etc.... is that a normal scenario?
Click to expand...
Click to collapse
In Philz 6.48.4 (also the one im using), you have to go to ''mounts and storage'' and do a ''format /data and /data/media (/sdcard)'', this will wipe your internal SD (phone storage) where your photos, whatsapp data etc. are stored, so before wiping it make sure anything you need is saved elsewhere on your pc. If you need to wipe your external SD (micro sd), you need to do a ''format /storage/sdcard1''.
SOME INFO ABOUT WIPING BEFORE INSTALLING A ROM:
The following actions are what i consider a normal wipe.
*This is the wipe that you need most of the time.
- wipe data/factory reset
- wipe cache partition
- in advanced ---> wipe dalvik cache
Now flash the rom you want..
This is what i consider a full wipe.
*This is the wipe that you need if you want to have a clean installation.
- wipe data/factory reset
- wipe cache partition
- in mounts and storage ---> format /data and /data/media (/sdcard)
- in advanced ---> wipe dalvik cache
Now flash the rom you want..
And this is what i consider a mega wipe.
*This is the wipe that you need if you absolutely need to wipe everything. (more for advanced users who know exactly what they are doing)
- wipe data/factory reset
- wipe cache partition
- in mounts and storage ---> format /data
- in mounts and storage ---> format /boot
- in mounts and storage ---> format /modem (do it only if the rom your gonna install has modem/s included!)
- in mounts and storage ---> format /data and /data/media (/sdcard)
- in advanced ---> wipe dalvik cache
Now flash the rom you want..
For using Samsung 4.4.4 roms, such as N4 Elite Lite, Eclipse, TGP or Amcha rom, it is recommended at this point to update your bootloader to a 4.4.4 kitkat bootloader if you are still on a 4.3 bootloader, you can do that by flashing a Samsung official firmware with ODIN, preferably one for your region if it exists, if not any other latest firmware will do.
And FYI, the bootloader cannot be removed, its a part of your device !
If you dont know what bootloader you have at the moment, you can check it by going to the first page of my recovery/guide thread and then scroll down and at the end of the OP you'll see some info about bootloaders with a picture, where it says ''step 5''.
Maybe you already know some of this, but still i explained in details so that it will be also usefull for others
Happy flashing! :good:

MaHo_66 said:
In Philz 6.48.4 (also the one im using), you have to go to ''mounts and storage'' and do a ''format /data and /data/media (/sdcard)'', this will wipe your internal SD (phone storage) where your photos, whatsapp data etc. are stored, so before wiping it make sure anything you need is saved elsewhere on your pc. If you need to wipe your external SD (micro sd), you need to do a ''format /storage/sdcard1''.
SOME INFO ABOUT WIPING BEFORE INSTALLING A ROM:
The following actions are what i consider a normal wipe.
*This is the wipe that you need most of the time.
- wipe data/factory reset
- wipe cache partition
- in advanced ---> wipe dalvik cache
Now flash the rom you want..
This is what i consider a full wipe.
*This is the wipe that you need if you want to have a clean installation.
- wipe data/factory reset
- wipe cache partition
- in mounts and storage ---> format /data and /data/media (/sdcard)
- in advanced ---> wipe dalvik cache
Now flash the rom you want..
And this is what i consider a mega wipe.
*This is the wipe that you need if you absolutely need to wipe everything. (more for advanced users who know exactly what they are doing)
- wipe data/factory reset
- wipe cache partition
- in mounts and storage ---> format /data
- in mounts and storage ---> format /boot
- in mounts and storage ---> format /modem (do it only if the rom your gonna install has modem/s included!)
- in mounts and storage ---> format /data and /data/media (/sdcard)
- in advanced ---> wipe dalvik cache
Now flash the rom you want..
For using Samsung 4.4.4 roms, such as N4 Elite Lite, Eclipse, TGP or Amcha rom, it is recommended at this point to update your bootloader to a 4.4.4 kitkat bootloader if you are still on a 4.3 bootloader, you can do that by flashing a Samsung official firmware with ODIN, preferably one for your region if it exists, if not any other latest firmware will do.
And FYI, the bootloader cannot be removed, its a part of your device !
If you dont know what bootloader you have at the moment, you can check it by going to the first page of my recovery/guide thread and then scroll down and at the end of the OP you'll see some info about bootloaders with a picture, where it says ''step 5''.
Maybe you already know some of this, but still i explained in details so that it will be also usefull for others
Happy flashing! :good:
Click to expand...
Click to collapse
Really thanks for your answer and appreciate your great work for the N4 elite rom!
I didn't flash an android since android 2.1 and at that time a full wipe using CWM will wipe everything in the device, so I just wonder why the wipe recently will keep user data... once again thanks very much! :good::good::good:

[Q&A] [Rom][D5803] M-XRom

Q&A for [Rom][D5803] M-XRom
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Rom][D5803] M-XRom. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Seems to be a way around the DRM problem: http://forum.xda-developers.com/showpost.php?p=57675821&postcount=348

I have 2 suggestions.
First - Congratulations !!!!
Second - I would suggest the DSB of paranoid and the hands Hover (Heads up) of paranoid. I will download and test the rom. But my smart broke the battery cover and I need to arrange for assistance. It'll have to wait a bit for the test and my feedback.
But, all Congratulations !!!

Can some point to to a detailed explanation about the DRM keys ?
How are the keys checked ? In the photo app ? If it's in software can't we just circumvent it ?
I saw this post that claims to solve the DRM issues (for the z3c):
1.Flash ftf file "23.0.1.A.5.77" by Flashtool.
2.Relock bootloader by Flashtool.
3.Flash ftf file "23.0.1.A.5.77" by Flashtool AGAIN.
4.Unlock bootloader by Flashtool.
5.Flash boot.img "AndroPlusKernel v12" by Fastboot.
6.Install DRM restore zip by TWRP.
7.reboot.
How can that save the DRM keys. I assumed as soon as you unlock/reflash you're overwriting the partitions and would lose access to the DRM keys (probably stored on some hidden partition). Did someone try the above method ?

Merci
merci et vive troyes le monde est petit

Changelog?

Hello. I find this Rome very good. Quick question. How can I change the background image of the Notifications / quick settings? Version 1.0.3
solved

sorry, posted by mistake... removed and repost to specific topic.

Not boot
version 1.04 not boot on my phone with locked bootloader phone stucks on sony logo and led color is red and phone rebooting again and again and again..

new version don't work on UBL

rEctifY For locked bootloader
I have a question according to the instruction for LB
" INSTALLATION
For locked bootloader
Flash official Sony's 23.0.1.A.5.77
Root using the method
Install XZDualRecovery (http://forum.xda-developers.com/z3-c...ry-qa-t3014208).
Boot Into Recovery
Wipe Data, Cache and Dalvik Cache
Flash Zip
Reboot and enjoy "
...my question, which method for root???

dr.xavier said:
I have a question according to the instruction for LB
" INSTALLATION
For locked bootloader
Flash official Sony's 23.0.1.A.5.77
Root using the method
Install XZDualRecovery (http://forum.xda-developers.com/z3-c...ry-qa-t3014208).
Boot Into Recovery
Wipe Data, Cache and Dalvik Cache
Flash Zip
Reboot and enjoy "
...my question, which method for root???
Click to expand...
Click to collapse
The instructions are missing a small part. As of now root has been achieved for the z3 line-up using @zxz0O0's giefroot tool.
Although it requires you to be on a firmware prior to the 5.77 (2.93 for example).
After that you should
boot into recovery
Wipe Data, Cache and Dalvik Cache
Flash Zip
Reboot and enjoy!

Sydrox said:
The instructions are missing a small part. As of now root has been achieved for the z3 line-up using @zxz0O0's giefroot tool.
Although it requires you to be on a firmware prior to the 5.77 (2.93 for example).
After that you should
boot into recovery
Wipe Data, Cache and Dalvik Cache
Flash Zip
Reboot and enjoy!
Click to expand...
Click to collapse
thank you very much!

rEctifY LB and ULB keeping DualRecovery
In the end of the instruction it is written:
"Be sure to flash Z3C-XZDRKernel2.8.1-RELEASE.flashable.zip from http://nut.xperia-files.com after installing the ROM and before you reboot, this way you will not lose recovery!"
...but when you look here: http://forum.xda-developers.com/z3-c...ry-qa-t3014208
they say:
"When installing custom ROMs:
Be sure to flash Z3C-lockeddualrecovery[VERSION]-RELEASE.flashable.zip from http://nut.xperia-files.com after installing the ROM and before you reboot, this way you will not lose recovery!"
For now, i am on the Firmware 23.0.1.A.5.77 Generic [ROOT/XZDR/SuperSU] and i want to move to the rEctifY Rom.
Would be very nice, if somebody can tell me which method after flahsing the Rom for keeping the DualRecovery i should use.
Anyway, what is the difference between the Z3C-XZDRKernel and the Z3C-lockeddualrecovery??

Ive installed v. 1.0.4 with XZ kernel .. dual recovery .. UBL .. and DRM restore
Everything is ok except if i install Androplus kernel.. then im stuck at sony logo...when i flash back XZ kernel .. system starts ..
Tried all versions of androplus
From v 18 to the latest
Why cant we use androplus with rectify rom ?

Confirmed for locked bootloader?
Has it been confirmed to work yet with an locked bootloader?
And regarding the instructions;
Firmware 77 needed
Rooted needed
flash rom
clear cache's
reboot and enjoy
The question is: if the phone has a locked bootloader with DRM function then I don't want the DRM function patch and the kernel, because those are for UBL, is this correct?
Also if I've already gained root access (dual recovery method) and kept DRM keys (locked BL) then is it as simple as flashing it in recovery and clearing cache's?
So is it ok to use CWM to flash?
I just want to be clear on the instructions.
Thank You
I just went ahead and used dualboot to boot into CWM, then flashed, everything seems to be working great, very impressed. Thank You.

Hello,
I think I lost recovery. I'd like to re-flash the rom however I'm unable to get to recovery even by re-installing dualrecovery.
Does busybox create known problems? What directory was I supposed to install it under? I noticed this problem after busybox installed to xbin. Busybox could be the problem as I'm unsure it uninstalled and won't re-intall to either bin or xbin.
Thanks

OK so I've downgraded the firmware using flashtool, went through the whole processes to upgrade to .77 (as per instruction to install rectify). During this I maintained root as well as confirmed recovery along the way. It's not until I install rectify mod that I loose recovery, and yes I flash dualboot flashable zip file after rom and before rebooting.
I'm out of ideas, can you please help.
---------- Post added at 07:40 PM ---------- Previous post was at 07:06 PM ----------
Like I'm talking to myself,
So I installed dual recovery from PC... again, however this time it's one of those clean installs and it worked. I haven't touched busy box but I did snoop around and see some links installed already. Is me doing a smart install what caused the problems in the first place?

Nice. Thanks!

Disable Five Buttons
Hi! Great work! How can i disable the five buttons? I just wanna back, home and recent apps. I'm on your new lollipop rom!
Thanks a lot!

[Q&A] [GALAXY S3 MINI TOOLKIT V2.0 Drivers, Backup, Root, CWM, TWRP, Flash, + MORE

[Q&A] [GALAXY S3 MINI TOOLKIT V2.0 Drivers, Backup, Root, CWM, TWRP, Flash, + MORE
Q&A for [GALAXY S3 MINI TOOLKIT V2.0 Drivers, Backup, Root, CWM, TWRP, Flash, + MORE
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GALAXY S3 MINI TOOLKIT V2.0 Drivers, Backup, Root, CWM, TWRP, Flash, + MORE. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Awesome software! Thanks!

Problem with renaming recovery
Hey,
so I've been trying to root the S3 Mini of a friend (8190N) but got problems installing the custom recovery. It didn't work hence I followed the instructions to rename the recovery through odin.
The Odin push works like a charm but I by god cannot get the phone into the custom recovery. If I push the named buttons it simply keeps booting and rebooting into the screen where it shows the battery. If I let go of the power button but keep the other two pressed it'll boot me straight into android and the process was for nothing.
Is there anything I am missing within the instructions? Am I just plain stupid? Never had the problem of renaming the recovery file on any of my phones before and it is freaking me out right now
Btw. Thanks so much for the toolkit. It is impressive how seeming-less it works!
Edit: Alright. I was simply too stupid. After the millionth time of rebooting, reinstalling and pressing my fingers I finally managed to get the custom recovery installed. Thanks guys!

[Q&A] [KERNEL][I9295][AOSP/CM11/CM12][TW-4.4]KT-SGS4 port for Active Intl

Q&A for [KERNEL][I9295][AOSP/CM11/CM12][TW-4.4]KT-SGS4 port for Active Intl
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [KERNEL][I9295][AOSP/CM11/CM12][TW-4.4]KT-SGS4 port for Active Intl. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Big Ups To spegelius
First of all I'd like to give big thanks to spegelius for his amazing work on the cm12 kernel!!
Using it on my daily driver and no hiccups yet what so ever.
Everything is perfect!! Only an LED issue at boot but that's cosmetic and easily fixed.
Could i please just request one thing.
WE ARE ALL WAITING DESPERATELY FOR YOUR TW 5.0.1 KERNEL.
TW is pretty shoddy without your FAST CHARGE or temp throttling to save battery.
PLEEEEASE PLEASE PLEASE MAKE THIS HAPPEN , i will forever be in your debt aha
THANK YOU spegelius

Hey guys, I'm having problems with this kernel my phone doesn't boot up it just gets stuck at the CM logo where there is that blue alien looking guy.
Im using a GT-I9295 with running cm-12.1-20150719-NIGHTLY-jactivelte ROM, I had no problems with it except battery drain and inactive sensors so I decided that flashing a custom kernel might help.
So today I decided to download the latest CM12.1 nightly for my S4 Active (cm-12.1-20150720-NIGHTLY-jactivelte) and the latest compatible custom kernel (KT-SGS4-LP5.0-AOSP-eur-02.15.2015).
I flashed my phone with adb as follows:
<procedure>
reboot to recovery (CWM-based recovery v6.0.3.5)
wipe data/factory reset
wipe cache partition
advanced -> wipe dalvik cache
install zip -> install zip from sideload -> adb sideload cm-12.1-20150720-NIGHTLY-jactivelte.zip
install zip -> install zip from sideload -> adb sideload gapps-5.1.x-20150404-minimal-edition-signed.zip
install zip -> install zip from sideload -> adb sideload KT-SGS4-LP5.0-AOSP-eur-02.15.2015.zip
reboot system now
fix permissions -> yes
</procedure>
now my phone doesn't boot up as I initially stated, it only shows me the CM logo and get stuck there, what did I do wrong?
Any comments/suggestions/tips/corrections is much appreciated!
Thanks!

[Q&A] [ROM] [5.1.1] Stock rooted LMY47Z - Init.d, Busybox, Decrypted boot.img

Q&A for [ROM] [5.1.1] Stock rooted LMY47Z - Init.d, Busybox, Decrypted boot.img
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] [5.1.1] Stock rooted LMY47Z - Init.d, Busybox, Decrypted boot.img. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Quick question in regards to updating instead of installing, is it possible to update 5.1 using this package? I would prefer having to not wipe all my data and then reload it all after installing this.
If so, what would be the preferred method? Wiping the cache and delvik cache, and then sideloading using adb?

PsychicHigh said:
Quick question in regards to updating instead of installing, is it possible to update 5.1 using this package? I would prefer having to not wipe all my data and then reload it all after installing this.
If so, what would be the preferred method? Wiping the cache and delvik cache, and then sideloading using adb?
Click to expand...
Click to collapse
Answered my own question by just diving in.
1) Downloaded the factory image from the google developer site, and grabbed the pre-rooted image
2) Used TWRP to create a backup, as well as transferred imported files from the 'sdcard' to the laptop
3) Flashed newest version of TWRP recovery
4) Cleared cache, delvik cache and data
4) Flashed radio
5) Used adb sideload to flash the pre-rooted stock ROM
6) Started phone and performed basic configuration
7) Restored data from backup
After rebooting and upgrading process, phone is now at 5.1.1, rooted with the unencrypted boot image, and all applications are setup as they were.
Thanks Danvdh!

Link is broken

plz need a mirror