Database Info

[Q] How to Root Nexus S 4.0.3 from OTA

I was wondering if someone has found a method to root the latest Nexus S update from the OTA version instead of needing to flash a new rom. I don't feel like resyncing my 3000+ contacts and join the facebook and twitter contacts.
It would really help if i could get root permissions and su working properly by flashing a file or something. Thanks to all that help in advance

High level method
Fastboot OEM unlock
Fastboot flash recovery clockworkmod
Install such.zip from recovery
Sendt fra min Galaxy Nexus med Tapatalk

diesel2k said:
High level method
Fastboot OEM unlock
Fastboot flash recovery clockworkmod
Install such.zip from recovery
Sendt fra min Galaxy Nexus med Tapatalk
Click to expand...
Click to collapse
I tried that... unless you know a specific version of SU to flash because the one I have isn't working

download this http://forum.xda-developers.com/attachment.php?attachmentid=821265&d=1324235293
and flash it

TrueYears said:
If you are rooted skip step 1
STEP 1: http://forum.xda-developers.com/show....php?t=1138755 Root it and unlock it
* I strongly suggest you understand what this will do. So check out this guide
http://theunlockr.com/2010/12/17/how...msung-nexus-s/
Once you have done this, make a folder in your phone called ROMS ( or anything doesnt matter) download the rom that you will be using, this zip and the SU zip. It will make it easier on you
Sub step 1.5: WIPE CACHE AND WIPE DATA
STEP 3: Flash the 4.0.3 Rom http://forum.xda-developers.com/show....php?t=1398302
Once you've done this, it will delete the recovery that you got and it will install the stock recovery
STEP 4: Flash this http://forum.xda-developers.com/show....php?t=1396959
this will make Superuser work allowing you to download ROM Manager and letting you flash recovery from there. Make sure to allow it
Click to expand...
Click to collapse
Tried it... it isn't a full stable root. meaning it doesn't give the root permissions prompt from SU once you are using 4.0.3

Azuske said:
Tried it... it isn't a full stable root. meaning it doesn't give the root permissions prompt from SU once you are using 4.0.3
Click to expand...
Click to collapse
Interesting
I purchased a Nexus S the other day and did exactly this
maybe if you had flashed the SU zip in that link it SU would have worked
oh well sucks you wont be able to try awesome ICS =/

TrueYears said:
Interesting
I purchased a Nexus S the other day and did exactly this
maybe if you had flashed the SU zip in that link it SU would have worked
oh well sucks you wont be able to try awesome ICS =/
Click to expand...
Click to collapse
Lol I'm using ICS already man i'm just having SU issues and i don't want to have to reflash anything because I have 3000+ contacts I need to have joined with twitter and facebook and its a pain to re sync and join

Azuske said:
Lol I'm using ICS already man i'm just having SU issues and i don't want to have to reflash anything because I have 3000+ contacts I need to have joined with twitter and facebook and its a pain to re sync and join
Click to expand...
Click to collapse
Nevermind I fixed it lmfao I someone sent me a newer SU to flash and it did the trick. Thanks for all your help

Azuske said:
Lol I'm using ICS already man i'm just having SU issues and i don't want to have to reflash anything because I have 3000+ contacts I need to have joined with twitter and facebook and its a pain to re sync and join
Click to expand...
Click to collapse
oh okay I mean I would just flash the new SU which was released yesterday that fixed
like did you even bothered to read what was on the link?
http://forum.xda-developers.com/showthread.php?t=1396959
---------- Post added at 08:22 AM ---------- Previous post was at 08:20 AM ----------
Azuske said:
Nevermind I fixed it lmfao I someone sent me a newer SU to flash and it did the trick. Thanks for all your help
Click to expand...
Click to collapse
You seriously couldnt follow just step 4 of my guide? lol................ oh boy

hi bro, i want it also, just because i do need u permissions for some apps , anyone success it ? if u share we will be graceful!

