Develop Bugs

[Q] Help With Restore

Hi All,
Just tried to install the Latest Leedroid ROM (GB) but then the desire hung on the HTC white screen.
I used Clockwork to install the ROM, but before doing so backed up via clockwork.
Now i want to restore that backup, but can't find a way of doing it.
I have been able to get to the recovery screen using 'Flash ROM', however from here when i try installing clockwork via the the zip file it does not work.
I used the option resotre from Nand but no Nandroid folder exists.
Having interrogated the SD Card there is a folder called clockworkrecovery and it does contain a backup folder with files that have a .img extension.
Can someone please help me get back to a working ROM, or explain a way i can use the backup i took to recover my phone.
Thanks in advance.
I have been looking for a simple enough guide to follow (2hrs +) but i have found nothing.

the_last_don said:
Hi All,
Just tried to install the Latest Leedroid ROM (GB) but then the desire hung on the HTC white screen.
I used Clockwork to install the ROM, but before doing so backed up via clockwork.
Now i want to restore that backup, but can't find a way of doing it.
I have been able to get to the recovery screen using 'Flash ROM', however from here when i try installing clockwork via the the zip file it does not work.
I used the option resotre from Nand but no Nandroid folder exists.
Having interrogated the SD Card there is a folder called clockworkrecovery and it does contain a backup folder with files that have a .img extension.
Can someone please help me get back to a working ROM, or explain a way i can use the backup i took to recover my phone.
Thanks in advance.
I have been looking for a simple enough guide to follow (2hrs +) but i have found nothing.
Click to expand...
Click to collapse
Can you boot to recovery? ie; turn phone off. Hold volume button (-) and press power button? Should boot to recovery. Then you can navigate to select the recovery file.

Yes i can get to recovery, it give me a red triangle with an exclamation mark, at that point i use Flash ROM - recovery-windows.bat to get into recovery, it at that point i am stuck, because none of the options give me the ability to restore from the backup i took via clockwork

First go to Normal recovery (Red Triangle) by maintaining Vol Down + Power
and then press Vol Up + Power
This will bring you to another recovery menu where you can : Reboot , Flash from sd , Wipe Data/factory ,Wipe Cache

THANKS!!!!
Can't believe i spent that long for such a simple task!

the_last_don said:
THANKS!!!!
Can't believe i spent that long for such a simple task!
Click to expand...
Click to collapse
Not such a simple task, if you don't know about it.
On a more personal note, I've been reading a lot of issues with LeeDroid ROMs lately. Maybe it is the spring weather. And it concerns updating.
Just a notice...
Be sure to hit Thanks! If it helped.

[Q] Repair platform.xml?

Hi folks,
I tried to modify the platform.xml file to enable some write permissions. As far as I can tell, the app I used to modify the file didn't write it back correctly, and now my device is what might be called "semi-bricked."
Almost everything force closes, WiFi and write permissions seem to be broken, and I can't seem to get my Galaxy Nexus to communicate with my PC via USB.
I tried booting into CWM and mounting some /system, but I'm not sure how to access it since fastboot/adb don't seem to recognize the device.
I've also booted into some sort of recovery (fastboot?) that looks like the attached image. But I can't get it to do anything except boot up into the normal OS when I click the power button.
Any suggestions on how I can get access back to my device so I can repair/replace the platform.xml file and restore functionality to my phone?
Thank you very much!

Deozaan said:
Hi folks,
I tried to modify the platform.xml file to enable some write permissions. As far as I can tell, the app I used to modify the file didn't write it back correctly, and now my device is what might be called "semi-bricked."
Almost everything force closes, WiFi and write permissions seem to be broken, and I can't seem to get my Galaxy Nexus to communicate with my PC via USB.
I tried booting into CWM and mounting some /system, but I'm not sure how to access it since fastboot/adb don't seem to recognize the device.
I've also booted into some sort of recovery (fastboot?) that looks like the attached image. But I can't get it to do anything except boot up into the normal OS when I click the power button.
Click to expand...
Click to collapse
No it is not bootloader. to access to the bootloader turn on your device long pressing power, volume up and volume down buttons together (don't use odin).
To access to cwm recovery from bootloader just press volume down button until you see "recovery" option, then press power button and it will boot in recovery.
which rom are you using?
solution: download the zip file of your rom and extract the file you modified, make a zip (if you can't make a flashable zip i'll post an attachment for you) and flash it in recovery

enryea123 said:
No it is not bootloader. to access to the bootloader turn on your device long pressing power, volume up and volume down buttons together (don't use odin).
To access to cwm recovery from bootloader just press volume down button until you see "recovery" option, then press power button and it will boot in recovery.
which rom are you using?
solution: download the zip file of your rom and extract the file you modified, make a zip (if you can't make a flashable zip i'll post an attachment for you) and flash it in recovery
Click to expand...
Click to collapse
Thanks for the reply.
I actually did manage to get my PC to recognize the device via USB/adb and I copied the file back to the way it should have been. But that didn't fix anything, so I ended up doing a wipe/factory reset. Everything works now but things still seem a bit. . . off. For instance, it takes a while after my phone boots up before the WiFi will actually connect. It used to be connected almost immediately. And it takes a while for the alarm icon to load/show up in the notification area at the top. And I can't find the option in the settings anymore to use USB debugging. There are lots of little things like that, where it works, but it just doesn't quite work like it used to. . .
And to answer your question, I'm using the stock ROM that came with the Galaxy Nexus (from Google Play Store).

Deozaan said:
Thanks for the reply.
I actually did manage to get my PC to recognize the device via USB/adb and I copied the file back to the way it should have been. But that didn't fix anything, so I ended up doing a wipe/factory reset. Everything works now but things still seem a bit. . . off. For instance, it takes a while after my phone boots up before the WiFi will actually connect. It used to be connected almost immediately. And it takes a while for the alarm icon to load/show up in the notification area at the top. And I can't find the option in the settings anymore to use USB debugging. There are lots of little things like that, where it works, but it just doesn't quite work like it used to. . .
And to answer your question, I'm using the stock ROM that came with the Galaxy Nexus (from Google Play Store).
Click to expand...
Click to collapse
first: to make the "developer settings" appear go settings/About phone and tap on build number 7 times (google has hidden it in 4.2).
said that, you can:
1) fix permissions in cwm recovery (under advanced menu)
2) download a zip of your rom and flash it in recovery
3) if your bootloader is unlocked (you see a padlock when you boot your phone) you can flash a factory image to return completely stock.
4) if your bootloader is locked you can follow the 3) method but you will lose all your sdcard data.

