Related
This is just a simple build.prop mod to fix the fingerprint back to the working ERE27 one used in CM. Everything in Settings still shows FroYo, but the Market sees you as ERE27 & thus gives you your protected apps back
To install run this from the directory you unzip the file to:
ADB Method:
Code:
adb remount
adb shell rm /system/build.prop
adb push froyo.prop /system/build.prop
adb shell reboot
Then, once it reboots, go into the dialer, and type
Code:
*#*#CHECKIN#*#*
which is
Code:
*#*#2432546#*#*
for those of you who are too lazy to read the letters
A message should pop up into the status bar after a few seconds depending on your connection speed saying checkin succeeded.
Now you're good to go, open Market and download away
EDIT: Since I know some of you will wonder what this does, it just changes the ro.build.fingerprint & ro.build.description settings back to ERE27. This alone would normally be enough, but you're depending on luck to when you next check in. Dialing that code in the Dialer will force a checkin.
EDIT 2: Thanks to Shafty023 here is a method for the shell:
LINUX SHELL METHOD
Copy froyo.zip to /sdcard, then open a Terminal shell on your phone
Code:
su
mount -o remount,rw /system
cd /system
mv build.prop new.build.prop
unzip /sdcard/froyo.zip
mv froyo.prop build.prop
rm /sdcard/froyo.zip
reboot
Upon booting back up, open Dialer and type in the following code
Code:
*#*#2432546#*#*
Once you see a notification in the notification bar that says checkin succeeded you can now open Market and are done.
Nice! Trying it now.
EDIT: Working great so far. Thanks!
athereal said:
Nice! Trying it now.
EDIT: Working great so far. Thanks!
Click to expand...
Click to collapse
testing it in a few minutes too.... [UPDATE: works like a charm!]
Nice job Geniusdog254! really nice
thanks!
Thanks, works great!
Grrr... adb has been broken for me for months. Any way to fix this without adb?
Part Four said:
Grrr... adb has been broken for me for months. Any way to fix this without adb?
Click to expand...
Click to collapse
Use one of the root file explorers to unzip the file, delete the old build.prop, put the new one in, and then type the command in the dialer
Works like a charm, thanks!
Worked great, THANK YOU!!!!!
I'm getting checkin failed. should I have renamed froyo.prop to build.prop?
edit: I'm able to see protected apps though.
So what happens when apps start getting udated to take advantage of JIT? If you have ERE27 signature do you get the JIT'less version of the apps? I know Replica Island is coming with a JIT version. I'm afraid to mess with anything right now, rather be patient and give it a few days.
dudebro said:
I'm getting checkin failed. should I have renamed froyo.prop to build.prop?
edit: I'm able to see protected apps though.
Click to expand...
Click to collapse
If you inserted this line correctly, it renames and places the file in its directory as build.prop
adb push froyo.prop /system/build.prop
Mikey1022 said:
If you inserted this line correctly, it renames and places the file in its directory as build.prop
adb push froyo.prop /system/build.prop
Click to expand...
Click to collapse
yeah, I was wondering if it worked because I was getting checkin failed.
bluehaze said:
So what happens when apps start getting udated to take advantage of JIT? If you have ERE27 signature do you get the JIT'less version of the apps? I know Replica Island is coming with a JIT version. I'm afraid to mess with anything right now, rather be patient and give it a few days.
Click to expand...
Click to collapse
Apps don't have to be updated to take advantage of JIT at all. They can be optimized but they can be optimized without JIT too. There are no different versions. JIT just converts the Java/Dalvik code into native code at app launch, instead of running it through the slower virtual machine. Its like C++ vs Java on a desktop, the native code (C++) is much faster when executed.
The only thing this will lead to is when apps start showing up in the Market as 2.2+ only, but by that point Google will have updated the market to recognize the new footprint.
Can someone give an example of a "Protected" app? If its worth anything, im assuming its paid apps. If so, i can see them without a modded build.prop.
serialtoon said:
Can someone give an example of a "Protected" app? If its worth anything, im assuming its paid apps. If so, i can see them without a modded build.prop.
Click to expand...
Click to collapse
I think Twidroid Pro is protected.
What I'm wondering is, if somebody swaps out the build prop but hasn't installed flash yet, would this block them from doing so?
serialtoon said:
Can someone give an example of a "Protected" app? If its worth anything, im assuming its paid apps. If so, i can see them without a modded build.prop.
Click to expand...
Click to collapse
Pure calender widget (agenda) is a protected app taht doesnt show up in the 2.2 market
Edit: Works perfect! Thanks.
If you are having problems with the checkin, make sure your on 3g and not WiFi.
Mi|enko said:
I think Twidroid Pro is protected.
What I'm wondering is, if somebody swaps out the build prop but hasn't installed flash yet, would this block them from doing so?
Click to expand...
Click to collapse
Nope, Flash still shows up in the Market top apps for me, but I already have it installed. Technically it probably should show up only on the 2.2 Market, but Google may not be able to filter that yet since they haven't enabled the 2.2 fingerprint yet. Just theories here, don't take anything I say too seriously
Also, a perfect example of protected apps is all the Gameloft apps. Search the Market for Gameloft. They won't show up on 2.2 without this, I tried multiple times
Geniusdog254 said:
Nope, Flash still shows up in the Market top apps for me, but I already have it installed. Technically it probably should show up only on the 2.2 Market, but Google may not be able to filter that yet since they haven't enabled the 2.2 fingerprint yet. Just theories here, don't take anything I say too seriously
Also, a perfect example of protected apps is all the Gameloft apps. Search the Market for Gameloft. They won't show up on 2.2 without this, I tried multiple times
Click to expand...
Click to collapse
Yea, im not getting any of the GameLoft games.
serialtoon said:
Yea, im not getting any of the GameLoft games.
Click to expand...
Click to collapse
Even after this?
I have the dlna.apk and the odex file was curious if there was a way to adb it back on the phone.. ( I removed it thinking I wouldn't use it )
I just don't know the commands for adb and if I try and just put them on sd card and install it says it is already installed but I know it is gone cause I removed it via titanium backup.
send it to me and let me see if i can do some work on getting it back on the phone. i took mine off too like you but dont have the dlna.apk
BRANDENDEUCE said:
send it to me and let me see if i can do some work on getting it back on the phone. i took mine off too like you but dont have the dlna.apk
Click to expand...
Click to collapse
http://www.mediafire.com/?hr510y2s9apihuy
Check the ADB threads and/or Root Explorer (it could probably do this too) for the commands.
As a last resort, if you really need it and can't figure it out.. just download the stock ROM in the dev forum and flash/restore it but you'll have to redo the settings so back up data with Titanium Backup.
Dlna.apk AllShare reinstall fail.
I'm using the Vibrant9 Eclair 2.1 rom which has removed Dlna.apk aka AllShare.
Any ideas how to get this reinstalled?
Some of my results.
When I try to install via the Vibrant file browser it I get the usual
"Do you want to install this application"
I click on Install and get
"Application not installed"
Tried to install via adb.
./adb install /SDK/app/Dlna/Dlna.apk
1175 KB/s (787522 bytes in 0.654s)
pkg: /data/local/tmp/Dlna.apk
execv /system/xbin/procrank returned -1
execv /system/xbin/librank returned -1
/mnt/.lfs: Function not implemented
execv /system/bin/parse_radio_log returned -1
[1] Killed pm install /data...
Tried to install while in adb shell, no errors untill reboot, got stuck on splash screen until it ended on a black screen, soft keys lit and stayed lit when I pressed them.
# install /sdcard/Dlna.apk /sdcard/system/app
# reboot
(black screen after splash loop on reboot)(adb shell active, can't gain su access though)
I've failed on trying to get it reinstalled too, anyone knowledgeable enough to fix this?
Bump... trying to get this working on FrankinTwiz...
Works fine on Bionix ROM, wonder whats different
I'm having the same issue. I can't get it to work on FrankinTwiz
Any luck?
I know this is an old thread, but has anyone had any luck at getting the Allshare app reinstalled with custom roms? I've googled to no avail.
u could try creating a .zip file and placing the dlna.apk in systems\app folder and flashing it in CWM.
For example, ur .zip file would look something like this.
C:\customzipfile.zip\system\app\dlna.apk
I havent tried it out though so not sure if it may work. Dont burn down my house if it doesnt. It just seems feasible.
Did you guys ever consider trying Bloater?
I'm trying to install it on my Nexus S, without success. Where should I put the Dlna.odex? When I installed the Dnla.apk, it says "installation succesful", even though it's not. Here's the log:
Code:
D/PackageManager( 332): Scanning package com.sec.android.app.dlna
E/PackageManager( 332): Package com.sec.android.app.dlna requires unavailable shared library touchwiz; failing!
W/PackageManager( 332): Package couldn't be installed in /data/app/com.sec.android.app.dlna-1.apk
I/InstallAppProgress( 7472): Finished installing com.sec.android.app.dlna
You can find the zip here, by the way: http://forum.xda-developers.com/showpost.php?p=7259961&postcount=5
Binary100100 said:
Did you guys ever consider trying Bloater?
Click to expand...
Click to collapse
+1 search and download
Samsung Allshare (DLNA)
pphi said:
I've failed on trying to get it reinstalled too, anyone knowledgeable enough to fix this?
Click to expand...
Click to collapse
Try serendipity7.weebly.com/add-ons . html
Hope this helps...
EDIT: DEAD. Unlock you bootloader and get perm root.
It still uses zergrush and absolutely does not provide any other capability than other temp roots. (Although some people have reported root apps see root better so it might actually be better). The only difference is I have the things relating to root (ie su,busybox, etc) stored in a ramdisk that lasts alot longer than things "written" or linked to /system. This is because we still have /system write locked so when we write things to it (like the original zergrush implementation) it gets forgotten after while.
Your mileage may vary. I am obviously not responsible for bricks, data loss, etc if you use this. I and others have used it for about a week and it has been fine.
To use:
0) Make sure superuser isn't installed
1) Reboot phone (full reboot), make sure usb debugging is on.
2) Plug in phone in charge only mode to PC.
3) Kill everything in the built in task manager, then go back to the rosie home screen.
4) Extract zip and doubleclick temproot.bat
5) There is a 20 second time out at the beginning just in case you forgot to plug in your phone, etc so you have time to cancel the process before it starts. To skip it just hit enter on the keyboard or wait the 20 seconds.
6) Hit the thanks button (bottom left of this post) if you like it!
Let me know if you like it better or if something bad happens so I can take it down. Lets hope we get S-Off soon and don't have to deal with this temp root **** anymore.
Troubleshooting:
1) Bootlooping? Pull the battery. If you still are boot looping, an RUU restore may be necessary. I believe this has only happened to one user and it was likely a result of something that was done AFTER root and not directly caused by this program.
2) Just not working? Reboot both your PC and Phone. If ADB cannot see your phone, it is not a fault of the program. If you haven't gotten other temp root methods to work, it is likely this one won't either.
3) If you want bluetooth to work while you are rooted, turn it on before running this app. It won't toggle on for some reason after the program is run.
Finally, if you want to contribute, thank the Revolutionary team for their work on the zergRush exploit!
ok so let me be the first to ask.... what's "better" about it?
It should stick longer.
has anyone figured out exactly why we lose root within minutes?
So every time we want to use this root again we'll have to uninstall SU first?
You can probably run without but I have always removed it first
ya it worked perfectly thanxs
You have to have drivers installers and such before you do this method? Thing is ny computer broke so I would be using a school computer which restricts me from downloading htc drivers
Sent from my ADR6425LVW using xda premium
The root access is definitely better. I have root access apps that would force reboot my phone before that actually run now. Nice work! It definitely sticks longer.
bast525 said:
has anyone figured out exactly why we lose root within minutes?
Click to expand...
Click to collapse
Since we don't have write access to /system. When the superuser stuff gets "written" to /system it really isn't so it goes away randomly after awhile. This helps to prolong the life of superuser.
NoNotReally said:
So every time we want to use this root again we'll have to uninstall SU first?
Click to expand...
Click to collapse
I am not sure... Try it. If you do I can have the script uninstall before it runs perhaps.
bokechukwu1 said:
You have to have drivers installers and such before you do this method? Thing is ny computer broke so I would be using a school computer which restricts me from downloading htc drivers
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Yes this just is what I think is a better root method. It is the same exploit, it is just stored on the device a bit differently.
mohkg said:
ya it worked perfectly thanxs
Click to expand...
Click to collapse
Good to hear.
flexor224 said:
The root access is definitely better. I have root access apps that would force reboot my phone before that actually run now. Nice work! It definitely sticks longer.
Click to expand...
Click to collapse
Also good to hear.
It has worked to control setcpu profiles for me very well over the past few days so it has stuck for about 72 hours+ for me before I rebooted to retest this script before release.
confirmed, this root is definitely working better. not only lasting longer, but some apps that require root that wouldn't work or wouldn't work fully before are now working. for instance, I have an sql database editor app that was not recognizing root before and wouldn't let me edit databases. works perfectly now. I want to try WiFi tether but do we know if Verizon can detect this now?
also, I'm guessing you're setting some low clock speed with setcpu when asleep/idle... noticing better battery?
Thank you! This works amazingly well. My root actually sticks this time. It doesnt give me a single issue.
Thank you once again!
I have run this script several times now and no worky.
- Installed drivers (no old drivers to conflict)
- fresh reboot, charge only, USB debug, tasks are terminated
- adb sees my device
SU does push to the phone, but apps like TB cannot get root access. Any thoughts folks? I have tried ever one of these temp root methods without success.
plug in your phone for me. Then shift+click on the folder that you extracted the stuff to and do open command prompt here or whatever. Then in there type adb shell and see if you get a shell.
It is likely if you haven't gotten success before this won't help. This is just and improved root, but not an improved way to get it on the device.
con247 said:
plug in your phone for me. Then shift+click on the folder that you extracted the stuff to and do open command prompt here or whatever. Then in there type adb shell and see if you get a shell.
It is likely if you haven't gotten success before this won't help. This is just and improved root, but not an improved way to get it on the device.
Click to expand...
Click to collapse
I have shell con.
My root held overnight. I was able to clear battery stats using Battery Monitor Widget (other temp roots could not), and using CPU Boost to underclock and run a screen off profile.... unfortunately I'm not really noticing any better battery.
Irieone said:
I have run this script several times now and no worky.
- Installed drivers (no old drivers to conflict)
- fresh reboot, charge only, USB debug, tasks are terminated
- adb sees my device
SU does push to the phone, but apps like TB cannot get root access. Any thoughts folks? I have tried ever one of these temp root methods without success.
Click to expand...
Click to collapse
Adb can see your device but still doesn't work..... Post the output from an adb command and maybe we can help.
Sent from my HTC Rezound via the XDA app
Definitely the best temp root method so far!
Already past 24hrs! Past methods would last an hour or so. This is awesome. How did you figure this out? Maybe it'll help those trying to get S-Off? Thanks!
It won't help with perma-root/s-off. I figured a ramdisk wouldn't get killed nearly as fast as the fake /system write does.
I am able to get it to run through now. At the end it tells me it needs to reboot my phone, enjoy root, etc... When the phone reboots. It boot-loops. I have to pull battery.
I was trying to modify build.prop to get Play Store to work which bricked the device. Tried factory reset and now it's totally not being recognized by the computer and ADB not working. Any solution or help.
Android Cowboy said:
I was trying to modify build.prop to get Play Store to work which bricked the device. Tried factory reset and now it's totally not being recognized by the computer and ADB not working. Any solution or help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2491057 Try this. It might at least get recognized in adb and then you can try factory reset in fastboot.
johnnydowngrief said:
http://forum.xda-developers.com/showthread.php?t=2491057 Try this. It might at least get recognized in adb and then you can try factory reset in fastboot.
Click to expand...
Click to collapse
I can't get into the safe mode either. I can get into recovery mode to factory reset but that's it. ADB still not recognized.
Android Cowboy said:
I can't get into the safe mode either. I can get into recovery mode to factory reset but that's it. ADB still not recognized.
Click to expand...
Click to collapse
Then maybe this. http://forum.xda-developers.com/showthread.php?t=1379875 But I'm just guessing here. I dont want to spam this thread. Maybe someone more experienced can help you.
I did same thing. Strange but I COULD finally use adb, but only from the Android SDK base folder & only after uninstalling all devices & using USB deview to remove all adb, mtp & other android related USB devices.
So far, it looks like Amz actually keeps a partial firmware backup on the device, which they can use via mayday when things get really messed up. I would bet, they can also see system mods. It may even function automatically in some instances, I goofed mine pretty bad restore HD system files with TB & after a couple resets, it seemed it restored the system files.
Sent from my Nexus 7 using XDA Premium HD app
GSLEON3 said:
I did same thing. Strange but I COULD finally use adb, but only from the Android SDK base folder & only after uninstalling all devices & using USB deview to remove all adb, mtp & other android related USB devices.
So far, it looks like Amz actually keeps a partial firmware backup on the device, which they can use via mayday when things get really messed up. I would bet, they can also see system mods. It may even function automatically in some instances, I goofed mine pretty bad restore HD system files with TB & after a couple resets, it seemed it restored the system files.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I will try that. If I could just push a new build.prop to overwrite the old one I put probably be okay. How did restore system files using ADB.
GSLEON3 said:
I did same thing. Strange but I COULD finally use adb, but only from the Android SDK base folder & only after uninstalling all devices & using USB deview to remove all adb, mtp & other android related USB devices.
So far, it looks like Amz actually keeps a partial firmware backup on the device, which they can use via mayday when things get really messed up. I would bet, they can also see system mods. It may even function automatically in some instances, I goofed mine pretty bad restore HD system files with TB & after a couple resets, it seemed it restored the system files.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Do you think you can pull a system.img for me in case I can get ADB working then I can try and flash. Lots of other people are bricking as well after root so it might be useful to many people. Thanks.
GSLEON3 said:
I did same thing. Strange but I COULD finally use adb, but only from the Android SDK base folder & only after uninstalling all devices & using USB deview to remove all adb, mtp & other android related USB devices.
So far, it looks like Amz actually keeps a partial firmware backup on the device, which they can use via mayday when things get really messed up. I would bet, they can also see system mods. It may even function automatically in some instances, I goofed mine pretty bad restore HD system files with TB & after a couple resets, it seemed it restored the system files.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
That didn't work for me, I've also trying factory resetting again multiple times through recovery, but no dice.
I got my fastboot cable working, and was able to get the device recognized as "Qualcomm USB modem converter"
I opened a thread about it, any help is appreciated!
Android Cowboy said:
Do you think you can pull a system.img for me in case I can get ADB working then I can try and flash. Lots of other people are bricking as well after root so it might be useful to many people. Thanks.
Click to expand...
Click to collapse
I am on the road right now, but I will see what I can do when I get home. You could try DL the firmware bin from Amazon. It is on their site & if you have ADB, pushing a file may be easiest, particularly since nobody has has any luck with flash or boot commands yet. At any rate, I'll do it as soon as I can, but seriously, start with just trying to push the build.prop so you still have SU & root level shell access.
GSLEON3 said:
I am on the road right now, but I will see what I can do when I get home. You could try DL the firmware bin from Amazon. It is on their site & if you have ADB, pushing a file may be easiest, particularly since nobody has has any luck with flash or boot commands yet. At any rate, I'll do it as soon as I can, but seriously, start with just trying to push the build.prop so you still have SU & root level shell access.
Click to expand...
Click to collapse
Even with the fastboot cable ADB/fastboot is not working. The Kindle finally gets recognized but as a Qualacomm device and can't find the right drivers that can make it recognize ADB. I actually have a replacement coming today so I might just let this one go. I was hoping to figure it out so I could help others in the same situation. But the factory rest really messed this thing up and Amazon is not making it easy.
Android Cowboy said:
Even with the fastboot cable ADB/fastboot is not working. The Kindle finally gets recognized but as a Qualacomm device and can't find the right drivers that can make it recognize ADB. I actually have a replacement coming today so I might just let this one go. I was hoping to figure it out so I could help others in the same situation. But the factory rest really messed this thing up and Amazon is not making it easy.
Click to expand...
Click to collapse
Did you try either of these drivers:
http://www.4shared.com/rar/kRIFBtGe/qualcomm_hsusb_device_drivers.html
http://drivers.softpedia.com/progDo...dows-7-x64-Windows-8-x64-Download-179130.html
So I actually had a similar thing happen today. build.prop mod caused my 7" to boot loop. It makes it to the first kindle screen and then the screen goes black. Based on what I've read I shouldn't try to factory reset it, because that will make it worse. I ordered a fastboot cable that should be in on Monday. Only issue is, I don't have much experience with fastboot. Would I be able to adb push a stock build.prop file to fix it if it's recognized by my computer?
S_transform said:
So I actually had a similar thing happen today. build.prop mod caused my 7" to boot loop. It makes it to the first kindle screen and then the screen goes black. Based on what I've read I shouldn't try to factory reset it, because that will make it worse. I ordered a fastboot cable that should be in on Monday. Only issue is, I don't have much experience with fastboot. Would I be able to adb push a stock build.prop file to fix it if it's recognized by my computer?
Click to expand...
Click to collapse
Since you didn't factory reset, does it show up on adb devices at all while it's trying to boot ?
S_transform said:
So I actually had a similar thing happen today. build.prop mod caused my 7" to boot loop. It makes it to the first kindle screen and then the screen goes black. Based on what I've read I shouldn't try to factory reset it, because that will make it worse. I ordered a fastboot cable that should be in on Monday. Only issue is, I don't have much experience with fastboot. Would I be able to adb push a stock build.prop file to fix it if it's recognized by my computer?
Click to expand...
Click to collapse
Try to use adb with root to push a new build.prop file. That's your best bet for recovery.
Sent from my Nexus 5 using Tapatalk
So currently its not showing up on adb while its booting, but that's probably because I haven't updated adb in a while. I'm going to update when I get home from work and report back.
EDIT: So I update ADB, which isn't recognizing it, but oddly enough, my computer can see it even after the screen shuts off as an android device. My only guess then is I'm missing a driver or something. Any suggestions?
Android Cowboy said:
Try to use adb with root to push a new build.prop file. That's your best bet for recovery.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
So I finally got ADB to recognize the device, and I can adb shell and everything, but its saying I don't have permission to adb push /system/build.prop. Also I thought that was where build.prop was located but I can't find it in adb shell. I have tried su and it hangs up, like its asking supersu for permission and I can't respond. What can I do?
S_transform said:
So I finally got ADB to recognize the device, and I can adb shell and everything, but its saying I don't have permission to adb push /system/build.prop. Also I thought that was where build.prop was located but I can't find it in adb shell. I have tried su and it hangs up, like its asking supersu for permission and I can't respond. What can I do?
Click to expand...
Click to collapse
Try adb root to reload it with root permission. Otherwise you'll need to chmod to make the system RW so you can push the build.prop file. And yes it's in the system folder. If you have the Android SDK then you can use the file manager in Monitor.bat file under "tool" folder to see to see all the files.
Android Cowboy said:
Try adb root to reload it with root permission. Otherwise you'll need to chmod to make the system RW so you can push the build.prop file. And yes it's in the system folder. If you have the Android SDK then you can use the file manager in Monitor.bat file under "tool" folder to see to see all the files.
Click to expand...
Click to collapse
When I try adb root it tells me I can't do that on consumer devices or something like that. what would the chmod command be? I dont think I've used it before. Also thank you so much for helping me.
S_transform said:
When I try adb root it tells me I can't do that on consumer devices or something like that. what would the chmod command be? I dont think I've used it before. Also thank you so much for helping me.
Click to expand...
Click to collapse
When you ADB shell, are you seeing a "#" which means you are rooted. I'm not the world's expert on ADB but this should help. Once you are shell and rooted you can just chmod 644 or 777 on /system and see if that works. http://gizbeat.com/2103/how-to-change-file-permissions-through-adb/
Intro
This is a guide for people who want to make some modifications to config files, or other files, on System partition but do not want to root their phone or install custom recovery in order to keep OTAs and some apps, which don't play nicely with rooted phones, working. Examples of those config mods could be changing DPI or changing volume levels etc, which you would only do once and forget about it.
While root allows you to do those kinds of changes from within android, this methods would require a PC.
If you are familiar with temporary booting into a custom recovery, skip to step 5.
The usual i am not responsible for any of your actions / bricked phones disclaimer applies.
Prerequisites
- A working adb / fastboot environment. Please use Android SDK, if you installed your adb and fastboot using other tools, things might not work, so please just install SDK, install Google USB Driver from SDK manager, install Platform-Tools from SDK manager (should be installed by default) and then add your sdk platform-tools path to your PATH environment variable to have it available in cmd in every path.
- Unlocked bootloader
- TWRP image for you phone (.img) https://twrp.me/devices/huaweinexus6p.html
Follow the [GUIDE] Unlock/Root/Flash for Nexus 6P for that.
Instructions
Here is an example of modifying DPI. I prefer build.prop method of modifying DPI because using the adb wm density command usually caused some issues for me, but modifying via build.prop didn't.
1 - With you phone ON, connect it to the PC and make sure adb is working by running
Code:
adb devices
and making sure that device is listed
2 - Reboot into bootloader. and make sure fastboot is good to go too. Run commands one at a time:
Code:
adb reboot bootloader
fastboot devices
3 - Place your TWRP image file in some easily accessible folder, for the sake of this example i will use C:\Mods.
4 - Temporary boot into TWRP (we are not flashing it here at all).
Code:
fastboot boot c:\Mods\twrp-2.8.7.0-angler.img
Here is where things may not work. If you don't see your phone boot into TWRP then either your adb / fastboot environment not setup correctly (installed via a tool instead of SDK) or your img file is corrupt.
One thing that works for me when TWRP refuses to boot is to restart cmd and issue the command again this closes and reopens adb/fastboot daemon.
5 - Once TWRP is up on your phone it may display a warning saying "TWRP has detected an unmounted system partition". Swipe to allow modifications at the bottom. This screen may not come up at all.
6 - Go to Mount >>> Tick System >>> Make sure "Only Mount System Read Only" is unticked >>> Press Back button
7 - Back on your PC check if your device is listed
Code:
adb devices
8 - Pull the file you need to modify from system partition to your PC. Please note the direction of the slashes:
Code:
adb pull /system/build.prop c:/Mods
9 - Now you should see build.prop in your c:\Mods folder. Use Notepad++ or something like that to edit the file. Find the line with lcd_density= and change it's value to whatever you need and save the file.
10 - Push the file back to your phone:
Code:
adb push c:/Mods/build.prop /system
11 - Reboot
Code:
adb reboot
12 - Profit.
Hope this will help anyone who is looking to do some mods without installing custom recovery and rooting your phone.
Cheers.
Would this work for adding the tethering bypass line in the build prop?
Yes it will. What's the line again I was looking for it the other day and couldn't find it...
Works are per OP's original post, tested and boosted the headphone volume without a problem.
Headphone path is /system/etc/mixer_paths.xml
So as per OP's example to pull: adb pull /system/etc/mixer_paths.xml c:/Mods
push: adb push c:/Mods/mixer_paths.xml /system/etc
I'm using the OP's "Mods" folder to demonstrate the file path but this may vary on your PC.
Can I use this to push SuperSU / etc to my device without having to permanently flash TWRP?
skrowl said:
Can I use this to push SuperSU / etc to my device without having to permanently flash TWRP?
Click to expand...
Click to collapse
You can certainly push the files to system partition and they will retain there after reboot. So if you know which files have to be pushed for SuperSU then give that a go. It shouldn't break anything.
I haven't tried pushing SuperSU files to system partition before so I can't guarantee that OTAs will work after this. The only way to find out is to try it i guess...
Can you run nandroids?
not sure if it's allowed or not.. but with this can i push hosts file onto the phone as well for ad-blocking...?????
I will say thanks now and try it later. These are the type of tweaks I would like to make to my phone. Do you know if changing the DPI cause any stock applications to show up broken like they do on the Samsung phones?
NCguy said:
Can you run nandroids?
Click to expand...
Click to collapse
Im not sure what you mean?
rohit25 said:
not sure if it's allowed or not.. but with this can i push hosts file onto the phone as well for ad-blocking...?????
Click to expand...
Click to collapse
If it's on the system partition then I yes you can.
locolbd said:
I will say thanks now and try it later. These are the type of tweaks I would like to make to my phone. Do you know if changing the DPI cause any stock applications to show up broken like they do on the Samsung phones?
Click to expand...
Click to collapse
I've never had a problem with changing DPI using this method on a nexus phone if that helps.
denk said:
Im not sure what you mean?
Click to expand...
Click to collapse
Can you run nandroids backups from TWRP by just booting into it?
okay so after i did this i get the following during boot up
"Your device is corrupt. It can't be trusted and may not work properly". Does this mean i will not get Securty Updates any more? I saw i had an update before i performed this however, now i do not see that update notifications any more.
locolbd said:
okay so after i did this i get the following during boot up
"Your device is corrupt. It can't be trusted and may not work properly". Does this mean i will not get Securty Updates any more? I saw i had an update before i performed this however, now i do not see that update notifications any more.
Click to expand...
Click to collapse
I got this too when I flashed MOAB via adb sideload. I'm just wondering if the same warning appears with the adb push method. Also, the file's permissions don't need to be set after adb push?
My main concern is if Android Pay still works with the red triangle warning. Anyone?
FYI Flashing back to stock is no issue for me.
NCguy said:
Can you run nandroids backups from TWRP by just booting into it?
Click to expand...
Click to collapse
I think if you get the latest TWRP which supports decryption of data partition (where all your stuff is) you should be able to back it up.
Edit: backup works on nexus 5 with temporary TWRP boot. Sorry I'm still waiting for my 6p to arrive.
locolbd said:
okay so after i did this i get the following during boot up
"Your device is corrupt. It can't be trusted and may not work properly". Does this mean i will not get Securty Updates any more? I saw i had an update before i performed this however, now i do not see that update notifications any more.
Click to expand...
Click to collapse
Thanks for trying it out! Sometimes OTA notifications take a little while to come up after reboot. But based on the warning Im afraid that they might be disabled now. It looks like it runs some sort of a check on the system partition to verify its legitimacy. So modifying files would be fine on it using this method but looks like adding them won't work.
TWRP just released their recovery with decryption support so you can just follow the standard procedure or just temporary booting into TWRP and rooting from there which works as well.
denk said:
I think if you get the latest TWRP which supports decryption of data partition (where all your stuff is) you should be able to back it up.
Edit: backup works on nexus 5 with temporary TWRP boot. Sorry I'm still waiting for my 6p to arrive.
Click to expand...
Click to collapse
On your Nexus5 I assume you are also unrooted? And have you tried a Nandroid restore, booted TWRP, no root?
NCguy said:
On your Nexus5 I assume you are also unrooted? And have you tried a Nandroid restore, booted TWRP, no root?
Click to expand...
Click to collapse
Just ran a restore to test it for you. Works fine as well.
My N5 is unrooted.
.
denk said:
Just ran a restore to test it for you. Works fine as well.
My N5 is unrooted.
.
Click to expand...
Click to collapse
Thanks a lot for that. I didn't unlock the bootloader. Ugh. Time to start over. To me nandroids alone make it worth the effort.