Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Details:
I am no longer continuing this project. Any issues refer to the bottom of this as I've tried to post the most common or read through thread.
Installing:
You need to install xRecovery, then extract the folder named "Eminence v1.2" to /sdcard/xrecovery/backup, then reboot into xRecovery and use the Restore option to install the ROM to your phone.
You can find a more detailed guide by hellsrage619 HERE
Credits:
MrRusch for his work on the framework mod, H0CKEY for the home screen ICONS, rabetionline for pointing out the obvious, zdzihu for xRecovery and the rooted ROM, Fightspit for the SuperCircle Mod, Kersey for pointing out the JIT issue, mbrad26 for THIS, Jassiered for the Animations & Calum for his Thread.
Change Log:
Not changed a great deal really, modified for the new update, changed the button press, new animations, JIT enabled, removed the recovery menu. I've not made the background so dark so it stands out a bit more and changed the bootscreen, also cleaned up the dialler buttons.
Included
3.D Gallery, BusyBox, FileManager, Gauge Battery Widget [free], HTC ime [Themed], LauncherPro, Linpack, Signal Strength Widget, Superuser, Tajm, Titanium Backup [Free Version], xRecovery, Rooted
Removed *
Chinese Text input, Creatouch, Digital Clock Widget, EManual, Emanual Launcher, Facebook, Face Recognition, Home Launcher, Latin IME, Learning Client, Moxiermail, Music, Officesuite, PC Companion, Playnow/Client/Back/App Installer, Quadrapop, Ringtones, Recent Calls, Status Switch, Semc/Checkin/Setup Wizard/TouchPal Korean Qwerty, Search Widget, Textinput TNG, Timescape/Plugin Manager/Provider/Themes, Track I.D, User Support, uWlop, Wallpaper
Features:
JIT
Framework Animations
SuperCircle Battery Mod
X10 Res Mods Styling
Extras:
Bootscreen, Comfertaa Font, Wallpaper
Screen Shots:
Boot Screen: (quality is better on the phone)
Download Links:
Download Link 1
Download Link 2
Download Link 3
PLEASE READ
You are free to use 99.9% for whatever you wish, HOWEVER, I created the lockscreen, I've used it in my themes, now this, and it's a feature, a signature if you like, of my work, which I don't wish to see used in other themes/ROMS, ESPECIALLY which are for the X10, and I don't think that's an unfair request, PLUS, if you are going to create something for the community, try and put your own stamp on it.
If you get a md5 "mismatch" error, smartgardens has posted a solution HERE. Or some have said renaming the folder, for example, "Eminence v1.2" to Eminence_v1.2" works also.
If you've not already used zdzihu's ROM and flashtool files to update to 2.0.2.A.0.24 then you need to update the Baseband as well. Doesn't matter if you don't, but as we all like to be upto date you might as well...
zdzihu said:
You need xRecovery to flash rooted system (and system only) image.
Then you need X10 flasher to flash all remaining parts (SIN files = kernel, baseband etc)
Cheers,
z
Click to expand...
Click to collapse
...so just run the flashtool from HERE
----------
x10_lynx said:
i was modifing app and framework directory in case of searching an solution for my market and gtalk problem. (market no download and gtalk wont start)
Click to expand...
Click to collapse
x10_lynx said:
i found a solution for my case of gtalk&market issues.
after deleting /data/system/accounts.db there was a clean accounts folder under settings.
after reboot i go to market and login with my account. after this no problem with market and gtalk!
Click to expand...
Click to collapse
----------
McKebapp said:
Well I'd like to change the comfortaa font to sonysketch.
The common way via TypeFont doesn't seem to work.
Click to expand...
Click to collapse
McKebapp said:
There is a free App called "Font Changer Lite".
Worked like charme
Click to expand...
Click to collapse
----------
llama69 said:
Ok first post - it doesn't look like anyone's solved this on here yet, so I registered to explain my experience;
Basically I didn't want to go without Timescape as I actually find it useful, so I tried to reinstall it (installing the Timescape* apks from my backup of /system/apps I made before putting the firmware on), however everytime I tried to log in I got the same error as above stating that my login details were incorrect!
After much frustration and searching for the reason, I finally found it - the uWlopProvider.apk had been removed. It's this apk that Timescape/Mediascape use to communicate with facebook/twitter, and without it they keep chucking up the incorrect username/password / authentication error messages (it would have saved me a LOT of time if they had simply said they could not communicate with the servers, but oh well...).
So, the solution to this problem is to get ahold of the uWlopProvider.apk file, either from the link in the first post (re getting removed apps) or restore the firmware and copy it from that, then reflash - then once you have the apk, install it with adb.
For reference - these are the commands I used to install Timescape back on (inc uWlopProvider.apk) - note you need adb installed on your pc and usb debugging turned on; (note the files you are installing from need to be in /sdcard/apps if you are copying/pasting below)
Code:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb shell dd if=/sdcard/apps/TimescapeLargeUI.apk of=/system/app/TimescapeLargeUI.apk
adb shell dd if=/sdcard/apps/TimescapeLargeUIThemeBlue.apk of=/system/app/TimescapeLargeUIThemeBlue.apk
adb shell dd if=/sdcard/apps/TimescapeLargeUIThemeGreen.apk of=/system/app/TimescapeLargeUIThemeGreen.apk
adb shell dd if=/sdcard/apps/TimescapeLargeUIThemeIndigo.apk of=/system/app/TimescapeLargeUIThemeIndigo.apk
adb shell dd if=/sdcard/apps/TimescapeLargeUIThemeOrange.apk of=/system/app/TimescapeLargeUIThemeOrange.apk
adb shell dd if=/sdcard/apps/TimescapeLargeUIThemeSakura.apk of=/system/app/TimescapeLargeUIThemeSakura.apk
adb shell dd if=/sdcard/apps/TimescapePluginManager.apk of=/system/app/TimescapePluginManager.apk
adb shell dd if=/sdcard/apps/TimescapeProvider.apk of=/system/app/TimescapeProvider.apk
adb shell dd if=/sdcard/apps/uWlopProvider.apk of=/system/app/uWlopProvider.apk
adb shell chmod 644 /system/app/Timescape*
adb shell chmod 644 /system/app/uWlopProvider.apk
adb shell reboot
And that's it - once the phone reboots Timescape should work. If you only want Mediascape to sync with fb/twitter and don't want Timescape back, then just do the dd and chmod on the uWlopProvider file above, not the Timescape ones (obviously!).
Hope that helps!
Click to expand...
Click to collapse
----------
Market Issues Have Nothing To Do With Themes
* You can find most of the apps that have been removed HERE, and if it's not listed in the first post chances are you will find it somewhere in the thread.
Some extras for your X10:
Fonts
Bootscreens
60 SMS Tones
178 Game HD wallpapers
Hubble Telescope wallpapers
FHM Top 10 2010 wallpapers
2.1 System Apps/Framework Files
http://forum.xda-developers.com/showthread.php?p=9877530#post9877530
already list your modded rom to above..
post 2...
if u want me to unlist, pm me..
purpose:supporting custom rom development...
Woah! Very nice!!
Just one question: What's the keyboard in this screenshot?
Can you share it please?
Thanks. I really appreciate your work.
That is so sexy I think I'm gonna have a crisis
fyzm345 said:
already list your modded rom to above..
post 2...
Click to expand...
Click to collapse
Thanks.
Farhang said:
Woah! Very nice!!
Click to expand...
Click to collapse
Thanks
Farhang said:
Just one question: What's the keyboard in this screenshot?
Click to expand...
Click to collapse
It's a themed HTC IME
Farhang said:
Can you share it please?
Click to expand...
Click to collapse
Sure, see attachment.
Farhang said:
Thanks. I really appreciate your work.
Click to expand...
Click to collapse
Thank you.
Gavilaaar said:
That is so sexy I think I'm gonna have a crisis
Click to expand...
Click to collapse
Thanks.
Wow, what can I say...what a great looking rom making my X10 even sexier.
Great work mate
The HTC IME is awesome thanks for sharing.
sent from my commodore 64
Congratulations XperiaX10iUser, I've always loved your themes and this is a beautifully themed ROM, I'll start to recommend this rom for the guys that ask for stock based ROM's in my own theme thread...
Just for you guys to know even though it's stated as JIT enabled I ran Linpack and was only getting around 6.45 MFLOPS.
Having enabled JIT via Terminal Emulator am now getting 17.638 MFLOPS
kersey said:
Great work mate
Click to expand...
Click to collapse
Thanks.
chiefy009 said:
The HTC IME is awesome thanks for sharing.
Click to expand...
Click to collapse
You're welcome.
rmourar said:
Congratulations XperiaX10iUser, I've always loved your themes and this is a beautifully themed ROM, I'll start to recommend this rom for the guys that ask for stock based ROM's in my own theme thread...
Click to expand...
Click to collapse
Thanks, and thanks.
kersey said:
Just for you guys to know even though it's stated as JIT enabled I ran Linpack and was only getting around 6.45 MFLOPS.
Having enabled JIT via Terminal Emulator am now getting 17.638 MFLOPS
Click to expand...
Click to collapse
See p.m.
This is the dogs danglers. Stunning.
Damnit, these download links are WAY TOO slow... Can't you post some more links because these are taking > 50 minutes to complete.. And I'm not planning to purchase a premium account
kersey said:
Having enabled JIT via Terminal Emulator am now getting 17.638 MFLOPS
Click to expand...
Click to collapse
Strange, having run the customiser and the optimiser I've got a similar score with Linpack to you, so seems like they haven't enabled it for me. Can you post the emulator command to see if that makes any difference?
buzzboy said:
This is the dogs danglers. Stunning.
Click to expand...
Click to collapse
Thanks.
dnifan said:
And I'm not planning to purchase a premium account
Click to expand...
Click to collapse
No for reasons already stated on my theme thread, and it takes less than 2 minutes to sign up for a free account.
XperiaX10iUser said:
Strange, having run the customiser and the optimiser I've got a similar score with Linpack to you, so seems like they haven't enabled it for me. Can you post the emulator command to see if that makes any difference?
Click to expand...
Click to collapse
Just replied to your p.m.
kersey said:
Just replied to your p.m.
Click to expand...
Click to collapse
Updated the first post and credits.
dnifan said:
Damnit, these download links are WAY TOO slow... Can't you post some more links because these are taking > 50 minutes to complete.. And I'm not planning to purchase a premium account [what r u What r utalking about?it just took me 4 minutes to download it,is your internet really working,lol!,anyway @XperiaX10User,great work as always,it just look awesome,and in my view the most stunning ROM so far available for our X10,keep it up dude...........thanks once again,hope u will continue this awesome work in the future as well.
Click to expand...
Click to collapse
SK_007 said:
anyway @XperiaX10User,great work as always,it just look awesome,and in my view the most stunning ROM so far available for our X10,keep it up dude...........thanks once again,hope u will continue this awesome work in the future as well.
Click to expand...
Click to collapse
Thanks, it's reading comments like that that will keep me going.
XperiaX10iUser said:
Thanks, it's reading comments like that that will keep me going.
Click to expand...
Click to collapse
oh forgot to mention one more thing that the new themed keyboard looks awesome and it matches perfectly with the theme/ROM.....
This rom is awesome!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[ Unofficial CyanogenMod 10 Build on HTC DNA ]
git @ https://github.com/drewx2/android/ (Updated to download all necessary repos)
..CURRENT BUILD NOTES/HISTORY..
03.24.13: CM10 doesn't include support for csd-client enabled phones (which we need). I have built a work around for it to utilize our csd-client lib; hopefully it brings audio one step closer.
My audio changes can be found at a separate git repo @ https://github.com/drewx2/android_hardware_qcom
03.23.13: Current Audio Status
I have some time to look at things, so here just getting started and thought I would post the first strace for those interested. Looks promising and not too difficult.
Code:
writev(4, [{"\4", 1}, {"AudioHardwareALSA\0", 18}, {"ucm instance opened: 1082445752\0", 32}], 3) = 51
writev(4, [{"\6", 1}, {"AudioFlinger\0", 13}, {"int android::load_audio_interfac"..., 103}], 3) = 117
writev(4, [{"\4", 1}, {"AudioFlinger\0", 13}, {"loadHwModule() error -22 loading"..., 49}], 3) = 63
writev(4, [{"\5", 1}, {"AudioPolicyManagerBase\0", 23}, {"could not open HW module primary"..., 33}], 3) = 57
writev(4, [{"\6", 1}, {"AudioPolicyManagerBase\0", 23}, {"Not output found for attached de"..., 47}], 3) = 71
writev(4, [{"\6", 1}, {"AudioPolicyManagerBase\0", 23}, {"Failed to open primary output\0", 30}], 3) = 54
writev(4, [{"\6", 1}, {"AudioPolicyManagerBase\0", 23}, {"getDeviceForStrategy() speaker d"..., 74}], 3) = 98
clock_gettime(CLOCK_MONOTONIC, {205, 684889413}) = 0
writev(4, [{"\6", 1}, {"AudioPolicyManagerBase\0", 23}, {"getDeviceForStrategy() speaker d"..., 74}], 3) = 98
writev(4, [{"\6", 1}, {"AudioPolicyService\0", 19}, {"couldn't init_check the audio po"..., 54}], 3) = 74
ioctl(3, 0xc0186201, 0xbe961a28) = 0
Complete strace available here: http://bit.ly/Xx3M0v
-------------------------------------------------------------------------------------------------------------------------------------
There won't be any builds posted until one of the "not working" items has been fixed. I mostly likely will focus on audio this weekend.
If you have something meaningful to share, please visit http://webchat.freenode.net/?channels=CM10DNA
03.04.13 @ 03:29AM: Wifi *now* really working
03.04.13 @ 03:29AM: Wifi now working.
Enable 3 dot menu: Settings -> Hardware keys -> Show action overflow [check]
Working:
Radio/RIL (no sound, so can't hear yet), SMS / MMS, 3G / 4G Data, Display, Orientation, Sensors, Lights, NFC, Torch, GPS (not tested), Wifi
Not working:
Camera, Audio, Bluetooth
To Do list
I plan to do bionic/kernel optimizations once all features working.
Click to expand...
Click to collapse
..INSTALL INSTRUCTIONS..If you do not have S-OFF, you need to unzip the file and flash the boot.img inside via fastboot.
Install Instructions:
1) Download http://bit.ly/W0RAY8
2) Reboot to recovery of your choosing; wipe system/data/dalvik-cache/cache.
3) Install downloaded zip
4) Reboot.
5) Enjoy.
Google Apps @ http://goo.im/gapps/gapps-jb-20121011-signed.zip
Click to expand...
Click to collapse
Click to expand...
Click to collapse
.SPECIAL THANKS FOR DONATING.
RuinedByMTV, drmp3z
kronikings, danahern, karn101, Majik Mushroomz, Matt P., Matt B., pio_masaki, Droidika, Wheelchairmitch, MrIcky, liquidhaste, jamiethemorris, rainabba
.SPECIAL THANKS.
Flyhalf205, x3demond3x[debugging]
dsb9938 [cmdline boot option]
x3demond3x [egl fix]
Jarocks [resized bootanimation/debugging], pio_masaki [debugging],
jcase [unlock], dees_troy [twrp], beaups, jcase, Dr_Drache, dsb9938 [S-OFF]
.... and of course the CyanogenMod team and those who laid the foundation for the DNA....
..WANT TO HELP? HERE ARE SOME DEBUGGING TIPS..1) Flash boot.img
2) On cmdline do "adb logcat"
Click to expand...
Click to collapse
If you're ever in the mood to donate, don't forget about the others that have helped advance the HTC DNA to new levels (e.g. dsb9938, jcase, Dr_Drache, beaups, CM team, or XDA for bringing us all together!). Although, I may be working on CM and it may seem like a completely different project, in many ways we all rely on each other to help make the DNA better.
Click to expand...
Click to collapse
I can't help you with specifics but the guys over on the nook color forums have great guides on building and may be amenable to questions if no one here gives you anything useful
sent from my unlocked and rooted droid DNA
jamesbra said:
I can't help you with specifics but the guys over on the nook color forums have great guides on building and may be amenable to questions if no one here gives you anything useful
Click to expand...
Click to collapse
Thanks. Brings me back to the days when I was writing some early scripts for the Nook Color... when you had to flash the "harder" way. Anyhow, it reminded me of just mounting each partition separately (/dev/block/mmcblk0pXX). Found kernel/system logs, just what I wanted.
What about radio??
Sent from my HTC6435LVW using xda premium
typeriz said:
What about radio??
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
That's a whole separate issue. We can have a Rom booting and usable without the ril working. Granted, this booting will most likely help with ril advancement.
Sent from outer space...
drewX2 said:
I've successfully built CM 10 on the DNA, however I'm stuck with debugging after booting in standby (assuming). For those that have built new roms on unsupported devices, how did you debug the boot process? Yes, I understand to use logcat/ddms/etc. I boot into standby with a black screen (no boot loop). Sdcard mounts once I get to black screen, however I built kernel from source as well so no hacks have been applied yet.
Also, when taking any kernel available right now, pulling it apart and remerging with no changes (just verifying process), I go into a boot loop on a working Rom (genome/ukb)
This is what I am doing to recreate boot.img:
Code:
(boot.img taking from DNA cubed kernel, I've renamed kernel and ramdisk)
unbootimg boot.img
mkbootimg --output boot.img --kernel kernel --ramdisk ramdisk.cpio.gz --cmdline 'console=ttyHSL0,115200,n8 androidboot.hardware=dlx user_debug=31' --board '' --base 80600000 --pagesize 2048
Any tips would be great so I can finish up and share. Seems so silly that I can't even remake a working boot.img after spending 20+ hrs working on CM10. It seems I'm a bit slow to get back into the swing of things since taking a hiatus from programming for several years.
Click to expand...
Click to collapse
I have gotten to the same point as you in my AOSP venture with the DNA. From my findings, without the correct kernel drivers being administered from the gate, the USB (debugging) features are not going to work properly. I am in the process of finding a kernel developer who is familiar with Sense (HTC) devices to build the proper kernel to make this possible. With the help of Dr_Drace I was able to put together a working DLX build tree and have successfully compiled FactoryROM (which is 4.2 AOSP based) but am stuck at the end of the boot process. And like you, I am unable to gather any logs due to the lack of USB access. We need a reliable kernel developer to get us past the hurdle. Unfortunately I am not one of them. As far as RIL, it's anyone's guess as to its functionality once we get things booting correctly. We have all of the drivers, it's just making them work together. :fingers-crossed:
MyComputerDoctor said:
I have gotten to the same point as you in my AOSP venture with the DNA. From my findings, without the correct kernel drivers being administered from the gate, the USB (debugging) features are not going to work properly. I am in the process of finding a kernel developer who is familiar with Sense (HTC) devices to build the proper kernel to make this possible. With the help of Dr_Drace I was able to put together a working DLX build tree and have successfully compiled FactoryROM (which is 4.2 AOSP based) but am stuck at the end of the boot process. And like you, I am unable to gather any logs due to the lack of USB access. We need a reliable kernel developer to get us past the hurdle. Unfortunately I am not one of them. As far as RIL, it's anyone's guess as to its functionality once we get things booting correctly. We have all of the drivers, it's just making them work together. :fingers-crossed:
Click to expand...
Click to collapse
I'm just going to try stripping as much away as I can to boot and then slowly add things back in. On a side note, I've made a working version of touch clockworkmod recovery. I am going to modify it to add some additional options before sharing (unless someone gets around to it before I do).
What I suggest doing is mounting /dev/block/mmcblk0p24 manually via working recovery. This is the log partition; system.log and kernel.log are written to it.
Please keep us updated on your progress. It would be greatly appreciated. And yes you may be part god.
Please try to keep this thread focused on development and free of clutter. The Thanks button still works just fine.
Do either of you have the device/vendor posted to Github by chance? I actually started putting one together but haven't had much time to actually make progress.
Which kernels have you used with source built Rom? Tried the stock kernel by chance? I always feel its a good starting point. Have either of you uploaded the zip? I can flash and take a look... They say two heads are better then one so if we're all working on the same thing I'm sure progress will be made! Lol
Sent from my HTC6435LVW using Tapatalk 2
Ill try to get it up or post a zip tonight (not workable, but see if you can troubleshoot ). I was off for a bit bit but now working four long shifts in a row.
I contacted cayniarb.. most familiar will remember him from all the tiamat htc kernels.. not sure if he will help but i sent him a link to the forum for him to take a look..
---------- Post added at 08:35 PM ---------- Previous post was at 07:53 PM ----------
since i am not versed in helping you guys ill will post cayniarbs comments in hopes something might give you a idea.. we talk breifly and when i say breifly it was only a few lines... " ok this isnt a unexpected problem the devs should try to straight up disabling problem drivers--- turning off usb means no debugging , but it might also make it boot---- as far the actual kernel changes for that it will consist of of rippin gour the sense usb drivers and replacing them with google driver.. by disable i mean just cut the init references out of the ramdisk"
hope this gives someone and idea that maybe they didnt have before.. sorry i can be no help- my skill dont lend to being this early in the project.
leech2082 said:
I contacted cayniarb.. most familiar will remember him from all the tiamat htc kernels.. not sure if he will help but i sent him a link to the forum for him to take a look..
---------- Post added at 08:35 PM ---------- Previous post was at 07:53 PM ----------
since i am not versed in helping you guys ill will post cayniarbs comments in hopes something might give you a idea.. we talk breifly and when i say breifly it was only a few lines... " ok this isnt a unexpected problem the devs should try to straight up disabling problem drivers--- turning off usb means no debugging , but it might also make it boot---- as far the actual kernel changes for that it will consist of of rippin gour the sense usb drivers and replacing them with google driver.. by disable i mean just cut the init references out of the ramdisk"
hope this gives someone and idea that maybe they didnt have before.. sorry i can be no help- my skill dont lend to being this early in the project.
Click to expand...
Click to collapse
Thanks for helping out anyway you can. Now that I've completed my work stretch, I can go back to working on this a bit. What he is saying is essentially what I am doing, however, the simple fact of taking a working boot.img, splitting it up, then remaking with zero changes and it it not working anymore has eluded me.
drewX2 said:
Thanks for helping out anyway you can. Now that I've completed my work stretch, I can go back to working on this a bit. What he is statins is essentially what I am doing, however, the simple fact of taking a working boot.img, splitting it up, then remaking with zero changes and it it not working anymore has eluded me.
Click to expand...
Click to collapse
Wink, wink!
D
.
dsb9938 said:
Wink, wink!
D
.
Click to expand...
Click to collapse
Haha judging by the amount of thanks I think we are all hoping that aosp is coming really soon for xmas and you guys are just playing us, haha. Thank you for your amazing work bringing the world of real android closer to reality
leech2082 said:
I contacted cayniarb.. most familiar will remember him from all the tiamat htc kernels.. not sure if he will help but i sent him a link to the forum for him to take a look..
---------- Post added at 08:35 PM ---------- Previous post was at 07:53 PM ----------
since i am not versed in helping you guys ill will post cayniarbs comments in hopes something might give you a idea.. we talk breifly and when i say breifly it was only a few lines... " ok this isnt a unexpected problem the devs should try to straight up disabling problem drivers--- turning off usb means no debugging , but it might also make it boot---- as far the actual kernel changes for that it will consist of of rippin gour the sense usb drivers and replacing them with google driver.. by disable i mean just cut the init references out of the ramdisk"
hope this gives someone and idea that maybe they didnt have before.. sorry i can be no help- my skill dont lend to being this early in the project.
Click to expand...
Click to collapse
Leech I actually worked with him two weeks ago to build an Tiamat AOSP kernel for the DNA. Since then I've had my birthday and 3 family members birthdays and now Christmas. The zip is still on my system waiting to be flashed We'll get it to work. The dudes built kernels for every single HTC device to date practically. I have faith.
Kernel building no longer issue. I just had one command left out which kept giving me a PITA. Now to find out which things can be eliminated from HTC and still boot.
And now to get the hardware to work properly lol. Battle has just begun. Great work guys. Will be downloading and attempting to fix some things after Xmas.
Sent from my DNA.
When did they add xxhdpi to aosp?
Sent from my SGH-I747 using Tapatalk 2
idkwhothatis123 said:
And now to get the hardware to work properly lol. Battle has just begun. Great work guys. Will be downloading and attempting to fix some things after Xmas.
Sent from my DNA.
Click to expand...
Click to collapse
Do you really have to wait until after Christmas? Come on.
:victory:
Hi,
This kernel/rom lets you connect an RT8187 USB Wifi adapter to your GT-P5210 and run aircrack-ng/airmon-ng/airodump-ng through Linux on Android.
Mind the noobness, I just compiled my first kernel(ever) and stuck it in someones image and it worked.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(worked untill i enabled the builtin wifi, lol)
After i bought one of these tablets I can't say I'm not a bit dissapointed about the amount of dev work on the GT-5210, (words go unspoken for DutchDanny, Angel_666, trevd)
It's an x86 device, anything should be compileable and runable without any arm mods (i'm looking at you kali linux) this thing should be owning the Nexus 7.
Tested with TWRP 2.7 recovery
Its built using builduntu, and from the P5210UEUAMI8 source, with the toolchain recommended in the Kernel Readme.
I followed this tutorial to enable driver support
And this detailed guide to compile the kernel and create a proper boot.img
Replaced the boot.img in Mod57's rom with my modified one. (god fed up with fastboot and usb issues on Win 8.1 and just flashed it, it worked. Thats my testing)
Mod57 said:
This is built using the Samsung GT-P5210 P5210UEUAMI8 [4.2.2] Jelly Bean base.
ORIGINAL THREAD
This is not debloated it's fat and sassy like Samsung intended it.
If you would like to debloat I highly recommend using DutchDanny's debloater which can be found here:
http://forum.xda-developers.com/showthread.php?t=2482582
Jelly Bean P5210UEUAMI8
Fully Deodexed
Rooted
BusyBox
Zipaligned
Extended Power Menu (Wanam Xposed)
Will Not Delete Internal SD
Thanks to:
DutchDanny
Angel_666
Zidkijah
and everyone else who has contributed to this device.
Download:
http://www.androidfilehost.com/?fid=23189362627838229
MD5: 79f732fefbaf7882bc7c814d3ac1e998
Click to expand...
Click to collapse
Once you have downloaded and verified Mod57's rom, open up the zip and replace boot.img with this one:
https://www.dropbox.com/s/9gfucdzsadciy66/boot.zip
MD5: 4dd95a78c78550586cf3c2f7953978ab boot.img
You must have a rooted device (I used TWRP 2.7, http://nasirtech.blogspot.dk/2014/03/root-p5210xxuanb4-android-422-stock.html)
Code:
Put the modified rom onto the sdcard
Go to recovery
Wipe Cache and dalvik-cache
Install the ROM
Reboot and enjoy
Once you have installed the kernel and it boots up, you must follow these steps to chroot into an ubuntu image and compile / install aircrack.
Code:
Download this image: ubuntu-13.10.LARGE.x86.ext2.v1.zip
from [url]http://sourceforge.net/projects/linuxonandroid/files/Ubuntu/13.10/x86/[/url]
and copy it to your sdcard
Thanks to jorgen_gustavsson for his excellent work [url]http://forum.xda-developers.com/showthread.php?t=2573441[/url]
1. Install busybox [url]https://play.google.com/store/apps/details?id=stericson.busybox[/url]
2. Install a vnc viewer [url]https://play.google.com/store/apps/details?id=android.androidVNC[/url]
3. Install [url]https://play.google.com/store/apps/details?id=com.zpwebsites.linuxonandroid[/url]
(Not sure, but open and close it once to be safe)
4. Copy bootscript.sh [url=http://forum.xda-developers.com/showthread.php?t=2573441]link to bootscript thread[/url] to /data/data/com.zpwebsites.linuxonandroid/files/ overwrite the old file.
bootscript.sh
(Thanks to xdadev: jorgen_gustavsson)
5. Unpack and Copy the ubuntu-13.10.LARGE.x86.ext2.img and .md5 to a place of your choosing on either internal or external sdcard.
6. Make a Linux on Android widget and point it to the img file you copied to your sdcard (ubuntu-13.10.LARGE.x86.ext2.v1.img).
7. Now click on the LOA widget you made in 6 and let linux ”bootup”
8. Press 'y' to check MD5 checksum
9. Connect vnc to localhost:5900 password ubuntu
Now to install Aircrack
# Libraries
sudo updatedb
sudo apt-get install build-essential
sudo apt-get install gcc
sudo apt-get install zlibg-dev
sudo apt-get install libssl-dev (or libssl-dev depending on your distribution)
#airolib-ng optional sqlite=true
sudo apt-get install libsqlite3-devel
#libnl optional libnl=true
sudo apt-get install libnl-genl-3-dev libnl-3-dev
#Required Extras
sudo apt-get install wireless-tools
sudo apt-get install net-tools
sudo apt-get install wicd-curses (or wicd-cli)
sudo apt-get install usbutils
sudo apt-get install wpasupplicant
sudo apt-get install dbus
# Download & unpack (or replace link with latest trunk)
wget [url]http://download.aircrack-ng.org/aircrack-ng-1.2-beta3.tar.gz[/url]
tar -zxvf aircrack-ng-1.2-beta3.tar.gz
cd aircrack-ng-1.2-beta3
# Make
sudo make libnl=false sqlite=false
sudo make install libnl=false sqlite=false
# or
make libnl=true;make libnl=true install
make install libnl=true;make libnl=true install
# or Airolib-ng support
make sqlite=true;make sqlite=true install
make install sqlite=true;make sqlite=true install
# Add binaries to path
export PATH=$PATH:/usr/local/sbin
# add the above line to below file for include path on startup
vim /home/ubuntu/.bashrc
# Update MAC OUI
airodump-ng-oui-update
Reboot and disable your internal wifi, connect your dongle, and get cracking.
This is what I spent my easter (and then some) doing, I hope someone can make good use of it. I can
Maybe someone can come along and add bcmon for the bcm4334 chipset
(Just maybe https://code.google.com/p/bcmon/source/browse/trunk/bcm4330/driver/src/bcmdhd/Kconfig?r=4 )
Any feedback and questions are welcome:
why didn't you use the latest source? -couldn't find it
Will this kernel work with xx rom? -probably not
Why aren't more roms including this? -dno, its in the menuconfig, should be easy
I've tried to give thanks where ever possible, let me know if you feel left out.
Ill come back tomorrow and clean up my post.
Best Regards
You my dear friend are a LEGEND
I'm also yoing to build an own kernel... And I think I'll add this feature too...
Sent from my GT-P5210 using Tapatalk
Keep having error while compiling kernel :"(
Daniel-TAz00 said:
Once you have downloaded and verified Mod57's rom
Click to expand...
Click to collapse
Thank your for your work. This is what I've been looking a long time for.
Please, would you provide a flashable zip of the rom with your kernel? It looks like I'm doing something wrong.
After flashing the modified rom my P5210 just keeps showing the wird boot logo and wont boot up at all.
Thanks in regard!
@Max4000 Do you realize that what Daniel-TAz00 original article is about!
He is showing us a way to run Aircrack-ng in a Ubuntu VNC session with our TAB3 wifi turned off but with a external USB WIFI Dongle!!!!.
He also suggest it will be nice if somebody, created the modification on our own TAB3 10.1 driver sources and compiled it in a new kernel. It was just a suggestion. Then a few commented but no buddy gave the final answer.
I did not follow his steps. I do not even understood why he start with a new TAB3 rom! And a new boot.img. I guess he gave that as a reference as how he did it.
@Jacker31 What is what you are trying to compile, your sources and steps? And what is the exact error?
This is an interested topic to me. But I been sick for more than a week.
r2d23cpo said:
@Max4000 Do you realize that what Daniel-TAz00 original article is about!
He is showing us a way to run Aircrack-ng in a Ubuntu VNC session with our TAB3 wifi turned off but with a external USB WIFI Dongle!!!!.
He also suggest it will be nice if somebody, created the modification on our own TAB3 10.1 driver sources and compiled it in a new kernel. It was just a suggestion. Then a few commented but no buddy gave the final answer.
I did not follow his steps. I do not even understood why he start with a new TAB3 rom! And a new boot.img. I guess he gave that as a reference as how he did it.
@Jacker31 What is what you are trying to compile, your sources and steps? And what is the exact error?
This is an interested topic to me. But I been sick for more than a week.
Click to expand...
Click to collapse
Well it have been a long story, I posted a thread about my error, here : http://forum.xda-developers.com/general/help/question-error-2-error-compiling-x86-t3047439 but in the end i found out i used the wrong toolchain. So i redownloaded the correct version and try again. It works but another error popup, its about some Broadcom error. I can successfully compile it after i disabled it in menuconfig. But instead of getting a Zimage i got a Bzimage. So Idk what to do with it. I googled a tones of information but still have no idea what to do with that bzimage. I used Kali Linux to compile and those kernel files are from http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=p5220 GT-P5220_SEA_KK_Opensource. Now i am trying to install builduntu and try to compile it again. Any tips or helps? especially with that bzimage
Daniel-TAz00 said:
Hi,
This kernel/rom lets you connect an RT8187 USB Wifi adapter to your GT-P5210 and run aircrack-ng/airmon-ng/airodump-ng through Linux on Android.
[...]
Once you have downloaded and verified Mod57's rom, open up the zip and replace boot.img with this one:
https://www.dropbox.com/s/9gfucdzsadciy66/boot.zip
MD5: 4dd95a78c78550586cf3c2f7953978ab boot.img
Click to expand...
Click to collapse
r2d23cpo said:
@Max4000 Do you realize that what Daniel-TAz00 original article is about!
He is showing us a way to run Aircrack-ng in a Ubuntu VNC session with our TAB3 wifi turned off but with a external USB WIFI Dongle!!!!.
He also suggest it will be nice if somebody, created the modification on our own TAB3 10.1 driver sources and compiled it in a new kernel. It was just a suggestion. Then a few commented but no buddy gave the final answer.
I did not follow his steps. I do not even understood why he start with a new TAB3 rom! And a new boot.img. I guess he gave that as a reference as how he did it.
Click to expand...
Click to collapse
I get it. He offers a kernel and tells to place it in an flashable zip of an other firmware.
This is not a new firmware, it's just a kernel.
Maybe someone can create a flashable zip of the kernel he has linked to. So I would try to flash it separately.
Max4000 said:
Maybe someone can create a flashable zip of the kernel he has linked to. So I would try to flash it separately.
Click to expand...
Click to collapse
I'll upload a complete zip for you, it's just gonna take a little while ....
OHH BOY!
This is Daniel-TAz00 thread, so he know what he is finally offering you when he said.
Daniel-TAz00 said:
I'll upload a complete zip for you, it's just gonna take a little while ....
Click to expand...
Click to collapse
Now what will be this "complete zip" he is offering! I hope is your desired kernel.
Max4000 said:
I get it. He offers a kernel and tells to place it in an flashable zip of an other firmware.
This is not a new firmware, it's just a kernel...
Click to expand...
Click to collapse
Max4000 In your quote
This kernel/rom lets you connect an RT8187 USB Wifi adapter to your GT-P5210 and run aircrack-ng/airmon-ng/airodump-ng through Linux on Android.
Click to expand...
Click to collapse
You are just looking in "This kernel/rom" at the beginning. While I am trying to tell you to look at the end "through Linux on Android."
So yes that kernel may have the "external RT8187 USB Wifi adapter driver" but in order to run "aircrack-ng/airmon-ng/airodump-ng" you need to run it through Linux....
Clearly the best approach is to use our internal wifi and some how run "aircrack-ng/airmon-ng/airodump-ng" without the need of "Linux" chrooted on Android.
@ Jacker31 I answered in your thread
http://forum.xda-developers.com/showpost.php?p=59310924&postcount=2
Here: https://www.dropbox.com/s/q27inuf6jmnhvdm/P5210UEUAMI8-Custom.zip?dl=0 942MB
It's what has been running on my tablet since I made the topic. If your tablet turns into a magic mushroom, it wasnt my fault
@r2d23cpo Thanks it was helpful for that Android Kitchen part How do you create a flashable .zip out of boot.img? I am thinking of using philz to create a custom rom backup and replace the boot.img with the one i modded.
@ Jacker31 I answered in your thread
http://forum.xda-developers.com/show...24&postcount=2
Click to expand...
Click to collapse
@Daniel-TAz00 Do you just edit the zimage or you even edited ur ramdisk? Eg: copy .ko modules into lib/modules/?
Jacker31 said:
@r2d23cpo Thanks it was helpful for that Android Kitchen part How do you create a flashable .zip out of boot.img? I am thinking of using philz to create a custom rom backup and replace the boot.img with the one i modded.
Click to expand...
Click to collapse
I did it with 7zip, open zip, replace boot.img, save zip, flash zip
Jacker31 said:
[MENTION=5688554]r2d23cpo[/MENTION
@Daniel-TAz00 Do you just edit the zimage or you even edited ur ramdisk? Eg: copy .ko modules into lib/modules/?
Click to expand...
Click to collapse
I compiled my zimage, and that was pretty much it i think
@Daniel-TAz00 Didn't expect was that easy XD just 7zip haha, gotta try it out after my dinner XD hope it works. I will post it if it works with p5220 since your post is for p5210. I have to agree with you that there is really rare to see Galaxy tab 3 10.1 series (00, 10 or 20(LTE)) development going, guess maybe there is limited advanced users on tab 3 10.1 series.
Is it possible to make a update.zip? If so how?
Daniel-TAz00 said:
Here: https://www.dropbox.com/s/q27inuf6jmnhvdm/P5210UEUAMI8-Custom.zip?dl=0 942MB...
Click to expand...
Click to collapse
@Daniel-TAz00 First thanks. Nice work. But can you tell us if your "942MB" file is just the same
This kernel/rom lets you connect an RT8187 USB Wifi adapter to your GT-P5210 and run aircrack-ng/airmon-ng/airodump-ng through Linux on Android.
Click to expand...
Click to collapse
In particular it is VNC Linux on Android
Now I think @Jacker31 is here for the fun of learning kernel compile and finding a way to implement "aircrack-ng/airmon-ng/airodump-ng" with TAB3 10.1 own Wifi and without Linux VNC. That is what I guess from his post.
Jacker31 said:
... it was helpful for that Android Kitchen part...
Click to expand...
Click to collapse
Thanks goes to the Greatest creator @osm0sis. Last time he complains on me for saying it was another Kitchen. So NOOOO It is the best Kitchen in xda. I know all this nice applications get hidden on so many post. @moonbutt74 was the one to point me to use AIK.
Jacker31 said:
... How do you create a flashable .zip out of boot.img? I am thinking of using philz to create a custom rom backup and replace the boot.img with the one i modded. ...
Click to expand...
Click to collapse
I will answer down
Jacker31 said:
... Do you just edit the zimage or you even edited ur ramdisk? Eg: copy .ko modules into lib/modules/?
Click to expand...
Click to collapse
You see Jacker31 is trying to include the needed driver in a kernel. But that is only a step.
So, which modules Tab3 10.1 own wifi? If so you need to recall that first we need to modify our driver bcmdhd to allow promiscuous communication!
Jacker31 said:
@Daniel-TAz00 Didn't expect was that easy XD just 7zip haha, gotta try it out after my dinner XD hope it works. I will post it if it works with p5220 since your post is for p5210. I have to agree with you that there is really rare to see Galaxy tab 3 10.1 series (00, 10 or 20(LTE)) development going, guess maybe there is limited advanced users on tab 3 10.1 series.
Click to expand...
Click to collapse
So I guess once you read this is going to be late, I was going you suggest to backup your own boot.img first! I do still you are a bit confuse it is not just ZIP!! see below
Code:
dd if=/dev/block/mmcblk0p10 of=/sdcard/mmcblk0p10.img bs=4096
Jacker31 said:
Is it possible to make a update.zip? If so how?
Click to expand...
Click to collapse
Yes, you see it is not just zip. In fact you need to make your own update.zip.
@Jacker31
1) So here is what you need to read. In this forum just search for "Edify", "updater script" and see how the script is build.
2) Please keep in mind that every device is different, in particular the partitions are in different places and in our case we are nor ARM but x86 or more technical we belong to the i686 family.
So if you unpack recovery.img an look inside the ramdiskfs you can find "/etc/recovery.fstab". By doing "cat /etc/recovery.fstab"
you will see
Code:
# mount point fstype device [device2]
/config ext4 /dev/block/mmcblk0p3
/cache ext4 /dev/block/mmcblk0p6
/system ext4 /dev/block/mmcblk0p8
/data ext4 /dev/block/mmcblk0p9 length=-16384
/recovery emmc /dev/block/mmcblk0p11
/boot emmc /dev/block/mmcblk0p10
/external_sd vfat /dev/block/mmcblk1p1
This tells you that "boot" is at partition "/dev/block/mmcblk0p10" and "recovery" at "/dev/block/mmcblk0p11".
So a valid script to introduce your new boot.img may read
Code:
ui_print("+++++++++++++++++++++++");
ui_print(" Galaxy Tab 3 gt-p52xx ");
ui_print("+++++++++++++++++++++++");
#
ui_print("Flashing boot.img");
ui_print("+++++++++++++++++++++");
#
#
package_extract_file("[COLOR="Blue"]boot.img[/COLOR]", "[COLOR="Blue"]/dev/block/mmcblk0p10[/COLOR]");
#
ui_print("Done");
ui_print("+++++++++++++++++++++");
Now I am attaching a update.zip skeleton. The needed part is in "update.zip\META-INF\com\google\android". There you will find "update-binary" valid for our x86 device. Observe how it is about 521KB. The ARM one is just around 125KB! Easily to distinguish. This "update-binary" is the program that will interpret the Edify commands that are store in "updater-script". So the "updater-script" holds the instructions.
In it you will find also "update.zip\META-INF\com\android". With "metadata" holds signature information when signed. And "otacert" with in fact holds the signature for ota validation. This files are only required when the update.zip is signed!! But that another process meant for distribution that I am not going to explain. In general when we test we do not sign the updtate.zip instead we disable that in the recovery menu, so that recovery accepts update.zip packages that are not signed. So I had include those for you knowledge but you can delete them if you want.
So the last file is "update.zip\boot.img". This is the file you are going to substitute and that you want to program.
And yes making the package is as simple of zipping all. Here is the important detail. When you zip the file you need to be in the same directory as the boot.img file is. So that the update.zip created do not contain an extra folder. In other words, when you double click a good update.zip you find quickly boot.img and META-INF folder. No extra folders.
Now waitttttt. That is just for your general knowledge. If you do use this info it is at your own risk. It is easily to do something wrong and break the device.
Example, Make sure you have a FULL battery before doing any firmware programing. The Charging mechanism is in boot image. If you have a bad boot image programing, then your device will not charge and if you get out of juice then you end up with a nonchargeable devices. It will feel that the device is dead, since you only way to charge will be to open the device and charge the battery separately!!!
OHHHH BOYY.
Now I am confuse! I guess it is my fault in assuming and not waiting for answers!
I guess Master Jacker31 was in fact into the Linux, he just release How to run Kali Linux on Galaxy Tab 3 10.1 => http://forum.xda-developers.com/gal...-to-run-kali-linux-galaxy-tab-3-10-1-t3050203
In any case I hope that my last post in update.zip is useful to him and others.
r2d23cpo said:
OHHHH BOYY.
Now I am confuse! I guess it is my fault in assuming and not waiting for answers!
I guess Master Jacker31 was in fact into the Linux, he just release How to run Kali Linux on Galaxy Tab 3 10.1 => http://forum.xda-developers.com/gal...-to-run-kali-linux-galaxy-tab-3-10-1-t3050203
In any case I hope that my last post in update.zip is useful to him and others.
Click to expand...
Click to collapse
@r2d23cpo
thanks for that answer, i am akinda into the linux, but there is plentyof stuff to get confused because of this x86 device and limited support from google. You are right, thats what i am going to research next, implement aircrack into the device it self and trying to find out that i can use the usb wifi dongle without turn off the build in wifi. Maybe you can surf facebook while attacking your neighbor network *joking* *its illegal anyways*
Well, Everything work well (I meant the script, I made some minor changes), except got stuck on that samsung Galaxy Tab 3 logo screen... I am trying to figure out why... I am trying to get a stock Boot.img and compile it again, since I used boot.img from philz back up...ANNNNNNNNNNNNND great bricked my device... not the first time though.
Jacker31 said:
Well, Everything work well, except got stuck on that samsung Galaxy Tab 3 logo screen... I am trying to figure out why...
Click to expand...
Click to collapse
I've got still the same problem.
WARNING: This won't work currently for the SM-G9730. I need a recovery.img(.lz4) from the latest firmware.
Here's a not-so-widely-tested fix for the spontaneous reboot that occurs after rooting the SM-G9750 and other Snapdragon S10 models.
tulth located this patch. If you read the description of that patch, it mentions a NULL pointer getting dereferenced in find_get_entry (such a thing tends to cause crashes in your average program, so when this happens in the kernel, it's not surprising that a crash and reset is the response). If you look at tulth's last_kmsg, my last_kmsg and G-ThGraf's last_kmsg from a G9730, you'll notice they all have one thing in common: SHTF at smaps_pte_range+0x29c. What's at that location on those devices' kernel? Why it's only find_get_entry(vma->vm_file. So yeah, it's the same bug, already known to Google and it's been fixed in their kernel tree since January. The bug is triggered externally by reading /proc/<pid>/smaps_rollup under certain conditions. You might be able to workaround this by disabling programs to get more free RAM, but The Only Way To Fix the Underlying Kernel Bug Is To Fix the Kernel Itself™.
We're probably not going to see a new kernel update until (if?) we get an update for the next major version of Android. We Snapdragon S10* users already have an older kernel compared to Exynos S10 owners (our 4.14.78 vs. their 4.14.85) and it's probably because of that they don't see this bug. So I think the idea of Samsung fixing this is a non-starter. While I did manage to build an SM-G9750 kernel from source (their instructions leave a lot to be desired) with that patch applied, I could not get my phone to boot the result.
I am not a programmer, but I do know just slightly enough to get the ball rolling and provide the fix that that aforementioned patch does in the opcode form that can be applied onto the existing kernel on the phone.
While I've not half-arsed it in the sense I took the easy way out (always having mss->check_shmem_swap set to zero is an easy one-liner workaround; however, freeing of unneeded SHM pages wouldn't happen, eventually causing your phone to crawl to a halt), I am not familiar with assembly language for any platform at all and, as such, I could not find a way to free up enough space in the show_smap function. So I jump quite far out into a chunk of the .text section where it's full of zeroes. I don't know anything about the ELF format to be able to tell you why this section of zeroes exists - I make the probably-wrong assumption it's perhaps a requirement of the ELF format if a linker that's very good at producing optimised code still bothers to output that or it's optimisation by alignment - but it's there and it's a good place to add extra code to on account of, you know, being empty and marked executable.
As far as I can see, where I have placed the code isn't referenced by anything else at all in the kernel but I can't be 100% certain on that. Nevertheless, I've been testing this on and off (I've had to manually initiate reboots in between for various reasons) myself for the past seven days or so and I've not noticed any adverse effects.
EDIT: Saying that, I think I'll try and move the code into load_module() when I get time because this kernel can't actually load modules (see below) thus much of the code there is pointless.The risk is yours, should you choose to apply this fix.
I would've liked to wrote this as a kernel module, being far easier to maintain, and hooked the relevant smap functions (in a similar vein to flar2's wp_mod and AleksJ's ric_mod) but thanks to the geniuses at Samsung, load_module() will always return early and the compiler accordingly realises it can optimise the function by excising all the code needed to actually load a module - there's no point in keeping unreachable code. Why Samsung bothered turning on mandatory module signing is beyond me because modules will never load! You can see this for yourself: insmod /system/vendor/lib/modules/wil6210.ko will always fail with "Exec format error", and that's a signed module built and shipped by Samsung themselves for their kernel. Anyway.
As long as the kernel version remains the same, it's likely, but not guaranteed, the same patches will work for future software updates from Samsung and all I'll have to do is update the compatibility list. If you try this on any other kernel version, the chances of not being able to boot are very high. The task of maintaining this doesn't enthuse me, but I'll continue to do so out of necessity, for I like having a rooted phone but not one that restarts at the worst of times.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I know people have reported longer uptimes than that on their phone before having a forced restart, but in my case, my phone has AOD enabled, the latest stable Magisk version installed and is running EdXposed. Before this fix, I've never seen an uptime longer than about 16 hours (usually less), regardless of whether the phone was in use or not, as getting multiple restarts in a day tends to have that effect.
As long as you only write to the recovery partition (and that's the only block device that this guide tells you to write to ), you should always be able to use Odin to reflash it to reverse this, the process being somewhat similar to flashing Magisk in the first place but with the notable exception of not needing to factory reset anything. The following flashing routine was adapted from Magisk, so my thanks to topjohnwu.
If someone has the bright idea of sharing their already-patched recovery.img because typing copy and pasting commands is hard, I'll point out the following: anybody flashing such an image should really make sure they're running the same firmware and Magisk version the image was designed for. (And after reading ianmacd's posts, topjohnwu supposedly doesn't like pre-patched images with Magisk being shared. I'll respect that, and so should you.)
I won't take any responsibility if this damages your phone. Perform the following at your own risk. If you agree, then:
If you haven't already, root the phone with Magisk. Make sure to keep a copy of the magisk_patched.tar somewhere on your computer so you can reflash it with ODIN if something goes wrong here. Always make sure Magisk is installed before modifying the recovery partition yourself. If you have a pending software update, install that with Odin and root that first before doing the following.
Set up ADB on your phone and computer
From your computer, adb shell into the phone
Run
Code:
uname -r
Only attempt to apply these patches if you get 4.14.78-16509050 back. For an older version, the bottom of this post has previous patches that may or may not apply. Or just update your phone.
Run
Code:
su
and then
Code:
rm -rf /data/local/tmp/q12kpwrk ; mkdir /data/local/tmp/q12kpwrk && cd /data/local/tmp/q12kpwrk
Run
Code:
mkdir recovery && cd recovery
Find the recovery partition on your phone by running:
Code:
recovery_blk="`readlink -f /dev/block/by-name/recovery`" ; [ -b "$recovery_blk" ] || echo "Eh, something's off here. Don't continue"
Dump it to a file by running:
Code:
dd if="$recovery_blk" of=recovery.img
Extract the kernel by running:
Code:
/data/adb/magisk/magiskboot unpack recovery.img || echo "Stop! Do not continue!"
If you see the warning message again on a new line, then stop.
Otherwise, if all went well with the step above (the message "Kernel is uncompressed or not a supported compressed type!" can be safely disregarded), then note that for any of these patches, if you don't get any matches or get more than one, then do not continue any further. Don't selectively apply any of these patches; it's all or nothing.
Apply the first patch by running:
Code:
/data/adb/magisk/magiskboot hexpatch kernel F7030032895240F9F64F00F9 F7030032FD10F997F64F00F9
Run
Code:
/data/adb/magisk/magiskboot hexpatch kernel 02000014C02E00F9E1630191 02000014ED10F997E1630191
If you have an SM-G9750/Snapdragon S10+: run
Code:
/data/adb/magisk/magiskboot hexpatch kernel F30300AAA1010035F40313AA750640F9890E41F83F7500F103010054AA02098BC10501B0407100D121B83191 F30300AA0D000014895240F9DF420239C0035FD600000000D22E40F94E02008BCE2E00F9C0035FD621B83191
OR if you have an SM-G9730/Snapdragon S10: there is currently no patch. Feel free to send me a recovery.img from the latest firmware and I'll adapt it
OR if you have an SM-G9700/Snapdragon S10e (thanks to Laikar_ for the recovery.img and testing): run
Code:
/data/adb/magisk/magiskboot hexpatch kernel F30300AAA1010035F40313AA750640F9890E41F83F7500F103010054AA02098BA10501D0407100D121B81D91 F30300AA0D000014895240F9DF420239C0035FD600000000D22E40F94E02008BCE2E00F9C0035FD621B81D91
Have the patched kernel placed into a new recovery image, new-boot.img, by running:
Code:
/data/adb/magisk/magiskboot repack recovery.img || echo "Stop! Do not continue!"
Check to see if new-boot.img isn't somehow larger than the recovery partition itself by running
Code:
[ `stat -c '%s' "new-boot.img"` -gt `blockdev --getsize64 "$recovery_blk"` ] && echo "Do not continue!"
Flash the new recovery image by running
Code:
cat new-boot.img /dev/zero >"$recovery_blk" 2>/dev/null
Run
Code:
sync ; sync ; sync ; reboot recovery
If the phone boots again, great! If you're stuck at the Samsung-only logo that fades in and out for many minutes, just restart the phone again whilst holding the recovery button combo to boot into Android with Magisk activated like normal.
You can rm -rf the /data/local/tmp/q12kpwrk folder afterwards to get some space back.
If your phone keeps restarting, or you automatically get put into semi-bootloader flashing mode, hold the bootloader button combo to get to the blue-background downloading mode and reflash magisk_patched.tar (and HOME_CSC) with Odin. If you didn't keep said file or a Magisk-patched recovery.img you can tar up with 7-Zip and get Odin to flash as AP, you'll need to download the latest firmware for your SM-G9750 with Frija or similar, reflash that and then follow the instructions to root your phone again with Magisk.
If you do get a reboot after applying this, looking at /proc/last_kmsg will indicate if it's something to do with this patch or something else entirely.
Q&A:
Q: Will I have to reapply this if I update Magisk from Magisk Manager with a direct install?
A: No.
Q: Will I have to reapply this if I update the phone's firmware?
A: Yes, but check the new kernel's version first and see if it's listed in the compatibility section. If not, then you'll need to wait for an update to this fix. And remember to make sure that Magisk is installed first before modifying the recovery partition yourself.
Q: I don't want to wait hours to see if my phone will restart out of the blue. How can I test for this bug?
A: A variation on the steps to reproduce here, you can do this:
Code:
su
dd if=/data/media/0/AP_G9750ZHU1ASF1_CL16082828_QB24224470_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar.md5 of=/dev/shm # or any very large file (3-4 GB, /dev/urandom might work). This fills up the allocated space for shared memory
cat /proc/*/smaps_rollup
If your kernel isn't patched, restart your phone certainly does. (Of course, you should probably run reboot recovery anyway if not because a full SHM isn't really conducive to a well-running Android session.)
Q: Do you have any other kernel patches?
A: Just the one, only tested on the SM-G9750, and it seems to not be needed at all - it has no bearing on this specific reboot issue anyway. This one disables one aspect of RKP. Again, I don't think this is actually needed on the S10+ , but Magisk still attempts to patch for this issue indiscriminately (probably for the benefit of older devices), although its patch will not apply to our kernel.
Code:
/data/adb/magisk/magiskboot hexpatch kernel 1FA50F7143010054491540B93FA50F71E30000544B0940B97FA50F71830000544A1940B95FA10F7168090054 1FA10F71810A0054491540B93FA10F71200A00544B0940B97FA10F71C00900544A1940B95FA10F7161090054
Q: Are you a dirty GPL violator, qwerty12?
A: No! What I am providing is the compiled form of the patch linked to in the beginning of this thread. If you want to understand what this does in lovely C, just look at that patch. Of course, I have to deal with this on the assembler level, so there is no source per se, just dump all the hex strings into an online disassembler. The first two magiskboot hexpatch invocations replace two existing instructions with jumps into the new code I add. The third hexpatch invocation adds the additional code implementing the patch - the original replaced instruction is executed, along with the code I added to set mss->check_shmem_swap to zero before vma->vm_file is checked for != NULL and for shmem_swapped to be added to mss->swap instead of replacing it.
Patches for older kernels:
4.14.78-16082828:
Use Magisk Manager to install the Busybox Magisk module. No, this is not optional. You can use a version of Busybox from another source, but note that this is the version I have personally tested all this with. Restart your phone anyway if you already have it installed; you want your phone's running state to be as fresh as possible to avoid the possibility of running into this bug while attempting to fix it.
Code:
/data/adb/magisk/magiskboot hexpatch kernel F7030032895240F9F64F00F9 F70300327ED15494F64F00F9
Code:
/data/adb/magisk/magiskboot hexpatch kernel 02000014C02E00F9E1630191 020000146ED15494E1630191
Code:
printf '\x89\x52\x40\xF9\xDF\x42\x02\x39\xC0\x03\x5F\xD6\x00\x00\x00\x00\xD2\x2E\x40\xF9\x4E\x02\x00\x8B\xCE\x2E\x00\xF9\xC0\x03\x5F\xD6' | busybox dd of=kernel bs=1 seek="$((0x017F9AAC + 20))" conv=notrunc
The magiskboot hexpatch equivalent of this was too large, so I settled for writing to a hard coded offset.
I have random reboot... will try this patch tomorrow.
Sent from my SM-G9750 using Tapatalk
Hi... already doing your patches... i thinks succesfully, because i dont have any error, and boot normally after last command.
So.... i have to wait if random reboot appear right ? *to test*
Thank you... will report in about 3 days
Hi,
Vuska said:
So.... i have to wait if random reboot appear right ? *to test*
Click to expand...
Click to collapse
You can run the commands under "Q: I don't want to wait hours to see if my phone will restart out of the blue. How can I test for this bug?" in the first post. If your phone restarts automatically when running cat, then your phone is still susceptible to restarting itself during use.
If it doesn't restart, then you need to run reboot recovery yourself immediately, but it means the fix was successfully applied.
PS D:\S10+\ADB platform-tools> ./adb devices
List of devices attached
R28M31K3DNZ device
PS D:\S10+\ADB platform-tools> ./adb shell
beyond2q:/ $ su
Permission denied
1|beyond2q:/ $
?????
N1ldo said:
PS D:\S10+\ADB platform-tools> ./adb devices
List of devices attached
R28M31K3DNZ device
PS D:\S10+\ADB platform-tools> ./adb shell
beyond2q:/ $ su
Permission denied
1|beyond2q:/ $
?????
Click to expand...
Click to collapse
do you already install busybox via magisk ? also there will be a pop up in your device to request access from computer. accept it
already enable usb debugging in developer menu ?
permission denied .... [emoji848] .. strange... already rooted right ?
Sent from my SM-G9750 using Tapatalk
Vuska said:
do you already install busybox via magisk ? also there will be a pop up in your device to request access from computer. accept it
already enable usb debugging in developer menu ?
permission denied .... [emoji848] .. strange... already rooted right ?
Sent from my SM-G9750 using Tapatalk
Click to expand...
Click to collapse
Yes.
As you can see in the prints below.
i try install another busybox to.
N1ldo said:
beyond2q:/ $ su
Permission denied
1|beyond2q:/ $
?????
Click to expand...
Click to collapse
Check your Magisk settings to see if you haven't turned off ADB superuser access and your apps list for a denied Shell entry.
qwerty12 said:
Check your Magisk settings to see if you haven't turned off ADB superuser access and your apps list for a denied Shell entry.
Click to expand...
Click to collapse
Thank you all ...:good::good:
Yes Shell was unauthorized root on Magisk application list :victory:
3 days now.... i can say it successfully fixed.... [emoji106][emoji106]
Thank you.
hope you will update too when new firmware arrives....
because i dont understand some code mean.... just follow and copy paste
Sent from my SM-G9750 using Tapatalk
*ASG7 firmware is out
I can provide a recovery.img from s10e (smg9700), also any way i can contact you for some help about building the kernel? I have been trying to do with s10e's one and i'm not having much success
FlatOutRU said:
*ASG7 firmware is out
Click to expand...
Click to collapse
Downloading...
is ASG7 can use this patches ?
Sent from my SM-G9750 using Tapatalk
FlatOutRU said:
*ASG7 firmware is out
Click to expand...
Click to collapse
Vuska said:
s ASG7 can use this patches ?
Click to expand...
Click to collapse
I'll download the update later and give it a once-over; however, I'll quote myself:
qwerty12 said:
As long as the kernel version remains the same, it's likely, but not guaranteed, the same patches will work for future software updates from Samsung and all I'll have to do is update the compatibility list.
Click to expand...
Click to collapse
Laikar_ said:
I can provide a recovery.img from s10e (smg9700), also any way i can contact you for some help about building the kernel? I have been trying to do with s10e's one and i'm not having much success
Click to expand...
Click to collapse
That would be appreciated, thanks. I can move the S10e into the "Patch not tested" section of the compatibility list.
I wish you'd have asked me this a few days ago, I deleted the kernel tree I had on my disk because I thought a new source ZIP from Samsung would be forthcoming for the new firmware. I'd've just attached a diff...
I did get the kernel to build but I could not get the result to boot. Some of the compiler warnings displayed during build didn't make it seem like I was going to get a working kernel image. I'll get back to you soon with some steps
qwerty12 said:
That would be appreciated, thanks. I can move the S10e into the "Patch not tested" section of the compatibility list.
I wish you'd have asked me this a few days ago, I deleted the kernel tree I had on my disk because I thought a new source ZIP from Samsung would be forthcoming for the new firmware. I'd've just attached a diff...
I did get the kernel to build but I could not get the result to boot. Some of the compiler warnings displayed during build didn't make it seem like I was going to get a working kernel image. I'll get back to you soon with some steps
Click to expand...
Click to collapse
I can't post links yet, tinyurl(dot)com/y537462u for the drive download link
Does EdXposed work for G9750?
qwerty12 said:
I'll download the update later and give it a once-over; however, I'll quote myself:
Click to expand...
Click to collapse
Its changed a bit
kakahoho said:
Does EdXposed work for G9750?
Click to expand...
Click to collapse
Yes.
FlatOutRU said:
Its changed a bit
Click to expand...
Click to collapse
Good call; there's now code at 0x017F9AAC + 20, probably not a good idea to overwrite that...
I was hoping the newer build date might have meant that Samsung applied the patch, meaning I could abandon this thread, but no such luck: I did the quick writing to /dev/shm test and my phone kernel panicked. Lovely.
I've updated the first thread with an updated patch. I followed through with my plan of moving my extra code into load_module() instead of the empty section of zeros as, thanks to Samsung's kernel developers' ineptness, that function will always fail - may as well make it early return and then use the extra space gained to store my code in.
Laikar_ said:
I can't post links yet, tinyurl(dot)com/y537462u for the drive download link
Click to expand...
Click to collapse
Thanks for the S10e recovery image, Laikar_. I've checked the recovery image's kernel and moved the S10e into the "Patch not tested" section. I'll write up some steps soon on building a kernel that won't boot
Anyway,
The S10 and S10e recovery images are not from ASG7, however, so I don't know if my newer patch applies to it but my old ones do. I think my newer one will do, too, but that's an educated guess.
Just like with the S10, anybody's welcome to try this on their S10e and let me know of the result.
qwerty12 said:
Yes.
Good call; there's now code at 0x017F9AAC + 20, probably not a good idea to overwrite that...
I was hoping the newer build date might have meant that Samsung applied the patch, meaning I could abandon this thread, but no such luck: I did the quick writing to /dev/shm test and my phone kernel panicked. Lovely.
I've updated the first thread with an updated patch. I followed through with my plan of moving my extra code into load_module() instead of the empty section of zeros as, thanks to Samsung's brainiac developers, that function will always fail - may as well make it early return and then use the extra space gained to store my code in.
Thanks for the S10e recovery image, Laikar_. I've checked the recovery image's kernel and moved the S10e into the "Patch not tested" section. I'll write up some steps soon on building a kernel that won't boot
Anyway,
The S10 and S10e recovery images are not from ASG7, however, so I don't know if my newer patch applies to it but my old ones do. I think my newer one will do, too, but that's an educated guess.
Just like with the S10, anybody's welcome to try this on their S10e and let me know of the result.
Click to expand...
Click to collapse
so the first post already update to 050 kernel right ?
mean after i updated my s10+ magisk etc.. i can do that all steps right ?
cool...
still not yet finished my download since yesterday... my internet down.. [emoji2357]
Sent from my SM-G9750 using Tapatalk
Vuska said:
so the first post already update to 050 kernel right ?
mean after i updated my s10+ magisk etc.. i can do that all steps right ?
Click to expand...
Click to collapse
Yep, the first post is updated for ASG7. Those steps are working on my SM-G9750 running it, anyway
Laikar_ said:
[...]any way i can contact you for some help about building the kernel? I have been trying to do with s10e's one and i'm not having much success
Click to expand...
Click to collapse
I'll mention again that I couldn't get the result to boot. If you work it out, please let me know. I hate loading kernel images into a disassembler
I did this on a Ubuntu 18.04.2 minimal installation. I figure that if you want to build a kernel then you, like me, have at least a working familiarity with GNU/Linux, so I won't go too in-depth.
First, install the packages needed to build:
Code:
sudo apt install git-core gnupg flex bison gperf build-essential zip zlib1g-dev libxml2-utils xsltproc unzip python bc libssl-dev
Download the toolchain mentioned in README_kernel.txt:
Code:
git clone --depth=1 https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9
Download Snapdragon LLVM Compiler for Android v6.0.9 - Linux64 from https://developer.qualcomm.com/software/snapdragon-llvm-compiler-android/tools and untar it somewhere on your system. (This isn't actually the exact compiler Samsung use - if you look at /proc/version on your phone, you'll see it says 6.0.10 - but this is the closest we mere mortals will get.)
Download the source code zip from Samsung and untar Kernel.tar.gz into a newly-created folder. Inside said folder, run chmod 644 Makefile ; chmod 755 build_kernel.sh.
Open build_kernel.sh in your favourite editor. Make the following changes:
Set BUILD_CROSS_COMPILE to the folder where aarch64-linux-android-gcc, aarch64-linux-android-ld etc. are after cloning from git. Make sure to leave the aarch64-linux-android- suffix at the end. For me, this line looks like this:
Code:
BUILD_CROSS_COMPILE=/home/fp/x/aarch64-linux-android-4.9/bin/aarch64-linux-android-
KERNEL_LLVM_BIN needs to be set to the location of the Clang binary downloaded from Qualcomm. For me, this line looks like this:
Code:
KERNEL_LLVM_BIN=/home/fp/x/93270/toolchains/llvm-Snapdragon_LLVM_for_Android_6.0/prebuilt/linux-x86_64/bin/clang
After both REAL_CC=$KERNEL_LLVM_BIN instances add
Code:
CFP_CC=$KERNEL_LLVM_BIN
(although I think this is the wrong way to do it, consider just disabling CONFIG_RKP_CFP)
Open the Makefile in your favourite editor. Find the following line
Code:
@echo Cannot use CONFIG_CC_STACKPROTECTOR_$(stackp-name): \
$(stackp-flag) not supported by compiler >&2 && exit 1
Remove the "&& exit 1". The proper way to fix this would be to set CONFIG_CC_STACKPROTECTOR_STRONG to n in the config file; however if you run clang --help, you'll see that -fstack-protector-strong is actually supported. Why turn off a useful security feature?
Run build_kernel.sh and the kernel should build (albeit with a metric crap-ton of warnings, which is just one reason why it's not surprising the resulting kernel won't boot)
I am trying to build a crdroid rom for the SM-T350. But i keep running into errors that im not sure how to fix.
steps i'v taken so far
Synced the CrDroid 9 repo
added a local manifest (this one https://github.com/Nubianprince/local_manifests/blob/master/crdroid-pie.xml)
repo synced again
Code:
repo sync -c --no-tags --no-clone-bundle -j2
git cloned this https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/
ran
Code:
export CROSS_COMPILE=/home/lividhen/crdroid/arm-eabi-4.8/bin/arm-eabi- && export ARCH=arm && export SUBARCH=arm
Code:
brunch gt58wifi
Ended with
Code:
(ninja: error: '/home/lividhen/crdroid/out/target/product/gt58wifi/kernel', needed by '/home/lividhen/crdroid/out/target/product/gt58wifi/boot.img', missing and no known rule to make it)
tried to build kernel, is that what i need to do?
Code:
(cd kernel/samsung/msm8916
ran
Code:
make menuconfig
then just saved with all the defaults, then ran
Code:
make msm8916_sec_gt58wifi_eur_defconfig)
ended with
Code:
make[2]: *** [scripts/Makefile.build:309: kernel/irq/irqdesc.o] Error 1
make[1]: *** [scripts/Makefile.build:455: kernel/irq] Error 2
make: *** [Makefile:834: kernel] Error 2
I feel as if I'm probably missing something important, I'm just not sure what. any help is appreciated. Do i need to provide more info? i am on WSL, but from what i'v heard, that shouldent make a difference.
Edit: ran make make VARIANT_CONFIG=msm8916_sec_gt58wifi_eur_defconfig again after running make clean and make mrproper in the kernel directory and got make: *** No rule to make target 'include/config/auto.conf', needed by 'include/config/kernel.release'. Stop
Try this.
Use this https://github.com/Nubianprince/local_manifests/blob/master/crdroid-pie.xml to update your crdroid-pie.xml file.
Delete device/samsung/msm8916-common
repo sync
. build/envsetup.sh && brunch gt58wifi
nubianprince said:
Try this.
Use this https://github.com/Nubianprince/local_manifests/blob/master/crdroid-pie.xml to update your crdroid-pie.xml file.
Delete device/samsung/msm8916-common
repo sync
. build/envsetup.sh && brunch gt58wifi
Click to expand...
Click to collapse
It is still throwing "ninja: error: '/home/lividhen/crdroid/out/target/product/gt58wifi/kernel', needed by '/home/lividhen/crdroid/out/target/product/gt58wifi/boot.img', missing and no known rule to make it
15:08:48 ninja failed with: exit status 1"
lividhen99 said:
It is still throwing "ninja: error: '/home/lividhen/crdroid/out/target/product/gt58wifi/kernel', needed by '/home/lividhen/crdroid/out/target/product/gt58wifi/boot.img', missing and no known rule to make it
15:08:48 ninja failed with: exit status 1"
Click to expand...
Click to collapse
In BoardConfigCommon.mk in msm8916-common folder what path are you using for TARGET_KERNEL_SOURCE and does it exist?
nubianprince said:
In BoardConfigCommon.mk in msm8916-common folder what path are you using for TARGET_KERNEL_SOURCE and does it exist?
Click to expand...
Click to collapse
It pointed twards kernel/samsung/msm8916 which no longer exists, so I changed it too kernel/samsung/evervolv, then I had a bunch of problems with the ncurses libs, but eventually got that sorted out, then FINALLY, it built successfully. Thank you.
Aaaaaand, audio not playing and camera is broken. How was this fixed?
lividhen99 said:
Aaaaaand, audio not playing and camera is broken. How was this fixed?
Click to expand...
Click to collapse
msm8916.mk & boardconfigcommon.mk update your audio config path.. change from TARGET_COPY_OUT_VENDOR to TARGET_COPY_OUT_SYSTEM
make clean && brunch gt58wifi
nubianprince said:
msm8916.mk & boardconfigcommon.mk update your audio config path.. change from TARGET_COPY_OUT_VENDOR to TARGET_COPY_OUT_SYSTEM
make clean && brunch gt58wifi
Click to expand...
Click to collapse
All the lines under audio already say TARGET_COPY_OUT_SYSTEM.
(also, quick off topic question, is the crdroid 6 usable yet? I'd guess not sence it hasn't been uploaded yet uploaded.)
lividhen99 said:
All the lines under audio already say TARGET_COPY_OUT_SYSTEM.
(also, quick off topic question, is the crdroid 6 usable yet? I'd guess not sence it hasn't been uploaded yet uploaded.)
Click to expand...
Click to collapse
How is this coming along?
nubianprince said:
How is this coming along?
Click to expand...
Click to collapse
Um... not. i'm not sure what else to do as i have never done this before . I guess i'll just keep poking around to see if i can do anything.
lividhen99 said:
Um... not. i'm not sure what else to do as i have never done this before . I guess i'll just keep poking around to see if i can do anything.
Click to expand...
Click to collapse
Maybe there is something missing from my git repos, I will update those this weekend.
nubianprince said:
Maybe there is something missing from my git repos, I will update those this weekend.
Click to expand...
Click to collapse
Okay, thanks.
Hey, I tried building with your latest commit, and I am not sure if that was supposed to fix anything,but it is still broken. I keep fiddling with the audio paths and can't seem to fix it ?
lividhen99 said:
Hey, I tried building with your latest commit, and I am not sure if that was supposed to fix anything,but it is still broken. I keep fiddling with the audio paths and can't seem to fix it ?
Click to expand...
Click to collapse
Did you do a clean build?
nubianprince said:
Did you do a clean build?
Click to expand...
Click to collapse
Yeah ? I'm just going to delete my entire android directory and start fresh.
okay, here is what i'm doing, just in case i'v done something terribly wrong. Initalize the crdroid repo, added crdroid-pie.xml to local_manifests, repo sync, then i try to build and it gives a liblights error so i comment out all of hardware/qcom/display-caf/msm8916/liblight/Android.mk and do a clean build.
Edit 1: I forgot to correct the kernel path in BoardConfigCommon.mk so i fixed that.
Edit 2: i am now getting build/make/core/shared_library_internal.mk:17: error: hardware/qcom/display-caf/msm8916/libmemtrack: Illegal use of OVERRIDE_BUILT_MODULE_PATH. which i wasn't getting before, so... potential progress?? i don't know.
lividhen99 said:
okay, here is what i'm doing, just in case i'v done something terribly wrong. Initalize the crdroid repo, added crdroid-pie.xml to local_manifests, repo sync, then i try to build and it gives a liblights error so i comment out all of hardware/qcom/display-caf/msm8916/liblight/Android.mk and do a clean build.
Edit 1: I forgot to correct the kernel path in BoardConfigCommon.mk so i fixed that.
Edit 2: i am now getting build/make/core/shared_library_internal.mk:17: error: hardware/qcom/display-caf/msm8916/libmemtrack: Illegal use of OVERRIDE_BUILT_MODULE_PATH. which i wasn't getting before, so... potential progress?? i don't know.
Click to expand...
Click to collapse
Sound like you messed something out in display-caf when you commented out liblight
okay, i got it to build again, i deleted display-caf and synced again, then commented the other of the two files defining liblights. now i'm back at the same issue again, neither camera nor audio works ?. all the audio paths in BoardConfigCommon.mk and msm8916.mk say TARGET_COPY_OUT_SYSTEM already, and i'm not sure what to do about the camera.
upload your device trees so I can take a look, I will upload my vendor trees and you can try building with those
nubianprince said:
upload your device trees so I can take a look, I will upload my vendor trees and you can try building with those
Click to expand...
Click to collapse
device/samsung
https://drive.google.com/open?id=11V3pcrDgMEId13l0bXG7inpyPUVx7FWp