Develop Bugs

Stuck on ANDROID logo boot anim after HBOOT flash

hey y'all
Was following this thread: on Alternative HBOOTs
tried the following:
I followed instructions on Apharev homepage and flashed the 'bravo_alphaspl-sense.img'
Downloaded the necessary PB99IMG zipfile and saved it to SD card
now phone goes silver ANDROID logo that reflects passing light after splash image - looks like this (only in silver):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
but won't load my homepage afterwards
HELP

What Rom are you using? perhaps there is not enough space on /system for the Rom now with your new hboot. Try flashing the stock hboot.
Sent from my HTC Desire using XDA App

Not to state the obvious but did you
1. Reinstall rom after changing hboot - necessary i believe
2. Install correct rom for hboot
If this fails you could re-flash to your previous hboot and reinstall whatever flavour of rom you were using
hope this helps
Jamadant

Yeah I'm pretty sure all that's happened is you installed a HBOOT that has different partitions for System, Data and Cache. Therefore you just need to reinstall the ROM. Simply boot into recovery (Turn the phone off, hold volume down and press power, use the volume keys to navigate to RECOVERY and press the power button) From there you need to go into "mounts and storage", wipe everything APART FROM YOUR SDCARD and then install a new ROM.
Hope that helps

Thanks all but the problem is that I longer have the Reflex S ROM on my phone (I removed it due to space).
I tried pushing it to phone via adb but not enough space
I tried to pull the nandroid backup from phone via adb (to free up space for pushing ROM to phone) but no luck
This is the command I used:
adb pull /clockworkmod/backup/2011-07-19.10.12.47/ C:\
but this gives me an error that /clockworkmod/backup/2011-07-19.10.12.47/ does not exist
???
Anyone know of an easier way
I have attached the adb logcat as well

herb1 said:
Thanks all but the problem is that I longer have the Reflex S ROM on my phone (I removed it due to space).
I tried pushing it to phone via adb but not enough space
I tried to pull the nandroid backup from phone via adb (to free up space for pushing ROM to phone) but no luck
This is the command I used:
adb pull /clockworkmod/backup/2011-07-19.10.12.47/ C:\
but this gives me an error that /clockworkmod/backup/2011-07-19.10.12.47/ does not exist
???
Anyone know of an easier way
I have attached the adb logcat as well
Click to expand...
Click to collapse
You can't restore nandroid after you've changed hboot. Hboot partition sizes have changed and chances are that you do not have enough space on them to restore the information on the original partitions.

paul.c said:
You can't restore nandroid after you've changed hboot. Hboot partition sizes have changed and chances are that you do not have enough space on them to restore the information on the original partitions.
Click to expand...
Click to collapse
I'm aware of that but I want to pull the nandroid backup to make space to push the ROM to phone via adb
what commands can I use

Why you want adb to copy clockworkmod backup.... just open your SD card from window explorer and .. copy paste on your C drive and delete from your SD card

managed to access SD card from Recovery by mounting as USB
cut & pasted the nandroid backup to my laptop,
copied the Reflex ROM over to SD & installed
but now stuck on splash screen

herb1 said:
managed to access SD card from Recovery by mounting as USB
cut & pasted the nandroid backup to my laptop,
copied the Reflex ROM over to SD & installed
but now stuck on splash screen
Click to expand...
Click to collapse
Configured sd card for reflex rom correctly? You need stock hboot or cm7 hboot to run reflex s (remember to downloaded corresponding version).

I've formatted my sd card, made it a gold card
trying to install Reflex S 2.1.2 ROM as per NeoPhyte's instructions (with Radio)
Do I flash the stock HBOOT after ROM install?
I'm quickly running outta ideas...me thinks I might have to go back to unrooted stock ROM
this will teach me not to fcuk around with my phone AGAIN