enryea123 said:
first: to make the "developer settings" appear go settings/About phone and tap on build number 7 times (google has hidden it in 4.2).
said that, you can:
1) fix permissions in cwm recovery (under advanced menu)
2) download a zip of your rom and flash it in recovery
3) if your bootloader is unlocked (you see a padlock when you boot your phone) you can flash a factory image to return completely stock.
4) if your bootloader is locked you can follow the 3) method but you will lose all your sdcard data.
Click to expand...
Click to collapse
Thanks again for the response.
I got developer settings to appear. Hooray! Fix Permissions is one of the first things I did to try to repair the platform.xml file when things were broken. I ran it again (but from ROM Manager rather than from CWM Recovery) and it didn't seem to have any effect on the weird sluggishness when first booting up.
My bootloader is unlocked. Will I have to root again if I flash one of those factory images? I'm currently backing up the contents of my "SD card" in case I have to completely wipe the entire thing.

Deozaan said:
Thanks again for the response.
I got developer settings to appear. Hooray! Fix Permissions is one of the first things I did to try to repair the platform.xml file when things were broken. I ran it again (but from ROM Manager rather than from CWM Recovery) and it didn't seem to have any effect on the weird sluggishness when first booting up.
My bootloader is unlocked. Will I have to root again if I flash one of those factory images? I'm currently backing up the contents of my "SD card" in case I have to completely wipe the entire thing.
Click to expand...
Click to collapse
well, you can firstly try to flash a zip of your rom (search on xda or google), it should fix.
the fastboot flash method is the google method so you won't need root (you just have to go into fastboot and connect your phone to your computer, doesn't matter if you have root, or a different rom/kernel/recovery).
If you don't know you to flash from fastboot try first to flash the rom zip.
having a backup of the sdcard is always a good idea :good:, i have 2 backups of mysdcard on 2 different hard drives of my computer and the pictures i take with the camera are automatically uploaded on my dropbox .

enryea123 said:
well, you can firstly try to flash a zip of your rom (search on xda or google), it should fix.
the fastboot flash method is the google method so you won't need root (you just have to go into fastboot and connect your phone to your computer, doesn't matter if you have root, or a different rom/kernel/recovery).
If you don't know you to flash from fastboot try first to flash the rom zip.
Click to expand...
Click to collapse
Weird things are happening. I was making a backup of the "SD Card" and partway through, things stopped copying over. And pretty much everything got erased from it. No big deal, since I'd already copied the important stuff first.
But CWM Recovery won't flash the zip file. It keeps telling me the update failed. I verified the hash on the zip I downloaded and it is the same as what is listed on Google's site. But it just won't flash in CWM.

Deozaan said:
Weird things are happening. I was making a backup of the "SD Card" and partway through, things stopped copying over. And pretty much everything got erased from it. No big deal, since I'd already copied the important stuff first.
But CWM Recovery won't flash the zip file. It keeps telling me the update failed. I verified the hash on the zip I downloaded and it is the same as what is listed on Google's site. But it just won't flash in CWM.
Click to expand...
Click to collapse
wait, are you in cwm recovery o just in stock recovery (they are different)? have you previously installed a cwm recovery using fastboot? which zip are you trying to flash?
edit: ok you know what is rom manager so i think that you are in cwm.
edit2: try this zip http://goo.im/devs/bigxie/maguro/bigxie_maguro_OTA_JOP40D-signed.zip

enryea123 said:
wait, are you in cwm recovery o just in stock recovery (they are different)? have you previously installed a cwm recovery using fastboot? which zip are you trying to flash?
edit: ok you know what is rom manager so i think that you are in cwm.
edit2: try this zip
Click to expand...
Click to collapse
I was in CWM Recovery. I was using the zip file that I extracted from the link you gave me for Google's stock ROMs (I can't post external links yet):
(Factory Images "takju" for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet) --> Android 4.2.1 (JOP40D))
Strangely enough, after "failing" to flash the zip, I had to log into my Google account again because I had selected the option to Wipe Data and Cache, and most things seem to be working very well again. One odd thing I'm still noticing, though, is that some things don't seem to be syncing properly. For example, if I archive some of my email in the Gmail app, then log into Gmail on my PC, the mail is still unread in my inbox. My phone downloads the new mail just fine. But the changes I make on my phone (reading, archiving, deleting, etc.) don't seem to be syncing to anywhere else.
I'm downloading the zip you suggested. I'll give that a try. Thanks!

