Database Users

Reflashing system partition?

I'm trying to upgrade my SuperSu to the latest beta so I can install Viper4Android for Angler. However, the instructions for SuperSu Beta states "If you are coming from any SuperSU install in /system, you must re-flash the stock system (and vendor and oem, if present) partition contents prior to installing this."
I was wondering if I could get some Nexus 6P specific instructions for doing that without screwing everything up. I assume this doesn't wipe my user apps. Thanks.

If you are comfortable with using ADB and fastboot, follow Section 10 of this guide. All you need to do is "fastboot flash system," just download the factory image that matches your current rom.
http://forum.xda-developers.com/showthread.php?t=3206928
Flashing just the system partition does not wipe app data.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
If you are comfortable with using ADB and fastboot, follow Section 10 of this guide. All you need to do is "fastboot flash system," just download the factory image that matches your current rom.
http://forum.xda-developers.com/showthread.php?t=3206928
Flashing just the system partition does not wipe app data.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Yeah, I'm pretty comfortable using adb and fastboot. I'll try it out. Thanks!.
Quick question, can I keep the TWRP recovery or do I need to flash stock recovery too? Thanks again.

hull22 said:
Yeah, I'm pretty comfortable using adb and fastboot. I'll try it out. Thanks!.
Quick question, can I keep the TWRP recovery or do I need to flash stock recovery too? Thanks again.
Click to expand...
Click to collapse
Cool! There is no need to touch the recovery partition. Just fastboot the system and vendor img's then boot right into TWRP and install SuperSU
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Cool! There is no need to touch the recovery partition. Just fastboot the system and vendor img's then boot right into TWRP and install SuperSU
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I screwed it up. Flashed everything just fine. Didn't have the SuperSu beta on the phone yet, booted to system. It tried to re-encrypt the device. I interrupted it because it seemed to be stuck. Now, I have to factory reset and lose all of my data. Not sure where I have to restart now, root, etc...

hull22 said:
I screwed it up. Flashed everything just fine. Didn't have the SuperSu beta on the phone yet, booted to system. It tried to re-encrypt the device. I interrupted it because it seemed to be stuck. Now, I have to factory reset and lose all of my data. Not sure where I have to restart now, root, etc...
Click to expand...
Click to collapse
Ahh dang, were your able to get set up? If the rom is messed up, you'll likely have to fastboot flash system, boot, and vendor IMG's for the 6.0.1 OTA you already downloaded.
I wasn't aware that you were decrypted, I would have been more expressive about not booting until things were flashed in recovery. SuperSU removes "force encrypt" from the stock boot.img so that would not have occurred.
Sent from my Nexus 5X using Tapatalk

Creating modified boot.img and enabling adb during first boot.

Modified boot.img of a rom is required to be flashed on that rom so that it works with TWRP.
Enabling ADB during first boot creates a way out in case your phone bootloops or stuck at MI logo and also hardbricked.
Many people hardbricked their phone while flashing MIUI based roms through TWRP, and they had to test-point to bring their phone back to life, my mod enables adb during boot and so people who used my mod and hardbricked their phone can access adb when their phone is stuck at MI logo or bootlooping and thus revive their phone.
Tools needed:-
1)Notepad++ (google it and download)
2)Android Image Kitchen(AIK) http://forum.xda-developers.com/attachment.php?attachmentid=3638835&d=1454959265
Steps:-
1)Download the required rom and extract its boot.img
2)Copy the boot.img to AIK folder and drag boot.img and drop it on unpackimg.bat
3)Open ramdisk folder and look for default.prop , open them with Notepad++
4)Editing default.prop Note:- This will enable adb at first boot
5)Change
Code:
ro.secure=1 to ro.secure=0
ro.adb.secure=1 to ro.adb.secure=0
ro.debuggable=0 to ro.debuggable=1
persist.sys.usb.config=none to persist.sys.usb.config=adb
delete the line ro.secureboot.devicelock=1 if present
OR (Alternate way)(recommended)
open ramdisk and look for fstab.qcom, open with notepad++ and search for ",verify" (without quotes) and delete it and save.
6)Now execute repackimg.bat, a image-new.img file will be compiled.
7)Flash the image-new.img through TWRP or through fastboot using "Fastboot flash boot image-new.img"
That's all
P.S:- Remember only use Boot.img specific for the miui version you wanna run, boot.img version not matching with MIUI version
will cause the Wifi to stop working.
Press thanks If this helped.:good:
Any queries feel free to ask me.:laugh:

Does the modified boot.img procedure need to be done for every ROM or just for the MIUI ROMs? I want to install the AOSP ROM and later CM 13 but I'm still not sure about the whole flashing process.
Sent from my Redmi Note 3 using XDA-Developers mobile app

SkinCoffin said:
Does the modified boot.img procedure need to be done for every ROM or just for the MIUI ROMs? I want to install the AOSP ROM and later CM 13 but I'm still not sure about the whole flashing process.
Sent from my Redmi Note 3 using XDA-Developers mobile app
Click to expand...
Click to collapse
modified boot.img is only for official MIUI roms, all other roms doesnt need it

Rajdip said:
modified boot.img is only for official MIUI roms, all other roms doesnt need it
Click to expand...
Click to collapse
So if I'm on Miui Official Global ROM 7.2.3 all I have to do is flash TWRP through fastboot, boot into it and flash the new ROM+GApps through it?

SkinCoffin said:
So if I'm on Miui Official Global ROM 7.2.3 all I have to do is flash TWRP through fastboot, boot into it and flash the new ROM+GApps through it?
Click to expand...
Click to collapse
exactly

Rajdip said:
exactly
Click to expand...
Click to collapse
Thank you! I just did it. It has booted and almost over in the "Optimizing apps" window. Thing is, I did forget to wipe system, data and cache before flashing, should I do it again or will it be fine like this?
EDIT: I rebooted the phone into recovery, wiped system, data and cache, flashed the ROM zip and wiped cache and dalvik cache. I booted the phone and it showed the Mi logo, then 4 circles screen flying around (green, red, blue and yellow) and it has been like this for like 5 min now.. Did I do something wrong? I'm starting to worry to be honest.

SkinCoffin said:
Thank you! I just did it. It has booted and almost over in the "Optimizing apps" window. Thing is, I did forget to wipe system, data and cache before flashing, should I do it again or will it be fine like this?
EDIT: I rebooted the phone into recovery, wiped system, data and cache, flashed the ROM zip and wiped cache and dalvik cache. I booted the phone and it showed the Mi logo, then 4 circles screen flying around (green, red, blue and yellow) and it has been like this for like 5 min now.. Did I do something wrong? I'm starting to worry to be honest.
Click to expand...
Click to collapse
it takes time to boot for the first time, did it boot now?

Rajdip said:
it takes time to boot for the first time, did it boot now?
Click to expand...
Click to collapse
Still hasn't booted. It has been on the flying circles screen for around 10 minutes now. Maybe fastboot twrp again and do the process all over again?

SkinCoffin said:
Still hasn't booted. It has been on the flying circles screen for around 10 minutes now. Maybe fastboot twrp again and do the process all over again?
Click to expand...
Click to collapse
Try again, goto TWRP, wipe system,data,cache,dalvik and flash the rom. Now reboot...

Rajdip said:
Try again, goto TWRP, wipe system,data,cache,dalvik and flash the rom. Now reboot...
Click to expand...
Click to collapse
So I shouldn't reinstall TWRP through fastboot?
EDIT: Ok so I restarted the phone and it booted normally into the ROM, everything seems alright. Will check if I have any problem, if I do I'll just reflash it.

SkinCoffin said:
So I shouldn't reinstall TWRP through fastboot?
Click to expand...
Click to collapse
No, first try what I said, dont wipe cache and dalvik after the rom is flashed

