Database Develop

[Q] Upgraded to "Overcome - Gingerbread", /efs folder empty

Hi guys,
Looking for helps here.
First I want to thank the guy created the "Overcome for Gingerbread", it comes w/ a great details instruction and I successfully upgraded.
My tab was original from Bell Canada, the phone feature was locked. I was able to unlock it by modifying the nv_data.bin file...
But now after I upgraded to Gingerbread, my phone feature is disabled again so I suppose I should do the whole unlock process again. However when I looked for the nv_data.bin file, the directory /efs is empty?!?!?!. Can someone help me here?
Thanks,
Edit: I found a nv_data.bin file on my laptop (not sure if it's the orginial one), trying to copy it to the /efs folder on the tablet, but I got error "not enough space"...

What program u using to copy with. Put that file on the SD card first from your PC.
Then get EF File Explorer rooted, and copy that from the SD card to the /efs directory

The nv_data.bin edit unlocks the tablet to allow use on other carriers like rogers, fido etc.
It does not provide phone usage, you need to flash a european rom to enable the phone,
then you need to flash a suitable modem to allow 3G data and phone, then edit your apn info.
Are you sure efs is empty, maybe your no longer rooted and can't see it?

You get the not enough space error because you have most probably renamed the original file and are trying to copy the new one in the directory. Delete the file and also the.md5 correspondent (it will be recreated on reboot.
P

Thanks for all the replies guys, but my problem is still there.
@Sonictab: I'm rooted and I'm sure that my /efs folder is empty.
@StarLog: I'm using Super Manager to copy the file
Now I can't even download files from the browser nor using the market place to download any apps. Something went wrong and I'm not sure what. Should I downgrade?

problem with replacing gps.conf

Hi,
I hope this is the write location for my post.
I have a HTC ONE rooted, android 4.3
I have a problem with my GPS: it doesn't lock any satellite. Reading on forum, I found that the problem may be the setting of gps.conf file in /system/etc.
In fact, checking it, I found that the NTP_SERVER set was for north.america, while I'm in Europe.
I would like to modify or replace it, but I'm experiencing some problem. Using Root Browser it seems to be able to modify it, but after rebooting the device it is exactly the same before the editing. I tried using other editors as ES File Explorer, but when I try to modify the file, it says "read only file system".
It makes me thing that also the other editor is not able to modify the file, since after reboot it is actually un-edited.
What do you think? how can I actually write in file system and actually modify gps.conf?
Thank you in advance
Let me add another detail: I tried to create a new empty file in the same folder with Root Browser. It seems to be able to create it, but after rebooting the device it desappears..so I guess I actually can't modify/write in the file system..

aerosmike said:
Hi,
I hope this is the write location for my post.
I have a HTC ONE rooted, android 4.3
I have a problem with my GPS: it doesn't lock any satellite. Reading on forum, I found that the problem may be the setting of gps.conf file in /system/etc.
In fact, checking it, I found that the NTP_SERVER set was for north.america, while I'm in Europe.
I would like to modify or replace it, but I'm experiencing some problem. Using Root Browser it seems to be able to modify it, but after rebooting the device it is exactly the same before the editing. I tried using other editors as ES File Explorer, but when I try to modify the file, it says "read only file system".
It makes me thing that also the other editor is not able to modify the file, since after reboot it is actually un-edited.
What do you think? how can I actually write in file system and actually modify gps.conf?
Thank you in advance
Let me add another detail: I tried to create a new empty file in the same folder with Root Browser. It seems to be able to create it, but after rebooting the device it desappears..so I guess I actually can't modify/write in the file system..
Click to expand...
Click to collapse
You need an unsecured kernel (/system writable) to write to /system partition of the htc one, not only root.. Otherwise, all changes will be reverted at reboot like you are experiencing.
Kernels for htc one here
And note that modifying/deleting files in /system will probably prevent you to install future ota unless you revert the change you have made. There is a md5 checksum of many files in /system before the ota installs. If the md5 cheksum doesn't match then the ota will not install. This might not apply to the .conf file you want to edit but just in case, make a backup of that file before. So if the next ota fail, you'll know why.

alray said:
You need an unsecured kernel (/system writable) to write to /system partition of the htc one, not only root.. Otherwise, all changes will be reverted at reboot like you are experiencing.
Kernels for htc one here
And note that modifying/deleting files in /system will probably prevent you to install future ota unless you revert the change you have made. There is a md5 checksum of many files in /system before the ota installs. If the md5 cheksum doesn't match then the ota will not install. This might not apply to the .conf file you want to edit but just in case, make a backup of that file before. So if the next ota fail, you'll know why.
Click to expand...
Click to collapse
Thank you very much

[Q] Problems with original firm install

Hi! When I install system.img this problem appears, sp space in not enough and I can't make work the wifi and the bluetooth, help! Sorry for my english, it's really bad, I hope you can understand me

Rezakorn said:
Hi! When I install system.img this problem appears, sp space in not enough and I can't make work the wifi and the bluetooth, help! Sorry for my english, it's really bad, I hope you can understand me
Click to expand...
Click to collapse
Hello Rezakorn,
From what I understand, the "sp space is not enough" message is harmless and will not affect the operation of your device.
I can help you with the WiFi and Bluetooth.
I need you to use "Root Browser" to open the /persist folder.
It should have these 4 files inside:
.bt_nv.bin
WCNSS_qcom_wlan_nv.bin
WCNSS_qcom_wlan_nv_calibration_persist.bin
WCNSS_qcom_wlan_nv_regulatory_persist.bin
I have a hunch that you are MISSING your WCNSS_qcom_wlan_nv.bin file! You see, this file is NOT restored when you flash back to stock. The persist partition is NEVER supposed to be erased. This means that the ONLY place you can get the missing file is from another member who owns a Moto X.
Check the /persist folder. Let me know if the file IS missing. If so, I will provide you with it. Once you place the file back in the correct location and change permissions, WiFi and bluetooth will start working again.

Best partition for custom bootanimation in Android 5+

I open this up to the broader community for discussion: Where do you think custom bootanimations should be stored on Lollipop devices?
Android 5.0 introduces a new /oem partition, that allows for a /oem/media/bootanimation.zip file that seems to take precedence over a system/media/bootanimation.zip file (although I haven't checked AOSP source yet to confirm the exact logic). So far only AT&T+Motorola has utilized this functionality on the AT&T-branded Nexus 6, although I imagine many more OEMs will follow, given the added simplicity it provides.
Given this new option, I humbly suggest that the bootanimation community collectively decide to start placing their bootanimations in oem/media/ (via manual directions and flashable zips) for Lollipop devices, for a number of reasons:
- If a device has a pre-loaded /oem/media/bootanimation.zip, the current flashable zips and manual directions to place at /system/media/bootanimation.zip simply will not work (/oem takes precedence)
- Placing the animation on the /oem partition will persist through an OTA update, ROM update, etc.
- Placing the animation on the /oem partition preserves the ability to receive OTA updates, while placing on the /system partition causes Android 5.0+ updates to fail
Ideally, all flashable zips would contain an updater-script that is more thoughtful than all that I've seen to date; specifically testing for an /oem partition and reacting appropriately.

I haven't looked at source yet, but it's interesting to note that /oem/media/bootanimation.zip seems to supercede /system/media/bootanimation.zip (if /oem is present, then only /oem matters), however /oem/media/audio is additive (ringtones and notifications from both /oem and /system are available to the user).

there are only 2 places to boot a boot animation into.. 1st is /system/media/, but its temporary there, and will get replaced when you flash a rom. 2nd place is /data/local/, there it will not get replaced if you flash a rom.

DA6030 said:
I haven't looked at source yet, but it's interesting to note that /oem/media/bootanimation.zip seems to supercede /system/media/bootanimation.zip (if /oem is present, then only /oem matters), however /oem/media/audio is additive (ringtones and notifications from both /oem and /system are available to the user).
Click to expand...
Click to collapse
That's because audio is selected out of a picklist whereas you cannot choose a boot loader.
Its always been the case that boot animation in /data/local will take over /system/media.

rootSU said:
Its always been the case that boot animation in /data/local will take over /system/media.
Click to expand...
Click to collapse
D'oh, I had forgotten about /data/local. So, that means there are three locations now.
/oem/media is documented in the AT&T Nexus 6 thread, although I'm not sure anyone's checked source to see how it's implemented, nor tested to see where it falls in precedence to /data/local.
http://forum.xda-developers.com/showpost.php?p=56942290&postcount=11
And for reference, looking at the Shamu build.prop, it looks like the oem.prop items are imported explicitly into the build.prop, so the precedence there is clear.

DA6030 said:
D'oh, I had forgotten about /data/local. So, that means there are three locations now.
/oem/media is documented in the AT&T Nexus 6 thread, although I'm not sure anyone's checked source to see how it's implemented, nor tested to see where it falls in precedence to /data/local.
http://forum.xda-developers.com/showpost.php?p=56942290&postcount=11
And for reference, looking at the Shamu build.prop, it looks like the oem.prop items are imported explicitly into the build.prop, so the precedence there is clear.
Click to expand...
Click to collapse
you cant just add it there after manually. and theres another place to put the boot animation, but only when building a rom. i dont remember the location, but you can see it yourself, if you delete the boot animations from /system/media/ and /data/local it will appear. this one just says android

simms22 said:
you cant just add it there after manually. and theres another place to put the boot animation, but only when building a rom. i dont remember the location, but you can see it yourself, if you delete the boot animations from /system/media/ and /data/local it will appear. this one just says android
Click to expand...
Click to collapse
It used to be compiled into the frameworks I think.. Not sure if thats still the case.

Heads UP
Don't know if this is actually what caused my bootloop... but I figured I'd mention it here.
I was trying to get rid of the AT&T boot animation on my N6 and while i was renaming to .bak thought to myself, "why don't I just do my own?" Grabbed another one online, put it in /oem/media/ and bam. No boot.
The worst part is I can't fix it without full restore to stock, because I can't seem to access or even view the /oem/ folder at all through recovery. Is it only mounted after boot?
Don't kow if this means anything to y'all, but I figured someone would find this information interesting.

I have tried several times to make use of the /OEM partition with no success. Every time I reboot the contents disappear.

i tried /data/local to see if it still worked and it didnt work for me....

cmh714 said:
i tried /data/local to see if it still worked and it didnt work for me....
Click to expand...
Click to collapse
i just tried myself, you are right. not working here as well.

simms22 said:
you cant just add it there after manually. and theres another place to put the boot animation, but only when building a rom. i dont remember the location, but you can see it yourself, if you delete the boot animations from /system/media/ and /data/local it will appear. this one just says android
Click to expand...
Click to collapse
It is within framework-res.apk/assets/images/ . . there are two images.
android-logo-mask.png
android-logo-shine.PNG
The mask is a static image with partial transparency. The shine scrolls from left to right behind the mask in a loop, shinning through the mask transparency. It is actually a pretty cool way to do it and I know @rascarlo uses it in rastapop instead of the traditional bootanimation.zip

hlxanthus said:
I have tried several times to make use of the /OEM partition with no success. Every time I reboot the contents disappear.
Click to expand...
Click to collapse
I have also tried (only on stock Google builds), and had the same experience.

OEM partition unformatted on non-ATT devices
hlxanthus said:
I have tried several times to make use of the /OEM partition with no success. Every time I reboot the contents disappear.
Click to expand...
Click to collapse
I just realized that on my device (not AT&T-branded), the /oem partition has always been RAW. So, I flashed the oem.img partition from AT&T firmware (although "fastboot format ext4 oem" would probably be good enough) the partition is now formatted correctly, and now I can use it for storing personalized ringtones, bootanimations, etc. that persist through a factory reset.

DA6030 said:
I just realized that on my device (not AT&T-branded), the /oem partition has always been RAW. So, I flashed the oem.img partition from AT&T firmware (although "fastboot format ext4 oem" would probably be good enough) the partition is now formatted correctly, and now I can use it for storing personalized ringtones, bootanimations, etc. that persist through a factory reset.
Click to expand...
Click to collapse
Okay, I gotta ask. I haven't been able to find the OEM.IMG in any of my searches, just the contents found there. I wasn't aware of any att specific factory images . . got a link you can share? If you don't remember, could you upload the IMG?

hlxanthus said:
Okay, I gotta ask. I haven't been able to find the OEM.IMG in any of my searches, just the contents found there. I wasn't aware of any att specific factory images . . got a link you can share? If you don't remember, could you upload the IMG?
Click to expand...
Click to collapse
There are definitely firmware repositories other than the official Google Developers site. The one I'm thinking of hosts the full .zip file they apply using mfastboot at the factory, which includes the signed oem.img, as well as radio parameters (e.g., SIM lock/unlock for subsidized phones). I can't remember XDA's policy on linking to other sites, so I'll leave it to say that if I search for "Motorola Firmware" (incognito, to avoid personalized search results) it's the 3rd and 4th link right now. The specific file you're looking for is SHAMU_LMY47D_release-keys_subsidy-ATT_CFC.xml.zip. I want you to find it, so if that's not helpful, let me know.

DA6030 said:
There are definitely firmware repositories other than the official Google Developers site. The one I'm thinking of hosts the full .zip file they apply using mfastboot at the factory, which includes the signed oem.img, as well as radio parameters (e.g., SIM lock/unlock for subsidized phones). I can't remember XDA's policy on linking to other sites, so I'll leave it to say that if I search for "Motorola Firmware" (incognito, to avoid personalized search results) it's the 3rd and 4th link right now. The specific file you're looking for is SHAMU_LMY47D_release-keys_subsidy-ATT_CFC.xml.zip. I want you to find it, so if that's not helpful, let me know.
Click to expand...
Click to collapse
Found it, thanks!
Edit: for the record fastboot format didn't work on OEM as it won't work on raw partitions. Extracted and flashed it just as you suggested and now have the crazy att boot animation . . which I will be deleting right now. Thanks a bunch. I will likely post something soon for people who wish to do this themselves.
For those interested in this, here is the OEM.IMG. Once I play with it some more I will open a dedicated thread on how to make use of this partition.
As a little teaser, as expected you can place and set default ringtone, alarm and notification tones. Or add a bootanimation.zip. What I expected to work though did, adding user apps to it. Simply create a directory of /app within the oem partion and place your apps in there. It should be noted there is only about 50mb of space in there. I simply used a file manager to go to the /data/app and copy the desired app folder to the oem partition.(not sure you have to but I simply mirrored the file structure used there). In my case I added a copy of Root Explorer and Titanium Backup in there so they are present for all new rom installs.
Download - SHAMU_subsidy-ATT_OEM.zip

hlxanthus said:
Edit: for the record fastboot format didn't work on OEM as it won't work on raw partitions. Extracted and flashed it just as you suggested and now have the crazy att boot animation . . which I will be deleting right now. Thanks a bunch. I will likely post something soon for people who wish to do this themselves.
As a little teaser, as expected you can place and set default ringtone, alarm and notification tones. Or add a bootanimation.zip. What I expected to work though did, adding user apps to it. Simply create a directory of /app within the oem partion and place your apps in there. It should be noted there is only about 50mb of space in there. I simply used a file manager to go to the /data/app and copy the desired app folder to the oem partition.(not sure you have to but I simply mirrored the file structure used there). In my case I added a copy of Root Explorer and Titanium Backup in there so they are present for all new rom installs.
Click to expand...
Click to collapse
That's a great discovery! Would you consider submitting this as a feature request to Titanium Backup ("move app to oem partition")?
Such a pity the partition can't be formatted from fastboot. Did you try including all the option parameters (ext4 and size)? Do you think it could work from the terminal in recovery (and therefore flashable zip)?

DA6030 said:
That's a great discovery! Would you consider submitting this as a feature request to Titanium Backup ("move app to oem partition")?
Such a pity the partition can't be formatted from fastboot. Did you try including all the option parameters (ext4 and size)? Do you think it could work from the terminal in recovery (and therefore flashable zip)?
Click to expand...
Click to collapse
Alas, I tried just a few variables with fastboot format and gave up and just flashed the OEM.IMG. But fastboot did throw an error stating it could not use the format function on a RAW partition, so I don't know if there is some variable that may have worked.
Only real problem is now that I have it formated I can no longer really test what may or may not work. I can play with it some and see if OEM is accessible via recovery (it is not shown in twrp file manager, that I do know). I have a few shamu guys I can call upon to test, so if I think something might work I will give it a shot.
As for any official TiBu support I doubt it would be accepted, the partition is only 50mb so not a lot of room for stuff.

hlxanthus said:
I can play with it some and see if OEM is accessible via recovery (it is not shown in twrp file manager, that I do know). I have a few shamu guys I can call upon to test, so if I think something might work I will give it a shot.
Click to expand...
Click to collapse
Oh, really good point - TWRP support (at minimum ability to for AT&T customers to wipe the partition, but also file manager) is a way better idea. If your shamu guys are able to format /dev/block/platform/dw_mmc.0/by-name/oem from RAW to ext4 using the appropriate updater-script or recovery terminal command, that would be great to point that out to the TWRP team, to add support for format and file manager. Worst case, I would think TWRP could implement wipe (for AT&T customers) using a delete_recursive. And if format is entirely off the table, one could accomplish the same thing with a flashable zip that flashes the AT&T oem.img and then does a delete_recursive.
By the way, have you tried the format commands in any of fastboot, updater-script or recovery terminal to format your ext4 partition back to RAW?

How to fix bluetooth on cm13 (Or any other rom)/ How to fix amazon jem not recognized

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.