WARNING!!! If using the Google Wallet "Fix" Do Not Use Mobile Odin!!! - T-Mobile, Samsung Galaxy SIII

For the sake of visibility, I figured I would go ahead and post this here for everybody. Wildchld did post in The Archangels "Don't Want a Brick..." sticky, but as it seems that many people don't read or keep up with the sticky threads, I thought it would be more noticeable here.
Also it appears that a lot of people may be using the Google Wallet workarounds, and potentially may be using Mobile Odin as well. This seemed important enough to post here to warn those using both of the potential to brick their device.
If you have modified your build.prop to trick Google Wallet into thinking it is on a different device...
DO NOT FLASH ANYTHING WITH MOBILE ODIN!!!
YOU WILL BRICK YOUR PHONE!​
So basically here's the deal...modifying these lines in the build.prop essentially fools an app such as Google Wallet into thinking it is on a different, supported device.
ro.product.device=d2tmo
ro.product.name=d2tmo
ro.product.model=SGH-T999
The values shown above are the CORRECT ones for our device. If you change them, Google Wallet is not the only app that will think it is on a different phone! This probably would not be a major concern for most apps. However, by tricking Mobile Odin into believing it is on a Nexus or something else will cause it to load the incorrect partition mapping (and maybe the wrong flash kernel). Then when you try to flash something under this setup it will flash the wrong partitions with the wrong images, resulting in a brand new brick!
Thanks to Wildchld for finding this! You can find his post about it here.
From his post, a quote from Chainfire: "Quite likely, you will brick your device so hard only a JTAG unit will be able to revive it. A service center will replace the mainboard (about half the price of a new device) to fix such a brick. I would strongly advise against making a program that writes raw partitions believe it's on a different phone than it really is."
I do not think this will be a problem for the regular PC Odin, but have not confirmed this yet.
If you want to flash with Mobile Odin, please restore your backed up copy of the build.prop before flashing! Probably would be a good idea to go into app manager and clear cache and data for Mobile Odin as well.
I believe there is a Wallet workaround that uses a hacked apk and does not require the build.prop edits to remain. You can change them back to original values after initial setup.
I do not use Wallet, so I am not sure which method is which right now.
I hope this information proves useful for some of you! Dont forget to hit the Thanks button when you check out Wildchlds post or XquiziT rom threads! I would not have known about this if not for him!
Note: This also applies to any mod that edits the build.prop in this way. Such as editing it so you can download/buy unsupported apps from the Play Store, among others.
There is nothing wrong with Mobile Odin! It is a powerful tool and functions just as it is supposed to. It is up to the user to use it in a safe way for their own purposes, and to know what they are doing with it!
Also, this is not meant to be an attack on those who have released these mods, my only intent is to caution folks so they may avoid serious and sometimes expensive problems!

Good post. Surprised to see this just being called out now. Just for the record tho, pc odin is not effected by this. And although it is dangerous and stupid to try, the partitions between the us variants are the same. So you most likely wouldnt full brick unless your build.prop was edited to reflect a whole different phone like the intl' i9300 or something. I only know this because i run tmo and vzw roms on my sprint phone without fixing the build.prop and its all good wen i use mobile odin. Even tells me that i have to unlock my bootloader cuz it thinks im using a vzw variant. none the less, Good call OP

Thanks for confirming it not being an issue with PC Odin.
I thought about mentioning the other US variants build.props not being a real problem for Mobile Odin, but decided not to in order to keep confusion to a minimum, and im not sure if Wallet will work with any of the other variants since i dont use it. Good points though. Thanks
Sent from my SGH-T999 using xda app-developers app

I thought the workaround instructions tell you to revert your build prop back to the original after you modify it and gw is installed?

As mentioned, Mobile Odin is not the only apk affected by build.prop changes. Be aware that goomanager will also show incorrect rom versions if you ask for compatible roms. Rom manager may also do this, though I wouldn't know as I don't use it.
Sent from my SGH-T999 using xda premium

crazexr7 said:
I thought the workaround instructions tell you to revert your build prop back to the original after you modify it and gw is installed?
Click to expand...
Click to collapse
Thats probably the one i mention in the op that you can change back after initial setup.
There are at least a couple of different ways people are doing this and at least one of them im pretty sure if you go back to the original build.prop itll stop working after reboot and need the edits to be reapplied.
Even so its probably worth the quick mention anyway as other mods (including future ones) will use this to gain operation of an app on unsupported devices. This really isnt just a GS3 issue. It can affect any phone. Though Mobile Odin is primarily a Samsung based app.
Sent from my SGH-T999 using xda app-developers app

P06o said:
As mentioned, Mobile Odin is not the only apk affected by build.prop changes. Be aware that goomanager will also show incorrect rom versions if you ask for compatible roms. Rom manager may also do this, though I wouldn't know as I don't use it.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Good point. Though i hope most people would abort the install when they go to install recovery or roms and it only offers choices for a different device. Im not sure what, if any, safety catch is incorporated into those so they are also worth the mention. Thanks!
Sent from my SGH-T999 using xda app-developers app

I would hope so too, but there will always be that one time someone doesn't pay attention - no matter how vigilant they are otherwise. I know I've done it before, but was lucky enough to abort the whole thing before I did any damage. It's easy to do when you have multiple devices in the household.
Sent from my SGH-T999 using xda premium

Sounds like its only with Mobile Odin then...bcos i flash stuff all the time with CWM and nothing happens.

{
"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"
}

babymatteo said:
Sounds like its only with Mobile Odin then...bcos i flash stuff all the time with CWM and nothing happens.
Click to expand...
Click to collapse
As long as you have the correct recovery installed CWM or TWRP are fine. Im pretty sure they have the correct partition mapping built in. If you were to somehow install a different devices recovery you would likely have the same issues. (You would get an immediate brick most likely since it would try to flash the wrong partition.)
The reason Mobile Odin is different here is because it uses those build.prop values to determine what device you have and automatically installs the appropriate flash kernel (temp recovery) for what it thinks is the device its on. It does this as soon as you run the app. As mentioned above, Goo Manager and Rom Manager do pretty much the same thing, except it will let you choose from different recoveries/roms and most people will notice that it says something other than Tmobile GS3 before going through with it. Plus usually folks install recovery right after rooting, before any mods to build.prop. so the recovery would be correct. Mobile Odin does this when you actually use it.
Hope that makes sense!
Sent from my SGH-T999 using xda app-developers app

