yashsingh1/xdaforums huggingface dataset:
[Xperia Z Android Development] AltairFriend:
Yes, I do. I will try to clear app's cache and settings.

Edit: clear app's cache and settings does not solve the problem :(
[Xperia Z Android Development] nielneal:
here is the link i downloaded this one its indian firmware

https://docs.google.com/file/d/0B8wQNvu4nHhfaWN3ZkNDVDBlcjg/edit?pli=1

Cheers
[Xperia Z Android Development] techpal:
Thanks dear , will try and flash this one.
[Xperia Z Android Development] hypetaxx:
Sorry I do not have the logs, I ended up going back to .434 (wiping everything (thank god that most if not all my data is in the cloud)) - rooted it - updated to yours .253 and then again updated to this .307 everything is working now :)
[Xperia Z Android Development] [NUT]:
Hmmm thats weird, just plain weird :silly:

Maybe this will solve your problem:

Make a backup using CWM or TWRP.

Do a factory reset in either recoveries.

Boot your phone and do first setup, skipping the backup setting to sync your settings and all to your Google account.

Install Titanium Backup.

Start Titanium Backup, set it up to store your backups on your external SD card and do a first backup of your phone (it requires root, so it will ask permission, make sure you tic the remember box).

Close Titanium Backup and start it again: Does it ask for permission again?.

If it did not work OK then: :eek: and I'm fresh out of ideas on how to fix it... :crying:

If it worked OK: continue;

Restore your CWM/TWRP backup.

Install Titanium Backup again,

Start Titanium Backup, set it up to store your backups on your external SD card and RESTORE app & data for SuperUser.

Done!

The settings will be cleared for all of your other ROOT apps, but it should now remember your choices...

If this didn't work... contact the app developer (ChainsDD)... :(
[Xperia Z Android Development] nielneal:
either try the way given by nut

or update yours supersu via chainfires thread ....maybe it could fix it

install superuser bcz m 99%sure yours phone is having the rooting issue

its alwys advisable to everyone to have the fresh and clean install always because by that way only u wud have rom without any errors...otherwise u will end up with errors and complications....

Cheers;)
[Xperia Z Android Development] BeDesireS:
Can anybody who has updated please test, if the voice output is working fine?

It's working fine in demo mode in settings, but it doesn't work in Google or sygic navigation for me!?

Thanks in advance!

Gesendet von meinem Xperia Z via Tapatalk
[Xperia Z Android Development] lilien98:
I had this once before. Uninstalling superuser and reinstall it from market solve my problem...

Just a "Note" with Tapatalk.
[Xperia Z Android Development] fards:
I use ivona which works a treat on 307
[Xperia Z Android Development] BeDesireS:
Thx for the tip, I will give ivona a try.

Edit: great voice, but does also not work with navigation. Really strange!?

Gesendet von meinem Xperia Z via Tapatalk
[Xperia Z Android Development] mandarjoshiin:
Why this is an Odex one??

Hit Thanks If I helped u!! :)