herb1 said:
I've formatted my sd card, made it a gold card
trying to install Reflex S 2.1.2 ROM as per NeoPhyte's instructions (with Radio)
Do I flash the stock HBOOT after ROM install?
I'm quickly running outta ideas...me thinks I might have to go back to unrooted stock ROM
this will teach me not to fcuk around with my phone AGAIN
Click to expand...
Click to collapse
Do I flash the stock HBOOT after ROM install?
Not if you have changed your hboot from stock!?!!!! Have you changed your partition tables yet? If you have flash cm 7

herb1 said:
I've formatted my sd card, made it a gold card
trying to install Reflex S 2.1.2 ROM as per NeoPhyte's instructions (with Radio)
Do I flash the stock HBOOT after ROM install?
I'm quickly running outta ideas...me thinks I might have to go back to unrooted stock ROM
this will teach me not to fcuk around with my phone AGAIN
Click to expand...
Click to collapse
One has to flash hboots always BEFORE installing a rom.

Can you not use fastboot its much more reliable!?

Nice guide how to use adb/fastboot:
http://androidforums.com/desire-all...stboot-windows-published-17th-may-2011-a.html

thanks for all the advice
I've been unable to use my phone for the past few days and I'm considering the following options (getting REAL desperate here):
* should I flash the stock ROM? (I've been on the Net, looking for similar situations and 90% of peeps recommend flash the stock ROM)
* flash the HBOOT for Reflex S, then install Reflex S ROM (as per recommendations above)?
The thing is (with option 2); I can't get into adb shell as phone does not detect in Recovery or at splash screen (where I'm at at the moment)...
I've even tried Android Flasher but it does work either!!!
MatDroiD...I know (with your skill & experience) that you can help...please, I need my phone back!!!

You don't have to go into adb shell to flash a new hboot, you can do it in fastboot mode, but you have to have s-off!!! (I assume you have, as you stated before that you followed the instruction on alpharev). To use fastboot you have to have the fastboot.exe (you'll find a download linke if you do a quick search). And then you can flash the correct hboot by following the instruction on alpharev
"1) Nandroid backup in recovery.
2) Verify the MD5SUM of the file you downloaded against the one in the table.
3) Flash HBOOT with your phone in fastboot mode (Back+POWER) -> 'fastboot flash hboot bravo_alphaspl.img' (change into the correct filename for the HBOOT you downloaded)
4) 'fastboot reboot-bootloader'
5) 'fastboot erase cache'
6) Boot recovery, wipe everything and restore."
Hope this helps...

I tried the following:
followed EddyOS guide to install RUU as PB99IMG.zip (as per FAQ)
got this message (which is different from EddyOS post)
SD Checking
Loading...[PB99DIAG.zip]
No image!
Loading...[PB99DIAG.nbh]
No image or wrong image!
Loading [PB99IMG.zip]
everything else goes fine, then get this displayed (after pressing YES to update device)
Update in progress...
Do not power off your device
can not roll back hboot version
[1] Bootloader - Bypassed
[2] Radio V2 - OK
[3] Radio Cust - OK
[4] Boot - OK
[5] Recovery - OK
[6] System - Failed-PU
[7] Userdata - OK
[8] Splash1 - OK
Partition update fail!
Update fail!
I chose not to reboot the device & booted into Recovery
Got a black screen with htc phone overlapped with red triangle & exclamation mark
Press volume UP & POWER and ended up in Android system recovery <3e> with limited recovery options (reboot system/apply sdcard:update.zip/wipe data/wipe cache)
Message displayed at bottom
'E:Can' open /cache/recovery/command'
Chose to reboot phone and observed that white HTC splash loaded with silver ANDROID flashing boot animation afterwards
Phone eventually loaded to what looks like Oxygen lockscreen
Unlocked screen and phone went into setup (keyboard, wifi, sync, etc)
At last SKIP, app forced closed
Screen went black, except for signal meter, battery, time (in top right corner)
Removed battery and volume DOWN & POWER to boot into Recovery
same result