Doc just a stupid question; I did edit build.prop and install wallet and now back into same build.prop . So should i be carefull using mobile odin ?
And other like rom manager and goo.im?
I am already in stock build. Prop so now what matters?
Sent from my SGH-T999 using xda premium

bikrame said:
Doc just a stupid question; I did edit build.prop and install wallet and now back into same build.prop . So should i be carefull using mobile odin ?
And other like rom manager and goo.im?
I am already in stock build. Prop so now what matters?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Once youve restored the original file you should be good to go. Just to be sure though check in your build.prop and if the lines i mentioned in the op match yours it ought to be fine.
Sent from my SGH-T999 using xda app-developers app

bfranklin1986 said:
Click to expand...
Click to collapse
Oh man that made me laugh.
Sent from my SGH-T999 using xda premium

Thank you for the warning!
Thank you for the heads up. I am a noob and rooted for the first time in a long time, so this has saved me for the future!

Related

[ROM] Vanilla AOSP 4.0.4 IMM76L with root and busybox (Updated with MODS) 6/12/12

Hey everyone.
I just wanted to share an ultra prestine build of the latest AOSP source, sync'ed tonight and compiled clean. I know there are ROMs with all sorts of great mods, pieces taken from CM9 and AOKP, linaro optimization, etc.... that isn't this ROM. This is simply the latest Google source of 4.0.4 IMM76L with root and busybox.
I built it for me and thought I'd share. Feel free to use it... or not.
As always, don't forget to Nandroid.
ROM:
http://www.mediafire.com/?o9xkbxocy3yqhf5
3/12/12 11:30pm - Updated so reported model is "Galaxy Nexus". Thanks al2x for pointing it out.
The latest ICS GAPPS work for this one too:
http://goo.im/gapps/gapps-ics-20120429-signed.zip
MODS:
The following mods I've tested and work with this ROM:
Mods found in mwalts AOSP ROM also work for mine.
http://forum.xda-developers.com/showthread.php?t=1631796
Native Tethering Patch (mwalt2)
http://d-h.st/6se
Enhanced Power Menu with Native Tether (mwalt2)
http://d-h.st/RdT
Battery with Percentage Mod (CMO220)
http://dl.dropbox.com/u/31971676/BatMod.zip
Stock Boot Animation - hi-res (Thanks NHLWil)
http://forum.xda-developers.com/showpost.php?p=27332536&postcount=13
Keyboard APK with dictionary (for now)
http://www.mediafire.com/?qdavsrl5c64rxbf
I've been struggling to get all my binaries together to build from source and what
I have to know are tethering provisions removed in a build like this?
****Tether Subscription Check is not removed in build 061112_211425****
doobie711 said:
I've been struggling to get all my binaries together to build from source and what
I have to know is are tethering provisions removed in a build like this?
Click to expand...
Click to collapse
I don't think anything is taken out from vanilla to prevent you from using a tethering app for rooted phones in the market. I don't tether so I don't know for sure though.
I was referring to the native ICS tethering option under "More..." in "Settings". I'll try it out and update my own post with an answer.
This is great, I hope you can continue this style of being 100% stock with root/bb as the updates continue to flow for the GN...
I'm going to be flashing soon but I do tether so I hope it bypasses the subscription check...
It does not bypass the subscription check. but I'm pretty sure an edit of the framework.apk can fix that.
I'll try to update op with some mods tomorrow.
Sent from my Full AOSP on Toro-VZW using Tapatalk 2
doobie711 said:
I was referring to the native ICS tethering option under "More..." in "Settings". I'll try it out and update my own post with an answer.
Click to expand...
Click to collapse
You have to make a couple changes to the device repo to get the stock ICS tethering options included.
imnuts said:
You have to make a couple changes to the device repo to get the stock ICS tethering options included.
Click to expand...
Click to collapse
Thanks. I think I found the changes. I'll give it a shot when I get home from work.
Updated OP with Tethering, Menu, and Battery mod links.
mmuzzy, I've been using the ROM and it's been pretty snappy. The first flash didn't go so well, there were a few force close/force waits but i reflashed it now with a new download and I think it's been good.
One request is if you could possibly edit the name computers pickup as the MTP device... it recognizes it as "Full AOSP on Toro-VZW" rather than simply "Galaxy Nexus" lol
If there is any way you could include the stock Galaxy Nexus boot animation, that would be great, otherwise this rom is great!
thanks
Snakehn said:
If there is any way you could include the stock Galaxy Nexus boot animation
Click to expand...
Click to collapse
Attached.
Higher definition versions here:
http://forum.xda-developers.com/showthread.php?t=1380655
This intrigues me. Might try it soon. I've wanted a 100% stock build and nobody had really made one. They all usually come with "tweaks and enhancements" pre installed.
Sent from my Galaxy Nexus using xda premium
Edit: flashed it so far so good but it thinks every word I type is wrong. As well as the IME switcher always being shown when typing and no other keyboards installed
{
"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"
}
Edit #2: saw a thread about a differnt rom needing specific gapps and without them it would do that gonna flash the ones from OP even though I have the 429 gapps already
Edit #3: thought that fixed it but it didn't. Maybe with a clean install with the gapps. I'll have to try in the morning.
Edit...again: more searching is bringing up that the ICS dictionary is missing or that there is a problem with the keyboard apk.
al2x said:
mmuzzy, I've been using the ROM and it's been pretty snappy. The first flash didn't go so well, there were a few force close/force waits but i reflashed it now with a new download and I think it's been good.
One request is if you could possibly edit the name computers pickup as the MTP device... it recognizes it as "Full AOSP on Toro-VZW" rather than simply "Galaxy Nexus" lol
Click to expand...
Click to collapse
Snakehn said:
If there is any way you could include the stock Galaxy Nexus boot animation, that would be great, otherwise this rom is great!
thanks
Click to expand...
Click to collapse
NHLWil said:
Attached.
Higher definition versions here:
http://forum.xda-developers.com/showthread.php?t=1380655
Click to expand...
Click to collapse
Op updated with changes. Thanks.
Anthonok said:
This intrigues me. Might try it soon. I've wanted a 100% stock build and nobody had really made one. They all usually come with "tweaks and enhancements" pre installed.
Sent from my Galaxy Nexus using xda premium
Edit: flashed it so far so good but it thinks every word I type is wrong. As well as the IME switcher always being shown when typing and no other keyboards installed
Edit #2: saw a thread about a differnt rom needing specific gapps and without them it would do that gonna flash the ones from OP even though I have the 429 gapps already
Edit #3: thought that fixed it but it didn't. Maybe with a clean install with the gapps. I'll have to try in the morning.
Edit...again: more searching is bringing up that the ICS dictionary is missing or that there is a problem with the keyboard apk.
Click to expand...
Click to collapse
Weird. I didn't notice that because I use SwiftX. Thanks for pointing it out. I don't know that is yet.
Anthonok said:
This intrigues me. Might try it soon. I've wanted a 100% stock build and nobody had really made one. They all usually come with "tweaks and enhancements" pre installed.
Sent from my Galaxy Nexus using xda premium
Edit: flashed it so far so good but it thinks every word I type is wrong. As well as the IME switcher always being shown when typing and no other keyboards installed
Edit #2: saw a thread about a differnt rom needing specific gapps and without them it would do that gonna flash the ones from OP even though I have the 429 gapps already
Edit #3: thought that fixed it but it didn't. Maybe with a clean install with the gapps. I'll have to try in the morning.
Edit...again: more searching is bringing up that the ICS dictionary is missing or that there is a problem with the keyboard apk.
Click to expand...
Click to collapse
I'm not sure why the keyboard as compiled from source doesn't have the dictionary but I installed a different keyboard apk and the dictionary works. Weird.
Edit: I put the APK in OP
mmuzzy said:
I'm not sure why the keyboard as compiled from source doesn't have the dictionary but I installed a different keyboard apk and the dictionary works. Weird.
Edit: I put the APK in OP
Click to expand...
Click to collapse
Didn't work for me still showing everything as wrong. If I turn off auto correction in the keyboard settings and use SwiftKey it works fine. It'll have to do for now
Sent from my Full AOSP on Toro-VZW using xda premium
Anthonok said:
Didn't work for me still showing everything as wrong. If I turn off auto correction in the keyboard settings and use SwiftKey it works fine. It'll have to do for now
Sent from my Full AOSP on Toro-VZW using xda premium
Click to expand...
Click to collapse
That's strange. I had the Dictionary issue until I used this APK.
I navigated to where the APK was in ES Explorer, clicked it, it asked if I wanted to replace the system file and after that I had word suggestions as I type.
mmuzzy said:
That's strange. I had the Dictionary issue until I used this APK.
I navigated to where the APK was in ES Explorer, clicked it, it asked if I wanted to replace the system file and after that I had word suggestions as I type.
Click to expand...
Click to collapse
Exactly what i did. But still doesn't work with stock keyboard.
Sent from my Full AOSP on Toro-VZW using xda premium
Anthonok said:
Exactly what i did. But still doesn't work with stock keyboard.
Sent from my Full AOSP on Toro-VZW using xda premium
Click to expand...
Click to collapse
That is strange. I also notice that unlike what I had happening you actually have some words that aren't highlighted. So either you added them or maybe the language isn't set? In the Notification area does yours say "English (US)" in input method when the keyboard is up?