enryea123 said:
edit2: try this zip http://goo.im/devs/bigxie/maguro/bigxie_maguro_OTA_JOP40D-signed.zip
Click to expand...
Click to collapse
Try this one
Deozaan said:
I was in CWM Recovery. I was using the zip file that I extracted from here the link you gave me (I can't post external links yet):
(Factory Images "takju" for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet) --> Android 4.2.1 (JOP40D))
Strangely enough, after "failing" to flash the zip, I had to log into my Google account again because I had selected the option to Wipe Data and Cache, and most things seem to be working very well again. One odd thing I'm still noticing, though, is that some things don't seem to be syncing properly. For example, if I archive some of my email in the Gmail app, then log into Gmail on my PC, the mail is still unread in my inbox. My phone downloads the new mail just fine. But the changes I make on my phone (reading, archiving, deleting, etc.) don't seem to be syncing to anywhere else.
I'm downloading the zip you suggested. I'll give that a try. Thanks!
Click to expand...
Click to collapse
That is not a flashable zip! It is a factory image, it must be flashed via fastboot using a computer.

enryea123 said:
That is not a flashable zip! It is a factory image, it must be flashed via fastboot using a computer.
Click to expand...
Click to collapse
Just to be sure I explained myself clearly, I downloaded that Google provided factory image (a .tgz file) and inside it I found a zip file named "image-takju-jop40d.zip" which is what I tried to flash.
That said, I've just recently finished downloading the one you just suggested to me and I will give that one a try soon. Thank you again for your help. I really appreciate it.

I got it working again. The ROM you gave me failed signature verification in CWM Recovery, but I told it to install anyway and it worked. Thank you.
The problem I was having with Gmail not syncing was that I used Titanium Backup to restore my data, but because all the data from my "SD card" got erased, Titanium Backup itself lots its settings, so my Device ID was different. I guess Gmail relies on the device ID for syncing.
Thank you so much for your help! I learned a lot from the experience.

Glad i helped you. well this is one of the reasons why i don't restore data with titanium (especially system data).
and by the way:
Deozaan said:
Just to be sure I explained myself clearly, I downloaded that Google provided factory image (a .tgz file) and inside it I found a zip file named "image-takju-jop40d.zip" which is what I tried to flash.
That said, I've just recently finished downloading the one you just suggested to me and I will give that one a try soon. Thank you again for your help. I really appreciate it.
Click to expand...
Click to collapse
To fully reset and install a clean rom using fastboot you have to extract the bootloader-blabla.img and radio-blabla.img files from the tar.gz archive and then extract the 4 .img files inside the zip (that is inside the tar.gz) and flash this 6 .img files connetting your phone in bootloader mode to your computer and using fastboot in terminal (in fact this procedure reinstall the recovery too).

[Recovery][CWM] CWM 6.0.2.8 for Mach Speed Trio Pro 9.7

So, there is actually a WORKING CWM 6.0.28 recovery, with an installer that runs from a root shell.
All features work for me. I'm able to mount my internal SD as USB, do a CWM backup, navigate through menus, etc
I didn't create it, but since it is verified working on this tablet, and I had such a difficult time finding a working CWM for this device, I thought I'd post the link and which file to grab.
Thread: CWM 6.0.2.8 for Allwinner A10 & A13 Tablets - v2a
http://forum.xda-developers.com/showthread.php?t=2189640
Download the file:
cwm6028-a10-10part-v2.zip
This is a 10 partition AllWinner A10 device, so that's the zip file we want.
NOTE: This "guide" assumes you know how to copy files via ADB, use basic Linux commands, and
Manual Install Method (Known Working):
Extract the files, copy the two .sh files and the recovery.img file to the device using ADB (probably /data/local would be a good spot). Make the .sh files executable (chmod 777 *.sh), and run install-recovery.sh
It will install the recovery for you. Takes about 10 seconds or so.
The reboot-recovery.sh script reboots to recovery. Go figure This device has an interesting way of rebooting. Check out the guts of the script for the command if you're interested. BTW, don't use any 3rd party utilities that reboot the system. It will probably end up in a factory reset of your device. I did that by accident... more than once.
Automatic Install Method (Might Work, Worth A Shot):
I'm not sure if the stock recovery will flash the ZIP file, but I would give it a shot before trying the above method. If it does let you install it, then it's a MUCH quicker way
Other Information:
Boot to recovery manually by powering the device off (holding the power button for 10 seconds). Then holding Volume Down & Power until it powers on, then release the Power button while still pressing the Volume Down button until the recovery boots.
Sorry for the scattered post. I'm just happy to have a working CWM and wanted to share it.

I can confirm that the stock recovery is able to install cwm6028-a10-10part-v2.zip from external memory. Quick & painless.:good:

AyDee said:
I can confirm that the stock recovery is able to install cwm6028-a10-10part-v2.zip from external memory. Quick & painless.:good:
Click to expand...
Click to collapse
unfortunately, this didn't work for me. I'm not sure what hardware version i have but the lot number is 120915-10205815

HELP
I have the mach speed trio and i accidentally screwed it up the only thing that happens when i turn it on is the android in the box icon appears, i rooted using the root toolbox and the run me .bat file on a windows pc. normal mode activated and it completed successfully now the only thing appearing on the screen when i power on is the logo, this happened after factory resetting it in cwm after the zip file in the guide to installing choco ics on it and cwm, the only thing that was on it then was the bootloader. is there any way for me to fix this, it is very urgent please pm me is you have specifics, it is the mach speed trio model stealth pro with ics 4.0.4 running on it before this happened and also when i tried to put the stock rom on it, it wouldn't let me.

