Related
So while I was still learning about flashing, ROMs, Kernels, etc, I managed to get a CM9 build on my Captivate. However, I installed the build for smtd device instead of mtd device. Now when I go to install the latest nightly CM9 build (mtd version), it fails right away with an assert failure. I think it is because it is checking my device type and sees that I have the smtd version currently.
Is there an easy way around this? I've considered editing the install script in the zip file to bypass the assert. Would that work, or there a better way?
cgulka said:
So while I was still learning about flashing, ROMs, Kernels, etc, I managed to get a CM9 build on my Captivate. However, I installed the build for smtd device instead of mtd device. Now when I go to install the latest nightly CM9 build (mtd version), it fails right away with an assert failure. I think it is because it is checking my device type and sees that I have the smtd version currently.
Is there an easy way around this? I've considered editing the install script in the zip file to bypass the assert. Would that work, or there a better way?
Click to expand...
Click to collapse
Open the .zip file with winrar, then go to "\META-INF\com\google\android" and open the file "updater-script" with Notepad ++. Delete all the lines (The very beginning) that says: assert(getprop("ro.product.device") == "captivate" etc... save it, let winrar update the files. Then try flashing it again.
Thanks! That worked. That was what I suspected I needed to do. I can tell you this, it takes a LONG time to re-zip such a large file on a little under-powered netbook.
Nick0703 said:
Open the .zip file with winrar, then go to "\META-INF\com\google\android" and open the file "updater-script" with Notepad ++. Delete all the lines (The very beginning) that says: assert(getprop("ro.product.device") == "captivate" etc... save it, let winrar update the files. Then try flashing it again.
Click to expand...
Click to collapse
I've been having a similar problem, so I did this and was able to install the ROM, but it gets stuck in the boot animation. Any ideas?
UPDATE: Fixed it by formatting the boot and system partitions. I blame semaphore.
First things first, the ROM is NOT booting
This is a very early build of MIUI for the Xperia Z. It is based off the latest Cyanogenmod 10.1 RC5 release and the latest MIUI release for the Nexus 4.
All credits go to the FreeXperia team as well as the Cyanogenmod Team, whom without these forums would be very empty. Also credits to the MIUI team on this wonderful ROM
As mentioned, the ROM is not yet booting but hopefully together we can get it to work.
Progress:
I've currently managed to get it booting up to the boot animation but it freezes from there
Download - Here is my current progress so far if anyone wants to build upon it.
Download - DevHost mirror
Issues :
I need to add the lines
Code:
service shelld /system/xbin/shelld
class main
to init.rc within the ramdisk. However, the recompiled boot.img with the applied changes does not boot.
If anyone can apply these changes and get the kernel to boot it would be greatly appreciated!
Resolved, thanks to DooMLoRD
Logcat doesn't seem to work
Other issues are unknown at this moment in time.
To Do List:
[*]Compile a kernel with the ramdisk changes that actually boots
Fixed by DooMLoRD
Fix logcat on boot
Get ROM to actually boot!
Installation Instructions:
NOTE: ROM will not boot, these instructions are just for users who want to help out or debug. Thank you
Place ROM on SD card
Boot into recovery
Flash zip
Wipe data / factory reset
Reboot
Porting Steps:
These steps have mainly been taken from this thread, with the necessary changes needed.
Full credits go to the OP as well as many thanks to those who posted helpful suggestions and hints.
Step 1. Choose which ROM to use as base. I've decided to go with Cyanogenmod. I'm using the latest RC5 release, which I believe to be very
stable. However, you're welcome to use any other ROM as base but I'm unsure as to what the results may be.
Step 2. Choose ROM to port from. I originally used the MIUI ROM for the Nexus 4 but in future other devices, i.e. the Oppo Find 5, may prove to be a more viable option.
Step 3. Extract the contents of your base ROM to a folder. For example, C:\MIUI\CyanogenmodBASE\
You will have the following folders:
system
META-INF
You will also have the file boot.img
Open the folder named system. Now you will see the following folders:
addon.d
app
bin
etc
extras
fonts
framework
lib
media
semc
tts
usr
vendor
xbin
You will also have the file build.prop
Delete the following folders:
app
framework
media
fonts
Step 4.
Extract the contents of the ROM you're porting from to a folder. i.e. C:\MIUI\PortROM\
Copy the folders that you deleted from the previous step to the CyanogenmodBASE folder
Navigate to the lib folder, (located within the system folder of PortROM)
C:\MIUI\PortROM\system\lib
Copy the following files to the lib folder found in the system folder of CyanogenmodBASE
content-type.properties (used for themes)
liblbesec.so (Used for LBA guard, MIUI equivalent of SuperUser)
liblocSDK_2_5OEM.so (Used in location access)
libjni_resource_drm.so (Used for themes and DRM)
libshell.so (Shell service)
libshell_jni.so
libshellservice.so
Now, from the etc folder, (located within system folder)
Copy the file named telocation.idf , to the etc folder inside system in the CyanogenmodBASE folder.
Then, within the etc folder, navigate to the folder named permissions. Copy the following permission over to the etc folder inside the CyanogenmodBASE folder.
com.google.android.media.effects.xml
com.google.widevine.software.drm.xml
com.google.android.maps.xml
In the system folder of PortROM, navigate to xbin and copy and paste the following files to the xbin folder in CyanogenmodBASE.
su
shelld
That's all the folders and files that need to be copied over. You also need to unpack the kernel and apply the ramdisk changes that DoomLoRD did. Then you need to repack the kernel.
Finally add the system and META-INF folders as well as the repacked kernel to a zip file and you have your flashable ROM :good:
This guide is very messy and is quite rushed. I'll clean it up when I get time but I do apologise in advance. If there's anything you're unsure of about these steps just post a reply and I'll try to help out as soon as I can
I cross my fingers and hope that you can solve the problems. Bit great done this far, looking towards MIUI V5!
Sent from my C6603 using Tapatalk 4 Beta
fareeed said:
Issues :
I need to add the lines
Code:
service shelld /system/xbin/shelld
class main
to init.rc within the ramdisk. However, the recompiled boot.img with the applied changes does not boot.
If anyone can apply these changes and get the kernel to boot it would be greatly appreciated!
Logcat doesn't seem to work
Other issues are unknown at this moment in time.
Click to expand...
Click to collapse
post just the kernel.. i will add the changes u need...
also at which stage is the kernel u used getting stuck up?
PS: i tried downloading the ROM from the link you posted but the download never begins... may be u can provide alternate download link?
DooMLoRD said:
post just the kernel.. i will add the changes u need...
also at which stage is the kernel u used getting stuck up?
PS: i tried downloading the ROM from the link you posted but the download never begins... may be u can provide alternate download link?
Click to expand...
Click to collapse
Thanks Doom, adding DevHost Mirror now.
As for the kernel, I unpacked and repacked using championswimmers kernel kitchen. Editing and repacking is fine but when I flash the repacked kernel, I just get a single vibration but nothing on the screen. Have to hard reset and flash previous kernel to get it to boot again.
p.s. The guide I'm following said to leave a blank line at the end init.rc, could this have had any effect?
Here's the boot.img that I'm trying to edit
Update: Roughly 20 mins left for DevHost mirrorr :good:
Ahw, i love MIUI interface, with FullHD of Xperia Z and that colors will be wonderful!!
fareeed said:
Thanks Doom, adding DevHost Mirror now.
As for the kernel, I unpacked and repacked using championswimmers kernel kitchen. Editing and repacking is fine but when I flash the repacked kernel, I just get a single vibration but nothing on the screen. Have to hard reset and flash previous kernel to get it to boot again.
p.s. The guide I'm following said to leave a blank line at the end init.rc, could this have had any effect?
Here's the boot.img that I'm trying to edit
Update: Roughly 20 mins left for DevHost mirrorr :good:
Click to expand...
Click to collapse
here u go:
http://d-h.st/GsY
i have added the info u requested in the end of the init.rc file...
i have checked and the kernel booted on my Xperia Z...
i dont have the ROM so i cant test...
DooMLoRD said:
here u go:
http://d-h.st/GsY
i have added the info u requested in the end of the init.rc file...
i have checked and the kernel booted on my Xperia Z...
i dont have the ROM so i cant test...
Click to expand...
Click to collapse
Thanks Doom, much appreciated , 6 minutes left on the DevHost mirror guys
UPDATE: Here is the devhost mirror
Important
Instructions:
After download, replace boot.img in zip with newer boot.img that DooMLoRD has very kindly provided.
Place zip on SD card
Reboot into recovery
Backup (ROM isn't guaranteed to boot)
Flash zip
Wipe data / factory reset
Reboot
Then report here and see what happens. I'll test ASAP as well. Also if possible, please try and provide a logcat. It should be said that I was unable to get one the first time but hopefully someone can
Update 2: Just realised I was editing init.sh instead of init.rc whoops, well all in the name of learning I suppose. At least I know for next time haha
Is the kernel based on the Cyanogenmod kernel? Which recovery is included?
Michealtbh said:
Is the kernel based on the Cyanogenmod kernel? Which recovery is included?
Click to expand...
Click to collapse
Yep based on latest Cyanogenmod RC 5, I think the recovery is CWM 6.0.32
fareeed said:
Yep based on latest Cyanogenmod RC 5, I think the recovery is CWM 6.0.32
Click to expand...
Click to collapse
Thanks, should use recovery from the FOTAkernel partition then.
I'll test tomorrow if I get time
Tried using the newer kernel from DooMLoRD but still hangs at boot animation.
@DooMLoRD Do you know how I can get a log cat during the boot process so I can find out what's giving me errors? I tried the normal adb command but I'm guessing USB debugging needs to be on for that. I think there's something I need to edit in the build prop to force enable USB debugging on boot? Thanks for your help
I already tried to port miui with cm kernel and also it freeze on boot logo.
Will try to help you as much as i know starting from Monday.
Sent from my C6603 using xda premium
gm007 said:
I already tried to port miui with cm kernel and also it freeze on boot logo.
Will try to help you as much as i know starting from Monday.
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
Thanks, I appreciate any help I can get.
Main obstacle in my way is getting logcat to work on boot. If I can get that working, then I can get a better idea of what the errors are. I found some build prop stuff which might be worth a try
fareeed said:
Thanks, I appreciate any help I can get.
Main obstacle in my way is getting logcat to work on boot. If I can get that working, then I can get a better idea of what the errors are. I found some build prop stuff which might be worth a try
Click to expand...
Click to collapse
From which device are you porting?
I tried nexus4,but the problem is the full hd.
Sent from my C6603 using xda premium
1080P devices?
gm007 said:
From which device are you porting?
I tried nexus4,but the problem is the full hd.
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
I'm not interested in MIUI but you might find this interesting.
http://bbs.gfan.com/forum.php?mod=viewthread&tid=5906702
Just put it in Google translate
I just googled 1080P MIUI or something.
The Oppo Find 5 is a very similar device to the XperiaZ.
snowman77 said:
I'm not interested in MIUI but you might find this interesting.
http://bbs.gfan.com/forum.php?mod=viewthread&tid=5906702
Just put it in Google translate
I just googled 1080P MIUI or something.
The Oppo Find 5 is a very similar device to the XperiaZ.
Click to expand...
Click to collapse
Personally I think you can ask MIUI forum for help
it seems that miui team has devoted all time toward Xiaomi Phone and ignored the existence of Xperia Z
Type this command: adb -d logcat
On your pc Before booting the phone to get logcat.
Sent from my C6603 using xda premium
WOOWWWW!!!!
REally Really great news!! miui interface are wonderful and in full HD OOOOOoooOOO, no words!! i'm waiting for news about boot!!!
Can't wait
Sent from my Kindle Fire HD 7 using xda app-developers app
Yeah Finally a MIUI rom thank you very much for trying to develop it i can't use my smartphones without MIUI, thanx DoomLord too I've always loved your work since the xperia x10, Sorry for spamming..
Hello,
I currently have Tsunami X 5.6 android 4.2.2.
I want to update to Kitkat roms but I cant.
I get "status 7" error while trying to install.
I understood that it's because I have an old CWM recovery (6.0.3.2).
How do I update it?
Sorry for the n00b question..
Status 7 error is caused while the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing called “asserts”.
How To Fix Statue error:
DO A NANDROID BACKUP if you haven't done so already just in case...
1. Copy the ROM zip file to your computer and extract it using your favorite unzipping software.
2. Once unzipped, browse to the META-INF/com/ google/android directory. You will find two files called “update-binary” and “updater-script”.
3. Rename “updater-script” to “updater-script.txt” and open with your favorite text file editor.
4. Get rid of the line starting with “assert” to next semi-colon. Usually this is the first line or one of the first lines at the top of the text file.
5. Save file.
6. Rename “updater-script.txt” back to “updater-script”.
7. Rezip all the files you’ve unzipped.
8. Copy the new, edited zip file to your phone.
9. Try re-installing ROM, now it should install fine without Status 7 error.
-MaoR- said:
Hello,
I currently have Tsunami X 5.6 android 4.2.2.
I want to update to Kitkat roms but I cant.
I get "status 7" error while trying to install.
I understood that it's because I have an old CWM recovery (6.0.3.2).
How do I update it?
Sorry for the n00b question..
Click to expand...
Click to collapse
If the previous answer is too complicated for you, just flash CM10.2 that will do proper partition for the latest ROMs and give you updated CWM recovery with which you can flash any KK rom. Just reboot once intonthe OS, then back to recovery and flash a KK rom. Don't forget to manually wipe /system before installing KK.
You will need to flash zip twice, as first time it will disolay warning of repartition and abbort with status 7. By next attempt it will work flawless.
pryerlee said:
Status 7 error is caused while the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing called “asserts”.
How To Fix Ststue error:
DO A NANDROID BACKUP if you haven't done so already just in case...
1. Copy the ROM zip file to your computer and extract it using your favorite unzipping software.
2. Once unzipped, browse to the META-INF/com/ google/android directory. You will find two files called “update-binary” and “updater-script”.
3. Rename “updater-script” to “updater-script.txt” and open with your favorite text file editor.
4. Get rid of the line starting with “assert” to next semi-colon. Usually this is the first line or one of the first lines at the top of the text file.
5. Save file.
6. Rename “updater-script.txt” back to “updater-script”.
7. Rezip all the files you’ve unzipped.
8. Copy the new, edited zip file to your phone.
9. Try re-installing ROM, now it should install fine without Status 7 error.
Click to expand...
Click to collapse
tetakpatak said:
If the previous answer is too complicated for you, just flash CM10.2 that will do proper partition for the latest ROMs and give you updated CWM recovery with which you can flash any KK rom. Just reboot once intonthe OS, then back to recovery and flash a KK rom. Don't forget to manually wipe /system before installing KK.
You will need to flash zip twice, as first time it will disolay warning of repartition and abbort with status 7. By next attempt it will work flawless.
Click to expand...
Click to collapse
Thanks guys.
I actually did flash CM 10.2 just before even seeing the your comments.
It worked great and now I actually think on staying with this ROM lol..
It's very clean and nice.
Thanks again!
[Sounds][Bootanimation][Recovery Flashable .zip] Stock Nexus 6 Sounds & Bootanimation
Hey guys,
Here's a recovery flashable .zip containing all the default Nexus 6 sounds & bootanimation. Initially I made this for myself, because I don't like the bootimage & sounds included in CM12; but I figured there might be some people that might be interested in .zip.
I pulled the files from a stock Nexus 6 ROM. FYI, the sounds found in Nexus 6 is device specific (Neither AOSP or other Nexus devices share the same sounds)
This will REPLACE everything in /SYSTEM/MEDIA into the stock bootanimation and sounds found in a Nexus 6.
Contents of the attached .zip:
Ringtones (12 files)
Notifications (11 files)
Alarms (9 files)
UI (24 files, which includes keyboard sounds, screen un/lock, wirelesscharging, nfc…, and a few others)
And lastly, the stock Nexus 6 bootanimation
Instruction
Copy the attached .zip file into your phone (or if you know what you're doing, you can just sideload it through recovery & ADB)
Boot into a custom recovery
Make a backup of your ROM
Flash the attached .zip
???
PROFIT!
EDIT:
The attached .zip has been edited to set permission, as per suggestion by @xanaxdroid. Thanks!
The standard disclaimer of flashingallthingsfromXDA applies (I'm not responsible if your phone blows up, bricked, melts, and possibly many other horrible things).
Mildly nerdy things (just my non-sense):
I'm completely new to making my own flashable .zip; so if I'm doing something wrong please tell me!
I've decided it's best to delete existing /system/media/. I see very little point keeping the sound files I dislike in the first place.
after deleting the previous 'media' directory, the script will copy the new 'media' directory into /system/media. This is the step where the script will put all the stock Nexus 6 sounds & bootimage in place.
since I flash a nightly CM12 ROM almost everyday, I will be flashing this .zip after the ROM. There's a possibility that if you flash a new ROM, the Nexus 6 sound files will be replaced. Simply re-flash the attached .zip again ;P.
I should probably set permission, but I'm not too sure how I would go about doing that yet ;P. But hey, it works!
Hey,
Can't comment on the technical side of things (permissions) but thank you so much for this. It always bugged me on the nexus 5 when stock and aosp were different.
This is perfect and I'll keep this should I want the sounds back. I really quite like them.
Cheers
tremblingwater said:
Hey,
Can't comment on the technical side of things (permissions) but thank you so much for this. It always bugged me on the nexus 5 when stock and aosp were different.
This is perfect and I'll keep this should I want the sounds back. I really quite like them.
Cheers
Click to expand...
Click to collapse
You're very welcomed! I'm glad to know I'm not the only one getting irked by the stock AOSP sounds!
Use this as your script to set permissions: Here
Sent from my Nexus 6
xanaxdroid said:
Use this as your script to set permissions: Here
Sent from my Nexus 6
Click to expand...
Click to collapse
Thanks! I've updated the first post & attached .zip to include the updated 'updater-script'.
can i flash this on my i9300 running cm12?
Noob question: Will this only work for Nexus 6? Just tried flashing to my S5 and it's hung at startup screen, where it just says "Samsung Galaxy S5"
hidea said:
Hey guys,
Here's a recovery flashable .zip containing all the default Nexus 6 sounds & bootanimation. Initially I made this for myself, because I don't like the bootimage & sounds included in CM12; but I figured there might be some people that might be interested in .zip.
I pulled the files from a stock Nexus 6 ROM. FYI, the sounds found in Nexus 6 is device specific (Neither AOSP or other Nexus devices share the same sounds)
This will REPLACE everything in /SYSTEM/MEDIA into the stock bootanimation and sounds found in a Nexus 6.
Contents of the attached .zip:
Ringtones (12 files)
Notifications (11 files)
Alarms (9 files)
UI (24 files, which includes keyboard sounds, screen un/lock, wirelesscharging, nfc…, and a few others)
And lastly, the stock Nexus 6 bootanimation
Instruction
Copy the attached .zip file into your phone (or if you know what you're doing, you can just sideload it through recovery & ADB)
Boot into a custom recovery
Make a backup of your ROM
Flash the attached .zip
???
PROFIT!
EDIT:
The attached .zip has been edited to set permission, as per suggestion by @xanaxdroid. Thanks!
The standard disclaimer of flashingallthingsfromXDA applies (I'm not responsible if your phone blows up, bricked, melts, and possibly many other horrible things).
Mildly nerdy things (just my non-sense):
I'm completely new to making my own flashable .zip; so if I'm doing something wrong please tell me!
I've decided it's best to delete existing /system/media/. I see very little point keeping the sound files I dislike in the first place.
after deleting the previous 'media' directory, the script will copy the new 'media' directory into /system/media. This is the step where the script will put all the stock Nexus 6 sounds & bootimage in place.
since I flash a nightly CM12 ROM almost everyday, I will be flashing this .zip after the ROM. There's a possibility that if you flash a new ROM, the Nexus 6 sound files will be replaced. Simply re-flash the attached .zip again ;P.
I should probably set permission, but I'm not too sure how I would go about doing that yet ;P. But hey, it works!
Click to expand...
Click to collapse
thanks for this. aosp and cyan are annoying in which the ui sounds sound like jelly bean.
thanks for sharing this!...
what am I missing I flashed this on my AT&T Nexus 6 thats riding on the Verizon Network and I still get the awful AT&T boot animation and sounds.
remlle said:
what am I missing I flashed this on my AT&T Nexus 6 thats riding on the Verizon Network and I still get the awful AT&T boot animation and sounds.
Click to expand...
Click to collapse
You have to go to OEM/media and rename the boot animation.zip
Is there a zip that doesn't contain the bootanimation??
Sent from my Nexus 6 using Tapatalk
thx, on my lg optimus g e975 works great
hidea said:
Hey guys,
Here's a recovery flashable .zip containing all the default Nexus 6 sounds & bootanimation. Initially I made this for myself, because I don't like the bootimage & sounds included in CM12; but I figured there might be some people that might be interested in .zip.
I pulled the files from a stock Nexus 6 ROM. FYI, the sounds found in Nexus 6 is device specific (Neither AOSP or other Nexus devices share the same sounds)
This will REPLACE everything in /SYSTEM/MEDIA into the stock bootanimation and sounds found in a Nexus 6.
Contents of the attached .zip:
Ringtones (12 files)
Notifications (11 files)
Alarms (9 files)
UI (24 files, which includes keyboard sounds, screen un/lock, wirelesscharging, nfc…, and a few others)
And lastly, the stock Nexus 6 bootanimation
Instruction
Copy the attached .zip file into your phone (or if you know what you're doing, you can just sideload it through recovery & ADB)
Boot into a custom recovery
Make a backup of your ROM
Flash the attached .zip
???
PROFIT!
EDIT:
The attached .zip has been edited to set permission, as per suggestion by @xanaxdroid. Thanks!
The standard disclaimer of flashingallthingsfromXDA applies (I'm not responsible if your phone blows up, bricked, melts, and possibly many other horrible things).
Mildly nerdy things (just my non-sense):
I'm completely new to making my own flashable .zip; so if I'm doing something wrong please tell me!
I've decided it's best to delete existing /system/media/. I see very little point keeping the sound files I dislike in the first place.
after deleting the previous 'media' directory, the script will copy the new 'media' directory into /system/media. This is the step where the script will put all the stock Nexus 6 sounds & bootimage in place.
since I flash a nightly CM12 ROM almost everyday, I will be flashing this .zip after the ROM. There's a possibility that if you flash a new ROM, the Nexus 6 sound files will be replaced. Simply re-flash the attached .zip again ;P.
I should probably set permission, but I'm not too sure how I would go about doing that yet ;P. But hey, it works!
Click to expand...
Click to collapse
Will this work on custom ROMs?
DSDONE said:
Will this work on custom ROMs?
Click to expand...
Click to collapse
Working
Sent from my Nexus 6 using Tapatalk
Nice!
Sent from my Nexus 6 using Tapatalk
Is there more boot sounds? If there are were can I find them?
H-AS Pharma V.I.P
Hi, can you please include the splash logo of nexus 6?
Hi. It would be possibile create a flashable zip with the new only google boot animation released with nougat? thanks!
Hello guys, I'm here to show you how to fix it without repeatedly turning it on and off. (I provided the stock bluetooth for you guys, that don't have it)
This is only for LTE jem, sorry for any convenience. (For bluetooth.)
1. Download this https://www.dropbox.com/s/29pw4nm27pgl8aj/Bluetooth fix.rar?dl=0
2. Extract it.
3. Replace /System/etc/Bluetooth/bcm2076_20mhz.hcd with BCM2076_26MHZ.HCD
4. Replace /System/vendor/firmware/bcm2076_20mhz.hcd with bcm2076_20mhz.hcd (The one I provided for you)
Then tada! Bluetooth works, you can only connect to compatible devices it seems but bluetooth finally works.
Now onto how to fix amazon jem not being recognized, on your pc/laptop.
I'm going to be honest here, this will be very short lol.
So anyways, go to this link https://windows10skill.com/kindle-fire-not-recognized-on-windows-10/#2 and follow the steps provided. Method 2 helped me, so try that first if you want. (This can work on windows 7 too, I forgot where I found it at but you can try following it still.)
That's all I have, for now. I hope all of you guys get everything fixed! Please let me know if this was helpful for you, I would appreciate it.
This RAR file won't open
Out of curiosity, I tried this with the latest CRdroid 3.8.7 from @transi1 in the other thread (which is useless because the ROM has functional bluetooth out of the box, at least with keyboards and mice). I was able to download and unpack the RAR, and install the files as described (had to remount /system for read-write in an adb shell in order to write in those directories). However, after replacement, the bluetooth didn't work any more, completely dead. When I restored the original files, it started working again. Maybe this is only for the LTE variant of the Jem (which reportedly has another Bluetooth chipset)?
EDIT : I checked that the HCD file above differs from the original one built into the ROM.
bapi28 said:
Out of curiosity, I tried this with the latest CRdroid 3.8.7 from @transi1 in the other thread (which is useless because the ROM has functional bluetooth out of the box, at least with keyboards and mice). I was able to download and unpack the RAR, and install the files as described (had to remount /system for read-write in an adb shell in order to write in those directories). However, after replacement, the bluetooth didn't work any more, completely dead. When I restored the original files, it started working again. Maybe this is only for the LTE variant of the Jem (which reportedly has another Bluetooth chipset)?
EDIT : I checked that the HCD file above differs from the original one built into the ROM.
Click to expand...
Click to collapse
Oh my god, I'm so sorry I forgot to mention this is only for lte devices. Sorry!
Understood step 4. But on step 3 when it states replace a file with a file having a different name, does that mean 1) delete original file and put new file in that folder, or 2) rename new file to existing files name and copy over top of existing file replacing it?
Ok, answered my own question and figured it out.
I did not have such a file in the /System/etc/Bluetooth folder.
I renamed the 26mhz file to 20mhz and replaced (overwrote) the file in the /System/vendor/firmware folder.
It is working great finally after issues for the past few years. Awesome. Thanks.