Rajdip said:
No, first try what I said, dont wipe cache and dalvik after the rom is flashed
Click to expand...
Click to collapse
Ok so I restarted the phone and it booted normally into the ROM, everything seems alright. Will check if I have any problem, if I do I'll just reflash it.

SkinCoffin said:
Ok so I restarted the phone and it booted normally into the ROM, everything seems alright. Will check if I have any problem, if I do I'll just reflash it.
Click to expand...
Click to collapse
okay

i do exactly like your tutor...i edit boot.img n delete ",verify"
repack than delete original boot.img, than use moded boot.img... but wifi doesn't work...
where my mistake...?

Mayoz said:
i do exactly like your tutor...i edit boot.img n delete ",verify"
repack than delete original boot.img, than use moded boot.img... but wifi doesn't work...
where my mistake...?
Click to expand...
Click to collapse
are you sure you are using the boot.img of the MIUI version you are flashing? there is two 7.2.3.0 version of boot.img one for global and one for china. Anyway try this and see if wifi works, goto TWRP(I hope you've already deleted the emmc_appsboot file), select mount and then tick on mount system as read only. Then flash the rom. This method will replace TWRP with MIUI recovery but your wifi should start working.

Rajdip said:
are you sure you are using the boot.img of the MIUI version you are flashing? there is two 7.2.3.0 version of boot.img one for global and one for china. Anyway try this and see if wifi works, goto TWRP(I hope you've already deleted the emmc_appsboot file), select mount and then tick on mount system as read only. Then flash the rom. This method will replace TWRP with MIUI recovery but your wifi should start working.
Click to expand...
Click to collapse
yes using the boot.img of the MIUI version to flashing...from recovery rom stable 7.2.3.0 china....maybe my mistake i replace emmc_appsboot file from miui forum...not delete "will replace TWRP with MIUI recovery...' still can booting? i already UBL...

Mayoz said:
yes using the boot.img of the MIUI version to flashing...from recovery rom stable 7.2.3.0 china....maybe my mistake i replace emmc_appsboot file from miui forum...not delete "will replace TWRP with MIUI recovery...' still can booting? i already UBL...
Click to expand...
Click to collapse
I didnt get you, can you be more clear?

Do I need to use Windows 64bits to flash TWRP?
Thanks.

pepemonje said:
Do I need to use Windows 64bits to flash TWRP?
Thanks.
Click to expand...
Click to collapse
no need 32bit works

Hello, I've followed a certain tutorial and flashed a fastboot Rom with modified emmc file in attempt to unlock bootloader by force because, even after two weeks of trying, I can't get a confirmation SMS from xiaomi to confirm sending an unlock request. After doing it and flashing TWRP onto my device, I'm still unable to enter recovery. Just shows a picture of device and a disconnected usb cable. I need to flash SuperSU in order to get root access.
Because this device is getting me really confused, please answer a couple of questions for me.
If I flash a recently uploaded global stable ROM 7.2.3.0. and flash TWRP with a modified boot image from this tutorial, will I finally be able to enter recovery and install SuperSU?
Flashing will probably relock my bootloader. Is it possible for me to finally enter TWRP and flash SuperSU after flashing the new boot image?
I've thought that I could enter TWRP just by unlocking the bootloader but it seems that I've missed something. I can't remember last time a phone got me this confused.
My only goal here is being able to enter TWRP and rooting my phone, I gave up on unlocking the bootloader officially because I can't ever get that confirmation SMS.
I appreciate the help!! :fingers-crossed:

TWRP wont stick keep going to stock

was trying to do a systemless root to use android pay and unrooted my device from the SU app and selected to keep my custom recovery, tried to go into recovery and gave me the stock recovery. Used fastboot to reinstall twrp but after reboot it reverts back to stock, what am i doing wrong.
stock 7.0

Look for a system file called recovery from boot.p (boot.p). Might be your culprit. It's a file , if I recall correctly, that on initial boot overwrites twrp. Puts you back on stock.

You don't need the twrp installed. Just boot to the bootloader and type: fastboot boot twrp-filename.img from your command prompt on your pc.

In order to make sure that custom recovery overwrites twrp, when you have finished flashing twrp, reboot into bootloader immediately. Then flash latest SuperSU. This modifies boot.img so it doesn't overwrite twrp.

so ill fastboot install twrp then i will not reboot into system because if i do the recovery will be overwriten with the old stock recovery. Trying to use a systemless root with magisk

blueyes said:
Look for a system file called recovery from boot.p (boot.p). Might be your culprit. It's a file , if I recall correctly, that on initial boot overwrites twrp. Puts you back on stock.
Click to expand...
Click to collapse
where is the file located, should i replace that file or just delete it. Thank you

Toxin715 said:
where is the file located, should i replace that file or just delete it. Thank you
Click to expand...
Click to collapse
No no no. Try like I mentioned. Flash TWRP then reboot recovery immediately. Then flash SU. This will prevent TWRP from being overwritten
Sent from my Nexus 6P using XDA-Developers mobile app

dratsablive said:
No no no. Try like I mentioned. Flash TWRP then reboot recovery immediately. Then flash SU. This will prevent TWRP from being overwritten
Click to expand...
Click to collapse
OK will do, well give results soon

dratsablive said:
No no no. Try like I mentioned. Flash TWRP then reboot recovery immediately. Then flash SU. This will prevent TWRP from being overwritten
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
ok systemless root with magisk works fine along with twrp sticking now. Things to know is when twrp is booting it still says unable to mount system but everything works fine if that matters. Thank you

Toxin715 said:
ok systemless root with magisk works fine along with twrp sticking now. Things to know is when twrp is booting it still says unable to mount system but everything works fine if that matters. Thank you
Click to expand...
Click to collapse
What version of TWRP are you flashing?
Sent from my Nexus 6P using XDA-Developers mobile app

OS wiped accidentally from TWRP recovery

I accidentally wiped the OS from advanced wipe option. How do I get my phone to work again. I tried to operate adb sideload from recovery but it failed. I have downloaded the stock rom but I do not know how to install it.
Please help.
Thanks.

Kalaxy said:
I accidentally wiped the OS from advanced wipe option. How do I get my phone to work again. I tried to operate adb sideload from recovery but it failed. I have downloaded the stock rom but I do not know how to install it.
Please help.
Thanks.
Click to expand...
Click to collapse
Just flash it from custom recovery, so download it into ur phone go to recovery and simply flash it and all should be good.
Sent from my Nexus 6P using Tapatalk

Exiwolfman said:
Just flash it from custom recovery, so download it into ur phone go to recovery and simply flash it and all should be good.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
How do I download it to my phone if I cannot boot into it. Is there any way I can copy a zip file (rom) onto the phone's internal memory.?

Your phone should boot into recovery, so as long as it goes on and boots all u do u is use ur pc to move file over and flash it...
Sent from my Nexus 6P using Tapatalk

Kalaxy said:
How do I download it to my phone if I cannot boot into it. Is there any way I can copy a zip file (rom) onto the phone's internal memory.?
Click to expand...
Click to collapse
Boot into bootloader (hold power and system on), flash the though recovery through adb, mount your .zip,, flash your .zip through recovery. Sorry if that doesn't make sense, I've been drinking with the roommates, lol.
Edit: if that doesn't work, send me an IM and I will help you in the morning
Sent from my Huawei Nexus 6P using XDA Labs

Which state is your phone in right now? Is it bootlooping or in recovery?
Sent from my HTC 10 using Tapatalk

The same thing happened to me also! The whole /data (incl. sdcard) partition went corrupt (showed up in TWRP as eemc instead of ext4) & the /vendor failed to mount.
First I had to repair the /data partition (unfortunately the data was lost, as it repaired to a blank partition). I ended up having to go home (was at work at the time) & hook the phone up to the PC & download the ROM & transfer it onto the sdcard. I'm not entirely sure why/how this happened, but I believe it was because a corrupt vendor IMG. Although that theory doesnt include why the /data partition corrupted, it only explains why the /vendor partition failed to mount.

Fastboot flash system system.img
?

removed

I have the same issue. The problem is, that my computer will not recognize the phone in bootloader mode or in recovery mode(MTP enabled). How can install usb drivers without being able to boot into phone OS???? I've tried Nexus Toolkit with no success. Please help?

Have a look here how to load in bootloader, flash, etc.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

So I did the same thing. I'm sitting in TWRP right now but have nothing on the phone. Will I be able to reboot from TWRP into the bootloader and just use the flash-all command to get my phone to boot back up, then just go through the process of custom recovery again?
Basically I'm worried about leaving twrp without an OS. I didn't wipe bootloader did I? Also, I tried to download a ROM and just drag it to internal memory, but I can't seem to add anything to the internal memory.

dbroer91884 said:
So I did the same thing. I'm sitting in TWRP right now but have nothing on the phone. Will I be able to reboot from TWRP into the bootloader and just use the flash-all command to get my phone to boot back up, then just go through the process of custom recovery again?
Basically I'm worried about leaving twrp without an OS. I didn't wipe bootloader did I? Also, I tried to download a ROM and just drag it to internal memory, but I can't seem to add anything to the internal memory.
Click to expand...
Click to collapse
Hi... Just boot into recovery and reflash system.img from the factory image of your choice in bootloader with fastboot. Also flash the vendor image from the same factory image. Done...
Or reflash the whole package with flash all (manually is better imho). But you'll waisted time... Let your phone reboot into Android and you'll have your internal storage back.

5.1 said:
Hi... Just boot into recovery and reflash system.img from the factory image of your choice in bootloader with fastboot. Also flash the vendor image from the same factory image. Done...
Or reflash the whole package with flash all (manually is better imho). But you'll waisted time... Let your phone reboot into Android and you'll have your internal storage back.
Click to expand...
Click to collapse
Thats what I thought. JUst wanted to make sure I could get into bootloader still

dbroer91884 said:
So I did the same thing. I'm sitting in TWRP right now but have nothing on the phone. Will I be able to reboot from TWRP into the bootloader and just use the flash-all command to get my phone to boot back up, then just go through the process of custom recovery again?
Basically I'm worried about leaving twrp without an OS. I didn't wipe bootloader did I? Also, I tried to download a ROM and just drag it to internal memory, but I can't seem to add anything to the internal memory.
Click to expand...
Click to collapse
Yes TWRP has a reboot to bootloader option available. So you can access fastboot via bootloader to flash the necessary images. Just don't forget to re flash TWRP image again in case the stock recovery image was flashed beforehand.

The odd thing was that I did choose that option to boot to bootloader in twrp and it didn't work. I ended up having to reboot to bootloader manually. Not a big deal. All is working now, but thought that was interesting.

Kalaxy said:
I accidentally wiped the OS from advanced wipe option. How do I get my phone to work again. I tried to operate adb sideload from recovery but it failed. I have downloaded the stock rom but I do not know how to install it.
Click to expand...
Click to collapse
Exactly which partitions did you wipe? system? data? Internal Storage (userdata)? all of the above? Hopefully you did not wipe userdata (all your stuff). Were you on a stock ROM? You should be able to d/l the Google image from the same build you were on, extract system and data and fastboot flash those. Don't flash userdata. All your stuff should be there. Follow the tutorial on how to set up fastboot and selectively flash partitions.
---------- Post added at 06:49 AM ---------- Previous post was at 06:44 AM ----------
This thread got hijacked at least 3 times. Let's hope OP can find his way back.

pocholo36 said:
I have the same issue. The problem is, that my computer will not recognize the phone in bootloader mode or in recovery mode(MTP enabled). How can install usb drivers without being able to boot into phone OS???? I've tried Nexus Toolkit with no success. Please help?
Click to expand...
Click to collapse
Try this Hope you get solution to your problem of installing adb and fastboot tools in the correct manner.

I just by mistake deleted my internal storage.
I have TWRP, how do i put the ROM on there and flash it? Someone please help.
Thanks

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!