Database Users

Unfinished rooting nexus one , please help

hi
I have a Nexus One on Official 2.3.4 update and i'm trying to root the phone, i'm having a hard time with the recovery image, I really like to know what i should do next.
1. read lots tutorials
2. Installed Android SDK and USB Driver for ADB thingy
3. downloaded and put fastboot in platform-tool and successfully unlocked bootloader
4. cannot get recovery to work, intended to install clockworkmod and RA one both give me the ! logo when i intend to boot in it
Questions
1. Should i downgrade first and then do this, if so, how does it work (if someone have a link to step by step tutorial)
2. Other methods
thanks a million

How are you trying to install recovery, and what errors/results are you seeing? Should be:
fastboot flash recovery name-of-recovery.img
How are you booting into recovery (if you reboot the phone, you will lose recovery)? Should be:
fastboot boot name-of-recovery.img
No need to downgrade. An unlocked bootloader is all you'll ever need...

danger-rat said:
How are you trying to install recovery, and what errors/results are you seeing? Should be:
fastboot flash recovery name-of-recovery.img
How are you booting into recovery (if you reboot the phone, you will lose recovery)? Should be:
fastboot boot name-of-recovery.img
No need to downgrade. An unlocked bootloader is all you'll ever need...
Click to expand...
Click to collapse
i install recovery that way yes, but i didn't boot that way, thanks i will try right now, will report back
EDIT - that works thanks so much, now i'm gonna attempt to root.

now i encounter another issue
so far i been following this guild http://forum.xda-developers.com/showthread.php?t=636795
and i cannot reboot to recovery after vol down+power menu.
do i just enter recovery with fastboot boot command and go from there?
what would be a better guild from this point on?

Place these two files on your sd card:
su zip: http://db.tt/BJudP0L
fix recovery zip: http://db.tt/ooDaCnU
Boot into recovery from the fastboot command, choose the flash zip from sd option, and flash the two files (one at a time). Done!

awesome, i had them installed. what's su and why is it recovery fix, if u don't mind can u explain these 2 files a little bit?
and what's next, do i just put the rom i'm flashing in the SD Card root and use recovery mode to install the zip?
going to use Cyanogen 7 for nexus one (update-cm-7.0.3-N1-signed.zip)
and also, what is this Google Add-on i read from the tutorial?

tripleccreation said:
awesome, i had them installed. what's su and why is it recovery fix, if u don't mind can u explain these 2 files a little bit?
and what's next, do i just put the rom i'm flashing in the SD Card root and use recovery mode to install the zip?
going to use Cyanogen 7 for nexus one (update-cm-7.0.3-N1-signed.zip)
and also, what is this Google Add-on i read from the tutorial?
Click to expand...
Click to collapse
su is short for superuser.. its basically using the root user account..
btw 7.1 RC is out if youre interested.. also take a look at the nightly releases

If you're going to install a custom rom like cm7 you do not have bother with the su part.
Put cm rom on the sd ( can be anywhere you just navigate to it) and the google addons (those or the gapps like the market etc.)
Flash custom recovery
Boot directly into the recovery (if you boot the os it overwrites the new recovery with the stock one)
Flash cm7
flash gapps.
reboot into cm7...
Your custom recovery will now stay there until you either flash a different one. Or flash a stock rom.

grimey01 said:
su is short for superuser.. its basically using the root user account..
btw 7.1 RC is out if youre interested.. also take a look at the nightly releases
Click to expand...
Click to collapse
should i just install the rom zip file in recovery mode? I'm not 100% sure what i'm suppose to do

albundy2010 said:
If you're going to install a custom rom like cm7 you do not have bother with the su part.
Put cm rom on the sd ( can be anywhere you just navigate to it) and the google addons (those or the gapps like the market etc.)
Flash custom recovery
Boot directly into the recovery (if you boot the os it overwrites the new recovery with the stock one)
Flash cm7
flash gapps.
reboot into cm7...
Your custom recovery will now stay there until you either flash a different one. Or flash a stock rom.
Click to expand...
Click to collapse
great, now u said flash cm7 do u mean "install zip file" but pick the cm7 file?
also, google add on, where should i acquire it?

also, for nightly release of cm (cm7.1 rc) for nexus one i should download the one called "passion" is that correcT?
http://download.cyanogenmod.com/?type=nightly

Also forgot to mention to do a wipe before you flash. That is also done in recovery.
gapps http://goo-inside.me/gapps/gapps-gb-20110613-signed.zip That is
In recovery you pick install zip file. You then browse to your cm7 rom.zip or any rom for the matter and install. Do the same for the gapps. Do the same for any other flashable zip like kernals etc.

Yes. Nightly/stable/RC's all have to passion (nexus 1)

Also for future reference post ?s in the Q and A section. A mod will probably move it there or delete this thread.

albundy2010 said:
Also for future reference post ?s in the Q and A section. A mod will probably move it there or delete this thread.
Click to expand...
Click to collapse
Great!
i will keep that in mind for sure.