herb1 said:
thanks for all the advice
I've been unable to use my phone for the past few days and I'm considering the following options (getting REAL desperate here):
* should I flash the stock ROM? (I've been on the Net, looking for similar situations and 90% of peeps recommend flash the stock ROM)
* flash the HBOOT for Reflex S, then install Reflex S ROM (as per recommendations above)?
The thing is (with option 2); I can't get into adb shell as phone does not detect in Recovery or at splash screen (where I'm at at the moment)...
I've even tried Android Flasher but it does work either!!!
MatDroiD...I know (with your skill & experience) that you can help...please, I need my phone back!!!
Click to expand...
Click to collapse
The thing is with option 2... is that you don't listen lol USE FASTBOOT
Like i've previously said it's much more reliable, you get mixed results from P99IMG method

BigMrB said:
The thing is with option 2... is that you don't listen lol USE FASTBOOT
Like i've previously said it's much more reliable, you get mixed results from P99IMG method
Click to expand...
Click to collapse
I'm going to try something:
Installing this ROM = RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00.32U_5.09.00.20_release_140022_signed
hope it works

[Q] clockworkmod recovery

hello,
last night i tried to flash an update from cm7 nightly and after trying it, decided to return to the previous build i was using. i did a nan restore and encountered an error "md5 mismatch". i asked for 3xeno help as to what could have possibly caused the error and suggested some possible causes and solution to my problem which I am still trying to figure out till now. but in the meantime i have just decided to reflash the nightly i was using and reinstalled all the apps i was using.
i read quite a few articles and threads here and if i understood it right there are some cwm version that encounter nandroid restore problems. i am currently using cwm 3.0.0.6 and i was wondering if there is a cwm version that i can use which is more stable and will not create any problems if i would make nan restores in the future.
thanks.

Switch to 5.0.2.0. No issues with Nandroid Backups / Restores. I have done tons of restores with this version.

3xeno said:
Switch to 5.0.2.0. No issues with Nandroid Backups / Restores. I have done tons of restores with this version.
Click to expand...
Click to collapse
will give it a try and see how it goes.
edit: i found the link from your guide you posted before sir. the zip for cwm 5.0.2.0 with the PC49IMG zip. sorry for the stupid question, should i flash both zip?

[email protected] said:
will give it a try and see how it goes.
edit: i found the link from your guide you posted before sir. the zip for cwm 5.0.2.0 with the PC49IMG zip. sorry for the stupid question, should i flash both zip?
Click to expand...
Click to collapse
The two zips are different ways of installing it.
Download PC49IMG.zip only and place on SD card root, go into hboot and press volume up when it asks you to update
Sent from my HTC Wildfire using XDA App

jacktyler1807 said:
The two zips are different ways of installing it.
Download PC49IMG.zip only and place on SD card root, go into hboot and press volume up when it asks you to update
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
Manage to flash it as per 3xeno guide and suggestions. Im now on cwm 5.0.2.0. Thought i had it figured out at first but it was only temporary recovery. Flashed PC4IMG zip and now everything is good.
Thanks.

3xeno said:
Switch to 5.0.2.0. No issues with Nandroid Backups / Restores. I have done tons of restores with this version.
Click to expand...
Click to collapse
I get lots of MD5SUM errors with this version of CWM, 4 out of 5 nands fail on me. I think my card may be to blame but i really dont trust my backups now. I'm sketchy about any mods I do now because i cant be sure if my backups will restore.

If you are ready to use fastboot, you can use it to push all the IMG files directly to your Wildfire without bothering about MD5 checksums. (I had loads of MD5 errors on versions 4.x, but not a single one yet, as I said before, on 5.0.2.0)

3xeno said:
If you are ready to use fastboot, you can use it to push all the IMG files directly to your Wildfire without bothering about MD5 checksums. (I had loads of MD5 errors on versions 4.x, but not a single one yet, as I said before, on 5.0.2.0)
Click to expand...
Click to collapse
Will probably try to learn that method over the weekend. I tried a nandroid backup and restore with cwm 5.0.2.0 and it went well so far. Thank you for the suggestion sir.
If my previous backups including my stock rom gets really messed up, I guess Im just gonna stick with cm7. I'm loving it anyway.

