Related
Mar 14th : 2002304 version Fixed work fine for me on 2.1 stock ROM.
only 964×544 faked Res
maybe you will need an other version if you run on a Custom Mod, post below if it worked or not for you ad which rom
WORK FOR MINI & PRO (and maybe others phones)
Here are the Versions :
2002306 (2.3.6) 544×964 faked Res teapea's work (thanks him) : http://www.megaupload.com/?d=STR8DHKW
---------------------------------------------------------------------------------------
To use older version : delete or rename marketupdater.apk
2002304 544×964 faked Res version: WORKING
Code:
http://www.megaupload.com/?d=L18MP8HY
signed 2002304 544×964 faked Res version: report as working
Code:
http://www.megaupload.com/?d=570LCOE0
the both versions are reported as WORKING on 2.1 stock ROM, I can't know if they work on any custom mod untill you confirm it.
******************************************************
floyo's custom mod this one WORKING :
http://www.megaupload.com/?d=WAPZVYD8
*****************************************************
giggleBread provided by ctalcant
http://www.megaupload.com/?d=S05I08YH NOT TESTED
http://www.megaupload.com/?d=GSEOQVMQ (signed version) NOT TESTED
compare results before and after and please reports below
************************************************************
here the old one (2002013) for those who hate the new userInterface (don't forget to delete/move marketupdater.apk
Code:
unsigned 2002013 version :TESTED/WORKING
http://www.megaupload.com/?d=19JB1BK2
http://www.mediafire.com/?aep26ecp55184rj
signed version 2002013: NOT TESTED
http://www.megaupload.com/?d=TXBQYD80
http://www.mediafire.com/?ssszch5r6as27r8
How to :
0- download and put the file on your sdcard, unmount your sdcard
0.5 - rename it "com.android.vending.shokmah.apk" (without the quotes)
1-activate FlightMode
2-goto settings > applications > manage applications > [menu bouton] filter > all
2.5 - select market then uninstall update, and force stop
3- activate usb debugging and launch adb on your computer then type these line
Code:
adb shell
su
mount -o rw,remount /dev/block/mtdblock0 /system
cat /system/app/Vending.apk > /sdcard/Vending.bkp.apk
rm /system/app/Vending.apk
rm -r /data/data/com.android.vending
rm /data/dalvik-cache/[email protected]@[email protected]
cat /sdcard/com.android.vending.shokmah.apk > /system/app/Vending.apk
For rm /data/dalvik-cache/[email protected]@[email protected] don't pay attention if you got an error !
If you found "adfree android" or 3544 (or +) results for video , it's worked.
If you want to thanks me, just choose the megaupload link.
Greetz:
Inteks for the old version
Orion for His Easy APK Disassembler
and what exactly are the benefits with this version compared to that one: showthread.php?t=742608
or that one: showthread.php?t=645286&highlight=market
i still dont know why it keeps saying, that im not allowed to "post outside links" when i write a link to another topic...
I dont know but inteks's version was "erased" by market updater so I take the update and Fake the resolution.
New users Are not allowed to post links
that's why I put mine with code "tag"
sorry for the english
Thanks, but there is no com.android.vending.apk in /system/app. Do you mean Vending.apk?
yes, mine disapearred after some tests, then I push it to com.android.vending.apk and it work well.
User report me that with Vending.Apk name it also work.
It works great! Can confirm it's the new version 2002012.
Thanks shokmah
Thanks for this shokmah!!
Whats the difference? ive done the patch, but i dont see any different...
I don't know the entire difference Between the Stock original One, but It may add new features such as Instant search, apk auto-update option, and many others features.
The patched version allow you to view app which require 320×480 screen Display, some of theses apps work great on our 240×320 screen Display.
I may add support for greater Screen resolution but more you Increase Resolution, More unlocked app will not work smoothly.
Sorry for the english, it's not my native language !
EDIT :
to verify if it work :
search for adfree android and you should found the app
search for video you should have 3544 found result
thanks a lot!
Now I can download "adfree android" app, but "video" string result get 2202 result..
ps: Xperia X10 mini pro, and 2.1
maybe it's different for other , I've french market
Worked for me
Thanks!
you know it works if you search "video" and see results for "video ringtones"
"video ringtones" : 46 matches
Thanks. Worked for me.
When i search "video", i get 3368 results.
How can i prevent the market from getting self-updated in the future? I dont want to disable the data traffic for ever
simplest way to hack the market is here by me..http://bit.ly/9E3Bii
Root explorer's way seem to be simplest way , but adb's way is powerful and completely free and normaly you should pay for RoOt Explorer .
@MonteChristo1979 : you have to delete marketupdater.apk in /system/app, for new update I or Someone will post a patched Vending.apk again
the market is not the problem ! its the marketupdater !!! delete it and everything is fine
badboybiky said:
simplest way to hack the market is here by me..http://bit.ly/9E3Bii
Click to expand...
Click to collapse
nope ! the simplest way you get here ->> http://forum.xda-developers.com/showthread.php?t=845130
wow, YOu made an awesome work, a GUI for those who are affraid of command lines is Great.
Q&A for [GUIDE][LINUX][MIUI] MIUI PatchROM -- BUILD YOUR OWN MIUI ROM
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GUIDE][LINUX][MIUI] MIUI PatchROM -- BUILD YOUR OWN MIUI ROM. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
[MIUI PATCHROM for WALTON PrimoF2[How to solve this??Please somebody help me...
Code:
[email protected]:~$ cd patchrom
[email protected]:~/patchrom$ . build/envsetup.sh
PATCHROM_BRANCH = jellybean42-mtk
ANDROID_PLATFORM = v17
PORT_ROOT = /home/atiq/patchrom
ANDROID_TOP =
ANDROID_OUT =
PORT_PRODUCT = Unknown
USE_ANDROID_OUT =
ANDROID_BRANCH =
[email protected]:~/patchrom$ cd primof2
bash: cd: primof2: No such file or directory
[email protected]:~/patchrom$ mkdir primof2
[email protected]:~/patchrom$ cd primof2
[email protected]:~/patchrom/primof2$ /home/atiq/patchrom/tools/releasetools/ota_target_from_phone -n
Wait for the device to be online...
Copy target file template into current working directory
Warning: the ota package will not contain bootimage!!!
Maybe you forget to pass the ota-package parameter.
Are you sure this is really what you want(yes/no):yes
Build recovery.fstab from device
Extract the whole /system from device
pull: building file list...
1423 files pulled. 0 files skipped.
2943 KB/s (570754099 bytes in 189.331s)
Remount /system to be writable
You don't have a rooted kernel. Please run the following command mannually
(1) adb shell
(2) su
(3) mount -o remount,rw /[email protected] /system
(3) chmod 0777 /system /system/*
If you finish running the above commands on your phone(yes/no):yes
/system/xbin/getfilesysteminfo: No such file or directory
Run getfilesysteminfo to build filesystem_config.txt
125 KB/s (5572 bytes in 0.043s)
Run getfilesysteminfo and recoverylink.py to recover symlink
Recovery link files success
Build apkcerts.txt
failed to copy '/data/system/packages.xml' to '/home/atiq/patchrom/primof2/out/target_files/packages.xml': Permission denied
Error: /home/atiq/patchrom/primof2/out/target_files/packages.xml doesn't exist or isn't a vaild xml file
rm: cannot remove ‘/home/atiq/patchrom/primof2/out/target_files/packages.xml’: No such file or directory
Generate metadata used to build target files...
Compress the target_files dir into zip file
/home/atiq/patchrom/primof2
Build full ota package: /home/atiq/patchrom/primof2/stockrom.zip
unzipping target target-files...
using device-specific extensions in .
unable to load device-specific module; assuming none
[MIUI CUST] OTA: copy data files
[MIUI CUST] OTA: handle relink
[MIUI CUST] OTA: SetPermissions
Picked up JAVA_TOOL_OPTIONS: -javaagent:/usr/share/java/jayatanaag.jar
done.
[email protected]:~/patchrom/primof2$
Where should I put the bellow commands
Code:
You don't have a rooted kernel. Please run the following command mannually
(1) adb shell
(2) su
(3) mount -o remount,rw /[email protected] /system
(3) chmod 0777 /system /system/*
If you finish running the above commands on your phone(yes/no):
here?? After this line?? Here I have only two option to input "yes" or "no" in this shell. Otherwise it shows too many arguments. Please tell me where to put those commands exactly?? another question: Is everything OK there except "packages.xml". I manually copied the packages.xml file from my device and paste it to target_files then zipped it. Will it work?? Please help..
Anyone here successfully booted miui 8 on MTK 32 bit kernel 3.18.19 can help me with bootloop!?
I already built the rom based on AOSP android one but it bootloops
Mysteryagr said:
Anyone here successfully booted miui 8 on MTK 32 bit kernel 3.18.19 can help me with bootloop!?
I already built the rom based on AOSP android one but it bootloops
Click to expand...
Click to collapse
Hook it up and run a log at on your pc. That will tell you what is bootlooping. It that should have been the first hinges you did. It is rom building basics
zelendel said:
Hook it up and run a log at on your pc. That will tell you what is bootlooping. It that should have been the first hinges you did. It is rom building basics
Click to expand...
Click to collapse
Thank you for your reply.
I already did that, and yes I edited defualt.prop inside the ramdisk to enable logcat during bootloop.
I have ported many roms, and also built some from source, and I noticed that I can only take logcat in bootloop if the rom is partially booted, notification led lights in red as a sign of that.
In Miui case the led doesn't light up, also I noticed that no space occupied in data partition (except for the extracted miui apps)
So I guess something prevent the rom to start and optimize any app, maybe it is the boot.img
If someone booted miui on MTK 32 bit chipset and MM kernel 3.18.19 can help me, I will be very thankful.
My device is Infinix Hot 2 running Android one 6.0 marshmallow, chipset: MT6580
Thanks in advance.
Mysteryagr said:
Thank you for your reply.
I already did that, and yes I edited defualt.prop inside the ramdisk to enable logcat during bootloop.
I have ported many roms, and also built some from source, and I noticed that I can only take logcat in bootloop if the rom is partially booted, notification led lights in red as a sign of that.
In Miui case the led doesn't light up, also I noticed that no space occupied in data partition (except for the extracted miui apps)
So I guess something prevent the rom to start and optimize any app, maybe it is the boot.img
If someone booted miui on MTK 32 bit chipset and MM kernel 3.18.19 can help me, I will be very thankful.
My device is Infinix Hot 2 running Android one 6.0 marshmallow, chipset: MT6580
Thanks in advance.
Click to expand...
Click to collapse
To be honest I have no other ideas. Devices with that chip maker are not sold in my country.
@zelendel
What is the difference between
make firstpatch
Click to expand...
Click to collapse
and
make second patch
Click to expand...
Click to collapse
?
Mysteryagr said:
@zelendel
What is the difference between
and
?
Click to expand...
Click to collapse
I don't know. To be honest I wouldn't touch miui with a 10 foot pole personally.
Thanks to @HypoTurtle for providing the .img files!
Root privilege allows users to download and use apps such as Titanium Backup. It also allows easier modification of settings.
I thought some of you would like a step-by-step to root the most recent .403 Remix OS. I have tried here to put together a procedure that even new members can follow. Please let me know how it works for you.
PLEASE REMEMBER THAT MESSING AROUND MIGHT RESULT IN PROBLEMS IF YOU DO NOT FOLLOW INSTRUCTIONS EXACTLY.
This is only for 64 bit. Please note that you MUST type all command line commands Exactly as shown (including spaces and caps)
To root you will need only two files: one is a modified ramdisk.img that you will install while in Windows; and one is a superuser su.img to add to the data partition from the Remix OS command line.
1 First, if you haven't already, download and install Remix OS Version .403 from their website. Go through the complete installation.
2 Next, from Windows, using your favorite browser, download ramdisk-403.img and su.img from:
https://drive.google.com/folderview?id=0B3gcDbDvV4MkVWRxU3pYMzVUWEU
3 To substitute the new ramdisk.img:
a Open the File Explorer and copy the ramdisk-403.img file.
b From the File Explorer, click on the Drive with your Remix OS.You will see a "RemixOS" folder.
c Click on it to open it. Now you should see the files including one named ramdisk.img.
d Click on the ramdisk.img and select rename the ramdisk.img to ramdiskorig.img to save it "just in case"
e Now rename the ramdisk-403.img to ramdisk.img
4 To finish you need to restart and boot into Remix OS.
a First thing to do in Remix is go to Settings/Experimental features/Enable terminal debug console and activate it.
b Open the File Manager and click on the Disk with Windows installed (usually Disk 1 or Disk 2)
c Click on "Users" and then on your user ID folder
d Find the "Downloads" folder and click on it. You should see the su.img that you downloaded while in Windows
e Click on the su.img file and drag it to the Download folder on the left. It will copy the su.img to your Download folder
5 Now you are ready to copy the su.img into your /data partition.
a Press ALT&F1 to open the command line. You should see a line of text with the # symbol.
b To copy su.img into /data, at the command line type: cp /data/media/0/Download/su.img /data/su.img
c Note that there are spaces ONLY after cp and img
d Press ENTER. If you receive no error message then you did it correctly.
Press ALT&F7 to leave the command line. Play it safe and reboot. You now can download and run any app that requires root access.
Set to go! Have fun. Let me know how it works for you.
Working
Works with 402???
My WiFi didn't broke with 402, so I'll not upgrade to 403...
Regnas said:
Works with 402???
My WiFi didn't broke with 402, so I'll not upgrade to 403...
Click to expand...
Click to collapse
Not sure. My wifi was broken with 402 and 403 fixed it. Whattaworld!
lollyjay said:
Not sure. My wifi was broken with 402 and 403 fixed it. Whattaworld!
Click to expand...
Click to collapse
Yeah, it's funny...
Anyway,I'll try that later..
Cheers..
lollyjay said:
Not sure. My wifi was broken with 402 and 403 fixed it. Whattaworld!
Click to expand...
Click to collapse
Any chance you have an lsmod from both. I know the issue in 402 was that both wl and b43 were both loaded - it might be viable to create a broadcom switch to flick between the two [one's proprietary and the other is open-source]
HypoTurtle said:
Any chance you have an lsmod from both. I know the issue in 402 was that both wl and b43 were both loaded - it might be viable to create a broadcom switch to flick between the two [one's proprietary and the other is open-source]
Click to expand...
Click to collapse
Yes, do you just want an lsmod output or do you want more specific?
lollyjay said:
Yes, do you just want an lsmod output or do you want more specific?
Click to expand...
Click to collapse
Both outputs or a diff 402-dmesg 403-dmesg > 402-403_diff would be fine. For some reason I'm still on 402 -- haven't gotten the 403 ota yet.
HypoTurtle said:
Both outputs or a diff 402-dmesg 403-dmesg > 402-403_diff would be fine. For some reason I'm still on 402 -- haven't gotten the 403 ota yet.
Click to expand...
Click to collapse
I don't have 402 any more. Here is one from 403. Maybe @Regnas can give you the other.
Module Size Used by Tainted: P
binfmt_misc 9163 1
hid_sensor_als 4217 0
hid_sensor_incl_3d 4947 0
hid_sensor_accel_3d 4768 2
hid_sensor_rotation 4683 0
hid_sensor_magn_3d 5925 0
hid_sensor_gyro_3d 4755 0
hid_sensor_trigger 3417 12 hid_sensor_als,hid_sensor_incl_3d,hid_sensor_accel_3d,hid_sensor_rotation,hid_sensor_magn_3d,hid_sensor_gyro_3d
industrialio_triggered_buffer 1874 6 hid_sensor_als,hid_sensor_incl_3d,hid_sensor_accel_3d,hid_sensor_rotation,hid_sensor_magn_3d,hid_sensor_gyro_3d
kfifo_buf 3374 1 industrialio_triggered_buffer
industrialio 45973 11 hid_sensor_als,hid_sensor_incl_3d,hid_sensor_accel_3d,hid_sensor_rotation,hid_sensor_magn_3d,hid_sensor_gyro_3d,hid_sensor_trigger,industrialio_triggered_buffer,kfifo_buf
hid_sensor_iio_common 5514 7 hid_sensor_als,hid_sensor_incl_3d,hid_sensor_accel_3d,hid_sensor_rotation,hid_sensor_magn_3d,hid_sensor_gyro_3d,hid_sensor_trigger
hid_sensor_custom 9846 0
rtsx_pci_ms 8248 0
memstick 9812 1 rtsx_pci_ms
rtsx_pci_sdmmc 15489 0
mac_hid 3843 0
bsd_comp 4698 0
ppp_deflate 3798 0
ppp_async 6285 0
pppoe 8725 0
pppox 2638 1 pppoe
ppp_generic 22934 5 bsd_comp,ppp_deflate,ppp_async,pppoe,pppox
slhc 5081 1 ppp_generic
wmi 8736 0
wl 6426390 0
cfg80211 477899 1 wl
uvcvideo 66519 1
snd_hda_codec_hdmi 38342 1
videobuf2_vmalloc 4693 1 uvcvideo
videobuf2_memops 2716 1 videobuf2_vmalloc
videobuf2_v4l2 19150 1 uvcvideo
videobuf2_core 21313 2 uvcvideo,videobuf2_v4l2
snd_hda_codec_realtek 67326 1
snd_hda_codec_generic 53744 1 snd_hda_codec_realtek
thinkpad_acpi 66626 1
nvram 6533 1 thinkpad_acpi
soc_button_array 2418 0
snd_hda_intel 28041 1
snd_hda_codec 105597 4 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_codec_generic,snd_hda_intel
snd_hda_core 53903 5 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_codec_generic,snd_hda_intel,snd_hda_codec
snd_hwdep 5785 1 snd_hda_codec
snd_pcm 87019 5 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core
snd_timer 20488 1 snd_pcm
snd 65356 9 snd_hda_codec_hdmi,snd_hda_codec_generic,thinkpad_acpi,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
soundcore 6615 1 snd
shpchp 23487 0
rtsx_pci 41858 2 rtsx_pci_ms,rtsx_pci_sdmmc
r8169 61453 0
mii 4910 1 r8169
psmouse 101828 0
pcspkr 2158 0
lpc_ich 14290 0
intel_rst 2468 0
i915 1084918 9
drm_kms_helper 108824 1 i915
drm 311256 11 i915,drm_kms_helper
fb_sys_fops 1759 1 drm_kms_helper
syscopyarea 3185 1 drm_kms_helper
sysfillrect 3485 1 drm_kms_helper
sysimgblt 2562 1 drm_kms_helper
i2c_algo_bit 5421 1 i915
i2c_i801 16755 0
hid_sensor_hub 11145 9 hid_sensor_als,hid_sensor_incl_3d,hid_sensor_accel_3d,hid_sensor_rotation,hid_sensor_magn_3d,hid_sensor_gyro_3d,hid_sensor_trigger,hid_sensor_iio_common,hid_sensor_custom
hid_multitouch 10208 0
coretemp 6156 0
hwmon 4404 2 thinkpad_acpi,coretemp
btusb 31833 0
btrtl 4762 1 btusb
btbcm 7000 1 btusb
btintel 8387 1 btusb
bluetooth 444084 9 btusb,btrtl,btbcm,btintel
Sent from my on Z00A using XDA Labs
Hi @lollyjay, the method is simple and easy and is working great....Thanks a lot for that.....But how do we enable system r/w because it did not let me edit build.prop to enable brigntness slider... in earlier version I used modified initrd.img....it there any other way to achieve system r/w... Thanks...
lollyjay said:
I don't have 402 any more. Here is one from 403. Maybe @Regnas can give you the other.
Click to expand...
Click to collapse
I would like to help but I don't know how to generate this info..
What is this?
ssanjy said:
Hi @lollyjay, the method is simple and easy and is working great....Thanks a lot for that.....But how do we enable system r/w because it did not let me edit build.prop to enable brigntness slider... in earlier version I used modified initrd.img....it there any other way to achieve system r/w... Thanks...
Click to expand...
Click to collapse
They have removed the brightness slider in 402 at least.
I'm not sure which ramdisk this is; check getprop and see what ro.remixos.box is set to.
I'll upload my ramdisk if you want to check if the slider was readded in 403 [if its set to true].
I also have the modified initrd.img on my thread; where these .imgs are from. But ideally it's best not to use it; the only downside being needing to modify ramdisk.img itself for ro.* prop entries.
HypoTurtle said:
They have removed the brightness slider in 402 at least.
I'm not sure which ramdisk this is; check getprop and see what ro.remixos.box is set to.
I'll upload my ramdisk if you want to check if the slider was readded in 403 [if its set to true].
I also have the modified initrd.img on my thread; where these .imgs are from. But ideally it's best not to use it; the only downside being needing to modify ramdisk.img itself for ro.* prop entries.
Click to expand...
Click to collapse
remixos.box is set to true and when I tried to change it to false I couldn't save it... While in 402 I had found modified initrd which did let me change value of build prop... Anyway thanks for the info
Sent from my S II using XDA Labs
ssanjy said:
remixos.box is set to true and when I tried to change it to false I couldn't save it... While in 402 I had found modified initrd which did let me change value of build prop... Anyway thanks for the info
Click to expand...
Click to collapse
Hi you might try Root Browser from Play Store it can change permissions
Sent from my on Z00A using XDA Labs
lollyjay said:
I don't have 402 any more. Here is one from 403. Maybe @Regnas can give you the other.
Sent from my on Z00A using XDA Labs
Click to expand...
Click to collapse
It would need both from the same device; think I found a 402 that you posted elsewhere.
Code:
[b]Removed[/b]
b43 375752 0
mac80211 504422 1 b43
ssb 45258 1 b43
rng_core 7153 1 b43
bcma 43126 1 b43
efivars 7470 0 [efi variables]
[b]Added[/b]
intel_rst 2468 0 [rapid storage tech]
psmouse 101828 0 [touchpad]
would be the module difference between 402 and 403; so perhaps just blacklisting b43 on 402 would have sufficed [the others are dependant on it]
ssanjy said:
remixos.box is set to true and when I tried to change it to false I couldn't save it... While in 402 I had found modified initrd which did let me change value of build prop... Anyway thanks for the info
Sent from my S II using XDA Labs
Click to expand...
Click to collapse
The 402 initrd should work fine [attach the 403 here just so I can compare to 402 just to see if anything was changed] if you want to modify it that way; but the slider is gone. Only options would be to add a shortcut to the brightness activity from SystemUI or a brightness app.
Hey guys, I'm using an HD install of remix os 403 - replaced the ramdisk - went back into Remix but couldn't access the ALT+F1 terminal for whatever reason. Eventually I managed to get the su.img into the right folder in the data.img and nothing happens. How would I be notified that it has worked? Would I see something different on startup? I assume the su.img is being mounted etc by the modified ramdisk.img.
Would it be a possibility to just make a fresh, clean data.img with just that su.img file already in? That way I could try just replacing the data.img and starting fresh. At this moment I can't see any change from the su.img and ramdisk.img being in place. Probably it's a problem at my end - but i'm confused why the ALT+F1 root terminal doesn't work for me?
I'm using a UK keyboard on an Alienware M17x R4 - any suggestions would be very welcome.
By the way I used Paragon ExtFS for Windows to access the data.img and insert the su.img file (which I verified in the terminal of remixos (not the root terminal, I couldn't get that working) but I can use the LS command in /data and I see that su.img is there.
Thank you for any suggestions
mrpras said:
Hey guys, I'm using an HD install of remix os 403 - replaced the ramdisk - went back into Remix but couldn't access the ALT+F1 terminal for whatever reason. Eventually I managed to get the su.img into the right folder in the data.img and nothing happens. How would I be notified that it has worked? Would I see something different on startup? I assume the su.img is being mounted etc by the modified ramdisk.img.
Would it be a possibility to just make a fresh, clean data.img with just that su.img file already in? That way I could try just replacing the data.img and starting fresh. At this moment I can't see any change from the su.img and ramdisk.img being in place. Probably it's a problem at my end - but i'm confused why the ALT+F1 root terminal doesn't work for me?
I'm using a UK keyboard on an Alienware M17x R4 - any suggestions would be very welcome.
By the way I used Paragon ExtFS for Windows to access the data.img and insert the su.img file (which I verified in the terminal of remixos (not the root terminal, I couldn't get that working) but I can use the LS command in /data and I see that su.img is there.
Thank you for any suggestions
Click to expand...
Click to collapse
Did you remember to go into settings/experimental features to enable terminal debug console? If so try Alt&right arrow for entry/egress
Sent from my on Z00A using XDA Labs
lollyjay said:
Did you remember to go into settings/experimental features to enable terminal debug console? If so try Alt&right arrow for entry/egress
Sent from my on Z00A using XDA Labs
Click to expand...
Click to collapse
I hadn't enabled the console/debug option thank you for that!
Now I'll go and try again. Thanks for the fix, and the systemless root files. I'll be back if it doesn't work, otherwise thanks again!
---------- Post added at 05:50 PM ---------- Previous post was at 05:28 PM ----------
Okay thanks, so that works - Just a small suggestion that somewhere in your description (where you mention the Alt+F1) it could be worth mentioning about enabling the debug console because I didn't find that information when scouring around. Maybe would be helpful to others as ignorant as me
mrpras said:
I hadn't enabled the console/debug option thank you for that!
Now I'll go and try again. Thanks for the fix, and the systemless root files. I'll be back if it doesn't work, otherwise thanks again!
Click to expand...
Click to collapse
My pleasure. You can test root by downloading an app that requires root such as Titanium Backup. It will immediately let you know if it cannot acquire root privilege
Sent from my on Z00A using XDA Labs
Just wanted to note here that the Lenovo ThinkPad Twist is a great dual Windows /Ubuntu and Remix OS daily driver. Great touchscreen display and can be used as a (heavy) tablet with Remix OS. Look at this on eBay http://www.ebay.com/itm/162121987813
I bought three from a school for $99 each.
Sent from my on Z00A using XDA Labs
I recently acquired a Samsung Z2 and have been working on trying to get it working at its full potential.
I have rooted the latest Indonesian firmware (BQD2) This is because I do not have an Indian Z2 to test with.
Thanks to @adfree for the help!
Here is the link: https://www.androidfilehost.com/?fid=818070582850505393
I am now working on trying to get android apps to show up on the main home screen.
One thing that I noticed is that the apk files in /opt/apps/ACL111OMWW/data/android/data/app are just symlinks to another area. You don't have to worry about replacing that apk "file". You only have to worry about the one it links to.
When you replace the linked apk in /usr/app/ with another android app, it just hangs at step 4. Now I just need to investigate more into the /usr/app/ directory.
Bro Don't Do this Because @adfree Already Have Did it..
Code:
[color=red] SDB
[/color]
But You Can Try. Also I can Help with You.
Clash Of Clans Must Be Important
And Also All Google Facility...
Go Ahead Bro......
forhadaliBan said:
Bro Don't Do this Because @adfree Already Have Did it..
Code:
[color=red] SDB
[/color]
But You Can Try. Also I can Help with You.
Clash Of Clans Must Be Important
And Also All Google Facility...
Go Ahead Bro......
Click to expand...
Click to collapse
SDB is different. That is the interface application that allows your computer to communicate with your tizen phone. Also, you need to have a rooted rootfs installed to get SDB Root enabled
Sent from my Q5 using XDA Free mobile app
iam Already Rooted My Z1...
Updates on my investigation into tpk files:
Thanks to the guy from Samsung for replying to my email in the Tizen mailing list and my question on stackoverflow: https://stackoverflow.com/questions/49637116/sha256-sum-is-not-sha256/49662083#49662083
NOTE: To sign and install tpks, you need a Samsung cert, not just a normal one which can be created once you install the certificate extension sdk. Not the standard cert manager.
Apparently the tizen-manifest file is the main important file. From there you can edit nearly everything important.
The ones you can safely edit are:
package
author
description
appid (which must match exec!)
exec
label
icon
I have not tested the editing of anything else.
ACL doesn't like it when you change things, so to make it scream less, you have to link the apk to the ACL folder.
You need to create a symbolic link to wherever the apk is stored in /opt/usr/apps/ACL111OMWW/data/android/data/app/
Once you do that, ACL will reach step 2 before failing. It will only reach step 2 after a reboot as otherwise it caches the app.
This is an immense step! We just have a little more to go and we can get Android apps running off of the Tizen app screen!
If anyone has any input, feel free to give it!
proof discord installs to the app screen: https://imgur.com/a/kYvD6
proof it reaches step 2: https://imgur.com/a/j4y5J
You Can Try with Both Method.Like Mobile Mini Shell And Tizen Studio For Pc
Plz Share Img In Xda
I have NOT so much time...
22nd March 2016, 02:18 PM
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=65978699&postcount=259
This Modification work since 2 yearS +... for me...
Something similar I made for Wearables too...
To have all 3 Privileges too...
Code:
Public
Partner
Platform
And with HashSigner Script I can simple sign this crap...
Can not find yet better Link... but click somewhere here...
https://forum.xda-developers.com/showpost.php?p=70436534&postcount=384
To find my infos about "hashsigner.sh"...
This PKI sh it still s h it...
Best Regards
Edit 1.
I have no idea why since months for me search not work...
vBulletin Message
An error occurred while performing a Searchlight query:
expected searchd protocol version 1+, found version
If you followed a valid link, please notify the administrator.
Click to expand...
Click to collapse
Edit 2.
Found my post via Google...
https://forum.xda-developers.com/showpost.php?p=72204916&postcount=184
In theory I have more posts where this is posted:
Choose between 3 Commands...
Code:
hash-signer.sh -a -d /opt/usr/media/test
public level
Code:
hash-signer.sh -p partner -a -d /opt/usr/media/test
partner level
Code:
hash-signer.sh -p platform -a -d /opt/usr/media/test
platform level
adfree said:
I have NOT so much time...
https://forum.xda-developers.com/showpost.php?p=65978699&postcount=259
This Modification work since 2 yearS +... for me...
Something similar I made for Wearables too...
To have all 3 Privileges too...
Code:
Public
Partner
Platform
And with HashSigner Script I can simple sign this crap...
Can not find yet better Link... but click somewhere here...
https://forum.xda-developers.com/showpost.php?p=70436534&postcount=384
To find my infos about "hashsigner.sh"...
This PKI sh it still s h it...
Best Regards
Edit 1.
I have no idea why since months for me search not work...
Edit 2.
Found my post via Google...
https://forum.xda-developers.com/showpost.php?p=72204916&postcount=184
In theory I have more posts where this is posted:
Choose between 3 Commands...
Code:
hash-signer.sh -a -d /opt/usr/media/test
public level
Code:
hash-signer.sh -p partner -a -d /opt/usr/media/test
partner level
Code:
hash-signer.sh -p platform -a -d /opt/usr/media/test
platform level
Click to expand...
Click to collapse
Thanks,
But where is the hash-signer.sh file?
Did you unpack and extract all files from rootfs.img?
I am toooooo lazy to check Z2 Firmware... if in latest available or removed by Samsung...
Code:
hash-signer.sh
Best Regards
adfree said:
Did you unpack and extract all files from rootfs.img?
I am toooooo lazy to check Z2 Firmware... if in latest available or removed by Samsung...
Code:
hash-signer.sh
Best Regards
Click to expand...
Click to collapse
It has been removed in the latest firmware
Could be... sometimes they only deactivated...
I was never able to sign with SM-R732 and SM-R760...
In theory few RPM files available...
Will check... need time...
In theory also RPM for Tizen Studio Emulator crap...
Best Regards
About Signing...
I was tooooo lazy to check...
But if this work we could use also other Certs with Password...
https://forum.xda-developers.com/gear-fit/general/howto-sign-sideload-tizen-applications-t3639793
Best Regards
adfree said:
About Signing...
I was tooooo lazy to check...
But if this work we could use also other Certs with Password...
https://forum.xda-developers.com/gear-fit/general/howto-sign-sideload-tizen-applications-t3639793
Best Regards
Click to expand...
Click to collapse
I can sign tpks just fine, the problem is that I cannot get ACL to run my apps that I resign and put on the homescreen
Sent from my Q5 using XDA Free mobile app
I cannot get ACL to run my apps that I resign and put on the homescreen
Click to expand...
Click to collapse
ACL is self checking Cert...
This is the reason why I have signed ACL AND TPK... with same key/cert....
For Original ACL you need Original RSA 2018 Cert...
and this is at the moment impossible...
So I fake signed ACL... to use my fake signed TPKs...
Best Regards
adfree said:
ACL is self checking Cert...
This is the reason why I have signed ACL AND TPK... with same key/cert....
For Original ACL you need Original RSA 2018 Cert...
and this is at the moment impossible...
So I fake signed ACL... to use my fake signed TPKs...
Best Regards
Click to expand...
Click to collapse
So, I have to extract ACL, resign ACL with the new cert and it will install all files with that cert?
Sent from my Q5 using XDA Free mobile app
https://forum.xda-developers.com/showpost.php?p=69049909&postcount=344
And few posts later...
Also fake signed TPKs added...
Best Regards
Anyone been able to install apk in this tpk..... i keep getting acl error
Hello.
Stock libraries on XZ1 Compact are using 25mA current for the flashlight, which leads to very dim light.
I fixed this to get 400mA current, and now flashlight is very bright, much better than on 25mA (stock) current.
WARNING: You may damage (or even fry) your flashlight LED with these libraries, but i'm think 400mA is fine, because there is 25..400mA limits in the code, and after 2 minutes of light at 400mA my phone's LED was just a bit warm (but not hot).
WARNING: You must disable dm-verity for /vendor/ partition before flashing any .zip attached below, or you will get bootloop.
NOTES:
1. The easiest way to disable dm-verity is to use Magisk to get root (it will automatically disable dm-verity of both /system/ and /vendor/ partitions when installed with default settings). The patched libraries does not require root access, Magisk is mentioned here only for disabling dm-verity.
2. To install Magisk you must unlock bootloader and flash TWRP. Please read [RECOVERY] TWRP 3.2.3-0 (lilac) [UPDATE: 2018-11-28] to learn more about TWRP installation for XZ1 Compact (or find appropriate TWRP for your device).
3. Please read [XZ1c/XZ1/XZp] temp root exploit to backup drm keys implemented to learn more about the way to backup your TA with DRM keys before unlocking your device's bootloader (this is important, because DRM keys will be lost on bootloader unlock, and you will have no way to get them back if you don't have TA backup with those DRM keys).
If you need other current value (in 25..400mA range) - feel free to contact me.
If you need patch for another ROM version or device - please contact me with attached /vendor/lib/libcameralight.so and /vendor/lib64/libcameralight.so from your ROM (and please tell me your device's model and version of your ROM).
You may try to do patch by yourself, tech details about patching is in Post #17 - feel free to upload patched .so files or flashable .zip for your device (please don't forget to write device model and ROM version in the description).
Files without model in name is for XZ1 Compact, other files (with model at the end of file name) is for corresponding phone models.
Files for 47.2.A.0.306 are also compatible with 47.2.A.2.33, 47.2.A.4.41 and 47.2.A.4.45 ROM versions, and may be compatible with future ROM releases (or may not - I don't know exactly, so please check compatibility before flashing).
Please check Post #25 for details about compatibility between fixes and ROM versions, and how to check compatibility if your ROM isn't listed.
You can use Magisk module from Post #32 instead of flashing the ZIP files directly to the /vendor/ (just replace existing .so files in Magisk module ZIP with desired versions (using any ZIP archiver) and install the module).
4PDA.ru post (in Russian)
@S-trace
please can modify for me the one for xz3 and for xzp. thank u
I assume root is needed?
karrouma said:
@S-trace
please can modify for me the one for xz3 and for xzp. thank u
Click to expand...
Click to collapse
Please upload necessary files here and tell me device models and firmware versions of each device you need, and which current should i set.
mEREHAIGE said:
I assume root is needed?
Click to expand...
Click to collapse
Yes, you must get root using Magisk (or disable verity on /vendor/ in any other way) before installing this mod, or you may get bootloop.
Root access itself is not necessary for mod to work, just disabled verity is needed (but installing Magisk is the easiest way to get this for me)
@S-trace
can you make a 350ma for pie version of xz1c
it is same as xzp
Can you make some medium for xz1c? Like 250 ?
karrouma said:
@S-tracecan you make a 350ma for pie version of xz1c
it is same as xzp
Click to expand...
Click to collapse
Done.
manuerduarte said:
Can you make some medium for xz1c? Like 250 ?
Click to expand...
Click to collapse
Done.
Thanks!
S-trace said:
Done.
Done.
Click to expand...
Click to collapse
Thank you my friend.
Teting the 350 and 400
400 is better in all condition for cam
And 400 has no heat so it is fine for daily use.
Thank you for your work
Here for xz3
Attached
Can you modified to 400ma
Thank you
Hi,
This is a welcome patch. It used to be (on Z3C) to just change flashled_calc_parameters file - do you think it's still possible on XZ1C? Can you share more details on how exactly you patch the .so files?
gshegosh81 said:
Hi,
This is a welcome patch. It used to be (on Z3C) to just change flashled_calc_parameters file - do you think it's still possible on XZ1C? Can you share more details on how exactly you patch the .so files?
Click to expand...
Click to collapse
Is there anyway, we can control the current that goes to the flash on the go?
S-trace said:
Done.
Done.
Click to expand...
Click to collapse
@S-trace
Can i take a little bit from your time
Can you make an 450ma and 500 for me.
Thank you
rsk_kelkar said:
Is there anyway, we can control the current that goes to the flash on the go?
Click to expand...
Click to collapse
You can use following script for testing different current values:
Code:
#!/system/bin/sh
toggle=$(cat /sys/class/leds/led:switch_0/brightness)
if [ "$toggle" = "0" ];then
echo 60 > /sys/class/leds/led:torch_0/brightness
echo 60 > /sys/class/leds/led:torch_1/brightness
echo 1 > /sys/class/leds/led:switch_0/brightness
echo "on"
else
echo 0 > /sys/class/leds/led:torch_0/brightness
echo 0 > /sys/class/leds/led:torch_1/brightness
echo 0 > /sys/class/leds/led:switch_0/brightness
echo "off"
fi
60 means 120mA here, stock value is 13 (25mA).
I don't know any way to control flashlight current dynamically from the Android OS (like display brightness can be controlled).
karrouma said:
@S-trace
Can i take a little bit from your time
Can you make an 450ma and 500 for me.
Thank you
Click to expand...
Click to collapse
No, it won't work (I tried) - kernel will limit current to 400mA. Maybe it will be possible if you will patch kernel/dt to overcome this limit, but I'm not sure.
S-trace said:
You can use following script for testing different current values:
Code:
#!/system/bin/sh
toggle=$(cat /sys/class/leds/led:switch_0/brightness)
if [ "$toggle" = "0" ];then
echo 60 > /sys/class/leds/led:torch_0/brightness
echo 60 > /sys/class/leds/led:torch_1/brightness
echo 1 > /sys/class/leds/led:switch_0/brightness
echo "on"
else
echo 0 > /sys/class/leds/led:torch_0/brightness
echo 0 > /sys/class/leds/led:torch_1/brightness
echo 0 > /sys/class/leds/led:switch_0/brightness
echo "off"
fi
60 means 120mA here, stock value is 13 (25mA).
I don't know any way to control flashlight current dynamically from the Android OS (like display brightness can be controlled).
No, it won't work (I tried) - kernel will limit current to 400mA. Maybe it will be possible if you will patch kernel/dt to overcome this limit, but I'm not sure.
Click to expand...
Click to collapse
Thank you
Can you use this on lineageos?
karrouma said:
Here for xz3
Attached
Can you modified to 400ma
Thank you
Click to expand...
Click to collapse
Modified
Can you tell exact ROM version (from which you have taken libraries) to let me upload these patched libraries and original libraries to the OP?
4684361 said:
Can you use this on lineageos?
Click to expand...
Click to collapse
This depends on LineageOS you have.
gshegosh81 said:
Hi,
This is a welcome patch. It used to be (on Z3C) to just change flashled_calc_parameters file - do you think it's still possible on XZ1C? Can you share more details on how exactly you patch the .so files?
Click to expand...
Click to collapse
I'm think /vendor/etc/flashled_calc_parameters.cfg holds only camera flash parameters, not torch parameters.
But you may try to edit this file if you want.
Details about patching (offsets is for XZ1c):
Code:
32bit 8.0: (Thumb-2)
0x3F52 ALL 23=>22
0x3F9A 300 00E0FFE746F2A810=>49F2E030C0F20400
0x3F9A 400 00E0FFE746F2A810=>41F68020C0F20600
64bit 8.0: (ARM64)
0x4BBC ALL 0003=>E002
0x4C18 300 020000140100001400358CD2=>007C92D28000A0F21F2003D5
0x4C18 400 020000140100001400358CD2=>005083D2C000A0F21F2003D5
32bit 9.0: (Thumb-2)
0x4D52 ALL 3C=>3B
0x4DCC 250 00E0FFE746F2A810=>4DF29000C0F20300
0x4DCC 350 00E0FFE746F2A810=>45F23070C0F20500
0x4DCC 400 00E0FFE746F2A810=>41F68020C0F20600
64bit 9.0: (ARM64)
0x5CAC ALL E0=>C0
0x5D64 250 020000140100001400358CD2=>00129AD26000A0F21F2003D5
0x5D64 350 020000140100001400358CD2=>00E68AD2A000A0F21F2003D5
0x5D64 400 020000140100001400358CD2=>005083D2C000A0F21F2003D5
Payloads:
32bit:
MOVW R0, #0x1A80
MOVT R0, #6
64bit:
MOVZ X0, #0x1A80
MOVK X0, #0x6, LSL #16
NOP
The first one-byte patch is just a fixup for BEQ offset (to make it jump to correct offset, because we need 4 extra bytes to insert one more instruction, so we'll replace two useless B opcodes with MOV* instructions).
The second multi-byte patch is a payload, in this example MOV* instructions store 0x61A80 (400000) in R0/X0.
You may use http://armconverter.com/ to assemble payload with desired current value and then use HEX editor to patch your libraries (32bit is more important, i don't know who and when will use 64bit library, but patch it too just to leave OS libraries consistent).
S-trace said:
Modified
Can you tell exact ROM version (from which you have taken libraries) to let me upload these patched libraries and original libraries to the OP?
This depends on LineageOS you have.
I'm think /vendor/etc/flashled_calc_parameters.cfg holds only camera flash parameters, not torch parameters.
But you may try to edit this file if you want.
Details about patching (offsets is for XZ1c):
Code:
32bit 8.0: (Thumb-2)
0x3F52 ALL 23=>22
0x3F9A 300 00E0FFE746F2A810=>49F2E030C0F20400
0x3F9A 400 00E0FFE746F2A810=>41F68020C0F20600
64bit 8.0: (ARM64)
0x4BBC ALL 0003=>E002
0x4C18 300 020000140100001400358CD2=>007C92D28000A0F21F2003D5
0x4C18 400 020000140100001400358CD2=>005083D2C000A0F21F2003D5
32bit 9.0: (Thumb-2)
0x4D52 ALL 3C=>3B
0x4DCC 250 00E0FFE746F2A810=>4DF29000C0F20300
0x4DCC 350 00E0FFE746F2A810=>45F23070C0F20500
0x4DCC 400 00E0FFE746F2A810=>41F68020C0F20600
64bit 9.0: (ARM64)
0x5CAC ALL E0=>C0
0x5D64 250 020000140100001400358CD2=>00129AD26000A0F21F2003D5
0x5D64 350 020000140100001400358CD2=>00E68AD2A000A0F21F2003D5
0x5D64 400 020000140100001400358CD2=>005083D2C000A0F21F2003D5
Payloads:
32bit:
MOVW R0, #0x1A80
MOVT R0, #6
64bit:
MOVZ X0, #0x1A80
MOVK X0, #0x6, LSL #16
NOP
The first one-byte patch is just a fixup for BEQ offset (to make it jump to correct offset, because we need 4 extra bytes to insert one more instruction, so we'll replace two useless B opcodes with MOV* instructions).
The second multi-byte patch is a payload, in this example MOV* instructions store 0x61A80 (400000) in R0/X0.
You may use http://armconverter.com/ to assemble payload with desired current value and then use HEX editor to patch your libraries (32bit is more important, i don't know who and when will use 64bit library, but patch it too just to leave OS libraries consistent).
Click to expand...
Click to collapse
52.0.A.3.84 xz3
karrouma said:
52.0.A.3.84 xz3
Click to expand...
Click to collapse
Thank you.
Uploaded files to the OP.
S-trace said:
Thank you.
Uploaded files to the OP.
Click to expand...
Click to collapse
Thank you