Update: Method Works now i know how to flash and root nexus one, awesome guys thanks a million.
Conclusion and Steps I did (probably helpful to many people like me research tons different tutorials)
1. Download Android SDK and install it,
2. Find "Nexus One USB Driver" download and install it, now install bootloader (follow guide here, but only do up to the boot loader part http://forum.xda-developers.com/showthread.php?t=636795)
3. Find "fastboot" download and extract it to Android SDK installation folder (one called Platform-tools)
4. download a recovery img, i got clockwork 3.0.0.5.
5. download the su (super user) (i dunno if this is necessary but i did it anyway, links are in previous replies) and copy the zip file to ur sd card.
6. download the custom rom u want to use and copy to sd card as well (i use cyanogenmod 7.1 rc here)
7. download the google addon and copy the zip to the sd card as well (link provided in previous replies)
8. go to start and type cmd to load up command prompt in windows (i use windows 7)
9. get to c:\program files (x86)\android\android-sdk\platform-tools\ (i use windows 7 64bit, if it's 32bit system, no need for (x86))
10. hold trackball + power to enter bootloader and fastboot usb enable (should be automatic)
11. type fastboot flash recovery [recovery name.img] (in Windows Command Prompt)
12. type fastboot boot [recovery name.img] (in windows command prompt)
13. do a backup first, then wipe all data and cache, and then navigate to "install zip" and install su, recovery fix, custom rom, google addon, one by one b4 restart
14. after all done, restart, and that's it.
it works for me. but of course, i'm pretty noob, you are still taking ur own risk if u follow my experience..

Step 5 (recovery fix) is only necessary if you are sticking with a stock ROM. All it does is delete the two files that restore the stock recovery. These two files are only in the stock ROM, which is why you don't need to do this if you install a custom ROM...
Also, as started earlier, you can also skip the su zip if you plan on installing a custom ROM...

[HOW-TO] Updating Nook HD+ Internal EMMC from CM11 to LN14.1

Caveat emptor: adopt/follow this guide at your own risk.
Below is a procedure that can be used to update your HD+ EMMC to LN14.1 from CM11 (if your HD+ is currently running stock ROM, use the process described at https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810/).
Download the following files to a location in your user content-media storage space on the HD+:
amaces' flashable TWRP zip file, e.g., twrp-3.0.1-0-ovation.zip ( https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778)
amaces' flashable LN14.1 ROM zip file, e.g., lnos_ovation-ota-NMF26Q.170104.zip from https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778
the flashable zip file of the Gapps pico package open_gapps-arm-7.1-pico-2017[mmdd].zip from http://opengapps.org/
Boot into your current EMMC recovery.
Select install zip and install the TWRP recovery zip file obtained in step 1(a).
Power off the Nook.
Boot into the new TWRP recovery flashed in the step 3 (press and hold the Home button, then press and hold the Power button until after the CyanoBoot Universal Bootloader screen comes on, then release both buttons).
Select wipe /data & factory reset.
Select install zip and install the LN14.1 zip file.
Select install zip and install the Gapps zip file.
Reboot into the new LN14.1.
Once the Nook completes the boot (be patient as it takes quite a bit of time), set up the Wifi connectivity and your Google account info. Note that the Apps you previously have on CM11 will not be auto-downloaded/restored into your new LN14.1.
If you run into problems during initial setup:
- absence of WiFi network setup step: see this post
- setup process crashes (as have been reported with some combos of ROM and GApps build versions): retry the clean install process with the sequence of steps # 6, #7 & #9 (i.e., skipping over step #8 flashing GApps) and complete the initial setup, then reboot into TWRP to flash GApps; see also https://forum.xda-developers.com/showpost.php?p=72104906&postcount=37 for solution for other setup crash causes.
To enable "Root", see https://forum.xda-developers.com/showpost.php?p=72185622&postcount=1915.
Notes
If you encounter errors in step 3 (using your existing CWM recovery to flash the new TWRP zip file):
- If you have a SD card handy, consider using the procedure described at https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810.
- Otherwise, you can try to flash the flashable TWRP zip file available at http://www.mediafire.com/file/3gj4g9j1x363dor/cwm-flashable_twrp-3.0.1-0-ovation.zip.
Please post any comment/question on the features or performance of AOSP & LN ROM builds on the Developer's thread at https://forum.xda-developers.com/nook-hd/development/marshmallow-nook-hd-hd-t3239269.

I'm on CM11 and am getting hung up trying to install TWRP. I get:
This package is for device: ovation; this device is .
Status 7
Installation aborted
Tips?
I'm running EMMC CWM v6.0.4.6

stupid_nut said:
I'm on CM11 and am getting hung up trying to install TWRP. I get:
This package is for device: ovation; this device is .
Status 7
Installation aborted
Tips?
I'm running EMMC CWM v6.0.4.6
Click to expand...
Click to collapse
Is your device a Nook HD+?

digixmax said:
Is your device a Nook HD+?
Click to expand...
Click to collapse
Made me question myself but yes.
Nook HD+
I'm running 11-2014-1112-SNAPSHOT-M12-ovation
Even wiped and backed up to a fresh copy of CM. The system info even says the device is ovation. Bit confused. Any ideas?

stupid_nut said:
Made me question myself but yes.
Nook HD+
I'm running 11-2014-1112-SNAPSHOT-M12-ovation
Even wiped and backed up to a fresh copy of CM. The system info even says the device is ovation. Bit confused. Any ideas?
Click to expand...
Click to collapse
Have you tried flashing TWRP through their official app? I think I also had trouble trying to flash TWRP through CWM, but the app worked at the time.
You could also flash internal TWRP through Amaces's multi mode bootable SD recovery. It does mean you'd need to setup a spare SD card for it, but it can be good to have handy anyway [emoji6]

stupid_nut said:
Made me question myself but yes.
Nook HD+
I'm running 11-2014-1112-SNAPSHOT-M12-ovation
Even wiped and backed up to a fresh copy of CM. The system info even says the device is ovation. Bit confused. Any ideas?
Click to expand...
Click to collapse
I can't tell why the update script doesn't identify your device as "ovation".
If you have an SD card handy, I'd suggest that you try the procedure described at https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810. Otherwise, you can try to flash the flashable TWRP zip file available at http://www.mediafire.com/file/3gj4g9j1x363dor/cwm-flashable_twrp-3.0.1-0-ovation.zip.

Thanks guys!
I just ended up using the SD card procedure. TWRP app failed as well. CM11 was slowing to a crawl on the NookHD+ so hopefully Lineage will give it new life!

error 20 on gapps (you don't have Android 7)
Hi, had CM11 on my HD+ for over a year. Unfortunately I left it on til battery completely discharged the other night, and even after charging to 100%, it would only go in a boot loop. (cyanogenmod bootloader, then robot face, then cyanogenmod bootloader again, then robot face again, etc, nonstop). So I thought, why not wipe it and put Lineage on?
So first following the link from this thread, for doing a from scratch install (not the link for if you have CM11 since it wasn't even booting for me, so assuming corrupt),
I got to the point of installing TWRP, and it failed with a zip signature verification error. So okay, I uncheck that verification box, and it appeared to install okay. Onto the lnos zip file. As a precaution, I also unchecked the verification box (thinking it might fail like the TWRP install), and besides a couple messages about "E: unknown command [LOG] " which I ignored (from what I read online can be safely ignored?) , and it took a good while (10 or more minutes? didn't time it) and says "script succeeded: result was [10000000] ,updating partition details, ....done" So I assumed it installed? Then tried installing open_gapps-arm-7.1-pico-20170329.zip, and it fails with "This GApps pkg is for Android 7.1.X only. Please download the correct version for your ROM: 4.4.4.(SDK 19) GApps installation failed No changes were made to your device. Installer will now exit Error Code: 20" and install failed basically. So I reboot and what do you know I still see the CM boot loop going on. Does this mean the old CM11 OS is still installed? Or just a bootloader? And if I press "N" I see TWRP as an option, as well as CM (legacy) So I boot to TWRP and go to Wipe, but this time, do Advanced, and select to wipe all items except external SD. Restart, and same CM boot loop is going on. (I had done the basic Wipe before that)
So something isn't right here, or I'm missing some steps? Any help please?

baytee said:
...
So something isn't right here, or I'm missing some steps? Any help please?
Click to expand...
Click to collapse
Since you're posting in this thread, I can't tell if you have tried the alternative procedure in this thread https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810.

digixmax said:
Since you're posting in this thread, I can't tell if you have tried the alternative procedure in this thread https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810.
Click to expand...
Click to collapse
YES I tried both procedures. In fact I tried that link you have for "installing new" procedure first But it failed on the Gapps part. And like I said the previous CM11 (at least boot part) seems corrupt as its stuck in a boot loop. So ideally if it's not riskier, I was attempting to wipe off the old system. (unless by checking all the boxes except SD, under Wipe, Advanced, I did accomplish that? and just the boot/bootloader portion remains?

baytee said:
...
So first following the link from this thread, for doing a from scratch install (not the link for if you have CM11 since it wasn't even booting for me, so assuming corrupt),
I got to the point of installing TWRP, and it failed with a zip signature verification error. So okay, I uncheck that verification box, and it appeared to install okay. Onto the lnos zip file. As a precaution, I also unchecked the verification box (thinking it might fail like the TWRP install), and besides a couple messages about "E: unknown command [LOG] " which I ignored (from what I read online can be safely ignored?) , and it took a good while (10 or more minutes? didn't time it) and says "script succeeded: result was [10000000] ,updating partition details, ....done" So I assumed it installed? Then tried installing open_gapps-arm-7.1-pico-20170329.zip, and it fails with "This GApps pkg is for Android 7.1.X only. Please download the correct version for your ROM: 4.4.4.(SDK 19) GApps installation failed No changes were made to your device. Installer will now exit Error Code: 20" and install failed basically. So I reboot and what do you know I still see the CM boot loop going on. Does this mean the old CM11 OS is still installed? Or just a bootloader?
Click to expand...
Click to collapse
It appears that the old CM11 ROM is still there, the "... succeed ... " message notwithstanding.
The problem behavior seems to be pointing to the possibility that your EMMC is hosed (not readable/writeable). You can test this by trying to re-install stock ROM (see #6 of https://forum.xda-developers.com/showthread.php?t=2062613).
And if I press "N" I see TWRP as an option, as well as CM (legacy)
Click to expand...
Click to collapse
These are just the choices of TWRP & CWM recovery available on the SD.
So I boot to TWRP and go to Wipe, but this time, do Advanced, and select to wipe all items except external SD. Restart, and same CM boot loop is going on. (I had done the basic Wipe before that)
...
Click to expand...
Click to collapse
You should never need to wipe anything other than /data and /cache (/system typically gets wiped automatically (aka reformatted) as part of the process of flashing a new ROM version).

digixmax said:
It appears that the old CM11 ROM is still there, the "... succeed ... " message notwithstanding.
The problem behavior seems to be pointing to the possibility that your EMMC is hosed (not readable/writeable). You can test this by trying to re-install stock ROM (see #6 of https://forum.xda-developers.com/showthread.php?t=2062613).
.
Click to expand...
Click to collapse
I downloaded the stock rom zip , put it on sdcard, booted to TWRP, didn't do any Wipe but clicked Install, chose that zip, unchecked zip signature verification, swiped to start it, get:
"Failed to retouch '/system/lib/libemoji.so'.
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/NookHDplus-stock-2.1.1.-rooted.zip'
Updating partition details...
...done
So, any hope for my HD+ ? If eMMC IS hosed as you mention, what causes this? And are there any tricks to UN-Hose it? Or is it now a useless dead tablet? Why would my battery going to zero screw things up so badly?

baytee said:
I downloaded the stock rom zip , put it on sdcard, booted to TWRP, didn't do any Wipe but clicked Install, chose that zip, unchecked zip signature verification, swiped to start it, get:
"Failed to retouch '/system/lib/libemoji.so'.
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/NookHDplus-stock-2.1.1.-rooted.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
To flash stock ROM you need CWM version 6.0.2.8 attached at the end of the post I referenced.
So, any hope for my HD+? If eMMC IS hosed as you mention, what causes this? And are there any tricks to UN-Hose it? Or is it now a useless dead tablet?
Click to expand...
Click to collapse
If your EMMC is dead, you can try to run CM11 entirely off an SD card -- see https://iamafanof.wordpress.com/201...-4-4-4-for-bricked-no-emmc-nook-hd-04nov2014/.

My Hd is one of those that won't reliably boot to sd card. Any possibility for unbricking , Similar to these (though these steps are for nook tablet, not HD)?
https://forum.xda-developers.com/showthread.php?t=1513583http://bishoptec.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/

baytee said:
My Hd is one of those that won't reliably boot to sd card. Any possibility for unbricking , Similar to these (though these steps are for nook tablet, not HD)?
https://forum.xda-developers.com/showthread.php?t=1513583http://bishoptec.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Click to expand...
Click to collapse
That "tool" for unbricking the NT also boots and runs off a SD card.

While it never reliably booted to the cm11 OS on the sdcard, it's been booting okay lately to recovery at least Twrp maybe even cwm , so assuming I can boot to those , again,does that repair option for NT also work for HD+?

baytee said:
While it never reliably booted to the cm11 OS on the sdcard, it's been booting okay lately to recovery at least Twrp maybe even cwm , so assuming I can boot to those , again,does that repair option for NT also work for HD+?
Click to expand...
Click to collapse
The NT unbricking tool only works for the NT.
Assuming your EMMC is not dead, and its factory-installed partition structure is not corrupted or altered, you can accomplish the same end-goal as the NT tool does by re-flashing to stock ROM using the files linked in the post I had referenced in my earlier reply.

​
digixmax said:
The NT unbricking tool only works for the NT.
Assuming your EMMC is not dead, and its factory-installed partition structure is not corrupted or altered, you can accomplish the same end-goal as the NT tool does by re-flashing to stock ROM using the files linked in the post I had referenced in my earlier reply.
Click to expand...
Click to collapse
Thank you but again , i tried that already and it failed, which is why I was asking if any of those procedures in the links I posted would work, which u already indicated the NT one wouldn't. I've seen various other xda posts talking about either ADB or partitioning or formatting commands. Was just hoping this HD+ wasn't dead and that I could somehow hack this back to life instead of chucking it in the trash....

baytee said:
​
Thank you but again , i tried that already and it failed, which is why I was asking if any of those procedures in the links I posted would work, which u already indicated the NT one wouldn't. I've seen various other xda posts talking about either ADB or partitioning or formatting commands. Was just hoping this HD+ wasn't dead and that I could somehow hack this back to life instead of chucking it in the trash....
Click to expand...
Click to collapse
The stock rom you tried to install was the rooted version that I customized. Try a plain stock rom from that same thread. Try an older version. That error was a common one for some devices.
Sent from my SM-T707V using XDA Premium HD app

Will this guide also work on the Nook HD? (Using the equivalent Hummingbird files, of course).

Create Stock Recovery.img from FTF File

Hi, I am in the process of preparing for upgrading from 7.0 to 7.1.1
I know I need to replace the Custom Kernel with the Stock Kernel. And I have to replace TWRP with Stock Recovery.
Can anybody tell me, which file inside the FTF is the stock recovery? I already found the kernel. Need help to find the stock recovery, thank you!

tempurastyle said:
Need help to find the stock recovery, thank you!
Click to expand...
Click to collapse
We don't have one which is why we have to use TWRP.

So my only way is to flash via Flashtool without wipe?

tempurastyle said:
So my only way is to flash via Flashtool without wipe?
Click to expand...
Click to collapse
Do that then mod your own kernel. [How To] make your own XPERIA DRM-fix kernel.
And flash a TWRP.img to the recovery partition.

fotakernel.sin reside's where we flash twrp on stock. you do not need to flash it to upgrade, contrary you can exclude it in flashtool and keep twrp between updates.

realtuxen said:
fotakernel.sin reside's where we flash twrp on stock. you do not need to flash it to upgrade, contrary you can exclude it in flashtool and keep twrp between updates.
Click to expand...
Click to collapse
this is real knowledge, thanks! so just to be sure, this is what i will do in flashtool:
1) wipe: nothing selected
2) exclude: fotakernel.sin selected
can anybody confirm this is correct?
then after this, i will flash a custom kernel via fastboot and magisk via twrp.
one question regarding magisk: will it be deleted during the flashtool update?

So I ran into a problem...
The Upgrade to 7.1.1 via flashtool was smooth. Then, i flashed twrp via fastboot as usual. When I tried to enter twrp, i get a password prompt to decrypt the phone. So i don't know which password i need to type in. I tried the unlock PIN, doesnt work. Any suggestions?

tempurastyle said:
Any suggestions?
Click to expand...
Click to collapse
To get round that you need to run the following commands...
Code:
fastboot format userdata
fastboot format cache
...so you'll need to backup all your data first.

XperienceD said:
To get round that you need to run the following commands...
Code:
fastboot format userdata
fastboot format cache
...so you'll need to backup all your data first.
Click to expand...
Click to collapse
Ok, so I decided to keep my data and don't install twrp. Now I got another issue, is it possible to install Magisk without TWRP? I already got my kernel using my ta backup according to the instructions a few posts above, which really works great.

tempurastyle said:
Ok, so I decided to keep my data and don't install twrp. Now I got another issue, is it possible to install Magisk without TWRP? I already got my kernel using my ta backup according to the instructions a few posts above, which really works great.
Click to expand...
Click to collapse
I thought you excluded fotakernel so you did not have to flash twrp again. Oh well anyway you can use twrp to flash zips just fine although /data is encrypted, most flash zips do not write to /data anyway some like supersu use /cache (which is not encrypted contrary to the info above) to get around encryption at next boot. And like magisk also patch the boot.img live on your phone, some write to /system which is not encrypted either, I never seen a flash zip that did write to /data. Only backup/browsing/etc on /data is affected.
So when presented with the password screen in twrp just press cancel and make sure the zip you want to flash is located on the external sd card (do not encrypt this in phone settings, your card will be unreadable from pcs to) then choose flash zip and choose the external sdcard to pick the zip from and flash magisk or whatever. You need to run your kernel through ta poc or rootkernel first and disable dm verity and sony ric. (you write you did this so just install twrp and flash away) Do not wipe cache before rebooting just in case magisk uses this in a similar way to supersu (I have no idea)

Also if you do the above fastboot format commands suggested in post#8 without disabling 'forceencrypt' for /data (fstab in the kernel image or with a tool) the phone will encrypt itself again as soon as you turn it on.
If forceencrypt is disabled the same can be achieved (clearing encryption) with a factory reset btw.
So if you did not bump into the password in twrp before you likely did a factory reset with a kernel with encryption disabled. Then, maybe after updating you rebooted stock and the phone encrypted itself again, then now you can not access /data in twrp. Thats also because we have no version of it that supports encryption on the X-compact though. Again do not worry, I have not meet a zip I could not flash, supersu, magisk, etc because they do not access /data anyway.

realtuxen said:
I thought you excluded fotakernel so you did not have to flash twrp again. Oh well anyway you can use twrp to flash zips just fine although /data is encrypted, most flash zips do not write to /data anyway some like supersu use /cache (which is not encrypted contrary to the info above) to get around encryption at next boot. And like magisk also patch the boot.img live on your phone, some write to /system which is not encrypted either, I never seen a flash zip that did write to /data. Only backup/browsing/etc on /data is affected.
So when presented with the password screen in twrp just press cancel and make sure the zip you want to flash is located on the external sd card (do not encrypt this in phone settings, your card will be unreadable from pcs to) then choose flash zip and choose the external sdcard to pick the zip from and flash magisk or whatever. You need to run your kernel through ta poc or rootkernel first and disable dm verity and sony ric. (you write you did this so just install twrp and flash away) Do not wipe cache before rebooting just in case magisk uses this in a similar way to supersu (I have no idea)
Click to expand...
Click to collapse
Yes, after the first upgrade attempt, i let twrp untouched. then when entering twrp, i didnt have a password, so i skipped it. i couldn't find the sd card in the file browser, and after i hit reboot in twrp the phone restarted and got stuck in boot.
So I flashed again, this time deleting twrp. the initial boot up went fine. Then i flashed twrp again and once again, without having a password, i just skipped the password prompt. still couldnt find the sd card, and i rebooted out of twrp. and the phone got stuck again.
after 2-3 trials, i figured out that everytime i rebooted out of twrp, the phone gets stuck during boot. even after turning it off and on, so a reflash was needed.
now i have given up using twrp, so i have an unrooted phone with an unlocked bootloader. which does not allow me to use android pay. i think to solve my problem is:
1) i need to know which twrp version really works, i have tried
this version
and this version
both cause a boot failure for me
2) i need to find the sd card location in the twrp file browser (all the folders show empty for me)
if nothing works, i guess i need to wipe my phone, but that's what i would like to avoid. thanks for your help guys!

tempurastyle said:
Yes, after the first upgrade attempt, i let twrp untouched. then when entering twrp, i didnt have a password, so i skipped it. i couldn't find the sd card in the file browser, and after i hit reboot in twrp the phone restarted and got stuck in boot.
So I flashed again, this time deleting twrp. the initial boot up went fine. Then i flashed twrp again and once again, without having a password, i just skipped the password prompt. still couldnt find the sd card, and i rebooted out of twrp. and the phone got stuck again.
after 2-3 trials, i figured out that everytime i rebooted out of twrp, the phone gets stuck during boot. even after turning it off and on, so a reflash was needed.
now i have given up using twrp, so i have an unrooted phone with an unlocked bootloader. which does not allow me to use android pay. i think to solve my problem is:
1) i need to know which twrp version really works, i have tried
this version
and this version
both cause a boot failure for me
2) i need to find the sd card location in the twrp file browser (all the folders show empty for me)
if nothing works, i guess i need to wipe my phone, but that's what i would like to avoid. thanks for your help guys!
Click to expand...
Click to collapse
The 2. issue with the sdcard is easy. After pressing 'install' button in twrp at the bottom left press the "select storage' button, a small window will pop up then select the 'micro sdcard' and press 'ok", you should see your files now.
The 1. ssue is really odd! I use the second twrp you posted, for some wierd reason the first one does not boot for me (twrp does not start). But I talked with another guy for him it was the other way around. It was really strange. I think most can use both though without problems
There is one more twrp 3.1 from bambamx, but I really do not get this, twrp boots from its own partition with its own kernel. They should be separated unless twrp does something to system ofcause which it very well shouldn't unless you ask it to, deleting a important file or flashing something. I have never heard of this sorry. One thing is certain our device sure could use a stable nougat encryption compatible twrp!
I will let you know if I find something, you can try the last available version, I have no idea if it will exhibit the same strange behaviour. But maybe its worth a shot although it seems something else is at play.
A couple of stupid questions sorry; You disabled dm verity and sony ric in ta poc right, and it does not happen if you boot your phone normal a couple of times.
Edit: sorry Mr. Sandman had not left so I did not read properly here from the morning. I will edit my post to actually answer as best as I can lol.

Just to let you know:
1. You do not need to install TWRP to use it! You can just do
Code:
fastboot boot <TWRP image>
to run TWRP on the phone (instead of
Code:
fastboot flash boot <TWRP image>
). The only drawback of this method is that you will always need a computer to enter TWRP. Btw. with this method you can also try out a custom kernel image before flashing it.
2. You do not need write access to /data partition to install Magisk. It was explained in another thread that Magisk can use /cache temporary when access to /data is not available. It will write to /data on first boot instead.
3. While using TWRP you can use adb to transfer files onto the phone, so you don't need to have them ready on the internal storage.

realtuxen said:
The 2. issue with the sdcard is easy. After pressing 'install' button in twrp at the bottom left press the "select storage' button, a small window will pop up then select the 'micro sdcard' and press 'ok", you should see your files now.
Click to expand...
Click to collapse
I did, but the SD card can't be selected, and the size shows as 0kb. I did a workaround though: i formatted a spare sd card and copied magisk on it. it was instantly recognized and selectable.
ypnos42 said:
Just to let you know:
1. You do not need to install TWRP to use it! You can just do
Code:
fastboot boot <TWRP image>
to run TWRP on the phone (instead of
Code:
fastboot flash boot <TWRP image>
). The only drawback of this method is that you will always need a computer to enter TWRP. Btw. with this method you can also try out a custom kernel image before flashing it.
3. While using TWRP you can use adb to transfer files onto the phone, so you don't need to have them ready on the internal storage.
Click to expand...
Click to collapse
GREAT advice! I launched TWRP from ADB and successfully flashed Magisk using ADB sideload. Thanks, my phone is rooted again!

Trouble Permanently Flashing TWRP

Hi,
I'm currently using the Skipsoft Android Toolkit to unlock flash TWRP onto my device. I've followed to first steps (install drivers, backup device and unlock bootloader) to the letter and everything went smooth.
Now the final part of installing TWRP is not going so well. Flashing the custom recovery works as expected and I end up in the TWRP menu. However, as soon as I reboot my phone and try to go back to the recovery via Advanced Reboot --> recovery, I end up in the default One Plus Recovery Menu. Now the tool mentioneds when this process fails, renaming the Recovery Restore Files is recommend to prevent the system from flashing the stock recovery on boot (what happens to my device). I follow this option in which I end up back in TWRP, flash a zip named 'permanent-recovery.zip' (while read only mode is turned off in TWRP) and reboot my device. Still when I use Advanced Reboot to open recovery, I end up once again in the Stock Recovery.
Is there anyone who could tell me where I am going wrong and how to solve this issue?
Thanks in advance

Rawrden said:
Hi,
I'm currently using the Skipsoft Android Toolkit to unlock flash TWRP onto my device. I've followed to first steps (install drivers, backup device and unlock bootloader) to the letter and everything went smooth.
Now the final part of installing TWRP is not going so well. Flashing the custom recovery works as expected and I end up in the TWRP menu. However, as soon as I reboot my phone and try to go back to the recovery via Advanced Reboot --> recovery, I end up in the default One Plus Recovery Menu. Now the tool mentioneds when this process fails, renaming the Recovery Restore Files is recommend to prevent the system from flashing the stock recovery on boot (what happens to my device). I follow this option in which I end up back in TWRP, flash a zip named 'permanent-recovery.zip' (while read only mode is turned off in TWRP) and reboot my device. Still when I use Advanced Reboot to open recovery, I end up once again in the Stock Recovery.
Is there anyone who could tell me where I am going wrong and how to solve this issue?
Thanks in advance
Click to expand...
Click to collapse
The basic "mechanics" of what happens seems to still be as follows:
As your phone is delivered with Stock OS, it has these two files installed:
Code:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
I know from looking at mine when I got it that it had /system/recovery-from-boot.p installed. If it's there, it is run when it runs at boot.
To stop that behavior you have to get rid of those files before you reboot the first time from recovery or else recovery will be replaced with the stock image. I'm aware that supposedly the custom recovery supposedly renames either one or the other or both of these but am not convinced it does this or whether installing root (either Magisk or SuperSU) does it. Either way, since you're stuck with the problem, either from file-manager in TWRP if that's all you can boot to, you need to rename /system/recovery-from-boot.p to something like /system/recovery-from-boot.p.orig and maybe the other one /system/etc/install-recovery.sh to /system/etc/install-recovery.sh.orig as well.
Once even the .p file is gone, it's not going to rewrite recovery. You must, of course, be rooted before you can touch those files although if you can sideboot TWRP, it seems like you are rooted while it is booted and "should" have access to system files if you can mount system rw.
I've fixed it this way on other phones. On this one, installing the "official" TWRP and Magisk did it. When I booted into /system after installing Magisk, I looked for the .p file and found it renamed to /system/recovery-from-boot.bak.
I found a link for a Samsung s8 for the same purpose. It's probably identical. http://www.teamandroid.com/2017/04/25/install-galaxy-s8-twrp-310-recovery/3/
Click to expand...
Click to collapse

I looked into those two files while in TWRP and noticed I only had the recovery-from-boot.p file. This was already in fact renamed to recovery-from-boot.p.bak. I renamed it once again (just to be sure) and after flashing the .zip I mentioned earlier, the TWRP did not last another reboot...
Can I after flashing TWRP again, immediately flash Magsik? I intended to hold off rooting because the rom I was going to install has Magisk build into it. I don't want to create a conflict when flashing later on. Is this going to be an issue?
@hachamacha I've reread your post and wondering if rooting my device is even going to make a difference right now? Since I'm already able to rename files in the system directory, would it even make a difference?

Rawrden said:
I looked into those two files while in TWRP and noticed and only had the recovery-from-boot.p file. This was already in fact renamed to record-from-boot.p.bak. I renamed it once again (just to be sure) and after flashing the .zip I mentioned earlier, the TWRP did not last another reboot...
Can I after flashing TWRP again, immediately flash Magsik? I intended to hold off rooting because the rom I was going to install has Magisk build into it. I don't want to create a conflict when flashing later on. Is this going to be an issue?
Click to expand...
Click to collapse
To me, it doesn't sound like a conflict to re-install Magisk over itself in FOS and see if that helps. The real "action" that counts is all about whether you've already booted into the OS after installing TWRP and then how you go about getting rid of the .p file without doing a regular reboot via the OS. Even installing the FOS ROM should get rid of the .p file (rename it), so something else is going on. I'll look around some more and update this if I can.
By the way: Depending upon how exactly you got from TWRP to the OS the first time, it could already have rewritten the stock recovery by the time you noticed *.p file renamed to *.bak.
OK: I recalled how I did this without a problem: I wrote instructions somewhere but have no idea where. This is what I think I did:
1) fastboot flash recovery recovery.img (custom/TWRP)
2) fastboot boot recovery.img (so force it to load recovery without a traditional reboot).
3) install ROM from that point and after done just hit the reboot button (or install Magisk from that point and hit reboot).
Click to expand...
Click to collapse
---------- Post added at 09:26 AM ---------- Previous post was at 08:59 AM ----------
Rawrden said:
@hachamacha I've reread your post and wondering if rooting my device is even going to make a difference right now? Since I'm already able to rename files in the system directory, would it even make a difference?
Click to expand...
Click to collapse
Just saw this note:
Anytime you're in TWRP, you're automatically "rooted" for the time you're there. It's integral to TWRP having permissions to do anything like install etc. If you just "loaded" TWRP (as in fastboot boot twrprecovery.img) then you'd be rooted, but when you rebooted to the system, you'd be unrooted. While you were in TWRP, in theory you could make file system changes to the /system partition (a) if TWRP lets you mount it rw which I think that first swipe does and b) if you can see the correct files in it's file manager.
So it "seems" like those file changes should be actual file changes to the correct place. Keep in mind that while booted in TWRP, TWRP may have it's own ./system/ that has nothing to do with the OS's ./system folder, so you've got to be able to mount the OS's ./system. TWRP's ./system is already fine and of no importance for this. I can boot mine into TWRP and look around to try to clear this up, but it might not be crystal clear to me either.
The output of a TWRP terminal emulator "mount" command might be of use but it will be messy. Maybe if you can do this in emulator from TWRP:
# mount | grep system, and look at that output, perhaps put it in this post, it'd be of help. The mounted rw ./system we need is going to be the same one you'd see from adb shell or terminal emulator while booted from the OS. My guess is that the one we don't want from TWRP's perspective will be mounted as /system (params...) and that the the OS's system either will not yet be mounted and you'll have to go to mounts and mount it and then look at the output of the mount cmd again to figure out what it was mounted as. Sorry about how complicated this explanation has become. Anyway: The ./system that corresponds to the OS is the only one we care about.
There's no easy way to explain it so I'll leave it hidden to spare anyone having to look at it:
I just booted into TWRP and used terminal emulator and file manager to explore:
findings: While in TWRP, using terminal emulator to do a
$ df and then a $ mount command shows no ./system mounted specifically. // maybe not a surprise.
// TWRP just mounts it's root / file system and there is a /system folder, just not a specific mount point for it.
// TWRP does not auto mount the OS's ./system partition by default. It depends what you're going to do there.
Without going into "mounts" and clicking on /system, it won't even try to mount /system for the OS.
If you can get that mount to work in read/write mode, then you should be able to see the ./system mount using terminal emulator as such.
$ mount | grep -i system (and look specifically for ./system on the right side of whatever appears).
In theory you should be able to make changes to the OS's /system partition now. When you're done, unmount it. (I'm assuming all this works from TWRP, a dodgy assumption)
At this point: I'm just trying to figure out how TWRP does things like installs OS zips to the /system & /data partitions which it is clearly successfully able to do. It could do it without mounting anything because it could use the linux dd command, which just writes to the /dev name. OR: It could mount /system and use it. I'm not sure which.

hachamacha said:
OK: I recalled how I did this without a problem: I wrote instructions somewhere but have no idea where. This is what I think I did:
Quote:
Code:
1) fastboot flash recovery recovery.img (custom/TWRP)
2) fastboot boot recovery.img (so force it to load recovery without a traditional reboot).
3) install ROM from that point and after done just hit the reboot button (or install Magisk from that point and hit reboot).
Click to expand...
Click to collapse
I followed these steps and I managed to install FreedomOS without any issues. My phone booted normally and after a few complimentary steps I booted back into recovery and... TWRP! No more stock recovery. Thanks a lot!
Just one more question: TWRP currently asks whether it is allowed to install itself as a system app. Now I assume it is already a system app, but I'm not expert at this so I can't say for sure. Would you recommend me to install TWRP as a system app?

