Related
he guys well i was going to install darky's rom until i saw that u needed 2erecovery if ur on froyo witch i am. iv heard about odin but u need the three button combo which i dont!!! sooo i need to know how to get 2erecovery
Sent from my GT-I9000 using XDA App
TheKoomba2010 said:
he guys well i was going to install darky's rom until i saw that u needed 2erecovery if ur on froyo witch i am. iv heard about odin but u need the three button combo which i dont!!! sooo i need to know how to get 2erecovery
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
just get 3btn combo working! it is easy...then
flash cf-root or hardcore's kernel with odin.....
http://forum.xda-developers.com/showthread.php?t=788108
Instructions (long)
- Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Unzip the attached CF-Root-JPx-vX.X.zip
- (USB) Disconnect your phone from your computer
- Start ODIN
- Click the PDA button, and select CF-Root-JPx-vX.X.tar
- Put your phone in download mode
- (USB) Connect the phone to your computer
- Make sure repartition is NOT checked
- Click the START button
- Wait for the phone to reboot
- Done (if it took you more than 30 seconds, you need practise!)
If you are on a JPx FW then all i did was flash the speedmod kernel via odin which has CWM recovery and 2e on it.
Place Darkyy's rom on your SD card
Boot into recovery and install the Darkyy zip.
The entire process should take about 10 minutes.
TheKoomba2010 said:
he guys well i was going to install darky's rom until i saw that u needed 2erecovery if ur on froyo witch i am. iv heard about odin but u need the three button combo which i dont!!! sooo i need to know how to get 2erecovery
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Hi TheKoomba2010;10993474. Unrar the attachment below and use root explorer to copy the recovery from the file to system/bin. Make sure you backup the recovery from the system first (just in case). Then copy all the content in the xbin from the file and paste in the system/xbin and reboot. Good luck.
Thanks angiogram! it worked. Now I have 2e recovery.
angiogram said:
Hi TheKoomba2010;10993474. Unrar the attachment below and use root explorer to copy the recovery from the file to system/bin. Make sure you backup the recovery from the system first (just in case). Then copy all the content in the xbin from the file and paste in the system/xbin and reboot. Good luck.
Click to expand...
Click to collapse
Wow, does this really work???
I have been looking something simple to enable 2e recovery, but all I could find was flashing kernel methods.
am i supposed to delete the contents of the xbin folder? phone didnt boot into recovery mode after following steps just stuck on Galaxys GT-I9000 screen
hi all....total Android noob here...
after a lot of research and some 'should i or shouldn't i' episodes, i've successfully rooted my wonder in order to flash to cm9. along the way i've discovered that it is 'desirable' to have cwm 6 installed first.
from what i understand, there are 2(?) ways of doing this...either via stock recovery in the ADB(?) shell or via ODIN...
ODIN *seems* to be the preferred method though. but here lies my problem.....i can't get it to work...i've found several links to download odin, and several links to download cwm 6.....also several different sets of instructions as to how to actually do it.....
it would really help if i had one set of downloads for odin and cwm 6 and one set of step by step, clear, precise, tried and tested instructions....
i've also tried nandroid backup as a 'partial' alternative to cwm 6, but it's not compatible with my phone.
additional info (if needed).....
os version - gingerbread 2.3.5
carrier - 3UK
kernel version - 2.6.35.7-perf-I8150XXK18-CL604835
[email protected] #3
many thanks in advance.....
Keith
Here is the way to flash CWM6 using Odin, if you wanna flash CWM5 just use the md5&ops files for CWM5, which you may need to find them somewhere
1. Download Odin & Ancora.ops & recovery-clockwork-6.0.1.2-ancora.tar.md5
2. Enable USB Debugging in Setting-Application- Development
3. Open Odin.
- Select the ops file, and enable one package in options
- then load the md5(recovery-clockwork-6.0.1.2-ancora.tar.md5) file with the One Package button.
- put ur phone it into download mode, first turn off phone, then hold Volume Down + Home + Power Button for a while.
- Phone will turn on and show some screen, then you plug in usb cable (it may look for the driver through Windows Update so please enable your computer's Internet connection).
Get the files (please find Odin from somewhere else): http://forum.xda-developers.com/showthread.php?t=1446593
Good luck and sorry for my bad English~
THESE STEPS NEEDS ROOT & BUSYBOX, DOESN'T NEED PC & ODIN..
FOR BEST RESULT, UPDATE YOUR SUPERUSER.APK, SU BINARY, AND BUSYBOX
-go here http://www.mediafire.com/?6wkwiko5gmqhuyr link by acro68 the author of W's CM9 and who made CWM possible to our device
-download and extract it..
-put the recovery.img in /mnt/sdcard
-download "Terminal Emulator" by Jack in market (FREE OF COURSE)
-open it then type "su" and click enter
-allow root access..
-then type "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13" then click enter <~ THAT IS "0" (ZERO) not "O" word..
-then some text will show in bottom
-exit terminal.. check the recovery by turning off the device then turn on with volume up botton, home button, and power button pressed together.. until "Galaxy W" screen shows up, release the power button only.. then you will enter CWM
-navigate with up (up) n down (down) vol button and home keys (select) and power (back) and click "reboot system now" to reboot
HAPPY FLASHING
*I'm not responsible if your phone bricked*
thank you both for your responses....greatly appreciated....
i thought i'd try IvanKurnia's method first as i thought it looked the easiest
it worked first time i'm happy to report........
i can finally feel a dose of CM9 goodness coming on.....yaay..lol
keithross39 said:
thank you both for your responses....greatly appreciated....
i thought i'd try IvanKurnia's method first as i thought it looked the easiest
it worked first time i'm happy to report........
i can finally feel a dose of CM9 goodness coming on.....yaay..lol
Click to expand...
Click to collapse
You are always welcome...Glad to hear that...Good luck to your CM9 ^^ Now we got more choices of CM9 since quite a number of people had ported AOKP and some other builds to it
MyDeSTiNaTe said:
2. Open Odin.
- Select the ops file, and enable one package in options
- then load the md5(recovery-clockwork-6.0.1.2-ancora.tar.md5) file with the One Package button.
- put ur phone it into download mode, first turn off phone, then hold Volume Down + Home + Power Button for a while.
- Phone will turn on and show some screen, then you plug in usb cable (it may look for the driver through Windows Update so please enable your computer's Internet connection)
Click to expand...
Click to collapse
did you forget to add -enable the "USB Debugging" on Setting-?
if you're gonna flashing stock rom with ODIN, you're not gonna need USB Debugging setting..
but if recovery, you need it..
IvanKurnia said:
did you forget to add -enable the "USB Debugging" on Setting-?
if you're gonna flashing stock rom with ODIN, you're not gonna need USB Debugging setting..
but if recovery, you need it..
Click to expand...
Click to collapse
Oh yea, thanks for reminding, I always enabled it so I forgot to mention that
Hi,
how can I know if CWM6 is compatible with my kernel?
Thanks a lot.
Model code: GT-I8150
Android version: 2.3.6
Version base band: I8150XXKL3
Kernel version: [email protected] #3
Build version: GINGERBREAD.XXLA2
as far as I know, recovery has it's own kernel..
Hi all...installed CM9 last night...all went well....
Have noticed that there's no Task Manager or Media Player Apps....is it just that I'm looking right at them and not recognizing them for what they are, or are they not included in the build?....if they're not included, which 3rd party apps would you recommend for use instead?.....
Also, for information, I had ONE minor glitch occurrence when using the camera.....as follows...
Started camera app..
Changed from primary to secondary (self portrait) camera...
Changed the exposure setting to +2....
App force closed.....
Apart from that, no other issues to report.....
A big thanks to everybody involved for taking the Galaxy W and producing such a fantastic alternative to 'stock'.....
PS......will cm10 be ported to the W?....lol...(got the Modding bug now . )
Sent from my GT-I8150 using xda app-developers app
Hi again....can confirm that the force close camera issue (as described above), is a continuing problem on all increments of exposure compensation setting. With that in mind, is there a 3rd party camera app available that has the same functionality as the installed app but without the gimmicks?......
As mentioned before, CM9 really is a welcome step up from the 'stock' OS, so if the camera issue is the only issue with CM9, it's still worth 'taking that leap'.....
Once again, many thanks for the work put in on this....Keith
Sent from my GT-I8150 with CM9 using xda app-developers app
better you post that on "CyanogenMod 9 bug report & discussion thread" by THE-E.. so then the bug will added to the list
CM9 very good right if there weren't any bugs..
IvanKurnia said:
THESE STEPS NEEDS ROOT & BUSYBOX, DOESN'T NEED PC & ODIN..
FOR BEST RESULT, UPDATE YOUR SUPERUSER.APK, SU BINARY, AND BUSYBOX
-go here http://www.mediafire.com/?6wkwiko5gmqhuyr link by acro68 the author of W's CM9 and who made CWM possible to our device
-download and extract it..
-put the recovery.img in /mnt/sdcard
-download "Terminal Emulator" by Jack in market (FREE OF COURSE)
-open it then type "su" and click enter
-allow root access..
-then type "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13" then click enter <~ THAT IS "0" (ZERO) not "O" word..
-then some text will show in bottom
-exit terminal.. check the recovery by turning off the device then turn on with volume up botton, home button, and power button pressed together.. until "Galaxy W" screen shows up, release the power button only.. then you will enter CWM
-navigate with up (up) n down (down) vol button and home keys (select) and power (back) and click "reboot system now" to reboot
HAPPY FLASHING
*I'm not responsible if your phone bricked*
Click to expand...
Click to collapse
It worked great, thanks a lot!
I would just suggest to add the following step BEFORE flashing CWM6, in order to have a backup of the existing recovery image:
dd if=/dev/block/mmcblk0p13 of=/sdcard/mybackup.img
[.::MDT::.] said:
It worked great, thanks a lot!
I would just suggest to add the following step BEFORE flashing CWM6, in order to have a backup of the existing recovery image:
dd if=/dev/block/mmcblk0p13 of=/sdcard/mybackup.img
Click to expand...
Click to collapse
yes.. add it.. don't forget to access root first by typing "su"
IvanKurnia said:
yes.. add it.. don't forget to access root first by typing "su"
Click to expand...
Click to collapse
Actually it worked for me even without typing "su" before...
[.::MDT::.] said:
Actually it worked for me even without typing "su" before...
Click to expand...
Click to collapse
what?! without typing "su" you will not be able to access root..
eh, did you have your USB Debugging enabled? maybe because of it..
Moving CWM6 backups to PC
Hi guys, I have a question here. How can I move my backups I created using CWM6 to a PC so I can free up my internal sd space? I don't think those folders on clockworkmod\backup are full backups because the blob folder is much larger.
I'm using Samsung Galaxy W I8150, CWM 6.0.1.2, CM9 Alpha7.
buruguduy said:
Hi guys, I have a question here. How can I move my backups I created using CWM6 to a PC so I can free up my internal sd space? I don't think those folders on clockworkmod\backup are full backups because the blob folder is much larger.
I'm using Samsung Galaxy W I8150, CWM 6.0.1.2, CM9 Alpha7.
Click to expand...
Click to collapse
just copy or cut the "clockworkmod" folder, to prevent file corrupt, rar or zip it.. if want to restore, copy or cut back to your SD..
safe backup
IvanKurnia said:
just copy or cut the "clockworkmod" folder, to prevent file corrupt, rar or zip it.. if want to restore, copy or cut back to your SD..
safe backup
Click to expand...
Click to collapse
did you already tried it? if i cut it manually from my phone, is there a risk CWM would be corrupted? sorry noob here..
buruguduy said:
did you already tried it? if i cut it manually from my phone, is there a risk CWM would be corrupted? sorry noob here..
Click to expand...
Click to collapse
have already and safe.. BUT:
-make sure your USB Cable is still in good condition.. if you are not sure, DO NOT MOVE CABLE WHILE COPYING FILES..
-you had fast enough PC.. DO NOT COPY FILES WHILE LAGGING
-NO VIRUS ON YOUR PC..
-make sure NO SOFTWARE BLOCKING YOUR PHONE DRIVER..
-if you backup to external sd, BETTER USE CARD READER TO COPY THOSE FILES TO PC
-IF ZIPPING OR RARING FILES, DP NOT COMPRESS LIKE CRAZY (COMPRESS NORMAL OR JUST STORE -without compression-)
-always reject/unmount removeable drive TO PREVENT CORRUPT FILES ON YOUR SD, USB, OR ETC..
safe backup
-=[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