Database Users

Samsung Vibrant 4G is BLOATED!

I want to remove all the unwanted bull so bad!!! Off the back it comes with so much unnecessary apps from T-Mobile.
I have less then 200MB left!
I can't root because the confirmed root that's out is for Windows. (SuperOneClick)

HeavyComponent said:
I want to remove all the unwanted bull so bad!!! Off the back it comes with so much unnecessary apps from T-Mobile.
I have less then 200MB left!
I can't root because the confirmed root that's out is for Windows. (SuperOneClick)
Click to expand...
Click to collapse
So run a windows virtual environment... or you can always just do rage manually.
And of course its bloated. Every phone comes that way these days. Just gotta root my friend.

Ok this is my first Vibrant so what's Rage and is it perm root? I can't find anything that says Rage on the development page.

I also caught it 190MB at corp store.
{
"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"
}
It may be defective because some members from hofo said it's 800MB left.
http://www.howardforums.com/showthread.php/1704050-what-to-get-nexus-s-vibrant-galaxy

omg is it sick or what though?? speedtest.net app!! I want to see this bad boy in action!
I'm a huge internet user on my phone btw hahaha

You'll find the Vibrant and SGS4G to be very easy to root compared to MTG4. Its always perm.
EDIT: You need to rename SU-V2 to SU. no extension.
Use the files you extract from that superoneclick to execute this.
- Extract the files to the Tools folder of your Android SDK folder
- Place your phone into Debugging Mode (Settings, Applications, Development, check USB Debugging)
- Open the command prompt (Start > Run > cmd > Press Enter)
- cd c:/wherever-your-sdk-tools-folder (Example: C:\Android-SDK-Windows\Tools)
- Then type adb devices to verify that the phone is connected. If it is connected, you will see the device serial number.
- Type in the below commands:
- adb push Superuser.apk /sdcard/Superuser.apk
- adb push su /sdcard/su
- adb push busybox /sdcard/busybox
- adb push rageagainstthecage /data/local/tmp/rageagainstthecage
- adb shell From here, you will see a $ instead of C:/
- cd data/local/tmp The output will return the same command as inputted
- chmod 0755 rageagainstthecage
- ./rageagainstthecage At this point, let it run and DO NOT TOUCH ANYTHING until it returns to the DOS Prompt (C:\Android-SDK-Windows\Tools). This will take up to two minutes or so.
- adb shell This time it will show a # sign as opposed to the $ sign before
- All of the below commands will again return the same output as the input
- mount -o rw,remount -t yaffs2 /dev/block/stl9 /system
- cp /sdcard/Superuser.apk /system/app/Superuser.apk
- cp /sdcard/su /system/xbin/su
- cp /sdcard/busybox /system/xbin/busybox
- chmod 4755 /system/xbin/su
- chmod 4755 /system/xbin/busybox
- mount -o ro,remount -t yaffs2 /dev/block/stl9 /system
- Exit x2 to close out of adb shell and the command prompt
I THINK that should work. Use at your own risk.

aloneinshadow said:
Use the files you extract from that superoneclick to execute this.
- Extract the files to the Tools folder of your Android SDK folder
- Place your phone into Debugging Mode (Settings, Applications, Development, check USB Debugging)
- Open the command prompt (Start > Run > cmd > Press Enter)
- cd c:/wherever-your-sdk-tools-folder (Example: C:\Android-SDK-Windows\Tools)
- Then type adb devices to verify that the phone is connected. If it is connected, you will see the device serial number.
- Type in the below commands:
- adb push Superuser.apk /sdcard/Superuser.apk
- adb push su /sdcard/su
- adb push busybox /sdcard/busybox
- adb push rageagainstthecage /data/local/tmp/rageagainstthecage
- adb shell From here, you will see a $ instead of C:/
- cd data/local/tmp The output will return the same command as inputted
- chmod 0755 rageagainstthecage-arm5.bin
- ./rageagainstthecage At this point, let it run and DO NOT TOUCH ANYTHING until it returns to the DOS Prompt (C:\Android-SDK-Windows\Tools). This will take up to two minutes or so.
- adb shell This time it will show a # sign as opposed to the $ sign before
- All of the below commands will again return the same output as the input
- mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
- cp /sdcard/Superuser.apk /system/app/Superuser.apk
- cp /sdcard/su /system/bin/su
- cp /sdcard/busybox /system/bin/busybox
- chmod 4755 /system/bin/su
- chmod 4755 /system/bin/busybox
- mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
- Exit x2 to close out of adb shell and the command prompt
I THINK that should work. Use at your own risk.
Click to expand...
Click to collapse
Thanks! And this is temp root? If so lets say I rebooted the device how would I get the root back?

HeavyComponent said:
Thanks! And this is temp root? If so lets say I rebooted the device how would I get the root back?
Click to expand...
Click to collapse
All roots on this phone are perm roots. No need for temp.

Oh ok cool.
You mind giving me the link where you got your info from? You did say "THINK" it will work. Lol

Um... Google? To be honest I didn't get it from any one page in perticular, just pieced it together. I've actually done it before, I just can't remember this one detail:
- mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
I can't remember if that one line is right or not. The rest I know works.
EDIT: I just tested this line on my phone and it ran fine. I'd try it and let me know if it works.

Ok good enough or me, I will give it a try.
EDIT: By the way, I'm on a Mac.

HeavyComponent said:
Ok good enough or me, I will give it a try.
EDIT: By the way, I'm on a Mac.
Click to expand...
Click to collapse
Yea I kinda figured. Nothing we can do about that now I'm afraid, I only hope you've learned from your mistakes.

What mistakes? The process works just as if I was on Windows just instead of "adb" I type in "./adb". It should work, I'll give it a try.
One thing I wanted to mention was their is 2 versions of su in the SuperOneClick file. Does it matter which one I use? su-v1 and su-v2.

HeavyComponent said:
What mistakes? The process works just as if I was on Windows just instead of "adb" I type in "./adb". It should work, I'll give it a try.
One thing I wanted to mention was their is 2 versions of su in the SuperOneClick file. Does it matter which one I use? su-v1 and su-v2.
Click to expand...
Click to collapse
rename SU-V2 to SU.
And I was referring to your mistake to buy a Mac.

aloneinshadow said:
So run a windows virtual environment... or you can always just do rage manually.
And of course its bloated. Every phone comes that way these days. Just gotta root my friend.
Click to expand...
Click to collapse
iOS and WP7 Devices aren't, and neither are T-Mobile's newer Blackberries. The excessive bloat seems to be a big thing on Symbian, Android, and Windows Mobile.

aloneinshadow said:
rename SU-V2 to SU.
And I was referring to your mistake to buy a Mac.
Click to expand...
Click to collapse
- adb shell This time it will show a # sign as opposed to the $ sign before
Never turned into "#" still shows "$". I did everything and it all went well until that part.

N8ter said:
iOS and WP7 Devices aren't, and neither are T-Mobile's newer Blackberries. The excessive bloat seems to be a big thing on Symbian, Android, and Windows Mobile.
Click to expand...
Click to collapse
My bad. All phones with operating systems that are worth at least two squirts of piss, are bloated from the start.