Rawrden said:
I followed these steps and I managed to install FreedomOS without any issues. My phone booted normally and after a few complimentary steps I booted back into recovery and... TWRP! No more stock recovery. Thanks a lot!
Just one more question: TWRP currently asks whether it is allowed to install itself as a system app. Now I assume it is already a system app, but I'm not expert at this so I can't say for sure. Would you recommend me to install TWRP as a system app?
Click to expand...
Click to collapse
Great! Glad that worked. I guess it's all about how that first boot to the OS occurs.
Anyway: Your question, I'm assuming is about TWRP "Manager" the app? If so, yes, it should be a system app. The thing is that "Official TWRP Manager" doesn't really do much of use that you wouldn't just as soon do from fastboot, so it's not critical and nothing other than TWRP manager will "not work" regardless of what you designate it. All saying it's a system app does is puts a slot for it in Magisks "root table".
Cheers.

hachamacha said:
Great! Glad that worked. I guess it's all about how that first boot to the OS occurs.
Anyway: Your question, I'm assuming is about TWRP "Manager" the app? If so, yes, it should be a system app. The thing is that "Official TWRP Manager" doesn't really do much of use that you wouldn't just as soon do from fastboot, so it's not critical and nothing other than TWRP manager will "not work" regardless of what you designate it. All saying it's a system app does is puts a slot for it in Magisks "root table".
Cheers.
Click to expand...
Click to collapse
Done! Can I just say how grateful I am to you for helping me out with this? Your answers have been extremely detailed and I've learned quite a few things. Unfortunately I can only thank your posts once, because you've earned more than that. Thanks again and keep being awesome!