Sent from my Sweetheart Xperia Z
[Xperia Z Android Development] fards:
I'm using it with navigation, both Google, locus pro and co pilot. Voice works with mytracks as well...have you disabled or deleted something?
[Xperia Z Android Development] BeDesireS:
No, I don`t think so.

I just updated to .307 and used sygic yesterday for the first time after update

and got no voice navigation. First I thought it was a sygic problem, but other apps also dont work.

The strange thing is, that in settings menu where you can listen to the demo of the selected voice they all work fine.

Maybe I try clearing cache, but I really dont know what to do.
[Xperia Z Android Development] [NUT]:
Well, thats simply because this ROM is stock Sony... :)
[Xperia Z Android Development] AltairFriend:
Thanks it is working :good:

Actually, I replaced superuser with superSU from "Flashable ROM Mutator" :o
[Xperia Z Android Development] juliospinoza:
C6602

Thanks for your work.

When I am trying to download the C6602 an error appears "network error unknow", I first I thought that was an error of Chrome, but the same happens with Mozilla and explorer, so I decided to use the download manager and is the same problem "can download because the server can confirm the last files" and bum! error again, This happens only with your files, because I already downloaded FTF and flashtools. Do you have a mirror or a different server?

thanks
[Xperia Z Android Development] YudiA1:
Great :)

Nice in here. No lost anything. root still work. tysm :good:
[Xperia Z Android Development] dave_id:
ok

I don't know what's going on...

I was on 253 rooted

I flashed with flashtool

then installed from TWRP

it rebooted then it says i'm still in 253 without root anymore??

please help if you can

thanks
[Xperia Z Android Development] [NUT]:
Ehrm... I'll double check the files, I've mixed up system partitions before, but you can check your downloaded file too, open using winrar, then open system.tgz and look in the build.prop what it says it is. ro.semc.version is the key I believe (from memory, not sure though).
[Xperia Z Android Development] dave_id:
what should I do then?

that's what I found:

ro.semc.version.cust=1270-6704

ro.semc.version.cust_revision=R4A

ro.semc.rem-roam-icon=1

ro.nfc.icon.enable=true

#############################################################################

ro.config.ringtone=xperia.ogg

ro.config.notification_sound=notification.ogg

ro.config.alarm_alert=alarm.ogg

ro.semc.content.number=PA9

################# Updating of the SW Version #################

ro.semc.version.fs_revision=10.1.1

---------- Post added at 11:14 PM ---------- Previous post was at 10:17 PM ----------

ok

I had to flash superuser.zip in recovery to regain root

then I did it all again

it worked...except I'm not rooted anymore

don't really know what happened...
[Xperia Z Android Development] [NUT]:
ro.semc.version.fs_revision=10.1.1

Thats the line i'm after, what does it end with?

When did you download the package? Almost the entire first week the C6602 package was online it contained .253 because i mixed up system partitions... maybe if you redownload it and install again?
[Xperia Z Android Development] dave_id:
here it is:

ro.semc.version.fs_revision=10.1.1.A.1.307

ro.build.id=10.1.1.A.1.307

ro.build.display.id=10.1.1.A.1.307

I downloaded the very latest version...
[Xperia Z Android Development] [NUT]:
Then please try to update one more time, then when you are still in .253 grab the logs from /cache/recovery and send them to me.
[Xperia Z Android Development] dave_id:
thanks!

as I said

I'm now (after a retry) in 307

except without root (happened the first time also)

so i had to flash superuser in recovery...

now it's fine
[Xperia Z Android Development] taivm:
Already on 307

Hi,

I upgrade from rooted 434 to 307 using PC Companion with locked bootloader. I had TWRP installed when on 434 but it seems it was removed during the upgrade to 307 so I reinstalled it using this http://www.mediafire.com/?oi5pe14l5cc89o0.

The install.bat file reported that the recovery was successfully installed but I cannot get into the recovery when pressing Volume Up or Down in the logo screen, phone just boot normally. I also notice that there is no LED during boot either.

So, since I can't get into the recovery, how can I root please? :(
[Xperia Z Android Development] [NUT]:
Can you send me the logs from /cache/recovery please? For me it works fine and I seriously do not know what is causing the difference...
[Xperia Z Android Development] taivm:
The cache folder is empty. I guess it is because I lost root when upgrading to 307.

Here is what happened:

1. I upgraded to 307 from a rooted, locked bootleader 434 using PC Companion and lost root, possibly the TWRP recovery too.

2. I flashed Xperia_Z_10.1.1.A.1.307_C6602_TW-stripped.ftf file using Flash tool.

3. After flashing, I found out that I was unable to open recovery so I tried to reinstall it using TWRP 2.4.3.0 Recovery installer (the one that use Windows to install).

4. The recovery installer reported something like this http://xdaforums.com/attachment.php?attachmentid=2049096&stc=1&d=1371455983 but I still can't open the recovery.

There, now I have no idea how to root without the recovery. :(
[Xperia Z Android Development] [NUT]:
Recovery installation needs a working root too.

Try going back to .434, root it and install XZDualRecovery. Then try to update.
[Xperia Z Android Development] taivm:
Ah, guess I have to do that after all. Many thanks, man. :good:
[Xperia Z Android Development] taivm:
Wait, can you make a FTF file so that it can be flashed via Flashtool instead of using the recovery?

I flashed the old 434 but now my phone keep rebooting when it's updating NFC firmware.
[Xperia Z Android Development] [NUT]:
I'm afraid that's impossible... Sorry :( you might want to update to .307 and use DooMLoRD's new root method, it might be the way out of your problematic situation...
[Xperia Z Android Development] taivm:
Yeah, I just reflashed 307 and rooted using DooMLoRD's method. Things are OK now. Thanks for the help, man. :)
[Xperia Z Android Development] [NUT]:
I doubt it will cause any problems tbh... but as I instruct in the step-by-step guide, create a solid backup first and give it a try. :)
[Xperia Z Android Development] NetSkill:
tryed twice

first straight from rooted .253 - this causes my device not boot it shows only triangle with progress bar...

and then downgraded to .434 i got updated but when mounting system as write it REBOOTS

tryed everithing you mentioned in the OP but no luck still the same.. any ideas ?
[Xperia Z Android Development] naujoks:
When I try to flash this in TWRP, it goes:

Updating partition details...

Running boot script...

Finished running boot script.

E:Mount: Unable to find partition for path '/st....

Error flashing zip 'storage/sdcard1/c6603...

Updating partition details

Failed.

And that's it. Anyone got any ideas?
[Xperia Z Android Development] Langdang02:
I face the same problem, seem that should come back 434 :(
[Xperia Z Android Development] [NUT]:
The triangle with progressbar is a low level flash operation, you should NEVER interrupt it and let it's do it's thing, it will continue boot after some time (took a little more then 2 minues with mine but i heard people talk about more then 10 for some).

-- EDIT --

I forgot a part of my answer to your problems: did you try the CWM Usage warning guide in a terminal app?

Can you get me the contents of /cache/recovery/ please? The most interesting bits are missing in this description.

No, it should not be needed... did you try to upgrade from .253?
[Xperia Z Android Development] Carceri:
I upgraded my ROM with the kernel from 307 and also got reboots when mounting system r/w. I checked briefly and it seems that the program responsible for these reboots is more persistent in this kernel. /system/bin/stop ric does not stop it and killing the process just causes it to respawn again. It seems that /init is responsible for starting ric now.

I solved this in my ROM by modifying the script that comes with the recovery for locked bootloaders. Since it runs early in the boot process, it can mount / rw, delete /sbin/ric before it is started and then mount / ro again. That solved the problem for me.
[Xperia Z Android Development] [NUT]:
Actually, init has always been responsible for starting ric ... it's 'fix' is a stop command initiated by the init as well in the install-recovery.sh which gets run by init. The same script is already in place in this ROM.

What script/program is your solution to this problem?
[Xperia Z Android Development] Carceri:
OK, I wasn't sure about that. I thought that it was started from /init.sony.rc earlier and only now by the binary /init, but I couldn't check since I didn't have time to flash an older kernel.

I also used the stop command in install-recovery.sh but as of the latest kernel that no longer works for me. A manual "stop ric" command via ADB didn't work either. Neither did killing the ric process - it just respawned.

I just added these three lines to /system/bin/chargemon just before it calls the original chargemon.stock.

${MOUNT} -o remount,rw /

${RM} -f /sbin/ric

${MOUNT} -o remount,ro /
[Xperia Z Android Development] [NUT]:
Can anyone confirm this as a solution to the reboot problem for .307? I'm not experiencing the same issues myself but if there are more people who can solve their problems with this method i can create an update / patch implementing this.
[Xperia Z Android Development] Carceri:
One advantage to this way of fixing the problem (besides that it is the only way that works for me with the latest kernel) is that people can't mess up by saying "Yes" when CWM asks if you want to fix flash stock recovery on boot :)
[Xperia Z Android Development] [NUT]:
That's true, but it also locks them in the recovery that I supply and breaks again when they reinstall a different recovery... I'll try to find an alternate solution to it though.
[Xperia Z Android Development] fards:
will give a try now, as Carceri found, killing ric doesn't help
[Xperia Z Android Development] [NUT]:
C6602 testers wanted!

Look at my files page... it is

currently 100% untested!

: if you want to try it, it's online now :)

Rooted and with XZDualRecovery.

Same instructions apply as with the .253 update package:

C6602: How to update to 10.1.1.A.1.307:

For C6602: Download C6602.flashable.307.zip (728MB) and Xperia_Z_10.1.1.A.1.307_C6602_TW-stripped.ftf (14MB), save it somewhere you remember;

Put 'C6602.flashable.307.zip' on (the external) SDcard1;

Put 'Xperia_Z_10.1.1.A.1.307_C6602_TW-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.307_C6602_TW-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.307.zip' in recovery (Works in both CWM and TWRP!)

Reboot to system

without

clearing (dalvik-/)cache.

Link in my signature.

C6602 Users, please let me know if it works OK, if it does, I'll add it to the OP :)
[Xperia Z Android Development] Minotavrs:
Respect !!!!:good::good:
[Xperia Z Android Development] Carceri:
Have you tried to kill it with: kill -9 "pid of ric" ?

I didn't try this, but if ric is respawning itself when responding to a TERM signal, this could work by not giving it the chance to respond to the TERM signal. If it works then the following in /system/etc/install-recovery.sh should work:

#!/system/bin/sh

pid=$(/system/xbin/ps -o pid,comm|/system/xbin/grep " ric$"|/system/xbin/cut -d" " -f1)
if [ ! -z "${pid}" ]; then
/system/xbin/kill -9 "${pid}"
fi

If it doesn't work then it means that something else is causing it to respawn.
[Xperia Z Android Development] naujoks:
Sorry, bit nooby here. Looking up the /cache folder using ES File Explorer shows it being empty. Am I doing the right thing?
[Xperia Z Android Development] [NUT]:
Yah, that just means your cache got terminated in some earlier stage... download this FTF and use it to restore a functional cache. It will work on all FW versions around, Sony never changed location or size of the partitions between them.

When you have flashed this, check /cache again and look for a folder called 'lost+found'. If it's there you have a functional cache partition again and can try to install again.
[Xperia Z Android Development] nhoc_huhu:
can U upload file supperuser.zip New...Because my rom C6602 and i installed Your supperuser.zip Old, root is Ok but when i flash basel and kernel .307,my phone reboot when i mout r/w ~~
[Xperia Z Android Development] [NUT]:
Download the AROMA ROM Mutator and try to re-install one of the superuser applications using TWRP, it will flash the patch to fix that too. Though it might be that Sony somehow made the process causing the reboots to be more persistent...
[Xperia Z Android Development] nhoc_huhu:
Thanks U...I will try now :silly:
[Xperia Z Android Development] [NUT]:
Hmm, I'll have a go at that tonight as soon as I have the time... we'll kill that SOB causing the reboots once and for all :cowboy:

Good for both our ROM releases ;)
[Xperia Z Android Development] Carceri:
I'll save you the trouble... it doesn't work :( It seems to be monitored and respawned by /init

The following works... sometimes. It kills ric and (hopefully) deletes it before it respawns and checks the filesystem permissions.

kill $(pidof /sbin/ric); mount -oremount,rw /; rm /sbin/ric; kill $(pidof /sbin/ric); mount -oremount,ro /

The major disadvantage of this method is that if ric spawns fast enough and manages to do its filesystem checks (which it probably will sometimes?) then the system reboots. Probably changing (temporarily) the priority of the init process will give us a better chance to delete ric before it's respawned.
[Xperia Z Android Development] [NUT]:
That's no problem, I have some other ideas but I need to check some things first.
[Xperia Z Android Development] fards:
ok carceris method doesnt work here.

dont have time to look into it in detail now, ill try and catch whats happening later
[Xperia Z Android Development] [NUT]:
No worries guys, we'll find a way around it, we always do :cool:
[Xperia Z Android Development] naujoks:
I tried to install that zip, but it broke off with the same error message as before.
[Xperia Z Android Development] lethalfriend:
Just a quick question, should we refrain to flash this Rom until the above issue will be fixed?
[Xperia Z Android Development] nikc0069:
Flashed in TWRP (existing twrp i believe was an earlier versin that 2.5.0.0), turn off, flashmode, flash ftf, reboot - totally fine :) (locked bl so no kernel changes)
[Xperia Z Android Development] [NUT]:
Then... where are the logs? :p

No, the ROM works just fine otherwise from what I gather from the people who did install it, it's just the remounting of /system which is a problem.
[Xperia Z Android Development] [NUT]:
If you flashed the entire FTF you also flashed the kernel, it's a stock Sony kernel so your phone with locked bootloader accepts that without problems :)
[Xperia Z Android Development] nikc0069:
Sorry I wasn't clear. I meant no kernel changes from stock - or in a clearer form: no custom kernel (should have said that to start with).
[Xperia Z Android Development] NetSkill:
First root for xperia z was causing this reboot problems and devs. fixed it ..so how ? ...Sony downloaded root applied and found a workaround to ensure future rooting i think... They forcing us to unlock the bootloader if one day someone find a solution for Bravia engine on unlocked bootloader i will unlock it immediately

Odoslané z C6603 cez Tapatalk 2
[Xperia Z Android Development] [NUT]:
My guess is that they moved some things in the boot order, which makes all previous fixes unusable... So, it's time to find another :)
[Xperia Z Android Development] NetSkill:
We need to delete ric daemon from boot

And reboots should be gone

Odoslané z C6603 cez Tapatalk 2
[Xperia Z Android Development] [NUT]:
Probably yes, the question is not what the fix is but when to apply it and from what script. If we integrate it in the chargemon hijack it will break too easily when updating or installing a recovery.
[Xperia Z Android Development] naujoks:
Sorry, noob alert! Where can I find the logs?
[Xperia Z Android Development] [NUT]:
uh... i already told you where :p /cache/recovery :silly:
[Xperia Z Android Development] [NUT]:
[MENTION=265575]fards[/MENTION] and [MENTION=3379666]Carceri[/MENTION]

I've found a candidate for replacing with a script...

I'll be testing that tonight on doomkernel to see if it breaks something, if it doesn't i'll try it on stock kernel.

This one is so early in the boot process there is no f*ck*ng way sony can prevent this from doing what we want: to delete ric :p
[Xperia Z Android Development] naujoks:
As mentioned, there is nothing in there, and trying to flash the file you recommended to rebuild the cache broke off with the same error I got when trying to flash the ROM.
[Xperia Z Android Development] [NUT]:
ack :eek: I'm mixing up people... sorry :angel:

Try to create a solid backup and restore your phone using SUS. Then try again.
[Xperia Z Android Development] naujoks:
No worries... Just occurred to me: should I have used Faltboot to flash the cache restore, or recovery?
[Xperia Z Android Development] [NUT]:
flashtool/flashmode...

I was too quick. It's an FTF... So flashmode is the only mode... You need to tick the box wipe cache.
[Xperia Z Android Development] lethalfriend:
Couple of more questions before i proceed to flash this rom, as per the OP instructions, is backing up of the sdcard0 mandatory? Also, is it necessary to use the external card to flash the rom or i can use the internal storage as well?

Thank you.
[Xperia Z Android Development] naga.nino:
My phone reboots after I:

1. mount r/w in root explorer

2. try to block adds with Lucky Patcher

3. try to type "chmod 755 /system/etc/install-recovery.sh" command in terminal emulator
[Xperia Z Android Development] Langdang02:
[MENTION=4904057][NUT][/MENTION] still waiting for your reboot solution, i like new 307 firmware :D
[Xperia Z Android Development] [NUT]:
No, it's not mandatory, but it's just for safety sake... If the sh*t might hit the fan, you won't lose anything...

You can use internal storage to install it if you don't have a sdcard.
[Xperia Z Android Development] lethalfriend:
Thank you for a quick response, i'll flash it shortly :) Also, best of luck for finding the fix for reboot issues.
[Xperia Z Android Development] RoberM:
Hi, just tested this rom it reboots when mounting /system/ like crazy, even if it is mounted as read only :eek:

I hope you find a fix :good: if you need some testing, just let me know ;)
[Xperia Z Android Development] naujoks:
I tried this with Flashtool/flashmode now, and it installed alright (cache folder still empty after install).

However, when trying to install your ROM again, I still get the same error...

Anything else I could try? I don't think I'd want to go through the whole Sony restore and restore all my data...
[Xperia Z Android Development] fards:
looks like the reboot issue was incredibly simple in the end..

ric is being called from /sbin not /system/bin (there's binaries in both)

change the permissions to 644, so its no longer executable.

I did remove /system/bin/ric and replace it with a blank file, so I'm just checking that replacing that with the original still works, set as non executable.

EDIT

sbin/ric gets its permissions reset on reboot, so setting a blank ric in system/bin/ and /sbin/ works (you can back up or rename ric to something like ricd or ricx if you want to keep it)

I guess deleting both would work as well but ive not tested that
[Xperia Z Android Development] shysparrow:
Thx

You rOcK Man..!

:highfive:

Everything just worked fine and in place.. thank u so much.. :good:
[Xperia Z Android Development] Carceri:
In reply to fards:

I don't see this working. /sbin is from the kernel ramdisk so nothing in there survives a reboot.

The /system/bin/ric is part of cwm recovery and just contains an empty loop. I don't know why it's there but I have removed it in my rom with no problems.
[Xperia Z Android Development] fards:
yes sbin/ric will get restored on reboot, but after reboot it's working all the same..
[Xperia Z Android Development] kostikos:
I 've installed 253 prerooted version of wawyed. Can i flash straight this, or i have to go back to 434 root it etc.?