yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] red423:
I have a new 1.5g dual sim clone s4. It is running Jellybean 4.2.1. Everything works well except for Netflix. Youtube runs great, video capture is good. I read the forums and did a search, most of the info is before this type of chip is used. I need help fixing the phone. netflix will only do audio, and it will show the captions. We can use the tool bar to fast froward the movie and it will show the movie clips, yet when it buffers to that point in the movie it will buffer and the screen goes dark (video won't play at all) but my question is this, WHY? what had occurred in the chinese making these knockoffs that this would happen? I have tried older versions of Netflix, called netflix, troubleshot the phone with them and no luck.

I have rooted my kindle, I have rooted my HP pad, but this seems to be a minor issue with the phone and 4.2?

Simply reloading a new rom or "here's a new download" doesn't answer the question of why is this happening???? Is it a simple fix I am not seeing? These phones are unlocked and supposedly rooted already, what am I missing? Thanks from a father who wants to learn............
[Windows Phone 8 Q&A, Help & Troubleshooting] aSpirit81:
can someone you guys give me link for v1 stock rom for htc 8x?

i have HTC_032 CID,and i must have this rom to flash my phone.

THX

RUU_ACCORD_U_APO_00_HTC_Europe_1.00.401.24_1.10.32.19.19_3_15.39.32_RELEASE.exe
[Windows Phone 8 Q&A, Help & Troubleshooting] DilanChd:
This?

http://htcfanboys.com/download/anaheiim/?action=list&file=6555
[Windows Phone 8 Q&A, Help & Troubleshooting] aSpirit81:
yes,but its corrupted.THX anyway mate.
[Windows Phone 8 Q&A, Help & Troubleshooting] DilanChd:
The MD5 checksum is the same, which means that the file is not corrupt.

Retry the download.
[Windows Phone 8 Q&A, Help & Troubleshooting] aSpirit81:
ok,i downloaded...you know what the correct tutorial?i put phone in bootloader mode,but i got error 338,pk verify error and phone got reboot.i use normal usb,i havent y cable.i just want to flash fresh rom,fresh instalation.
[Windows Phone 8 Q&A, Help & Troubleshooting] DilanChd:
The only tutorial for the HTC 8X, that I could find: [Guide] Unbrand HTC 8X
[Windows Phone 8 Q&A, Help & Troubleshooting] aSpirit81:
thx mate...whata misteika i meika...hahah...i cant believe,the phone its not cheap,we even cant flash the fresh rom.cant believe.
[Windows Phone 8 Q&A, Help & Troubleshooting] pfg:
HTC 8x and can not be upgraded for CDR3

Plz help !

I have the HTC 8x and can not be upgraded for CDR3.

Downloading the update on my phone is normally but can not go in and update

sent message: "Can not open (8009000d)"

Can anyone help?
[Xperia Z1 Original Android Development] Phil3759:
Main thread + features + install instructions + dev support

http://xdaforums.com/showthread.php?t=2201860

PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM

It is a well proven recovery for many phones

It also adds a full touch interface a completely configurable GUI

Please give your feedback, what works, and any bug you could encounter

Read the features, and check if you are missing something

Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut

Download links

Last version can be found here:

Big credits to [MENTION=2784807]DooMLoRD[/MENTION] for his help to rebase on stock kernel

XDA:DevDB Information

[honami][CWM Advanced Edition] PhilZ Touch, a Tool/Utility for the Sony Xperia Z1

Contributors

Phil3759, DooMLoRD, [NUT]

Version Information

Status: Testing

Created 2014-03-29

Last Updated 2014-03-29
[Xperia Z1 Original Android Development] xque_31:
hello and thank you.

I have found the file. img I can not find my method for installing or flashed to the files on my Z1.

sorry i use google translation I'm French

Français

bonjour et merci . j'ai bien trouvé le fichier .img mes je ne trouve pas la méthode pour l installer ni pour flashé le fichiers sur mon Z1

Bien cordialement

Xque_31

Envoyé de mon C6903 en utilisant Tapatalk
[Xperia Z1 Original Android Development] DooMLoRD:
hi [MENTION=4666971]Phil3759[/MENTION],

firstly welcome to the Z1 forums!

the kernel image you posted will not boot on any device as it misses the crucial device tree files... here are detailed instructions on how to build bootable kernels for many Xperia device since 2011:

http://xdaforums.com/showthread.php?t=2447310

I have fixed this by integrating the ramdisk with stock FW 290 (android 4.3) so that people can test out this recovery..

download link for fixed image is:

http://d-h.st/Iz2

BTW me and my colleague [MENTION=4224819]Napstar[/MENTION] have worked on similar "Advanced recovery" before (it was released some time in late 2011/early 2012):

[YOUTUBE]7FN4toSbB5A[/YOUTUBE]

our sources have also been released quite some time back:

http://xdaforums.com/showthread.php?t=1485829

but i discontinued work on it as i got busy with personal work

I would recommend getting in touch with [MENTION=4224819]Napstar[/MENTION], may be we can collaborate for some bigger things :)