Need help. Infected by malware, flashing factory image doesnt help.

Hi All,
Im pretty close now to throwing Nexus 6p into the wall. Im honestly desperate now.. Few weeks ago replaced battery and usb dock.. and now Im infected by malware which I cannot even remove. Trying different methods for a week now.
Ads pop up (saying Im won something most of the times) in chrome after factory reset without any apps installed, before I even log in to google or anywhere. Same happens on different wifi networks and 3g.
What I tried up to now:
1. Factory reseting through android,
2. Factory reseting and clearing system cache through bootloader
3. Flashing new image from https://developers.google.com/android/images. Im not very familiar with this so had few issues: during procedure "flash-all.sh" - it did not work - nothing happend after trying to run it. So I did (or at least tried) to use this tutorial https://forum.xda-developers.com/nexus-6p/general/tutorial-how-to-flash-factory-image-t3252931 - Method no. 2. Managed to do almost everything apart these lines "fastboot flash userdata C:/images/userdata.img" and "fastboot flash cache C:/images/cache.img" because they are simply not in the zip file of image I got from google.
After all this, phone restarted fine, but still came up with ads as soon as I open any few pages in chrome.
Could you please help me this this to guide through what to do? I spent ages on google trying to find exact solution but some are old, some I dont get, some without clear instructions what to do...
Appreciate your time guys,