Quoting myself from a previous post:
2) Use Fastboot
- Download this attachment and extract it to any folder (eg: C:\fastboot)
http://forum.xda-developers.com/atta...1&d=1308537074
- Download CWM IMG Image for Wildfire (Buzz) from here:
http://download.clockworkmod.com/rec...0.2.0-buzz.img
- Place that IMG file along with the 4 files from the attachment in the same folder you created
- Now, turn off your Wildfire, connect to PC, and turn on in HBoot
- Navigate to Fastboot and Select it
- Open a Command Prompt Window (Start > Run > cmd)
- Type the following one by one and press Enter (It is assumed you created the folder in C Drive and have named it fastboot)
- cd\
- cd fastboot
- fastboot flash recovery recovery-clockwork-5.0.2.0-buzz.img
- This should produce 2 lines of code - SENDING RECOVERY and WRITING RECOVERY. If both states OK at the end, you should have CWM installed successfully after this.
Click to expand...
Click to collapse
The above Quote was for installing a Recovery Image like CWM. Fastboot commands use the following syntax:
fastboot flash <partition name> <name of IMG file to be flashed>
So, the other command names will change according to the files from your previous Nandroid Backup. Examples:
fastboot flash cache cache.img
fastboot flash system system.img
fastboot flash data data.img
... and so on

will give this a try sir. thanks

[Q] - Error mounting SDcard in CWM [SOLVED]

Hello I'm new to the nexus line and recently upgraded form a SGS. my phone is Rooted, unlocked boot loader and running the most recent version of CWM 5.5.0.4. I'm running the GSM version of the Nexus.
My question is how do I flash the my first rom? When I boot into recovery and click install zip from SDcard i get "E: Can't mount /sdcard/" I am also unable to mound the data partition within. windows drivers are installed for both fastboot and adb so I can flash that way, i'm just wondering what the exact steps are and if that error mounting data is normal.
I also downloaded the most recent franco.Kernel as I want to run that, I know how to flash that with fastboot but wasnt' sure if that is how you would flash a rom with the nexus, on the SGS i used to use odin.
Thanks and sorry for the noobness.

How did you "unlock fastboot" and "root" and "install CWM"? Did you use one of the "Tool Kits"?
Do you have ROM Manager installed on your device?

yiannisthegreek said:
How did you "unlock fastboot" and "root" and "install CWM"? Did you use one of the "Tool Kits"?
Do you have ROM Manager installed on your device?
Click to expand...
Click to collapse
Sorry, Yes I have ROM Manager installed and its' paid for.
I unlocked my boot loader using fastboot oem unlock, I rooted by using an app because I couldn't mount the data partition in recovery so had to use some app some guy made that downloaded the su.zip from clockwork and flashed on it's own.
I installed CWM using fastboot.
fastboot flash recovery recovery.img
it's the dam data partition that i'm really having trouble with, i'm just wondering if this is normal, all the posts on the web say to flash a zip by choosing "choose zip from scard" but mine wont mount???
I should also mention that my entire device is encrypted.....that is whats causing it isn't it?

I'm not 100% sure but it could be that you flashed the wrong recovery.
According to this thread
http://forum.xda-developers.com/showthread.php?t=1357642
the recovery for the GSM version is 5.5.0.2 and not 0.4.
I would flash the correct recovery then try again.

You can not mount sdcard from CWM recovery (don't ask me why, I don't know.. maybe because it is not supported yet ..)
anyway, do like me, use CWM 5.5.0.2 and then try again toflash zip files .. It works for me

P4p3r1n0 said:
You can not mount sdcard from CWM recovery (don't ask me why, I don't know.. maybe because it is not supported yet ..)
anyway, do like me, use CWM 5.5.0.2 and then try again toflash zip files .. It works for me
Click to expand...
Click to collapse
He posted it on his Google+ account here:
https://plus.google.com/112476065271141473049/posts
I'm starting to think it's my encrypted phone, technically when I boot I have to decrypt the device before it boots into android.
I'm going to factory reset and see if that helps. I have a feeling that is what my problem is