[STOCK][C6502&C6503&C6506] Update to 10.1.1.A.1.253 [Root&XZDualRecovery][LB/UB]

[STOCK][C6502&C6503&C6506] Update to 10.1.1.A.1.253 [Root&XZDualRecovery][LB/UB]
After my release for the Z and the success stories on it, i had some requests to do the same for the ZL. Finally I'm ready for it's release! :victory:
Thanks go to @butatx for his invaluable testing contribution and taking one for the team.
Requirements:
Flashtool
A recovery (can be both CWM and TWRP)
NOTE: As some people have problems flashing the update, please update your existing recovery to the latest (BETA) recovery with XZDualRecovery
Current FW version: 10.1.A.1.350 or 10.1.A.1.434: maybe others too, try and let me know!
From the users in the original thread I noticed people using CWM running into trouble because their cache partition is gone. See the 'Known Issues' in the OP of the XZDualRecovery link above for more info and links to a fix. Fix that first before you attempt this update using CWM!
Special features:
Superuser integrated in system, FULL root, no reboots when remounting /system RW!
XZDualRecovery 2.3 RELEASE (CWM 6.0.3.2 & TWRP 2.5.0.0) pre-installed;
Tailored FTF to minimize the chance of accidental system wiping!
No need to clear caches!
@shem2409 created a nice youtube video guide to assist you in your work, be sure to check his post for it! Thanks m8!
TIP: This ROM is compatible with the shutdown/reboot MOD by @niaboc79
TIP: This ROM and the integrated recovery are compatible with the reboot wrapper by @DooMLoRD, get it here!
C6502: How to update to 10.1.1.A.1.253:
For C6502: Download C6502.flashable.253.zip (Bittorrent: 752MB) and Xperia_Z_10.1.1.A.1.253_C6502-stripped.ftf (14MB), save it somewhere you remember;
Put 'C6502.flashable.253.zip' on (the external) SDcard1;
Put 'Xperia_Z_10.1.1.A.1.253_C6502-stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash everything in 'Xperia_Z_10.1.1.A.1.253_C6502-stripped.ftf' to your phone and boot the phone straight to recovery after that;
NOTE: If you have an unlocked bootloader, you CAN flash the kernel, but you do not need to, to keep your custom kernel. DooMKernel v7 has support for this ROM version.
Flash 'C6602.flashable.253.zip' in recovery (Works in both CWM and TWRP!)
Reboot to system without clearing (dalvik-/)cache.
C6503: How to update to 10.1.1.A.1.253:
For C6503: Download C6503.flashable.253.zip (Bittorrent: 715MB) and Xperia_Z_10.1.1.A.1.253_C6503-stripped.ftf (14MB), save it somewhere you remember;
Put 'C6503.flashable.253.zip' on (the external) SDcard1;
Put 'Xperia_Z_10.1.1.A.1.253_C6503-stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash everything in 'Xperia_Z_10.1.1.A.1.253_C6503-stripped.ftf' to your phone and boot the phone straight to recovery after that;
NOTE: If you have an unlocked bootloader, you CAN flash the kernel, but you do not need to, to keep your custom kernel. DooMKernel v7 has support for this ROM version.
Flash 'C6503.flashable.253.zip' in recovery (Works in both CWM and TWRP!)
Reboot to system without clearing (dalvik-/)cache.
C6506: How to update to 10.1.1.A.1.253:
For C6506: Download C6506.flashable.253.zip (Bittorrent: 730MB) and Xperia_Z_10.1.1.A.1.253_C6506-stripped.ftf (14MB), save it somewhere you remember;
Put 'C6506.flashable.253.zip' on (the external) SDcard1;
Put 'Xperia_Z_10.1.1.A.1.253_C6506-stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash everything in 'Xperia_Z_10.1.1.A.1.253_C6506-stripped.ftf' to your phone and boot the phone straight to recovery after that;
NOTE: If you have an unlocked bootloader, you CAN flash the kernel, but you do not need to, to keep your custom kernel. DooMKernel v7 has support for this ROM version.
Flash 'C6506.flashable.253.zip' in recovery (Works in both CWM and TWRP!)
Reboot to system without clearing (dalvik-/)cache.
The first boot will be considerably slower and after a long wait at the boot animation you will see Android optimizing the apps on your phone, It will update your NFC with a firmware and after that, all is done!
IMPORTANT NOTE:
For some devices the first or second reboot after the successful upgrade may be used by the ROM/Kernel to upgrade some low-level firmware. This will be done from the screen which normally shows you the kernel logo. This upgrade flash will also happen when on a custom kernel by @DooMLoRD. DO NOT INTERRUPT THAT WHATEVER YOU DO OR HOWEVER LONG IT TAKES! Just let it do it's thing and wait, your phone will continue boot as soon as it's done.
I have done this myself, using my own method on the Z and I have not found any problem yet. :fingers-crossed:
Enjoy! :victory:
Known XZDualRecovery Issues:
All known issues in TWRP and CWM on locked boot loaders apply, see their respective threads for more information.
Be especially careful with the cache partition when using CWM. Hopefully version 2.0 solved the cache issues but in case of problems with /cache use the FTF in my files to restore the cache partition if yours ever stops mounting due to the CWM issues, read this and this for more info on that. This FTF was created for .434 but as the cache did not change between .350, .434 and .253 you can still use it to fix the cache partition.
CWM Usage warning: Root can be lost (almost worst case), a bootloop can be experienced (worst case) or a reboot upon remounting /system to be able to write to it (most cases, relatively harmless) when using CWM and before a reboot out of recovery the 'ROM may flash recovery, fix it?' question is answered with 'yes'. This can be recovered from by opening a terminal app and typing the following commands:
Code:
su
/system/bin/stop ric
mount -o remount,rw /system
chmod 755 /system/etc/install-recovery.sh
Alternatively you can boot in to TWRP and go to the Advanced menu -> File manager and look for /system/etc/install-recovery.sh to set permissions 755 on it.
If even that is too much to handle for you, see the patch at the bottom of the OP to flash the fix.
TWRP Usage warning: It seems TWRP 2.5.0.0 has issues with the internal storage, which seem related to the changes made to support encrypted storage volumes... This means the internal storage sometimes shows up almost empty (just folders) and no files. Try to use CWM when that happens.
Busybox Updater/Installer: If you have XZDualRecovery installed, un-install any Busybox updating app/tool as most if not all of them will install a version of busybox which does not support the lzma compression applets XZDualRecovery depends on. The version installed together with XZDualRecovery is very stable and I have yet to hear anyone complain about it's stability.
How to report errors:
Please, before shouting out "It doesn't work!!1!" or "I lost root!" or even "My phone reboots when remounting /system RW!!" try the following:
Restore a .434 /system ONLY using any means you are familiar with so you can try again.
Root it using any means you are familiar with.
Install XZDualRecovery and then try to update again using TWRP. This time you can skip the FTF as it has already done it's job.
If it still fails something from there on: LOGS!!.
NOTE: The important ones can be found in /cache/recovery and in /tmp/XZDualRecovery, pack them up and send them to me.
Thank you
Flashable ROM Mutator:
Download AROMA ROM Mutator 0.13
This (former patch package) uses AROMA to create a user friendly menu to choose between updates to be installed.
If you want to switch from SuperUser (default in this ROM) to SuperSU you can use this to make the change.
If you have the reboot problem when trying to remount /system writable, you can reinstall the superuser app of your preference, it's installation includes the patch.
If you are missing /system/bin/chargemon.stock and you want to be able to charge your phone while it's turned off.
Flash using one of the recoveries!
Version 0.13 and upwards is using AROMA 2.70B1 or better, the below warning can be ignored for now. Let me know how it performs!
AROMA Warning: AROMA currently works best in TWRP but even there it has some issues on the Z/ZL. It sometimes does not start up correctly or it has a 'sticky button' issue. It makes it a little less easy to use but this will be fixed in time. It is a combination problem caused by the new hardware and incompatibility with it and the fact the recoveries both have been updated considerably to work on the latest phones, causing issues with some functionality of AROMA.
If it hangs when trying to start, reboot your phone and try again.
If it has the sticky buttons, press the button again to activate.
You can avoid the sticky buttons by pressing them for about half a second (that means not too short and not too long). It will work, it's just showing a bug associated with the latest recoveries.
The Samsung S4, HTC One and One X and the Nexus 4 & 7 show the same issues. For them AROMA sometimes crashes, this is an issue i have not yet observed on the Z/ZL.