also another thing... since I have worked on multi-recoveries in my kernels, i had 4 recoveries in my X10 kernel way back in septmber 2011!!, and since you are actively developing this advanced recovery, do i have your permission to integrate this recovery in my DooMKernel? (I have made my DooMKernel for close to 21 devices from various vendors Sony, HTC, Samsung, Huawei, Kindle, etc; currently I actively support only 4 devices though: Xperia Z1, Z, SP & T)

note to users:

if you want to test out this recovery then you need to HOTBOOT this kernel:

fastboot boot kernel.img

regards,

DooMLoRD
[Xperia Z1 Original Android Development] Phil3759:
Many thanks for your support

Yes, I looked at your amazing work. TWRP-ifying CWM is just amazing

However, the codes we use diverge too much, but yes, why not, collaboration can be always welcome. It just take a big effort to start so that each one familiarizes with other's code

Obviously you can use and repack any of my files to your wish

I also should added a note that this is a sample for devs to use it at their wish, like I do for Xperia Z. I knew well that it won't boot any stock ROM. Thought it would boot cm-11.0 roms though...

Anything I have to do when compiling to make it at least boot cm-11.0?

If you agree, I will add your recovery.img to goo.im instead of actual one + add full credits in OP
[Xperia Z1 Original Android Development] DooMLoRD:
well [MENTION=4224819]Napstar[/MENTION] is currently working on something new :) please get in touch with him, he is busy with his PhD work but I am sure he can find out some time ;)

it wont even boot on any Z1 irrespective of ROM... actually the kernel formats for Sony devices vary A LOT! they are not using standard boot.img format... and anyways especially for the msm8974 board (and beyond) the new device tree format will be used... its a bit tricky to explain but Krab has a good tutorial here:

http://xdaforums.com/showthread.php?t=2469421

sure go ahead... u can link the recovery.img where ever u want :p i just repacked ur ramdisk with the correct zImage & dt.img :D
[Xperia Z1 Original Android Development] DooMLoRD:
here is a bonus for you...

build tools for honami...

http://d-h.st/Vk3

just extract the archive, replace the ramdisk.cpio.gz with new compressed ramdisk and run makeit.sh

that should build a bootable boot.img for Z1 (honami)
[Xperia Z1 Original Android Development] Phil3759:
That's a lot

I will take a look at it or maybe just provide recovery.zip installer so that interested devs can repack, or even the ramdisk

Huge thanks

I will get in touch with Napster :good:
[Xperia Z1 Original Android Development] Phil3759:
I took a look at your script

I was aware of the dt.img and already use it for Note 3 and Note 10.1 2014 from Samsung and on many of the new LG devices

Actually, cm-11.0 build tree is fixed to use a custom bootimg make file:

https://github.com/CyanogenMod/android_device_sony_rhine-common/blob/cm-11.0/custombootimg.mk#L56

The dt.img is kernel specific and is built along the zImage as you surely know. When compiling cm-11.0 boot.img, the zImage and matching dt.img are compiled and repacked using custombootimg.mk

Unpacking your fixed recovery.img I see the only changes are the dt.img and zImage to be able to use with stock ROMs. That's great and most people would prefer it that way

However, I am still unsure why you say that my original release won't boot a cm-11.0 ROM? Is it mandatory to have the kernel built along the ROM ? I do not think else your repack with zImage would work only on one specific ROM

Hope you can enlighten me on that
[Xperia Z1 Original Android Development] DooMLoRD:
the original boot.img didnt have a dt.img :)
[Xperia Z1 Original Android Development] Phil3759:
really wired as I used the device tree with custom bootimg make file I linked above

I will look at it and thank you for your repack. I added to main goo.im repo
[Xperia Z1 Original Android Development] dlads:
Afternoon chaps,

Just wanted to give this a whirl as i've used your recoveries before, so out of the two which are on the download section, which one should work on 4.2.2, with a locked bootloader?

Cheers m8 an glad you've made it onto the Z1 ;)
[Xperia Z1 Original Android Development] [NUT]:
[MENTION=4666971]Phil3759[/MENTION]

For some reason on locked bootloader devices, while the texfat module has been loaded, I'm unable to get philz touch to mount any exFAT sdcard unless I change the extra.fstab line for it from 'auto' to 'texfat' ... any way to get this working normal again?
[Xperia Z1 Original Android Development] Phil3759:
The honami version is compiled without minivold support for exfat modules. It will only work with fuse

https://github.com/PhilZ-cwm6/philz_touch_cwm6/blob/cm-11.0/boardconfig/BoardConfig.mk#L520

You can try to use the yuga minivold binary instead. If it is ok and you want to add support it officially with updates, I will do like yuga and enable the exfat flag
[Xperia Z1 Original Android Development] DooMLoRD:
hey I have the Xperia T & SP can you create a touch version for them too?

i can be your guinea pig for testing :)

SP: https://github.com/CyanogenMod/android_device_sony_huashan

T: https://github.com/CyanogenMod/android_device_sony_mint
[Xperia Z1 Original Android Development] Phil3759:
Compiled and opened dedicated threads

Feel free to put your magic if needed :angel:
[Xperia Z1 Original Android Development] [NUT]:
[MENTION=4666971]Phil3759[/MENTION]: The backlight is really very dim on locked bootloader devices... setting that to the max setting doesn't change it all that much either.

Anything I can do to test if it's philz touch causing this?
[Xperia Z1 Original Android Development] Phil3759:
I use this path:

/sys/class/leds/wled:backlight/brightness

Since the repack was done using a stock kernel, not sure if it still matches!
[Xperia Z1 Original Android Development] [NUT]:
It does still match. It's like the value to it got cut in half...
[Xperia Z1 Original Android Development] Phil3759:
try to set brightness in recovery gui, then:

adb shell
cat "/sys/class/leds/wled:backlight/brightness"

Post the value here, maybe you're getting some crap because I did not properly escape those ":"

No idea why Sony have such genius ideas in naming their paths
[Xperia Z1 Original Android Development] [NUT]:
Busy with making a system dump on my Z1 now, will do that soon though.

---------- Post added at 12:55 AM ---------- Previous post was at 12:36 AM ----------

Done that:

~ # cat "/sys/class/leds/wled:backlight/brightness"
10
~ # cat "/sys/class/leds/wled:backlight/brightness"
255

First one is from the screen/power save mode, the second is when fully lit... but still the screen is only half as bright or maybe even less then half compared to using the XZ philz ...
[Xperia Z1 Original Android Development] Phil3759:
Good news for my code...

Can you try the version not repacked by DoomLord and try to boot it into recovery if it works and fixes your brightness