HeavyComponent said:
- adb shell This time it will show a # sign as opposed to the $ sign before
Never turned into "#" still shows "$". I did everything and it all went well until that part.
Click to expand...
Click to collapse
Hmmm... not sure why it didn't work. I'm half tempted to just tell you to download Wine for mac and run superoneclick, but you've come this far. I'd just keep going with the code and see what happens. Can't really screw it up, it just won't work.
EDIT: Looks like I had this wrong. I think it should be:
- mount -o rw,remount -t yaffs2 /dev/block/stl9 /system
Based it off of this run by superoneclick:
SuperOneClick v1.6.5.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
103 KB/s (5392 bytes in 0.051s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
ROOTED
Pushing busybox...
1264 KB/s (1062992 bytes in 0.821s)
OK
chmod busybox...
OK
Getting mount path...
/dev/block/stl9
OK
Reading OS Version properties...
Version: 2.2.1
OK
Remounting system with read-write access...
OK
Pushing su-v2...
449 KB/s (26264 bytes in 0.057s)
OK
chmod su...
OK
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK
Copying busybox (/system/xbin/)...
OK
chmod busybox (/system/xbin/)...
OK
Installing busybox (/system/xbin/)...
OK
Pushing Superuser.apk...
1323 KB/s (196521 bytes in 0.145s)
OK
Remounting system with read-only access...
mount: mounting /dev/block/stl9 on /system failed: Device or resource busy
OK
Remounting system with read-only access...
OK

aloneinshadow said:
Hmmm... not sure why it didn't work. I'm half tempted to just tell you to download Wine for mac and run superoneclick, but you've come this far. I'd just keep going with the code and see what happens. Can't really screw it up, it just won't work.
Click to expand...
Click to collapse
Ok I tried the command over right before that step and now it's working.
I'm assuming "cp" is copy and paste? How do I do that? Because I typed in "cp" thinking it's part of the command, but it says "cp: not found".

Try "Busybox cp" I think you also can use dd: "dd if=/sdcard/su of=/system/xbin/su" instead of cp.

EVO Shift Temp Root for 2.3.3 and HBoot Downgrade

To downgrade your HBOOT to go back to 2.2 visit this link http://forum.xda-developers.com/showthread.php?t=1255474
This will allow you to flash 2.2 to perm root the phone
If you wish to help with perm root status for Android 2.3.3, please visit this thread http://forum.xda-developers.com/showthread.php?t=1218580
Thanks to everyone in this post who has helped get this far. You will need to have the Android SDK installed and working knowledge of ADB and basic file system structure.
Major help from minneyar
TEMP ROOT Instructions:
Download http://tinyw.in/1lI
Unzip if required and put in your ADB folder
Launch command prompt and navigate to your ADB folder
adb push fre3vo /data/local/tmp/
adb shell
chmod 777 /data/local/tmp/fre3vo
/data/local/tmp/fre3vo -debug -start fbb58a00 -end FFFFFFFF (if this doesn't work, try rebooting phone)
Download these 2 files here and put them in your ADB directory: http://forum.xda-developers.com/showthread.php?p=14927732#post14927732
exit back to command prompt if you aren't there already
adb push Superuser3-beta1.apk /data/app/
adb push su-3.0-alpha7 /data/local/tmp
adb shell (should now see # instead of $)
cd /data/local/tmp
chmod 777 su-3.0-alpha7
./su-3.0-alpha7
cd /
mount -o remount,rw -t rootfs rootfs /
rm vendor
mkdir vendor
mkdir vendor/bin
cat /data/local/tmp/su-3.0-alpha7 > /vendor/bin/su
chmod 4755 /vendor/bin/su
You now have temp root. Disregard any notification about outdated SU binary. Root will go away if you reboot. If you reboot your phone you can obtain root again by just running the following
adb shell
chmod 777 /data/local/tmp/fre3vo
/data/local/tmp/fre3vo -debug -start fbb58a00 -end FFFFFFFF
adb shell (should now see # instead of $)
cd /data/local/tmp
chmod 777 su-3.0-alpha7
./su-3.0-alpha7
cd /
mount -o remount,rw -t rootfs rootfs /
rm vendor
mkdir vendor
mkdir vendor/bin
cat /data/local/tmp/su-3.0-alpha7 > /vendor/bin/su
chmod 4755 /vendor/bin/su
I haven't found a way to re-root after rebooting without connecting to a PC

Type su and see if it gives you root permissions
Sent from my MiuiSpeedy

says su: not found.

You are saying you cannot install the superuser app? From reading in the Evo3D forums, you could install Superuser, even without being rooted, but it obviously won't allow root access, until you run a root exploit.
Try rebooting the phone, installing superuser, run fre3vo, and then try the adb shell, and su method.
This is getting interesting. Hopefully you are on to something.

Stuke00 said:
See screenshot. Doesn't the # mean temp rooted? Tho I cannot install SU and Root Explorer isn't working. Anything else I need to do first or something?
Click to expand...
Click to collapse
Looks hopeful!

tokuzumi said:
You are saying you cannot install the superuser app? From reading in the Evo3D forums, you could install Superuser, even without being rooted, but it obviously won't allow root access, until you run a root exploit.
Try rebooting the phone, installing superuser, run fre3vo, and then try the adb shell, and su method.
This is getting interesting. Hopefully you are on to something.
Click to expand...
Click to collapse
Okay let me clarify
I can install SU but it wouldn't install the binaries. I did all of the above. Says su: not found.
I then tried something else.
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# cat /system/bin/sh > /system/bin/su
# chmod 4755 /system/bin/su
I was then able to get the SU binaries to install but Titanium Backup says:
"Busybox works but the "su" command does not elevate to root: "whoami" reports "app_135" instead of root/uid 0.
then su from the command prompt was saying "link_image[1935]: 3160 missing essential tablesCANNOT LINK EXECUTABLE" and now back to su: not found again....

I don't know enough about linux commands to give you any real info. Like in the other thread, talk to agrabren, to see what he has to say.

tokuzumi said:
I don't know enough about linux commands to give you any real info. Like in the other thread, talk to agrabren, to see what he has to say.
Click to expand...
Click to collapse
Yeah I tweeted him with what I could provide with 160 characters. Just waiting now.

Well here's a tweet he put out a couple of hours ago.
@agrabren: For those with the SHIFT, it's a known bug in my code that we missed the address. One too many zeroes in the list. I'll try to fix it soon.
Sent from my PG06100 using XDA App

crump84 said:
Well here's a tweet he put out a couple of hours ago.
@agrabren: For those with the SHIFT, it's a known bug in my code that we missed the address. One too many zeroes in the list. I'll try to fix it soon.
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Yeah he posted that right after I gave him the memory address for the exploit. Just means that I did it the manual way through debugging. At least I think so... hopefully soon!

Good news, everybody! I have successfully acquired temp root on my Shift!
First, fre3vo has to be pointed at the right address. After copying it over to my phone, I did "adb shell" and then ran it like so:
/data/local/tmp/fre3vo -debug -start fbb58a00 -end FFFFFFFF
That printed out a message that it found an exploit and kicked me out of the shell. After doing "adb shell" again, I got a command prompt. I tried installing the 2.3.6.3 version of Superuser, but it complained about being unable to install "su"; I tried to find a separate su binary and copy it over manually, but it didn't work due to a linker error.
After searching around, I found a beta version of Superuser 3:
http://forum.xda-developers.com/showthread.php?p=14927732#post14927732
First I uninstalled the old version of Superuser and then used adb to install the new one from that thread. I ran it and it said it was unable to install su, so I downloaded the version of su provided there and installed it manually. The process went something like:
Code:
adb push su-3.0-alpha7 /data/local/tmp
adb shell
# cd /data/local/tmp
# chmod 4755 su-3.0-alpha7
# ./su-3.0-alpha7
# mount -o remount,rw -t ext3 /dev/block/mmcblk0p26 /system
# cat su-3.0-alpha7 > /system/bin/su
# chmod 4755 /system/bin/su
I don't know if explicitly running "./su-3.0-alpha7" is necessary, it just seemed like a good idea at the time. I don't know if everybody's block device will be named "mmcblk0p26", I used "mount" to figure out what was mounted at /system.
Anyway, after all that was done, I ran Superuser again and it didn't complain. To test it out, I started up Wireless Tether. It asked me for superuser permissions, which I granted it, and it's working fine.
Root successful!

Good job!!
Sent from my Speedy HTC EVO shift on XDA Premium app

I followed those steps exactly and got what I would call a partial root. Some of the 'you need root' errors are gone but "su" still results in 'not found' even though "mkdir su" results in 'file exists.'
mmcblk0p26 exists on this unit.
The weirdest part is that Adfree will accept the device as rooted and with superuser but says it can't find a partition to modify. And after a reboot root is definitely gone.
I think you're on to it but it isn't quite there yet.

It seems to be fully temprooted to me; I have to redo it if I reboot, but otherwise it's working perfectly. After following the steps I listed above, running "ls -l /system/bin/su" should produce this output:
Code:
# ls -l /system/bin/su
ls -l /system/bin/su
-rwsr-xr-x root root 22228 2011-07-25 19:14 su
If it says "No such file or directory" instead, then the su binary isn't in the right place.
Looking back over what I wrote, I think I left out a step -- if you were following what I listed exactly, it probably won't work, because I forgot to change to the /data/local/tmp directory. I'll update that...
Update: after playing around with it for a while, something is definitely not quite right. Everything works fine at first; I've tested Wireless Tether and Titanium Backup and they're both fine. After leaving my phone for a while and coming back, though, applications that try to get root access mysteriously fail. The dialog prompt doesn't even appear.
Going back into the adb shell, /system/bin/su is still there, but trying to run "su" causes this to happen:
Code:
# su
su
link_image[1935]: 3802 missing essential tablesCANNOT LINK EXECUTABLE
But if I use cat to overwrite su and then chmod it again, everything works. su must somehow be getting modified by something else and replaced with a bad version... but I'm not sure where to look.

I caught something like that.
I think there should be a chmod 777 su-3.0-alpha7 after cd /data/local/tmp

minneyar said:
It seems to be fully temprooted to me; I have to redo it if I reboot, but otherwise it's working perfectly. After following the steps I listed above, running "ls -l /system/bin/su" should produce this output:
Code:
# ls -l /system/bin/su
ls -l /system/bin/su
-rwsr-xr-x root root 22228 2011-07-25 19:14 su
If it says "No such file or directory" instead, then the su binary isn't in the right place.
Looking back over what I wrote, I think I left out a step -- if you were following what I listed exactly, it probably won't work, because I forgot to change to the /data/local/tmp directory. I'll update that...
Update: after playing around with it for a while, something is definitely not quite right. Everything works fine at first; I've tested Wireless Tether and Titanium Backup and they're both fine. After leaving my phone for a while and coming back, though, applications that try to get root access mysteriously fail. The dialog prompt doesn't even appear.
Going back into the adb shell, /system/bin/su is still there, but trying to run "su" causes this to happen:
Code:
# su
su
link_image[1935]: 3802 missing essential tablesCANNOT LINK EXECUTABLE
But if I use cat to overwrite su and then chmod it again, everything works. su must somehow be getting modified by something else and replaced with a bad version... but I'm not sure where to look.
Click to expand...
Click to collapse
YES! I have root! I was able to install a screenshot app and test it this is amazing progress! Thanks for that.
So now when I reboot, you have to do the entire thing again? SU and all?

Stuke00 said:
So now when I reboot, you have to do the entire thing again? SU and all?
Click to expand...
Click to collapse
Yes, every time you reboot you'll have to redo the whole process, including running fre3vo and then copying su into /system/bin. Hopefully somebody will figure out a permanent root soon.

Wow those SU binaries are disappearing before I even reboot! Already gone and I haven't rebooted the phone

I think I had that issue too. I just couldn't believe the files just disappeared and thought I did something wrong somewhere.

Would a logcat help anyone at all? Anything I should look for?

[TUTORIAL]How to manual root official 2.3

I always have problems to root official 2.3 with automatic ways, and found that this caused from some adb miscommunication.
So this is how to do it manual, in case automatic ways stacked.
First install adb-sdk and add its path to system variables, so to don't have to go to adb' s path before you can run it.
Then download doomlord' s rooting tool and extract it to drive C:\DoomLordRoot.v3.
http://forum.xda-developers.com/attachment.php?attachmentid=784296&stc=1&d=1321435888
Preparation steps on device:
1) Dial: *#*#2846579#*#*
2) Go to projectmenu > background settings > log settings > log switch > set Log on
3) Reboot Phone
4) Switch USB Debugging ON
5) uncheck fast boot from settings -> applications
Click to expand...
Click to collapse
Open windows command prompt window and do the above:
Code:
adb push c:\DoomLordRoot.v3\files\zergRush /data/local/tmp/
[COLOR="DarkSlateBlue"]adb shell[/COLOR]
chmod 777 /data/local/tmp/zergRush
./data/local/tmp/zergRush
[COLOR="DarkSlateBlue"]Hit CTRL+C to exit from adb shell[/COLOR]
adb push c:\DoomLordRoot.v3\files\busybox /data/local/tmp/
[COLOR="DarkSlateBlue"]adb shell[/COLOR]
su
chmod 755 /data/local/tmp/busybox
/data/local/tmp/busybox mount -o remount,rw /system
dd if=/data/local/tmp/busybox of=/system/xbin/busybox
chown root.shell /system/xbin/busybox
chmod 04755 /system/xbin/busybox
/system/xbin/busybox --install -s /system/xbin
rm -r /data/local/tmp/busybox
[COLOR="DarkSlateBlue"]Hit CTRL+C to exit again from adb shell[/COLOR]
adb push c:\DoomLordRoot.v3\files\su /system/bin/su
[COLOR="DarkSlateBlue"]adb shell[/COLOR]
su
chown root.shell /system/bin/su
chmod 06755 /system/bin/su
rm /system/xbin/su
ln -s /system/bin/su /system/xbin/su
[COLOR="DarkSlateBlue"]Hit CTRL+C to exit once more from adb shell[/COLOR]
adb push c:\DoomLordRoot.v3\files\Superuser.apk /system/app/
[COLOR="DarkSlateBlue"]adb shell[/COLOR]
su
cd /data/local/tmp/
rm *
reboot
This is basic what the runme.bat file does, just some paths corrected to point to the right locations.