Reserved, just in case

There seems some error with the instructions why you created a stripped file as a zip as it is nota ftf file which cannot be used with flashtool.
I just waiting for the other file currently downloading to finish so I assume you mean used the .253 zip file inside moved to the sdcard of smartphone and the ftf firmware inside of it to the flashtool/firmware folder to flash so I seem confusion on your part.

That will be big help for us
Thank you

Just downloaded both files the stripped file in a zip file not an ftf so what do I do this please as it will need to be convert into a ftf file somehow?
Can you create a stripped ftf file please.

Darkfunnyguy said:
Just downloaded both files the stripped file in a zip file not an ftf so what do I do this please as it will need to be convert into a ftf file somehow?
Can you create a stripped ftf file please.
Click to expand...
Click to collapse
paullu said:
That will be big help for us
Thank you
Click to expand...
Click to collapse
There was a small issue with the download site, which now has been fixed. You can rename the ZIP file you downloaded and change the extension from .zip to .ftf
From there on you can flash it using flashtool.
Sorry guys

Hi NUT, tested your rom, it work flawlessly + rooted , thanks for your work :good:

confused
Is it right that the file called in instruction as"C6506.flashable.253.zip " in real is C6603??:
C6506: How to update to 10.1.1.A.1.253:
For C6506: Download C6506.flashable.253.zip (730MB) and Xperia_Z_10.1.1.A.1.253_C6506-stripped.ftf (14MB), save it somewhere you remember;
Put 'C6506.flashable.253.zip' on (the external) SDcard1;
Put 'Xperia_Z_10.1.1.A.1.253_C6506-stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash everything in 'Xperia_Z_10.1.1.A.1.253_C6506-stripped.ftf' to your phone and boot the phone straight to recovery after that;
NOTE: If you have an unlocked bootloader, you CAN flash the kernel, but you do not need to, to keep your custom kernel. DooMKernel v7 has support for this ROM version.
Flash 'C6603.flashable.253.zip' in recovery (Works in both CWM and TWRP!)
Reboot to system without clearing (dalvik-/)cache.
the total confusion with what file has to be renamed and used by Flash tool and which one with CWM. In order to avoid misinterpretation may be NUT closes this thread and open a new one with all corrections.

Successfully updated to 10.1.1.A.1.253 with everything intact including roots and recovery.

Hi, NUT. It works fine. Thanks for your work!