However it could fail as DoomLord suspected it is missing the dt.img despite after reviewing sources I am quiet sure it is bundled with.

I did not have time to unpack and manually verify it however

Else, in adb shell, try to manually echo to the brightness sys file

Also maybe your device needs some properties set for it to work
[Xperia Z1 Original Android Development] [NUT]:
Actually, I did the same thing with your build I have always done for the XZ, didn't download doom's repack but yours, extracted the ramdisk and used that.

Still want me to try?
[Xperia Z1 Original Android Development] AndroPlus:
Stock value in "/sys/class/leds/wled:backlight/brightness" is from 288 to 4095.

255 is lower than the lowest value, maybe it's the problem.
[Xperia Z1 Original Android Development] [NUT]:
Scrap that :D

I found a possible fix, which is elegant and easy to adopt for you I think:

~ # ls -la /sys/class/leds/wled:backlight/
drwxr-xr-x 3 root root 0 Apr 8 23:34 .
drwxr-xr-x 3 root root 0 Apr 8 23:34 ..
-rw-r--r-- 1 root root 4096 Apr 8 23:36 [B]brightness[/B]
-rw-rw-r-- 1 root root 4096 Apr 8 23:34 cabc
lrwxrwxrwx 1 root root 0 Apr 8 23:34 device -> ../../../leds-qpnp-ee2ff600
-rw-r--r-- 1 root root 4096 Apr 8 23:34 [B]max_brightness[/B]
-rw-rw-r-- 1 root root 4096 Apr 8 23:34 max_current
drwxr-xr-x 2 root root 0 Apr 8 23:34 power
lrwxrwxrwx 1 root root 0 Apr 8 23:34 subsystem -> ../../../../class/leds
-rw-r--r-- 1 root root 4096 Apr 8 23:34 trigger
-rw-r--r-- 1 root root 4096 Apr 8 23:34 uevent
~ # cat /sys/class/leds/wled:backlight/max_brightness
4095

The value inside max_brightness is the true maximum you can set in to brightness. When brightness is set to 4095, the screen is at it's true maximum backlight power..

Can you make philz touch read that value as a maximum it will allow to set using the setting in philz?

Probably wise to use your current code but with a check on max_brightness value to calculate the step values for the setting.

---------- Post added at 02:00 AM ---------- Previous post was at 01:58 AM ----------

Actually, 0 is the lowest possible value (which is off) but the ROM brightness control allows nothing less then 288 probably :)
[Xperia Z1 Original Android Development] jagdesh:
hi Philz

I have flashed latest dual recovery zip file by Nut on my Z1 Locked Bootloader.

When I enter into your recovery for some reason the backlight of the phone is not working. I mean in your recovery the phone's baclight does not come on and it remains quite dark. I went into settings and even after selecting maximum brightness still it was quite dark compared to the normal settings I have had till now. TWRP is working fine but your recovery this is the only problem I am facing now.

I wrote this on Nut's thread and he advised me to write this issue here since it only pretains to your recovery.

Hope you can find a fix soon.
[Xperia Z1 Original Android Development] DooMLoRD:
change max_current
[Xperia Z1 Original Android Development] Phil3759:
Sony sucks on this

Is there another file i can use to use usual 0 to 255 settings?

Or a property to set
[Xperia Z1 Original Android Development] DooMLoRD:
Hold on let me check
[Xperia Z1 Original Android Development] [NUT]:
The max_brightness exists on my Xperia Z as well, which has 255 as maximum.

I've not touched max_current yet because I considered reading max_brightness the most effective way...

If you wish I can test the current settings too but from my perspective it's probably easier to modify your code to read the max brightness if the file exists and then devide the value to the 5 or 6 steps which are default in your brightness control to use... If the file doesn't exist, you can easily ignore that and go for default. Safe and simple. In my eyes anyway :)
[Xperia Z1 Original Android Development] DooMLoRD:
easiest solution is to update init script to