I have the latest official gingerbread (I think v3) and have been trying to root with no luck. I've gone through the steps here but when try to get root access (su), it gives me permission denied...
Any ideas?

Oneclickroot v2. 2 did the work for me or something like this
Sent from my U8800

SS said:
I have the latest official gingerbread (I think v3) and have been trying to root with no luck. I've gone through the steps here but when try to get root access (su), it gives me permission denied...
Any ideas?
Click to expand...
Click to collapse
This probably means that rooting failed.
What messages you get when you run zergrush?

dancer_69 said:
This probably means that rooting failed.
What messages you get when you run zergrush?
Click to expand...
Click to collapse
I got messages for sending 149, then 189 zerglings, then messages about not being able to mount, find or write to directories.
It seems like it wasn't able to get root access to be able to run its process.
In any case, I just downgraded to the previous release and then used ZergRush, which worked perfectly

don't work.

try this, it works for my B528 rom!
http://forum.xda-developers.com/showpost.php?p=23565074&postcount=7

[Q] About root Motorola RAZR 201M(XT902)

Hello everyone...
I have a Motorola RAZR 201M(XT902) in Japan and use Motofail2go to root it.But it doesn't work.
(follow http://forum.xda-developers.com/showthread.php?p=32889627)
I installed Sudoku.apk and push the motofail2go to the device(also su,Superuser.apk,busybox).
when
$ run-as com.motorola.bug2go /data/local/tmp/motofail2go prep2
Here is the error message:
"run-as: exec failed for /data/local/tmp/motofail2go Error: Operation not permitted"
and i try $ run-as com.motorola.bug2go
but error message : "run-as: exec failed"
Anyone help? Thanks...

Sorry buddy. Nothing works. We 201m users are SOL.

Have you tried this?
http://www.droidrzr.com/index.php/topic/15208-root-motochopper-yet-another-android-root-exploit/

Thanks Paul!
No luck with that either. Appreciate the feedback, however.

I hope somebody will study the XT902 root.

goodayoo said:
I hope somebody will study the XT902 root.
Click to expand...
Click to collapse
I really want this thing rooted. How do one go about figuring out how to root it? I assume because of it's lack of popularity, no one has done it, but I'm willing to do the grunt work if there's some sort of guide or assistance. I changed over to DoCoMo with the GS4 and now have this paperweight that I would want to actually use.
Thanks!

Almalieque said:
I really want this thing rooted. How do one go about figuring out how to root it? I assume because of it's lack of popularity, no one has done it, but I'm willing to do the grunt work if there's some sort of guide or assistance. I changed over to DoCoMo with the GS4 and now have this paperweight that I would want to actually use.
Thanks!
Click to expand...
Click to collapse
There some Japanese guys doing some things to try and get root. They are active. The site has a lot of rather unpleasant (read offensive) advertisements. PM if you are interested (its in Japanese)

root
help!!!

Root and Unlocked bootloaders!
Proceed at yor own risk
hungln03 said:
help!!!
Click to expand...
Click to collapse
1)Prep
Android SDKと各種ドライバを導入する。
以下の必要ファイルをC:\***（何でも良い）に配置する。
　・XT902_SBMの中身(http://www1.axfc.net/uploader/so/2991543 >>125氏)
　・su（http://www1.axfc.net/uploader/so/2918729 password：f10d）
　・Superuser.apk（in the above downloaded）
　・busybox（in the above downnloaded）
201M Plug the phone into the comp
any port will do
2)adb pushで必要ファイルを/data/local/tmp転送
コマンドプロンプトを開く
C:\Users\（ユーザー名） >cd C:\***
adb push su /data/local/tmp
adb push Superuser.apk /data/local/tmp
adb push busybox /data/local/tmp
adb push unlock_security_module /data/local/tmp
adb push break_setresuid /data/local/tmp/
adb push mole-plough-ccsecurity.so /data/local/tmp/
adb push mole-plough-lsm.so /data/local/tmp/
3)unlock_security_module（temp root）
adb shell
[email protected]:/ $ cd /data/local/tmp/
[email protected]:/data/local/tmp $ chmod 777 *
[email protected]:/data/local/tmp $ ./unlock_security_module
[email protected]:/data/local/tmp $ ./break_setresuid
（unlock_security_moduleが動いてMIYABIとNANDロック解除）
　（色々表示されるので↓が出る間で待つ）
　Unlocked LSM.
　Do setresuid...
　OK.
　[email protected]:/data/local/tmp #
　（#if done correctly temp root should be achieved）
271 ：270：2013/09/15(日) 23:31:42.67 ID:tIg7fkl6
4)system putting together su，Superuser.apk，busybox
[email protected]:/data/local/tmp # mount -o rw,remount /system /system
[email protected]:/data/local/tmp # cat /data/local/tmp/su > /system/xbin/su
[email protected]:/data/local/tmp # cat /data/local/tmp/busybox > /system/xbin/busybox
[email protected]:/data/local/tmp # cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
[email protected]:/data/local/tmp # chmod 644 /system/app/Superuser.apk
[email protected]:/data/local/tmp # cd /system/xbin
[email protected]:/system/xbin # chown root.root su
[email protected]:/system/xbin # chown root.root busybox
[email protected]:/system/xbin # chmod 6755 su
[email protected]:/system/xbin # chmod 755 busybox
[email protected]:/system/xbin # mount -o ro,remount /system /system
After the opperation is done it is ok to remove the cable from the pc。
check and see if「SuperSU」was installed if it wasn't download chainfire (su) from the play store
⇒SU --> update
Fro the play store download busybox。
⇒busybox -->update
Get the right CWM.img http://forum.xda-developers.com/showthread.php?t=2298521の201M
put the CWM.img you downloaded in motoapoc file you find here
adb push unlock /data/local/tmp/
adb shell chmod 755 /data/local/tmp/unlock
adb shell
cd /data/local/tmp/
chmod 777 *
./unlock_security_module
./break_setresuid
./unlock
New Command prompt
5)Inserting CWM(PC Operation)
adb shell "su -c 'mount -o remount,rw /system'"
adb shell "su -c 'mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak'"
adb shell "su -c 'mv /system/recovery-from-boot.p /system/recovery-from-boot.bak'"
adb push cwm.img /data/local/tmp/cwm.img > nul
adb shell "su -c 'dd if=/data/local/tmp/cwm.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery'"
adb shell "su -c 'rm /data/local/tmp/cwm.img'"
adb reboot recovery
You should be in CWM
Cheers! I take 0 credit. Long Live the Developers!!