On one post I found that sequence what needs to be installed should be:
"fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash cache C:\angler\images\cache.img
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
On 7.1.2 and above you'll also need to boot into TWRP recovery and wipe cache and dalvik cache. "
What does last line mean? What is TWRP recovery, dalvik cache?

BenasJ said:
On one post I found that sequence what needs to be installed should be:
"fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash cache C:\angler\images\cache.img
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
On 7.1.2 and above you'll also need to boot into TWRP recovery and wipe cache and dalvik cache. "
What does last line mean? What is TWRP recovery, dalvik cache?
Click to expand...
Click to collapse
What you need to do is backup all your downloads , music, pictures and anything you've saved in the internal memory. Then go to wipe in twrp and select everything inc internal. That is where it's probably hiding and factory reset won't erase your storage only with internal wipe. But remember you will loose everything so do a manual backup onto desktop or thumb drive. Then you can go flash whatever you please. I'm on the latest 8.1 April and it's working flawlessly. You don't have to wipe davlick and cache after factory flash just good practice to avoid any hiccups like hanging on first boot.

Exodusche said:
What you need to do is backup all your downloads , music, pictures and anything you've saved in the internal memory. Then go to wipe in twrp and select everything inc internal. That is where it's probably hiding and factory reset won't erase your storage only with internal wipe. But remember you will loose everything so do a manual backup onto desktop or thumb drive. Then you can go flash whatever you please. I'm on the latest 8.1 April and it's working flawlessly. You don't have to wipe davlick and cache after factory flash just good practice to avoid any hiccups like hanging on first boot.
Click to expand...
Click to collapse
Is there a easier way to do this? As I understand I would need to have my phone rooted, to do this I need to to have twrp, to have it I need to install custum recovery through bootloader....
Is there a easier way to just to wipe all the internal data?
Can someone please just give quick sequence what after what needs to be done? Taking into account I got stock non rooted android 8.1. (I dont give a .. about photos and videos, whats the simplest way to make phone functioning as it supposed to again)
Thanks