rfg13 said:
Is it right that the file called in instruction as"C6506.flashable.253.zip " in real is C6603??:
C6506: How to update to 10.1.1.A.1.253:
For C6506: Download C6506.flashable.253.zip (730MB) and Xperia_Z_10.1.1.A.1.253_C6506-stripped.ftf (14MB), save it somewhere you remember;
Put 'C6506.flashable.253.zip' on (the external) SDcard1;
Put 'Xperia_Z_10.1.1.A.1.253_C6506-stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash everything in 'Xperia_Z_10.1.1.A.1.253_C6506-stripped.ftf' to your phone and boot the phone straight to recovery after that;
NOTE: If you have an unlocked bootloader, you CAN flash the kernel, but you do not need to, to keep your custom kernel. DooMKernel v7 has support for this ROM version.
Flash 'C6603.flashable.253.zip' in recovery (Works in both CWM and TWRP!)
Reboot to system without clearing (dalvik-/)cache.
the total confusion with what file has to be renamed and used by Flash tool and which one with CWM. In order to avoid misinterpretation may be NUT closes this thread and open a new one with all corrections.
Click to expand...
Click to collapse
Whups, i might have linked to the wrong file then... Check my download link in my signature in case you get the wrong file, my bad
Sent from my C6603 using xda app-developers app
-- EDIT --
Fixed links in the OP and a typo. Sorry for the confusion!

Thanks Mr. NUT...i'm downloading it now

Kylez said:
Thanks Mr. NUT...i'm downloading it now
Click to expand...
Click to collapse
did i lose everything in phone if i flash this zip?

daniLaLaLaLaLa said:
did i lose everything in phone if i flash this zip?
Click to expand...
Click to collapse
No. Data, programs and settings will be saved.

Bird40 said:
No. Data, programs and settings will be saved.
Click to expand...
Click to collapse
Good, i tried it tomorrow after i wake up from sleep .:thumbup:
Sent from my C6502 using xda app-developers app

Hi,
I seemed to have run in a little trouble with this. Heres what happened - I was running a stock but rooted build 434 before attempting this. My BL cannot be unlocked so also stock Kernel. I wasnt running any recoveries. So I followed the steps in the post to install recovery "XZDualRecovery" which ran the bat file successfully and then rebooted my phone into the CWM recovery for the first time. I then tried to go back to recovery with no luck... tried several times wether with Vol+ (CWM) or Vol- (TWRP). I then followed a different post to install a single recovery which installed properly and I was able to boot my phone in CWM all the time... So Success!!
So i then copied the ZIP to my EXT Card and flashed my phone with the Stripped FTF file, I then rebooted straight to CWM and installed the ZIP from SD Card. Perfect, it rebooted, Android was upgrading x out of 293 apps... That was successfull and I was rooted and inside the ROM. The Gmail app kept crashing so I decided to reboot. Here is the problem, The Sony logo appears followed by the wrench in the white triangle. I wasnt even able to turn off my phone by holding Vol+ and Power. I could only reset with little yellow button next to the SD Card.
I tried to flash my phone with the stock FTF file using flashtool but no luck (Nearly crapped my pants)
Anyway after several attempts, I finally managed to get into flashmode and I am now with build 253 and no root.
Ill flash back to 434 later but would really like to know what I did wrong?
Geez, I think I just wrote a book but I wanted to be clear with everything I did..
Thanks

Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash everything in 'Xperia_Z_10.1.1.A.1.253_C6506-stripped.ftf' to your phone and boot the phone straight to recovery after that;
Click to expand...
Click to collapse
You are steller [NUT], great work here.
as quested above is the cwm backup for safety in case there are issues?
and flash everything, as i have not tried yet do we need to un check wipe, data, cache, appslog?
or does the ftf have the wipe options already unchecked?
Thanks again for the great work.

HackitZ said:
and flash everything, as i have not tried yet do we need to un check wipe, data, cache, appslog?
or does the ftf have the wipe options already unchecked?
Click to expand...
Click to collapse
Yes, when I flash the ftf-file, there were no wipe options.

Crash338 said:
Hi,
I seemed to have run in a little trouble with this. Heres what happened - I was running a stock but rooted build 434 before attempting this. My BL cannot be unlocked so also stock Kernel. I wasnt running any recoveries. So I followed the steps in the post to install recovery "XZDualRecovery" which ran the bat file successfully and then rebooted my phone into the CWM recovery for the first time. I then tried to go back to recovery with no luck... tried several times wether with Vol+ (CWM) or Vol- (TWRP). I then followed a different post to install a single recovery which installed properly and I was able to boot my phone in CWM all the time... So Success!!
So i then copied the ZIP to my EXT Card and flashed my phone with the Stripped FTF file, I then rebooted straight to CWM and installed the ZIP from SD Card. Perfect, it rebooted, Android was upgrading x out of 293 apps... That was successfull and I was rooted and inside the ROM. The Gmail app kept crashing so I decided to reboot. Here is the problem, The Sony logo appears followed by the wrench in the white triangle. I wasnt even able to turn off my phone by holding Vol+ and Power. I could only reset with little yellow button next to the SD Card.
I tried to flash my phone with the stock FTF file using flashtool but no luck (Nearly crapped my pants)
Anyway after several attempts, I finally managed to get into flashmode and I am now with build 253 and no root.
Ill flash back to 434 later but would really like to know what I did wrong?
Geez, I think I just wrote a book but I wanted to be clear with everything I did..
Thanks
Click to expand...
Click to collapse
The triangle showing is your phone flashing a new update to a low level device, NEVER interrupt that process, I believe it's not even possible to skip it.
XZDualRecovery not working is related to a 2.1 incompatible method of reading the keypress. You could have noticed it was already superseded by a BETA release fixing that. It's even included in this Rom release
Your Gmail app crashing can be fixed by clearing its cache from the apps menu. If that doesn't help you can remove it using a root app like titanium backup. Then install it again from play store.
HackitZ said:
You are steller [NUT], great work here.
as quested above is the cwm backup for safety in case there are issues?
Click to expand...
Click to collapse
Exactly, it is just a precaution, a case of better safe then sorry. Your other question got answered by @Bird40.
Sent from my C6603 using xda app-developers app