I don't own the 902, but it's good to see this. I know quite a few people have been looking for this. You should start your own thread with the procedures, so it will get more publicity.

Thank u!
thank u so much.!1

sbeaber4 said:
Proceed at yor own risk
271 ：270：2013/09/15(日) 23:31:42.67 ID:tIg7fkl6
Get the right CWM.img http://forum.xda-developers.com/showthread.php?t=2298521の201M
put the CWM.img you downloaded in motoapoc file you find here
adb push unlock /data/local/tmp/
adb shell chmod 755 /data/local/tmp/unlock
adb shell
cd /data/local/tmp/
chmod 777 *
./unlock_security_module
./break_setresuid
./unlock
New Command prompt
5)Inserting CWM(PC Operation)
adb shell "su -c 'mount -o remount,rw /system'"
adb shell "su -c 'mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak'"
adb shell "su -c 'mv /system/recovery-from-boot.p /system/recovery-from-boot.bak'"
adb push cwm.img /data/local/tmp/cwm.img > nul
adb shell "su -c 'dd if=/data/local/tmp/cwm.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery'"
adb shell "su -c 'rm /data/local/tmp/cwm.img'"
adb reboot recovery
You should be in CWM
Cheers! I take 0 credit. Long Live the Developers!!
Click to expand...
Click to collapse
Can you tell me more about this step