BenasJ said:
Is there a easier way to do this? As I understand I would need to have my phone rooted, to do this I need to to have twrp, to have it I need to install custum recovery through bootloader....
Is there a easier way to just to wipe all the internal data?
Can someone please just give quick sequence what after what needs to be done? Taking into account I got stock non rooted android 8.1. (I dont give a .. about photos and videos, whats the simplest way to make phone functioning as it supposed to again)
Thanks
Click to expand...
Click to collapse
I suppose you can use fastboot command "fastboot format userdata". I'm not sure if it would effect your current install but shouldn't.

Hi.
Flashed image again and ran command: "fastboot format userdata".
However again no luck.. still same anoying advert after doing few clicks in browser..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any ideas?

BenasJ said:
Hi.
Flashed image again and ran command: "fastboot format userdata".
However again no luck.. still same anoying advert after doing few clicks in browser..
Any ideas?
Click to expand...
Click to collapse
My opinion/idea/fix:
1. Unlock bootloader
2. Backup your recovery stock thing (Using Nexus Toolkit, google it)
2. Flash Custom Recovery (TWRP recovery zip, using adb)
3. Boot to Recovery (TWRP)
4. Wipe everything EXCEPT bootloader and recovery
5. Flash the 2nd step backed up recovery.img using TWRP recovery, to recovery partition.
.....
Procced with the stock steps you followed earlier and failed.
Not sure if I am clear.
Also not sure if you know how to do the steps.
I can help you try the solution I described tho, let me know!