[NUT] said:
The triangle showing is your phone flashing a new update to a low level device, NEVER interrupt that process, I believe it's not even possible to skip it.
XZDualRecovery not working is related to a 2.1 incompatible method of reading the keypress. You could have noticed it was already superseded by a BETA release fixing that. It's even included in this Rom release
Your Gmail app crashing can be fixed by clearing its cache from the apps menu. If that doesn't help you can remove it using a root app like titanium backup. Then install it again from play store.
I actually started everything over by flashing a clean 434 FTF. Mine was a mess, I had played a lot with the system files. So this second try, the phone reboots properly, no triangle, no app crash but the Recovery still doesn't work and I also tried with the latest 2.2 BETA (same result). I also re-installed Root Explorer and when going from R/W to R/O, it reboots the phone, so I switched from SuperUser to SuperSU but same result.
Any suggestions?
Click to expand...
Click to collapse

Stuck on Asus load screen

After a update for better compatibility for 3rd party app, my Zenfone wont get past the ASUS screen at all.

Im also stuck at the asus load screen. I played around with the permissions of the sd card, after rebooting its stuck. Guys how to unbrick?

bratski said:
Im also stuck at the asus load screen. I played around with the permissions of the sd card, after rebooting its stuck. Guys how to unbrick?
Click to expand...
Click to collapse
you may want to flash your phone back. so this consist of
1) read up how to access to Temp CWM
2) download and transfer the full rom to your SD card
3) do a wipe all partition and go to advanced setting, wipe cache
4) install zip and choose from external SD, point to that .zip file for the full rom and apply.
5) installation may take 10min or so do not switch it off. after installation you are good as new.
I believe this should solve your problem, normal if things get bricked is due to config file error could be [syntax, corrupted, missing, setting].
Flashing should solve mostly of it unless the file that you previously accessed require root and cwm does not give permission to the file. that is a permanent bricking.
As always, newbie should not try tweaking permission required files, you end up having bricking the device as there might be no solution to recover it due to access rights. ALWAYS have a back up file so you can at least copy the file back and chmod it.

jerk48 said:
After a update for better compatibility for 3rd party app, my Zenfone wont get past the ASUS screen at all.
Click to expand...
Click to collapse
by asus screen, did you mean the ASUS Setup Wizard?

sooty84 said:
you may want to flash your phone back. so this consist of
1) read up how to access to Temp CWM
2) download and transfer the full rom to your SD card
3) do a wipe all partition and go to advanced setting, wipe cache
4) install zip and choose from external SD, point to that .zip file for the full rom and apply.
5) installation may take 10min or so do not switch it off. after installation you are good as new.
I believe this should solve your problem, normal if things get bricked is due to config file error could be [syntax, corrupted, missing, setting].
Flashing should solve mostly of it unless the file that you previously accessed require root and cwm does not give permission to the file. that is a permanent bricking.
As always, newbie should not try tweaking permission required files, you end up having bricking the device as there might be no solution to recover it due to access rights. ALWAYS have a back up file so you can at least copy the file back and chmod it.
Click to expand...
Click to collapse
my problem right now is my pc wont detect my phone. Ive already installed the drivers.

Same thing happened to me when I tried flashing the OTA update with my phone being rooted. You have get into recovery mode on the phone and then use ADB to put the original image back to the device to get it back to stock so it will reboot. It worked for me

sooty84 said:
you may want to flash your phone back. so this consist of
1) read up how to access to Temp CWM
2) download and transfer the full rom to your SD card
3) do a wipe all partition and go to advanced setting, wipe cache
4) install zip and choose from external SD, point to that .zip file for the full rom and apply.
5) installation may take 10min or so do not switch it off. after installation you are good as new.
I believe this should solve your problem, normal if things get bricked is due to config file error could be [syntax, corrupted, missing, setting].
Flashing should solve mostly of it unless the file that you previously accessed require root and cwm does not give permission to the file. that is a permanent bricking.
As always, newbie should not try tweaking permission required files, you end up having bricking the device as there might be no solution to recover it due to access rights. ALWAYS have a back up file so you can at least copy the file back and chmod it.
Click to expand...
Click to collapse
downshift00 said:
Same thing happened to me when I tried flashing the OTA update with my phone being rooted. You have get into recovery mode on the phone and then use ADB to put the original image back to the device to get it back to stock so it will reboot. It worked for me
Click to expand...
Click to collapse
where do i get the stock image?

bratski said:
where do i get the stock image?
Click to expand...
Click to collapse
here is the stock firmware.
https://www.asus.com/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/
its fine if your phone does not talk to your PC now. copy the firmware to your SD card via other means. [card reader etc]
then try my method of flashing it back to original state, you stated that adb dont work, have you tried the temp CWM method yet?
the main goal is to wipe dalvik cache under advanced menu in CWM, and cache partition and all hard reset.
then you flash back your original file.
hope it works for you.

