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
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
Motorola Defy Mini XT320/XT321 all-in-one script/utility
I've ported mattlgroff's DROIDRAZR all-in-one Script to the Motorola Defy Mini XT320/XT321. This will make life easier and it will do it for you.
Make sure you have fastboot mode if not please refer to this guide for fastboot but there is a fastboot checker in option 6 but it won't install fastboot for you.
Link: http://forum.xda-developers.com/showpost.php?p=36199694&postcount=3
Options available:
1. Root your Motorola Defy Mini XT320/XT321
2. Install 2nd-init/TWRP Recovery
3. Overclock installation
4. Unroot Device
5. Wipe Data/Factory Reset
6. Fastboot checker.
7. Exit Utility
Instructions:
NEW PACKAGE & instructions
1. Download the EXE file at http://www.mediafire.com/?c81fnrtrki65e9i
2. Double click on the exe.
3. Choose an option by entering a number from 1 to 7
OLD PACKAGE & instructions
1. Download package at [REMOVED OLD LINK]
Please Download the fixed package at http://www.mediafire.com/?krxtemrthsz5ier
EXE Version: http://www.mediafire.com/?0kwmx4whjj1ua8c
2. Extract the zip file making sure all the files are in the same place.
3. Click on the batch file named 'DefyMiniUtility.bat'
4. Choose an option by entering a number from 1 to 7.
Credits to:
- Bernd.Defy for overclock module and Guitwo2 for init.d script
- Guitwo2 and jkkk88 for TWRP and aweosomeabhjeet for 2nd-init
- DoOMLoRD for unroot script
- Mattlgroff for the original DROID RAZR all-in-one script
If anyone knows if I missed a member for the credits, please PM me. Thanks
Make sure press thanks if it works
Guys please don't repost it as your own work, otherwise I'll report it and you will get banned from XDA.
NOTE: If you have previously used the old EXE to install TWRP then please remove the old folders by using these instructions using cmd before using updated exe to install TWRP;
1.
Code:
adb shell
2.
Code:
su
3.
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock11 /system
4.
Code:
rm -R /system/bootmenu
Then use the updated exe to install TWRP.
NOTE: If you don't like TWRP, you can download Guitwo2's Permanent CWM at http://forum.xda-developers.com/attachment.php?attachmentid=1875373&d=1365682716
Temporary CWM Recovery: http://forum.xda-developers.com/attachment.php?attachmentid=1875299&d=1365680458
2nd-init does NOT work in CWM Recovery
Thanks to @Guitwo2 for CWM Recovery.
Instructions on how to install Permanent CWM Recovery:
1. Make sure stericson-busybox is installed
2. Put XT320_bootmenuV2.zip in the root of your sdcard
3. Reboot into fastboot mode by typing this command in cmd:
Code:
adb reboot bootloader
4. Then type this command in cmd:
Code:
fastboot boot recovery.img
5. Then use volume keys to navigate and power button to select option. Select install zip from sdcard, then select XT320_bootmenuV2.zip and select yes to install the zip file
6. Then reboot device by selecting reboot device now.
CWM 6 has a bug where it asks you to 'disable recovery flash' when you select reboot system now make sure you select NO or you will soft brick your device.
Changelog:
-v2 No need to mount /sdcard in CWM Recovery. Fixed TWRP installation issues.
-v2.0.1 Released an .exe version of script, to simplify installation
-v2.0.1.1 Fixed bootmenu.zip
This can install a custom recovery?
This can install a custom recovery?
Thank you
The root process worked for me. Now i can install link2sd and set up a swap partition.
I cant install TWRP and i think the reason is that the bat was having some problem to send that bootmenu.tar file to my sd card. I tried to send that file myself before starting the entire process and it didnt worked.
I took a picture of the error i'm getting . Thank you again, i was really mad about that low internal space xD
same problem... someone can fix it? please
fca.sjc said:
The root process worked for me. Now i can install link2sd and set up a swap partition.
I cant install TWRP and i think the reason is that the bat was having some problem to send that bootmenu.tar file to my sd card. I tried to send that file myself before starting the entire process and it didnt worked.
I took a picture of the error i'm getting . Thank you again, i was really mad about that low internal space xD
Click to expand...
Click to collapse
sfoot13 said:
same problem... someone can fix it? please
Click to expand...
Click to collapse
Ok, I've made a fixed script here. The error was that the sdcard is a directory so it will refuse to push files into it.
Here's the updated script below. Just put the .bat file in the same place as the other files.
Thanks
rootdefyxt320 said:
Ok, I've made a fixed script here. The error was that the sdcard is a directory so it will refuse to push files into it.
Here's the updated script below. Just put the .bat file in the same place as the other files.
Click to expand...
Click to collapse
Ty for the quickly answer.
Btw, my gsm network wasnt working after the root process. If the same thing happens to someone else, just do a master reset and it will work again.
pull command is working now
That sdcard copy part is working now. The TWRP process is still not working for me. I tried to do myself the commands using the adb interface and when i use the command to intall the tar, i got the message 'tar: no space left on device" . I hope you can help me with that and i'm sorry about all this questions xD .
fca.sjc said:
That sdcard copy part is working now. The TWRP process is still not working for me. I tried to do myself the commands using the adb interface and when i use the command to intall the tar, i got the message 'tar: no space left on device" . I hope you can help me with that and i'm sorry about all this questions xD .
Click to expand...
Click to collapse
You must have more than 5MB free in your /system partition. Please move your apps to the /flex partition or delete the useless apps in /system.
rootdefyxt320 said:
You must have more than 5MB free in your /system partition. Please move your apps to the /flex partition or delete the useless apps in /system.
Click to expand...
Click to collapse
Thank u so much to everyone who make it possible xD
(can i do now a overclock to 720 without problems?)
sfoot13 said:
Thank u so much to everyone who make it possible xD
(can i do now a overclock to 720 without problems?)
Click to expand...
Click to collapse
Yes but it sometimes gets unstable so you should overclock to 700MHz which is the highest I got without reboots. pll2_l_val=73 gives you 700MHz.
rootdefyxt320 said:
Yes but it sometimes gets unstable so you should overclock to 700MHz which is the highest I got without reboots. pll2_l_val=73 gives you 700MHz.
Click to expand...
Click to collapse
Thank u so much and TWRP doesn't work xD i have 8.5 mb free on system but it can't create the folders on bootmenu
sfoot13 said:
Thank u so much and TWRP doesn't work xD i have 8.5 mb free on system but it can't create the folders on bootmenu
Click to expand...
Click to collapse
I've released an .exe version of my script. This should work now .
Link: http://www.mediafire.com/?0kwmx4whjj1ua8c
Thank u bro and sorry but i can't overclock it to 700 =/
i installed TWRP but it doesn't work and when i turn on my mobile it freezes on home screen :/ is a mess.... it's possible install it via recovery (temportal CWM)?
OFF TOPIC.
Congrats on your well deserved mention on the portal.
sfoot13 said:
i installed TWRP but it doesn't work and when i turn on my mobile it freezes on home screen :/ is a mess.... it's possible install it via recovery (temportal CWM)?
Click to expand...
Click to collapse
It worked for others but in your situation the only thing I can advise is to do a data wipe and relfash SBF file. Just go to Guitwo2's there to install permanent CWM.
Link: http://forum.xda-developers.com/showthread.php?t=2229233
rootdefyxt320 said:
It worked for others but in your situation the only thing I can advise is to do a data wipe and relfash SBF file. Just go to Guitwo2's there to install permanent CWM.
Link: http://forum.xda-developers.com/showthread.php?t=2229233
Click to expand...
Click to collapse
:good: Working! Thank u so much, now i have CWM working on my defy mini, i'm really thankful, thanks again
Hi, it's me again... i have a new trouble
i installed the xt320_bootmenu.zip (from this thread http://forum.xda-developers.com/showthread.php?t=2229233) the first time that i rebooted works fine, but the on the second reboot it doesn't work, then i went to data to check if test.log was there and here's the problem... no test.log...
init.d was working fine until that i did it, i guess that my phone have troubles making work init.d
some solution for this annoying guy? thanks in advance!
sfoot13 said:
Hi, it's me again... i have a new trouble
i installed the xt320_bootmenu.zip (from this thread http://forum.xda-developers.com/showthread.php?t=2229233) the first time that i rebooted works fine, but the on the second reboot it doesn't work, then i went to data to check if test.log was there and here's the problem... no test.log...
init.d was working fine until that i did it, i guess that my phone have troubles making work init.d
some solution for this annoying guy? thanks in advance!
Click to expand...
Click to collapse
Looks like 97bootmenu deleted itself, please reinstall the CWM zip again and it should work.
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:
Ace 2 Gt-i8160L LATIN. How to install CM?
When I install CM, don't wok sim-card and not IMEI.
Restore IMEI don't helped.
This is modem or hw problems, i think.
Sorry my english is bad.
...
Replace tee folder in rom zip /system/lib with the one from stock rom
Sent from my GT-I8160 using Tapatalk
1) backup tee folder
2) On build.prop change all GT-I8160L to GT-I8160 (without L)
3) all wipes factory/cache/dalvik
3) Install CM_Xversion
4) Whith roo explorer replace tee folder
Enjoy.
2) also can delete assert :/
4) you can just replace in zip before flashing (just sayin)
Sent from my GT-I8160 using Tapatalk
When to alter ROM
teddytsen said:
2) also can delete assert :/
4) you can just replace in zip before flashing (just sayin)
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
Am located in New Zealand, and hence using model i8160L, running stock JB ROM
Am trying to modify / install Maclaw CM KK ROM -- but am having problems
-- it "reads" the ROM and "immediately" (afaik) but aborts installation
-- NO ERROR MESSAGES come up for any indication as to why it's aborting
Am trying to do the following -- appreciate any feedback to correct procedure if I'm making eny errors
(i) omitting any and all references to L in 8160L string -- should I restrict it to any particular lines? -- using Build.Prop Editor
-- the Settings/About Device shows it as an 8160, rather than an 8160L after the Build.Prop changes, but the boot screen still shows it as the 8160L -- but at least I don't get the error message about trying to install ROM on wrong device
(ii) before attempting installation, downloading the latest ROM, unzipping the ROM using 7zip, deleting "tee" folder
-- and pasting tee folder from the stock JB ROM installed on my phone
(iii) re-zipping the ROM using 7zip -- I notice I get a different MD5 to that llsted on the download page
(iv) attempting to flash the modified ROM in Recovery mode, but it aborts
Don't know enough to know if install procedure tries to validate the "to be installed" ROM's MD5 and aborts since it's different from that on the download page
Don't know what purpose of tee folder is -- is it to connect to local carrier?
How about if I try to install "unmodified" ROM (in its unmodified form) and once it's installed, if it does (?), replace the tee folder at that later stage, to check for ability to connect to carrier?
Do I need to unlock the SIM card first --- as that's also something I haven't done
(naturally, I've backed up and able to restore to what I had before attempting the install)
KiwiCool60a said:
Am located in New Zealand, and hence using model i8160L, running stock JB ROM
Am trying to modify / install Maclaw CM KK ROM -- but am having problems
-- it "reads" the ROM and "immediately" (afaik) but aborts installation
-- NO ERROR MESSAGES come up for any indication as to why it's aborting
Am trying to do the following -- appreciate any feedback to correct procedure if I'm making eny errors
(i) omitting any and all references to L in 8160L string -- should I restrict it to any particular lines? -- using Build.Prop Editor
-- the Settings/About Device shows it as an 8160, rather than an 8160L after the Build.Prop changes, but the boot screen still shows it as the 8160L -- but at least I don't get the error message about trying to install ROM on wrong device
(ii) before attempting installation, downloading the latest ROM, unzipping the ROM using 7zip, deleting "tee" folder
-- and pasting tee folder from the stock JB ROM installed on my phone
(iii) re-zipping the ROM using 7zip -- I notice I get a different MD5 to that llsted on the download page
(iv) attempting to flash the modified ROM in Recovery mode, but it aborts
Don't know enough to know if install procedure tries to validate the "to be installed" ROM's MD5 and aborts since it's different from that on the download page
Don't know what purpose of tee folder is -- is it to connect to local carrier?
How about if I try to install "unmodified" ROM (in its unmodified form) and once it's installed, if it does (?), replace the tee folder at that later stage, to check for ability to connect to carrier?
Do I need to unlock the SIM card first --- as that's also something I haven't done
(naturally, I've backed up and able to restore to what I had before attempting the install)
Click to expand...
Click to collapse
md5 sum change probably because you uncompressed and re-compressed file.
no you dont have to unlock carrier.
use total commander and delete first 3 lines in updater-script.(all before mount.. bahblablah) and then compress it, then try.
btw it doesnt show any status errors?
When to alter ROM cont'd
teddytsen said:
md5 sum change probably because you uncompressed and re-compressed file.
no you dont have to unlock carrier.
use total commander and delete first 3 lines in updater-script.(all before mount.. bahblablah) and then compress it, then try.
btw it doesnt show any status errors?
Click to expand...
Click to collapse
MANY MANY thanks for your very prompt reply, and further information
"status errors" -- as a result of ?? -- no status errors evident after rebooting with modfified Build.Prop
had lots of "fun" on my previous efforts with custom ROMs -- played with several on a Huawei G300 I had --
-- but, gee, this is an ongoing learning process -- now to learn about updater script !!!
(only learnt about Total Commander from your post - despite its high rating -- but note others have used other things for "text editing")
(but have discovered some TUTs on xda)
Reading more carefully through the posts I see it may be possible to flash the ROM, and then later, substitute the tee folder supplied in the Maclaw ROM with the stock JB one -- right?
I'll definitely learn more about updater-script, but I'll try to flash the ROM again without modifying the ROM === OK?
KiwiCool60a said:
MANY MANY thanks for your very prompt reply, and further information
"status errors" -- as a result of ?? -- no status errors evident after rebooting with modfified Build.Prop
had lots of "fun" on my previous efforts with custom ROMs -- played with several on a Huawei G300 I had --
-- but, gee, this is an ongoing learning process -- now to learn about updater script !!!
(only learnt about Total Commander from your post - despite its high rating -- but note others have used other things for "text editing")
(but have discovered some TUTs on xda)
Reading more carefully through the posts I see it may be possible to flash the ROM, and then later, substitute the tee folder supplied in the Maclaw ROM with the stock JB one -- right?
I'll definitely learn more about updater-script, but I'll try to flash the ROM again without modifying the ROM === OK?
Click to expand...
Click to collapse
-Dont care about ro.build.model. once assert is deleted you dont have to change it. And its not mandatory.
-I recommended total commander just because its the only root browser i have that shows the assert in 3 lines exactly. Unless es etc. You can also use other editors ^.^
-like when installation is aborted, it says status 7(or 0 etc)
Sent from my GT-I8160 using Tapatalk
Many thanks -- now for the "rest" and time for tee
teddytsen said:
-Dont care about ro.build.model. once assert is deleted you dont have to change it. And its not mandatory.
-I recommended total commander just because its the only root browser i have that shows the assert in 3 lines exactly. Unless es etc. You can also use other editors ^.^
-like when installation is aborted, it says status 7(or 0 etc)
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
Many thanks!! KK installed -- that was the "fascinating" thing -- no status errors on previous failed attempt at installation -- nothing
but now it's installed -- with GApps added, and now to "worry" about the rest of it all
unsurprisingly -- if tee does what I think it does -- but I can't find a TUT on that anywhere
-- so currently, I can't connect to my local carrier, so it's currently not a :"phone" as such
even more frustratingly, computer found phone when it was first plugged in, but now seems to have lost it!! time to reboot system
-- and, it's been a while since I used CM but I can't find extsdcard!!
Cm file manager?
Settings-general settings-access mode- root
Sent from my GT-I8160 using Tapatalk
Permissions
teddytsen said:
Cm file manager?
Settings-general settings-access mode- root
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
sorry, not used to that one -- for that matter, I tend to stay away from things affecting the system I don't know
so I'm lost in permissions in different apps -- can't find "paste" in CM file, and can't find RW permissions in ES!!
But you're being exceptionally patient! thanks, heaps
Lot easier than I thought -- and MANY thanks again
KiwiCool60a said:
sorry, not used to that one -- for that matter, I tend to stay away from things affecting the system I don't know
so I'm lost in permissions in different apps -- can't find "paste" in CM file, and can't find RW permissions in ES!!
But you're being exceptionally patient! thanks, heaps
Click to expand...
Click to collapse
Actually, it's a lot easier than I thought -- working phone, with KK installed -- without need to unlock carrier!!
Many thanks for the guidance, patience ....
and, of course, to the ROM developers
Repeated problems with Maclaw KK ROM
KiwiCool60a said:
Actually, it's a lot easier than I thought -- working phone, with KK installed -- without need to unlock carrier!!
Many thanks for the guidance, patience ....
and, of course, to the ROM developers
Click to expand...
Click to collapse
Many thanks for past help with intall procedure -- but have had repeated problems of late -- last installed ROM on March 9th -- could install several versions prior to that date, and use them successfully, but since then have been unable since I repeatedly get "Error searching for networks", and hence cannot connect to carrier, and hence unable to use phone as phone, though other functions seem to work OK, -- any ideas??
hi!
i installed the regulat 1.6 update to my FP1 and everything was just fine.
then I tried to install the "unified 1.6 update" which worked but the problems begun:
things I noticed:
1. backup ist not really a backup for the apps but just a way to reinstall the apps I had installed without any settings. not a fun way to find that out when reopening your apps.
2. the update to the 1.6 unifyed also messed with my SD card and deleted files and put new ones there. not something I was expecting. luckily I had a backup of the SD card.
the thing I am looking for a solution:
after merging the partitions I cannot acces the phone storage on my PC (mac osx 10.9.4). not directly as a drive. the android fil transfer tool works, but it does not have all abilities finder/explorere provides. how do I get acces to the phone storage again?
As all my settings are gone anyway I am open to reinstall the phone from scratch.
fivel_ said:
the thing I am looking for a solution:
after merging the partitions I cannot acces the phone storage on my PC (mac osx 10.9.4). not directly as a drive. the android fil transfer tool works, but it does not have all abilities finder/explorere provides. how do I get acces to the phone storage again?
Click to expand...
Click to collapse
Because of the partition layout it no longer is possible to expose the internal storage as mass storage device. Adb will work but the preferred way of transferring files is using the MTP protocol.
I am not a mac user but I think you need to install some additional software.
https://www.android.com/filetransfer/
_keesj said:
Because of the partition layout it no longer is possible to expose the internal storage as mass storage device. Adb will work but the preferred way of transferring files is using the MTP protocol.
Click to expand...
Click to collapse
thanks a lot, that is what I feared.
hi, i'm also have an upgrade problem: mine is that i can't upgrade at all.
i've repartitioned earlier with the app mentioned in the wiki (wiki/Fairphone_Fairphone/Guides#How_to_partition_your_Fairphone).
i've also done the steps _keesj descripes in thread "unified storage setup on re-partitioned FP1" ("Steps for "fiixing" your upgrade").
i'm having Cherry 1.6, and two 7 GB partitions.
does anyone has a solution?
see other (missplaced) post
This post might be of help:
http://forum.xda-developers.com/fairphone/general/unified-storage-setup-partitioned-fp1-t2834642
Donat.Callens said:
This post might be of help:
http://forum.xda-developers.com/fairphone/general/unified-storage-setup-partitioned-fp1-t2834642
Click to expand...
Click to collapse
thanks, i've read it again and tried _keesj's solution again, unfortunately it didn't solve my situation.
i'm a layman in this area, so probably i shoudn't haved 'played' with partitions at all (but with the app it was easy).
my previous post wasn't quite complete... i have had an unified partition before...
because of an app that didn't work, i used the repartition app again to see if that could solve the problem.
it did, but later i wondered if a wrong install in the unified sistuation was the problem... so i thought 'let's try the unified partition again'...
i thought i could simply re-use the Fairphone Updater...
so maybe i'm now having a unified partition divided in 2?
and lost the ability to ever upgrade to newer versions of the Fairphone OS?
i hope someone can help me...
jjjanssen said:
i could simply re-use the Fairphone Updater...
Click to expand...
Click to collapse
Make sure you allow it to reinstall the default recovery.
Donat.Callens said:
Make sure you allow it to reinstall the default recovery.
Click to expand...
Click to collapse
how do I allow it? i didn't get the question you've got ("ROM may flash stock recovery on boot. Fix?").
i downloaded Cherry 1.6 again and chose Install, gave it SU (forever) access, it automatically restarted to the Android with the text “Installing system update…” (no progress bar), and after a few minutes it restarted and nothing is changed. After starting the Fairphone Updater again, it immediately gave the Install option again. Same after selecting the Storage Upgrader.
I also tried restoring from the recovery (default, never replaced), from sd and adb (1.6 does install, 1.3 doesn't, and 1.6 partition upgrader doesn't either, gets aborted)…
Hi,
jjjanssen said:
how do I allow it? i didn't get the question you've got ("ROM may flash stock recovery on boot. Fix?").
i downloaded Cherry 1.6 again and chose Install, gave it SU (forever) access, it automatically restarted to the Android with the text “Installing system update…” (no progress bar), and after a few minutes it restarted and nothing is changed. After starting the Fairphone Updater again, it immediately gave the Install option again. Same after selecting the Storage Upgrader.
I also tried restoring from the recovery (default, never replaced), from sd and adb (1.6 does install, 1.3 doesn't, and 1.6 partition upgrader doesn't either, gets aborted)…
Click to expand...
Click to collapse
Non unified images have a different signature. The moment you use the partition upgrader it will change the accepted signature and will no longer allow older images. If all is as I expected your running image is still the parition upgrader image and it contains the tools to perform the last step of the re-partitioning (e.g. calling the script and performing a recovery with format).
If you want to know what is going wrong with the zip install check the /cache/recovery direcotry. it will contain logs of the failing install.
As for a solutions I think you either need to run the script or flash your device using a 1.6 FUSE image.
_keesj said:
If you want to know what is going wrong with the zip install check the /cache/recovery direcotry. it will contain logs of the failing install.
As for a solutions I think you either need to run the script or flash your device using a 1.6 FUSE image.
Click to expand...
Click to collapse
I couldn't find any (log) files in /cache/recovery, but...
flashing the EBR1 from the FUSE binaries (FP1U) to my FP1 solved it! :victory:
thanks to _keesj, Rick (from Fairphone) and Christian (Fairphone forum)!
here is Rick's tutorial (with a few notes of my own):
You can only fix this by flashing your phone:
For GURU's only! (flashing with ADB). The alternative is to use the windows flasher tool.
1) Download the original image binaries from Fairphone's site (as a new user I, jjjanssen, can't post links yet).
(Download FP1U's zip: Fairphone_Cherry_1.6_FUSE_Image_2014-07-31.zip)
2) unzip the file
(I chose to unzip to location D:/FP1U.
after that i moved all content from the directory which contained EBR1, to D:/FP1U.)
3) enable usb debugging (on your phone: Settings, Developer options, turn USB debugging on)
4) push EBR1 on the phone: (Open (if you're using Windows) the Command Prompt)
adb push FP1U/EBR1 /mnt/sdcard/
(For instructions on how to use ADB search this site)
5) become root:
adb shell
(after that I also became super user (command su), but maybe that's not necessary; Rick didn't mention it. )
6) override the partition inforation:
dd if=/mnt/sdcard/EBR1 of=/dev/ebr1
7) reboot into recovery:
reboot recovery
8) choose to wipe data and cache
(after that, choose reboot)
Click to expand...
Click to collapse