Related
Google Maps Voice Navigation was much simpler to set up on a Cyanogen ROM then reading the thread made it seem, so I made a script that follows the same process I did, and though it should work, I have not tested it, so please let me know if it needs any fixes. It will back-up any necessary files to the sdcard, so there are no real worries in giving it a try.
1. Download Google Voice from the market
2. Unzip the file, and make sure the two files, build.trout.prop, and mapsnav.sh are on the root of the sdcard.
3. Open the terminal and enter
Code:
su
sh sdcard/mapsnav.sh
This will do its work then reboot the phone. When it is back up, you should be set.
Doesn't seem to work for me. Upon running the script, I got a few errors ("Google not found," "Cannot locate dalvik-cache on sd," etc.; the phone rebooted before I could get a look at all of them). After the reboot, I still had the same old Maps. I tried installing the APK provided in the zip, which seemed to be a successful install, but still, no navigate feature.
jay652 said:
Doesn't seem to work for me. Upon running the script, I got a few errors ("Google not found," "Cannot locate dalvik-cache on sd," etc.; the phone rebooted before I could get a look at all of them). After the reboot, I still had the same old Maps. I tried installing the APK provided in the zip, which seemed to be a successful install, but still, no navigate feature.
Click to expand...
Click to collapse
Are you using a Cyanogen ROM, with apps2sd?
cloverdale said:
Are you using a Cyanogen ROM, with apps2sd?
Click to expand...
Click to collapse
Yupp, 4.2.3.1, or whatever the second-latest one is.
The problem is that your dalvik-cache and maps folders seem to be somewhere other than on my phone. If you first clear your dalvik cache, find the maps folder in /data/data/, and erase it, then run the script, it should work. I will figure this out and post when I get off of work.
I got the "no google found" error.
Also on boot up im missing gmaps all together.
edit: i also forgot to mention while the script was running scoreboard and mixzing forceclosed.. and on boot up advanced launcher foreclosed about 5 times.
[Script] droidNavi
Try this to have the DROID maps w/Navi correctly installed.
Download the droidNavi.zip file
1: place DroidMaps folder on the root of your /sdcard
2: go into terminal
3: su
4: sh /sdcard/DroidMaps/naviScript.sh
and let it do its thing, also you must reboot once the script is done
ravenjr said:
Try this to have the DROID maps w/Navi correctly installed.
Download the droidNavi.zip file
1: place DroidMaps folder on the root of your /sdcard
2: go into terminal
3: su
4: sh /sdcard/DroidMaps/naviScript.sh
and let it do its thing, also you must reboot once the script is done
Click to expand...
Click to collapse
Will this work got the Magic too or just the Dream?
works for me thanks alot, i was hoping someone would make a script.... it did tell me google not found but it works =)
ravenjr said:
Try this to have the DROID maps w/Navi correctly installed.
Download the droidNavi.zip file
1: place DroidMaps folder on the root of your /sdcard
2: go into terminal
3: su
4: sh /sdcard/DroidMaps/naviScript.sh
and let it do its thing, also you must reboot once the script is done
Click to expand...
Click to collapse
i did this. Everything seems to have worked out fine... but i get forceclose upon opening navigate
got it to work. I had to install the speechsynth stuff from the settings.
Works great thx.
ravenjr said:
Try this to have the DROID maps w/Navi correctly installed.
Download the droidNavi.zip file
1: place DroidMaps folder on the root of your /sdcard
2: go into terminal
3: su
4: sh /sdcard/DroidMaps/naviScript.sh
and let it do its thing, also you must reboot once the script is done
Click to expand...
Click to collapse
This worked great! only problem is Google Voice doesn't work afterward. It force closed at first, then I reinstalled it, now it just will not download messages and will not call out.
almus said:
This worked great! only problem is Google Voice doesn't work afterward. It force closed at first, then I reinstalled it, now it just will not download messages and will not call out.
Click to expand...
Click to collapse
did you set it back up after the reinstall?
almus said:
This worked great! only problem is Google Voice doesn't work afterward. It force closed at first, then I reinstalled it, now it just will not download messages and will not call out.
Click to expand...
Click to collapse
I am having the exact same problem. This has happened to me before, and this fixed it at the time. But the solution does not apply here... anyone else with Google Voice problems?
--- fixed! ---
ok in debug mode I see these:
11-13 23:35:17.845: ERROR/GoogleVoice(2939): Unable to prepare post-Donut Contact API
11-13 23:35:17.845: ERROR/GoogleVoice(2939): java.lang.ClassNotFoundException: android.provider.ContactsContract$Contacts
...
Click to expand...
Click to collapse
I tried messing around with swapping out the contacts but gave up for now. I've replaced my build.prop and build.trout.prop files with the backed up ones and GV is working again. I've read that some people have seen the navigation menu disappear when they do this - it doesn't sound likely, but I'll be watching out for that for the next few days I guess.
So - go back to your prop files and GV and GM will both work, at least for now.
fixed! (I think)
hmm how do I delete a dupe post?
For those of you having trouble seeing protected apps, I modified our fingerprint in the build.prop. What this does is spoofs the market into thinking its seeing a Droid 2 (with Froyo) It worked for me, let me know if it does for you.
1. Put build.prop into your AndroidSDK\TOOLS folder
2. Connect via USB.
3. CD (Navigate) in CMD to your tools folder
Mount your /system (adb remount) works for me
Copy and paste this
4. adb remount
5. adb push build.prop /system/build.prop
6. adb reboot
To test if you need this before you push the build.prop fix, search the market for Us Bank. If only 2 or 3 show up, you are not getting the full market. After this fix, you should see 10 items listed when you search for Us Bank.
Hope this helps.
2.2 Market Fix Build.Prop -- WITH STAGEFRIGHT=TRUE
This can also be done via Root Explorer.
Edit: Here is a "clean" build.prop for those of you who do not want the stagefright fix (which breaks video playback) Sorry, I was not aware it did that. Thank you.
Non Stagefright Build.prop -- WITH STAGEFRIGHT=FALSE
For everyone flipping out about Birdmans tweet and you want the stock build.prop, here ya go
Stock Build.prop -- WITH NOTHING! STOCK!
You only need the stock one if you ever plan on doing a factory reset. But, you also cant do a factory reset if you have removed or renamed apps so I feel that should be mentioned. If you've done any modding and you are planning on upgrading, your best bet is to always use the SBF anyway. I dont think birdman realizes the panic he sets in with one little tweet. Factory resets suck anyway. But then again... "you decide..."
Thanks to Jcase for giving me the original idea way back when. I just basically applied his Eris Market Fix to work with our phones.
This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions
Found a fix
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Zaphod-Beeblebrox said:
This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions
Click to expand...
Click to collapse
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html
elkniwcire said:
i must say i take no responsibility if this causes problems but this worked for me. Do a search in the market for "eris market fix." it was designed for the eris but works just fine on my droid x. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but i assume most everyone on froyo already is rooted.
Click to expand...
Click to collapse
yes this worked for me aswell thank you
Yes this method definitely works. I have market working now and can search for protected apps etc.
elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.
he was just explaining where the idea comes from i think... You'd have to be crazy to use the eris market fix app on a droidx, just simply edit the build.prop fingerprint line.
I just used the root explorer meathod and now it wont boot.
I downloaded the file.
renamed my build.prob to build.prob/bak
placed the new build.prob in the system folder
rebooted and now after the M screen it just goes to a black screen with the backlight lit. Wont boot up. Im learning adb so this may be a noob question but can I access adb if the phone wont boot all the way up. That way I could change the build.prob back
Edit Delete Post: Im just retarted haha .prop not .prob :/
Could you plz give us some details on doing this with root explorer. Thanks
Prolly simple but I did try moving current build file then renaming and pasting yours without success doing us bank search. Also rebooted cleared cache and market history prior to search. Appreciate any help with doing this via root explorer.
LexusBrian400 said:
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html
Click to expand...
Click to collapse
LexusBrian400 said:
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.
Click to expand...
Click to collapse
I took a brief look at each file and I really don't understand how I got into trouble. As I said, I had not yet started doing any mods, just trying to install a few apps.
While I'm no computer or phone neophyte, I don't profess to be up to speed on Android yet. I do typically read through instructions pretty well, and search out multiple sources/explanations so I have a better 'understanding' of what I'm doing, rather than just "parrotting" the steps.
Having said that, I would like to know the difference between using 'adb remount' and the instructions I used in my first post. Is that just the difference in doing this via a shell command and not? ie, they perform the same action, just from a different starting point?
As for the Eris file, I did download that and all seems to be OK right now.
Sorry ahead of time for a possibly stupid question but I just wanted to be sure. Do you have to be rooted to do this fix?
Yes, it requires an edit to a file that you can only be edited when rooted
elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
This works for me...thanks!
OP has been updated with original build.prop
Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input
will2live said:
Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input
Click to expand...
Click to collapse
Just use the non-stagefright one.
Just like the post says, stagefright breaks HD video playback for SOME people. However some people dont care and just want higher quadrant scores, so they use the stagefright=true build.prop
Use the =false version for better stability.
Thanks for the reply.
Hello Everyone,
So I unfroze all of my apps in Titanium Backup and flashed the OTA that is posted in the development forum for the Droid 3 and it seems to have worked great other than one small problem. Every time I try to use the camera or camcorder they will open for about 2-3 seconds and then they close and I end up back at my home screen. Does anyone have any ideas on what I can try to make my camera apps work again?
EDIT: Sorry, forgot to mention that I did try rebooting the phone as well as clearing the cache for the camera app, no change. Also Camera Zoom FX stays open but just has black where the camera image would normally be.
Thanks!
Maybe you... forgot to unfreeze the camera app lol.
No but id check what you do have frozen, maybe there's a service the camera app is dependent upon you might have accidentally frozen (assuming you rerooted after update)
Sent from my DROID3 using Tapatalk
I did re-root after applying the OTA update and then I froze about 15 apps that I found to be annoying/un-needed, however even after unfreezing all of them, any app involving the camera still isn't working. I also just noticed that my flashlight app that worked before the OTA is not working either.
First thing I would try is "clear data" for the Camera app and reboot.
rtbrjason said:
First thing I would try is "clear data" for the Camera app and reboot.
Click to expand...
Click to collapse
Tried that a couple of times but no change. I just also noticed that the camera app flashes a small message up at the bottom of the screen really quickly stating that the camera is unable to initialize.
Uninstall any third-party app that uses the camera (if you have any) the try again.
kishin14 said:
Uninstall any third-party app that uses the camera (if you have any) the try again.
Click to expand...
Click to collapse
Thank you for the suggestion, I hadn't thought of that. Unfortunately that did not work either. No change, still getting the same message for about a second or two and then it closes.
Try re-uploading the camera apk and odex files, might need to set permissions the same as the other system apps.
Unzip and use something like rootexplorer, delete current BlurCamera.apk and BlurCamera.odex, set write access on system/app folder then copy these.
-smc
The problem is the camera firmware, amongst other things, is first deleted and then replaced during the OTA update - if something happens, that firmware is never copied back causing the camera to fail.
The problem I had was too much stuff installed in /system and it simply ran out of space. This also caused my recovery to fail to update which then failed checksum if I tried to boot to recovery.
I had a bunch of binaries I installed in /system/xbin taking up several MB of space. I deleted them - including busybox - and reran the update. Now everything works fine.
If your recovery is hosed, I posted how to fix in the update thread.
If you need help and haven't wiped /cache yet, post /cache/recovery/last_log
limaxray said:
The problem is the camera firmware, amongst other things, is first deleted and then replaced during the OTA update - if something happens, that firmware is never copied back causing the camera to fail.
The problem I had was too much stuff installed in /system and it simply ran out of space. This also caused my recovery to fail to update which then failed checksum if I tried to boot to recovery.
I had a bunch of binaries I installed in /system/xbin taking up several MB of space. I deleted them - including busybox - and reran the update. Now everything works fine.
If your recovery is hosed, I posted how to fix in the update thread.
If you need help and haven't wiped /cache yet, post /cache/recovery/last_log
Click to expand...
Click to collapse
also, one note, i'm seeing alot of people reporting issues with the stock apps AFTER they've removed bloat (any method). the first thing people should do is put the bloat back, or in worse case scenario, do a wipe to see if there's really something wrong.
i froze an email service and it cause my text messenger to stop working. you don't know what libraries are shared with what. freeze with caution.
640k said:
also, one note, i'm seeing alot of people reporting issues with the stock apps AFTER they've removed bloat (any method). the first thing people should do is put the bloat back, or in worse case scenario, do a wipe to see if there's really something wrong.
i froze an email service and it cause my text messenger to stop working. you don't know what libraries are shared with what. freeze with caution.
Click to expand...
Click to collapse
I agree, and would suggest to anyone to use the script for removing and replacing the bloat - it makes it much easier to do (especially from adb when you foul it up) and keeps track of what you've done.
That said, I highly doubt that is the issue here. The update script first checksums everything that needs to be patched and deletes everything that is to be replaced. So if you have anything removed, it will either cause it to fail (if the file is to be patched) or not matter (if it is to be deleted or simply isn't touched). In other words, if you have anything missing that is needed, the update wouldn't touch anything.
Furthermore, I don't think any of the commonly removed bloatware serves as a dependency for the camera. At least not as far as I can tell.
I can tell you that /system is filled to the brim with all of the bloatware. The current ROM is just barely shoehorned in there. Many 'for-root-users' apps like to install stuff to /system and since the updater script doesn't check for free space, it may very well fail to extract in the middle of execution even though it already deleted a bunch of files.
So I think more importantly than restoring bloat, you should remove anything you added.
I tried your directions and re-ran the update after fixing recovery, however my camera still doesn't work because of the same basic issue, running out of space before the update completed. Upon re-rooting and going in to my system directory with root explorer I noticed that I now only have 195k free there. I checked the xbin folder and do not see busybox or anything else there that I recognize that I could delete to free up space. How can I tell what is safe to delete and what isn't so I can free up enough to fix my recovery again and hopefully get the update to work properly?
You can see a breakdown of disk usage with this command:
Code:
du -sh /system/*
Here's mine with busybox removed:
Code:
147.6M /system/app
7.5M /system/bin
11.0K /system/build.prop
5.5M /system/etc
5.1M /system/fonts
35.5M /system/framework
75.7M /system/lib
1.0K /system/lost+found
19.2M /system/media
0 /system/preinstall
304.0K /system/recovery-from-boot.p
4.6M /system/tts
8.3M /system/usr
135.0K /system/xbin
And my free space is
Code:
$ df /system
Filesystem Size Used Free Blksize
/system 320M 317M 2M 1024
Other than su, the only files you need in xbin are (don't worry about the symlinks)
Code:
backup dexdump drm1_func_test run_backup run_restore ssmgrd
I think the only extra bits I now have on /system is su.
I also found the system dump from this post to be very helpful.
Whenever I'm trying du It's saying that the command wasn't found. What are you using for your terminal access?
Hmm it seems du isn't a standard binary even though I have it in bin. I sure don't remember putting that in there...
Anyway, I use adb or Better Terminal Emulator Pro, depending what mood on in.
To use adb, you'll need to install busybox to /data somewhere (I have mine in /data/local/bin) and use
Code:
$ /data/local/bin/busybox du -sh /system/*
BTEP has a fairly complete set of CLI tools included - such as du - so you don't need busybox.
I figured out how to do the command through busybox and have come up with some interesting results...
I am over yours on...
Code:
153.8M /system/app
1.9M /system/xbin
I am under yours on...
Code:
4.7M /system/bin
4.9M /system/etc
71.8M /system/lib
And I match yours on...
Code:
11.0K /system/build.prop
5.1M /system/fonts
35.5M /system/framework
1.0K /system/lost+found
19.2M /system/media
0 /system/preinstall
304.0K /system/recovery-from-boot.p
4.6M /system/tts
8.3M /system/usr
This is with busybox installed in the xbin folder so that is probably why I am over on that one, however the app folder is quite a bit over as well but I can't figure out why. The only file that I can find in there that doesn't seem to belong is Superuser.apk but it is only 191k.
UPDATE: I finally found a large app that wasn't present in the system dump that you had mentioned before. I backed it up to my sd card and removed it, went through the update, and now my camera is working. Thank you very much to everyone who helped, especially limaxray!
Glad I was able to help!
This is a great example for why we should always wipe data/cache before any rom update.
dsw361 said:
This is a great example for why we should always wipe data/cache before any rom update.
Click to expand...
Click to collapse
That wouldn't have helped here at all. If anything, it would have made it impossible to use adb in case of a boot loop.
These are not like community ROM updates and don't need anything wiped.
limaxray said:
That wouldn't have helped here at all. If anything, it would have made it impossible to use adb in case of a boot loop.
These are not like community ROM updates and don't need anything wiped.
Click to expand...
Click to collapse
Exactly. the last thing I would do is wipe data/cache if we encountered a bootloop. Adb is so important to us right now because we don't have a custom recovery or an sbf.
Sent from my DROID3 using Tapatalk
DXMD3 Stock Jelly Bean Phabletized!
DISCLAIMER TIME:
First thing's first: I am not a chef, nor am I a developer of any sort. This was just an experiment and it worked. All I'm doing is sharing the results and the method of achieving them.
Also, I am in no way responsible if you mess up your device. That said, these modifications are mostly harmless and reversible, if you follow the instructions to the letter. (Worst case scenario: You flash stock JB again or restore a nand backup and you're safe.)
Oh and your device must be rooted. You can't go around changing things if it's not.
I do need a bit of help with some things, you can read the help wanted section at the bottom of the post,
If you're still interested, read on.
INTRO SPEECH:
I've always wanted the phablet experience on my 7.7, but all of the roms I've tried had imperfections (if ever so slight). If any developers are reading this, please do not take this as an insult. Your roms are wonderful masterpieces. I admit I couldn't even begin to understand how much knowledge and hard work is poured into them. I just wanted a 100% daily driver to have and to hold, meaning as few updates as possible (oh the irony). The closest I could find to a perfect rom was the PAC rom by @daniel_hk, but it always started acting out after a couple of weeks. Might have also been my apps or a combination of apps that did this, I don't know. The customization options on PAC are… It's simply amazing. If you're up for it, do check it out in the development thread. Out of all the roms I've tried, I liked PAC the best. That was a message from our (non)sponsors (my personal opinion). Then I tried E-Robot, which is almost stock – I'd say it's a Note 8 rom modified for our 7.7. But it still didn't feel right. I went back to the stock JB rom and started thinking I could simply alter build.prop's dpi setting and get phablet on stock JB. I was half-right. I did alter it and got phablet mode, but a lot of apps stopped working, a few of them crucial (phone, contacts, …). So I started replacing those apps with apps from the E-Robot rom. And it worked. I've identified and replaced most of the apps and the rom is very smooth. I dare say it's even smoother than E-Robot.
List of apps that need replacing:
- Accuweather
- Most mini apps
- Pen memo
- Camera
- Gallery
- Calculator
- S Planner / Calendar
- Phone
- Contacts
- TouchWiz Launcher
- Task manager
- Memo (text memo)
List of apps I haven't yet found replacements for (HELP WANTED, see below):
- Samsung keyboard
- Reader's hub
APPS YOU'LL NEED:
I like ES File Explorer the most, you can use other file managers if you like. LINK
I find it easiest to flash roms with Mobile ODIN. LINK
If you're not interested in purchasing Mobile Odin, you can look it up on XDA forums. It's available for free.
7zip. You'll need to unzip the package. LINK
APP SUBSTITUTION PACKAGE:
LINK
Please, do not mirror this as these instructions are not yet 100% complete.
INSTRUCTIONS:
Read first. Then apply.
1) Get the stock DXMD3 Jelly Bean on www.samfirmware.com
2) I can't stress this enough: Back up all of your files on your internal storage. All of them. I will not be blamed for the loss your lolcat collection.
3) Flash it with Mobile Odin and choose to root the rom and inject superuser
4) A custom recovery is probably a good idea. Use either CWM or TWRP and make a full system backup. Just in case. Easiest to flash with Odin.
5) Unzip the "PHABLETIZE!" package to your tablet internal storage.
6) Default home to a custom launcher. Just in case. I used Apex. (You'll be replacing TouchWiz, remember?) Also, Install a custom keyboard. The stock keyboard isn't happy with 213dpi. I use Jelly Bean Keyboard.
7) Turn on "Root Explorer" mode in ES File Explorer (side menu, accessible from the top left bluish globe icon)
7a) Alternatively, you can use LCDDensity from Play. I haven't tested this personally. This is a recommendation from obbeguin. Skip step 8.
8) Make a backup of your build.prop file. Edit the build.prop to be used by the system (/system/build.prop): "ro.sf.lcd_density=160" changed to "ro.sf.lcd_density=213" (the one between rild.libargs and ro.lcd_brightness)
9) Restart and marvel at the half-finished glory of phablet mode.
10) Here is where you would see TouchWiz crash and you'd be stuck if you hadn't defaulted to a custom launcher in step 6. Luckily, you did.
11) Open ES, navigate to /system/app/ and start replacing the apps from the package. Yes, manually. I don't know how to make a CWM flashable package, so again, yes, manually. (HELP WANTED) I'd also recommend backing up the original files (just copy them to a backup folder on your storage). All apps should replace just fine, since they crash when launched anyway. You should also backup and delete their odex counterparts. Do not replace those.
12) I haven't included the camera and gallery apks. The gallery wasn't working well and I found a replacement here. Not sure yet if I can hijack his files to use in my zip so I'm posting a link for the time being. Also, I've found I like the SGS4 dialer and messaging app much better than the tablet apps from Note8. Look for it here.
13) Restart
14) If you have any issues with any of the apps, first try clearing their caches and data or wiping dalvik cache and cache in recovery mode.
I'd also recommend SkyHigh's custom kernel. I like it and it allows me to use ExFat on my external SD card. It's no NTFS, but large files (>4GB) get across just fine and it works on my computer and in my tablet without a hitch.
And for that extra "Startled Android" effect, I went with Xposed framework and per-app dpi settings. Not quite paranoid but does the job ok.
If you like the Samsung keyboard, you might want to give this one a go. Suggested by @stenny
HELP WANTED SECTION:
As written before, I need some help. It would be tons easier to just flash a CWM package over the stock JB and get phablet mode. Trouble is, I can't build it. Getting around to this one. Got around to it. Now I'm having scripting problems. If anyone is script savvy, please check out the code below.
I have no clue where to find a replacement Reader's hub app – one that works on 213dpi instead of 160dpi If anyone knows where I could find it, please leave a comment.
Don't hesitate to leave your feedback in the comments.
Unhide to see the script code.
#!/sbin/sh
# remove old backup
[ -d /sdcard/phabletize/backup ] && rm -r /sdcard/phabletize/backup
# backing up original apk
echo "Backing up /system/app/"
busybox mkdir -p /sdcard/phabletize/backup/system/app
busybox mkdir -p /sdcard/phabletize/system/app
cd /sdcard/phabletize/list/
for f in $(ls)
do
echo "Processing $f"
busybox cp /system/app/$f /sdcard/phabletize/backup/system/app/
busybox rm /system/app/$f
done
echo "Backups done for system apps"
# backing up original build.prop
echo "Backing up /system/build.prop"
cp /system/build.prop /sdcard/phabletize/backup/system/build.prop
echo "Backup done for build.prop"
# delete odex files and old apk files
echo "Deleting original odex and apk files from /system/app"
cd /sdcard/phabletize/list
for f in $(ls)
do
echo "Processing $f"
busybox rm /system/app/$f
done
echo "Original odex and apk files deleted. Don't worry. You still have your backup."
# for each of the system apps needing processed
echo "Copying modified apks to /system/app"
cd /sdcard/phabletize/system/app
cp -p * /system/app
echo "Finished copying modified apks"
# copy modified build.prop
echo "Copying modified build.prop to /system"
cd /sdcard/phabletize/system
cp -p build.prop /system
echo "Finished copying modified build.prop"
# the end
echo "All done. Enjoy you Phabletized 7.7 JB"
The above left my tablet in a bootloop stuck on the bootanimation turned landscape and distorted/stretched. I was trying to accomplish the following: back up the original apks and build.prop file to a folder on the sdcard. The list of apks needing backups would be determined from the list of apks in the replacement folder. And copying the replacement apks and build.prop file to the proper folder in /system.
I hope I've proofread this enough times so that it's decent...
Screenshots:
They're big. There are many, Unhide to see.
Mostly just showing off the Samsung apps. From my experience, most apps are a lot easier to handle on a bigger dpi. Again, if on some apps you don't like the change...go with Xposed framework.
Undoubtedly you'll notice how the fonts in the Settings app seem smaller than the rest of the rom and the alarm clock app seems bigger. You're right. They are. That's Xposed + App settings hard at work. I want the alarm clock buttons big when I'm smacking the **** out of my tab in the morning (300dpi) and don't need the big fonts when I'm fiddling with the settings (160dpi).
By the way, don't mind the "25% brightness" (I had it at -28% on some other screenshot). That's just Lux. It helps keep the display at a comfortable level in the dark. A screen filter basically. I also found this and this very helpful on a big screen and fiddly-sometimes-hard-to-press-when-your-hands-are-messy-when-cooking-and-just-need-to-look-at-the-recipe-one-more-time buttons (the other two persistent notifications).
Coming soon: Flashable zip. I'll get around to it, I promise. Having trouble scripting the thing. Take a look at the help wanted section if you think you can help. Thanks.
It is wonderful seeing someone try to create something for our Tablets...
I wish I could help in your efforts but instead I can only thank and applause you...
Good luck...
actually... e-robot doing the same thing that you're doing... replacing the apk from note 8.0 to 7.7 but they did alter some apk to fit their mod.
btw. you can use the keyboard from e-robot as well. but you need to find all related lib files to make it work on 7.7
Conserning cwm flashable zips... I don't know the syntax either. But I just use a zip from gapps and delete all the contents and modify the outputted text. Don't use a zip from a rom because they often wipe stuff.
Sent from my GT-p6800 using xda app-developers app
Lemme start by giving you a well deserved thanks and excellent job.
Can you maybe post a few screenshots and maybe even a video of you have time?
Sent from my GT-P6800 using xda app-developers app
zip
You can use the app "app2zip". It shows you all installed apps, then you choose yours from your pack and
click create. This zip file is then flashable in the recovery.
edan1979 said:
actually... e-robot doing the same thing that you're doing... replacing the apk from note 8.0 to 7.7 but they did alter some apk to fit their mod.
btw. you can use the keyboard from e-robot as well. but you need to find all related lib files to make it work on 7.7
Click to expand...
Click to collapse
Doesn't e-robot have some issues? I got the distinct feeling it wasn't quite so stock. I might be wrong though.
EDIT: Now I remember! I couldn't get over the flickering wifi icon in the status bar. Annoyed the **** out of me. Trivial, I know. I could live with something not working quite right if it wasn't visible most of the time.
{Diemex} said:
Conserning cwm flashable zips... I don't know the syntax either. But I just use a zip from gapps and delete all the contents and modify the outputted text. Don't use a zip from a rom because they often wipe stuff.
Sent from my GT-p6800 using xda app-developers app
Click to expand...
Click to collapse
Good tip. Thanks!
vivalamoza said:
Lemme start by giving you a well deserved thanks and excellent job.
Can you maybe post a few screenshots and maybe even a video of you have time?
Sent from my GT-P6800 using xda app-developers app
Click to expand...
Click to collapse
I'll take some and post asap.
konsolen said:
You can use the app "app2zip". It shows you all installed apps, then you choose yours from your pack and
click create. This zip file is then flashable in the recovery.
Click to expand...
Click to collapse
Can this create a single zip for multiple apps or is it one app = one zip?
It creates one ZIP file. So exactly what you looking for.
Just a quick update:
I'm working on a cwm flashable zip that would back up the original apk and odex files and copy the new ones in place. Plus, I've been toying around with other versions of system apps.
I will be posting everything in the next few days - after I test it out.
Cheers
paranoiadk said:
DXMD3 Stock Jelly Bean Phabletized!
INSTRUCTIONS:
Read first. Then apply.
1) Get the stock DXMD3 Jelly Bean on www.samfirmware.com
2) I can't stress this enough: Back up all of your files on your internal storage. All of them. I will not be blamed for the loss your lolcat collection.
3) Flash it with Mobile Odin and choose to root the rom and inject superuser
4) A custom recovery is probably a good idea. Use either CWM or TWRP and make a full system backup. Just in case. Easiest to flash with Odin.
5) Unzip the "PHABLETIZE!" package to your tablet internal storage.
6) Default home to a custom launcher. Just in case. I used Apex. (You'll be replacing TouchWiz, remember?) Also, Install a custom keyboard. The stock keyboard isn't happy with 213dpi. I use Jelly Bean Keyboard.
7) Turn on "Root Explorer" mode in ES File Explorer (side menu, accessible from the top left bluish globe icon)
8) Make a backup of your build.prop file. Edit the build.prop to be used by the system (/system/build.prop): "ro.sf.lcd_density=160" changed to "ro.sf.lcd_density=213" (the one between rild.libargs and ro.lcd_brightness)
9) Restart and marvel at the half-finished glory of phablet mode.
10) Here is where you would see TouchWiz crash and you'd be stuck if you hadn't defaulted to a custom launcher in step 6. Luckily, you did.
11) Open ES, navigate to /system/app/ and start replacing the apps from the package. Yes, manually. I don't know how to make a CWM flashable package, so again, yes, manually. (HELP WANTED) I'd also recommend backing up the original files (just copy them to a backup folder on your storage). All apps should replace just fine, since they crash when launched anyway. You should also backup and delete their odex counterparts. Do not replace those.
12) Restart
13) If you have any issues with any of the apps, first try clearing their caches and data.
Click to expand...
Click to collapse
Concerning the point 7 & 8, wouldnt it be easier to just use LCDDensity for root ?
Using it, it is must more easy to change the density without even having to manually modify the build.prop file... And the phablet mod start for any density higher than 180..
And for people who forgot to install a second launcher, they no need to panic..
They can still go to the tablet settings using the notification bar, even if Touchwiz doesnt work.
There, they can check they are connected to internet and install a second launcher by logging on google play by using a PC.
obeguin said:
Concerning the point 7 & 8, wouldnt it be easier to just use LCDDensity for root ?
Using it, it is must more easy to change the density without even having to manually modify the build.prop file... And the phablet mod start for any density higher than 180..
And for people who forgot to install a second launcher, they no need to panic..
They can still go to the tablet settings using the notification bar, even if Touchwiz doesnt work.
There, they can check they are connected to internet and install a second launcher by logging on google play by using a PC.
Click to expand...
Click to collapse
Never heard of LCDDensity before, but I'll add it to the instructions.
You're correct, the phablet ui starts at 180 (176 I believe), but the navigation bar keys are off center when lcd density is not set to 213.
Sort of defeats the purpose of phablet ui for me. Personally, I changed to a smaller dpi (for a smaller status bar - 195) and removed the navigation bar with the qemu.hw.mainkeys switch. I mainly navigate thru gestures (using GMD Gesture Control) anyway.
Again, you're correct. But when starting out on a freshly flashed rom, some might happen to skip the part where they connect to the wifi or connect their google account. Besides, I've seen Play being hesitant to install and update on it's own - sometimes it requires you to launch it before you get update notifications and automated app downloads which requires a launcher. I want the instructions to be as foolproof as possible. That's why I'll be making a separate flashable zip with a custom home and keyboard, just in case.
On that topic, do you know anything about scripting? I'm having trouble with the update script. Check out the first post.
You can try this note 8 samsung keyboard, it work on both tablet and phablet ui.
http://forum.xda-developers.com/showthread.php?t=2228836
Sent from my GT-P6800 using XDA Premium 4 mobile app
paranoiadk said:
DXMD3 Stock Jelly Bean Phabletized!
DISCLAIMER TIME:
First thing's first: I am not a chef, nor am I a developer of any sort. This was just an experiment and it worked. All I'm doing is sharing the results and the method of achieving them.
Also, I am in no way responsible if you mess up your device. That said, these modifications are mostly harmless and reversible, if you follow the instructions to the letter. (Worst case scenario: You flash stock JB again or restore a nand backup and you're safe.)
Oh and your device must be rooted. You can't go around changing things if it's not.
I do need a bit of help with some things, you can read the help wanted section at the bottom of the post,
If you're still interested, read on.
INTRO SPEECH:
I've always wanted the phablet experience on my 7.7, but all of the roms I've tried had imperfections (if ever so slight). If any developers are reading this, please do not take this as an insult. Your roms are wonderful masterpieces. I admit I couldn't even begin to understand how much knowledge and hard work is poured into them. I just wanted a 100% daily driver to have and to hold, meaning as few updates as possible (oh the irony). The closest I could find to a perfect rom was the PAC rom by @daniel_hk, but it always started acting out after a couple of weeks. Might have also been my apps or a combination of apps that did this, I don't know. The customization options on PAC are… It's simply amazing. If you're up for it, do check it out in the development thread. Out of all the roms I've tried, I liked PAC the best. That was a message from our (non)sponsors (my personal opinion). Then I tried E-Robot, which is almost stock – I'd say it's a Note 8 rom modified for our 7.7. But it still didn't feel right. I went back to the stock JB rom and started thinking I could simply alter build.prop's dpi setting and get phablet on stock JB. I was half-right. I did alter it and got phablet mode, but a lot of apps stopped working, a few of them crucial (phone, contacts, …). So I started replacing those apps with apps from the E-Robot rom. And it worked. I've identified and replaced most of the apps and the rom is very smooth. I dare say it's even smoother than E-Robot.
List of apps that need replacing:
- Accuweather
- Most mini apps
- Pen memo
- Camera
- Gallery
- Calculator
- S Planner / Calendar
- Phone
- Contacts
- TouchWiz Launcher
- Task manager
- Memo (text memo)
List of apps I haven't yet found replacements for (HELP WANTED, see below):
- Samsung keyboard
- Reader's hub
APPS YOU'LL NEED:
I like ES File Explorer the most, you can use other file managers if you like. LINK
I find it easiest to flash roms with Mobile ODIN. LINK
If you're not interested in purchasing Mobile Odin, you can look it up on XDA forums. It's available for free.
7zip. You'll need to unzip the package. LINK
APP SUBSTITUTION PACKAGE:
LINK
Please, do not mirror this as these instructions are not yet 100% complete.
INSTRUCTIONS:
Read first. Then apply.
1) Get the stock DXMD3 Jelly Bean on www.samfirmware.com
2) I can't stress this enough: Back up all of your files on your internal storage. All of them. I will not be blamed for the loss your lolcat collection.
3) Flash it with Mobile Odin and choose to root the rom and inject superuser
4) A custom recovery is probably a good idea. Use either CWM or TWRP and make a full system backup. Just in case. Easiest to flash with Odin.
5) Unzip the "PHABLETIZE!" package to your tablet internal storage.
6) Default home to a custom launcher. Just in case. I used Apex. (You'll be replacing TouchWiz, remember?) Also, Install a custom keyboard. The stock keyboard isn't happy with 213dpi. I use Jelly Bean Keyboard.
7) Turn on "Root Explorer" mode in ES File Explorer (side menu, accessible from the top left bluish globe icon)
7a) Alternatively, you can use LCDDensity from Play. I haven't tested this personally. This is a recommendation from obbeguin. Skip step 8.
8) Make a backup of your build.prop file. Edit the build.prop to be used by the system (/system/build.prop): "ro.sf.lcd_density=160" changed to "ro.sf.lcd_density=213" (the one between rild.libargs and ro.lcd_brightness)
9) Restart and marvel at the half-finished glory of phablet mode.
10) Here is where you would see TouchWiz crash and you'd be stuck if you hadn't defaulted to a custom launcher in step 6. Luckily, you did.
11) Open ES, navigate to /system/app/ and start replacing the apps from the package. Yes, manually. I don't know how to make a CWM flashable package, so again, yes, manually. (HELP WANTED) I'd also recommend backing up the original files (just copy them to a backup folder on your storage). All apps should replace just fine, since they crash when launched anyway. You should also backup and delete their odex counterparts. Do not replace those.
12) I haven't included the camera and gallery apks. The gallery wasn't working well and I found a replacement here. Not sure yet if I can hijack his files to use in my zip so I'm posting a link for the time being. Also, I've found I like the SGS4 dialer and messaging app much better than the tablet apps from Note8. Look for it here.
13) Restart
14) If you have any issues with any of the apps, first try clearing their caches and data or wiping dalvik cache and cache in recovery mode.
I'd also recommend SkyHigh's custom kernel. I like it and it allows me to use ExFat on my external SD card. It's no NTFS, but large files (>4GB) get across just fine and it works on my computer and in my tablet without a hitch.
And for that extra "Startled Android" effect, I went with Xposed framework and per-app dpi settings. Not quite paranoid but does the job ok.
If you like the Samsung keyboard, you might want to give this one a go. Suggested by @stenny
HELP WANTED SECTION:
As written before, I need some help. It would be tons easier to just flash a CWM package over the stock JB and get phablet mode. Trouble is, I can't build it. Getting around to this one. Got around to it. Now I'm having scripting problems. If anyone is script savvy, please check out the code below.
I have no clue where to find a replacement Reader's hub app – one that works on 213dpi instead of 160dpi If anyone knows where I could find it, please leave a comment.
Don't hesitate to leave your feedback in the comments.
Unhide to see the script code.
#!/sbin/sh
# remove old backup
[ -d /sdcard/phabletize/backup ] && rm -r /sdcard/phabletize/backup
# backing up original apk
echo "Backing up /system/app/"
busybox mkdir -p /sdcard/phabletize/backup/system/app
busybox mkdir -p /sdcard/phabletize/system/app
cd /sdcard/phabletize/list/
for f in $(ls)
do
echo "Processing $f"
busybox cp /system/app/$f /sdcard/phabletize/backup/system/app/
busybox rm /system/app/$f
done
echo "Backups done for system apps"
# backing up original build.prop
echo "Backing up /system/build.prop"
cp /system/build.prop /sdcard/phabletize/backup/system/build.prop
echo "Backup done for build.prop"
# delete odex files and old apk files
echo "Deleting original odex and apk files from /system/app"
cd /sdcard/phabletize/list
for f in $(ls)
do
echo "Processing $f"
busybox rm /system/app/$f
done
echo "Original odex and apk files deleted. Don't worry. You still have your backup."
# for each of the system apps needing processed
echo "Copying modified apks to /system/app"
cd /sdcard/phabletize/system/app
cp -p * /system/app
echo "Finished copying modified apks"
# copy modified build.prop
echo "Copying modified build.prop to /system"
cd /sdcard/phabletize/system
cp -p build.prop /system
echo "Finished copying modified build.prop"
# the end
echo "All done. Enjoy you Phabletized 7.7 JB"
The above left my tablet in a bootloop stuck on the bootanimation turned landscape and distorted/stretched. I was trying to accomplish the following: back up the original apks and build.prop file to a folder on the sdcard. The list of apks needing backups would be determined from the list of apks in the replacement folder. And copying the replacement apks and build.prop file to the proper folder in /system.
I hope I've proofread this enough times so that it's decent...
Click to expand...
Click to collapse
Didn't work for me, lots of apps couldn't be pasted in system/app even after R/W, I even tried to do it in TWRP and it still failed
vivalamoza said:
Didn't work for me, lots of apps couldn't be pasted in system/app even after R/W, I even tried to do it in TWRP and it still failed
Click to expand...
Click to collapse
My suggestions:
You sure you're rooted?
You might have free space issues. Try disabling and uninstalling the apps from titanium backup and then pasting the apps in place. Samsung roms are pretty huge and fill the available space almost to the limit.
Pasting sometimes didn't work for me when the apps were running. Try closing them from a task manager. I always did the modding after a fresh boot on a fresh rom.
I hope this is helpful.
Hi everyone
I'm trying to get the infamous GPS Location Spoofer installed as a system app on my rooted HTC phone, but so far no luck, so I figured I would try to ask for help here, in case anyone went through a similar situation, or knows what I've been doing wrong. This is what I tried so far:
Installed the app from Google App store, and using File Explorer with root , tried to move the app folder to /system/app or /system/priv-app, , but pasting the folder there would result in an instant reboot and the app would not be there.
So I installed lucky patcher , and using apk downloader, downloaded the apk file from the App Store, copied it over to the phone, and used the "Rebuild and Install" option, choosing the option to install it as a system app , and it would process it and say that the installation was sucessfull, needs to reboot to complete, but after the reboot the app would not be there (not only not showing on the apps list, but navigating to the /system folder with File Explorer and checking app and priv-app I could verify that it was not installed).
SO I tried to use adb shell to do the work , and this is what I did:
mount -o remount /dev/block/mmcblk0p35 /system
to mount the /system filesystem as read write , and it did
cp /sdcard/Download/com.incorporateapps.fakegps.fre-55.apk /system/app
to copy the file under /system/app
chmod 644 com.incorporateapps.fakegps.fre-55.apk
to set the permissions as required
and reboot the phone, but after the reboot, the file would not be there. I tried also to create a folder under /system/app named com.incorporateapps.fakegps.fre-55, move the apk inside; installing normally , changing the mount point to read-write and moving it from /data/app to /system/app or /system/priv-app using the shell and chaning ownership / permissions , but the app will not stick , either rebooting or just re-mounting the filesystem as read-only again will cause everything that was done to be lost; and after trying any of the above one time, doing it for a second time would cause the phone to reboot.
I figure that there must be an image of the /system mount point somewhere , which gets installed every time there is a remount to read-only or reboot , or something of that nature, that will cause any changes made under /system to be lost. Maybe I'm wrong but it seems to be related to HTC phones, since there's load of people doing it on other models without issues, or maybe I'm doing something wrong, since I'm no android expert
Does anyone knows what could be the issue, or what can I do ? I searched the net quite a bit for a solution to no avail (here as well), any help is appreciated
Thanks
sasteck said:
Hi everyone
I'm trying to get the infamous GPS Location Spoofer installed as a system app on my rooted HTC phone, but so far no luck, so I figured I would try to ask for help here, in case anyone went through a similar situation, or knows what I've been doing wrong. This is what I tried so far:
Installed the app from Google App store, and using File Explorer with root , tried to move the app folder to /system/app or /system/priv-app, , but pasting the folder there would result in an instant reboot and the app would not be there.
So I installed lucky patcher , and using apk downloader, downloaded the apk file from the App Store, copied it over to the phone, and used the "Rebuild and Install" option, choosing the option to install it as a system app , and it would process it and say that the installation was sucessfull, needs to reboot to complete, but after the reboot the app would not be there (not only not showing on the apps list, but navigating to the /system folder with File Explorer and checking app and priv-app I could verify that it was not installed).
SO I tried to use adb shell to do the work , and this is what I did:
mount -o remount /dev/block/mmcblk0p35 /system
to mount the /system filesystem as read write , and it did
cp /sdcard/Download/com.incorporateapps.fakegps.fre-55.apk /system/app
to copy the file under /system/app
chmod 644 com.incorporateapps.fakegps.fre-55.apk
to set the permissions as required
and reboot the phone, but after the reboot, the file would not be there. I tried also to create a folder under /system/app named com.incorporateapps.fakegps.fre-55, move the apk inside; installing normally , changing the mount point to read-write and moving it from /data/app to /system/app or /system/priv-app using the shell and chaning ownership / permissions , but the app will not stick , either rebooting or just re-mounting the filesystem as read-only again will cause everything that was done to be lost; and after trying any of the above one time, doing it for a second time would cause the phone to reboot.
I figure that there must be an image of the /system mount point somewhere , which gets installed every time there is a remount to read-only or reboot , or something of that nature, that will cause any changes made under /system to be lost. Maybe I'm wrong but it seems to be related to HTC phones, since there's load of people doing it on other models without issues, or maybe I'm doing something wrong, since I'm no android expert
Does anyone knows what could be the issue, or what can I do ? I searched the net quite a bit for a solution to no avail (here as well), any help is appreciated
Thanks
Click to expand...
Click to collapse
Are you using stock kernel?
donkeykong1 said:
Are you using stock kernel?
Click to expand...
Click to collapse
Yes, kernel is the default that comes with the phone (3.4.10.g96cae32 , android 5.0.2)
sasteck said:
Yes, kernel is the default that comes with the phone (3.4.10.g96cae32 , android 5.0.2)
Click to expand...
Click to collapse
And there's your problem. Stock kernel has system write protection, so you can't mount system as writeable. You can, but after reboot, it comes back to read only, and nothing will stick into system partition. You have 2 choices now - disable system write protection on stock kernel, or flash a custom kernel
donkeykong1 said:
And there's your problem. Stock kernel has system write protection, so you can't mount system as writeable. You can, but after reboot, it comes back to read only, and nothing will stick into system partition. You have 2 choices now - disable system write protection on stock kernel, or flash a custom kernel
Click to expand...
Click to collapse
oh I see.. didn't know about that , thanks! I'll check about disabling system write protection , otherwise look for a custom kernel, never did it before but will give it a try
donkeykong1 said:
And there's your problem. Stock kernel has system write protection, so you can't mount system as writeable. You can, but after reboot, it comes back to read only, and nothing will stick into system partition. You have 2 choices now - disable system write protection on stock kernel, or flash a custom kernel
Click to expand...
Click to collapse
Shhhhhh, don't help him, he's going to steal everyone's pokemons
Sent from my HTC One using XDA Labs
alray said:
Shhhhhh, don't help him, he's going to steal everyone's pokemons
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
Ooooohhh... That's why he's trying the spoofer.... If I knew, I wouldn't help at all [emoji6]
donkeykong1 said:
Ooooohhh... That's why he's trying the spoofer.... If I knew, I wouldn't help at all [emoji6]
Click to expand...
Click to collapse
Sorry you feel that way, but I appreciate the help anyway. This is something that I never tampered with before, so I still had some doubts about the process, but I am liking the whole thing and will install a custom rom on my own phone, been reading about the Ressurection rom and it looks very nice, will try it as soon as I'm better informed
sasteck said:
Sorry you feel that way, but I appreciate the help anyway. This is something that I never tampered with before, so I still had some doubts about the process, but I am liking the whole thing and will install a custom rom on my own phone, been reading about the Ressurection rom and it looks very nice, will try it as soon as I'm better informed
Click to expand...
Click to collapse
That was a joke mate. I don't care what you do with your phone, but I'm here to help if I can [emoji6]