Confirm?
Can confirm if the latest instructions have worked for your 201m?
That your rooted and bootloader unlock.
Thanks a bunch!

Boot loader is unlocked and CWM is installed. Initially I still
Had temp root so I flashed slim beans xt907 rom. It works. I'm unable to test data with it as I don't have a SoftBank sim. Also I still can't connect to the play store.

sbeaber4 said:
Boot loader is unlocked and CWM is installed. Initially I still
Had temp root so I flashed slim beans xt907 rom. It works. I'm unable to test data with it as I don't have a SoftBank sim. Also I still can't connect to the play store.
Click to expand...
Click to collapse
Thanks for the feedback.
Still awaiting more confirmation with others. It's a step forward though.
I've had my phone for almost a year now. If I cancel my softbank service or run the contract to the end I want an option to root and unlock the bootloader in the future.

could u provide more friendly filehost?
i can't find the download button there

Root! (temp root that is...)
I'm just posting to confirm I've rooted my 201m (xt902).
Props to sbeaber4!
From my limited knowledge since it's temp root if I restart my phone I lose root access...
Next step in the future unlock bootloader.
Peace y'all.

Quick Tip
zenstarlight said:
I'm just posting to confirm I've rooted my 201m (xt902).
Props to sbeaber4!
From my limited knowledge since it's temp root if I restart my phone I lose root access...
Next step in the future unlock bootloader.
Peace y'all.
Click to expand...
Click to collapse
Found that if I a did restart my phone root was lost but I found a quick fix without going through the whole process again.
Just do these steps
unlock_security_module（temp root）
adb shell
[email protected]:/ $ cd /data/local/tmp/
[email protected]:/data/local/tmp $ ./unlock_security_module
Just enter those three steps then you're back to temp root
Also you can just to a quick reboot with link2sd or any other app that just reboots the android ui. You don't have to enter commands every time you reboot unless it's a full reboot.

Help for Gaigin rooting 201M
sbeaber4 said:
Proceed at yor own risk
...
You should be in CWM
Cheers! I take 0 credit. Long Live the Developers!!
Click to expand...
Click to collapse
Noob on XDA, and rooted a MT4G in the past wth help from these forums.
Can someone help translate the kanji for rooting the 201M? Will rooting allow you to change the device location and prevent random all Japanese pop-up alerts/"are you sure" messages? Thanks for any help

kprower said:
Noob on XDA, and rooted a MT4G in the past wth help from these forums.
Can someone help translate the kanji for rooting the 201M? Will rooting allow you to change the device location and prevent random all Japanese pop-up alerts/"are you sure" messages? Thanks for any help
Click to expand...
Click to collapse
Once CWM is online you might be able to flash a VZW or Aussie stock ROM. Actually, you could probably flash CM... That'll fix the Japanese popups. Of course, it also could very possibly brick it. Proper precautions must be made... On my tablet at the moment, does anyone know if sbf.droid-developers has 902 images?
Sent from my Nexus 7 using Tapatalk 4

Intel (Joying) Android 6.0.1 and Bluetooth

Hi,
I hope this is a thread that will soon be completely unnecessary.
Disclaimer: I have hardly any knowledge of bluetooth. I don't use it much either. I use WiFi tethering, I hardly ever call in my car (it is considered too dangerous and I agree), I have my music on SDcard.
So the reason for this post is not because I want "to tell" about bluetooth. The only reason is that multiple users sent me PMs asking questions about it.
To have it not too cluttered, and without the real bluetooth experts being able to give their valuable opinion in the forum, I created this post.
I downloaded a Cyanogenmod CM-13 6.0.1 (beta) ROM for the Asus Zenfone, and I downloaded the official 6.0.1 Asus ROM for the Zenfone.
The Asus Zenfone has an Intel(R) atom Z3560 CPU.
Our Joying has a Sofia x64 from the C3200 series, so there is a difference but programmaticaly they are the same. I can't find specifics on the used bluetooth chip set and of course the underlying MCU, in case of the Joying, is totally different.
So for those users who asked me and are brave enough to try for themselves I created two zips containing all necessary files AFAIK.
The CM13 file is of course the Cyanogenmod, the UL-Z00 is the official Asus one. The real system "stuff" in the Cyanogenmod is in general more a "fits all possible x86 architectures" build whereas brand specific ROMS are of course more tuned to the specific hardware.
I took these from the following links:
http://rootmygalaxy.net/install-cm13-on-zenfone-2/
http://rootmygalaxy.net/download-in...c550kl-android-6-0-1-marshmallow-beta-update/
https://www.asus.com/Phone/ZenFone_2_ZE551ML/HelpDesk_Knowledge/ (and likewise support pages for the variety of the models)
So again: If you are brave enough, try for yourself.
I hope some bluetooth expert can shine a light on this. Or better: That Joying or FYT fixes it.
I also downloaded another intel-MTCD (other MCU) head unit ROM, but it seems for 95% the same as the Joying 27 April first 6.0.1 ROM, so to me not worth the effort.

