Related
The following is just a product of assumption and it is NOT tested. It may brick your phone
Since the last update of SEUS, Sony Ericsson made it almost impossible to unbrand the X10 mini (with the blob_fs file changing method).
However SaintyUK has given us a nice guide about debranding the X10 mini pro here
So let's assume it is working for the X10 mini. The only different thing we need is a new "build.prop" file (UK Generic from a X10 mini)!
See SaintyUK's post for instructions, if anyone is willing to try it.
*EDIT* I have uploaded a different build.prop with changed values in the version of the FW. This might work.
*EDIT2* From the latest results of the members that have tried SaintyUK's method with the attached build.prop files, it seems that it is actually working.
PS:All credits to SaintyUK for his great guide.
DISCLAIMER:MEMBERS HAVE CONFIRMED THAT THIS METHOD IS ACTUALLY WORKING BUT I HAVEN'T AND THEREFORE I AM NOT RESPONSIBLE, IN ANY WAY, FOR BRICKED PHONES.
This method worked for me. But if your current FW version is not 1.2.A.1.174, dont't use the attached file directly!
ra3al said:
This method worked for me. But if your current FW version is not 1.2.A.1.174, dont't use the attached file directly!
Click to expand...
Click to collapse
A little more info, could be quite usefull!
You said "don't use the attached file directly. You mean that in a mini with FW version 1.1.A.0.8 this build.prop (1.2.A.1.174) is not going to work?
But in a branded 1.2.A.1.174 it should work right?
Good on you DaRk_dOg
SaintyUK said:
Good on you DaRk_dOg
Click to expand...
Click to collapse
Thank you sir,
But we would be even better if we could finaly solve it!
If what ra3al said is true then we might need the build.prop from 1.1.A.0.8
But someone must confirm it first. I cannot confirm it myself because i've already debrand my mini the old fashion way (blob_fs) long time ago
At least it worked for ra3al, thats great as even it helps one person thats good
We maybe able to edit the the values in the file. Thats what I did for the X10 Mini Pro. I found the CDF number (post 2 of my thread) and inserted it into the file!
Dosn't work... The original build.prop gets restored after reboot. Used root explorer.. Also somewhere in the forum there is a target-World build.prop
Sent from my E10i using XDA App
Ok i've edited the build.prop with the value for E10i Generic UK (1237-0392). Also this build.prop is from a E10i 1.1.A.0.8
Hope this will work.
(First post updated)
It was a root explorer issye. Working with latest versuon. Place build.prop in system then repair through seus.
Sent from my E10i using XDA App
DAXGr said:
It was a root explorer issye. Working with latest versuon. Place build.prop in system then repair through seus.
Sent from my E10i using XDA App
Click to expand...
Click to collapse
The first build.prop? Or the one i added today?
Could you also tell me your FW version?
so, which build.prop should I use to debrand my x10 mini? Buildprop11A08BrandedE10i.zip or E10i_build.prop_UK_Generic.zip?
my current version is:
Phone Software Version:
1235-3408_1.1.A.0.8
GENERIC - user
File System Version:
WORLD-1-8_1.1.A.0.8
Thanks.
So placing this file in the folder and then updating will be unbranded?
Yes thats correct SEUS will hopefully debrand. Try the 'E10i_build.prop_UK_Generic.rar' file first if not try the other file (see first post)
Thanks it worked... Now i'm 1.2.A.1.174
It works using any build.prop with file system version World-1.8-....
Sent from my E10i using XDA App
e10a
Would it work with E10a version.
Also, if it's not much asking, could someone write a guide for the mini?
Thank you devs very much...you rock!
chagolucho said:
Would it work with E10a version.
Also, if it's not much asking, could someone write a guide for the mini?
Thank you devs very much...you rock!
Click to expand...
Click to collapse
You cannot use any of the build.prop attached, as they only work for E10i. On the other hand if you find a build.prop of an E10a Generic UK it could work.
*First post updated*
You mean't E10a right DaRk_dOg?
SaintyUK said:
You mean't E10a right DaRk_dOg?
Click to expand...
Click to collapse
Yeap! I'm terribly sorry, made the correction!
But it MUST be from UK???
I dont think we would be able to get a E10a build.prop from there...
And the following question would be...does somebody have a E10a generic build.prop????????
Hi,
did any one have the last update from SE for Multi-Touch ?
I tryed to change the No. in build.prop file to
1238-6349
and i updated my x10 with update service again
now i have multi-touch but the market is gone
if any one have this update pls give me the nombers of build.prop file
Genaric, Global or Nordic
waiting for you guyz
really this update very important for me coz it has Arabic font without any problem
try this thread: HERE
Tehouster said:
try this thread: HERE
Click to expand...
Click to collapse
thanks any way
but
u didnt get my point
i want to ask did any one has the update with this build Number
2.1.A.0.435
if it does i want the build.prop file
try here instead... http://forum.xda-developers.com/showthread.php?t=933920
Ghaith Alshareef said:
Hi,
did any one have the last update from SE for Multi-Touch ?
I tryed to change the No. in build.prop file to
1238-6349
and i updated my x10 with update service again
now i have multi-touch but the market is gone
if any one have this update pls give me the nombers of build.prop file
Genaric, Global or Nordic
waiting for you guyz
really this update very important for me coz it has Arabic font without any problem
Click to expand...
Click to collapse
search, search, search...
go HERE follow HOT-TO HERE
search, search, search...
Hi all,
I was fed up with waiting for an official update for my branded SK17i (with azerty keyboard so I couldn't just flash the generic global and anyway, I rather wanted an update through SEUS).
So I found out that it's possible to fool SEUS into thinking your phone belongs to another region by editing the region codes (CDA strings, they're called, apparently) in /system/build.prop
Prerequisites: only a rooted phone and a way to read and change files in the system directories (either via ADB or via a root file explorer like ES file explorer which I used). No need to unlock bootloader as seems to be required for other flashing methods!
So for those of you who wish to try the same, I'll try and compile a list of region codes. Feel free to post your region code (it can be found in /system/build.prop)
and I'll add it to this list!
PHONE: Mini Pro - SK17
1251-0622 - Generic - French - AZERTY
1250-5673 - Mobistar - Belgium - AZERTY
1254-0468 - Generic - Belgium - AZERTY (thanks to Swimon)
1248-7407 - Generic UK - QWERTY (thanks to Raph4)
1249-8051 - Generic Baltic - QWERTY (thanks to Raph4)
1249-8044 - Generic Nordic 1 (SE/FI) - QWERTY (thanks to Raph4)
1249-8053 - Generic Nordic 2 (NO/DK/IS) - QWERTY (thanks to Raph4)
1250-2159 - Generic Iberic - QWERTY (thanks to Raph4)
1250-0859 - O2 UK - QWERTY (thanks to Matchstick)
1249-1887 - Generic - German - QWERTZ (thanks to Ragalthar)
A whole list of SK17i codes(thanks to koperta4512)
Phone: Live With Walkman - WT19
1254-1864 - Czech: T-Mobile (thanks to strby)
A whole list of WT19i CDA codes(thanks to boyq)
Phone: Mini - ST15
A whole list of codes(thanks to koperta4512)
Phone: Arc - LT15
A whole list of codes(thanks to koperta4512)
Phone: Active - ST17
A whole list of codes(thanks to koperta4512)
Phone: Ray - ST18
A whole list of codes(thanks to koperta4512)
Phone: Neo V - MT11
A whole list of codes(thanks to koperta4512)
Phone: Neo - MT15
A whole list of codes(thanks to koperta4512)
Phone: Arc S - LT18
A whole list of codes(thanks to koperta4512)
Explanation of the country codes in the links found above: Here, thanks to MSTHETERROR
NOTE: while this fools SEUS into doing a firmware upgrade to a localized firmware, it is of course possible to just accept having a generic world firmware, and to just set the language of your hardware keyboard (see this guide here: http://forum.xda-developers.com/showthread.php?t=1224511 )
(below is the original post)
Hi,
is there any way to fool my Xperia Mini Pro (or PC Companion) into thinking it should be a generic French phone instead of a Mobistar Branded one?
I'm fed up with waiting for an update to .58 while everyone else has got it, and I'm not willing (at this time) to unlock the bootloader in order to flash with flashtool.
Maybe there's a text file somewhere that can be edited so the phone thinks it's an unbranded one?
My phone:
Belgium - Mobistar branded:
ro.product.name=SK17i_1250-5673;
ro.build.fingerprint=SEMC/SK17i_1250-5673/SK17i:2.3.3/4.0.A.2.335/sPb_3w:user/release-keys
EDIT: changed into 1251-0622 which should be generic french...
Click to expand...
Click to collapse
dryhte said:
Hi,
is there any way to fool my Xperia Mini Pro (or PC Companion) into thinking it should be a generic French phone instead of a Mobistar Branded one?
I'm fed up with waiting for an update to .58 while everyone else has got it, and I'm not willing (at this time) to unlock the bootloader in order to flash with flashtool.
Maybe there's a text file somewhere that can be edited so the phone thinks it's an unbranded one?
Click to expand...
Click to collapse
Use wotanserver!
Gustavo RD78 said:
Use wotanserver!
Click to expand...
Click to collapse
Hi. As the mate writes upstairs, this one is a solution.
There's another one. It worked in X10 Eclair times.
Try editing your build.prop file. Look in /system/build.prop.
Open it with RootExplorer and edit ro.semc.version.cust=xxxx-xxxx and ro.product.name=WT19i_xxxx-xxxx where x are your region firmware brand.Mine is 1254-1854, German.
Then edit the ro.semc.version.cust=xxxx-xxxx file in /system/etc/customization/settings/cust.prop
Save and exit for every file you modded.
Reboot your phone. Turn off and use SEUS.
I hope it works
Peppoid said:
Hi. As the mate writes upstairs, this one is a solution.
There's another one. It worked in X10 Eclair times.
Try editing your build.prop file. Look in /system/build.prop.
Open it with RootExplorer and edit ro.semc.version.cust=xxxx-xxxx and ro.product.name=WT19i_xxxx-xxxx where x are your region firmware brand.Mine is 1254-1854, German.
Then edit the ro.semc.version.cust=xxxx-xxxx file in /system/etc/customization/settings/cust.prop
Save and exit for every file you modded.
Reboot your phone. Turn off and use SEUS.
I hope it works
Click to expand...
Click to collapse
Only dont put WT19i because then you will recieve the WT19i update
dumraden said:
Only dont put WT19i because then you will recieve the WT19i update
Click to expand...
Click to collapse
Lol
Don't worry, in your build.prop will be the right device written
If this should work, we could open a thread like that
Peppoid said:
Hi. As the mate writes upstairs, this one is a solution.
There's another one. It worked in X10 Eclair times.
Try editing your build.prop file. Look in /system/build.prop.
Open it with RootExplorer and edit ro.semc.version.cust=xxxx-xxxx and ro.product.name=WT19i_xxxx-xxxx where x are your region firmware brand.Mine is 1254-1854, German.
Then edit the ro.semc.version.cust=xxxx-xxxx file in /system/etc/customization/settings/cust.prop
Save and exit for every file you modded.
Reboot your phone. Turn off and use SEUS.
I hope it works
Click to expand...
Click to collapse
Ok, so:
Code:
Belgium: Mobistar branded:
ro.product.name=SK17i_1250-5673;
ro.build.fingerprint=SEMC/SK17i_1250-5673/SK17i:2.3.3/4.0.A.2.335/sPb_3w:user/release-keys
EDIT: Since I couldn't find any other product names around, I decided to give Wotanserver a try... however, upon downloading the client, it continually tells me it's old and needs to update. Anyone around who used it before?
oh, and by the way, if anyone has a non-mobistar belgian AZERTY mini pro (with .58 firmware), please share your region code with me I'd love to have normal OTA updates working...
dryhte said:
Ok, so:
Code:
Belgium: Mobistar branded:
ro.product.name=SK17i_1250-5673;
ro.build.fingerprint=SEMC/SK17i_1250-5673/SK17i:2.3.3/4.0.A.2.335/sPb_3w:user/release-keys
EDIT: Since I couldn't find any other product names around, I decided to give Wotanserver a try... however, upon downloading the client, it continually tells me it's old and needs to update. Anyone around who used it before?
oh, and by the way, if anyone has a non-mobistar belgian AZERTY mini pro (with .58 firmware), please share your region code with me I'd love to have normal OTA updates working...
Click to expand...
Click to collapse
Hope it works. Give a try.
Bye
Peppoid said:
...
Hope it works. Give a try.
Bye
Click to expand...
Click to collapse
Peppoid, I don't think that will work unless you phone is specifically Belgian? (you don't have a SK17 either)
I don't want to end up with a QWERTY layout instead of my AZERTY keyboard... (I know I should have chosen a QWERTY phone instead, but hey, 70€ cheaper tickled my fancy )
I have a belgian Mini too (sk15i), it's unbranded and the software version is also .42 and not .58!
I think the software update is just not released for our region.
Crossing my fingers now... I found that 1251-0622 is generic french; I updated all occurrences of the location code in build.prop and now SEUS is downloading an update. We'll soon know if the azerty for FR is the same as for BE And we know now that editing build.prop works if we want to fool SEUS into thinking we're in another region.
Well, it worked so now let's start and compile a list of region codes known to work! If you reply to this post with your region code and hardware keyboard layout (QWERTY/QWERTZ/AZERTY/DVORAK ) I'll add them to the first post!
LOL - nobody interested in building this list? It's an additional way of getting newer firmwares on your phone B-) apparently this was quite a popular topic in the Xperia X10 forum...
Sent from my SK17i using XDA App
X10 who?
Hey, nice job!
I'd love to get the code for the Latin America region.
What's the difference of updating with SEUS and PC Companion?
Thanks!
tianGO said:
Hey, nice job!
I'd love to get the code for the Latin America region.
Click to expand...
Click to collapse
Maybe someone is so good to share it with us
tianGO said:
What's the difference of updating with SEUS and PC Companion?
Click to expand...
Click to collapse
My guess is that it should be exactly the same... Except that seus does nothing else than updates/restores whereas pcc tries to be everything to everyone ;-)
Sent from my SK17i using XDA App
Hey,
after long searching i'm glad to have found this post. I also have a branded phone of Mobistar and still stuck on 4.0.A.2.335 and i've tried everything described in this post, but i'm unable to succeed...
Things i've done:
- rooted my phone with Root / Unroot Sony Ericsson Xperia 2011 v1.5 (http://forum.xda-developers.com/showthread.php?t=1346198)
- installed ES File explorer and located the build.prop file
but i can't save the file and i'm unable to change the file permissions.
Can anyone help and tell me what i've done wrong???
Many thx in advance
fredgoddeeris said:
Hey,
after long searching i'm glad to have found this post. I also have a branded phone of Mobistar and still stuck on 4.0.A.2.335 and i've tried everything described in this post, but i'm unable to succeed...
Things i've done:
- rooted my phone with Root / Unroot Sony Ericsson Xperia 2011 v1.5 (http://forum.xda-developers.com/showthread.php?t=1346198)
- installed ES File explorer and located the build.prop file
but i can't save the file and i'm unable to change the file permissions.
Can anyone help and tell me what i've done wrong???
Many thx in advance
Click to expand...
Click to collapse
I'm at work atm so can't go into too much detail, but what I did is:
- copy the build.prop file with es file explorer to my sd card
- edit it while connected to my pc & save
- make sure my es file explorer has root access (check settings, maybe there's a flag that must be set first)
- copy back the build.prop file (I didn't change any file permissions IIRC)
dryhte said:
I'm at work atm so can't go into too much detail, but what I did is:
- copy the build.prop file with es file explorer to my sd card
- edit it while connected to my pc & save
- make sure my es file explorer has root access (check settings, maybe there's a flag that must be set first)
- copy back the build.prop file (I didn't change any file permissions IIRC)
Click to expand...
Click to collapse
THX SO MUCH !!!!
was finally able to update
stupid Mobistar...
fredgoddeeris said:
THX SO MUCH !!!!
was finally able to update
stupid Mobistar...
Click to expand...
Click to collapse
;-)
Sent from my SK17i using XDA App
Hi,
as I promised (but with some delay )
hope it will help you.
'cause I'm not really sure what you're trying to achieve. Could you maybe explain it one more time?
swimon said:
Hi,
as I promised (but with some delay )
hope it will help you.
'cause I'm not really sure what you're trying to achieve. Could you maybe explain it one more time?
Click to expand...
Click to collapse
Okay, so if you edit this build.prop file (and just change the CDA code, in your case 1254-0468, to another existing SK17I code) you can fool SEUS into thinking that you have a phone from another region or operator, and give you another firmware than you would've gotten, or even give you an update even while none was available for you. Not useful for you, but very useful for people with a branded phone like me, who want to debrand or just update it.
Sent from my SK17i using XDA App
All credit to alcaloide_
I have test his files ... and this systemui.apk work on all JB roms ( tested on SFR - Orange - Retail BR - O2 - Telstra... )
Work great with no glitch and FC ! ( Retail BR systemui.apk don't have carrier but i get some FC with others roms )
Just want post here because if a people want it ... is very difficult to see ... and i have tested for you on all roms
Thanks again to alcaloide_
http://forum.xda-developers.com/showpost.php?p=35808008&postcount=31
Thank you !!!! work fine on o2 Jelly Bean
Thank you, works perfectly.
Does anyone wants to share a systemUI.apk which includes the 1% battery mod, please.
I will even donate
dan.steck said:
Thank you, works perfectly.
Does anyone wants to share a systemUI.apk which includes the 1% battery mod, please.
I will even donate
Click to expand...
Click to collapse
You can try mine, 1% battery mod with the carrier removed from notification bar - stock Rogers JB odexed 4.1.2.
thanks heaps, but I think I need the .odex file too; I've tried yours and no go.
forgot to mention I have a xt925 telstra stock 4.1.2
I'm not too lazy to at least try and do it myself, just "married...with children" and a 10h/day job, that's why I'm willing to pay someone...
thank you
dan.steck said:
thanks heaps, but I think I need the .odex file too; I've tried yours and no go.
forgot to mention I have a xt925 telstra stock 4.1.2
I'm not too lazy to at least try and do it myself, just "married...with children" and a 10h/day job, that's why I'm willing to pay someone...
thank you
Click to expand...
Click to collapse
No problems,
Here's the SystemUI.odex from my Rogers 4.1.2 if you want to give it a try (zipped).
There's a few other systemUI's floating around that seemed to work well for others but nothing that worked with my stock Rogers Rom, not sure why so I made this one up more to rid of the irritating carrier name in the notification bar.
thank you, appreciate it, but doesn't seem to work(status bar & buttons dissapear + wallpaper reverts to the original one)
So I also tried it. Stock.. rooted.. unlocked boot loader.. Rogers ROM but I lose my shortcuts n my status bar. Any help ?
Sent from my XT925 using xda premium
finally found one that works on my xt925 stock telstra 4.1.2, with no carrier in status bar and 1% battery.
i've replaced the pngs with some that I've been using previously with BuglessBeast Rom on my old gnex (I don't know the original author to give credit)
it is supposed to work with european carriers too
o2qc418 said:
All credit to alcaloide_
I have test his files ... and this systemui.apk work on all JB roms ( tested on SFR - Orange - Retail BR - O2 - Telstra... )
Work great with no glitch and FC ! ( Retail BR systemui.apk don't have carrier but i get some FC with others roms )
Just want post here because if a people want it ... is very difficult to see ... and i have tested for you on all roms
Thanks again to alcaloide_
http://forum.xda-developers.com/showpost.php?p=35808008&postcount=31
Click to expand...
Click to collapse
Hello,
I'm currently trying to make No carrier mod too, I succeed to do the 1% mod, but I don't know where to search for carrier...
Could you help me ? I deodexed my ROM, and I can decompile/compile it .
Edit : I finally found myself by decompiling your APK, thank you
Thank you.
Best regards
dan.steck said:
finally found one that works on my xt925 stock telstra 4.1.2, with no carrier in status bar and 1% battery.
i've replaced the pngs with some that I've been using previously with BuglessBeast Rom on my old gnex (I don't know the original author to give credit)
it is supposed to work with european carriers too
Click to expand...
Click to collapse
Thanks, I'm on Telstra too but quick question, how do I install, I've unzipped it but I don't see the apk file?
Cheers
Thanks!!
Im on CEE 4.1.2, and works great!
just delete the .zip extension. I've uploaded from an windows laptop and did not noticed in explorer the double extension
to install it: you need a file manager with root capabiliyies to copy it to /system/app, make sure has the same permissions as the other files.
tip: first rename the existing systemui.apk to something else, just in case you get problems with the new one and want to revert to the original
Sent from my XT925 using xda premium
that crashed my GUI, anyone can confirm which one works on stock fido 4.1.2? :laugh:
dan.steck said:
just delete the .zip extension. I've uploaded from an windows laptop and did not noticed in explorer the double extension
to install it: you need a file manager with root capabiliyies to copy it to /system/app, make sure has the same permissions as the other files.
tip: first rename the existing systemui.apk to something else, just in case you get problems with the new one and want to revert to the original
Sent from my XT925 using xda premium
Click to expand...
Click to collapse
Here with my systemui BR version also doesnt work
I had fc and nothing resolves...
Somebody can help me?
-----------------------------------------------
Sorry, but my system isn't deodexed... and now I tried to do that, but without success
My phone doesn't boot up... What can I make?
tankrider said:
You can try mine, 1% battery mod with the carrier removed from notification bar - stock Rogers JB odexed 4.1.2.
Click to expand...
Click to collapse
I'm also with Rogers firmware, and using this file I got rid of the carrier but still no 1% mod on the battery
Any idea what might be wrong, or could you maybe check with your phone if this file does indeed have the % mod please? Thank you...
Here with my systemui BR version also doesnt work
I had fc and nothing resolves...
Somebody can help me?
-----------------------------------------------
Sorry, but my system isn't deodexed... and now I tried to do that, but without success
My phone doesn't boot up... What can I make?
----------------------------------------------
HEEEEEEEEEEELP ME GUYS
Why doesn't work with me???
dan.steck said:
finally found one that works on my xt925 stock telstra 4.1.2, with no carrier in status bar and 1% battery.
i've replaced the pngs with some that I've been using previously with BuglessBeast Rom on my old gnex (I don't know the original author to give credit)
it is supposed to work with european carriers too
Click to expand...
Click to collapse
Can someone teach me how to do this? I'm on ics still
Sent from my XT925
system interface disappeared when rebooted.
Orphee said:
Hello,
I'm currently trying to make No carrier mod too, I succeed to do the 1% mod, but I don't know where to search for carrier...
Could you help me ? I deodexed my ROM, and I can decompile/compile it .
Edit : I finally found myself by decompiling your APK, thank you
Thank you.
Best regards
Click to expand...
Click to collapse
Can you upload it for me? As I recall, you're also on Telstra.
Hi all,
Thanks to a forum member on my home forum, who found some information from the Russian 4PDA forum, I would like to post the findings here for English speaking users.
NOTE: THIS IS MEANT FOR 501L devices with B002 or B003 ROMS, as they do not have many features from the 501u and 503L devices
I currently have a 7D-501L from Malaysia (updated to Western Europe B003 ROM) and have successfully tested the following:
You may first need to rename the file "setimmutable.list" to something else otherwise build.prop changes may not be permanent.
/system/build.prop
On Gloves - mode
Append: ro.config.hw_glovemode_enabled = 1
On muting the shutter sound option in the camera
Append: ro.hwcamera.sound.muteable = true
This setting needs to be changed at /data/cust/prop/local.prop
When saving, the charset needs to be set to GBK otherwise you will brick your phone.
#ro.config.ShowNavigationBar=true <=add "#" to comment out the original line, then add the 2 lines below.
ro.config.hw_shownavisettings=true
ro.config.hw_navigationbar=true
Link to the post on my home forum:
https://forum.lowyat.net/index.php?showtopic=3280093&view=findpost&p=69302439
I have also managed to install Xposed framework successfully and GravityBox is working fine.
joytest said:
Hi all,
Thanks to a forum member on my home forum, who found some information from the Russian 4PDA forum, I would like to post the findings here for English speaking users.
I currently have a 7D-501L from Malaysia and have successfully tested the following:
/system/build.prop
On Gloves - mode
Append: ro.config.hw_glovemode_enabled = 1
On muting the shutter sound option in the camera
Append: ro.hwcamera.sound.muteable = true
This setting needs to be changed at /data/cust/prop/local.prop
When saving, the charset needs to be set to GBK otherwise you will brick your phone.
#ro.config.ShowNavigationBar=true <=add "#" to comment out the original line, then add the 2 lines below.
ro.config.hw_shownavisettings=true
ro.config.hw_navigationbar=true
Link to the post on my home forum:
https://forum.lowyat.net/index.php?showtopic=3280093&view=findpost&p=69302439
Click to expand...
Click to collapse
hi i m from malaysia too. just got this device a few days earlier. however i failed to edit the build.prop file as well as /data/cust/prop/local.prop.
with root explorer. i m not sure what went wrong and hopefully u could guide me on this. thank u.
Hey man,
there already has these options in the phone settings.
Useless to play with this sensitive file
Jcc13 said:
Hey man,
there already has these options in the phone settings.
Useless to play with this sensitive file
Click to expand...
Click to collapse
Hi, these settings are not available in version B002 for the 501L which is why we have to do it manually
Sent from my SM-N9005 using Tapatalk
neurosis130 said:
hi i m from malaysia too. just got this device a few days earlier. however i failed to edit the build.prop file as well as /data/cust/prop/local.prop.
with root explorer. i m not sure what went wrong and hopefully u could guide me on this. thank u.
Click to expand...
Click to collapse
You need to rename the file setimmutable.list to something else.
Then change the properties of build.prop and local.prop to -rwrwrwx- or 777 using some root-aware file explorer.
Make the changes with a text editor, remembering to save it in the same Encoding as the original.
Then revert the properties back to -rw-r-rx- or something, I can't recall, but you can see it from the file explorer. I use Solid Explorer which is awfully handy.
joytest said:
Hi, these settings are not available in version B002 for the 501L which is why we have to do it manually
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Ok, that all right, i didn't know. :good:
joytest said:
Hi all,
Thanks to a forum member on my home forum, who found some information from the Russian 4PDA forum, I would like to post the findings here for English speaking users.
I currently have a 7D-501L from Malaysia and have successfully tested the following:
This setting needs to be changed at /data/cust/prop/local.prop
When saving, the charset needs to be set to GBK otherwise you will brick your phone.
#ro.config.ShowNavigationBar=true <=add "#" to comment out the original line, then add the 2 lines below.
ro.config.hw_shownavisettings=true
ro.config.hw_navigationbar=true
Link to the post on my home forum:
https://forum.lowyat.net/index.php?showtopic=3280093&view=findpost&p=69302439
Click to expand...
Click to collapse
Thanks! Working great with 7D-501L B003
joytest said:
You need to rename the file setimmutable.list to something else.
Then change the properties of build.prop and local.prop to -rwrwrwx- or 777 using some root-aware file explorer.
Make the changes with a text editor, remembering to save it in the same Encoding as the original.
Then revert the properties back to -rw-r-rx- or something, I can't recall, but you can see it from the file explorer. I use Solid Explorer which is awfully handy.
Click to expand...
Click to collapse
finally done .this is so different with my honor 2.but at least able to learn something .thank u so much for ur help .
tulikirnu said:
Thanks! Working great with 7D-501L B003
Click to expand...
Click to collapse
I have installed Xposed with GravityBox and the rotate lockscreen feature works fine.
Xposed
joytest said:
I have installed Xposed with GravityBox and the rotate lockscreen feature works fine.
Click to expand...
Click to collapse
1/ Do you need to be Rooted in order to install Xposed ?
2/ What another Xposed modules have you installed which work fine ?
lvpl said:
1/ Do you need to be Rooted in order to install Xposed ?
2/ What another Xposed modules have you installed which work fine ?
Click to expand...
Click to collapse
Yes you MUST be rooted to install Xposed.
I installed Dimensions Editor and Play Permissions. Both work nicely.
The navbar and app titlebards are much smaller now and I don't even need to hide the navbar much.