joose1983 said:
hi bro, i want it also, just because i do need u permissions for some apps , anyone success it ? if u share we will be graceful!
Click to expand...
Click to collapse
if you are already on 4.0.3 and want SU permission to work right
just download this and flash it in the recovery........... its like you people don't read anything and just want people to give it to you
http://forum.xda-developers.com/attachment.php?attachmentid=821265&d=1324235293

TrueYears said:
oh okay I mean I would just flash the new SU which was released yesterday that fixed
like did you even bothered to read what was on the link?
http://forum.xda-developers.com/showthread.php?t=1396959
---------- Post added at 08:22 AM ---------- Previous post was at 08:20 AM ----------
You seriously couldnt follow just step 4 of my guide? lol................ oh boy
Click to expand...
Click to collapse
Click your link... it didn't work... atleast not for me...
Edit: the 2nd link was the same file (atleast by name) that was sent to me

Azuske said:
Click your link... it didn't work
Click to expand...
Click to collapse
oh yeah weird I'll go fix that

Guys, it really isn't difficult or compled. You just have to follow the instructions carefully and do it one stage at a time.
Here is what I have just run through myself after losing root following the OTA update to ICS 4.0.3.
Before anything else you'll need the Android SDK installed so you have access to the adb and fastboot commands on your PC/Mac/Linux. If you haven't done that then you aren't going anywhere further. I already had this installed.
First, gather the two files that you'll need to install on your Nexus S, these are:
Superuser from here --> http://forum.xda-developers.com/showthread.php?t=1396959
and
Recovery from here --> http://wiki.cyanogenmod.com/wiki/Ne...de#Installing_the_ClockworkMod_Recovery_Image
Copy the file on to the Nexus S in a suitable directory or root, it doesn't matter, you'll be using it later.
Then, and only then, you should follow the instructions on the Wiki page to install the recovery.zip to your Nexus S
Boot the Nexus S into recovery and choose install zip from sdcard.
Select the Superuser.zip file (it may be a longer filename) and press go, it will install Superuser
Reboot back into Android and load up a suitable file manager (I use root explorer).
Navigate to /etc and rename the file installrecovery.sh to something else (I just appended .old to the filename)
Reboot back into bootloader and repeat the flash recovery recovery.img
Thats it, your'e done. Rooted and with Recovery permanent on the Nexus S.
Caveat: If any of the above doesn't mean very much to you then STOP right now. Get someone you know to help you or you'll likely end up with a brick.

TrueYears said:
if you are already on 4.0.3 and want SU permission to work right
just download this and flash it in the recovery........... its like you people don't read anything and just want people to give it to you
http://forum.xda-developers.com/attachment.php?attachmentid=821265&d=1324235293
Click to expand...
Click to collapse
Well I tried this but something happened that I was not prepared for. I have the OTA 4.0.3 update installed and I actually flashed it with the stock recovery that already came with my Nexus S. Surprisenly, now, I can't boot to recovery. I press the power button and the phone reboots, then quickly a "dead" droid appears with a red attention sign on his belly and the phone goes black and I need to get the battery off. It does not boot into recovery, it does not respond, its simply black. What the hell should I do? Please help I'm new to the NS, just bought it this week
EDIT: Everything else is working fine. Just cant access my recovery