[APP]|Glazed Mods|A New Way To Mod|Beta|6-22-12|

Hey forum i back yet again, this time i present to you a new kind of app its called glazed mods. This app is so uniques to all the others, well maybe it may only be one of a kind. So what does this app do, easy it allows you to download the mods that are posted on it. I thought to myself, hmm why not make anyone on any rom enjoy this app, so i am, currently all of the apps are working on glazed ICS, any other rom such as gederom can only download the ones with a little orange plus on them.
By what i mean this app is one of a kind i mean that it uses a new way of presenting apps to you. So what makes it unique is that it is a WebView loading a 600*1024 flash website. It fits perfectly to your screen and the abbilities of flash is customization, and many other little tweaks that this app can support.
Things you need to know
Do not click an item multiple times it might cause the app to crash
There is an update feature that downloads the latest update of the roms listed, if you want to see more roms. Contact me or comment below, need devs permission.
You will recieve automatic updates but not by updating the app.
Please report any bugs in the request section
YOU NEED FLASH INSTALLED
Screenshots
{
"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"
}
Version 1.2 - Download
Version 1.1 - Download
Version 1.2 - Fixed the weird freeze after download
Version 1.1 - Initial release
If you want to see a mod or something you find, just post it in the request section and as always guys ENJOY.
BIG THANKS TO POWERPOINT45​
thank you for this it works very well. I also wanted to know of the reboot into recovery worked.
Sent from my Galaxy Nexus using xda premium
Hi Hyperrunner, excited to try this, if I already have Mods installed on glazed will this detect them and let me disable them if I want to, or do I have to install them through the app itself? Thanks
I made this app and he made the website. just saying. We work as a great team. XD. I like XDA cause u can take out the A and it makes a cool face. XD
Just tell me if u want the source code. A thanks would be appreciated. Hope we never depreciate that meathod.
Sent from my Glazed ICS using XDA
TahrirSquare said:
Hi Hyperrunner, excited to try this, if I already have Mods installed on glazed will this detect them and let me disable them if I want to, or do I have to install them through the app itself? Thanks
Click to expand...
Click to collapse
You have to install through the app in order to detect that it is downloaded. But you can reflash glazed ics or any other rom and it will delete all the mods.
Yes reboot into recovery works, but if you are using FFF 1.4a it doesnt (The one that can have 2 roms at a time)
alright thanks for the info
Thanks!
Well, there goes any chance of my getting anything productive done today. I am just going to have to play with this.
Thanks, guys, I appreciate all your work.
Very cool app! Used it to get the inverted market on AOKP and everything worked perfectly. Can't wait to see even more mods!
Hyperrunner said:
Yes reboot into recovery works, but if you are using FFF 1.4a it doesnt (The one that can have 2 roms at a time)
Click to expand...
Click to collapse
just wanted to comment on this. fff1.4a is the latest available bootloader, and works with reboot recovery option.
dual-boot fff extended does not.
one question about the app, why does it need su?
Sent from my HTC Glacier using xda premium
Sorry, yeah thats what i meant, im not sure your going to have to talk to powerpoint since he made the app.
smirkis said:
just wanted to comment on this. fff1.4a is the latest available bootloader, and works with reboot recovery option.
dual-boot fff extended does not.
one question about the app, why does it need su?
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
It needs su because It installs a custom virus. JK.I am using a lot of native code such as wget and that's why I need switch user permissions. It was not working until I added su -c.If you look in the super user logs you can see all commands it uses.
Sent from my Galaxy Nexus using XDA
powerpoint45 said:
It needs su because It installs a custom virus. JK.I am using a lot of native code such as wget and that's why I need switch user permissions. It was not working until I added su -c.If you look in the super user logs you can see all commands it uses.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
The download link just takes me to minus.com. I do I need to set up an account to download? Haven't tried from a pc browser yet.
Sent from my Galaxy Nexus using Tapatalk 2
We are having many problems with minus. It either works or it doesnt. We are thinking of reuploading but we have no money for a direct link service were only using minus because its free. Do you have any other direct link service other than dropbox?
Oh a fix for your problem maybe would be to clear cache and data then reboot and it should work.
If that doesnt work you can use the pc version. Its not the best size in the world but it works.
http://hyperrunner.wix.com/glazeydone
Dont ask about the weird name.
powerpoint45 said:
I made this app and he made the website. just saying. We work as a great team. XD. I like XDA cause u can take out the A and it makes a cool face. XD
Just tell me if u want the source code. A thanks would be appreciated. Hope we never depreciate that meathod.
Sent from my Glazed ICS using XDA
Click to expand...
Click to collapse
I for one would like to see a source code if you don't mind
Hyperrunner said:
We are having many problems with minus. It either works or it doesnt. We are thinking of reuploading but we have no money for a direct link service were only using minus because its free. Do you have any other direct link service other than dropbox?
Oh a fix for your problem maybe would be to clear cache and data then reboot and it should work.
If that doesnt work you can use the pc version. Its not the best size in the world but it works.
http://hyperrunner.wix.com/glazeydone
Dont ask about the weird name.
Click to expand...
Click to collapse
I tried it a couple times and now all is well. Everything works fantastically. Really like the selection of inverted mods.
Sent from my Galaxy Nexus using Tapatalk 2
Has anyone tried the Eyecandy theme with gederom?
I know it's listed as not compatible with all ROMs but I swear I thought I had read in a thread somewhere that someone had used it w/ gederom successfully.
Is it possible for you to add some features from the SGT7 rom as a flashable mod?
---------- Post added at 12:09 PM ---------- Previous post was at 11:48 AM ----------
Hyperrunner said:
We are having many problems with minus. It either works or it doesnt. We are thinking of reuploading but we have no money for a direct link service were only using minus because its free. Do you have any other direct link service other than dropbox?
Oh a fix for your problem maybe would be to clear cache and data then reboot and it should work.
If that doesnt work you can use the pc version. Its not the best size in the world but it works.
http://hyperrunner.wix.com/glazeydone
Dont ask about the weird name.
Click to expand...
Click to collapse
You could try this site. I just tried it and it seems to work fine and has direct linking.
http://www.peejeshare.com/upload
Source code
rukin5197 said:
I for one would like to see a source code if you don't mind
Click to expand...
Click to collapse
For anyone who wants the source code, here it is:
https://dl.dropbox.com/u/86322124/Glazed Mods 1.1.zip
It is set up to compile for android 4.0
Anyone else experience this?
After using the app and installing the inverted play store i was stuck at the boot animation, let it sit for 30 min with no luck so i had to restore a backup.
Knowing how stupid i am i went to restore a backup and i forgot that i had deleted both the rom zip and my backups from my sd card so i had to get out the ol' laptop, download the rom again and mount through twrp to install. Last part was totally my fault
But anyways im going to try to induce the same problem and see if i can pull the log to see what was going on. Shouldve done that in the first place but again Beer does impair my thinking haha!
apply at goo.im for a dev account. u get hosting, and goo manager access which kind of does what your trying to do with this. or just use it for hosting.

