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
Related
Hi so I just got an HTC one x+ and unlocked and it and rooted it. I flashbooted a boot.img from a custom and realized I forgot to put the custom ROM itself on the phone. My phone now can't use WiFi or show up on the computer unless in fastboot. I really need help please let me know what to do. Thanks!!!
Sent from my SGH-T999 using xda app-developers app
brianisawesome1 said:
Hi so I just got an HTC one x+ and unlocked and it and rooted it. I flashbooted a boot.img from a custom and realized I forgot to put the custom ROM itself on the phone. My phone now can't use WiFi or show up on the computer unless in fastboot. I really need help please let me know what to do. Thanks!!!
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Within a custom recovery, ex. TWRP. Go into advance and select adb sideload. Use adb to sideload the Rom using the command adb sideload Rom.zip to your phone
Sent from my HTC One X+ using Tapatalk
nheolon thous
I have a similar problem here.
I wanted to try this"adb sideload" but I can get ti to work because when I use "adb devices". I get nothing listed.
can I get an extra help please?
Thank you
XAlexander_AlexanderX said:
Within a custom recovery, ex. TWRP. Go into advance and select adb sideload. Use adb to sideload the Rom using the command adb sideload Rom.zip to your phone
Sent from my HTC One X+ using Tapatalk
Click to expand...
Click to collapse
I got cannot read ROM.zip anything more specific I didn't do
Sent from my SGH-T999 using xda app-developers app
brianisawesome1 said:
I got cannot read ROM.zip anything more specific I didn't do
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Use the name of the Rom. For example. If the Rom name is cm10. You type adb sideload cm10.zip
Sent from my HTC One X+ using Tapatalk
XAlexander_AlexanderX said:
Use the name of the Rom. For example. If the Rom name is cm10. You type adb sideload cm10.zip
Sent from my HTC One X+ using Tapatalk
Click to expand...
Click to collapse
Ya I did that and still sane problem
Sent from my SGH-T999 using xda app-developers app
brianisawesome1 said:
Ya I did that and still sane problem
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Is the Rom in the same folder as adb (if your using windows )?
Sent from my HTC One X+ using Tapatalk
XAlexander_AlexanderX said:
Is the Rom in the same folder as adb (if your using windows )?
Sent from my HTC One X+ using Tapatalk
Click to expand...
Click to collapse
Ill tell u step by step what I do:
1. Recovery to adb sideload on phone
2. Move ROM to c:\android where fastboot and adb are located
3. Run cmd
4. cd c:\android
5. Adb sideload "ROM name"
6. I get the error
Sent from my SGH-T999 using xda app-developers app
brianisawesome1 said:
Ill tell u step by step what I do:
1. Recovery to adb sideload on phone
2. Move ROM to c:\android where fastboot and adb are located
3. Run cmd
4. cd c:\android
5. Adb sideload "ROM name"
6. I get the error
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Adb is located in platform tools. Put Rom there and CD cmd there and run the command.
Sent from my HTC One X+ using Tapatalk
brianisawesome1 said:
Ill tell u step by step what I do:
1. Recovery to adb sideload on phone
2. Move ROM to c:\android where fastboot and adb are located
3. Run cmd
4. cd c:\android
5. Adb sideload "ROM name"
6. I get the error
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
open platform-tools(or the folder where adb is found) shift + right click on any empty space, you will find "open command prompt here" press on it, then type ADB devices, if it is read, simply type " adb sideload " then drag and drop the rom zip into the command prompt. it will automatically write its location and prevent the spelling mistakes.
IF: ADB devices can't read your device try the following:
1-Try another usb port, if you tried 2.0 then try 3.0 and vice versa.
2- If you are on windows vista or above, open start menu and search for cmd, right click on it and run as administrator, however you will have to cd to the platform tools location, " cd C:\Android\sdk\platform-tools " then you type in adb devices should read your device fine now. however running cmd as admin prevents the drag and drop technique (atleast here on windows 8.1 it does) so you have to type in the location of your rom and rom name correctly, and dont forget the .zip
Ghand0ur said:
open platform-tools(or the folder where adb is found) shift + right click on any empty space, you will find "open command prompt here" press on it, then type ADB devices, if it is read, simply type " adb sideload " then drag and drop the rom zip into the command prompt. it will automatically write its location and prevent the spelling mistakes.
IF: ADB devices can't read your device try the following:
1-Try another usb port, if you tried 2.0 then try 3.0 and vice versa.
2- If you are on windows vista or above, open start menu and search for cmd, right click on it and run as administrator, however you will have to cd to the platform tools location, " cd C:\Android\sdk\platform-tools " then you type in adb devices should read your device fine now. however running cmd as admin prevents the drag and drop technique (atleast here on windows 8.1 it does) so you have to type in the location of your rom and rom name correctly, and dont forget the .zip
Click to expand...
Click to collapse
Ok great thanks it worked! Question: can u flash a custom kernel that's not in the same and ROM? I got viper ROM and everything is slow and I'm trying to make it fast
Sent from my SGH-T999 using xda app-developers app
brianisawesome1 said:
Ok great thanks it worked! Question: can u flash a custom kernel that's not in the same and ROM? I got viper ROM and everything is slow and I'm trying to make it fast
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Since we have the stupid s-on, your choice of custom kernels is very limited and they make almost no difference, if you are on viper rom which is sense based, you can use the stock kernel (I THINK<<< Not sure) or insertcoin kernel's , but no they don't make any difference as far as i know. Try and see
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
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"
Hi there,
SOLVED
I first of all want to thank you all for the amazing guides you have on rooting phones. I managed to do it and I have never attempted anything like this before. So thank you!
Okay, so I have an issue with my phone. I cannot do anything with the /system/app folder, I cannot delete, I cannot rename and it's driving me up the wall.
I flashed my phone with Generic Firmware so I could use Towelroot to root the phone. It all worked well and all apps show that my phone is rooted. But no matter what I cannot for the life of me get anything to work. It is as if I do not have permissions to modify /system/
Any help would be great. I am using an xperia z2 and will be happy to answer any questions about what I've done.
SPGSean said:
Hi there,
I first of all want to thank you all for the amazing guides you have on rooting phones. I managed to do it and I have never attempted anything like this before. So thank you!
Okay, so I have an issue with my phone. I cannot do anything with the /system/app folder, I cannot delete, I cannot rename and it's driving me up the wall.
I flashed my phone with Generic Firmware so I could use Towelroot to root the phone. It all worked well and all apps show that my phone is rooted. But no matter what I cannot for the life of me get anything to work. It is as if I do not have permissions to modify /system/
Any help would be great. I am using an xperia z2 and will be happy to answer any questions about what I've done.
Click to expand...
Click to collapse
Go to super su and uncheck mount system space *something*
Sent from my D6503 using XDA Free mobile app
Safarend said:
Go to super su and uncheck mount system space *something*
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
I'm afraid that didn't do much of anything.
Thanks though.
Untick mount namespace seapration and reboot
Sent from my D6503 using XDA Free mobile app
Safarend said:
Untick mount namespace seapration and reboot
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
Yep I did that. It didn't change anything :/
SPGSean said:
Yep I did that. It didn't change anything :/
Click to expand...
Click to collapse
Which app are you using to modify system files? Did you enable root in that application? Can you see that the supersu give a permission to that app?
Sent from my D6503 using XDA Free mobile app
Safarend said:
Which app are you using to modify system files? Did you enable root in that application? Can you see that the supersu give a permission to that app?
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
I've tried everything from Rom toolbox, to Titanium Backup, to ES File Browser, to Root browser.
I've also tried removing it through shell and it says read only file system.
I cannot change the file system to RW I have tried that in ES FIle manager and it doesnt do anything. No errors, no warnings no nothing.
SPGSean said:
I've tried everything from Rom toolbox, to Titanium Backup, to ES File Browser, to Root browser.
I've also tried removing it through shell and it says read only file system.
I cannot change the file system to RW I have tried that in ES FIle manager and it doesnt do anything. No errors, no warnings no nothing.
Click to expand...
Click to collapse
[STOCK][LOLLIPOP] D6503 23.1.A.0.690 BAL | Rooted | No recovery | Mirrors added - http://forum.xda-developers.com/showthread.php?p=59500251
[STOCK][LOLLIPOP] D6503 23.1.A.0.690 BAL | Rooted | No recovery | Mirrors added
Go to this link and try to take similar picture of root checker
Sent from my D6503 using XDA Free mobile app
Safarend said:
[STOCK][LOLLIPOP] D6503 23.1.A.0.690 BAL | Rooted | No recovery | Mirrors added - http://forum.xda-developers.com/showthread.php?p=59500251
[STOCK][LOLLIPOP] D6503 23.1.A.0.690 BAL | Rooted | No recovery | Mirrors added
Go to this link and try to take similar picture of root checker
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
Hi,
I have got 3 pictures.
http://pixldrop.com/drop/H0Vmaw5RzmwUMKh0.png
http://pixldrop.com/drop/JBTx5gITlkoKsUn5.png
http://pixldrop.com/drop/jMyNmGyunaVORA2P.png
Sihuca said:
I think thats what u looking for. u need the correct SU for it.
adb root
adb remount
adb push su /system/xbin/
adb push su /system/bin/
adb shell
[email protected]:/ # chmod 4755 /system/xbin/su
[email protected]:/ # chmod 4755 /system/bin/su
Click to expand...
Click to collapse
Check this out.
Sent from my D6503 using XDA Free mobile app
Safarend said:
Check this out.
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
Got these errors
http://pixldrop.com/drop/IRLFEWP4ieFaO5Qt.png
SPGSean said:
Got these errors
http://pixldrop.com/drop/IRLFEWP4ieFaO5Qt.png
Click to expand...
Click to collapse
adb push su ******
su here is a binary file that you need to download not a command
Sent from my D6503 using XDA Free mobile app
---------- Post added at 03:10 AM ---------- Previous post was at 03:08 AM ----------
Push the file su to the two directory specified
Sent from my D6503 using XDA Free mobile app
Safarend said:
adb push su ******
su here is a binary file that you need to download not a command
Sent from my D6503 using XDA Free mobile app
---------- Post added at 03:10 AM ---------- Previous post was at 03:08 AM ----------
Push the file su to the two directory specified
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
Do you have a link to SU?
Thanks!
---------- Post added at 03:20 AM ---------- Previous post was at 03:18 AM ----------
[/COLOR]
SPGSean said:
Do you have a link to SU?
Thanks!
Click to expand...
Click to collapse
http://download.chainfire.eu/supersu
This one is the last one ignore the previous link
Sent from my D6503 using XDA Free mobile app
---------- Post added at 03:21 AM ---------- Previous post was at 03:20 AM ----------
Under arm folder
Safarend said:
---------- Post added at 03:20 AM ---------- Previous post was at 03:18 AM ----------
[/COLOR]
http://download.chainfire.eu/supersu
This one is the last one ignore the previous link
Sent from my D6503 using XDA Free mobile app
---------- Post added at 03:21 AM ---------- Previous post was at 03:20 AM ----------
Under arm folder
Click to expand...
Click to collapse
Okay but I still don't have the ability to do adb root because my device is in secure mode
SPGSean said:
Okay but I still don't have the ability to do adb root because my device is in secure mode
Click to expand...
Click to collapse
Did you manage to push su ?
Safarend said:
Did you manage to push su ?
Click to expand...
Click to collapse
No. It won't allow me to do ADB Root
And when I go into ADB Shell and try to push using root it says no device found.
SPGSean said:
No. It won't allow me to do ADB Root
And when I go into ADB Shell and try to push using root it says no device found.
Click to expand...
Click to collapse
Copy the su file into your phone
adb push su /sdcard
---------- Post added at 03:56 AM ---------- Previous post was at 03:54 AM ----------
adb push su /sdcard
adb shell
su
cp /sdcard/su system/xbin
cp /sdcard/su system/bin
chmod blah blah for both su's
Safarend said:
Copy the su file into your phone
adb push su /sdcard
---------- Post added at 03:56 AM ---------- Previous post was at 03:54 AM ----------
adb push su /sdcard
adb shell
su
cp /sdcard/su system/xbin
cp /sdcard/su system/bin
chmod blah blah for both su's
Click to expand...
Click to collapse
Doesn't work either.
http://pixldrop.com/drop/NcjXRL4tpcHuMAGc.png
Take a pic of the folder containing su
---------- Post added at 04:13 AM ---------- Previous post was at 04:11 AM ----------
SPGSean said:
Doesn't work either.
http://pixldrop.com/drop/NcjXRL4tpcHuMAGc.png
Click to expand...
Click to collapse
It will be easier if you download the zip file from your phone and extract the su file to /sdcard
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