surfer63 said:
Hi,
I hope this is a thread that will soon be completely unnecessary.
Disclaimer: I have hardly any knowledge of bluetooth. I don't use it much either. I use WiFi tethering, I hardly ever call in my car (it is considered too dangerous and I agree), I have my music on SDcard.
So the reason for this post is not because I want "to tell" about bluetooth. The only reason is that multiple users sent me PMs asking questions about it.
To have it not too cluttered, and without the real bluetooth experts being able to give their valuable opinion in the forum, I created this post.
I downloaded a Cyanogenmod CM-13 6.0.1 (beta) ROM for the Asus Zenfone, and I downloaded the official 6.0.1 Asus ROM for the Zenfone.
The Asus Zenfone has an Intel(R) atom Z3560 CPU.
Our Joying has a Sofia x64 from the C3200 series, so there is a difference but programmaticaly they are the same. I can't find specifics on the used bluetooth chip set and of course the underlying MCU, in case of the Joying, is totally different.
So for those users who asked me and are brave enough to try for themselves I created two zips containing all necessary files AFAIK.
The CM13 file is of course the Cyanogenmod, the UL-Z00 is the official Asus one. The real system "stuff" in the Cyanogenmod is in general more a "fits all possible x86 architectures" build whereas brand specific ROMS are of course more tuned to the specific hardware.
I took these from the following links:
http://rootmygalaxy.net/install-cm13-on-zenfone-2/
http://rootmygalaxy.net/download-in...c550kl-android-6-0-1-marshmallow-beta-update/
https://www.asus.com/Phone/ZenFone_2_ZE551ML/HelpDesk_Knowledge/ (and likewise support pages for the variety of the models)
So again: If you are brave enough, try for yourself.
I hope some bluetooth expert can shine a light on this. Or better: That Joying or FYT fixes it.
I also downloaded another intel-MTCD (other MCU) head unit ROM, but it seems for 95% the same as the Joying 27 April first 6.0.1 ROM, so to me not worth the effort.
Click to expand...
Click to collapse
Will give this a try as soon as possible
Sent from my HUAWEI M2-802L using Tapatalk

I am going to have a try today and see what happens.
@surfer63
Is there anything in the joying server that is interacting with the Bluetooth core or the Joying BT app?
I have a funny feeling that something joying is turning the BT off if not using the Joying BT app, been doing this since android 6.0 after about 3mins.
sucks for people running apps that don't require the Joying BT app, eg Inet Truma Box for incar heating controlled with BT

So I started today putting together a batch ADB file to test the CM version of the BT for joying
I have completely run out of time to finish it and I wont be able to complete it till next week, there is quite a bit to go on it and i am not even sure it works, so if anyone want to continue with it, u can.
The ADB Files are not my work and i don't take credit for it, I only added the files and made the batch
This work is not complete and SHOULD NOT BE USED in its current state.
Attached is the half built BluetoothUpgrade Files
View attachment BluetoothUpdate.zip
Echo off
adb kill-server
adb connect %1
adb root
adb connect %1
adb shell mount -o rw,remount /system
adb shell mount -o rw,remount /system /system
adb shell mount -o rw,remount /
adb shell mount -o rw,remount / /
# Push New Files To SDcard (Should Be Finished)
adb push Bluetooth.apk /sdcard/
adb push BluetoothExt.apk /sdcard/
adb push BluetoothMidiService.apk /sdcard/
adb push btnvtool /sdcard/
adb push btsnoop /sdcard/
adb push MTP_WCD9306_Bluetooth_cal.acdb /sdcard/
adb push MTP_Bluetooth_cal_ZD550KL.acdb /sdcard/
adb push MTP_Bluetooth_cal_ZE550KL.acdb /sdcard/
adb push MTP_Bluetooth_cal_ZE600KL.acdb /sdcard/
adb push QRD_Bluetooth_cal.acdb /sdcard/
adb push QRD_SKUL_Bluetooth_cal.acdb /sdcard/
adb push bt_did.conf /sdcard/
adb push bt_stack.conf /sdcard/
adb push android.hardware.bluetooth.xml /sdcard/
adb push android.hardware.bluetooth_le.xml /sdcard/
adb push init.qcom.bt.sh /sdcard/
adb push libbluetooth_jni.so /sdcard/
adb push bluetooth.default.so /sdcard/
adb push libbt-vendor.so /sdcard/
adb push libbtnv.so /sdcard/
# Move The Original Files To OLD Files (List Not Finsished)
adb shell "su -c cp /system/Bluetooth/Bluetooth.apk /system/Bluetooth/Bluetooth.apk.old"
adb shell "su -c cp /system/Bluetooth/oat/x86/Bluetooth.odex /system/Bluetooth/oat/x86/Bluetooth.odex.old"
adb shell "su -c cp /system/Bluetooth/lib/libbluetooth_jni.so /system/Bluetooth/lib/libbluetooth_jni.so.old"
adb shell "su -c cp /system/BluetoothMidiService/BluetoothMidiService.apk /system/BluetoothMidiService/BluetoothMidiService.apk.old"
adb shell "su -c cp /system/BluetoothMidiService/oat/x86/BluetoothMidiService.odex /system/BluetoothMidiService/oat/x86/BluetoothMidiService.odex.old"
# Make New Directories (List Not Finished)
adb shell "mkdir /system/app/BluetoothExt/"
adb shell "mkdir /system/etc/acdbdata/"
adb shell "mkdir /system/etc/acdbdata/MTP/"
adb shell "mkdir /system/etc/acdbdata/MTP/msm8939-tapan-snd-card/"
adb shell "mkdir /system/etc/acdbdata/MTP/ZD550KL/"
adb shell "mkdir /system/etc/acdbdata/MTP/ZE550KL/"
adb shell "mkdir /system/etc/acdbdata/MTP/ZE600KL/"
adb shell "mkdir /system/etc/acdbdata/QRD/"
adb shell "mkdir /system/etc/acdbdata/QRD/msm8939-snd-card-skul/"
adb shell "mkdir /system/vendor/lib64"
# Set Permissions Of New Directories (List Not Finished)
adb shell "chmod 0755 /system/app/BluetoothExt/"
adb shell "chmod 0755 /system/etc/acdbdata/"
adb shell "chmod 0755 /system/etc/acdbdata/MTP/"
adb shell "chmod 0755 /system/etc/acdbdata/MTP/msm8939-tapan-snd-card/"
adb shell "chmod 0755 /system/etc/acdbdata/MTP/ZD550KL/"
adb shell "chmod 0755 /system/etc/acdbdata/MTP/ZE550KL/"
adb shell "chmod 0755 /system/etc/acdbdata/MTP/ZE600KL/"
adb shell "chmod 0755 /system/etc/acdbdata/QRD/"
adb shell "chmod 0755 /system/etc/acdbdata/QRD/msm8939-snd-card-skul/
adb shell "chmod 0755 /system/vendor/lib64"
# Copy The New Files To Locations (Should Be Finished, Not tested)
adb shell "su -c cp /sdcard/Bluetooth.apk /system/app/Bluetooth/Bluetooth.apk"
adb shell "su -c cp /sdcard/BluetoothExt.apk /system/app/BluetoothExt/BluetoothExt.apk"
adb shell "su -c cp /sdcard/BluetoothMidiService.apk /system/app/BluetoothMidiService/BluetoothMidiService.apk"
adb shell "su -c cp /sdcard/btnvtool /system/bin/btnvtool"
adb shell "su -c cp /sdcard/btsnoop /system/bin/btsnoop"
adb shell "su -c cp /sdcard/MTP_Bluetooth_cal.acdb /system/etc/acdbdata/MTP/MTP_Bluetooth_cal.acdb"
adb shell "su -c cp /sdcard/MTP_WCD9306_Bluetooth_cal.acdb /system/etc/acdbdata/MTP/msm8939-tapan-snd-card/MTP_WCD9306_Bluetooth_cal.acdb"
adb shell "su -c cp /sdcard/MTP_Bluetooth_cal_ZD550KL.acdb /system/etc/acdbdata/MTP/ZD550KL/MTP_Bluetooth_cal_ZD550KL.acdb"
adb shell "su -c cp /sdcard/MTP_Bluetooth_cal_ZE550KL.acdb /system/etc/acdbdata/MTP/ZE550KL/MTP_Bluetooth_cal_ZE550KL.acdb"
adb shell "su -c cp /sdcard/MTP_Bluetooth_cal_ZE600KL.acdb /system/etc/acdbdata/MTP/ZE600KL/MTP_Bluetooth_cal_ZE600KL.acdb"
adb shell "su -c cp /sdcard/QRD_Bluetooth_cal.acdb /system/etc/acdbdata/QRD/QRD_Bluetooth_cal.acdb"
adb shell "su -c cp /sdcard/QRD_SKUL_Bluetooth_cal.acdb /system/etc/acdbdata/QRD/msm8939-snd-card-skul/QRD_SKUL_Bluetooth_cal.acdb"
adb shell "su -c cp /sdcard/bt_did.conf /system/etc/bluetooth/bt_did.conf"
adb shell "su -c cp /sdcard/bt_stack.conf /system/etc/bluetooth/bt_stack.conf"
adb shell "su -c cp /sdcard/android.hardware.bluetooth.xml /system/etc/permissions/android.hardware.bluetooth.xml"
adb shell "su -c cp /sdcard/android.hardware.bluetooth_le.xml /system/etc/permissions/android.hardware.bluetooth_le.xml"
adb shell "su -c cp /sdcard/init.qcom.bt.sh /system/etc/init.qcom.bt.sh"
adb shell "su -c cp /sdcard/libbluetooth_jni.so /system/lib/libbluetooth_jni.so"
adb shell "su -c cp /sdcard/bluetooth.default.so /system/lib/hw/bluetooth.default.so"
adb shell "su -c cp /sdcard/libbt-vendor.so /system/vendor/lib/libbt-vendor.so"
adb shell "su -c cp /sdcard/libbtnv.so /system/vendor/lib64/libbtnv.so"
# Set Permission Of New Files (Should Be Finished, Not tested)
adb shell "su -c chmod 644 /system/app/Bluetooth/Bluetooth.apk"
adb shell "su -c chmod 644 /system/app/BluetoothExt/BluetoothExt.apk"
adb shell "su -c chmod 644 /system/app/BluetoothMidiService/BluetoothMidiService.apk"
adb shell "su -c chmod 644 /system/bin/btnvtool"
adb shell "su -c chmod 644 /system/bin/btsnoop"
adb shell "su -c chmod 644 /system/etc/acdbdata/MTP/MTP_Bluetooth_cal.acdb"
adb shell "su -c chmod 644 /system/etc/acdbdata/MTP/msm8939-tapan-snd-card/MTP_WCD9306_Bluetooth_cal.acdb"
adb shell "su -c chmod 644 /system/etc/acdbdata/MTP/ZD550KL/MTP_Bluetooth_cal_ZD550KL.acdb"
adb shell "su -c chmod 644 /system/etc/acdbdata/MTP/ZE550KL/MTP_Bluetooth_cal_ZE550KL.acdb"
adb shell "su -c chmod 644 /system/etc/acdbdata/MTP/ZE600KL/MTP_Bluetooth_cal_ZE600KL.acdb"
adb shell "su -c chmod 644 /system/etc/acdbdata/QRD/QRD_Bluetooth_cal.acdb"
adb shell "su -c chmod 644 /system/etc/acdbdata/QRD/msm8939-snd-card-skul/QRD_SKUL_Bluetooth_cal.acdb"
adb shell "su -c chmod 644 /system/etc/bluetooth/bt_did.conf"
adb shell "su -c chmod 644 /system/etc/bluetooth/bt_stack.conf"
adb shell "su -c chmod 644 /system/etc/permissions/android.hardware.bluetooth.xml"
adb shell "su -c chmod 644 /system/etc/permissions/android.hardware.bluetooth_le.xml"
adb shell "su -c chmod 644 /system/etc/init.qcom.bt.sh"
adb shell "su -c chmod 644 /system/lib/libbluetooth_jni.so"
adb shell "su -c chmod 644 /system/lib/hw/bluetooth.default.so"
adb shell "su -c chmod 644 /system/vendor/lib/libbt-vendor.so"
adb shell "su -c chmod 644 /system/vendor/lib64/libbtnv.so"