Pipiou211 said:
My opinion/idea/fix:
1. Unlock bootloader
2. Backup your recovery stock thing (Using Nexus Toolkit, google it)
2. Flash Custom Recovery (TWRP recovery zip, using adb)
3. Boot to Recovery (TWRP)
4. Wipe everything EXCEPT bootloader and recovery
5. Flash the 2nd step backed up recovery.img using TWRP recovery, to recovery partition.
.....
Procced with the stock steps you followed earlier and failed.
Not sure if I am clear.
Also not sure if you know how to do the steps.
I can help you try the solution I described tho, let me know!
Click to expand...
Click to collapse
Hi, Thank you for responding!
Before you posted your message thats what I did:
1. Replaced/reflashed recovery.img with twrp
2. Inside TWRP (opened trough bootloader holding power + down...) in advanced wipe options, wiped everything possible
3. Rebooted into bootloader and using ./fastboot commands flashed bootloader, radio, boot, recovery, system, vendor with stock image
4. Replaced/reflashed recovery.img with twrp again
5. Wiped cache and dalvik cache
Still the same problem..
What I can understand I pretty much did what you suggested, correct? I dont have access to Windows pc untill Monday so cannot use Nexus Toolkit. But thanks for recomending it! I'll look into it

BenasJ said:
Hi, Thank you for responding!
Before you posted your message thats what I did:
1. Replaced/reflashed recovery.img with twrp
2. Inside TWRP (opened trough bootloader holding power + down...) in advanced wipe options, wiped everything possible
3. Rebooted into bootloader and using ./fastboot commands flashed bootloader, radio, boot, recovery, system, vendor with stock image
4. Replaced/reflashed recovery.img with twrp again
5. Wiped cache and dalvik cache
Still the same problem..
What I can understand I pretty much did what you suggested, correct? I dont have access to Windows pc untill Monday so cannot use Nexus Toolkit. But thanks for recomending it! I'll look into it
Click to expand...
Click to collapse
Yea, it's the same idea/thing.
Good luck ... Professionals of XDA community should help you clean this malware.
It is obviously a strong **** ...
It obviously can draw attention !!
---------- Post added at 07:13 PM ---------- Previous post was at 06:56 PM ----------
Worth the double post, yolo.
Is there a chance that someone is having access to your network? Manipulating the html requests? :fingers-crossed:
crying: it combined the posts )

Pipiou211 said:
Yea, it's the same idea/thing.
Good luck ... Professionals of XDA community should help you clean this malware.
It is obviously a strong **** ...
It obviously can draw attention !!
---------- Post added at 07:13 PM ---------- Previous post was at 06:56 PM ----------
Worth the double post, yolo.
Is there a chance that someone is having access to your network? Manipulating the html requests? :fingers-crossed:
crying: it combined the posts )
Click to expand...
Click to collapse
I thought of it aswell, tried at home wifi network, 3g, work wifi network, but exactly same type of ad pop-ups come up on every network. FYI it happens like I said even on completely clean/fresh factory reseted phone before putting any logins or installing anything

BenasJ said:
I thought of it aswell, tried at home wifi network, 3g, work wifi network, but exactly same type of ad pop-ups come up on every network. FYI it happens like I said even on completely clean/fresh factory reseted phone before putting any logins or installing anything
Click to expand...
Click to collapse
It is the real thing !!!
Good luck you will find it, it is an html request for sure!
Or not?

Pipiou211 said:
It is the real thing !!!
Good luck you will find it, it is an html request for sure!
Or not?
Click to expand...
Click to collapse
Thank you for your encouragement I'm getting more and more annoyed.. Another few days without luck and I'll be buying my first iphone if I wont find solution
Let me know if you get any other ideas

Pipiou211 said:
It is the real thing !!!
Good luck you will find it, it is an html request for sure!
Or not?
Click to expand...
Click to collapse
Can you have a look into text file and tell am I doing everything correctly? Its copy of terminal of how I flashed image last time. After this I wipe system data inside recovery and reboot.
Are these 100% correct steps Im doing?
Thanks !!

BenasJ said:
Can you have a look into text file and tell am I doing everything correctly? Its copy of terminal of how I flashed image last time. After this I wipe system data inside recovery and reboot.
Are these 100% correct steps Im doing?
Thanks !!
Click to expand...
Click to collapse
Not in the mood, I have soo long time to flash OTA full or updates .zip(s) anyway, really.
I can give you a solution tho, preety good to go with.
1. Choose between those 2 -stock enough- custom roms:
(MY PERSONAL PREFERENCE)
--- Pure Nexus 7.1.1 (Older Android - Faster - Solid AF)
--- SuperXE 8.1.0 (Latest Android - Slower and maaaybe a little worst battery life - Still Solid, I am using it atm as main ROM)
----
Let me know If I should keep writing, so we can try from zero the attempt I previously mentioned (wiping and reflashing).
In my opinion if you follow the steps I am about to write you SHOULD not believe in your eyes if you still see the virus, or consider that the malware is actually something else, somewhere else and not in your smartphone's ROM or Storage.
(If you wanna go for it, start downloading the ROM files you choosen, it will save you/us time, find them here on XDA Nexus 6P section)
(I will edit this post)
----
2. Follow the steps @Cile381 gives on SuperXE thread, if you have any questions I will respond/help instantly, just use @Pipiou211 so I will receive the notification.
BE VERY VERY VERY CAREFUL with your bootloader, radio and recovery sections, if you leave one of them empty, flash wrong .zip/.img or unplug your smartphone while flashing you will HARDBRICK your device.
Especialy Bootloader.
Update them to be ready for Oreo Android and move to next steps (vendor and rom).

Pipiou211 said:
Not in the mood, I have soo long time to flash OTA full or updates .zip(s) anyway, really.
I can give you a solution tho, preety good to go with.
1. Choose between those 2 -stock enough- custom roms:
(MY PERSONAL PREFERENCE)
--- Pure Nexus 7.1.1 (Older Android - Faster - Solid AF)
--- SuperXE 8.1.0 (Latest Android - Slower and maaaybe a little worst battery life - Still Solid, I am using it atm as main ROM)
2. Let me know If I should keep writing, so we can try from zero the attempt I previously mentioned (wiping and reflashing).
In my opinion if you follow the steps I am about to write you SHOULD not believe in your eyes if you still see the virus, or consider that the malware is actually something else, somewhere else and not in your smartphone's ROM or Storage.
(If you wanna go for it, start downloading the ROM files you choosen, it will save you/us time, find them here on XDA Nexus 6P section)
(I will edit this post)
Click to expand...
Click to collapse
Yes, If you just have time I would be very interested to go through your method! I'm downloading SuperXE 8.1.0 as we speak, but speed is not very consistant from the server (says it could take between 20min and 4 hours to download..) But please guide me through the process if you can. Thank you!