OK so that was the problem, the data partition was encrypted (now that I think of this it makes sense that it wouldn't mount) anyways, for whatever reason a factory reset from android wouldn't work. I removed the "recovery-from-boot.p" file from my system folder originally so the CWM image would remain in tact.
anyways, I flashed the original recovery over the CWM recovery, preformed a factory wipe (which is the only way to decrypt your phone) then flashed CWM back on and now I can mount the data partition
what a pain in the ass, guess I wont be encrypting the phone any time soon, I wish there was an option to decrypt the drive and then get into recovery....wouldn't have this issue.

spectre85 said:
OK so that was the problem, the data partition was encrypted (now that I think of this it makes sense that it wouldn't mount) anyways, for whatever reason a factory reset from android wouldn't work. I removed the "recovery-from-boot.p" file from my system folder originally so the CWM image would remain in tact.
anyways, I flashed the original recovery over the CWM recovery, preformed a factory wipe (which is the only way to decrypt your phone) then flashed CWM back on and now I can mount the data partition
what a pain in the ass, guess I wont be encrypting the phone any time soon, I wish there was an option to decrypt the drive and then get into recovery....wouldn't have this issue.
Click to expand...
Click to collapse
It is possible now on 4.1.2 to decrypt the device. You must provide a password for dectypting (chane from unlock pin to passw).

[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

[Q] Help -- CWM not working

Can't install any ROMs on G2.
Had CWM 5.0.27, I think. Couldn't install any of several ROMs. Installed CWM 6.0.4.5. Same outcome.
Aroma installer always stops at "Symlinking..." after extracting files.
Says "set_perm: some changes failed" and Status 7.
What am I doing wrong?

O's said:
Can't install any ROMs on G2.
Had CWM 5.0.27, I think. Couldn't install any of several ROMs. Installed CWM 6.0.4.5. Same outcome.
Aroma installer always stops at "Symlinking..." after extracting files.
Says "set_perm: some changes failed" and Status 7.
What am I doing wrong?
Click to expand...
Click to collapse
Well as far as I remember, the new roms were better to be installed with 4ext Recovery, because the CWM had some problems working with ext4 filesystem. Try the one I have on the web site below, that should fix it for you.

a.s.j said:
Well as far as I remember, the new roms were better to be installed with 4ext Recovery, because the CWM had some problems working with ext4 filesystem. Try the one I have on the web site below, that should fix it for you.
Click to expand...
Click to collapse
Thanks, but the zip didn't work. Put it in sdcard root and tried several times with CWM Touch 5.8.1.0 -- installation failed, every time.
I've since gotten CM10.1 and Mimicry to work with CWM, but I'm struggling with one ROM in particular no matter the recovery: coolIOS, a 4.0.4.
Tried to install it with CWM 5.0.2.7 and got the error described at top.
Tried with CWM 6.0.4.5.
Tried with CWM Touch 5.8.1.0.
Tried with TWRP 2.6.3.0.
Same error, every time. Redownloaded the ROM, but same. I'm really at a loss with that one. It worked fine on a previous G2.

O's said:
Thanks, but the zip didn't work. Put it in sdcard root and tried several times with CWM Touch 5.8.1.0 -
Click to expand...
Click to collapse
Just try to install 4EXT recovery !
http://4ext.net/

Kéno40 said:
Just try to install 4EXT recovery !
http://4ext.net/
Click to expand...
Click to collapse
I meant the only 4ext install zip I could find didn't work.
Downloaded the apk from the site and got "Cannot open file".
Yes, Unknown Sources is checked.
Thanks, anyway.
EDIT: Got 4ext working, but still no help. Had to extract the .img from the install zip, install Mimicry ROM, and use the Terminal Emulator to flash the .img. That got it working, but it only boots in safe mode. Says it can't read the cache partition, and also says this:
"If you changed hboot you should choose to format all partitions (except sdcard)".
Formatted all partitions, rebooted recovery -- still safe mode. Still says it can't read cache.
Starting to think some of the physical memory is corrupt.
But if that's the case, why do other ROMs work? Or does someone else see another plan/fix/anything here? Thanks.

O's said:
I meant the only 4ext install zip I could find didn't work.
Downloaded the apk from the site and got "Cannot open file".
Yes, Unknown Sources is checked.
Thanks, anyway.
EDIT: Got 4ext working, but still no help. Had to extract the .img from the install zip, install Mimicry ROM, and use the Terminal Emulator to flash the .img. That got it working, but it only boots in safe mode. Says it can't read the cache partition, and also says this:
"If you changed hboot you should choose to format all partitions (except sdcard)".
Formatted all partitions, rebooted recovery -- still safe mode. Still says it can't read cache.
Starting to think some of the physical memory is corrupt.
But if that's the case, why do other ROMs work? Or does someone else see another plan/fix/anything here? Thanks.
Click to expand...
Click to collapse
There is no install zip on my pages, just zipped image which should be pushed in via Fastboot. You are perhaps doing something terribly wrong my friend.
What you need to do can be achieved by several ways:
- Rename recovery.zip to PC10IMG.zip put it into your /sdcard root and start your phone to recovery (hold Vol-Down and Power to start recovery system)
- use adb to push the image to the recovery partition
- or the easiest could be to check this one: http://www.4ext.net/install.pdf

a.s.j said:
There is no install zip on my pages, just zipped image which should be pushed in via Fastboot. You are perhaps doing something terribly wrong my friend.
What you need to do can be achieved by several ways:
- Rename recovery.zip to PC10IMG.zip put it into your /sdcard root and start your phone to recovery (hold Vol-Down and Power to start recovery system)
- use adb to push the image to the recovery partition
- or the easiest could be to check this one: http://www.4ext.net/install.pdf
Click to expand...
Click to collapse
Perhaps I was unclear. I downloaded your zip and renamed it PC10IMG.zip and put it in sdcard root and started to recovery, but that did not work. I thought it would work, since the phone showed the "vertical progress bar" as if it was about to change recovery, but I didn't get the prompt to "Update recovery?" that I usually see there. So nothing happened.
I also tried to download the 4ext apk directly from the site onto my phone, but after downloading the apk, phone said "Cannot open file."
Instead, I got 4ext working by downloading the zip in the 4ext forum zip. It contains an .img that I flashed in Terminal Emulator, which got 4ext working.
Once I booted to 4ext, it said it could only load in safe mode because it couldn't read the cache. It advised to wipe the cache, so I wiped everything several times, but it still only loads in safe mode.
I'll try your zip method again, and I thank you for the assistance. I just don't get why five different recoveries work on some ROMs but not one that worked fine on a past G2.

O's said:
Perhaps I was unclear. I downloaded your zip and renamed it PC10IMG.zip and put it in sdcard root and started to recovery, but that did not work. I thought it would work, since the phone showed the "vertical progress bar" as if it was about to change recovery, but I didn't get the prompt to "Update recovery?" that I usually see there. So nothing happened.
I also tried to download the 4ext apk directly from the site onto my phone, but after downloading the apk, phone said "Cannot open file."
Instead, I got 4ext working by downloading the zip in the 4ext forum zip. It contains an .img that I flashed in Terminal Emulator, which got 4ext working.
Once I booted to 4ext, it said it could only load in safe mode because it couldn't read the cache. It advised to wipe the cache, so I wiped everything several times, but it still only loads in safe mode.
I'll try your zip method again, and I thank you for the assistance. I just don't get why five different recoveries work on some ROMs but not one that worked fine on a past G2.
Click to expand...
Click to collapse
SOLVED: Helps if I read the instructions. Thread for that ROM clearly says to have Desire Z hboot; I had G2 hboot. In all the years of using a G2, I've never had to switch hboot and was unfamiliar with it. If anyone else has same issues as this post, might try installing the Virtuous Team's PC10IMG.zip and read up on it at the Hboot thread. Thanks to all who beared with my lack of knowledge.