sooty84 said:
here is the stock firmware.
https://www.asus.com/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/
its fine if your phone does not talk to your PC now. copy the firmware to your SD card via other means. [card reader etc]
then try my method of flashing it back to original state, you stated that adb dont work, have you tried the temp CWM method yet?
the main goal is to wipe dalvik cache under advanced menu in CWM, and cache partition and all hard reset.
then you flash back your original file.
hope it works for you.
Click to expand...
Click to collapse
ive read about the temp cmw method and i cant figure out how to go about it. it says on the instruction that you need to turn on phone before running the cai_dat_CWM. how am i going to do this as my phone will only boot to the asus logo? thanks

just figured it out. I need to boot in fastboot so the phone will get recognized. However, the latest build available on the asus website is still 2.17.40.12. I already have the 2.18.40.12 version. The 2.17 firmware can't overwrite the newer build in temp CWM recovery. Anybody knows where i can download the full rom? Z00A-WW-2.18.40.12?

bratski said:
just figured it out. I need to boot in fastboot so the phone will get recognized. However, the latest build available on the asus website is still 2.17.40.12. I already have the 2.18.40.12 version. The 2.17 firmware can't overwrite the newer build in temp CWM recovery. Anybody knows where i can download the full rom? Z00A-WW-2.18.40.12?
Click to expand...
Click to collapse
I GOT THE SAME PROBLEM.
dunno what to do anymore.
sigh...
help me please

Ninjakura said:
I GOT THE SAME PROBLEM.
dunno what to do anymore.
sigh...
help me please
Click to expand...
Click to collapse
here is the link for stock but pre-rooted img for latest 2.18.40.12 firmware,,make sure to download Z00A firmware if you have ZE551ML device.. and if I was not mistaken, you may choose to FULL UNROOT in SuperSU apps to go back to stock rom..

cangcan said:
here is the link for stock but pre-rooted img for latest 2.18.40.12 firmware,,make sure to download Z00A firmware if you have ZE551ML device.. and if I was not mistaken, you may choose to FULL UNROOT in SuperSU apps to go back to stock rom..
Click to expand...
Click to collapse
thanks. problem solved after i followed instructions from this thread, http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835

bratski said:
my problem right now is my pc wont detect my phone. Ive already installed the drivers.
Click to expand...
Click to collapse
me too, any idea on how to fix it?

sooty84 said:
you may want to flash your phone back. so this consist of
1) read up how to access to Temp CWM
2) download and transfer the full rom to your SD card
3) do a wipe all partition and go to advanced setting, wipe cache
4) install zip and choose from external SD, point to that .zip file for the full rom and apply.
5) installation may take 10min or so do not switch it off. after installation you are good as new.
I believe this should solve your problem, normal if things get bricked is due to config file error could be [syntax, corrupted, missing, setting].
Flashing should solve mostly of it unless the file that you previously accessed require root and cwm does not give permission to the file. that is a permanent bricking.
As always, newbie should not try tweaking permission required files, you end up having bricking the device as there might be no solution to recover it due to access rights. ALWAYS have a back up file so you can at least copy the file back and chmod it.
Click to expand...
Click to collapse
I have same prolem as OP's got.
I've got stuck on Asus Loading screen after install OTA update on rooted device.
I'm gonna try your method.
Thanks

downshift00 said:
Same thing happened to me when I tried flashing the OTA update with my phone being rooted. You have get into recovery mode on the phone and then use ADB to put the original image back to the device to get it back to stock so it will reboot. It worked for me
Click to expand...
Click to collapse
how did u do that? can u give me step by step instruction please?
ty

Did anyone able to fix this problem (stuck at Asus logo and not able to get to recovery mode or connect to the computer)? Thanks!

SAN_MARINO said:
Did anyone able to fix this problem (stuck at Asus logo and not able to get to recovery mode or connect to the computer)? Thanks!
Click to expand...
Click to collapse
Press Power+Volume Up key, After vibration leave Power Button then choose Recovery Mode using Volume keys, if sleeping Android screen appear at Recovery with Error message, Press Volume Up and Power and leave immediately Power Key, it will show you the Recovery Menu, then Reset your device, it will solve your problem.
If I am helped you, Press Thanks button.

k576 said:
Press Power+Volume Up key, After vibration leave Power Button then choose Recovery Mode using Volume keys, if sleeping Android screen appear at Recovery with Error message, Press Volume Up and Power and leave immediately Power Key, it will show you the Recovery Menu, then Reset your device, it will solve your problem.
If I am helped you, Press Thanks button.
Click to expand...
Click to collapse
Thanks!
I already tried it like 20 or more times. The ASUS logo still shown for like 10 seconds and died and came back again (ASUS logo). When I tried to connect it with my laptop, the computer won't recognize the device.

SAN_MARINO said:
Thanks!
I already tried it like 20 or more times. The ASUS logo still shown for like 10 seconds and died and came back again (ASUS logo). When I tried to connect it with my laptop, the computer won't recognize the device.
Click to expand...
Click to collapse
I will try to tell you step by step:
1. Press Power Button + Volume Button
You enter into Recovery Fastboot Option, then Choose Recovery menu using Volume Key (3 Option mostly shown)
then press Power Button (From Recovery Mode), it restart.
2. Then after Restart it shows you (Mostly) Sleeping Android Screen with Error text, then Press First Volume Up Button, and Press Power Button (Power button for a second or two then leave it, IF YOU PRESS MORE TIME, IT WILL RESTART THE PHONE).
3. You can now see the Recovery Menu with Normally appear in other phones also - Reset, Restart, Etc Option.
Hope you will now able to reset your phone...
----------------------------------------------------------
PRESS THANKS BUTTON IF I AM HELPED YOU
----------------------------------------------------------