Firstly a massive thanks to RyokoN and [NUT] - much more of this is their work than mine.
The end result is unbranded UK firmware (no docomo/jp apps etc.) 14.2.A.1.114 with SuperSU and NUT's Dual Recovery. The bootloader of course remains locked.
Downloads:
http://dl.weeaboo.com/Z1Compact/C6903_14.1.G.534_ianford10_UK Unbranded.ftf
http://dl.weeaboo.com/Z1Compact/D5503_14.2.A.1.114_Generic UK.ftf
http://dl.weeaboo.com/Z1Compact/SO-02F_14.1.H.1.281_docomo.ftf
http://dl.weeaboo.com/Z1Compact/z1c-43-uk.system.flashable.zip
SuperSU flashable zip from http://download.chainfire.eu/supersu
LATEST Z1C-lockeddualrecovery flashable and installer .zip from http://nut.xperia-files.com/ (thanks to [NUT])
FlashTool: http://www.flashtool.net/index.php
Process:
Copy UPDATE-SuperSU-v1.(...).zip, z1c-43-uk.system.flashable.zip and Z1C-lockeddualrecovery(...)flashable.zip to your external SD card.
Take a full backup, as all phone memory INCLUDING INTERNAL SD will be wiped.
Flash SO-02F_14.1.H.1.281_docomo.ftf (WIPE: select all, EXCLUDE: select none)
Boot and enable USB debugging and installation of apps from unknown sources
Flash C6903_14.1.G.534_ianford10_UK Unbranded.ftf (WIPE: select none, EXCLUDE: select all except system and kernel)
Turn phone on (display will be blank)
Run Z1C-lockeddualrecovery(...)installer.zip's install.bat, selecting option 3 (Installation on unrooted ROM).
Turn phone off using the power + vol up combination.
Flash D5503_14.2.A.1.114_Generic UK.ftf (WIPE: select none, EXCLUDE: select system only)
Boot to philz recovery by turning phone on normally then pressing vol up after the vibrate + green LED
Factory reset and clear for rom installation
Flash in this order without rebooting between each:
z1c-43-uk.system.flashable.zip
Z1C-lockeddualrecovery(...)flashable.zip
UPDATE-SuperSU-v1.(...).zip.
You're done
nice work
Thank you!
Not exactly noob-friendly....
But I will try it as soon as I can put my hands on my XZ1C!
sweet! gonna try this in a couple of days when i get a microsd card..
just to be safe though, because this is my first sony: ftf files are flashed with emma, right?
Sent from my D5503 using Tapatalk
Thanks, I am new to Sony too. Hope a video step by step tutorial will be appreciated.
Sent from my pigeon
labbe- said:
sweet! gonna try this in a couple of days when i get a microsd card..
just to be safe though, because this is my first sony: ftf files are flashed with emma, right?
Sent from my D5503 using Tapatalk
Click to expand...
Click to collapse
For the ftfs use flashtool in flashmode http://www.flashtool.net/index.php
Sent from my D5503 using Tapatalk
Hi! Great work.... haven't tried this yet, my first Sony, so a little outside my comfort zone.....
Have you tried backing up the TA partition? Thanks
Sent from my D5503 using XDA Premium 4 mobile app
nelvinchi said:
Hi! Great work.... haven't tried this yet, my first Sony, so a little outside my comfort zone.....
Have you tried backing up the TA partition? Thanks
Sent from my D5503 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Haven't tried that yet as I don't plan on touching the bootloader (sony stock roms are excellent imo)
No reason why it wouldn't work, unless sony has added some sort of extra protection (unlikely).
i´ve problem with ddms, as log i can see i´ve installed needed parts, got those error messages:
[2014-02-03 20:59:08 - hierarchyviewer]Unable to get view server version from device CB5A1XBJ56
[2014-02-03 20:59:08 - hierarchyviewer]Unable to get view server protocol version from device CB5A1XBJ56
[2014-02-03 20:59:08 - ViewServerDevice]Unable to debug device: sony-c6903-CB5A1XBJ56
[2014-02-03 20:59:08 - hierarchyviewer]Missing forwarded port for CB5A1XBJ56
[2014-02-03 20:59:08 - hierarchyviewer]Unable to get the focused window from device CB5A1XBJ56
do you know what to do about it?
funiewski said:
i´ve problem with ddms, as log i can see i´ve installed needed parts, got those error messages:
[2014-02-03 20:59:08 - hierarchyviewer]Unable to get view server version from device CB5A1XBJ56
[2014-02-03 20:59:08 - hierarchyviewer]Unable to get view server protocol version from device CB5A1XBJ56
[2014-02-03 20:59:08 - ViewServerDevice]Unable to debug device: sony-c6903-CB5A1XBJ56
[2014-02-03 20:59:08 - hierarchyviewer]Missing forwarded port for CB5A1XBJ56
[2014-02-03 20:59:08 - hierarchyviewer]Unable to get the focused window from device CB5A1XBJ56
do you know what to do about it?
Click to expand...
Click to collapse
Not really sure what could cause that, are you able to connect to e.g. adb shell ok?
Darkimmortal said:
[*]Set up DDMS http://forum.xda-developers.com/showthread.php?t=2303834 and ensure it's working ok (you can see phone's screen on PC and can blindly tap on the touchscreen with response visible on PC)
Click to expand...
Click to collapse
DDMS is working (I have taken a screenshot of my phone), but whati is the command to view the phone screen on PC?
c_c_c_66 said:
DDMS is working (I have taken a screenshot of my phone), but whati is the command to view the phone screen on PC?
Click to expand...
Click to collapse
There is no realtime view, you can only refresh the screenshot
Sent from my D5503 using Tapatalk
Darkimmortal said:
Haven't tried that yet as I don't plan on touching the bootloader (sony stock roms are excellent imo)
No reason why it wouldn't work, unless sony has added some sort of extra protection (unlikely).
Click to expand...
Click to collapse
Thanks for that - I'll give your walkthrough a go tonight when I get home.... I'll report back on the results of attempting a TA partition backup....
Fyi, you note that the only thing "lacking" is a writeable /system - should anyone require to mount as rw, try this:
Install Android Terminal Emulator from the store, start it and do this:
su
mount -o rw,remount -t ext4 /system
Done!
nelvinchi said:
Thanks for that - I'll give your walkthrough a go tonight when I get home.... I'll report back on the results of attempting a TA partition backup....
Fyi, you note that the only thing "lacking" is a writeable /system - should anyone require to mount as rw, try this:
Install Android Terminal Emulator from the store, start it and do this:
su
mount -o rw,remount -t ext4 /system
Done!
Click to expand...
Click to collapse
Oi get on hangouts u Iggy can't wait to get the Z1C and try this out
Sent from my HTC One mini using Tapatalk
@Darkimmortal
Please replace the links in the OP for the official development thread and download page: http://nut.xperia-files.com as 2.7.80 is already outdated (TWRP has the wrong alignment and has been replaced by 2 improved versions already). That and I kindly requested not to mirror any of my files...
It's not to give you a hard time, but this way your users can NEVER be sure the files are from me or slightly modified by you to do some bad juju... This is my way to grant users somewhat of a quality control. I hope you understand.
I'll be opening a Q&A thread here soon though, for the official device specific support.
Problems
Hi
I'm getting problems on "14. Boot to philz recovery by turning phone on normally then continually pressing vol up after the single vibrate", the device only vibrates 2 times and the "sony" logo is on the screen but nothing happens.
Does anybody have a fix?
[NUT] said:
@Darkimmortal
Please replace the links in the OP for the official development thread and download page: http://nut.xperia-files.com as 2.7.80 is already outdated (TWRP has the wrong alignment and has been replaced by 2 improved versions already). That and I kindly requested not to mirror any of my files...
It's not to give you a hard time, but this way your users can NEVER be sure the files are from me or slightly modified by you to do some bad juju... This is my way to grant users somewhat of a quality control. I hope you understand.
I'll be opening a Q&A thread here soon though, for the official device specific support.
Click to expand...
Click to collapse
Certainly, I've updated that now
I only checked your download page for any no mirror warnings
torjohron said:
Hi
I'm getting problems on "14. Boot to philz recovery by turning phone on normally then continually pressing vol up after the single vibrate", the device only vibrates 2 times and the "sony" logo is on the screen but nothing happens.
Does anybody have a fix?
Click to expand...
Click to collapse
It may boot loop in this way a couple of times - try turning it off again with the power+vol up 3 vibrate combo
If you still can't get it into recovery, start over and ensure the recovery installer.zip step is performed correctly
Darkimmortal said:
Certainly, I've updated that now
I only checked your download page for any no mirror warnings
Click to expand...
Click to collapse
That's a good point, I'll add that warning soon
Thanks for updating the op guide :good:
Success :laugh:
Thanks for your work, ddms was a bit tricky, you need patience
No problem with making backup of ta partition
now unlocking bootloader
:good:
Related
-=[XZDualRecovery]=-
PhilZ Touch & CWM & TWRP
*** For Locked and Unlocked BOOTLOADERS! ***
Welcome to the Xperia ZL Questions & Answers thread!
I proudly present you the first and only DUAL RECOVERY for locked boot loaders on our lovely Xperia phones!
If you have an unlocked bootloader and chose to keep the STOCK Sony kernel, you can also use this MOD.
Currently supported XPERIA models:
These are also links to the device specific Q&A threads.
Xperia Z: SO-02E, C6602, C6603, C6606, C6616
Xperia ZL: C6502, C6503, C6506
Xperia Tablet Z: SO-03E, SGP311, SGP312, SGP321, SGP351
Xperia Z Ultra: C6802, C6806, C6833, C6843
Xperia Z1: C6902, C6903, C6906, C6943, C6916
Xperia Z1 Compact: D5502, D5503, D5506
Xperia Z2: D6502, D6503, D6506, D6543, D6563
Xperia Tablet Z2: SGP511, SGP512, SGP521, SGP551, SGP561
Xperia ZR: C5602, C5603, C5606
Xperia T, TX, TL and V: LT30p, LT29, LT30at, LT25i
Xperia S: LT26i
Xperia SP: C5302, C5303
Xperia T2 Ultra: D5303, D5322
Xperia Z3: D6603, D6633, D6643, D6653, D6616
Xperia Z3 Compact: D5803, D5833
Xperia Tablet Z3 Compact: SGP621, SGP641, SGP651
To follow development, be sure to check the DevDB thread!
XZDualRecovery User Manual
Special Thanks:
@DooMLoRD for all his excellent work on our much loved Sony phones!
The Team Win developers for TWRP
The ClockWorkMod developers for CWM
@alexocean for his awesome job testing almost all FW releases and the discovery of SuperSU causing problems for the installation of this recovery!
@RoberM for testing
@surdu_petru for testing and handy pointers
@Androxyde for allowing to use his linux and mac adb binaries.
@lancebukkake for finding the TWRP 'fix' to use exFAT formatted sdcards!
@delewer for the final fix for TWRP and its use of exFAT formatted sdcards
@DevShaft for some code help on the windows installer (the menu!)
@Androxyde again, but now for his bash code/script suggestions... oh boy this guy is a genius! :highfive:
@Tamirwig and @shoey63 for their excellent job at testing early BETA's (Xperia Z)
@gregbradley for his extensive testing on the Xperia Z1
Well, enjoy! :fingers-crossed:
The origins of this XZDualRecovery package are in the packages done by:
Krabappel2548, Cpasjuste and DooMLoRD
Thank you for your excellent work guys! :victory:
[Locked Bootloader]CWM recovery 6.0.2.8 for locked bootloaders v4[25-03] by Krabappel2548
[APP/RECOVERY] TWRP 2.4.3.0 for lockled bootloaders installer by Cpasjuste
[KERNEL][Z] DooMKernel {JB}(v06)[20130414] by DooMLoRD
Your thanks (and donations) should (also) go out to them, they deserve it! :highfive:
I just used this, and after finishing the process by restarting phone after the CWM prompt, and I restart again and try to press either up or down volume buttons during the green light, nothing happens it just keeps booting to ROM, I've tried rapidly pressing the volume keys or holding it down nothing would activate recovery. It boots into safe mode if I keep holding it down.
XDA STATUS UPDATE:
I'm at a TAPAsBar, flashing around my ZL.
ehBrY said:
I just used this, and after finishing the process by restarting phone after the CWM prompt, and I restart again and try to press either up or down volume buttons during the green light, nothing happens it just keeps booting to ROM, I've tried rapidly pressing the volume keys or holding it down nothing would activate recovery. It boots into safe mode if I keep holding it down.
XDA STATUS UPDATE:
I'm at a TAPAsBar, flashing around my ZL.
Click to expand...
Click to collapse
Can you please do a new attempt and include your logs (if any) mentioned in the OP? I have nothing to work with now!
Sent from my C6603 using xda app-developers app
I am also not able to get into recovery by pressing either of the volume buttons
ehBrY said:
I just used this, and after finishing the process by restarting phone after the CWM prompt, and I restart again and try to press either up or down volume buttons during the green light, nothing happens it just keeps booting to ROM, I've tried rapidly pressing the volume keys or holding it down nothing would activate recovery. It boots into safe mode if I keep holding it down.
XDA STATUS UPDATE:
I'm at a TAPAsBar, flashing around my ZL.
Click to expand...
Click to collapse
R4GE199 said:
I am also not able to get into recovery by pressing either of the volume buttons
Click to expand...
Click to collapse
To both above:
Open a root explorer app, see if there is a folder called 'lost+found' inside /cache ... if it's not there, you need to use an FTF to restore it (just cache, nothing else!).
If it's there you can see the folders 'recovery' and 'XZDualRecovery' if an external SDCard (sdcard1) is absent, otherwise this last folder will be on your external SDCard. Create a file called 'boot' inside either one of directories. You will be able to boot to CWM that way. If you create a file called 'default' inside the XZDualRecovery folder and put in just the word 'twrp' (without quotes and no new line) to make it boot into TWRP when the 'boot' file is found.
Open CWM at first and do the advanced -> key test and provide me with the codes it produces while pressing the UP volume key once and the DOWN volume key once. Open the lid where your SIM is and with a paper-clip or pointy pen press the 'reset' button there to reboot your phone.
That way i know what to fix and what to check for during the boot of the script.
Don't worry guys, I'll get it fixed
[NUT] said:
If it's there you can see the folders 'recovery' and 'XZDualRecovery' if an external SDCard (sdcard1) is absent, otherwise this last folder will be on your external SDCard. Create a file called 'boot' inside either one of directories. You will be able to boot to CWM that way.
...
Open CWM at first and do the advanced -> key test and provide me with the codes it produces while pressing the UP volume key once and the DOWN volume key once.
Click to expand...
Click to collapse
Code:
CWM-based Recovery v6.0.3.2
Outputting key codes.
Go back to end debugging.
Key: 115
Key: 114
File "boot" after rebooting the system are removed.
Bird40 said:
Code:
CWM-based Recovery v6.0.3.2
Outputting key codes.
Go back to end debugging.
Key: 115
Key: 114
File "boot" after rebooting the system are removed.
Click to expand...
Click to collapse
Thats funny, the keycodes are the same on C6603 ... hmmm stuff to ponder on.
The boot file will be removed indeed, otherwise you would never be able to boot your phone in a normal way
-- EDIT --
I've found what is causing this... i'll do a ZL patch release soon.
[XZDualRecovery] Version 2.2 BETA released!
BETA Change log:
BETA releases will only appear on http://www.fun-industries.nl/xda/ and as soon as enough people report it to be working fine will it move in to the OP as a RELEASE version.
Version 2.2:
Fixed ZL Keycheck, again... :silly:
Did some more code cleaning, simplifying the SDCard1 mounting process.
Released the LINUX installer (Requires root privileges, so it will prompt for a sudo password) - Thanks go to @Androxyde for the adb binary!
Please update and test!
[NUT] said:
BETA releases
...
Version 2.2
...
Please update and test!
Click to expand...
Click to collapse
Thanks, it works.
I was able to get into CWM and TWRP 3 times.
[NUT] said:
How to remove:
...
Then inside /system/bin/ rename chargemon.stock to chargemon check its permissions (should be 755 or otherwise visible as -rwxr-x-r-x). ...
Click to expand...
Click to collapse
May be rwxr-xr-x?
Bird40 said:
May be rwxr-xr-x?
Click to expand...
Click to collapse
Nice spotting
Sent from my C6603 using xda app-developers app
2.2 is still not working for me. I noticed at the first attempt of this recovery modification, the restart message asked me if I wanted it to prevent the boot from changing my recovery again. And now when I'm trying to reinstall 2.2 over it, it never asked me that. Could that be why? How do I start from scratch if that's whats needed. It hasn't asked me that message again, just a normal restart phone message. I am anxious to do my TWRP backups, please advise! Again, the green light still comes on after 2.2 attempt, but still no luck on the volume key presses. Will the person that got it working with 2.2 please tell me what you did to get it working? Thanks ahead of time.
[NUT] said:
BETA Change log:
BETA releases will only appear on http://www.fun-industries.nl/xda/ and until enough people report it to be working fine will it move in to the OP as a RELEASE version.
Version 2.2:
Fixed ZL Keycheck, again... :silly:
Did some more code cleaning, simplifying the SDCard1 mounting process.
Released the LINUX installer (Requires root privileges, so it will prompt for a sudo password) - Thanks go to @Androxyde for the adb binary!
Please update and test!
Click to expand...
Click to collapse
ehBrY said:
2.2 is still not working for me. I noticed at the first attempt of this recovery modification, the restart message asked me if I wanted it to prevent the boot from changing my recovery again. And now when I'm trying to reinstall 2.2 over it, it never asked me that. Could that be why? How do I start from scratch if that's whats needed. It hasn't asked me that message again, just a normal restart phone message. I am anxious to do my TWRP backups, please advise! Again, the green light still comes on after 2.2 attempt, but still no luck on the volume key presses. Will the person that got it working with 2.2 please tell me what you did to get it working? Thanks ahead of time.
Click to expand...
Click to collapse
If you downloaded straight after the initial release, re-download it and try again. I made a mistake in the first BETA of 2.2...
There is a guide in the OP on how to remove this recovery modification.
Before you do try, check if you can remount /system as 'rw' using root explorer or es file explorer. If you phone goes into a reboot you probably said 'yes' where you never should in CWM.
If thats the case then try this:
Create the file 'default' in the XZDualRecovery folder in either /cache or /sdcard1 and put in the single word 'twrp'. Then create an empty file called 'boot' inside /sdcard1/XZDualRecovery/ or /cache/XZDualRecovery and reboot your phone. You will go in to TWRP the next boot.
Go to advanced -> file manager and navigate to /system/etc/ and look for a file called install-recovery.sh and fix it's permissions to be 755.
Reboot your phone and try the remount test again.
So just to clarify is the latest 2.2 Beta. Windows. Update or beta with nothing else? It would help if to ur file list shows the upload date. Thx I'll give it a try, so I should not say yes to that message in CWM on first boot? But that's the only option it gives me to reboot, if I press one of the many NOs it will still reboot?
XDA STATUS UPDATE:
I'm at a TAPAsBar, flashing around my ZL.
---------- Post added at 12:50 AM ---------- Previous post was at 12:46 AM ----------
When you say remount the system folder as RW do you mean changing the permissions to all RW? I just did that on solid explorer so that it is now 777 is that actually safe? Please advise thanks.
XDA STATUS UPDATE:
I'm at a TAPAsBar, flashing around my ZL.
ehBrY said:
So just to clarify is the latest 2.2 Beta. Windows. Update or beta with nothing else? It would help if to ur file list shows the upload date. Thx I'll give it a try, so I should not say yes to that message in CWM on first boot? But that's the only option it gives me to reboot, if I press one of the many NOs it will still reboot?
XDA STATUS UPDATE:
I'm at a TAPAsBar, flashing around my ZL.
---------- Post added at 12:50 AM ---------- Previous post was at 12:46 AM ----------
When you say remount the system folder as RW do you mean changing the permissions to all RW? I just did that on solid explorer so that it is now 777 is that actually safe? Please advise thanks.
XDA STATUS UPDATE:
I'm at a TAPAsBar, flashing around my ZL.
Click to expand...
Click to collapse
You can use the update package to get it up to the latest BETA release. I'm working on refining the download page, it will probably also contain the file date in that version. Thanks for the tip!
Oh after re-reading your question... whoops: you need to remount, not set permissions... Download root explorer or es file explorer to do so.
Just keep saying no, it will reboot no problem.
If you tried 2.2 beta and find it working, let us all know if it did!
Same in reverse, I need you people to feed me feedback whichever way it goes!
Sent from my C6603 using xda app-developers app
[NUT] said:
If you tried 2.2 beta and find it working, let us all know if it did!
Click to expand...
Click to collapse
Thanks, it works
Bird40 said:
Thanks, it works
Click to expand...
Click to collapse
Heh, I knew it worked for you, thanks for that and the testing, but I was actually referring to others downloading and getting no feedback
Sent from my C6603 using xda app-developers app
I AM NOT RESPONSIBLE FOR ANY NEGATIVE IMPACTS OR CONSEQUENCES ON YOUR PHONE IF YOU SO CHOOSE TO USE THIS GUIDE.
This is primarily for D802 users. However, people with other variants have had some issues and asked for help, so I have added some files here to help them as well.
PREREQUESITES
1) You must be rooted.
2) Then download one of the following files:
2.6.3.3
IMG
Download the D802 img file here.
Download the AT&T img file here.
Download the VZW img file here.
AUTO
Download the automated D802 file here.
Download the automated AT&T file here.
Download the automated VZW file here.
ZIP
Download the ZIP if flashing from a different TWRP version, or CWM: D802, AT&T, VZW
NOTE: If USB-OTG does not seem to be working on TWRP 2.6.3.3, please revert to 2.6.3.2. if this feature is needed.
Themes - Samurai Champloo
Download the theme itself here.
Download the Flashable ZIP of the theme here.
Download the Flashable D802 TWRP 2.6.3.3 and theme here.
2.6.3.2
Download the D802 img file here, or the latest official software F320K img file here.
Download the automated D802 file here, or the latest automated official software F320K file here.
Download the ZIP if flashing from a different TWRP version, or CWM: D802, F320K, TMO, VZW
INSTALLATION
Auto-Method
1) Extract the contents of the RAR file.
2) Double-click "Install.bat".
3) Prompt will open, click any button to proceed.
4) RSA Fingerprint message will appear on the phone (accept).
5) After installation procedure, type "y" and press enter to reboot into recovery!
1st Manual Method: Initiate ADB and use the following code.
Code:
[COLOR="DarkOrange"]REPLACE "XXX" WITH THE ACTUAL IMG NAME! DO NOT TYPE THE ORANGE WRITING![/COLOR]
adb push XXX.img /data/local/tmp/XXX.img
adb shell
[COLOR="DarkOrange"]IF YOU DONT SEE A # prompt, type su to get it.[/COLOR]
cd /data/local/tmp
dd if=/data/local/tmp/XXX.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
[COLOR="DarkOrange"]Be sure to replace "data/local/tmp" with the actual place your img is stored.[/COLOR]
exit
adb reboot recovery
2nd Manual Method: Place the img on your phone, then use a terminal emulator app with the following code.
Code:
[COLOR="DarkOrange"]REPLACE "XXX" WITH THE ACTUAL IMG NAME! DO NOT TYPE THE ORANGE WRITING![/COLOR]
su
dd if=/data/local/tmp/XXX.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
[COLOR="DarkOrange"](Be sure to replace "data/local/tmp" with the actual place your img is stored.)[/COLOR]
Optional Method: If you want to run some safety checks first, use loki [method here as first option].
INSTALL THEME MANUALLY
1) Connect your phone to your PC.
2) Go into your "internal storage" (internal SD card).
3) Find and open the TWRP folder.
4) Add a folder called "theme".
5) Place the ui.zip into the "theme" folder.
ENTER RECOVERY
Method 1: Hold the power button + volume down button until the LG image appears. Once it does let go of the buttons then immediately push and hold them again until recovery boots.
NOTE: The method above will arrive at the "hard reset" area, but when choosing hard reset, it will take you to TWRP (without actually resetting).
Method 2: Download the free app "Rebooter" from Google Play. If you have root, you will be able to select to reboot into recovery (among other options).
SLOW WIPE CACHE FIX
1) Once in TWRP, go into Settings.
2) Check off the box, "Use rm -rf instead of formatting."
3) Go back and now go into Wipe.
4) Wipe Cache (or another option with wiping cache).
Credit: Credit goes to Dees_Troy and wolfgart, djrbliss who made all recoveries for this phone possible, WACOMalt for his steps, and thecubed for his auto-install code.
USB-OTG
To access USB-OTG devices, go into the desired area (Install, Backup, or Restore). Select "Internal Storage" at the top. Press your USB-OTG device. It may take a second to show as selected on the screen. Once selected, press OK.
If your device does not show up, you can first try going to Mount and check off the USB-OTG box. If it doesn't allow you to check the box, then it doesn't support that device.
NOTE: It may not work with OTG cables and USB devices...
MISC.
Folder Name - There is an "issue" with the date and time [1970]. This issue is reflected in the backup folder names. There are two options to change a backup folder name:
Go into recovery and select Restore. Select the folder you wish to rename. There should now be an option to change the backup folder name.
Go into your TWRP folder by connecting to a PC or using a file explorer and change the backup folder name.
Time Zone - The time zone may be wrong but can be changed in Settings.
SUPPORT
Please check previous posts to see if your question has been answered prior to posting (there is a good chance it has).
Please always include with whether you are rooted or not.
Please always include the variant you are using.
Please always include the method you used.
Please always explain what happened in as much detail as possible.
Anything else that may be relevant.
Otherwise, you might have to wait for others to help you...
now for the mods and custom roms (hopefully kernels too)!!!! Thanks bros!
Thank you for all built hardwork. Was waiting for this.
-LG G2
Thank
Sent from my LG-D802 using Tapatalk 2
Thank you ! Flash successfull on my D802.
But when I want to wipe cache + dalvik cache, it stay on "wipe cache", it's normal issue ?
When I used Wipe Cache it took a long time to finish.
Ok thank you
Like 10 minutes or more ?
Envoyé depuis mon LG-D802 avec Tapatalk 4
I don't recall the exact time, but I would say at least 10 minutes.
Heatshiver said:
I don't recall the exact time, but I would say at least 10 minutes.
Click to expand...
Click to collapse
I have the same. But its not 10min. It is one min. Maximum two.
Sent from my LG-D802 using xda app-developers app
cosmique said:
I have the same. But its not 10min. It is one min. Maximum two.
Click to expand...
Click to collapse
I've noticed the time changing for certain things. One restore I did took nearly 30 minutes! I did restore after that took less than 10. As long as it works, that's all that matters! :good:
I'm on a Recovery Loop. Selected Reboot > System and it keeps rebooting to TWRP.
Used Flashify btw.
m0ngstr0us said:
I'm on a Recovery Loop. Selected Reboot > System and it keeps rebooting to TWRP.
Used Flashify btw.
Click to expand...
Click to collapse
Did you have a recovery before this installed? If so, what recovery? Did you have a good WiFi connection when you downloaded the file (i.e @home, @restaurant, etc.)? Did you try any other methods before flashify?
This should be fixable in either case. If you have a backup from before, I suggest restoring. If not, then you may have to follow this guide to unbrick your phone.
Oddly enough, I'll be in Singapore tomorrow, but I won't be able to reply until late night.
Works perfectly. Thanks!
Sent from my LG-D802 using xda app-developers app
Heatshiver said:
Did you have a recovery before this installed? If so, what recovery? Did you have a good WiFi connection when you downloaded the file (i.e @home, @restaurant, etc.)? Did you try any other methods before flashify?
This should be fixable in either case. If you have a backup from before, I suggest restoring. If not, then you may have to follow this guide to unbrick your phone.
Oddly enough, I'll be in Singapore tomorrow, but I won't be able to reply until late night.
Click to expand...
Click to collapse
Heya! Restoring as we speak. Home networks pretty stable.
Currently downloading the firmware. I can see that the system was not mounted on TWRP. Hence the Recovery bootloop.
Jumped from the Samsung era, gosh I didnt know LG doesnt have much support.
Once back up, bahhh imma just remain stock till more Devs pops up.
Cheers man.
m0ngstr0us said:
Heya! Restoring as we speak. Home networks pretty stable.
Currently downloading the firmware. I can see that the system was not mounted on TWRP. Hence the Recovery bootloop.
Jumped from the Samsung era, gosh I didnt know LG doesnt have much support.
Once back up, bahhh imma just remain stock till more Devs pops up.
Cheers man.
Click to expand...
Click to collapse
Feel free to try CWM, it's much easier to install, and also has a touch-interface.
Heatshiver said:
Feel free to try CWM, it's much easier to install, and also has a touch-interface.
Click to expand...
Click to collapse
I need sleeppppp ~ T.T Lol! Its 1:14am here man. Getting up at 6am later. Prolly another round (with CWM) over the weekends!
I travel to the airport in 4 hours, no rest for the wicked!
Heatshiver said:
I travel to the airport in 4 hours, no rest for the wicked!
Click to expand...
Click to collapse
Just want to check the link is still up, as i'm getting a dead page on the file.
Edit: Ignore the above, i couldnt get online at all. Rebooted and now all ok. Used Flashify to backup original and then flash TWRP.
Thanks
Sent from my LG-D802 using Tapatalk 4
can i use this method to upgrade from twrp 2.6.3 to 2.6.3.2 ?
j_h3000 said:
can i use this method to upgrade from twrp 2.6.3 to 2.6.3.2 ?
Click to expand...
Click to collapse
Yes. I have done so.
UPDATE: check out TowelRoot app by @geohot! One-click root solution that works with latest firmware released for Xperia M single/dual (provides half-root only, don't forget to apply root fixer)
Nicki Root is deprecated, it got merged in my new dd Flasher tool and works across many devices, not only Xperia M. The attachments and changelog from Nicki Root were kept below for archiving history, but I won't provide support for it anymore. For any problem you may encounter, go to dd Flasher thread. If you want to root Xperia M through dd Flasher, downgrade your device to Android 4.1 or 4.2.2 firmware, root it with Cydia Impactor and follow the instructions from dd Flasher thread.
Changelog
Version 2.0
• Nicki Root now is called dd Flasher
Old versions
Version 1.3.3
• Bugfixes for Linux script
• Updated SuperSU to 2.02
Version 1.3.2
• Make sure the temporary folder exists before pushing the script
Version 1.3.1
• Now compatible with Linux
Version 1.3
• Implement log capabilities (users can pull last log by selecting appropriate option in main menu)
• Drop "reboot in flash mode" (after using dd, system partition layout is different and device can't be rebooted)
• Check if LED can be used to indicate status, otherwise disable it
• Minor code changes
Version 1.2
• Rewrote most of the code
• Script now uses LED to indicate status
• By popular demand, dropped choice command in favour of set command (should work with Windows XP again)
• For every single command, script will now check if it failed or not and warn the user if anything get wrong
• Rewrote the mount/umount routine, loop device is selected automatically and resource busy issues are fixed now
• Can be used with half-rooted devices now (script check if device is fully rooted and apply root fixer at runtime if needed)
• Implemented "reboot in flash mode" command to avoid needing to pull/reinsert battery manually (experimental, sometimes doesn't work)
Version 1.1
• Make sure busybox is installed after first boot (previous versions pushed busybox but didn't install it)
• Drop choice32/choice64 applets and use built-in OS command (Windows XP no longer supported)
Version 1.0.1
• Typo fix (Nicky => Nicki)
• Updated busybox to 1.22.1
Version 1.0
• Initial release
Will test as soon as Indian Firmware Update show up...
Sent from my C2004 using Tapatalk
Well done @mbc07, this is great news. Dont forget to give credit to @joemarshall, afterall, he cane up with the idea . Thanks for testing it and creating this thread, nevertheless
sent from wadiya using my mafroom
I'll be trying this (probably) in the next hour, I'll post results for the Single SIM afterwards.
RESULTS TIME: This method of rooting worked and I am now running 4.3 with root access. Thank you.
Sent from my C1905 using xda app-developers app
Gonna test after I download 4.1.2 ftf, hope it works
rizla2 said:
Gonna test after I download 4.1.2 ftf, hope it works
Click to expand...
Click to collapse
It works perfectly, I'm now rooted on 4.3 thanks to this. The only error I had was when the tool first tried to push the system.ext4 to the SD Card, it said there wasn't enough space, I just deleted the incomplete copy and then ran the tool again and it worked.
Hmm, I'd not thought of mounting the image and doing dd, that is pretty tidy.
Balls, It didn't work for me first try, error mounting the loopback device, said it was busy. I'm re-flashing the phone back to 4.1 now. I've split the shell scripts into 2, first one does the modifications of system.ext4, second one does the dd flash, with a press any key between. That way if the modifications to system.ext4 fail, you're not stuck with an unrooted phone where system partition has already been written, and you can happily start again. I was flashing from sd card if that makes any difference.
Also, would it be possible to copy the reboot executable into your temp folder before you do the dd, so that you don't have to do the battery out reset in the middle of the process, or won't reboot work once you're in that state?
Edit: Second time lucky, thanks ever so much. Maybe I just needed to start from a blank slate version of 4.1, blimey that first boot takes some time though!
cheers,
Joe
mbc07 said:
It took me a lot of time and I tried a lot of methods but I finally managed to root the new 4.3 update without unlocking the bootloader, let's root that thing.
Requirements:
You will need FlashTool and the FTF file of 4.3 update for your phone
You should be running Android 4.1.2/4.2.2 firmware with full root. If you already updated to 4.3, sorry, you'll need to downgrade to 4.1.2/4.2.2 and root it, otherwise this method won't work
You should have at least 1.5GB of free space in your Internal Storage or in your SD Card. If you don't have enough space, the installation will be aborted and your phone will be left intact
Make sure you have full root (eg. your phone doesn't reboot when you remount /system with RW access). Using this method without full root may reboot your phone during the procedure, getting you in a bootloop
Currently the script works only on Windows, I'll try to get a Linux version soon
Getting system.ext4 file: before continuing, we'll need to extract system.ext4 from system.sin present in the update. Open the FTF it with WinRAR or 7-zip and extract system.sin somewhere, then open FlashTool, go to Tools => Sin Editor, locate the system.sin file extracted previously and then click in "Extract Data". You'll get system.ext4 in the same folder you extracted system.sin. Now you're good to go
Procedure:
Download the attached ZIP and unzip its contents somewhere
Move system.ext4 extracted previously to the same folder where root.bat is
Open root.bat and follow the instructions
After the process finished, the script will tell you and your phone will be in a frozen state (it's normal). At that point, you should manually remove the USB cable and then pull/reinsert your battery. DON'T TURN IT ON, we haven't finished yet (turning it on now will get you in a bootloop).
Open FlashTool again and flash the entire 4.3 FTF, but exclude system (if you forget to do so, the root will be removed and you'll need to start over)
After flashing finished, disconnect the USB cable and start your phone. If everything went well you should be in 4.3 now, with full root access
NOTE: I'm not that good with BASH/Shell scripts, and although I had implemented some sanity checks, something may have escaped that checks. So, if you do this procedure and the shell script finish with errors, it's better to start over since something may have not worked and you may be in a partial root state...
Click to expand...
Click to collapse
It worked for me thanks to you
About flashing 4.3 can I do a data and cache wipe?
Wysłane z mojego GT-P3110 przy użyciu Tapatalka
iks8 said:
About flashing 4.3 can I do a data and cache wipe?
Wysłane z mojego GT-P3110 przy użyciu Tapatalka
Click to expand...
Click to collapse
Flashtoll wil wipe data and cache when you flash 4.3 You don't need to do anything else.
paper13579 said:
Well done @mbc07, this is great news. Dont forget to give credit to @joemarshall, afterall, he cane up with the idea . Thanks for testing it and creating this thread, nevertheless
sent from wadiya using my mafroom
Click to expand...
Click to collapse
I still need to rework the OP, many people from Root for FTF 4.3 Update 15.4.A.0.23 LOCKED BOOTLOADER deserves credits, after all I wouldn't have that idea without their replies... Will get these guys credited in the OP soon
joemarshall said:
Hmm, I'd not thought of mounting the image and doing dd, that is pretty tidy.
Balls, It didn't work for me first try, error mounting the loopback device, said it was busy. I'm re-flashing the phone back to 4.1 now. I've split the shell scripts into 2, first one does the modifications of system.ext4, second one does the dd flash, with a press any key between. That way if the modifications to system.ext4 fail, you're not stuck with an unrooted phone where system partition has already been written, and you can happily start again. I was flashing from sd card if that makes any difference.
Also, would it be possible to copy the reboot executable into your temp folder before you do the dd, so that you don't have to do the battery out reset in the middle of the process, or won't reboot work once you're in that state?
Edit: Second time lucky, thanks ever so much. Maybe I just needed to start from a blank slate version of 4.1, blimey that first boot takes some time though!
cheers,
Joe
Click to expand...
Click to collapse
Thank you for the feedback, I'll try to add some sanity checks before using dd. About reboot, I tried using busybox reboot but nothing happened, the same for adb reboot. Apparently after using stop, the reboot command doesn't seems to work
Uh, I forgot... Anybody tried pushing to SD Card? Did it worked?
mbc07 said:
Uh, I forgot... Anybody tried pushing to SD Card? Did it worked?
Click to expand...
Click to collapse
Yes it did, sort of. The first time I did it I got an error saying there wasn't enough space (I had over 10GB free however). Once I got the error I deleted the incomplete file from my SD Card and then I ran the script again, this time it copied the file fully and then installed properly.
This occurred on the Single SIM C1905 Xperia M by the way.
Yes! Finally rooted. Thanks a lot!
Btw don't forget to change usb mode to mtp instead msc (I've tried msc and it can't copy files)
mbc07 said:
I still need to rework the OP, many people from Root for FTF 4.3 Update 15.4.A.0.23 LOCKED BOOTLOADER deserves credits, after all I wouldn't have that idea without their replies... Will get these guys credited in the OP soon
Thank you for the feedback, I'll try to add some sanity checks before using dd. About reboot, I tried using busybox reboot but nothing happened, the same for adb reboot. Apparently after using stop, the reboot command doesn't seems to work
Click to expand...
Click to collapse
At first time i've had also 'mount: mounting /dev/block/loop0 on /data/local/tmp/system failed: Device or res
ource busy'
Flash new, clean Android 4.1 solve problem.
Thank you very much.
Hey guys, does this give you full root?
sent from wadiya using my mafroom
paper13579 said:
Hey guys, does this give you full root?
sent from wadiya using my mafroom
Click to expand...
Click to collapse
Yes it does.
I'll check about the loop device errors (apparently they may occur in Xperia M single SIM), thanks for reporting guys...
paper13579 said:
Hey guys, does this give you full root?
sent from wadiya using my mafroom
Click to expand...
Click to collapse
Yes. I implemented the disable ric service method from [NUT] root fixer too
Man, this is a great achievement, you should be proud. Im about to try it now. Wish me luck
sent from wadiya using my mafroom
Before your script use dd it should check:
1. That there is no any apps mounted in /dev/block/loop0 (for example Swift Key). If yes, you will see 'mount: mounting /dev/block/loop0 on /data/local/tmp/system failed: Device or resource busy' (you can it by type losetup)
2. Phone is in MTP USB MODE. If you set to memory storage mode, Android will not access to sd card with system.ext4 image (script would check that can it access to /sdcard) and you will get mount argument error
zROM+ 28.0.A.8.251 Android 5.0.2 - V1.1Sony Xperia Z3+ E6553
ROM Features
Based on Sony firmware 28.0.A.8.251 Generic Hong Kong
Aroma installer
Deodexed and zipaligned
Rooted with SuperSU preinstalled
Dual boot/ TWRP recovery environment
Custom kernel with runtime control of SELinux enforcing status and RIC disabled
Google apps updated and with customizable graphical installer for Gapps
Writeable external SD card
Xposed framework functional (in SELinux permissive mode)
Bloatware removed
The following apps and bloatware have been removed and can be installed directly from the Play store if desired. The first two are installable by selecting the appropriate option in the ROM installer
What's New
Xperia lounge
AVG Antivirus
AAStocks
Anonymous Data Collection
Facebook
Lifelog
Mobisystems File Commander
Mobisystems Office
MyXperia
Playstation App
Playstation Network Portal
Privilege Movies
Sketch
Socialife
Sony Movie Creator
Spotify
Trackid
Please hit the Thanks button if you use this ROM. Many downloads but few thanks....
Installation instructions
NOTE: You must perform a factory reset before install by wiping cache and data.
Click to expand...
Click to collapse
Step 1
Download the TWRP image for the Z3+ and unpack it
Download zROM+ and the zROM+ md5 file
Run a command shell
Code:
c:>adb reboot bootloader
c:>fastboot boot recovery.img
c:>adb push zrom-v1.1.zip /sdcard/zrom-v1.1.zip
c:>adb push zrom-v1.1.zip.md5 /sdcard/zrom-v1.1.zip.md5
The file is big, so it will take 5 or more minutes to complete the upload. If you're impatient put your external SD in a card reader and load it that way.
Step 2
In the interface for TWRP, navigate to Wipe and perform a factory reset
In the interface for TWRP, navigate to Install
Click install, select zrom-v1.1.zip from the internal storage
Swipe to flash
Read and follow the instructions
Reboot when complete
Click to expand...
Click to collapse
The first boot is painfully slow. It takes about 10 minutes, so just be patient. It will stay in the blue booting screen for a long time. This is normal. Do not reboot your phone. Just wait and it will eventually boot up. You can always rerun the installer to flash additional Google Apps. If you do so, be sure to deselect the install ROM option and do not do a factory reset.
Notes
This ROM has a kernel that supports runtime SELinux mode changes. The mode change is accomplished through a script /system/su.d/permissive.sh, which sets SELinux to permissive mode at boot time. If you wish to run Xposed, you must run SELinux in permissive mode. Failure to do so results in multiple system applications force closing at startup and a device that is locked up.
If you don't run Xposed I recommend that you keep SELinux in enforcing mode. To do so, go to Settings-->About and click multiple times on the Build number until it tells you that Developer mode is activated. When developer mode is activated, back out and select the Developer option and enable USB debugging. Now run an adb shell and remove the permissive mode script. Grant permission for USB debugging when the prompt comes up
Code:
c:>adb shell
[email protected]:/ $ su
Wait for the SuperSU prompt and grant permission to adb
Code:
[email protected]:/ # mount -o rw,remount /system
[email protected]:/ # rm -f /system/su.d/permissive.sh
[email protected]:/ # reboot
If you choose not to install any of the Google apps, a minimum core Google framework will be installed anyway. This includes Google framework, GmsCore, Google Play, Google Login Services, Google Contacts and Backup Sync, SteupWizard and OneTimeInitializer that runs after first boot. Apart from the Play store app and the first time setup apps, the rest of these apps are not visible in your app drawer.
While I have made every effort to test this ROM in a variety of different install scenarios, it is a beta ROM and you may experience some bugs. I make no warranty as to its fitness for purpose or its performance and you use it at your own risk.
PLEASE SEE NOTE BBELOW IN POST TWO ON USING XPOSED FRAMEWORK
This ROM now supports booting directly into TWRP recovery mode. To access recovery mode, power on the phone and when you see the yellow LED illuminate press the down volume button once or twice.
Downloads
TWRP v2.8.7.0 for Z3+
zROM+ v1.1 for Z3+ (md5: 999452b5ac29f92473b964af819a3cd6)
zROM+ v1.1 for Z3+ MD5
for GPL purposes, the kernel and associated dowloads
Changelog
Current changelog: -- 01 October 2015
01 October - Release v1.1
Add dual boot/recovery environment
Remove Android Pay due to Google restrictions on root
Update Google apps
19 September - Release v1 beta
Thanks To/Credits
amarullz for the Aroma graphical installer
The OpenGapps team at www.opengapps.org for the Gapps binaries for aarch64
osm0sis for some of the functions used in the installer script
XDA:DevDB Information
zROM+, ROM for the Sony Xperia Z4
Contributors
dl12345
ROM OS Version: 5.0.x Lollipop
Based On: 28.0.A.8.251
Version Information
Status: Beta
Current Beta Version: v1.1 beta
Beta Release Date: 2015-10-01
Created 2015-09-20
Last Updated 2015-09-19
Xposed framework v74 bootloops on Xperia Z3+. The reason for this is discussed in this post
To use Xposed on zROM+, please download the [UNOFFICIAL] xposed-v74-sdk21-arm64-dl12345-UNOFFICIAL-20150929 for Xperia Z3+
You MUST do a wipe cache and dalvik after installation otherwise you will get errors including one that claims your storage space is full and another 504 error when installing anything from the Play Store
Please read the instructions in the referenced post
Have been waiting for this with baited breath. So far so good! Thanks for the great work!
Do need unlockbootloader to install rom?
manhhung1420 said:
Do need unlockbootloader to install rom?
Click to expand...
Click to collapse
Yes.
Thank you for your efforts.
Any chance that this ROM can work for E6533 (dual SIM) variant? Or can you plan to support?
Rookie123 said:
Thank you for your efforts.
Any chance that this ROM can work for E6533 (dual SIM) variant? Or can you plan to support?
Click to expand...
Click to collapse
Offhand, I'd say it's unlikely. Sony has a different firmware for this phone.
I'm unlikely to support a device I don't have access to. Apologies.
Works great thanks. Is there any way to make a sound mod to increase headphones volume?
pikeylfc said:
Works great thanks. Is there any way to make a sound mod to increase headphones volume?
Click to expand...
Click to collapse
There's probably something in the xposed repository for that....
Am so sorry to heard that I wanted to install a fresh rom on my hot phone
lilloscar said:
Am so sorry to heard that I wanted to install a fresh rom on my hot phone
Click to expand...
Click to collapse
Sorry to hear what?
dl12345 said:
Sorry to hear what?
Click to expand...
Click to collapse
That this rom wont support the dual version
Great work! finally working recovery...but please..cant access my external sd card! fix this please!
chrisss5000 said:
Great work! finally working recovery...but please..cant access my external sd card! fix this please!
Click to expand...
Click to collapse
No problem here accessing my external SD card in recovery mode and when booted in the ROM. Have you formatted your external card? In recovery mode, the path to the external SD card is /external_sd...
so weird...try to enable it..but it dosent work...and the rom cant start...stock at bot sony xperia logo...
chrisss5000 said:
so weird...try to enable it..but it dosent work...and the rom cant start...stock at bot sony xperia logo...
Click to expand...
Click to collapse
You likely didn't do a wipe. Go to advanced wipe. Wipe dalvik cache, system, data, cache. Reinstall the rom.
dl12345 said:
You likely didn't do a wipe. Go to advanced wipe. Wipe dalvik cache, system, data, cache. Reinstall the rom.
Click to expand...
Click to collapse
I have installed roms like hundrad times...I did a factory reset and I did advanced wipe etc...dosent work..so weird..
I guess something is wrong..something with premissions? Because every time I have wiped my phones it takes a while..But when I wiped now with this recovery it was done in a heart beat...
chrisss5000 said:
I have installed roms like hundrad times...I did a factory reset and I did advanced wipe etc...dosent work..so weird..
I guess something is wrong..something with premissions? Because every time I have wiped my phones it takes a while..But when I wiped now with this recovery it was done in a heart beat...
Click to expand...
Click to collapse
You're installing on a Z3+ e6553 single sim version, right? My wipes are pretty quick too....once the wipe is done, go to the mount option in recovery, mount the filesystems and make sure they're empty (well, they will contain a lost+found folder for the ext4 filesystems and your sdcard contents for the /data filesystem).
Permissions are unlikely to be the problem. The ROM is untarred from an ext4 filesystem copy, so original filesystem permissions are preserved. It also installs an updated file_contexts and does a selinux restorecon to make sure selinux contexts are correct...
dl12345 said:
You're installing on a Z3+ e6553 single sim version, right? My wipes are pretty quick too....once the wipe is done, go to the mount option in recovery, mount the filesystems and make sure they're empty (well, they will contain a lost+found folder for the ext4 filesystems and your sdcard contents for the /data filesystem).
Permissions are unlikely to be the problem. The ROM is untarred from an ext4 filesystem copy, so original filesystem permissions are preserved. It also installs an updated file_contexts and does a selinux restorecon to make sure selinux contexts are correct...
Click to expand...
Click to collapse
Incidentally, on first boot, it takes a few minutes to get past the Sony logo. then once you hit the blue screen be prepared for a 10 minute wait...
dl12345 said:
Incidentally, on first boot, it takes a few minutes to get past the Sony logo. then once you hit the blue screen be prepared for a 10 minute wait...
Click to expand...
Click to collapse
Yes it is Xpera Z3+ E6553
Okay I will test it now! I will come back with results
big thanks!!
---------- Post added at 08:05 PM ---------- Previous post was at 08:00 PM ----------
dl12345 said:
Incidentally, on first boot, it takes a few minutes to get past the Sony logo. then once you hit the blue screen be prepared for a 10 minute wait...
Click to expand...
Click to collapse
Uhm should the installing just take 15 sec? I nearly drop my finger from the screen and it is wiped....something is wrong...
---------- Post added at 08:07 PM ---------- Previous post was at 08:05 PM ----------
dl12345 said:
Incidentally, on first boot, it takes a few minutes to get past the Sony logo. then once you hit the blue screen be prepared for a 10 minute wait...
Click to expand...
Click to collapse
it dosent work...it only get stuck at sony loggo
Hi All!!
This thread will now contain pre rooted Odin files for F926B users to flash and update
Before you start, download "420rom_F926B_BVA9_Odin_EUY.zip" from HERE
THIS IS FOR F926B ONLY
The process requires knowledge of basic adb and YOU MUST HAVE ADB INSTALLED BEFORE TRYING THIS
This will no longer wipe data but it is advisable to backup first anyway - i wont be responsible for any data lost that could have been backed up
PROCESS to update from rooted a11 or a12
1 - Unzip the 4 odin files from the zip provided in the link above & connect phone to PC
2 - load ODIN on PC and disable AUTO Reboot - Next load BL.tar in BL, AP.tar in AP, Stock CP in CP and Stock HOMECSC in CSC
3 - Click start to flash the files - when completed, keeping phone connected to PC, press and hold power and volume down and as soon as the screen turns off, press and hold vol up and power UNTIL in TWRP
4 - Head to the TWRP mount menu disable MTP
5 - ONLY IF YOU DONT HAVE A MAGISK.ZIP ON INTERNAL STORAGE copy app-debug.zip to your adb folder and then open a command window and first confirm adb is working by typing adb devices you should see your device listed and "recovery" next to the device in command window - this means adb is working - type adb push app-debug.zip /sdcard this should send the app-debug.zip to internal storage (or sdcard if you prefer)
6 - go to the TWRP flash menu and you should see the app-debug.zip, flash it to root your A12 device - this needs to be done everytime TWRP is flashed in Odin it seems
7 - reboot to system from TWRP power menu
You will boot rooted, updated and with intact data if all the steps above are followed correctly
------------------------------------------------------------------------------------------------------------------
PROCESS IF COMING FROM STOCK A12
1 - Unzip the 4 odin files from the zip provided in the link above & connect phone to PC (please ensure dev settings are enabled and that you have unlocked bootloader and checked "Oem unlock" is faded out under dev settings)
2 - load ODIN on PC and disable AUTO Reboot - Next load BL.tar in BL, AP.tar in AP, Stock CP in CP and Stock HOMECSC in CSC
3 - Click start to flash the files - when completed, keeping phone connected to PC, press and hold power and volume down and as soon as the screen turns off, press and hold vol up and power UNTIL in TWRP
4 - Head to the TWRP wipe menu and format device (type yes and press enter) - then reboot TWRP
5 - when TWRP has rebooted, go to the mounts menu and disable MTP -> this will allow us to send app-debug.zip (magisk) to your sdcard
6 - copy app-debug.zip to your adb folder and then open a command window and first confirm adb is working by typing adb devices you should see your device listed and "recovery" next to the device in command window - this means adb is working
7 - type adb push app-debug.zip /sdcard this should send the app-debug.zip to internal storage (or sdcard if you prefer) - go to the TWRP flash menu and you should see this app-debug.zip, flash it to root your A12 device
8 - as stated previously, i have disabled encryption therefore we just need to boot STRAIGHT to SYSTEM from the TWRP POWER MENU
9 -When phone reboots, set up as normal and you should now see a magisk stub in the app drawer meaning you are rooted
PLEASE NOTE THAT THE MAGISK PATCHED AP FILE IS UPLOADING AND WILL BE AVAILABLE IN A FEW HOURS
Reuploading patched AP file to Mega and will be available shortly
G-drive too a dump on me last night - apologies for the delay
@ianmacd is working on his disabler soon so we will be able to simplify things a bit also - thanks for bearing with me!!
ok my teammate has built a tested and working AP file to use in the guide above - this will be up very shortly
mine was fine however my internet connection is not lol
Ok guys - sorry for the muck about!! the patched AP file is now live in the first post - therefore you can go ahead and root!
Follow the steps carefully, please also read and make sure you have everything prepared before you start
Had a couple of peeps join my telegram chat asking about OEM option being missing.
Please note that this guide only covers the WWE F926B at the moment (US models have a locked bootloader afaik)
Thanks a lot for your work, Just got my hands on with the device.
Is losing the camera option inevitable?
There is no way to keep it enabled?
JazonX said:
Thanks a lot for your work, Just got my hands on with the device.
Is losing the camera option inevitable?
There is no way to keep it enabled?
Click to expand...
Click to collapse
At the moment there is sadly no camera til the bootloader is relocked. Hopefully a fix is found soon
exocetdj said:
Reuploading patched AP file to Mega and will be available shortly
G-drive too a dump on me last night - apologies for the delay
@ianmacd is working on his disabler soon so we will be able to simplify things a bit also - thanks for bearing with me!!
Click to expand...
Click to collapse
Hi, have you managed to upload it to Mega too? I can’t download it from google drive — it failed three times and now it tells me it’s inaccessible as too many people tried to download it...
白い熊 said:
Hi, have you managed to upload it to Mega too? I can’t download it from google drive — it failed three times and now it tells me it’s inaccessible as too many people tried to download it...
Click to expand...
Click to collapse
Hi mate have you managed to access it yet? if not ill try sort links out
白い熊 said:
Hi, have you managed to upload it to Mega too? I can’t download it from google drive — it failed three times and now it tells me it’s inaccessible as too many people tried to download it...
Click to expand...
Click to collapse
try this alternative link
If not ill ask my teammate to mirror to Mega
exocetdj said:
Hi mate have you managed to access it yet? if not ill try sort links out
Click to expand...
Click to collapse
Yeah, after an hour or so it let me in again, and didn’t fail this time. :O)
Killing the camera after unlocking the bootloader is a stupid and crappy move by Samsung.
I remember, oh so long ago, when Samsung actually supported us here on XDA, found quite a large number of things done by devs here suddenly appearing on their "next big thing", then they quietly withdrew their support and went over to the dark side of the Apple-verse.
ultramag69 said:
Killing the camera after unlocking the bootloader is a stupid and crappy move by Samsung.
I remember, oh so long ago, when Samsung actually supported us here on XDA, found quite a large number of things done by devs here suddenly appearing on their "next big thing", then they quietly withdrew their support and went over to the dark side of the Apple-verse.
Click to expand...
Click to collapse
They don't seem to care as much about the modding community nowadays it seems.
Iv had Sammy phones since s8 and been modding with roms since March last year and they've all been a ***** in some way to root
exocetdj said:
They don't seem to care as much about the modding community nowadays it seems.
Iv had Sammy phones since s8 and been modding with roms since March last year and they've all been a ***** in some way to root
Click to expand...
Click to collapse
See, now I'm starting to feel old.
Been here since S2.
Samsung actually had representatives on the forum. They actively helped with rooting and used features that were developed here on XDA, assuming with the dev's permission, in their latest phones (suffice to say most of the features we take for granted today were developed here).
Rooting was EASY. As simple as flashing CWM on to your phone. No worries about KNOX or losing any features. That came around the time of the Note 3 along with region locking.
ultramag69 said:
See, now I'm starting to feel old.
Been here since S2.
Samsung actually had representatives on the forum. They actively helped with rooting and used features that were developed here on XDA, assuming with the dev's permission, in their latest phones (suffice to say most of the features we take for granted today were developed here).
Rooting was EASY. As simple as flashing CWM on to your phone. No worries about KNOX or losing any features. That came around the time of the Note 3 along with region locking.
Click to expand...
Click to collapse
So from my understanding, Knox was actually designed for dual rom booting, as a way to keep the original firmware in tact and safe, but also be able to flash a custom rom for dual boot. But investors, carriers, and the like decided they weren't happy with that and saw that it could also be used to lock the device down to make everything more secure for their intents. After like 4 iterations where Samsung kept being pushed, it became what it is today.
I'm assuming they thought if they just impliment everything that a person would root for, that it would make people OK with it, but of course not the case. In the end, just like any other major corporation, they let money push them around
If we root, remove bloat, and then re-lock the bootloader, would the bloat still be gone? Knowing Sammy, they would prevent us from removing bloat.
I can handle holding out on flashing a sweet ROM if I can remove garbage like Bixby.
As soon as you flash any custom binary then your software is classed as custom and will not boot at all with a locked bootloader. It would soft brick requiring a stock odin flash to revive device most likely
dirtybudha said:
If we root, remove bloat, and then re-lock the bootloader, would the bloat still be gone? Knowing Sammy, they would prevent us from removing bloat.
I can handle holding out on flashing a sweet ROM if I can remove garbage like Bixby.
Click to expand...
Click to collapse
You can remove and/or disable bloat with adb commands for now. There is a thread about it somewhere in our forum
Samkey apparently now supports f926b but I'm getting unsupported firmware errors on AUG8 and AUHF. I really want to get rid of this three bloat