busybox echo 4095 > /sys/devices/leds-qpnp-ee311400/leds/wled:backlight/brightness

just before recovery ramdisk extraction
[Xperia Z1 Original Android Development] Phil3759:
but I guess that when ever the screen auto-dims or user sets a different brightness level, your fix is bypassed
[Xperia Z1 Original Android Development] [NUT]:
Hmm... From what I see upon entering philz, it will set the saved setting anyway, regardless of the brightness setting already there.
[Xperia Z1 Original Android Development] Phil3759:
true + my above post
[Xperia Z1 Original Android Development] [NUT]:
Yah, we posted the same thing at the same time :D

I think we agree... ;)
[Xperia Z1 Original Android Development] Phil3759:
I will work on your idea

I just cannot get how they came with those values
[Xperia Z1 Original Android Development] [NUT]:
Probably because of a higher brightness control or simply because of different hardware being used...
[Xperia Z1 Original Android Development] POWER1FM:
Is it possible to make this recovery compatible with rom manager?

It's very useful for setting name and correct date!

Great work anyway! I love it!
[Xperia Z1 Original Android Development] [NUT]:
Just

FINALLY

fixed the time issues on XZDualRecovery, install 2.7.76 and your need for the ROM Manager will disappear :good:
[Xperia Z1 Original Android Development] Phil3759:
Update 6.10.0

I added needed code to get max_brightness

Please report if setting brightness is now fixed

Also, I added credits to OP [MENTION=2784807]DooMLoRD[/MENTION] for his help

I uploaded a repack based on stock kernel and original for cm-11.0
[Xperia Z1 Original Android Development] [NUT]:
Will include and test it tonight or tomorrow at the latest.

Thanks for fixing it :)
[Xperia Z1 Original Android Development] POWER1FM:
I like rom manager because you just set the name and when the job is done the device boots automatically in to the os.

Thanks anyway!!!

Keep up the good job!!! :)
[Xperia Z1 Original Android Development] [NUT]:
Testing done now... unfortunately it doesn't work. The max I can set in recovery still is 255... :(
[Xperia Z1 Original Android Development] Phil3759:
Wired

I will release a debug version
[Xperia Z1 Original Android Development] Phil3759:
Update 6.10.2

fixed reading max brightness

Was a bug on my side, sorry

I tested this on my i9505 and I can correctly read the file now
[Xperia Z1 Original Android Development] [NUT]:
Will test it in about an hour or so, will let you know the results :good:

-- EDIT --

Confirmed working :good:
[Xperia Z1 Original Android Development] Phil3759:
Great, thank you for the support

This is a good patch as all devices has the max_brightness

This is the first time I see it beyond 255 though
[Xperia Z1 Original Android Development] [NUT]:
Something else popped up though:

When someone is using an exFAT formatted sdcard, philz is not able to mount it. It seems similar to the problem [MENTION=4675598]shoey63[/MENTION] fixed, but I don't have that luxury of changing the kernel commandline as it's intended for locked bootloader devices.

You said in the yuga thread something needs to be set to allow the selinux rules to apply on the sony kernel... how do I enable these?

I can mount the sdcard from adb shell using mount -t texfat <blockdev> /external_sd but even when I try to restart philz, it won't pick it up.
[Xperia Z1 Original Android Development] Phil3759:
they should be mounted to /storage/sdcard1

The change is made during compile time. Try to use my sepolicy binary and let me know
[Xperia Z1 Original Android Development] [NUT]:
At work now and I didn't bring the Z1, so a question before I try later tonight:

Any particular moment to run this binary? Does it require any commandline switches to set something?

-- EDIT --

Just re-read your comment: So, if I mount it by hand on the (non existent) folder sdcard1 inside /storage it should pick it up?
[Xperia Z1 Original Android Development] Phil3759:
yes, if you mount it by hand there it should be fine

I see now: I did not enable use of exfat modules in the honami