shanetrainST said:
So I started today putting together a batch ADB file to test the CM version of the BT for joying
I have completely run out of time to finish it and I wont be able to complete it till next week, there is quite a bit to go on it and i am not even sure it works, so if anyone want to continue with it, u can.
The ADB Files are not my work and i don't take credit for it, I only added the files and made the batch
This work is not complete and SHOULD NOT BE USED in its current state.
Click to expand...
Click to collapse
Nice work.
However, I would start with simply replacing the bluetooth.apk first.
And then the bluetooth.apk, the libbluetooth_jni.so and the bluetooth.default.so
Or did you already try that?
Note also that the "libbt-vendor.so" is seemingly a vendor library. Maybe you still need the original from Joying for the specific Intel vendor bluetooth stuff. On the other hand: the CM-13 is not hardware specific, so maybe it is more cross-compatible.

Going to try that soon thanks for tips, had a bit of time on my lunch break.
new batch file that replaces the three files u mentioned.
If anyone want to test it, file attached
I take zero responsibility if anything happens to your unit
To undo if it don't work just use root browser to delete the new files and rename the old files.
View attachment BluetoothUpdate2.zip
BluetoothHalfUpdate.bat
Echo off
adb kill-server
adb connect %1
adb root
adb connect %1
adb push Bluetooth.apk /sdcard/
adb push libbluetooth_jni.so /sdcard/
adb push bluetooth.default.so /sdcard/
adb shell mount -o rw,remount /system
adb shell mount -o rw,remount /system /system
adb shell mount -o rw,remount /
adb shell mount -o rw,remount / /
adb shell "su -c mount -o remount,rw /system"
adb shell "su -c cp /system/Bluetooth/Bluetooth.apk /system/Bluetooth/Bluetooth.apk.old"
adb shell "su -c cp /system/Bluetooth/oat/x86/Bluetooth.odex /system/Bluetooth/oat/x86/Bluetooth.odex.old"
adb shell "su -c cp /system/Bluetooth/lib/libbluetooth_jni.so /system/Bluetooth/lib/libbluetooth_jni.so.old"
adb shell "su -c cp /system/lib/hw/bluetooth.default.so /system/lib/hw/bluetooth.default.so.old"
adb shell "su -c cp /sdcard/Bluetooth.apk /system/app/Bluetooth/Bluetooth.apk"
adb shell "su -c cp /sdcard/libbluetooth_jni.so /system/lib/libbluetooth_jni.so"
adb shell "su -c cp /sdcard/bluetooth.default.so /system/lib/hw/bluetooth.default.so"
adb shell "su -c chmod 644 /system/app/Bluetooth/Bluetooth.apk"
adb shell "su -c chmod 644 /system/lib/libbluetooth_jni.so"
adb shell "su -c chmod 644 /system/lib/hw/bluetooth.default.so"
adb reboot

