NEITHER MYSELF NOR XDA ARE RESPONSIBLE FOR YOUR PHONE. FLASH AT YOUR OWN RISK
1. Download Root Explorer by Jrummy in the Play store.
2. Download the tether zip attached to this post.
3. Go into Root Explorer and find System folder, find priv-app, inside priv-app long press VZWEntitlementServices.apk and VZWEntitlementServices.odex rename to VZWEntitlementServices.apk.bak and VZWEntitlementServices.odex.bak and back out to first folder.
4. Go to sdcard folder, download and find tether.zip that you downloaded from step 2. Extract the build.prop, copy it and back out to the home folder. enter the system folder. Rename the build.prop that is there to build.prop.bak, then paste the one you extracted from the zip.
5. Long press on the file and hit permissions in the menu. change permissions Owner: Read/Write, Group:Read, Others: Read (should show rw-r--r--)
6. Exit out of root explorer
7. Reboot
8. Check the tether it should work.
9. PROFIT! Thank baby jesus and buy me a beer lol
Topsnake said:
I TAKE NO RESPONSIBILITY FOR YOUR PHONE OR ANY DAMAGE INCURRED FROM APPLYING THIS.
Prerequisites:
Rooted Maxx/Ultra on Kit Kat 19.6.3
You will not be able to do this on stock phones. If you are on Kit Kat 19.6.3 and are stock, there is currently no way to root it.
1. Download Root Explorer by Jrummy in the Play store.
2. Download the tether zip attached to this post.
3. Go into Root Explorer and find System folder, find priv-app, inside priv-app long press VZWEntitlementServices.apk and VZWEntitlementServices.odex rename to VZWEntitlementServices.apk.bak and VZWEntitlementServices.odex.bak and back out to first folder.
4. Go to sdcard folder, download and find tether.zip that you downloaded from step 2. Extract the build.prop, copy it and back out to the home folder. enter the system folder. Delete the build.prop that is there, then paste the one you extracted from the zip.
5. Long press on the file and hit permissions in the menu. change permissions Owner: Read/Write, Group:Read, Others: Read (should show rw-r--r--)
6. Exit out of root explorer
7. Reboot
8. Check the tether it should work.
9. PROFIT! Thank baby jesus and buy me a beer lol
10. Donations are appreciated to TopSnake
Click to expand...
Click to collapse
Any reason why we shouldn't use the Native Tether for Kit Kat 19.5.3 ?? its working fine here on 19.6.3
Jimmy8881 said:
Any reason why we shouldn't use the Native Tether for Kit Kat 19.5.3 ?? its working fine here on 19.6.3
Click to expand...
Click to collapse
Not really. This is just for those that have yet to apply the 19.5.3 Tether. Its also a slightly more simple method.
This is beautiful! Thank you Topsnake so very much!!!
SupremeOverlord said:
This is beautiful! Thank you Topsnake so very much!!!
Click to expand...
Click to collapse
No problem!
Droid Maxx "Developer Edition"
I did this and now my phone turns on and goes to a black screen. Any ideas? I see the unlocked bootloader then it goes black
smooth781 said:
I did this and now my phone turns on and goes to a black screen. Any ideas? I see the unlocked bootloader then it goes black
Click to expand...
Click to collapse
Likely you borked something with the build prop. Did you make a back up before you tried this?
Sent From Droid Ultra
If I helped you, consider hitting thanks.
no of course I was too lazy to do this.I have never had any problems with these things before. I know the phone is on I have it hook to my computer but I have no picture
---------- Post added at 09:34 PM ---------- Previous post was at 09:25 PM ----------
smooth781 said:
no of course I was too lazy to do this.I have never had any problems with these things before. I know the phone is on I have it hook to my computer but I have no picture
Click to expand...
Click to collapse
I did get twrp reinstalled but it does not seem to do much. I can get into it
smooth781 said:
no of course I was too lazy to do this.I have never had any problems with these things before. I know the phone is on I have it hook to my computer but I have no picture
---------- Post added at 09:34 PM ---------- Previous post was at 09:25 PM ----------
I did get twrp reinstalled but it does not seem to do much. I can get into it
Click to expand...
Click to collapse
You need to fxz with save data. You know how to do that I'm sure?
Sent From Droid Ultra
If I helped you, consider hitting thanks.
Caseyk621 said:
You need to fxz with save data. You know how to do that I'm sure?
Sent From Droid Ultra
If I helped you, consider hitting thanks.
Click to expand...
Click to collapse
No I know nothing about it. can you point me in the direction please
smooth781 said:
No I know nothing about it. can you point me in the direction please
Click to expand...
Click to collapse
You know how to use adb and fastboot right. You likely used fastboot to flash TWRP.
Sent From Droid Ultra
If I helped you, consider hitting thanks.
smooth781 said:
No I know nothing about it. can you point me in the direction please
Click to expand...
Click to collapse
I think im doing the right thing to get this working. I am downloading the latest firmware from the fxz people. 800 meg. I am just not sure 100% what to do with it after I get it
Download fxz from here. Extract. Open command prompt in the folder that you extracted to, the one that contains system.img. Then type the command:
fastboot flash system system.img
That should get you back up and running. Then for WiFi tether use this xposed module. (Easier to apply easier to revert for future OTA.)
http://repo.xposed.info/module/com.dym.motoxtether
Sent From Droid Ultra
If I helped you, consider hitting thanks.
---------- Post added at 10:00 PM ---------- Previous post was at 09:59 PM ----------
smooth781 said:
I think im doing the right thing to get this working. I am downloading the latest firmware from the fxz people. 800 meg. I am just not sure 100% what to do with it after I get it
Click to expand...
Click to collapse
Yeah that's the idea!
Sent From Droid Ultra
If I helped you, consider hitting thanks.
I thought everything was going good then I got an error
bootloader sparse image is malformatted
then
remote failure
---------- Post added at 10:12 PM ---------- Previous post was at 10:10 PM ----------
I also saw at the beginning bootloader variable not supported
I aslo just tried the mfastboot command and so far it is going forward. We will see
smooth781 said:
I thought everything was going good then I got an error
bootloader sparse image is malformatted
then
remote failure
---------- Post added at 10:12 PM ---------- Previous post was at 10:10 PM ----------
I also saw at the beginning bootloader variable not supported
I aslo just tried the mfastboot command and so far it is going forward. We will see
Click to expand...
Click to collapse
Crap. Try using mfastboot. Get from here
http://dottech.org/146758/how-to-root-moto-x-on-android-4-4-kitkat-and-flash-twrp-recovery-guide/
Sent From Droid Ultra
If I helped you, consider hitting thanks.
and my phone just booted up. Thanks for pointing me in the right direction. I could not have done it with out help.
smooth781 said:
and my phone just booted up. Thanks for pointing me in the right direction. I could not have done it with out help.
Click to expand...
Click to collapse
What'd you do to get it working?
Sent From Droid Ultra
If I helped you, consider hitting thanks.
Caseyk621 said:
What'd you do to get it working?
Sent From Droid Ultra
If I helped you, consider hitting thanks.
Click to expand...
Click to collapse
When I used the mfastboot instead of fastboot it took right off. I am updating the apps right now on my phone then I will try the wifi you linked above.
smooth781 said:
When I used the mfastboot instead of fastboot it took right off. I am updating the apps right now on my phone then I will try the wifi you linked above.
Click to expand...
Click to collapse
Cool. Glad you got it working. Yeah I'm using the xposed for WiFi tether. Working just fine.
Sent From Droid Ultra
If I helped you, consider hitting thanks.
For those that are now rooted on 19.6.3 remember this exploit
Droid Maxx "Developer Edition"
Related
For ICS 4.0.4 here is two mods battery percentage(circle and rectangular);instructions:
copy systemUI in system/app with permision RW-R-R and then reboot.
Your phone must be rooted.
PS:systemUI is for circle and systemUI(R) is for rectangular;if use rectangular delete(R) the files must be systemUI.
UPDATE:new mod named android is systemui(A)
Thank You !
What the SystemUI(R) ?
i can't change permission for this file, it say file system do not allow permission changes
---------- Post added at 10:27 PM ---------- Previous post was at 10:14 PM ----------
nmv i got it
How can I root my device to use it ??
That rectangular battery is awesome. Looks like it was part of the update!
wssherbiny said:
How can I root my device to use it ??
Click to expand...
Click to collapse
If you can root your phone try this :http://forum.xda-developers.com/showthread.php?t=1723610&page=26
Thanks. The (R) one looks grea t:good:
I prefer battery stock icon with percentage above ? anyone helps ?
Many tkssssssss
Sent from my LT26i using Tapatalk 2
damn was looking just for this, many thanks man!
how can i change permission for this file ???
fantasyduc said:
how can i change permission for this file ???
Click to expand...
Click to collapse
First your phone must be rooted and then with root explorer or else and choose R/W.
umarian said:
First your phone must be rooted and then with root explorer or else and choose R/W.
Click to expand...
Click to collapse
don it with the rom toolbox, -> long press the file, go on "permissions" and set it up... very easy
umarian said:
First your phone must be rooted and then with root explorer or else and choose R/W.
Click to expand...
Click to collapse
i do it and it say permissions cannot be change because the file system is read only
fantasyduc said:
i do it and it say permissions cannot be change because the file system is read only
Click to expand...
Click to collapse
I sent a pm to explain.
Oddly enough when running this, from time to time it will revert back to the stock battery, then back to the modded one.
When I tried skyfir123 versions in his thread it doesn't do that.
Can you fix that? Cause I much prefer the R version you have to anything else.
bustervic said:
Oddly enough when running this, from time to time it will revert back to the stock battery, then back to the modded one.
When I tried skyfir123 versions in his thread it doesn't do that.
Can you fix that? Cause I much prefer the R version you have to anything else.
Click to expand...
Click to collapse
I thing(maybe i am wrong) this happen because method of root;for me it work good.How instal for me:
I instal 4.0.4 with flastool(TWICE)
For root follow next step:
0.Copy in your phone superuser-3.0.7-efgi-signed.
1.Download recovery-nozomi.img from here: http://forum.xda-developers.com/show....php?t=1596285
2.Flash the recovery-nozomi.img with next comand: fastboot flash boot recovery-nozomi.img
3.Enter in recovery(push volume down) and instal superuser-3.0.7-efgi-signed.
4.Turn off phone.
5.flash the kernel.sin with next comand:fastboot flash boot kernel.sin
6.Reboot and your phone is rooted.
PS:sorry for my bad english and this method it work for bootloader unlocked.
PS2:in recovery mode if superuser aborted enter in advanced menu and check fix permission.
Thanks.
My first mod on ics
Sent from my Transformer TF101 using XDA Premium App
Hmm, well I did follow the step by step rooting myself (before the pre rooted img was up)
http://forum.xda-developers.com/showpost.php?p=27692994&postcount=1
Everything else was fine. I suppose I could try the pre-rooted version w/o a wipe and see if it improves anything.
Does the same for me too
I created this file in 2012 for the EVO3D I had as a alternative to init.d scripts.
This is intended to create real performance. Not performance to create crazy benchmark numbers like done on the 3D forums before. For shiggles....I am getting 22k on AnTuTu Bench. This is a rough post as I just spent 4 hrs creating a biology study guide and I am quite tired.
*DISCLAIMER*
I AM NOT LIABLE FOR YOU JACKING THINGS UP
I have a ATT Moto X(XT1058). Rooted, unlocked, on 4.4.2....Still stock recovery. Though this should work on any Moto X.
Keep in mind this should be considered a beta as I tweak it for the Moto X and add things like I had done before.
Version 1.0
Initial Release for Moto X
Cleaned useless code from orginal that doesn't apply to our phone. Cpu 2 & 3 settings IE.
[Stock uses Interactive as the governor.
Changed settings used for the ramp up of the cpu under load
Changed settings to improve VM performance and battery life(supposedly)
Changed scheduler to noop and read ahead to 3072
Changed network settings to help optimize them
Optimized the EXT4 mounts.
Zip align files on boot - Checks them first
Installing this is quite simple...Just need to click a file in windows. That simple basicly.
Everything you need is there in one folder
No need to reboot into recovery.
Instructions
Download the zip file.
Extract the files to a folder.
Run the file Push.bat
Hit any key to keep going.
Let it reboot.
RESTORING
If you decide this is not for you...hey I got your 6.
Run the File named Restore.bat and it will replace the old postboot for you and reboot.
To Do:
Tweak Current settings and add new
Create a flashable zip
Add user customization
Sweet will test it out tommorw! Could we get some further details at exactly what if changes and tweaks? Or is that in the download
Sent from my Nexus 7 using Tapatalk
Yeah I will today. Sorry wasn't exactly awake.
The batch file is for those who still have stock recovery but rooted and unlocked or write protection disabled.
If you get a read only error pushing the files to the phone then your kernel isn't insecure. If you get the error just close the command prompt screen.
If you have a stock kernel then you need a app like adbd insecure. Buy or aquire it, lol, and check the option in the settings. It will pop up a window saying patching. Then run the push.bat file.
Custom kernels shouldn't be a problem lol. If so then who made it is stupid.
When I make the flashable zip then you won't need a app and such.
Sent from my XT1058 using xda app-developers app
southern87 said:
Yeah I will today. Sorry wasn't exactly awake.
The batch file is for those who still have stock recovery but rooted and unlocked or write protection disabled.
If you get a read only error pushing the files to the phone then your kernel isn't insecure. If you get the error just close the command prompt screen.
If you have a stock kernel then you need a app like adbd insecure. Buy or aquire it, lol, and check the option in the settings. It will pop up a window saying patching. Then run the push.bat file.
Custom kernels shouldn't be a problem lol. If so then who made it is stupid.
When I make the flashable zip then you won't need a app and such.
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
Hi Southern,
Thanks for your time and effort. I have ran your tool and received an error. I have a Dev Edition Moto X with custom recovery and Eclipse (Blur based 4.4.2) Rom. Please take a look at the attached pic.
thanks
hryusha said:
Hi Southern,
Thanks for your time and effort. I have ran your tool and received an error. I have a Dev Edition Moto X with custom recovery and Eclipse (Blur based 4.4.2) Rom. Please take a look at the attached pic.
thanks
Click to expand...
Click to collapse
Install this. Your kernel is not unsecure. This will allow you to push and pull system files via adb.
http://forum.xda-developers.com/showthread.php?t=1687590
About to add the flashable zip if you want to flash it instead.
southern87 said:
Install this. Your kernel is not unsecure. This will allow you to push and pull system files via adb.
http://forum.xda-developers.com/showthread.php?t=1687590
About to add the flashable zip if you want to flash it instead.
Click to expand...
Click to collapse
Thanks! I will just wait for the flashable file, but will still download the above file just in case.
---------- Post added at 12:23 PM ---------- Previous post was at 12:16 PM ----------
Tried the flashable version and it failed. I am using TWRP 2.7 if that helps at all.
I will now try the file you suggested 2 posts above and the usual windows method.
hryusha said:
Thanks! I will just wait for the flashable file, but will still download the above file just in case.
---------- Post added at 12:23 PM ---------- Previous post was at 12:16 PM ----------
Tried the flashable version and it failed. I am using TWRP 2.7 if that helps at all.
I will now try the file you suggested 2 posts above and the usual windows method.
Click to expand...
Click to collapse
I took it down. I just looked at it and realized I got ahead of myself on the updater-script. I need to flash a recovery anyways, just hadn't had time.
but yeah if you install that app, it will let you run the batch.
southern87 said:
I took it down. I just looked at it and realized I got ahead of myself on the updater-script. I need to flash a recovery anyways, just hadn't had time.
but yeah if you install that app, it will let you run the batch.
Click to expand...
Click to collapse
Ok NP, I will try the other method and will get back to you with my findings.
---------- Post added at 12:38 PM ---------- Previous post was at 12:32 PM ----------
Everything went smooth (with the windows cmd process), phone is now restarting. I will monitor how my battery life is today and will report with my findings.
hryusha said:
Ok NP, I will try the other method and will get back to you with my findings.
---------- Post added at 12:38 PM ---------- Previous post was at 12:32 PM ----------
Everything went smooth (with the windows cmd process), phone is now restarting. I will monitor how my battery life is today and will report with my findings.
Click to expand...
Click to collapse
good deal. Maybe 2.7 doesn't play well with the X. I don't think its officially suppported. Everything I try to do gives me the same error while flashing.
southern87 said:
good deal. Maybe 2.7 doesn't play well with the X. I don't think its officially suppported. Everything I try to do gives me the same error while flashing.
Click to expand...
Click to collapse
Just FYI, 2.7 works well with all the other flashing I had to do.... Eclipse rom as well as some random additions i had to flash via the recovery, all went without an issue. I did see that 2.6.3 is the only one in the Moto X forum though.
hryusha said:
Just FYI, 2.7 works well with all the other flashing I had to do.... Eclipse rom as well as some random additions i had to flash via the recovery, all went without an issue. I did see that 2.6.3 is the only one in the Moto X forum though.
Click to expand...
Click to collapse
I figured.
No versions of TWRP are "officially" supported.
2.7 works without issue for me -- the dev (I believe its dhacker) just didn't bother making a thread for it
ahh I see. I always had HTC devices so wasn''t really a issue.
From what I read KitKat changed some stuff to do with the updater-scripts. I was starting to get pissed with this lol.
Going to add it to the OP in a second.
Hi Southern...
What is Moto Z in your signature? Which device is it?
kenosis said:
Hi Southern...
What is Moto Z in your signature? Which device is it?
Click to expand...
Click to collapse
It's supposed to be a x. Sorry hahaha
Sent from my XT1058 using xda app-developers app
Initial findings.
Ds battery monitor disabled, but I think it still is still running.
Adm check box 1 unchecked, Google now disabled. Used app ops to disable some gps permissions.
Beats music kills the data on high quality haha. Like 600 megs
Sent from my XT1058 using xda app-developers app
how can I know whether installation is successful or not successful?
kenosis said:
how can I know whether installation is successful or not successful?
Click to expand...
Click to collapse
If you go to system/etc/ and find the post boot it will be like 6 or 7kb in size as the original is 20.
That or use adb to pull it from a phone after you install it.
Sent from my XT1058 using xda app-developers app
southern87 said:
If you go to system/etc/ and find the post boot it will be like 6 or 7kb in size as the original is 20.
That or use adb to pull it from a phone after you install it.
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
failed to move zipalign and int.qcom.post.boot.sh to folders.
I didn't change or screen said failed? Read only? Or did you use the flashable zip?
If it's read only error it'd saying. Your kernel isn't unsecure. There is a link to a app that can fix it. It's temporary unless you set it to start at boot.
It allows you to push and pull system files via adb.
Flashing isn't affected by this
Sent from my XT1058 using xda app-developers app
Any suggestions on what I can do to fix this?
londonandlawson said:
Any suggestions on what I can do to fix this?
Click to expand...
Click to collapse
If you can boot into TWRP, you can ADB push a ROM or recovery file from your PC.
I have the stock software on my pc, a .tgz file i downloaded. Would you care to link me to instructions on what to do?
londonandlawson said:
I have the stock software on my pc, a .tgz file i downloaded. Would you care to link me to instructions on what to do?
Click to expand...
Click to collapse
You have some homework. Start by reading this and asking questions in that thread. You will eventually recover your device, but not going to happen tomorrow. This is a good learning exercise.
Go here >http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
I have the C:\\adb folder setup, I just wanted to make sure I had the right commands to use
londonandlawson said:
I have the C:\\adb folder setup, I just wanted to make sure I had the right commands to use
Click to expand...
Click to collapse
So you will want to download a custom ROM from Android Development section. Put it in the same folder as ADB and fastboot. Then use the ADB command to push that .zip file to your N6. Syntax of the command is critical. I'd suggest googling ADB push and read several different threads. Here's one to start with >http://forum.xda-developers.com/showthread.php?t=1601802&page=4
---------- Post added at 08:09 PM ---------- Previous post was at 07:48 PM ----------
londonandlawson said:
Any suggestions on what I can do to fix this?
Click to expand...
Click to collapse
One other point: are you sure you have drivers loaded on your PC, and your PC can see your N9?
---------- Post added at 08:14 PM ---------- Previous post was at 08:09 PM ----------
londonandlawson said:
Any suggestions on what I can do to fix this?
Click to expand...
Click to collapse
Since you are trying to connect your N9 to your PC while booted to TWRP, you may need to uninstall and reinstall drivers, IF your PC can't see your N9.
got it going
londonandlawson said:
got it going
Click to expand...
Click to collapse
Great news! Care to share for other users?
I just downloaded the factory image and unzipped it in the C://adb folder then held shift-right click in that folder to open a new command window. From there I did the commands to install the recovery, system image and kernel
I'm on B309 right now. I'm not part of any Huawei user tests or anything, and my phone is basically stock--no unlocked bootloader or root, other than having installed B309. Can I use the downloaded (from somebody's google drive, not the OTA server) b321 zip file to update? If so, how would I do that?
you have to update to B320 first. Get it from here:
http://forum.xda-developers.com/showpost.php?p=61682526&postcount=3
Then you can download the B321 update.
I installed it the other day, but it didn't take for some reason. Totally stock B320 here.
Once I download it, how do I get the update to actually run? Thank you.
bobschmidt said:
Once I download it, how do I get the update to actually run? Thank you.
Click to expand...
Click to collapse
Settings--Updater--Local update (your /dead folder bearing the file)
Sent from my MT2L03 using XDA Free mobile app
Does installing B320 reset your phone to factory defaults?
monkey39 said:
Does installing B320 reset your phone to factory defaults?
Click to expand...
Click to collapse
Yep
MT2-User said:
Settings--Updater--Local update (your /dead folder bearing the file)
Sent from my MT2L03 using XDA Free mobile app
Click to expand...
Click to collapse
I did that, the update ran, but when it restarted, I was still on B309. Sounds like a similar problem to NRFITCHETT's.
bobschmidt said:
I did that, the update ran, but when it restarted, I was still on B309. Sounds like a similar problem to NRFITCHETT's.
Click to expand...
Click to collapse
Unzip 320 to external sd card in a folder named dload. Boot recovery and it will update.
So that worked and I'm on 320. How do I get to 321? I downloaded the zip, but it had much more stuff than 320. I tried just putting the update.app file in the dload folder, but the update runs, but doesn't actually update me to 321.
bobschmidt said:
So that worked and I'm on 320. How do I get to 321? I downloaded the zip, but it had much more stuff than 320. I tried just putting the update.app file in the dload folder, but the update runs, but doesn't actually update me to 321.
Click to expand...
Click to collapse
https://community.gethuawei.com/sup...15/06/30/mate2-android-l-update-now-available
Like that.
---------- Post added at 09:48 PM ---------- Previous post was at 09:47 PM ----------
Moody66 said:
https://community.gethuawei.com/sup...15/06/30/mate2-android-l-update-now-available
Like that.
Click to expand...
Click to collapse
Scratch that. For that one put it I'm your huawei update folder and do it locally. Folder is named HuaweiOtaU or something like that. Look around with a file browser. You will see it.
#11
I'm having same issue as Bob. I looked for huawei update folder and signed up for imei ota through huawei support. I'm lost have 321 unzipped and ready just no clue where it goes?
Yeah, I unzipped into dload, pressed up-down, power, and it just says "Huawei software update 0%, do not remove USB" and stays there. If I move the update.app file into the dload directory, the update will run, but once it restarts I'll be at 320 still.
Didn't catch your edit, will try that.
Moody66 said:
https://community.gethuawei.com/sup...15/06/30/mate2-android-l-update-now-available
Like that.
---------- Post added at 09:48 PM ---------- Previous post was at 09:47 PM ----------
Scratch that. For that one put it I'm your huawei update folder and do it locally. Folder is named HuaweiOtaU or something like that. Look around with a file browser. You will see it.
Click to expand...
Click to collapse
I don't see that folder on either the SD or internal storage. I also am not sure what "do it locally" means.
You update locally from your phone settings bob. Look under settings, then go to updater under system settings, then hit menu at bottom and choose local update. I have been looking how to do this all day and I also couldn't find Huawei ota updater folder anywhere in internal or sd through computer or phone.
Hello! I'm pretty new here and I was hoping if someone could help me
My O+ Fab Lite 2.0 is stuck in my boot animation after I installed a new font. I installed a font before that and everything went smoothly. But instead of replacing the default android font (which I think is Roboto if I'm not mistaken), I replaced the Roboto Bold font. I rebooted my phone just like the app asked me to do. Next thing I know my phone is bricked! I used FontFix from JRummyApps to replace the Roboto Bold font. I really hope I can fix this with your help!! Thank you!
!
PatrickJRS said:
Hello! I'm pretty new here and I was hoping if someone could help me
My O+ Fab Lite 2.0 is stuck in my boot animation after I installed a new font. I installed a font before that and everything went smoothly. But instead of replacing the default android font (which I think is Roboto if I'm not mistaken), I replaced the Roboto Bold font. I rebooted my phone just like the app asked me to do. Next thing I know my phone is bricked! I used FontFix from JRummyApps to replace the Roboto Bold font. I really hope I can fix this with your help!! Thank you!
!
Click to expand...
Click to collapse
Been there, I can help you. Do you have a backup of the font? If so we can use adb or terminal to fix. If not, I can give you a copy of mine.
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
Been there, I can help you.. Do you have a backup of the font? If so we can use adb or terminal to fix. If not, I can give you a copy of mine.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Thank you so much! I don't think I have a backup though.
PatrickJRS said:
Thank you so much! I don't think I have a backup though.
Click to expand...
Click to collapse
Ok, I'll upload a copy of mine. (Should be somewhat universal) Do you have adb or a terminal app that you can type commands into?
Sent from my SM-T210 using Tapatalk
RealWelder said:
Ok, I'll upload a copy of mine. (Should be somewhat universal) Do you have adb or a terminal app that you can type commands into?
Sent from my SM-T210 using Tapatalk
Click to expand...
Click to collapse
do you mean like on a pc? if yes, I do have adb.
If you have TWRP or other custom recovery, you can just flash this zip with it.
https://drive.google.com/file/d/0B3XczzpnAnvwbjhxVG1MVWVtQVE/view?usp=drivesdk
If not, you will need to extract the font and we will install it manually.
Sent from my SM-T210 using Tapatalk
RealWelder said:
If you have TWRP or other custom recovery, you can just flash this zip with it.
https://drive.google.com/file/d/0B3XczzpnAnvwbjhxVG1MVWVtQVE/view?usp=drivesdk
If not, you will need to extract the font and we will install it manually.
Sent from my SM-T210 using Tapatalk
Click to expand...
Click to collapse
Sadly, I've been searching for custom recoveries for my device a while back and it seems like there isn't one available. So no :crying: , I don't have a custom recovery.
To install manually:
1.Extract the font
2.Use adb to push the font to /sdcard/ (adb push * /sdcard/) for the * just drag n drop the font into the cmd window
3. Now we will start our shell commands
adb shell
su
mount -o remount,rw /system /system
cd /system/fonts
cp /sdcard/Roboto-Bold.ttf Roboto-Bold.ttf
chmod 0644 Roboto-Bold.ttf
reboot
Sent from my SM-T210 using Tapatalk
RealWelder said:
To install manually:
1.Extract the font
2.Use adb to push the font to /sdcard/ (adb push * /sdcard/) for the * just drag n drop the font into the cmd window
3. Now we will start our shell commands
adb shell
su
mount -o remount,rw /system /system
cd /system/fonts
cp /sdcard/Roboto-Bold.ttf Roboto-Bold.ttf
chmod 0644 Roboto-Bold.ttf
reboot
Sent from my SM-T210 using Tapatalk
Click to expand...
Click to collapse
sorry for the late reply but when I tried to do the first step this is what it said " adb: error: connect failed: no devices/emulators found "
PatrickJRS said:
sorry for the late reply but when I tried to do the first step this is what it said " adb: error: connect failed: no devices/emulators found "
Click to expand...
Click to collapse
You will need to install adb drivers for your device. If you've ever used adb with this device before, you should already have them installed, though.
Also, the phone will have to be doing it's loop for adb to read it. You may also want to try another usb cable.
Sent from my KYOCERA-C6745 using Tapatalk
PatrickJRS said:
sorry for the late reply but when I tried to do the first step this is what it said " adb: error: connect failed: no devices/emulators found "
Click to expand...
Click to collapse
How's it going?
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
How's it going?
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
whoops, sorry there. well uhm.. I researched on how to install drivers and I can't seem to get it working. Maybe I could turn to you for help again?
I'll see if I can find them for you.
Sent from my KYOCERA-C6745 using Tapatalk
---------- Post added at 07:14 PM ---------- Previous post was at 07:09 PM ----------
Try this. http://www.mediafire.com/file/d68cbf3latzv8cb/
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
I'll see if I can find them for you.
Sent from my KYOCERA-C6745 using Tapatalk
---------- Post added at 07:14 PM ---------- Previous post was at 07:09 PM ----------
Try this. http://www.mediafire.com/file/d68cbf3latzv8cb/
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
hmmm why does it say " The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for 32-bit systems. "
PatrickJRS said:
hmmm why does it say " The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for 32-bit systems. "
Click to expand...
Click to collapse
My bad, looking in the zip it is only for 64 bit. I'll keep looking. In the meantime you might get lucky with the Universal Android USB drivers. You should try that and see if you can get adb going.
To test it just type adb devices and if it sees your phone it will show it under List of attached devices.
Sent from my KYOCERA-C6745 using Tapatalk
---------- Post added at 07:41 PM ---------- Previous post was at 07:31 PM ----------
PatrickJRS said:
hmmm why does it say " The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for 32-bit systems. "
Click to expand...
Click to collapse
Is this an MTK device? If so you can download the mtk drivers.
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
My bad, looking in the zip it is only for 64 bit. I'll keep looking. In the meantime you might get lucky with the Universal Android USB drivers. You should try that and see if you can get adb going.
To test it just type adb devices and if it sees your phone it will show it under List of attached devices.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
sorry but what // which one do you mean by Universal Android USB drivers? I just typed in adb devices but I don't see my device under it.
RealWelder said:
My bad, looking in the zip it is only for 64 bit. I'll keep looking. In the meantime you might get lucky with the Universal Android USB drivers. You should try that and see if you can get adb going.
To test it just type adb devices and if it sees your phone it will show it under List of attached devices.
Sent from my KYOCERA-C6745 using Tapatalk
---------- Post added at 07:41 PM ---------- Previous post was at 07:31 PM ----------
Is this an MTK device? If so you can download the mtk drivers.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Not really sure but by what I remember it is an MTK device
PatrickJRS said:
Not really sure but by what I remeber it is an MTK device
Click to expand...
Click to collapse
https://androidmtk.com/download-mtk-usb-all-drivers
Install these, unplug the device, reboot computer, and then plug it back in an try adb devices again.
As soon as we can get adb to recognize it we can fix it.
Sent from my KYOCERA-C6745 using Tapatalk
---------- Post added at 07:54 PM ---------- Previous post was at 07:50 PM ----------
PatrickJRS said:
Not really sure but by what I remember it is an MTK device
Click to expand...
Click to collapse
I just had another thought too. If you can get it to boot into recovery sometimes adb will see it there. I had a Huawei that I did this same thing to with a font, for it I could only get adb to see it in recovery.
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
https://androidmtk.com/download-mtk-usb-all-drivers
Install these, unplug the device, reboot computer, and then plug it back in an try adb devices again.
As soon as we can get adb to recognize it we can fix it.
Sent from my KYOCERA-C6745 using Tapatalk
---------- Post added at 07:54 PM ---------- Previous post was at 07:50 PM ----------
I just had another thought too. If you can get it to boot into recovery sometimes adb will see it there. I had a Huawei that I did this same thing to with a font, for it I could only get adb to see it in recovery.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
man tough luck :crying:
" Install these, unplug the device, reboot computer, and then plug it back in an try adb devices again. " I did exactly what you said but I still can't see my device. I'm not losing hope though! I'll try getting it in recovery mode but I'll do it tomorrow (or later lol) cause it's like 3:00 in the morning here in my country so yeah I need to get some shut eye. talk to ya later I guess! btw thanks for helping me out I obviously don't know much about these lol :laugh::good:
PatrickJRS said:
man tough luck :crying:
" Install these, unplug the device, reboot computer, and then plug it back in an try adb devices again. " I did exactly what you said but I still can't see my device. I'm not losing hope though! I'll try getting it in recovery mode but I'll do it tomorrow (or later lol) cause it's like 3:00 in the morning here in my country so yeah I need to get some shut eye. talk to ya later I guess! btw thanks for helping me out I obviously don't know much about these lol [emoji23]:good:
Click to expand...
Click to collapse
No problem.
Sent from my KYOCERA-C6745 using Tapatalk