Try to just use the minivold from the Z and let me know
[Xperia Z1 Original Android Development] [NUT]:
Will do, I'll get on it later tonight :)
[Xperia Z1 Original Android Development] Phil3759:
Well, no

I maybe need to enable exfat ko module at compile time to get you a working minivold

But, by default, you should get a fuse mount. Can you explain in detail what is happening on my default ramdisk?
[Xperia Z1 Original Android Development] [NUT]:
Well, nothing bad, but it just doesn't mount the sdcard :)

It will mount the sdcard by hand though: the texfat module has been loaded correctly by the scripting bootstrapping the recovery.

It just doesn't like the 'auto' setting much...

/devices/msm_sdcc.2/mmc_host /storage/sdcard1 auto defaults voldmanaged=sdcard1:auto

If I change auto to texfat it will work, but of course only for exfat sdcards :eek:

Maybe a change back to fuse is the only option, in the Sony ROM fuse is working just fine.
[Xperia Z1 Original Android Development] Phil3759:
Ok

I will try to do some changes to sepolicy binary and modify recovery sources to use texfat
[Xperia Z1 Original Android Development] Phil3759:
Here's the ramdisk of 6.10.3 release:

http://d-h.st/sp8

I enabled use of texfat kernel module (minvold binary) and added texfat selinux properties into sepolicy binary

Let me know if it works
[Xperia Z1 Original Android Development] [NUT]:
I'll test it tonight again, will let you know how it behaves :)
[Xperia Z1 Original Android Development] [NUT]:
I was home early today, had some minutes to burn: test done, still does not work by default :(

Anything specific you want me to test or do on this version?

I'll try again tonight, including all the adb tricks to see if i can make it budge...
[Xperia Z1 Original Android Development] Phil3759:
A log maybe after mount in recovery fails

Also adb shell results

I did not make needed changes to drop to system mount properly. I would like to debug the minivold part.

Can you ask [MENTION=4675598]shoey63[/MENTION] how he fixed it on Yuga?
[Xperia Z1 Original Android Development] [NUT]:
I can and I will :)
[Xperia Z1 Original Android Development] [NUT]:
Tried 2 times. The vold devices path doesn't match the sony kernel's sys path so I corrected it to go to /sys/devices instead.

I haven't been able to talk to shoey63 yet but this are the logs from my attempts.

I can mount the exfat card by hand without issues... but philz doesn't pick it up, not even when I mount it inside /storage as sdcard1
[Xperia Z1 Original Android Development] Phil3759:
If recovery cannot see it, then there is an issue in either permissions or path

Try to use real /dev/block/mmcblk1p1

/dev/block/mmcblk1p1 auto auto defaults voldmanaged=sdcard1:auto

selinux permissions are important too

I really have no big idea without the device to check/test
[Xperia Z1 Original Android Development] [NUT]:
it's really what you wrote? I mean, twice the 'auto' ?
[Xperia Z1 Original Android Development] [NUT]:
[MENTION=4666971]Phil3759[/MENTION] I could give you adb access to the phone through a Linux ssh and a webcam view on the phone, just the recovery navigation will be a bit harder...

If you want me to make it happen, let me know :)
[Xperia Z1 Original Android Development] Phil3759:
Yes, new vold uses label and mount point should be auto

Oh, too short on time. [MENTION=4675598]shoey63[/MENTION] fixed it for yuga. I am interested in how he did if he can tell us.

Also look at his latest ramdisk repack

And let me know if you fix it please
[Xperia Z1 Original Android Development] [NUT]:
Okay, I will let you know if and how I fixed it :)

Thanks sofar!
[Xperia Z1 Original Android Development] shoey63:
My fix for Yuga involves adding selinux =permissive to the kernel command line so that Philz recovery can see it. (Whilst selinux is present in Sony kernels, it is dormant ATM)

Unfortunately this solution is totally useless for pure stock kernel, as unpack, modify and repack is required :(