Azuske said:
I was wondering if someone has found a method to root the latest Nexus S update from the OTA version instead of needing to flash a new rom. I don't feel like resyncing my 3000+ contacts and join the facebook and twitter contacts.
It would really help if i could get root permissions and su working properly by flashing a file or something. Thanks to all that help in advance
Click to expand...
Click to collapse
I can tell you what worked for me: http://forum.xda-developers.com/showthread.php?t=1479831
I'm running stock ICS on i9023, now rooted but with bootloader still locked.
Credits go to saurik who found the exploit (https://github.com/saurik/mempodroid)

Hands0n said:
Guys, it really isn't difficult or compled. You just have to follow the instructions carefully and do it one stage at a time.
Here is what I have just run through myself after losing root following the OTA update to ICS 4.0.3.
Before anything else you'll need the Android SDK installed so you have access to the adb and fastboot commands on your PC/Mac/Linux. If you haven't done that then you aren't going anywhere further. I already had this installed.
First, gather the two files that you'll need to install on your Nexus S, these are:
Superuser from here --> http://forum.xda-developers.com/showthread.php?t=1396959
and
Recovery from here --> http://wiki.cyanogenmod.com/wiki/Ne...de#Installing_the_ClockworkMod_Recovery_Image
Copy the file on to the Nexus S in a suitable directory or root, it doesn't matter, you'll be using it later.
Then, and only then, you should follow the instructions on the Wiki page to install the recovery.zip to your Nexus S
Boot the Nexus S into recovery and choose install zip from sdcard.
Select the Superuser.zip file (it may be a longer filename) and press go, it will install Superuser
Reboot back into Android and load up a suitable file manager (I use root explorer).
Navigate to /etc and rename the file installrecovery.sh to something else (I just appended .old to the filename)
Reboot back into bootloader and repeat the flash recovery recovery.img
Thats it, your'e done. Rooted and with Recovery permanent on the Nexus S.
Caveat: If any of the above doesn't mean very much to you then STOP right now. Get someone you know to help you or you'll likely end up with a brick.
Click to expand...
Click to collapse
I was searching on this post for a clear how-to, and this guy made it! Thanks alot!

[SCH-I705] Help can I unbrick my tablet

I have a Galaxy Tab 2 VZW and was trying to install the ClearRom, but I guess I forgot to unlock bootloader, so now everytime I turn the tab on I get message statitng " System Software not authorized by Verizon Wireless has been found on your phone."
I have a backup from before I tried installing the ROM but don't know what to do with it
Any help will be appreciated

melog69 said:
I have a Galaxy Tab 2 VZW and was trying to install the ClearRom, but I guess I forgot to unlock bootloader, so now everytime I turn the tab on I get message statitng " System Software not authorized by Verizon Wireless has been found on your phone."
I have a backup from before I tried installing the ROM but don't know what to do with it
Any help will be appreciated
Click to expand...
Click to collapse
HOw did you make the backup? CWM? If so, then install CMW recovery and do a restore.

DigitalMD said:
HOw did you make the backup? CWM? If so, then install CMW recovery and do a restore.
Click to expand...
Click to collapse
I tried getting into recovery mode, but I get the following screen everytime, I think I need the Stock Firmware to flash with ODIN but I don't know where to find it.
<iframe src="https://skydrive.live.com/embed?cid=47A1A726F16BDCFD&resid=47A1A726F16BDCFD%212570&authkey=AE3MPZ8PewFeQos" width="180" height="320" frameborder="0" scrolling="no"></iframe>

Always, ALWAYS, follow directions exactly how they're laid out.
What you need to do is download the aboot.img to your sd card. Reboot into recovery, ADB Shell into your device (you may need linux for this part as Windows doesn't recognize the device in recovery mode). Once you ADB into recovery, make sure you are root (noted by # instead of $).
Then:
dd if=/sdcard/aboot.img of=/dev/block/mmcblk0p5
reboot download
This should unlock you bootloader so you can get by verizons pesky warning.
We can't see the picture you tried attaching.

MrHyde03 said:
Always, ALWAYS, follow directions exactly how they're laid out.
What you need to do is download the aboot.img to your sd card. Reboot into recovery, ADB Shell into your device (you may need linux for this part as Windows doesn't recognize the device in recovery mode). Once you ADB into recovery, make sure you are root (noted by # instead of $).
Then:
dd if=/sdcard/aboot.img of=/dev/block/mmcblk0p5
reboot download
This should unlock you bootloader so you can get by verizons pesky warning.
We can't see the picture you tried attaching.
Click to expand...
Click to collapse
I cannot get to recovery mode, only download mode, also ClearRom did not specify that the bootloader, that is why I did not even bother

melog69 said:
I cannot get to recovery mode, only download mode, also ClearRom did not specify that the bootloader, that is why I did not even bother
Click to expand...
Click to collapse
You'll more than likely have to send it back. There has been no official release of stock firmware, unfortunately (none that I have found at least). In the root thread there are steps 1 - 3 for a reason. 1 - Root, 2 - Unlock and Recovery, 3 - Custom ROM. Always follow directions.

MrHyde03 said:
You'll more than likely have to send it back. There has been no official release of stock firmware, unfortunately (none that I have found at least). In the root thread there are steps 1 - 3 for a reason. 1 - Root, 2 - Unlock and Recovery, 3 - Custom ROM. Always follow directions.
Click to expand...
Click to collapse
Well, thanks guys now I know what to do when it's fixed

melog69 said:
Well, thanks guys now I know what to do when it's fixed
Click to expand...
Click to collapse
Maybe try a stock 3100 rom? If the hardware is the same should work, just need to set APN etc.Then reroot, install recovery, install cuztom rom.
---------- Post added at 04:04 PM ---------- Previous post was at 03:54 PM ----------
acefsw said:
Maybe try a stock 3100 rom? If the hardware is the same should work, just need to set APN etc.Then reroot, install recovery, install cuztom rom.
Click to expand...
Click to collapse
Actually, according to here http://forum.xda-developers.com/showthread.php?t=1885558 you just need download mode to install the stock image and then follow the rest of the steps.

acefsw said:
Maybe try a stock 3100 rom? If the hardware is the same should work, just need to set APN etc.Then reroot, install recovery, install cuztom rom.
Click to expand...
Click to collapse
DO NOT INSTALL A P3100 ROM. It's not the same hardware (not really even close), so that would only make it worse.

imnuts said:
DO NOT INSTALL A P3100 ROM. It's not the same hardware (not really even close), so that would only make it worse.
Click to expand...
Click to collapse
I edited the post, read the link, it is for his device

imnuts is correct. These devices are extremely different and really does need it's own subforum so people don't keep getting confused. The i705 is closest to the i535 (s3), nearly identical actually.

MrHyde03 said:
imnuts is correct. These devices are extremely different and really does need it's own subforum so people don't keep getting confused. The i705 is closest to the i535 (s3), nearly identical actually.
Click to expand...
Click to collapse
Then wouldn't it be easier to flash an S Rom?

melog69 said:
Then wouldn't it be easier to flash an S Rom?
Click to expand...
Click to collapse
It still wouldn't work. boot, recovery, and system for the s3 are designed for the s3. The hardware is the same, but the software has it's differences. What differences, though, is beyond me.

I have the same issue, this is the first time I've ever "Bricked" a device. Thought I followed the instructions correctly, I can successfully flash recovery.tar.md5 on Mr.Hydes thread http://forum.xda-developers.com/showthread.php?t=1885558 but when it goes to reboot it gives me the Yellow ExclaTriangle "System software not authorized by Verizion , yadi, yadi ya da".
I can get into Download mode but NO RECOVERY, Tried flashing (With ODIN) CWM 6.0.1.9 located here http://forum.xda-developers.com/showthread.php?t=2044630 but ERROR with NAND WRITE FAIL.
Does anyone have a PIT file? I want give Heimdall a stab at it before I go throw it through Verizon's front window. Appreciate any help, like I said I understand the importance of following Instructions, I've done plenty of Android devices before including The Original GTab7, I dont mind cracking it open either, I've already had it apart to disconnect the battery but that did no help either, BTW it's really easy to open up.

Sounds like you didn't flash the unsecure bootloader
Sent from my SCH-I535 using XDA Premium HD app

MrHyde03 said:
Sounds like you didn't flash the unsecure bootloader
Sent from my SCH-I535 using XDA Premium HD app
Click to expand...
Click to collapse
I couldn't boot into Recovery to Flash, I'm Trying to flash now using Odin but get "Secure Check Fail". Any Ideas?

The bootloader needs to be flashed before the recovery using the dd command. Its listed first under step 2, before the recovery.
Sent from my SCH-I535 using XDA Premium HD app

MrHyde03 said:
The bootloader needs to be flashed before the recovery using the dd command. Its listed first under step 2, before the recovery.
Sent from my SCH-I535 using XDA Premium HD app
Click to expand...
Click to collapse
Yeah that's where I'm confused, I've had it rooted and unlocked since November following your original Development, I was on G3 not J1. Followed the Instructions and then crap.

Unlocked since Nov and it just now crapped? That doesn't make any sense.. When you boot into download mode right now, what orientation is the screen? Portrait or landscape? Landscape would mean a correctly flashed aboot.img (boot loader)
Sent from my SCH-I535 using XDA Premium HD app

iwSachin plain
MrHyde03 said:
Unlocked since Nov and it just now crapped? That doesn't make any sense.. When you boot into download mode right now, what orientation is the screen? Portrait or landscape? Landscape would mean a correctly flashed about.img (boot loader)
Sent from my SCH-I535 using XDA Premium HD app
Click to expand...
Click to collapse
I followed this thread of yours in the beginning of NOV. http://forum.xda-developers.com/showthread.php?t=1942674 I was rooted and unsecured bootloader, had CWM and SuperUser, but there weren't any ROMS out yet. Everything was fine until I went to install CleanRom the other day.
Portrait Orientation in Download mode.

4.3 system image

If at all possible, can someone upload a system image of 4.3?
if you're rooted and on 4.3 OTA, you can use adb with
Code:
dd if=/dev/block/mmcblk0 of=/storage/sdcard1/debrick.bin bs=1024 count=81920
or flash this in recovery (will probably need to use stock recovery)
https://www.copy.com/s/1ggUuyIqHUrF
If you're wondering why I'm inquiring about an .img
for reference, if it works for them. Then it MAY work for vzw and it'll help some unbrick.
- http://forum.xda-developers.com/showthread.php?t=2369125
- http://forum.xda-developers.com/showthread.php?t=2439367
- http://forum.xda-developers.com/showthread.php?t=2549068

Hahaha I just realized this thread was here! Oops!
Sent From My Last Ever Samsung Device.

SpyroDazee said:
If at all possible, can someone upload a system image of 4.3?
if you're rooted and on 4.3 OTA, you can use adb with
Code:
dd if=/dev/block/mmcblk0 of=/storage/sdcard1/debrick.bin bs=1024 count=81920
or flash this in recovery (will probably need to use stock recovery)
Click to expand...
Click to collapse
i would be glad to help but, im currently unrooted on 4.3. ive found a way to root my phone (saferoot) but i am uncertain if it works for the s3. im reading into it now

smokyngord said:
i would be glad to help but, im currently unrooted on 4.3. ive found a way to root my phone (saferoot) but i am uncertain if it works for the s3. im reading into it now
Click to expand...
Click to collapse
Safe root works without issue, but please, don't flash any custom recovery or OS or you will brick.
Sent from my Last Ever Samsung Device.
---------- Post added at 11:32 AM ---------- Previous post was at 11:32 AM ----------
And don't try and downgrade back to anything below 4.3
Sent from my Last Ever Samsung Device.

0331 said:
Safe root works without issue, but please, don't flash any custom recovery or OS or you will brick.
Click to expand...
Click to collapse
i'm not just want root. but right now my computer isnt reading my phone. it shows that it connects under device manager but cant see any of the files.

Try reinstalling drivers
Sent from my Last Ever Samsung Device.

0331 said:
Try reinstalling drivers
Sent from my Last Ever Samsung Device.
Click to expand...
Click to collapse
i will but for the sake of the OP i will pm you if i cant figure it out

I think tsachi might have it? http://forum.xda-developers.com/showthread.php?p=48735040#post48735040

[Q] Nexus Toolkit "EOCD not found, not Zip"

Hello all, I was messing with my build.prop to get the free book from the Play Books offer when after a reboot my device stopped booting. After the "Google" I just get a black screen. I'm trying to use the Nexus Toolkit the "Back to Stock" Tool, I can get into fastboot just fine but when the tool opens the command window I get "EOCD not found, not zip" then a bunch of nonsense characters. Took a screenshot http://i.imgur.com/FwsfgzI.jpg Any suggestions?

yea, dont use root toolkits.
flash the factory img via fastboot while youre in the bootloader. and if you want to edit your build.prop, use a root file manager, edit it, then save. reboot for it to take affect.

What he said ^^^
Try this guide,
http://forum.xda-developers.com/showthread.php?t=2513701

nameback said:
Any suggestions?
Click to expand...
Click to collapse
Stop using toolkits.
Just extract the build.prop out of the rom zip and push it with adb.
Code:
adb push build.prop /system
LOL. Simms is way ahead of me.

No suggestions for this toolkits. We don't recommend them.
Editing the build prop incorrectly will cause a boot loop. Its an easy fix. Reflash your ROM (download a ROM.zip and flash via recovery) or restore your nandroid backup that you will have taken before modifying /system
Going back to stock is a very long and noob thing to do. This is the problem with toolkits. No one understands what they're doing.
Please read through the guides here. They will help you no end. They're in my signature

oh, i messed up. first suggestion should have been just reflash your rom, dirty(no wiping) :angel:

simms22 said:
oh, i messed up. first suggestion should have been just reflash your rom, dirty(no wiping) :angel:
Click to expand...
Click to collapse
Lol Guess disregard my link too. ?

theesotericone said:
Stop using toolkits.
Just extract the build.prop out of the rom zip and push it with adb.
Code:
adb push build.prop /system
LOL. Simms is way ahead of me.
Click to expand...
Click to collapse
I'm just running stock and I've been meaning to learn how to do things properly so I'll download the SDK and give it a whirl. Thanks for the help all!

nameback said:
Stop using toolkits.
Just extract the build.prop out of the rom zip and push it with adb.
I'm just running stock and I've been meaning to learn how to do things properly so I'll download the SDK and give it a whirl. Thanks for the help all!
Click to expand...
Click to collapse
You don't need the SDK.
Click the guides link in my signature and read "adb and fastboot. What is it?"

Sorry maybe I need a little more hand holding here, how do I get adb working if I can't boot my device? It doesn't seem like you can push with fastboot.

Adb works in custom recovery or android.
Again, all covered in my thread that I asked you to read.

Tried to pm you but apparently you don't get them. Your sig has disappeared. Just a heads up. To the OP, look at the sticky in N5 q&a about adb.
Weird, you sig is in one post but not the one you told the OP to check it in.

wangdaning said:
Tried to pm you but apparently you don't get them. Your sig has disappeared. Just a heads up. To the OP, look at the sticky in N5 q&a about adb.
Weird, you sig is in one post but not the one you told the OP to check it in.
Click to expand...
Click to collapse
Ah interesting, thanks. I posted that from the XDA one alpha app.
---------- Post added at 03:26 AM ---------- Previous post was at 03:24 AM ----------
Test

Is it possible to root, install an apk as system then unroot?

I'm wondering if it's possible to root my phone, install an app that's required to be installed as system then unroot my phone back to normal?
I'm on the latest stable miui 8.5.2.0. I'd like to install the new pixel launcher and have Google now working which requires the APK to be installed as a system app.
Require unrooted phone for work/banking apps.

Easier way: copy the apk to /system/app/ in twrp. When you reboot, it should be installed as a system app.

theOriginalSuperl2 said:
Easier way: copy the apk to /system/app/ in twrp. When you reboot, it should be installed as a system app.
Click to expand...
Click to collapse
Oh cool I never knew about that way. But I don't have TWRP installed. It took me forever to get the vendor ROM off my Xiaomi phone and get back to stock.
Are you saying I should install TWRP and then unroot?

umirza85 said:
Oh cool I never knew about that way. But I don't have TWRP installed. It took me forever to get the vendor ROM off my Xiaomi phone and get back to stock.
Are you saying I should install TWRP and then unroot?
Click to expand...
Click to collapse
If you install TWRP, and copy the APK, then it won't root your phone at all. You can re-flash the stock recovery after, if you want.

theOriginalSuperl2 said:
If you install TWRP, and copy the APK, then it won't root your phone at all. You can re-flash the stock recovery after, if you want.
Click to expand...
Click to collapse
Oh thats so awesome! I believe I read somewhere that you need the stock recovery in order to do OTA updates, so that would definitely be preferable.
Thanks so much for taking the time to reply. One more question, is there a guide anywhere on how to put the stock recovery back onto the Mi 5s Plus?

umirza85 said:
Oh thats so awesome! I believe I read somewhere that you need the stock recovery in order to do OTA updates, so that would definitely be preferable.
Thanks so much for taking the time to reply. One more question, is there a guide anywhere on how to put the stock recovery back onto the Mi 5s Plus?
Click to expand...
Click to collapse
I don't think so, but all you need to do is flash a stock recovery image with fastboot. You have to find one online.
---------- Post added at 02:05 PM ---------- Previous post was at 01:57 PM ----------
theOriginalSuperl2 said:
I don't think so, but all you need to do is flash a stock recovery image with fastboot. You have to find one online.
Click to expand...
Click to collapse
Hang on. There's a much easier way, and I can't find the images online. I'll post how soon, have to go for now.

theOriginalSuperl2 said:
I don't think so, but all you need to do is flash a stock recovery image with fastboot. You have to find one online.
---------- Post added at 02:05 PM ---------- Previous post was at 01:57 PM ----------
Hang on. There's a much easier way, and I can't find the images online. I'll post how soon, have to go for now.
Click to expand...
Click to collapse
Thats great thanks! Appreciate it.

umirza85 said:
Thats great thanks! Appreciate it.
Click to expand...
Click to collapse
You actually don't need to flash TWRP at all.
1: Download TWRP on your computer.
2: Make sure you have the APK on your phone.
3: Run the command "fastboot boot twrp.img" in fastboot mode, where twrp.img is the TWRP filename. On Linux, this may need to be run as root. This command will temporarily boot TWRP, without flashing it.
4: Copy your APK to /system/app/
5: Reboot into android. The app should be installed.
I'm curious why you need to install an app as a system app?

theOriginalSuperl2 said:
You actually don't need to flash TWRP at all.
1: Download TWRP on your computer.
2: Make sure you have the APK on your phone.
3: Run the command "fastboot boot twrp.img" in fastboot mode, where twrp.img is the TWRP filename. On Linux, this may need to be run as root. This command will temporarily boot TWRP, without flashing it.
4: Copy your APK to /system/app/
5: Reboot into android. The app should be installed.
I'm curious why you need to install an app as a system app?
Click to expand...
Click to collapse
Whoa!! no way! That is so much easier and dont have to mess about with trying to but the phone back to stock after. Youre the best!
I want to use the new pixel 2 launcher, and for all the functionality to work (i.e google now integration) the app needs to be installed as a system app!
This was make it so simple to try it out without making any permanent changes. Thanks again!

umirza85 said:
Whoa!! no way! That is so much easier and dont have to mess about with trying to but the phone back to stock after. Youre the best!
I want to use the new pixel 2 launcher, and for all the functionality to work (i.e google now integration) the app needs to be installed as a system app!
This was make it so simple to try it out without making any permanent changes. Thanks again!
Click to expand...
Click to collapse
I guessed it was to use the pixel launcher. You could get a modded version instead of installing in the system, though.
I tried out the launcher too, but it was really buggy and laggy for me.

theOriginalSuperl2 said:
I guessed it was to use the pixel launcher. You could get a modded version instead of installing in the system, though.
I tried out the launcher too, but it was really buggy and laggy for me.
Click to expand...
Click to collapse
Yeah I've tried out the modded version and sucks that the google now functionality doesnt work, and as you said its quite buggy. Read in a few places that installing as system really helps, and with your method it seems we can try it out without switching my phone off of being completely stock (also forgot to mention that I need stock recovery to properly use the phone encryption feature as required by my company policy).