Thanks guys for taking the time to fix it.
Have you tested just a little bit? It works?

Not having much luck with mine, also missed a line of command in the shell that I will add later that mounts it
Every time I get ADB shell root, it connects for about 2seconds then kick me off. I am on the latest July rom
Sent from my iPhone using Tapatalk

So I updated
Bluetooth.apk
(Strange that it didn't produce a Bluetooth.odex on reboot)
Libbluetooth-Jni.so
Bluetooth.default.so
When unit boot's up it shows that Bluetooth sharing has crashed, not sure how to fix it
Must need more files replaced, anyone know a android Bluetooth expert? Would help heaps
So far the BT is broken and won't power on and the Joying app cannot use it but...
Anyone remember was Bluetooth tethering in the menu? Pic attached
{
"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"
}
Sent from my iPhone using Tapatalk

That's difficult to understand this with my knowledge at the moment.:crying:

shanetrainST said:
So I updated
Bluetooth.apk
(Strange that it didn't produce a Bluetooth.odex on reboot)
Libbluetooth-Jni.so
Bluetooth.default.so
Click to expand...
Click to collapse
That is because the odex can't be written to the read-only /system on startup. So it will be written to /data/app like any downloaded app.
Most probably you will find it at /data/app/com.android.bluetooth/oat/x86/base.odex
For the rest I don't have an answer.

I might just put back the original Bluetooth.apk
Just swap the Bluetooth.default.so first
Sent from my iPhone using Tapatalk

This is probably a silly suggestion and already been tried but not seen anything on the joying threads... has anyone tried a Bluetooth tethering manager for the tethering side?
I use this for connecting my phone to a tablet in car.
Bluetooth tethering manager
https://play.google.com/store/apps/details?id=com.tomlocksapps.bluetoothtetheringmanager
Sent from my SM-G920F using Tapatalk

Merlous said:
This is probably a silly suggestion and already been tried but not seen anything on the joying threads... has anyone tried a Bluetooth tethering manager for the tethering side?
I use this for connecting my phone to a tablet in car.
Bluetooth tethering manager
https://play.google.com/store/apps/details?id=com.tomlocksapps.bluetoothtetheringmanager
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
I've used that app and although it works fine I found it to be a bit slow.
I found the app the @doitright wrote a lot faster and it works fine and it's free
https://forum.xda-developers.com/an...elopment/bluetooth-settings-launcher-t3504526
If you want to read more head to my Q&A : https://forum.xda-developers.com/an...ts/intel-sofia-to-micro-tutorials-qa-t3616074

instead of swapping out apk's
try firmware from another device. joying uses realtek rtl8723a/rtk8723
check out
~5009_60/system/vendor/etc/bluetooth
~5009_60/system/vendor/etc/firmware/bt
/nvm_fs_partition/bluetooth
/system/bin/bt_vendor_test
???

edit said:
I've used that app and although it works fine I found it to be a bit slow.
I found the app the @doitright wrote a lot faster and it works fine and it's free
https://forum.xda-developers.com/an...elopment/bluetooth-settings-launcher-t3504526
If you want to read more head to my Q&A : https://forum.xda-developers.com/an...ts/intel-sofia-to-micro-tutorials-qa-t3616074
Click to expand...
Click to collapse
Thought you probably had but better safe than sorry! Thanks will check that one out.
Following your thread for when I get mine but just delayed it. Was ordering the single din 8" with 5.0.1 on but then they announced the newer cooler running one but it's on 6 and no 8" yet... was hoping this July 7th update might have solved more. Don't really need Bluetooth calling as I have side mounted exhausts and too loud really to talk and it's only a sheet of aluminium between the stereo and the outside so in the sun it will get rather hot...
Worse case will end up WiFi tethering.
Sent from my SM-G920F using Tapatalk

gtxaspec said:
instead of swapping out apk's
try firmware from another device. joying uses realtek rtl8723a/rtk8723
check out
~5009_60/system/vendor/etc/bluetooth
~5009_60/system/vendor/etc/firmware/bt
/nvm_fs_partition/bluetooth
/system/bin/bt_vendor_test
???
Click to expand...
Click to collapse
Thanks for the info
In the Joying 6.0 running OS I find there is this firmware file
vendor/etc/firmware/bt
-A11.Pbn
In the Joying 5.1 rom zip I found
vendor/etc/firmware/bt
-A00.pbn
-A10.pbn
-A11.pbn
Could anyone confirm what firmware file the 5.1 is running on
Could be as simple as swapping the A11.pbn for one of the other two.
A00.pbn seems to have the largest file size?? Not sure if it might be a fully featured firmware for the Realtek BT or it could be because they are using a few different variations of the RTL8723A
Will test tonight
Sent from my iPhone using Tapatalk

Getting very close to working out why Bluetooth disconnect and reconnect on apps that make their own Bluetooth connections without the Joying app.
This might be helpful for inet truma box aswell if it suffers the same issue.
The original problem was it would disconnect the apps Bluetooth after 3 and the the app would have to reconnect/disconnect/reconnect and then it would work fine.
I have started to rename some of the sys/app/ files as apk.old
I started renaming one at a time and got board and renamed a heap.
End result is my BT stays connected now and the app don't disconnect after 3mins of usages.
I think Joying turns the BT off if there is no device paired/connected via their Joying app, and one of the system apps takes care of it.
Tonight I will go back through and work out the culprit.
This has been a few month battle for me trying to figure out this issues, so happy it's not a driver or a Android core apk causing this
Sent from my iPhone using Tapatalk

shanetrainST said:
Getting very close to working out why Bluetooth disconnect and reconnect on apps that make their own Bluetooth connections without the Joying app.
This might be helpful for inet truma box aswell if it suffers the same issue.
The original problem was it would disconnect the apps Bluetooth after 3 and the the app would have to reconnect/disconnect/reconnect and then it would work fine.
I have started to rename some of the sys/app/ files as apk.old
I started renaming one at a time and got board and renamed a heap.
End result is my BT stays connected now and the app don't disconnect after 3mins of usages.
I think Joying turns the BT off if there is no device paired/connected via their Joying app, and one of the system apps takes care of it.
Tonight I will go back through and work out the culprit.
This has been a few month battle for me trying to figure out this issues, so happy it's not a driver or a Android core apk causing this
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Interesting and well done hopefully, I would have been the same as you with the impatience lol.
Sent from my SM-G920F using Tapatalk