BenasJ said:
Yes, If you just have time I would be very interested to go through your method! I'm downloading SuperXE 8.1.0 as we speak, but speed is not very consistant from the server (says it could take between 20min and 4 hours to download..) But please guide me through the process if you can. Thank you!
Click to expand...
Click to collapse
Sure, updating previous post ....
---------- Post added at 04:48 PM ---------- Previous post was at 04:21 PM ----------
BenasJ said:
Yes, If you just have time I would be very interested to go through your method! I'm downloading SuperXE 8.1.0 as we speak, but speed is not very consistant from the server (says it could take between 20min and 4 hours to download..) But please guide me through the process if you can. Thank you!
Click to expand...
Click to collapse
1.2GB file right? (flashable zip actually) @BenasJ

Pipiou211 said:
Sure, updating previous post ....
---------- Post added at 04:48 PM ---------- Previous post was at 04:21 PM ----------
1.2GB file right? (flashable zip actually) @BenasJ
Click to expand...
Click to collapse
Yes, 1.28 GB. Got it from here: https://forum.xda-developers.com/nexus-6p/development/rom-t3488519

Pipiou211 said:
Sure, updating previous post ....
---------- Post added at 04:48 PM ---------- Previous post was at 04:21 PM ----------
1.2GB file right? (flashable zip actually) @BenasJ
Click to expand...
Click to collapse
@Pipiou211
Quick few question I got:
According to SuperXE instructions I need to:
- Reboot to recovery (Question 1: by recovery it means twrp? do I need to root my phone to do this or just simply replace recovery with twrp using "fastboot flash..." commend like I did before?
- Take necessary backups
- Wipe system/data/cache
- Flash the appropriate vendor.img
- Flash Rom.zip
- Reboot to system
Question 2: Would these be correct - more detailed instructions how to install "Zip" not "IMG" ?
7. How To Install A ROM with TWRP Recovery
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
Installing a ROM is a pretty straight forward and easy process. Before you install anything you should make a nandroid backup (instructions above).
Download a ROM and appropriate Gapps package and place on your device. You'll also need to find out what build your ROM is based on and download the vendor image for that build, you'll find the latest in my index here.
Boot into your custom recovery.
Perform a full wipe.
Select the wipe option from the TWRP home screen.
Select advanced wipe.
Check the system, data, cache, and dalvik cache options.
Swipe to wipe.
Install the ROM.
Select the install option from the TWRP home screen.
Navigate to where you have the ROM zip stored on your internal storage and select it. You can hit the "add more zips" button now to queue up your gapps package to be flashed after the ROM zip.
Swipe to install.
Most ROMs will run an installer script at this point but some ROMs have what is called an Aroma Installer which allow you to choose some install options before the script runs.
Hit the home button once everything has finished installing.
Install the appropriate vendor image.
Select the install option from the TWRP home screen.
Click the "install image" button in the bottom-right corner.
Navigate to where you have the vendor image stored on your internal storage and select it.
You'll now be asked which partition to flash the image to, select vendor.
Swipe to install.
Once you've installed all necessary zips/images you'll have an option to wipe cache/dalvik and an option to reboot system, hit the reboot system button and you'll boot into your new ROM.
If Yes, Question 3: What is Gapps? Do I need it?
Found answer myself for this: Realised that it was shortening for Google apps. As I understand I need ARM64-8.1 android-stock. Correct?
Thanks

BenasJ said:
@Pipiou211
Quick few question I got:
According to SuperXE instructions I need to:
- Reboot to recovery (Question 1: by recovery it means twrp? do I need to root my phone to do this or just simply replace recovery with twrp using "fastboot flash..." commend like I did before?
- Take necessary backups
- Wipe system/data/cache
- Flash the appropriate vendor.img
- Flash Rom.zip
- Reboot to system
Question 2: Would these be correct - more detailed instructions how to install "Zip" not "IMG" ?
7. How To Install A ROM with TWRP Recovery
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
Installing a ROM is a pretty straight forward and easy process. Before you install anything you should make a nandroid backup (instructions above).
Download a ROM and appropriate Gapps package and place on your device. You'll also need to find out what build your ROM is based on and download the vendor image for that build, you'll find the latest in my index here.
Boot into your custom recovery.
Perform a full wipe.
Select the wipe option from the TWRP home screen.
Select advanced wipe.
Check the system, data, cache, and dalvik cache options.
Swipe to wipe.
Install the ROM.
Select the install option from the TWRP home screen.
Navigate to where you have the ROM zip stored on your internal storage and select it. You can hit the "add more zips" button now to queue up your gapps package to be flashed after the ROM zip.
Swipe to install.
Most ROMs will run an installer script at this point but some ROMs have what is called an Aroma Installer which allow you to choose some install options before the script runs.
Hit the home button once everything has finished installing.
Install the appropriate vendor image.
Select the install option from the TWRP home screen.
Click the "install image" button in the bottom-right corner.
Navigate to where you have the vendor image stored on your internal storage and select it.
You'll now be asked which partition to flash the image to, select vendor.
Swipe to install.
Once you've installed all necessary zips/images you'll have an option to wipe cache/dalvik and an option to reboot system, hit the reboot system button and you'll boot into your new ROM.
If Yes, Question 3: What is Gapps? Do I need it?
Thanks
Click to expand...
Click to collapse
1. (YES to Question 1)
Flash TWRP (latest) to recovery partition.
2. PowerButton+VolumeUp and access TWRP.
3. Flash bootloader (the one cile381 "tell you" to)
4. Flash vendor (the one cile381 tells)
5. Wipe>Advanced check everything except Bootloader, Vendor and Recovery (already installed TWRP in our case)
6. Flash SuperXE ROM (chill and have fun with the Aroma Installer guidance, if unsure leave everything unticked and just NEXT, NEXT, NEXT, NEXT!!)
7. Reboot and check for the malware, after first-time-setup (wifi google account and so on).
DO NOT restore application data from previous "phone".
(8. If we get softbrick) Flash latest radio.img, will tell you the way if we get softbricked, we probably dont need that.
---
(Response to Question 2.)
Step 3. and 4. are .img flashing.
Step 6. is .zip file flashing.
To flash .zip file just tap Flash in the TWRP and tap the 1.28GB .zip file.
To flash .img file(s) tap Flash, then a button like 'Image' or something, you will see it there are just two buttons, including 'Back', then tap the .img file and tap the partition you wanna flash/install it.
Am I clear? My english is not the best sorry about that.

Pipiou211 said:
1. (YES to Question 1)
Flash TWRP (latest) to recovery partition.
2. PowerButton+VolumeUp and access TWRP.
3. Flash bootloader (the one cile381 "tell you" to)
4. Flash vendor (the one cile381 tells)
5. Wipe>Advanced check everything except Bootloader, Vendor and Recovery (already installed TWRP in our case)
6. Flash SuperXE ROM (chill and have fun with the Aroma Installer guidance, if unsure leave everything unticked and just NEXT, NEXT, NEXT, NEXT!!)
7. Reboot and check for the malware, after first-time-setup (wifi google account and so on).
DO NOT restore application data from previous "phone".
(8. If we get softbrick) Flash latest radio.img, will tell you the way if we get softbricked, we probably dont need that.
---
(Response to Question 2.)
Step 3. and 4. are .img flashing.
Step 6. is .zip file flashing.
To flash .zip file just tap Flash in the TWRP and tap the 1.28GB .zip file.
To flash .img file(s) tap Flash, then a button like 'Image' or something, you will see it there are just two buttons, including 'Back', then tap the .img file and tap the partition you wanna flash/install it.
Am I clear? My english is not the best sorry about that.
Click to expand...
Click to collapse
@Pipiou211 All clear apart section 3:
3. Flash bootloader (the one cile381 "tell you" to)
In their page cile381 provides only ROM and Vendor. Where do I get bootloader from?