New camera from UVALH2

So I liked the ability to do the color differentiate thing and other little mods I noticed with the new camera... but I don't like the builds we have right now as I'm seeing to much TouchWiz lag in them... (came JB lol) so I just pulled it from WildChild's rom.
You need to install it by renaming the old camera file (located in /system/app) SamsungCamera.apk.bak this is as a backup just in case you dont like the new app for whatever reason.
copy and paste the file to /system/app/
reboot
Then it should work. Check permissions as I did and it wasn't set properly even though the camera functioned properly...
Easier then I thought and wrote up.
Be sure to wipe cache after all is done just in case as @DocHoliday77 suggested.
Yes I just did this process all over again.
http://dl.dropbox.com/u/92214305/SamsungCamera.apk
http://i45.tinypic.com/1zxxrux.png
http://i49.tinypic.com/jkaz9i.png
Confirmed on: Wicked [v2]
I'm sure this will work on any TouchWiz rom, waiting on confirmations.
any questions ask away I'll check frequently and update post if need be...
I tried this and wasn't able to get the camera to work. I'm running stock rom on tmobile but have upgraded to the UVLH2 radio.
I renamed the SamsungCamera.apk to SamsungCamera.apk.bak
I copied the file you posted to the /system/app folder
I set the permissions to what you posted in your pic
I rebooted and when I tried to use the camera I got a force close.
I rebooted again and still got a force close error.
I then tried installing the camera by clicking on the apk in root explorer. It told me the camera failed to install.
At that point I just reverted back to my old camera app. Is there something different I should be doing?
Looks like i should right the instructions a little better... I'll do a better right up in a little bit when i can get to my computer.
Sent from my SGH-T999 using xda premium
Try unchecking Execute.
updated, it's actually stupid simple copy and paste, and reboot that's all I did and then took a picture.
@mt3g
What rom base are you currently on?
Reason I ask is cause there is quite a change between the first two and the latest update.
If you're on an older base some things from the latest may not work correctly.
If you are running one of the first two, and it works fine then at least we know that's not the case here.
Sent from my SGH-T999 using xda app-developers app
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
infinitron said:
I tried this and wasn't able to get the camera to work. I'm running stock rom on tmobile but have upgraded to the UVLH2 radio.
I renamed the SamsungCamera.apk to SamsungCamera.apk.bak
I copied the file you posted to the /system/app folder
I set the permissions to what you posted in your pic
I rebooted and when I tried to use the camera I got a force close.
I rebooted again and still got a force close error.
I then tried installing the camera by clicking on the apk in root explorer. It told me the camera failed to install.
At that point I just reverted back to my old camera app. Is there something different I should be doing?
Click to expand...
Click to collapse
Whenever you replace an app in /system/app, its a good idea to boot recovery and wipe cache and dalvik. Try doing that and let us know!
Sent from my SGH-T999 using xda app-developers app
Wicked [v2]
tested out all the features color chooser, cartoon, panorama, FFC & back camera recording, all work 100%
{
"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 followed the instructions in the OP and it's working perfectly.
Thanks!
Sent from my SGH-T999 using xda premium
@Ozzywhat rom are you on, glad it worked.
@Doc I'll add that it's best to wipe cache after wards, thanks.
mt3g said:
@Ozzywhat rom are you on, glad it worked.
Click to expand...
Click to collapse
I'm on Wicked V2.
Alright that's good, need other's to try it out and see if we got lucky, I don't see how it'd be too different from other TW based roms though.
Just tried this myself and it worked great. I am running the new update (deodexed stock) and I didn't have the new camera. Just wanted to let everyone know that it was working on deodexed stock as well
Sent from my SGH-T999 using xda app-developers app
trimble83 said:
Just tried this myself and it worked great. I am running the new update (deodexed stock) and I didn't have the new camera. Just wanted to let everyone know that it was working on deodexed stock as well
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I'm just on rooted stock UVALH2 and followed OP instructions, wipe, wipe dalvik cache and nothing happened. Still stock without added options.
Do I have to be on a custom rom?
Thanks
It is the same as the CM10 camera. What other features did you add? It works well but it is missing the burst mode and storage location to save the photos.
Oh, and I didn't have to wipe data or non of that! but just copied/pasted and reboot.
eggnoodle said:
I'm just on rooted stock UVALH2 and followed OP instructions, wipe, wipe dalvik cache and nothing happened. Still stock without added options.
Do I have to be on a custom rom?
Thanks
Click to expand...
Click to collapse
I'm curious, how did you update? Did yoh flash the rooted rom? Or did you install the full update via kies or odin. Or did you install the ota update?
I've been suspecting the following for a while now but could never get an answer to confirm.
Basically if you just flash the rooted update, you are going to miss out on a number of other firmware updates to other parts of your phone. Flashing the rom does not update the other partitions like installing via kies or odin will.
I could be wrong here or at least in your case, but not having the FULL update installed could cause exactly what you are seeing.
Just food for thought but would love to hear others input on this theory.
Note: you could try the dialer code mentioned in another thread to try updating JUST the camera firmware. I think its in general.
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
I'm curious, how did you update? Did yoh flash the rooted rom? Or did you install the full update via kies or odin. Or did you install the ota update?
I've been suspecting the following for a while now but could never get an answer to confirm.
Basically if you just flash the rooted update, you are going to miss out on a number of other firmware updates to other parts of your phone. Flashing the rom does not update the other partitions like installing via kies or odin will.
I could be wrong here or at least in your case, but not having the FULL update installed could cause exactly what you are seeing.
Just food for thought but would love to hear others input on this theory.
Note: you could try the dialer code mentioned in another thread to try updating JUST the camera firmware. I think its in general.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
i flashed wildchld rooted rom.
Sent from my SGH-T999 using Tapatalk 2
mt3g said:
@Ozzywhat rom are you on, glad it worked.
@Doc I'll add that it's best to wipe cache after wards, thanks.
Click to expand...
Click to collapse
Thanks for the share by the way!
I've not updated yet and have a number of 'tests' I want to play with. Just added this to the list!
Sent from my SGH-T999 using xda app-developers app
This may help for those who haven't seen it.
This is quoted from another thread.
Post by nyyankees3511
"Theres also a new camera firmware that you need to update manually, previously mine showed zdfe02 and now its updated to zdff03. To do so go to the dialer and type *#34971539# then hit “Phone / CAM FW Ver check” and if the phone FW is different than the cam FW you then hit "phone to cam FW write (rear)" and reboot."
Ok, I am currently running UVALG1 via wildchlds flashable rom. I installed the camera as per op and worked great! So my theory was at least part if not fully wrong.
However I have a question/request of anyone willing. Enter the dialer code from above and choose the first option Check Camera fw Ver. A toast will popup telling what your cameras and phones versions are. Mine said zdfe02 for both, but as stated above, his said one was zdff03.
Would you guys be willing to do that and let me know what it says? I figure zdff03 will show up if you have updated to UVALH2.
Thanks in advance! Hope I'm not annoying you with this stuff, I just want to know more!!!
Sent from my SGH-T999 using xda app-developers app
Fine by me I did and was on 2 plus all the numbers. I updated through windchilds Rom not Odin nor Kies...
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
This may help for those who haven't seen it.
This is quoted from another thread.
Post by nyyankees3511
"Theres also a new camera firmware that you need to update manually, previously mine showed zdfe02 and now its updated to zdff03. To do so go to the dialer and type *#34971539# then hit “Phone / CAM FW Ver check” and if the phone FW is different than the cam FW you then hit "phone to cam FW write (rear)" and reboot."
Ok, I am currently running UVALG1 via wildchlds flashable rom. I installed the camera as per op and worked great! So my theory was at least part if not fully wrong.
However I have a question/request of anyone willing. Enter the dialer code from above and choose the first option Check Camera fw Ver. A toast will popup telling what your cameras and phones versions are. Mine said zdfe02 for both, but as stated above, his said one was zdff03.
Would you guys be willing to do that and let me know what it says? I figure zdff03 will show up if you have updated to UVALH2.
Thanks in advance! Hope I'm not annoying you with this stuff, I just want to know more!!!
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
i have both zdfe02 for cam FW. I'm on UVALH2 but still on old baseband UVLEM. I'm wondering if this is causing me not to be able to get the updated cam??

[ROM][CM10.1] UNOFFICIAL CM10.1 for LS970

BACKUP YOUR EFS THROUGH FREEGEE AND/OR TWRP
{
"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"
}
CM10.1 is here for the LS970, aka the Sprint LG Optimus G.
This is a source build rom, which includes all the latest changes from cm and codefirex with respect to kernel.
While the efs issues have not been solved, our custom ril class seems to have helped. The rom by default backups up on first flash to /sdcard/EFS_BACKUPS/ because I know some of you won't make efs backups before flashing.
Instructions
You must use lgnpst to flash the jb bin. You need the jb tot to get new rpm/tz
If the rom doesn't boot, it's cause you didn't lgnpst the jb bin!
Lgnpst is currently the safest way to update your tz and rpm partitions, we are looking into other methods, but in the process to get things to you the fastest that is what must be done for now. Flashable zip might come once we can make it so partitions can be verified after flashing. A bad rpm/tz flash is a hard brick like a bad sbl flash, so lgnpst is the way to go for now.
Download cm-10.1, and gapps. Put them on your sdcard, reboot to recovery. Flash, and enjoy!
The current version is:
20130523
The latest will be avaliable at:
http://downloads.codefi.re/shelnutt2/optimusg/sprint/cm10_1/
Gapps:
Currently BaNkS Seems to work best:
http://forum.xda-developers.com/showthread.php?t=2012857
Click to expand...
Click to collapse
Known Issue
Most issues can be fixed by flashing the jb modem.
Calls hang up but then procced.
Call timer is bugged
If nfc doesn't work flash this: http://downloads.codefi.re/shelnutt2/optimusg/fix_nfc.zip
Click to expand...
Click to collapse
Change Log
Current Version: 20130523
Changelog:
20130411:
New kernel, new blobs, unified sources with all optimus g's. Everything works.
20130330:
Easter edition! No easter eggs though just a resync and start of nightlies.
20130326
Latest cm changes including Pie.
Camera hals removed again, so people don't see kernel panics. Previously was left in by accident due to testing
20130314:
EFS partitions are now backups by default on your first flash if they do not exist.
Click to expand...
Click to collapse
Special Thanks To!
None of this would be possible without the following people:
rlasalle15
chadouming
dvhexer
synergy
thecubed
autoprime
sextape
Click to expand...
Click to collapse
Source
Device repo, Vendor Blobs and kernel
http://github.com/TeamLGOG
Click to expand...
Click to collapse
Need to update your RPM/TZ?
Instead of flashing a 1GB+ .bin file for lgnpst... try a TeenyBin
TeenyBin is currently the safest, fastest and easiest way to flash RPM/TZ... it also safely flashes the SBL stack.
GPS Not Working?
Always check recent posts at the end of this thread to see if a current build has any current issues. If GPS is working for most people but not you... try flashing back to an LG-based rom... something stock is perfect(stock zvb deodex for example). Boot into LG-based rom and disable wifi/mobile networks in GPS settings.. only have GPS Sat checked. Go outside and try to get a lock. You could also try ##GPSCLRX# (phone dialer code) or something like GPS Status to reset your GPS data. After getting a successful GPS lock on the LG-based rom.. power off... reboot into recovery and reflash the rom and gapps zip... wipe data. Reboot when finished.. cross fingers and hope for the best.
MMS Not Working?
MMS confirmed working for a few in IRC.. send receive should work now if you're lucky and can follow directions.
1. Delete telephony.db located at /data/data/com.android.providers.telephony/databases/telephony.db ...Open ES File Explorer > Press the menu button > Settings > Scroll to the bottom > Make sure "Root Explorer" is checked > Click "OK" > navigate to the directory starting from "/" (you could prob do this with the CM file explorer too)
2. Delete messaging Data...From home screen > Press menu button > Manage Apps > "All" tab > Find Messaging > Press "Clear data" button
3. Reboot. Clear cache if you want.
Not sure if NFC is working?
You don't need NFC tags or Google Wallet to check. Just go to the NFC settings... are you able to check/uncheck the NFC option? If no, NFC is "broken"
Awesome finally some cm to try.
This is so awesome/frustrating having so many great ROMs! I can't decide!
Sent from my LG-LS970 using xda app-developers app
What is ehrpd, I'm guessing that is 4g...
**** just got real...
Sent from my LG-LS970 using xda premium
saramon said:
What is ehrpd, I'm guessing that is 4g...
Click to expand...
Click to collapse
no, 4G LTE works if you're in an LTE coverage area.
more info on eHRPD here - http://s4gru.com/index.php?/topic/1819-what-is-ehrpd/ (post 12)
HOLY $HIT!!! SHELNUTT I LOVE YOU!!!
Sent from my LG-LS970 using xda premium
autoprime said:
no, 4G LTE works if you're in an LTE coverage area.
more info on eHRPD here - http://s4gru.com/index.php?/topic/1819-what-is-ehrpd/
Click to expand...
Click to collapse
That first thread is the most hilarious conversation ever.
Edit: so, if I get it correctly, eherpderp is the software that makes for a smooth 3g to lte transition, which our phones suck at doing anyway.
Sent from my LG-LS970 using xda app-developers app
outerpip said:
That first thread is the most hilarious conversation ever.
Edit: so, if I get it correctly, eherpderp is the software that makes for a smooth 3g to lte transition, which our phones suck at doing anyway.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
correct.. it lets u keep same IP if I'm not mistaken... and takes care of the 3g/lte handoff stuffs.
not having proper working eHRPD on this rom currently isnt end of world.. can still use normal EVDO Rev A 3G... and can still use 4G... :good:
There are some cases where the phone stick to eHRPD only and at that point data seems to not work at all. To fix that.. you can toggle "CDMA" rather than CDMA/LTE in the network settings. Once eHRPD is fixed.. no one will have to worry about any of that.
autoprime said:
no, 4G LTE works if you're in an LTE coverage area.
more info on eHRPD here - http://s4gru.com/index.php?/topic/1819-what-is-ehrpd/ (post 12)
Click to expand...
Click to collapse
Thank you kindly
So I guess now that we have an AOSP base, I can try my hand at porting some roms over, if I remember correctly this is a nexus 4 base, is that right?
Ugh... This is one reason I disliked wimax on my evo3d. I never used it because I'd be on wimax trying to log into something, and it bump me to 3g and change my ip. But yeah, not the end of the world. At work, I'm in and out of a cave several times a shift, so having to toggle data every time I leave is normal everyday life to me.
Sent from my LG-LS970 using xda app-developers app
I have a few other bugs I have noticed just to point out so we don't have 100 threads reporting it.
1. LED lights flash wrong color when charging
2. USB tethering doesn't work (might be only for MacBooks, can someone else test.
3. auto brightness doesn't adjust at all.
4. I need some other people to test this one, when making a call it says call ended but it still dials, but the timer for the call does not start.
Again, these are not complaints, but I think it would be useful to gather all bug reports in one place.
So downloading the gapps... there are like 5 things to download... which one do we download and flash?
Sent from my LG-LS970 using xda premium
alsaces daddy said:
So downloading the gapps... there are like 5 things to download... which one do we download and flash?
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
1. One with the Stock Keyboard with Gestures and the Stock Photosphere Camera
2. One without the Stock Keyboard with Gestures and without the Stock Photosphere Camera so you can use the AOSP ones that come in some ROMS
3. One without the Stock Calendar and the Stock Keyboard with Gestures and Stock Photosphere Camera so you can use the AOSP ones that come in some ROMS
4. A minimal gapps package only containing Gtalk,Playstore with syncing stuff
Click to expand...
Click to collapse
From the thread
quickshade said:
From the thread
Click to expand...
Click to collapse
Sorry i didnt clarify... which one do we download.(recommended)
Sent from my LG-LS970 using xda premium
Woo! Thanks.
Sent from my LG-LS970 using xda premium
alsaces daddy said:
Sorry i didnt clarify... which one do we download.(recommended)
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
Just the basic google syncing stuff and the play store then number 4.
everything number 1.
I did number one.
quickshade said:
Just the basic google syncing stuff and the play store then number 4.
everything number 1.
I did number one.
Click to expand...
Click to collapse
Thank you quickshade.
Sent from my LG-LS970 using xda premium
TY shell, I love you full homo! Dlin this now.
backed up my EFS already and never use camera so WOOOOOO

[Q] could someone help me in Bluetooth.apk?

I did some modifications to Bluetooth share in /system/app/Bluetooth.
But after that I pushed the app via adb...then a lot of error messages that said (Bluetooth Share Stopped).
Then I removed the modified Bluetooth app and pushed the stock one via adb and rebooted the device but the error message still appears although I make
1) wipe cache+dalvik
2) reflash the kernel
Why the error message still appears although I used the stock unmodified app.
Where is the problem?
Could someone help me with this problem?
Here are some logs
{
"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"
}
Check your ROM zip for symlink. Different Bluetooth Sharing apk may require different different libbluetooth_jbi.so if linked to /system/app/Bluetooth/lib/arm folder from /system/lib/libbluetooth_jni.so For that reason, you have to watch for 0 bit lib files when pulling application from another ROM flashed on phone. (It may been a symlink if true).
Did you try verifying permissions and ownership and clearing data for Bluetooth Sharing and reboot?
Got a backup? If not, try dirty flashing ROM. You may just have to start over. Consider making a backup before making changes.
Sent from my SM-N930P using Tapatalk
samep said:
Check your ROM zip for symlink. Different Bluetooth Sharing apk may require different different libbluetooth_jbi.so if linked to /system/app/Bluetooth/lib/arm folder from /system/lib/libbluetooth_jni.so For that reason, you have to watch for 0 bit lib files when pulling application from another ROM flashed on phone. (It may been a symlink if true).
Did you try verifying permissions and ownership and clearing data for Bluetooth Sharing and reboot?
Got a backup? If not, try dirty flashing ROM. You may just have to start over. Consider making a backup before making changes.
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
How to verify permission and ownership from terminal?
Yes I have a backup but I want to know more about the problem.
I have some logcat about the problem.
It may help to figure out what happened
And
Could be mismatch of apk and lib. Did you replace both and set a new link?
It's easy to set with a root browser.
Sent from my SM-N930P using Tapatalk
samep said:
Could be mismatch of apk and lib. Did you replace both and set a new link?
It's easy to set with a root browser.
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
Thank you very much @samep
Yes that works like a charm.
Recreate the symlink solve my problem.
samep said:
Could be mismatch of apk and lib. Did you replace both and set a new link?
It's easy to set with a root browser.
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
can u give me a easy throughput as a newbie ?
hessamx said:
can u give me a easy throughput as a newbie ?
Click to expand...
Click to collapse
I think the members moved on to oyher endeavors. Not much activity on the Sprint Note 4. However, I used this method posted by Lawyer-06 to port some system apps and CSC files from my stock rooted rom to a customer rom I was having issues with.
https://forum.xda-developers.com/showpost.php?p=60831252&postcount=3443
hessamx said:
can u give me a easy throughput as a newbie ?
Click to expand...
Click to collapse
Mr. JAVI said:
I think the members moved on to oyher endeavors. Not much activity on the Sprint Note 4. However, I used this method posted by Lawyer-06 to port some system apps and CSC files from my stock rooted rom to a customer rom I was having issues with.
https://forum.xda-developers.com/showpost.php?p=60831252&postcount=3443
Click to expand...
Click to collapse
Nice tutorial share. Thanks for helping.
What may be missing is linking the lib so the application works. It's a matter of checking original file as installed on phone before replacing and duplicating with a root browser. Long press the lib file, scroll through options, select link to this folder (maybe last option) and then browsing and selecting same folder location as seen from original link. Hint: the lib linking and appearance in its location will look the same when linked properly.
In the case of this thread, unzipping the ROM and reading the install scripts for proper linking may have been done to link the files after installing. The Bluetooth application simply needed to know where to get it's vital resources to work with. There are exceptions where replacing apk and lib, setting permissions, clearing data and rebooting aren't enough. Developers may write install scripts into patch zip accordingly as needed to get this done without a ROM update. Or even alternately in an aroma installer. Or those that test ROMs to support a developer may need to do this manually in that support capacity. Then again, it could be user in another country or region needing to make changes for themselves in order to use a developed ROM.
Sent from my PH-1 using Tapatalk
samep said:
Nice tutorial share. Thanks for helping.
What may be missing is linking the lib so the application works. It's a matter of checking original file as installed on phone before replacing and duplicating with a root browser. Long press the lib file, scroll through options, select link to this folder (maybe last option) and then browsing and selecting same folder location as seen from original link. Hint: the lib linking and appearance in its location will look the same when linked properly.
In the case of this thread, unzipping the ROM and reading the install scripts for proper linking may have been done to link the files after installing. The Bluetooth application simply needed to know where to get it's vital resources to work with. There are exceptions where replacing apk and lib, setting permissions, clearing data and rebooting aren't enough. Developers may write install scripts into patch zip accordingly as needed to get this done without a ROM update. Or even alternately in an aroma installer. Or those that test ROMs to support a developer may need to do this manually in that support capacity. Then again, it could be user in another country or region needing to make changes for themselves in order to use a developed ROM.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
thanks for replying but i have log cat and its said cant find some files can u help me ?
E/AndroidRuntime(11055): Process: com.android.bluetooth, PID: 11055
E/AndroidRuntime(11055): java.lang.RuntimeException: Unable to instantiate application com.android.bluetooth.btservice.AdapterApp: java.lang.ClassNotFoundException: Didn't find class "com.android.bluetooth.btservice.AdapterApp" on path: DexPathList[[zip file "/system/framework/javax.obex.jar", zip file "/data/app/com.android.bluetooth-2/base.apk"],nativeLibraryDirectories=[/data/app/com.android.bluetooth-2/lib/arm64, /data/app/com.android.bluetooth-2/base.apk!/lib/armeabi-v7a, /vendor/lib, /system/lib]]
Click to expand...
Click to collapse
hessamx said:
thanks for replying but i have log cat and its said cant find some files can u help me ?
Click to expand...
Click to collapse
Sorry. Gotta say I'm not experienced with resolving an issue like this. Not sure what you're doing when getting this logcat? References to zipped files? Should they be zipped?
What I would do in a situation like this and ensure I've done everything properly. Could be a simple mistake.
Otherwise, no idea if this helps you or not but a little searching found this blog:
https://javarevisited.blogspot.com/2011/08/classnotfoundexception-in-java-example.html?m=1
If Java tutorials makes sense to you, there's some suggested fixes to look into. Maybe it helps? Best wishes you resolve this and learn enough to help the next guy.
Sent from my PH-1 using Tapatalk
samep said:
Nice tutorial share. Thanks for helping.
What may be missing is linking the lib so the application works. It's a matter of checking original file as installed on phone before replacing and duplicating with a root browser. Long press the lib file, scroll through options, select link to this folder (maybe last option) and then browsing and selecting same folder location as seen from original link. Hint: the lib linking and appearance in its location will look the same when linked properly.
In the case of this thread, unzipping the ROM and reading the install scripts for proper linking may have been done to link the files after installing. The Bluetooth application simply needed to know where to get it's vital resources to work with. There are exceptions where replacing apk and lib, setting permissions, clearing data and rebooting aren't enough. Developers may write install scripts into patch zip accordingly as needed to get this done without a ROM update. Or even alternately in an aroma installer. Or those that test ROMs to support a developer may need to do this manually in that support capacity. Then again, it could be user in another country or region needing to make changes for themselves in order to use a developed ROM.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
I just want to say, thank you samep. I really appreciate your input on this subject. Your way of explaining this is well put and your points are valid. Bluetooth issues is something I have not had in any custom rom as of yet. However, I like to be prepared and knowledge is power.
Thought I'd give a little of my personal background followed by a few questions. I have no formal education with computers or Android. Although, I have not been a member on XDA for very long, I have been on this site for many years. Having lost my previous N4,
the only n910ps for sale were on the latest update 5DQ15. The fused 5 aboot prevents downgrading to previous firmwares. No chance of downgrading the boot or modem without SW REV CHECK Odin fail. Fortunately, 6.0 MM roms can still be flashed. With every single custom rom I flashed, my hotspot settings disappeared, except stock rooted deodexed roms. in which the hotspot setting remained. I remember reading a post somewhere on XDA stating that it was in CSC others.xml so I copied the entire CSC in stock rooted rom to external sd then flashed the custom rom and with the tutorial in the link above I replaced the custom roms CSC's with the stock rooted CSC's. Rebooted to TWRP wiped dalvik /chache and booted the phone. My Hotspot now appeared in the custom rom settings. However, I am not questioning your information. In fact, I remember reading an XDA thread about custom rom development that specifically backs up what you stated. More to it than simple copy and past, Its just I didnt know any other way. Although this worked for me with setting option , I know the phones Bluetooth connection is a bit more intricate than a simple CSC others.xml.
Which brings me to my question and I quote "Long press the lib file, scroll through options, select link to this folder (maybe last option)" What root browser do you recommend. This option is not provided as an option when I long press with my current root file manager. Yea, I know ES file manager has been kick of Google PS but Im still using it . LOL.. I wish to thank you ince again for your very informative posts.
Mr. JAVI said:
I just want to say, thank you samep. I really appreciate your input on this subject. Your way of explaining this is well put and your points are valid. Bluetooth issues is something I have not had in any custom rom as of yet. However, I like to be prepared and knowledge is power.
Thought I'd give a little of my personal background followed by a few questions. I have no formal education with computers or Android. Although, I have not been a member on XDA for very long, I have been on this site for many years. Having lost my previous N4,
the only n910ps for sale were on the latest update 5DQ15. The fused 5 aboot prevents downgrading to previous firmwares. No chance of downgrading the boot or modem without SW REV CHECK Odin fail. Fortunately, 6.0 MM roms can still be flashed. With every single custom rom I flashed, my hotspot settings disappeared, except stock rooted deodexed roms. in which the hotspot setting remained. I remember reading a post somewhere on XDA stating that it was in CSC others.xml so I copied the entire CSC in stock rooted rom to external sd then flashed the custom rom and with the tutorial in the link above I replaced the custom roms CSC's with the stock rooted CSC's. Rebooted to TWRP wiped dalvik /chache and booted the phone. My Hotspot now appeared in the custom rom settings. However, I am not questioning your information. In fact, I remember reading an XDA thread about custom rom development that specifically backs up what you stated. More to it than simple copy and past, Its just I didnt know any other way. Although this worked for me with setting option , I know the phones Bluetooth connection is a bit more intricate than a simple CSC others.xml.
Which brings me to my question and I quote "Long press the lib file, scroll through options, select link to this folder (maybe last option)" What root browser do you recommend. This option is not provided as an option when I long press with my current root file manager. Yea, I know ES file manager has been kick of Google PS but Im still using it . LOL.. I wish to thank you ince again for your very informative posts.
Click to expand...
Click to collapse
I can appreciate your background and effort and even the experiences you share. Best wishes for your success.
I used to use script manager pro for a root browser. When I started working with developers in XDA, they pointed me to Root Explorer by speedsoftware (link below). I use it exclusively since and find it as capable as the other. I had gotten this one years earlier as a free promotional app on Amazon Prime through their Android app store. I was ecstatic when the developers of Root Explorer asked for my license key to transfer it to Google Play! Really? I asked, not expecting satisfaction, and they complied stating they've done it for others as well. It's their discretion and pleasure to do so. The app is still in Google Play; I get my updates there now.
https://play.google.com/store/apps/details?id=com.speedsoftware.rootexplorer
But I haven't done much at all since leaving the Note 4 and Sprint. I forget so much when not using it. Sad but true and being honest. I miss those days but always wanted better data coverage and a faster phone. But even that's a work in progress.
Sent from my PH-1 using Tapatalk

Categories

Resources