hey guys i'm having issues downgrading my Razr M back to ICS. I did read through alot of threads, I downloaded RSD Lite 6.1.4 then i downloaded the software for Razr M ICS. I then followed the instructions and opened up the XML file and deleted the GETVAR line and OEM line. but it just gives me an error when i try to flash the file, can somone tell me what i'm doing wrong?
I got this file US|Verizon|4.0.4|Blur_Version.77.111.10.XT907.Verizon.en.US
it came out as VZW_XT907_4.0.4-7.7.1Q-144_SMQ_S1-36-10_CFC.xml after i unzipped it.
then i went and edit VZW_XT907_4.0.4-7.7.1Q-144_SMQ_S1-36-10_CFC.xml to delete the GETVAR line
I then loaded it into RSD to try to flash, it says failed and now the phoen is stuck in AP fastboot because it had a flash failure.
can somone tell me what i did wrong? do i need to rezip it into a SBF file?
edit: so i reflashed the 4.1.2 file on there and now it turns back on. but can somone tell me how to take it back to 4.0.4? here is the XML file i edited if anyone is interested
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="SM_VZW_CFC" />
<software_version version="scorpion_mini-user 4.0.4 7.7.1Q-144_SMQ_S136-10 20 release-keysSM_BP_1139.000.32.12P" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="flash" partition="partition" filename="gpt_main0.bin" MD5="164ABBBEDFC1A113F5A1890DD63C0A93" />
<step operation="flash" partition="sbl1" filename="sbl1.mbn" MD5="169C16EE30F086C084EFB239741E9775" />
<step operation="flash" partition="sbl2" filename="sbl2.mbn" MD5="2A98236BC098E74D9EE9CBBC6049FB2C" />
<step operation="flash" partition="sbl3" filename="sbl3.mbn" MD5="112950A3D7962D7E8E0A1B115DC0E796" />
<step operation="flash" partition="rpm" filename="rpm.mbn" MD5="16C5ED30D233CE9BDB8D271DE163C38A" />
<step operation="flash" partition="tz" filename="tz.mbn" MD5="567676B28DF3B060A443FEADA9C5C783" />
<step operation="flash" partition="aboot" filename="emmc_appsboot.mbn" MD5="ADCDB8732B367F57B1975B447A9AA2AC" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="45429E3985203D3A1E7334C09BD237C7" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="0B28FEFE8D9FCF02B6F92A582D5D7A07" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="logo" filename="logo.bin" MD5="506F42184C465D9CD8BB2BD27DB77F1A" />
<step operation="flash" partition="boot" filename="boot.img" MD5="C75BBEA9B6879CDFBE95A2801C6A0CE0" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="5F2DA0989ED59E2508716DCA88011746" />
<step operation="flash" partition="devtree" filename="device_tree.bin" MD5="66AD59B88203992915EAF476C9E17E58" />
<step operation="flash" partition="system" filename="system.img.ext4" MD5="3C96F96D399B4AAAC7C9A7222FEF05F2" />
<step operation="flash" partition="cdrom" filename="cdrom" MD5="8C578BC3308036F86BF30BA802E488DF" />
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
</steps>
</flashing>
The undisputed easiest way is Matt's utility 1.2
You need to be in AP fast boot and it will flash the latest stock ota from Verizon which is not ICS. I'm afraid to say once you go jellybean, no more ICS. Seriously though the utility is a one stop shop to restore, root, unlock boot loader, and flash a recovery.
Sent from my XT907 using Xparent Cyan Tapatalk 2
bmplekan said:
The undisputed easiest way is Matt's utility 1.2
You need to be in AP fast boot and it will flash the latest stock ota from Verizon which is not ICS. I'm afraid to say once you go jellybean, no more ICS. Seriously though the utility is a one stop shop to restore, root, unlock boot loader, and flash a recovery.
Sent from my XT907 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
O once i am at JB i cant downgrade to ICS? damn okay thanks
If your boot loader is locked, you can't go back. If you unlock your boot loader, you can use the FXZ files to go back.
RikRong said:
If your boot loader is locked, you can't go back. If you unlock your boot loader, you can use the FXZ files to go back.
Click to expand...
Click to collapse
so if i get the Bootloader unlocked, i can go back to 4.0.4 even though its on JB?
So i got SU and BL unlocked on JB, i'm searching for FXZ files and its not talked about much. I saw the bat utility, and i also have the SBF file. can you give me a little more direction please.
thanks
TELL ME HOW... lol
truwrxtacy said:
so if i get the Bootloader unlocked, i can go back to 4.0.4 even though its on JB?
So i got SU and BL unlocked on JB, i'm searching for FXZ files and its not talked about much. I saw the bat utility, and i also have the SBF file. can you give me a little more direction please.
thanks
Click to expand...
Click to collapse
you've unlocked??? please inform me as to how? i'm completely stumped. i have root access and everything in the latest 4.1.2 OTA and i can't unlock. no suprise, the phone isnt eligible for a motorola tool unlock using their site...
It's not possible with the latest 4.1.2 OTA, but with some earlier it was.
Related
Hello everyone. i need a proper CFC text file for the jellybean firmware of droid razr M as i have to completely flash new XML/SBF for some reason through RSD LITE
I downloaded the stock jellybeans firmware for my phone but when i open it in RSD LITE it say "please check input file Either xml format is wrong or image files associated with it are missing" i did removed the getvar line in the CFC file but nothing happens still its the same error i really need to flash this SBF/XML on my droid please help guys need urgent help. i just want to get this XML working in RSD LITE any how please share your ideas and suggestions.
the CFC text file looks like this:
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="SM_JB_VZW_CFC" />
<software_version version="smq_vzw-user 4.1.2 9.8.1Q-94-1 77 release-keysSM_BP_101032.021.32.80P" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="oem" var="fb_mode_set" />
<step operation="flash" partition="partition" filename="gpt_main0.bin" MD5="FB3D9083F1B5890BBF2FA8617D31A70A" />
<step operation="flash" partition="sbl1" filename="sbl1.mbn" MD5="FB458002D5B1B3430B0519E0F206C361" />
<step operation="flash" partition="sbl2" filename="sbl2.mbn" MD5="5E1E096A29FB49A955C595B3E7759CA7" />
<step operation="flash" partition="sbl3" filename="sbl3.mbn" MD5="16813AF63FFBF4044FBF72D75BD47DB1" />
<step operation="flash" partition="rpm" filename="rpm.mbn" MD5="0C3F4FF07D3B5037E17B8EFE5F4C66EE" />
<step operation="flash" partition="tz" filename="tz.mbn" MD5="474F31095C8146D1F86D0E5CE72B878F" />
<step operation="flash" partition="aboot" filename="emmc_appsboot.mbn" MD5="A40F6AAFA4A581023A2EDA9F23202453" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="3E7F1624D8DDA8C8E4995F99A68B321F" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="0898A1859E77F05B62E2A6D04251E30E" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="logo" filename="logo.bin" MD5="506F42184C465D9CD8BB2BD27DB77F1A" />
<step operation="flash" partition="devtree" filename="device_tree.bin" MD5="66AD59B88203992915EAF476C9E17E58" />
<step operation="flash" partition="boot" filename="boot.img" MD5="624AD56D21BE40E2C62F2D8666C1A3DA" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="A51ACEFFB3DE7BB9259F345AF8E5ABB6" />
<step operation="flash" partition="cdrom" filename="cdrom" MD5="8C578BC3308036F86BF30BA802E488DF" />
<step operation="flash" partition="system" filename="system.img" MD5="AFF82B543EF8E558892AA67D4909C067" />
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="oem" var="fb_mode_clear" />
</steps>
</flashing>
now i dont know whats wrong in it because i removed get var line. please help
or if someone is a professional and can tell me the procedure of flashing new rom through cmd that would be really great i am not a professional so i dont know what commands i have to write to flash new rom if anyone can tell me the commands properly that would be really appreciated
Here's my XML file that worked. On my phone so I can't compare for you.
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="SM_JB_VZW_CFC" />
<software_version version="smq_vzw-user 4.1.2 9.8.1Q-94-1 77 release-keysSM_BP_101032.021.32.80P" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="oem" var="fb_mode_set" />
<step operation="flash" partition="partition" filename="gpt_main0.bin" MD5="FB3D9083F1B5890BBF2FA8617D31A70A" />
<step operation="flash" partition="sbl1" filename="sbl1.mbn" MD5="FB458002D5B1B3430B0519E0F206C361" />
<step operation="flash" partition="sbl2" filename="sbl2.mbn" MD5="5E1E096A29FB49A955C595B3E7759CA7" />
<step operation="flash" partition="sbl3" filename="sbl3.mbn" MD5="16813AF63FFBF4044FBF72D75BD47DB1" />
<step operation="flash" partition="rpm" filename="rpm.mbn" MD5="0C3F4FF07D3B5037E17B8EFE5F4C66EE" />
<step operation="flash" partition="tz" filename="tz.mbn" MD5="474F31095C8146D1F86D0E5CE72B878F" />
<step operation="flash" partition="aboot" filename="emmc_appsboot.mbn" MD5="A40F6AAFA4A581023A2EDA9F23202453" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="3E7F1624D8DDA8C8E4995F99A68B321F" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="0898A1859E77F05B62E2A6D04251E30E" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="logo" filename="logo.bin" MD5="506F42184C465D9CD8BB2BD27DB77F1A" />
<step operation="flash" partition="devtree" filename="device_tree.bin" MD5="66AD59B88203992915EAF476C9E17E58" />
<step operation="flash" partition="boot" filename="boot.img" MD5="624AD56D21BE40E2C62F2D8666C1A3DA" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="A51ACEFFB3DE7BB9259F345AF8E5ABB6" />
<step operation="flash" partition="cdrom" filename="cdrom" MD5="8C578BC3308036F86BF30BA802E488DF" />
<step operation="flash" partition="system" filename="system.img" MD5="AFF82B543EF8E558892AA67D4909C067" />
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="oem" var="fb_mode_clear" />
</steps>
</flashing>
Sent from my XT907 using XDA Free mobile app
frozenbear said:
Here's my XML file that worked. On my phone so I can't compare for you.
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="SM_JB_VZW_CFC" />
<software_version version="smq_vzw-user 4.1.2 9.8.1Q-94-1 77 release-keysSM_BP_101032.021.32.80P" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="oem" var="fb_mode_set" />
<step operation="flash" partition="partition" filename="gpt_main0.bin" MD5="FB3D9083F1B5890BBF2FA8617D31A70A" />
<step operation="flash" partition="sbl1" filename="sbl1.mbn" MD5="FB458002D5B1B3430B0519E0F206C361" />
<step operation="flash" partition="sbl2" filename="sbl2.mbn" MD5="5E1E096A29FB49A955C595B3E7759CA7" />
<step operation="flash" partition="sbl3" filename="sbl3.mbn" MD5="16813AF63FFBF4044FBF72D75BD47DB1" />
<step operation="flash" partition="rpm" filename="rpm.mbn" MD5="0C3F4FF07D3B5037E17B8EFE5F4C66EE" />
<step operation="flash" partition="tz" filename="tz.mbn" MD5="474F31095C8146D1F86D0E5CE72B878F" />
<step operation="flash" partition="aboot" filename="emmc_appsboot.mbn" MD5="A40F6AAFA4A581023A2EDA9F23202453" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="3E7F1624D8DDA8C8E4995F99A68B321F" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="0898A1859E77F05B62E2A6D04251E30E" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="logo" filename="logo.bin" MD5="506F42184C465D9CD8BB2BD27DB77F1A" />
<step operation="flash" partition="devtree" filename="device_tree.bin" MD5="66AD59B88203992915EAF476C9E17E58" />
<step operation="flash" partition="boot" filename="boot.img" MD5="624AD56D21BE40E2C62F2D8666C1A3DA" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="A51ACEFFB3DE7BB9259F345AF8E5ABB6" />
<step operation="flash" partition="cdrom" filename="cdrom" MD5="8C578BC3308036F86BF30BA802E488DF" />
<step operation="flash" partition="system" filename="system.img" MD5="AFF82B543EF8E558892AA67D4909C067" />
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="oem" var="fb_mode_clear" />
</steps>
</flashing>
Thank you so much i am trying it right now
Click to expand...
Click to collapse
no it didnt worked it fails to load on RSD LITE it says "please check input file Either xml format is wrong or image files associated with it are missing" please help me when i press uncompress on RSD LITE it fails.
if anyone can tell me the manual method from cmd i would be very thankful because RSD LITE doesnt seem to work for me.. :\
whizinc said:
if anyone can tell me the manual method from cmd i would be very thankful because RSD LITE doesnt seem to work for me.. :\
Click to expand...
Click to collapse
Make sure you are uncompressing your zip file before running rsd
http://forum.xda-developers.com/showpost.php?p=52701350&postcount=13
My wife had a water mishap with her G2 which made it unusable. I flashed the .15 update on an old RAZR M for her to use. The bootloader was unlocked prior to the update. She doesn't care about being rooted or anything, just wants a phone to use. After flashing the update the entire phone is all wonky.
First off, a message pops up saying the UIDs are inconsistent and the data partition should be wiped or the device will be unstable.
Then, all sorts of apps start "stopping" with error message after message.
The Play store won't even open in order to update apps.
Any ideas how to solve this??
Where did you get the .15?... It kinda sounds like a bad flash... I would re download and flash it again... Maybe (as its unlocked) modify the XML of .10 flash it give it a run if all is good and you/she wants the .15 flash it.. Or wipe the partitions manually and flash them... Idk the fastboot commands but I can look for the thread where they are posted if that is the route that is needed to resolve the issue
We cannot teach people anything; we can only help them discover it within themselves.
dbreezy187 said:
Where did you get the .15?... It kinda sounds like a bad flash... I would re download and flash it again... Maybe (as its unlocked) modify the XML of .10 flash it give it a run if all is good and you/she wants the .15 flash it.. Or wipe the partitions manually and flash them... Idk the fastboot commands but I can look for the thread where they are posted if that is the route that is needed to resolve the issue
Click to expand...
Click to collapse
I got the .15 file from somewhere here, at least the links were from somewhere here. I'll re-download and try flashing again.
Since it was previously unlocked is it actually possible to fool it into flashing .10 and re-rooting? It's not that important really but I'd really prefer to root it for her and at least get rid of the bloat.
The most important thing is to actually get it to work properly.
Since your unlocked you have your freedom still. Don't like kk? You can go back to jb 4.1.2. Root on even .15 is as easy as flashing a recovery in fastboot and flashing su zip. As for your issues. They don't sound like the normal kk issues. I agree with dbreezy187 try a reflash
thewraith420 said:
Since your unlocked you have your freedom still. Don't like kk? You can go back to jb 4.1.2. Root on even .15 is as easy as flashing a recovery in fastboot and flashing su zip. As for your issues. They don't sound like the normal kk issues. I agree with dbreezy187 try a reflash
Click to expand...
Click to collapse
I didn't think you could go back to anything once you've flashed .15?!?
Are you saying I can start all over since I was unlocked prior to flashing .15?
chucklehead said:
I didn't think you could go back to anything once you've flashed .15?!?
Are you saying I can start all over since I was unlocked prior to flashing .15?
Click to expand...
Click to collapse
I believe you can yes... I've read a few posts from people that went from .10 all the way down to ICS so I would think the same method could be used... Just modify the XML of the firmware your flashing remove the get_ver line and you should be good to flash it
We cannot teach people anything; we can only help them discover it within themselves.
dbreezy187 said:
I believe you can yes... I've read a few posts from people that went from .10 all the way down to ICS so I would think the same method could be used... Just modify the XML of the firmware your flashing remove the get_ver line and you should be good to flash it.
Click to expand...
Click to collapse
I don't see such a line in the xml file of any of the firmwares I've downloaded:
Code:
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="VZW_XT907_CFC" />
<software_version version="smq_vzw-user 4.4.2 KDA20.62-10.1 10 release-keysSM_BP_101031.042.32.86P" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="getvar" var="max-download-size" />
<step operation="oem" var="fb_mode_set" />
<step operation="flash" partition="partition" filename="gpt.bin" MD5="5B3FD782141145E4BD1C9270D954AFF1" />
<step operation="flash" partition="sbl1" filename="sbl1.mbn" MD5="B06997B2407D87205454D47A4DE2CA77" />
<step operation="flash" partition="sbl2" filename="sbl2.mbn" MD5="9EBD6FB39A7DDBD3DD8BB0F0E7B4E612" />
<step operation="flash" partition="sbl3" filename="sbl3.mbn" MD5="B3D58C0A21BAA8DEAC238B6002ABB59E" />
<step operation="flash" partition="rpm" filename="rpm.mbn" MD5="6ACFA1DA4F8FF45341D7C2EC40C733F7" />
<step operation="flash" partition="tz" filename="tz.mbn" MD5="8514ED883150B7A0579F9431CD872B39" />
<step operation="flash" partition="aboot" filename="emmc_appsboot.mbn" MD5="974770FC264C73E429B716F1832A8C38" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="56CC3781D10C94A342F5262560EFEFDB" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="42661F0BBF0DB568369F9337324F7BEC" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="logo" filename="logo.bin" MD5="506F42184C465D9CD8BB2BD27DB77F1A" />
<step operation="flash" partition="boot" filename="boot.img" MD5="B59DF3268823BCE19DF80409C036645D" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="2FD6AB345BBE5B6C99DE1B5CE1D56F2C" />
<step operation="flash" partition="system" filename="system.img" MD5="1362E5D51CA3D71089F9B48A836624C9" />
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="oem" var="fb_mode_clear" />
</steps>
</flashing>
Its the getvar line I'm sorry
We cannot teach people anything; we can only help them discover it within themselves.
Hello everyone!
I have been searching about this matter for a few days now but can't seem to find a solution for it.
I am running a Samsung Galaxy S5 (SCL23)
I have a modified stock version of Android Lollipop Touchwiz 5.0.
I have already Deodexed the whole ROM.
I have successfully decompiled the whole SystemUi.apk and recompiled it without any errors.
I can change the color of the battery percentage text in the colors.xml (<color name="battery_text_color">#ffff0000</color>)
It works flawless!
But what i cannot seem to do is to remove the battery percentage completely.
I have tried adding: android:visibility="gone"
In the files: msim_system_icons.xml & system_icons.xml
Code:
<TextView android:textSize="@dimen/battery_text_size" android:textColor="@color/battery_text_color" android:layout_gravity="center" android:id="@id/battery_text" android:layout_width="wrap_content" android:layout_height="wrap_content" android:alpha="0.74" android:importantForAccessibility="no" android:fontFamily="sans-serif" android:layout_marginStart="@dimen/battery_text_marginStart" android:visibility="gone" />
But without any effect at all...
It just boots normally.
I have tried removing the "<TextView />" line completely.
But that just results in a SystemUI has stopped working on boot.
Is there anything i'm missing here?
Appreciating any kind of help!
Here is a full copy of msim_system_icons.xml & system_icons.xml
msim_system_icons.xml
Code:
<?xml version="1.0" encoding="utf-8"?>
<LinearLayout android:gravity="center_vertical" android:id="@id/system_icons" android:layout_width="wrap_content" android:layout_height="fill_parent"
xmlns:android="http://schemas.android.com/apk/res/android">
<com.android.keyguard.AlphaOptimizedLinearLayout android:gravity="center_vertical" android:orientation="horizontal" android:id="@id/statusIcons" android:layout_width="wrap_content" android:layout_height="fill_parent" />
<LinearLayout android:gravity="center" android:orientation="horizontal" android:id="@id/signal_battery_cluster" android:layout_width="wrap_content" android:layout_height="fill_parent" android:paddingStart="2.0dip">
<include android:id="@id/msim_signal_cluster" android:layout_width="wrap_content" android:layout_height="wrap_content" android:layout_marginStart="2.0dip" android:layout_marginEnd="@dimen/rssi_battery_gap" layout="@layout/msim_signal_cluster_view" />
<TextView android:textSize="@dimen/battery_text_size" android:textColor="@color/battery_text_color" android:layout_gravity="center" android:id="@id/battery_text" android:layout_width="wrap_content" android:layout_height="wrap_content" android:importantForAccessibility="no" android:fontFamily="sans-serif" android:layout_marginStart="@dimen/battery_text_marginStart" android:visibility="gone" />
<com.android.systemui.BatteryMeterView android:id="@id/battery" android:layout_width="@dimen/battery_icon_width" android:layout_height="@dimen/battery_icon_height" android:layout_marginBottom="@dimen/battery_icon_bottom_margin" android:layout_marginStart="3.0dip" />
</LinearLayout>
</LinearLayout>
system_icons.xml
Code:
<?xml version="1.0" encoding="utf-8"?>
<LinearLayout android:gravity="center_vertical" android:id="@id/system_icons" android:layout_width="wrap_content" android:layout_height="fill_parent"
xmlns:android="http://schemas.android.com/apk/res/android">
<com.android.keyguard.AlphaOptimizedLinearLayout android:gravity="center_vertical" android:orientation="horizontal" android:id="@id/statusIcons" android:layout_width="wrap_content" android:layout_height="fill_parent" android:alpha="0.74" />
<LinearLayout android:gravity="center" android:orientation="horizontal" android:id="@id/signal_battery_cluster" android:layout_width="wrap_content" android:layout_height="fill_parent" android:paddingStart="2.0dip">
<include android:id="@id/signal_cluster" android:layout_width="wrap_content" android:layout_height="wrap_content" android:layout_marginStart="2.0dip" android:layout_marginEnd="@dimen/rssi_battery_gap" layout="@layout/signal_cluster_view" />
<TextView android:textSize="@dimen/battery_text_size" android:textColor="@color/battery_text_color" android:layout_gravity="center" android:id="@id/battery_text" android:layout_width="wrap_content" android:layout_height="wrap_content" android:alpha="0.74" android:importantForAccessibility="no" android:fontFamily="sans-serif" android:layout_marginStart="@dimen/battery_text_marginStart" android:visibility="gone" />
<com.android.systemui.BatteryMeterView android:id="@id/battery" android:layout_width="@dimen/battery_icon_width" android:layout_height="@dimen/battery_icon_height" android:layout_marginBottom="@dimen/battery_icon_bottom_margin" android:alpha="0.74" android:layout_marginStart="3.0dip" />
</LinearLayout>
</LinearLayout>
In the latest LP firmware, there is a toggle switch in battery settings to remove the % from the status bar
*Detection* said:
In the latest LP firmware, there is a toggle switch in battery settings to remove the % from the status bar
Click to expand...
Click to collapse
Unfortunately that is not possible, since the latest update for SCL23 is LP 5.0 only.
Is it possible to add this switch by myself instead?
My idea is to locate the files that is controlling this number and just edit it away.
I'm still sitting here and fiddling with it, trying different things.
If anyone want some files from me just ask and i will post them.
I would really love to fix this, any other ideas?
It is LP 5.0 with the switch
I was thinking you could figure out what that switch changes, and add the code yourself
*Detection* said:
It is LP 5.0 with the switch
I was thinking you could figure out what that switch changes, and add the code yourself
Click to expand...
Click to collapse
I will try and look at a different ROM SystemUi and see if i can make any sense out of it.
Or maybe i will have to install The same ROM i have in a Emulator on my computer for quicker modding.
I just changed:
Dimens.xml
Code:
<dimen name="battery_text_marginStart">0.0dip</dimen>
<dimen name="battery_text_size">0.0dip</dimen>
Rebuilded.
Replaced the SystemUI, with 0644 permissions.
Also wiped Dalvik Cache & Cache.
And fixed permissions.
Restarted
To see if it will go away, i will see if it works tomorrow morning.
Its upgrading all the apps now and I've got to sleep.
Yay! That fixed it, the text is gone!
Device model Meizu MX5
OS version (android version 5.0.1)
I have that device, and i get error device is not supporting when i download app from store and try to launch the application.
https://play.google.com/store/apps/details?id=com.netvariant.banknizwa
Possible to know some reasons? and why?
The manifest
<uses-permission android:name="com.google.android.providers.gsf.permission.READ_GSERVICES" />
<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
<uses-permission android:name="android.permission.ACCESS_MOCK_LOCATION" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.WRITE_USER_DICTIONARY" />
<uses-permission android:name="android.permission.CALL_PHONE" />
<uses-permission android:name="android.permission.READ_USER_DICTIONARY" />
<uses-permission android:name="android.permission.READ_CONTACTS" />
<uses-permission android:name="android.permission.READ_PHONE_STATE" />
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
<uses-feature
android:name="android.hardware.location.gps"
android:required="false" />
<uses-feature
android:name="android.hardware.location.network"
android:required="false" />
<uses-feature
android:name="android.hardware.wifi"
android:required="false" />
<uses-feature
android:name="android.hardware.location"
android:required="false" />
<uses-feature
android:name="android.hardware.screen.portrait"
android:required="false" />
<uses-feature
android:name="android.hardware.telephony"
android:required="false" />
<uses-sdk
android:minSdkVersion="8"
android:targetSdkVersion="22" />
<uses-feature
android:glEsVersion="0x00020000"
android:required="true" />
An xposed module disable device check on playstore just apply this module ;D
How would you do that?
I used all the patches to make i9505 rom work on i9515... and finelly i find this patch...<br /><br />
Now You can install i9505 roms touchwiz on your i9515 or i9515l phone based like:<br /><br />
<br /><br />
<br /><br />
1.Note ux themed asta port rom:<br /><br />
https://mega.nz/#!B1NVQCCb!_NyO7P--oG5XePVzRLagSaO2lA_wsbPqDHWNl2C16Q8<br /><br />
<br /><br />
I use this rom and it work fine wifi , blutooth , data mobile....<br /><br />
<br /><br />
<br /><br />
<br /><br />
2.Thor v1.5 rom:<br /><br />
https://www.androidfilehost.com/?fid=24580943222146715<br /><br />
<br /><br />
So you must install the twrp recovery and install one of this roms<br /><br />
<br /><br />
Installation Instructions:<br /><br />
1. Flash a custom recovery like TWRP via Odin.<br /><br />
2. Download the Rom from the link below & copy it on your external sdcard.<br /><br />
3. Boot your phone to custom recovery (TWRP): Click Wipe --> Advanced Wipe --> Tick Dalvik, System, Data, & Cache, then swipe to confirm.<br /><br />
4. Now click Install & navigate to where you saved the downloaded Rom (external sdcard).<br /><br />
5. Swipe to confirm installation.<br /><br />
<br /><br />
After that flash this patch is for i9515 and i9515l:<br /><br />
https://mega.nz/#!i0hGwRjJ!wR064d13JIWywANY9j9iUtSvWhZsTdx-9nokHVK2wDc<br /><br />
<br /><br />
Notice: this patch work on all roms tw based<br />
Enjoy [emoji106] <br /><br />
<br />
<br />
Sent from my SM-G903F using Tapatalk
Sent from my GT-I9515 using Tapatalk
S4 gt i9515
Hello
If i will install kernel patch a4 gt i9515 will work with s7 rom
Thanks
Eu8530 said:
Hello
If i will install kernel patch a4 gt i9515 will work with s7 rom
Thanks
Click to expand...
Click to collapse
See there
https://youtu.be/YF7pb6Odkik
This channel it work on i9515
I still use this rom and it work clearly
Sent from my SM-A9000 using Tapatalk
Special thanks for sharing the patch
salem.k.salem said:
I used all the patches to make i9505 rom work on i9515... and finelly i find this patch...<br /><br />
Now You can install i9505 roms touchwiz on your i9515 or i9515l phone based like:<br /><br />
<br /><br />
<br /><br />
1.Note ux themed asta port rom:<br /><br />
https://mega.nz/#!B1NVQCCb!_NyO7P--oG5XePVzRLagSaO2lA_wsbPqDHWNl2C16Q8<br /><br />
<br /><br />
I use this rom and it work fine wifi , blutooth , data mobile....<br /><br />
<br /><br />
<br /><br />
<br /><br />
2.Thor v1.5 rom:<br /><br />
https://www.androidfilehost.com/?fid=24580943222146715<br /><br />
<br /><br />
So you must install the twrp recovery and install one of this roms<br /><br />
<br /><br />
Installation Instructions:<br /><br />
1. Flash a custom recovery like TWRP via Odin.<br /><br />
2. Download the Rom from the link below & copy it on your external sdcard.<br /><br />
3. Boot your phone to custom recovery (TWRP): Click Wipe --> Advanced Wipe --> Tick Dalvik, System, Data, & Cache, then swipe to confirm.<br /><br />
4. Now click Install & navigate to where you saved the downloaded Rom (external sdcard).<br /><br />
5. Swipe to confirm installation.<br /><br />
<br /><br />
After that flash this patch is for i9515 and i9515l:<br /><br />
https://mega.nz/#!i0hGwRjJ!wR064d13JIWywANY9j9iUtSvWhZsTdx-9nokHVK2wDc<br /><br />
<br /><br />
Notice: this patch work on all roms tw based<br />
Enjoy [emoji106] <br /><br />
<br />
<br />
Sent from my SM-G903F using Tapatalk
Sent from my GT-I9515 using Tapatalk
Click to expand...
Click to collapse
The patch shared by you works perfectly on my phone. No other patch or kernel worked before where one or the other issue I encountered.
Everything works smoothly. Thanks!
Note: Am using Albe95 ROM with Baseband: BOC3 and old Bootloader: ANI3