Got a SIM FREE Moto G4 from Amazon, unlocked bootloader and rooted (BETA-SuperSU-v2.74-2-20160519174328.zip with "SYSTEMLESS=true" > /data/.supersu – seems to be working as other versions don't work fully with some apps)). Also, GApps pack from http://opengapps.org/ seems to be working so far as well as the latest version of Xposed Framework.
Would appreciate if anyone can advise on following issues:
(1) A link where I can download a UK firmware (MPJ24.139-24.4, retgb, M8952_70004.04.03.32R ATHENE_EMEA_CUST)
(2) OEM\APP
The phone has an OEM Partition (using around 635mb) with APPs installed (Indian ones). Can’t be uninstalled but can be deleted using Root Explorer. Also, apps can be moved to OEM\app via Root Explorer and they seem to be working. However, when you go to System Settings>Apps, it crashes - 'Unfortunately, Setting has stopped'. Any ideas or UK firmware which does not have the partition – Hoping I can use the space: -)
Thanks
B
Ok, deleted all files and folders from OEM partition and it seems to be working. I think the phone is ready now for proper build\testing, will report if I experience any issues, cheers
XT1622 is a UK phone but came with India market apps in OEM partition?
Which apps we talking of?
Sorry for late reply, yes, indian apps like BellTVWidget, BRApps2, CCMyConsumer, OmegaPttBR, OmegaPttMX, FileBrowser-indian, Republic
Anyone knows where I can download UK SIM free firmware for this model (MPJ24.139-24.4, retgb, M8952_70004.04.03.32R ATHENE_EMEA_CUST)?
OTA update was failing ("error" message) so reverted to XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml.zip as I could not find a MPJ24.139-24.4, retgb version . However, when flashing I was getting below:
>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.531s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.438s]
finished. total time: 0.969s
>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (16484 KB)...
OKAY [ 0.531s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.438s]
finished. total time: 0.969s
Click to expand...
Click to collapse
The rest seems to have worked fine.
Any ideas?
buddimanv said:
Sorry for late reply, yes, indian apps like BellTVWidget, BRApps2, CCMyConsumer, OmegaPttBR, OmegaPttMX, FileBrowser-indian, Republic
Anyone knows where I can download UK SIM free firmware for this model (MPJ24.139-24.4, retgb, M8952_70004.04.03.32R ATHENE_EMEA_CUST)?
Click to expand...
Click to collapse
Do you know for sure if deleting those apps won't damage the phone? As a current owner of Huawei phone, I am pretty surprised (negatively) with the amount of garbage bloatware on Moto phones. Looks like nobody in Lenovo/Moto cares about providing a little bit customization to different regions' firmwares.
Bloatware on Moto phones?! Are we on a different planet??
I'm also struggling with UK XT1622... not much in the way of advice about this particular model online!
trevorcobb said:
XT1622 is a UK phone but came with India market apps in OEM partition?
Click to expand...
Click to collapse
Yes, just check my xt1622, it does have those apps.
Sold my G4 now, but you can delete them - no issues at all. Also, you can move apps to that partition and they work as well. On the other hand, on Huawei phones (p9 Lite and Honor 5C), you can also delete their oem\per-installed apps like keyboard, but apps don't work if you move them to that partition.
buddimanv said:
Sold my G4 now, but you can delete them - no issues at all. Also, you can move apps to that partition and they work as well. On the other hand, on Huawei phones (p9 Lite and Honor 5C), you can also delete their oem\per-installed apps like keyboard, but apps don't work if you move them to that partition.
Click to expand...
Click to collapse
buddimanv may not own the G4 any more, but I do, and I can assure you with 100% certainty that you cannot - i'll repeat that - you CANNOT delete files from the root/OEM/App folder without stuffing your phone. I know they have no relevance to the retgb version of the xt1622, but delete them at your peril. I did, and I could no longer open the android app manager (Settings/Apps) because every time I tried Settings would force close. Luckily I had a flashfire backup of my OEM partion (twrp does not back up this location by default or possibly at all, I am not sure) so if you only have a twrp backup there is no recovery from this situation, even a factory reset will not help you.
!!!DO NOT DELETE THESE APPS!!!
Lol..... was working for me – did it several times when I had the phone.
I had the same issue opening the settings\apps, but needed to delete other files from that PARTITION, I think the xml/prop file there. So, steps as below (from my memory):
1. COPY all the OEM partition folders\files to SD Card using Root Explorer (so you can move them back in case you have issues). The OEM partition can also restored if you upgrade firmware from scratch!
2. Delete ALL files from all OEM\Folders including xml/prop file (trying to remember what it was) &, REBOOT - you will be able to open Settings/Apps as well.
Note: don’t delete root folder like APPS, etc., just sub-folders.
You can also move apps to that partitions i.e. OEM\APP as it has over 500gb space or so (and reboot although one or two apps did not work, so just moved them again).
darkglobe87 said:
Bloatware on Moto phones?! Are we on a different planet??
Click to expand...
Click to collapse
No, we are not. As it is mentioned in the thread, there is an oem/app folder with bloatware. There are also google and moto bloatware: google play "music/video", google photo gallery, text-to-speech, chrome, youtube (etc - none can be deleted without root), minor useless moto apps (rescue add-on, for example), as well as moto remote services with only purpose of stalking about the user (3c_main and a bunch of other 3c-services).
The problem is that half of the bloatware is hidden. Messing with oem/app leads to permanent issues with settings/apps. And i confirm opinions above - it cannot be helped by restoring a twrp backup or a factory reset. After the official release of android 7 i'll try stock once again, but for now i prefer to stay at cm, which is mostly bloatware free
buddimanv said:
(2) OEM\APP
The phone has an OEM Partition (using around 635mb) with APPs installed (Indian ones). Can’t be uninstalled but can be deleted using Root Explorer. Also, apps can be moved to OEM\app via Root Explorer and they seem to be working. However, when you go to System Settings>Apps, it crashes - 'Unfortunately, Setting has stopped'. Any ideas or UK firmware which does not have the partition – Hoping I can use the space: -)
Thanks
B
Click to expand...
Click to collapse
Its bit odd that we still think that deleting the files from OEM partition don't work (you need Root of course). I mentioned the issue on my first post (i.e. can't access system\app) and then on the 2nd post stated that I have resolved the issue by myself through experimentation (on 27th August 2016, 12:16 PM. ). Perhaps, it was not clear so given steps above. lol
buddimanv said:
Ok, deleted all files and folders from OEM partition and it seems to be working. I think the phone is ready now for proper build\testing, will report if I experience any issues, cheers
Click to expand...
Click to collapse
buddimanv said:
Lol..... was working for me – did it several times when I had the phone.
I had the same issue opening the settings\apps, but needed to delete other files from that PARTITION, I think the xml/prop file there. So, steps as below (from my memory):
1. COPY all the OEM partition folders\files to SD Card using Root Explorer (so you can move them back in case you have issues). The OEM partition can also restored if you upgrade firmware from scratch!
2. Delete ALL files from all OEM\Folders including xml/prop file (trying to remember what it was) &, REBOOT - you will be able to open Settings/Apps as well.
Note: don’t delete root folder like APPS, etc., just sub-folders.
You can also move apps to that partitions i.e. OEM\APP as it has over 500gb space or so (and reboot although one or two apps did not work, so just moved them again).
Click to expand...
Click to collapse
Actually, I will give you that. If you completely empty the /root/oem/ folder then things seem to work normally, but you can't just remove the apps and leave the rest behind, strangely even removing the apps then later putting them back after a reboot doesn't work, the whole contents of the oem folder must be removed. I will leave my g4 in that state for a while and see if I notice any problems if I don't post back it is safe to do this, and does remove a bit of unnecessary bloat.
viking777, hmmm.....I don't have the phone anymore but would have sent a screenshot, lol.....But, I think you will find that if you remove associated files with the app deleted from these OEM\sub-folders, then it works. And/or there is a file under OEM root level which if you delete (can't remember whether it was xml or prop) system\app works. My objective was to use that space so I deleted everything and then moved loads of apps there and they worked fine.
buddimanv said:
viking777, hmmm.....I don't have the phone anymore but would have sent a screenshot, lol.....But, I think you will find that if you remove associated files with the app deleted from these OEM\sub-folders, then it works. And/or there is a file under OEM root level which if you delete (can't remember whether it was xml or prop) system\app works. My objective was to use that space so I deleted everything and then moved loads of apps there and they worked fine.
Click to expand...
Click to collapse
Well, you may well be right that there is some mid point that works where you delete some things but not others, but personally, I don't want to dig that deep into it. My difficulties have been well answered - can I delete the apps in root/oem/apps - answer no (at least not without deleting other things at the same time). Can I delete the whole contents of the /root/oem folder - answer yes. That is all I needed to know as it removes the unwanted bloat with no side effects (so far), so thanks for getting back and clarifying it.
BTW it was a build.prop file that you are recollecting in the /root/oem/ folder.
Related
The Motorola Flipout is fairly easy to root, at least now. Universal Androot (get it here) works.
I am thinking about moving apps to the sd card. However, since I haven't reflashed the phone, and I don't have a ROM for it, I'd like to do it without reflashing. Is that possible?
If I partition an SD card correctly (ext3), copy all of /data onto that partition, and then mount that partition over /data, will that work? Or do I have to mount the card before the phone boots?
Or is it better to just copy /data/data, and mount the partition over /data/data?
It seems to me that mounting over a directory, as opposed to creating a link is least invasive, because on reboot the phone is as it was before. Is this right?
If I have to mount the sdcard before the phone boots, can I just edit one of the init scripts, or is that more complicated? I read about editing init.rc and repacking boot.img
Oh, HOWTO unpack edit and repack boot images seems to give good instructions. On the Flipout, boot is mtd4, and recovery is mtd5.
If I only modify boot, I can't brick my phone too badly? Since I haven't changed recovery, I should be able to recover (?). Can I create an update.zip that flashes the old boot.img and undoes my changes in case something goes wrong?
I just got the flipout from rogers.. Is there anyplace that has a development forum for it? And does it have the efuse ? If it does, is it possible to do what was done with the droid X to it?
How did go so far ghostwheel? I'm eager to hear what else you have figured out.
You use App2Card.apk at below for app2sd without flash:
http://www.tinhte.vn/f280/app2card-2-4-4-20-9-cai-dat-ung-dung-len-nho-phan-vung-456586/
Requires: just a rooted phone
Steps:
- install app
- click Menu / Partition button then use slide bars to create ext2 for your sd card if it hasn't been splited yet
- click Install App2card button
- phone will be rebooted and you just taste app on sd after then
Note: above page has further instruction but it is vietnamese, you must use google translate to get it. This app runs perfectly on my Milestone.
Sent from my Milestone using XDA App
ghostwheel said:
The Motorola Flipout is fairly easy to root, at least now. Universal Androot (get it here) works.
I am thinking about moving apps to the sd card. However, since I haven't reflashed the phone, and I don't have a ROM for it, I'd like to do it without reflashing. Is that possible?
If I partition an SD card correctly (ext3), copy all of /data onto that partition, and then mount that partition over /data, will that work? Or do I have to mount the card before the phone boots?
Or is it better to just copy /data/data, and mount the partition over /data/data?
It seems to me that mounting over a directory, as opposed to creating a link is least invasive, because on reboot the phone is as it was before. Is this right?
If I have to mount the sdcard before the phone boots, can I just edit one of the init scripts, or is that more complicated? I read about editing init.rc and repacking boot.img
Oh, HOWTO unpack edit and repack boot images seems to give good instructions. On the Flipout, boot is mtd4, and recovery is mtd5.
If I only modify boot, I can't brick my phone too badly? Since I haven't changed recovery, I should be able to recover (?). Can I create an update.zip that flashes the old boot.img and undoes my changes in case something goes wrong?
Click to expand...
Click to collapse
Hi,
I'd really like to help with that (I'm a confirm dev. for Cliq and CliqXT phones).
Hopefully we can do great things like we did for Cliq and CLiqXT (upgrade to 2.1!). (check my work at http://bit.ly/adlxmod).
First thing would be to generate a system dump (a dump of all the files in the /system partition). Hopefully we then could generate a custom recovery to flash on the phone, and then custom roms, either base on the dump you provide or other roms from other files. Contact me on twitter @adumont (say it's for Flipout) and I'll guide you to generate the dump!
Looking forward to do great things for that litle phone!
I'm in touch with adlxdum to give him my dump but I think we should start a separated thread like "Custom rom, modding (work in progress)" so that we can follow adlxdum work.
And...thx in advance ;-)
flusshd said:
You use App2Card.apk at below for app2sd without flash:
http://www.tinhte.vn/f280/app2card-2-4-4-20-9-cai-dat-ung-dung-len-nho-phan-vung-456586/
Requires: just a rooted phone
Steps:
- install app
- click Menu / Partition button then use slide bars to create ext2 for your sd card if it hasn't been splited yet
- click Install App2card button
- phone will be rebooted and you just taste app on sd after then
Note: above page has further instruction but it is vietnamese, you must use google translate to get it. This app runs perfectly on my Milestone.
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
Worked!
I couldn't repartition the SD card with the program, so I had to partition it myself. But once that was done, thing seem to work well. A bit slower...
I'm not totally sure how to use the app. Internal seems to still be full, but ext2 on the SD is quite empty. I can't seem to be able to tell if an app is installed to internal or external.
I have to try and install some more apps to see if I run out of memory.
Thanks!!
I'm guessing the flipout and charm are almost identical phones?
My wife has a charm and i'm one of those "i'm not a developer, but I'd like to help" guys.
MrShides said:
I'm guessing the flipout and charm are almost identical phones?
My wife has a charm and i'm one of those "i'm not a developer, but I'd like to help" guys.
Click to expand...
Click to collapse
Yes, I think they are very similar.
One thing that I'm interested in is the accelerometer. On the Flipout, most apps that use it are twisted - for example wikitude, and many games (labyrinth lite works!) I wonder if things work on the charm...
the charm has the same issue.
MrShides said:
the charm has the same issue.
Click to expand...
Click to collapse
thanks! Too bad....
Hi ghostwheel
I've tried installing app2card, but I'm having some problems. I got the new version 2.7.2.
As you said, the partition doesnt work. For me it says sd card is full but its empty...
How did you manually partition it?
I've found some tutorials but it was for other phones and they required a custom rom...
I partitioned the card using a linux computer, with the program fdisk.
I allocated 2GB to a partition of type ext2. But, I think there are many alternatives for partitioning a disk, see this page:
http://androidcommunity.com/forums/f9/how-to-create-ext2-partition-14232/
Wow great link! Many different options! Will try this as soon as I get a micro sd card adapter. Thanks!
You mentioned in your old post that you were having problems using app2card, That you weren't sure if it was working. Have you been able to use it since? Is it working well? and if not have you found an alternative?
I just started using this phone and I'm almost running out of memory... this is quite annoying!
longlife_01 said:
You mentioned in your old post that you were having problems using app2card, That you weren't sure if it was working. Have you been able to use it since? Is it working well? and if not have you found an alternative?
!
Click to expand...
Click to collapse
Yes, I was having problems. Mainly when restarting the phone, sometimes oodles of apps don't work, including launcher pro, and app2card. You have to remember that when the phone reboots and seems to have FC problems, don't chose any home screen as the default, in case it crashes, and keep a spare app2card to reinstall on the sdcard. I think "severe" problems I had only twice, or so.
So, I have almost no problems. Most of the time it works really well. So well, in fact, that I'm a bit afraid to upgrade it, in case something breaks. And, I totally forgot what it is like to have to delete apps to install another one.
I have more of the opposite problem - finding an app among all those installed takes a realllly long time if you forgot its name. Apps organizer helps.
hello, i am new and i have flipout to test in poland orange network, i just root him using 1st post in this forum, great job! thanks
OK, I am having some problems with the current version of app2card. As I said, sometimes when I turn the device off and back on, app2card fails, and many apps give a FC which starting. Then one needs to fix the apps from app2card. It seems that once that is done, some apps lose some of their data. So, for example, droidwall (excellent program!!), lost all firewall data. I'll have to check if newer versions of app2card don't have this problem. It doesn't happen very often.
Instructions to root Flipout
Hi - I'd consider myself a newbie regarding rooting. I just got the AT&T Flipout - I really like the form factor. I just tried running the Universal Androot from my phone but got the security warning message about only being able to install from trusted sources.
Can someone point me in the right direction please?
Many thanks!
it says that with a lot of apps installed like that, including gmote that I downloaded from the developers site. Just look at what you're downloading like you would on any machine
go to settings > Application and tick on unknown sources to be able to install it.
U8800V100R001C00B136(Overseas General version) is available at Huawei's downloadcenter. When I unzip that, there are two APPs in the dload folder, UPDATE.APP and UPDATE_CUST.APP
What is that CUST.APP, what does it include? Do I have to use that too when upgrading?
My current version seems to be U8800V100R001COOB136 with custom version CUSTC235D001 (Elisa-edition in Finland). Can I update my phone with that new package to get rid of extra applications?
Thanks, and sorry about stupid questions....
Hi, well to pinpoint out the most obvious. They included a pdf guide, have you given a quick look at it?
Simple steps.
1.Have clean SD card with a folder called dload and place everything in that folder. You must have at least 512MB free space after placing the files into SD card.
2.Turn off Phone.
3.Hold Volume down and up buttons, start the phone.
4.Wait, the phone will start upgrading firmware.
5.???
6.Profit !!!
Anyhow this should sum up the whole thing.
Don't forget to backup !
Thanks for the reply!
And yes, I read the pdf, actually twice
But now I still want to know what that UPDATE_CUST.APP contains (some Huawei-branded-extra-apps?), and do I have to install that too or can I remove it and use only UPDATE.APP....
Yari71 said:
Thanks for the reply!
And yes, I read the pdf, actually twice
But now I still want to know what that UPDATE_CUST.APP contains (some Huawei-branded-extra-apps?), and do I have to install that too or can I remove it and use only UPDATE.APP....
Click to expand...
Click to collapse
yes u can skip UPDATE_CUST.APP and just upgrade with UPDATE.APP.. in this way ur current /cust/xxx/xxx/ folder will be kept intact..
that UPDATE_CUST.APP contains some extra apps that may or may not be useful to u.. though i have upgraded with the whole package, most of the cust apps were removed afterwards and i kept just 3 (Google Goggles, Huawei Input Method, and Swype Input Method)..
No problems in installation, everything worked fine after restart.
No more custom-apps/games
Some unnnecessary apps still available: Aldiko, Documents To Go, Hi Space...
Let's see if this works ok
When I go to huaweidevice.com and then downloads, I don't have the Build 136 to download, link anyone?
wiki dot modaco dot com/index.php/Huawei_Firmware_U8800
or
www dot huaweidevice dot com/cn/downloadCenter.do?method=list&flay=software&directoryId=20&treeId=0#
(no idea why there is this white space in "directoryId", remove it...)
Well, that "Overseas General version" did not work properly, calls end randomly, no idea how to fix that. Must use the original one...
Hi,
This is my first time with android - that's why I'm trying SD.
All went ok for about 3 days - I tried many apps from the market & all of a sudden my phone rebooted!
When it booted again I saw the lock screen & can see the tiny icons on the status bar then it just reboot again!
After several attempts I got it booting but most of the apps now force close - my contacts are gone so as my SMS.
Any idea what might caused something like that? is Android so vulnerable that
installing some application can cause a total loss of the system?
- Do I need to re-install every thing again?
- will deleting data.img is enough to force a clean install?
- Is there a way to restore my old data from data.img?
- Is there a recommended book to upgrade from a noob to an educated user?
Thanks,
it's strange because when Americn android craches, it should bootloop.
here's a couple of suggestions:
backup the valuable contents of your SD card then search for file system errors, if your card has a corrupt file here and there it might be the one causing the problem, for the how to, it's in my troubleshooter, check my sig.
Usually a fresh data.img file is considered a clean install unless you've messed with root explorer (or any similar app) and did something wrong to your sytem files.
I'm not sure how to get the data back, I know you can access the data.img contents using a special tool, see here for info http://www.howtoforge.com/access-linux-partitions-from-windows
there's also a tool on softpedia to do so.
but you can try to look for the SMS data somewhere on your data.img, extract them to your harddrive, then copy them back using android explorer. I haven't tried it, and theoretically it might work, but I can not guarantee it.
My advice is that don't put too much pressure on the device, it's running Android from the SD which is not designed to work as NAND. let the device take a breath for a few seconds after each installation, it may say it finished, but it's still doing something in the background, I learned that the hard way. and always backup our data before you do something new.
and yes, if you use a fresh data.img you will have to install everything again.
I'm following the beginners guide to release my Moto X Pure from it's shackles and am getting this from the command prompt on step 2.
Can anyone provide some assistance?
https://forum.xda-developers.com/moto-x-style/general/guides-how-to-guides-beginners-t3200808
C:\Android\sdk\platform-tools>fastboot flash recovery twrpclark.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (0 KB)...
OKAY [ 0.004s]
writing 'recovery'...
(bootloader) Invalid boot image
FAILED (remote failure)
finished. total time: 0.019s
C:\Android\sdk\platform-tools>
You need a newer TWRP image most likely, if you are using the one in that tutorial it is OLD!!!
The Moto X Pure/Style is officially supported device. Go to https://dl.twrp.me/clark/ and download
twrp-3.0.2-0-clark.img
Make sure your bootloader is unlocked and enter the following command:
fastboot flash recovery twrp-3.0.2-0-clark.img
Do NOT reboot, then on your device press VOL DN until it says Recovery and press Power, TWRP should start and allow changes to system and perform a backup to the SD card.
And BTW, pretty much everything else in that tutorial after the bootloader unlock is incorrect/outdated. Look in my signature for the proper way to root if that is your objective.
Thanks again. Petition signed.
Is there an up to date sticky/guide on editing build.prop? I believe I need to add the following line so I can use native hot spot.
net.tethering.noprovisioning=true
I've downloaded ES File Explorer but I don't know if something has changed in Android or in the Explorer, but the guide I'm following isn't helping.
lip008 said:
Is there an up to date sticky/guide on editing build.prop? I believe I need to add the following line so I can use native hot spot.
net.tethering.noprovisioning=true
I've downloaded ES File Explorer but I don't know if something has changed in Android or in the Explorer, but the guide I'm following isn't helping.
Click to expand...
Click to collapse
Got me... I've never had a problem tethering on any Moto device.
acejavelin said:
Got me... I've never had a problem tethering on any Moto device.
Click to expand...
Click to collapse
Neither have a lot of people from what I've read. I didn't have this issue on the Z Play but I sold that device. I want the Pure to be my daily driver, but I need to get this hot spot working. All this work for this!
lip008 said:
Neither have a lot of people from what I've read. I didn't have this issue on the Z Play but I sold that device. I want the Pure to be my daily driver, but I need to get this hot spot working. All this work for this!
Click to expand...
Click to collapse
I think you are chasing the wrong problem... The fix you have is for when carrier's block tethering in provisioning, if it worked fine in Z then that isn't the problem.
I assume you tried the normal cache wipe, network reset, and maybe even factory default?
You need to try to use it and when it fails pull a logcat and see why.
acejavelin said:
I think you are chasing the wrong problem... The fix you have is for when carrier's block tethering in provisioning, if it worked fine in Z then that isn't the problem.
I assume you tried the normal cache wipe, network reset, and maybe even factory default?
You need to try to use it and when it fails pull a logcat and see why.
Click to expand...
Click to collapse
IDK. Lots of unlocked devices still honor the carrier's flag in regards to hotspot. The Nexus devices and my gfriend's Pixel does. A new unlocked Axon 7 or the Moto Z Play do not. I've hard reset the device and now that it's been bootloader unlocked, reset again. I haven't wiped any cache or a network reset. Are those done automatically once a factory reset/bootloader unlock is done?
My device says to contact the carrier in regards to getting the hot spot enabled. I haven't tried it again with the bootloader being unlocked, but I will give it a go this morning and see what happens.
lip008 said:
IDK. Lots of unlocked devices still honor the carrier's flag in regards to hotspot. The Nexus devices and my gfriend's Pixel does. A new unlocked Axon 7 or the Moto Z Play do not. I've hard reset the device and now that it's been bootloader unlocked, reset again. I haven't wiped any cache or a network reset. Are those done automatically once a factory reset/bootloader unlock is done?
My device says to contact the carrier in regards to getting the hot spot enabled. I haven't tried it again with the bootloader being unlocked, but I will give it a go this morning and see what happens.
Click to expand...
Click to collapse
Hmm... That sure sounds like carrier provisioning, weird... I technically don't have tethering on H2O but it works fine and I am stock and bootloader locked.
EDIT: Well, I am a bold faced liar... I tried it now on H2O and got the "Account not set up for tethering" messaging, I know it worked on AT&T before I switched last month but I think my account there had it. Now I am curious too...
Maybe best to search in the Moto X area and if you can't find a thread about it (I looked, but only for a minute), start a new one... the title of this thread won't likely get help for this problem.
---------- Post added at 08:52 AM ---------- Previous post was at 08:49 AM ----------
I found this:
Enable Wireless Tethering Rooted Moto X Pure
1. Modifying system files could render your device useless, so by continuing you’re assuming that risk
2. Using a root file explorer, navigate to /system/
3. (Optional) Make a copy of the build.prop
4. Open the build.prop file with a text editor
5. Add the following line to the bottom of build.prop file: net.tethering.noprovisioning=true
6. Save the file and reboot your device
Click to expand...
Click to collapse
Might root again and try it, I haven't had a need for root in a while... Will see, I am lazy so maybe I won't until I need to.
I generally prefer using Solid Explorer in Root Mode and QuickEdit for editing root files... ES File Explorer was once king, but became overbloated garbage the last couple years.
That's what brings me back to editing the build.prop.
I have a ES file Exporer and checked off the root option so I should be able to access everything on the device.
I have never edited the build.prop and need to find the file path for it.
A sticky or something on editing build.prop would be great.
lip008 said:
That's what brings me back to editing the build.prop.
I have a ES file Exporer and checked off the root option so I should be able to access everything on the device.
I have never edited the build.prop and need to find the file path for it.
A sticky or something on editing build.prop would be great.
Click to expand...
Click to collapse
No likely... It is so rare to have to edit it anymore, so few things require it.
Try a different explorer... ES is junk, use Solid or Root Explorer
acejavelin said:
No likely... It is so rare to have to edit it anymore, so few things require it.
Try a different explorer... ES is junk, use Solid or Root Explorer
Click to expand...
Click to collapse
Thanks you...especially for the quick replies. Maybe I will start up a new thread if I can't find an existing one on this hot spot issue.
lip008 said:
Thanks you...especially for the quick replies. Maybe I will start up a new thread if I can't find an existing one on this hot spot issue.
Click to expand...
Click to collapse
Here is the thread... You can bump it if you need to: https://forum.xda-developers.com/mo...nable-wireless-tethering-moto-x-pure-t3227738
acejavelin said:
Here is the thread... You can bump it if you need to: https://forum.xda-developers.com/mo...nable-wireless-tethering-moto-x-pure-t3227738
Click to expand...
Click to collapse
How do I bump a thread?
lip008 said:
How do I bump a thread?
Click to expand...
Click to collapse
Lol... Just post a reply, it will "bump" it to the top of the thread list for that section.
acejavelin said:
Here is the thread... You can bump it if you need to: https://forum.xda-developers.com/mo...nable-wireless-tethering-moto-x-pure-t3227738
Click to expand...
Click to collapse
I was confused by the "you can bump it if you need to" comment. I took it as being something extra in addition to replying. I wasn't able to figure out the root path, but using the search function on ES Explorer I found the build.prop file, made the change, and presto....I know have hotspot working. Next up is to research the popular ROMS. I'm interested in some of the built in features like ad blocking and of course Nougat. Thanks again.
The following is the latest version of TWRP compiled for the T-mobile V10 Model H901.
https://androidfilehost.com/?fid=818070582850501883
MD5SUM: b89d341cd61da31a5348d8f6b3c75c97
The heavy lifting was done by the twrpbuilder project who were generous enough to compile TWRP for our device. They also provide their services to see TWRP is available for devices that don't yet have it. I've personally used this version to do a backup and restore but can't guarantee there won't be issues. If there are while you are still in twrp you should go to the advanced section and copy the log to your external sd card. This log will help them diagnose any issues.
The project is located at: https://twrpbuilder.github.io
Their XDA thread is located here: https://forum.xda-developers.com/android/apps-games/twrpbuilder-t3744253
If you already have TWRP installed installation is as follows: Click Install, choose Image file, navigate to where the TWRP img file is located on your external sdcard and flash that img to the recovery partition. Back out to the root dir and you can select reboot then recovery...it should bounce you right back into recovery and you should see the new version loaded. If you have root in the rom and run into issues the app "flashify" can reflash TWRP 3.0 so make sure you also have it's img available.
This is pretty much only for folks who already have twrp to update to the latest. If you are on nougat you are still stuck until an exploit is released that works for nougat the way dirtycow did for marshmallow and below. *update* an exploit to give root to nougat users is now available thanks to @runningnak3d here: https://forum.xda-developers.com/tmobile-lg-v10/general/root-h901-nougat-t3773942
Reserved Post #1
Reserved Post #2
famewolf said:
The following is the latest version of TWRP compiled for the T-mobile V10 Model H901.
https://www.androidfilehost.com/?fid=8180705828505018
MD5SUM: b89d341cd61da31a5348d8f6b3c75c97
Click to expand...
Click to collapse
Looks to me like that URL should read
https://androidfilehost.com/?fid=818070582850501883
[ EDIT ] Yup, confirmed.. The URL I listed works fine.
Thanks for the file!
:laugh::silly:
NYLimited said:
Looks to me like that URL should read
https://androidfilehost.com/?fid=818070582850501883
[ EDIT ] Yup, confirmed.. The URL I listed works fine.
Thanks for the file!
:laugh::silly:
Click to expand...
Click to collapse
You are correct. For some reason a few characters got truncated. I've corrected the url in post #1.
famewolf said:
The following is the latest version of TWRP compiled for the T-mobile V10 Model H901.
https://androidfilehost.com/?fid=818070582850501883
MD5SUM: b89d341cd61da31a5348d8f6b3c75c97
The heavy lifting was done by the twrpbuilder project who were generous enough to compile TWRP for our device. They also provide their services to see TWRP is available for devices that don't yet have it.
Click to expand...
Click to collapse
Just as an aside, this version seems to correct (mostly) the date issue of previous TWRP versions for the V10. Versions before this one used to generate a default date (folder name) for the backup dating back to the 1970s as I recall.
This one has the correct month and day and time and the year is only 1 off - it showed 2017 on my very quick attempt to play with it.
One additional note to those installing it via TWRP itself - after selecting image flash , MAKE SURE you specify RECOVERY partition, not BOOT! Specifying BOOT will most likely have some less than desirable results.. :laugh:
NYLimited said:
Just as an aside, this version seems to correct (mostly) the date issue of previous TWRP versions for the V10. Versions before this one used to generate a default date (folder name) for the backup dating back to the 1970s as I recall.
This one has the correct month and day and time and the year is only 1 off - it showed 2017 on my very quick attempt to play with it.
One additional note to those installing it via TWRP itself - after selecting image flash , MAKE SURE you specify RECOVERY partition, not BOOT! Specifying BOOT will most likely have some less than desirable results.. :laugh:
Click to expand...
Click to collapse
I've passed on the date issue. Uncertain if he'll generate another build though.
famewolf said:
I've passed on the date issue. Uncertain if he'll generate another build though.
Click to expand...
Click to collapse
Seems that either nobody is using this version or nobody knows about it or they just have nothing to say..
Anyway, as you know, I have spent a fair amount of time recently working with this and installing it. A couple of observations that may be worth noting..
I double checked and I did set a screen timeout on TWRP. Previous versions would first, dim the screen, followed by turning it off completely. If you had the device near you on a desk while backing up the screen lighting up again when TWRP completed was a sure signal that it was finished.
This version of TWRP dims the screen but the screen is never turned off completely. A minor annoyance I suppose but something is different from previous versions.
During the /data partition backup I noted a (to me) new display in yellow: "Backups of data do not include any files in internal storage such as pictures or downloads"
Seriously? Is this something new? Certainly the display is but I always kinda relied on all that being backed up with /data and having the ability to restore them. This is a more serious issue for me which may make me consider going backward..
Thoughts?
NYLimited said:
Seems that either nobody is using this version or nobody knows about it or they just have nothing to say..
Anyway, as you know, I have spent a fair amount of time recently working with this and installing it. A couple of observations that may be worth noting..
I double checked and I did set a screen timeout on TWRP. Previous versions would first, dim the screen, followed by turning it off completely. If you had the device near you on a desk while backing up the screen lighting up again when TWRP completed was a sure signal that it was finished.
This version of TWRP dims the screen but the screen is never turned off completely. A minor annoyance I suppose but something is different from previous versions.
During the /data partition backup I noted a (to me) new display in yellow: "Backups of data do not include any files in internal storage such as pictures or downloads"
Seriously? Is this something new? Certainly the display is but I always kinda relied on all that being backed up with /data and having the ability to restore them. This is a more serious issue for me which may make me consider going backward..
Thoughts?
Click to expand...
Click to collapse
I use my v10 as my backup phone now. On my HTC U11 life when I make a nandroid it shows that it is not backing up files on internal storage. I think this is normal now on the latest version of twrp.
NYLimited said:
Seems that either nobody is using this version or nobody knows about it or they just have nothing to say..
Anyway, as you know, I have spent a fair amount of time recently working with this and installing it. A couple of observations that may be worth noting..
I double checked and I did set a screen timeout on TWRP. Previous versions would first, dim the screen, followed by turning it off completely. If you had the device near you on a desk while backing up the screen lighting up again when TWRP completed was a sure signal that it was finished.
This version of TWRP dims the screen but the screen is never turned off completely. A minor annoyance I suppose but something is different from previous versions.
During the /data partition backup I noted a (to me) new display in yellow: "Backups of data do not include any files in internal storage such as pictures or downloads"
Seriously? Is this something new? Certainly the display is but I always kinda relied on all that being backed up with /data and having the ability to restore them. This is a more serious issue for me which may make me consider going backward..
Thoughts?
Click to expand...
Click to collapse
On your last issue this is business as usual...twrp has NEVER backed up the internal SDCARD unless you selected the sdcard entry in the list of sections to be backed up. DCIM (pictures) and the Downloads folder/dir have never been included.
As to the dimming, you can check in settings to see if something can be configured however each person compiling twrp can set their own options as to how they want it to function. There is no guarantee or expectation that Person B is going to use the same options as Person A. You are of course free to compile your own copy configured the way you would prefer it to behave but the process was enough of a pain in the butt I just requested twrpbuilder to generate one as I kept getting errors. The process to compile it also appears poorly documented.
sabresfan said:
I use my v10 as my backup phone now. On my HTC U11 life when I make a nandroid it shows that it is not backing up files on internal storage. I think this is normal now on the latest version of twrp.
Click to expand...
Click to collapse
I kinda suspected that but that is, at best, a questionable choice since I don't even have the option to check or uncheck a selection for it. Not happy..
famewolf said:
On your last issue this is business as usual...twrp has NEVER backed up the internal SDCARD unless you selected the sdcard entry in the list of sections to be backed up. DCIM (pictures) and the Downloads folder/dir have never been included.
Click to expand...
Click to collapse
Not quite. INTERNAL is not the SD Card. Internal is emulated sd on /0. In TWRP if you tap select storage, for example, you can pick "internal" or "SD" for backup destination, as one example.
I keep a fair number of things in /Download - things I grab in my travels, things I save there for later use.. whatever. I'll have to device a Tasker module or something for copying all those to the actual SD card...
NYLimited said:
I kinda suspected that but that is, at best, a questionable choice since I don't even have the option to check or uncheck a selection for it. Not happy..
Not quite. INTERNAL is not the SD Card. Internal is emulated sd on /0. In TWRP if you tap select storage, for example, you can pick "internal" or "SD" for backup destination, as one example.
I keep a fair number of things in /Download - things I grab in my travels, things I save there for later use.. whatever. I'll have to device a Tasker module or something for copying all those to the actual SD card...
Click to expand...
Click to collapse
A fairly recent app/utility created by @kdrag0n called Tipatch brings a long-needed resolution to the table regarding "full backups" of Data using TWRP. In a nutshell, Tipatch installs to your Android device as a basic APK. Within the simple GUI, once root permissions are granted (In-Place Patching) Tipatch will decompile, patch, recompile and flash the patched TWRP to /recovery, effectively patching your TWRP build to backup the contents of Internal Storage (emulated SD card) as part of Data itself, so that backups will now include those Internal Storage contents such as downloads, photos, videos, game data, and other various files. I've tried it on this particular build of TWRP and it works without any issues. There are options to patch TWRP without root permissions as well. There are Windows, Mac & Linux versions available too. If you are patching TWRP on a device with an A/B partitioning scheme, the patched TWRP can be installed on both A & B using a one-click option. Of course, one insurmountable caveat to patching TWRP with Tipatch is that wiping Data now will also wipe Internal Storage (emulated SD card). In short, the utility works on pretty well all device types and chipset platforms (Exynos, Kirin, Snapdragon, MediaTek, etc.). The latest Tipatch update, v1.6, includes support for TWRP builds that use LZMA compression, and removes the now-misleading notification previously listed when backing up Data -- that Internal Storage (/data/media/ path / emulated SD card) contents are not backed up. Anyway guys, here is a link to the Tipatch Discussion & Support thread: https://forum.xda-developers.com/android/apps-games/app-twrp-tipatch-backup-internal-t3831217
The latest Tipatch v1.6 app is also available on the Play Store and many other app & apk repos for Android. Versions for Windows, Mac and Linux can be downloaded using the above link.