Develop Bugs

Uh-oh ... brick HELP!

Hi guys,
Long time reader, and great help to be found I hope!
I just bought a Z1C, followed successfully the full DRM backup, full root process and bootloader unlocked, from the guide posted : http://forum.xda-developers.com/showthread.php?t=2642081
I took a full backup of DRM keys and Nandroid.
I then went to load the Resurrection Remix ROM. I booted in to PhilZ recovery and did a full wipe and factory reset - "Ready for ROM". This completed successfully.
I then realized I forgot to copy the Resurrection ROM files onto my external SD and cancelled/exit out of PhilZ Recovery.
Now when I power up, all I get is SONY logo. I assume this is because the phone has no operating system due to the ROM being wiped and nothing being installed in it's place.
I can confirm I can get into Fastboot mode (Blue LED, but connecting USB and holding UP volume button) but nothing else!!!
If anyone has any ideas, I would really really appreciate it!
thanks in advance!

... ok, so I found a quick fix, sorry for the alarm. I just used ADB to flashboot a version of CWM6 and made it boot into recovery, copied the Resurrection ROM onto my external SD with a card-reader (seperate) then installed the ROM ... hooray! Now I can sleep.
Thanks to anyone who started reading...

For future reference, just using fastboot to install a boot partition with a recovery on it is sufficient to fix these kinds of issues.
fastboot boot path/to/boot.img
or
fastboot flash boot path/to/boot.img
And for the record, with most recoveries you can mount your SDcard on your computer via USB, in CWM it is available in the mounts menu as "Mount USB storage"

Rekoil said:
For future reference, just using fastboot to install a boot partition with a recovery on it is sufficient to fix these kinds of issues.
fastboot boot path/to/boot.img
or
fastboot flash boot path/to/boot.img
And for the record, with most recoveries you can mount your SDcard on your computer via USB, in CWM it is available in the mounts menu as "Mount USB storage"
Click to expand...
Click to collapse
Thanks for the tips. I'm a bit new to this thing ... I assume your commands above will create a separate partition for booting, but how do I get to that recovery screen? ... and I assume boot.img is a recovery boot file? Renamed from CWM?
My issue above was I couldn't load up anything (Sony logo appears, and nothing else, couldn't proceed to recovery screen by pressing UP volume) ... I only could connect to my computer in flash mode for Flashtools to read, and had to start the whole "root my phone" process again.
I am playing around with the stock Sony UK ROM, but I am keen to flash Aura's AURom or maybe another one ... is there a way that I can basically create a "rollback point" so that if I don't like the new ROM I can re-instate what I am playing with now? I really don't want to have to go through the whole root process again if I semi-brick again! Just want to do an easy "undo" ...
Many thanks for putting up with the noob-ness.

boot.img is an image of the kernel. Note that this command is only for unlocked bootloader.
Seems you are using dualrecovery (which resides inside /system) and since you wiped /system you couldn't get into recovery anymore. If you have unlocked bootloader you should use a custom kernel. You can use the one of [NUT] (same functionality as dualrecovery) or the one from Doomlord.
I really don't want to have to go through the whole root process again
Click to expand...
Click to collapse
You do realize that the root process with unlocked bootloader is as followed:
1. Flash custom kernel
2. Go to recovery and flash SuperSU zip

zxz0O0 said:
You do realize that the root process with unlocked bootloader is as followed:
1. Flash custom kernel
2. Go to recovery and flash SuperSU zip
Click to expand...
Click to collapse
Exactly, and if you have saved your TA partition already, then you can always unlock the bootloader, root, and then relock bootloader by flashing your TA partition back.

Awesome, thanks guys for all the help. I will give the AURom a go and hopefully succeed this time.
One last question, what is contained in the TA backup, and what is in a Nandroid backup? From reading, TA is just a set of keys and Nandroid is a Rom backup?

TA backup is a backup of the Trim Area partition, inside of this partition there are DRM keys. Nandroid backup is a backup of various partitions (/system, /data/, etc.) but not TA partition.

zxz0O0 said:
TA backup is a backup of the Trim Area partition, inside of this partition there are DRM keys. Nandroid backup is a backup of various partitions (/system, /data/, etc.) but not TA partition.
Click to expand...
Click to collapse
Super thanks guys, much appreciated

TWRP Can't Mount /System - OP3 Bricks When Trying to Flash New ROM??

I'm currently running my OP3 on Resurrection Remix 5.7.4 (MM 6.01), the phone has the latest version of TWRP and I've flashed other ROMs in the past without any issue
RR has proven to be quite unstable for me, the system UI keeps crashing, which renders the phone unusable until after a reboot so I wanted to flash Freedom OS as that worked quite well for me previously. When I tried to flash the ROM in TWRP the ROM seemed to flash successfully but when I rebooted, only the boot logo showed and then the screen went black and the phone refused to respond at all for about two hours, after that exactly the same thing happened. I managed to boot into recovery and tried flashing a different ROM but the result was the same every time, the only way to get the phone to work normally was to flash RR again/restore from a Nandroid backup, either way, the result is the same, I'm stuck on an unstable ROM and I don't know why, the last time I flashed these ROMs they worked fine, I followed all of the instructions for flashing said ROMs to the letter, I have the latest version of TWRP, etc.
Also it seems TWRP can't mount /system, in TWRP under "mount", system is unchecked, I checked it and tried again but found that whenever I rebooted the phone or attempted to flash a new ROM, it would always uncheck itself and flashing the ROM would fail, however strangely flashing the same version of RR was always successful. Is this why the flashing keeps failing and does anyone know what the problem could be?
Thanks!

bronderb said:
Go into your bootloader and format system, cache, and userdata (This will wipe EVERYTHING so be sure to backup). Then latest official flash stock rom and reboot. This should fix it. If this helped hit thanks!
Click to expand...
Click to collapse
Bootloader? There is no option in the bootloader to delete everything as far as I can see, do you mean in recovery? And if I wipe everything off the phone, how do I get the stock ROM onto the phone to flash it? When you say wipe userdata do you mean wipe internal storage or am I misunderstanding and you're telling me to wipe the usual dalvik, cache and data as you would for a normal clean flash?

bronderb said:
No, go into fastboot and plug into pc. Open cmd and type "fastboot format userdata" "fastboot format cache" "fastboot format system"
Click to expand...
Click to collapse
Okay, thanks, and then what? Do I flash TWRP then push the stock ROM to the phone and flash that? And exactly how do I do that?

bronderb said:
You just go into twrp (no need to reflash) then adb sideload oxygen os
Click to expand...
Click to collapse
Thank you, I am now running OOS, hopefully everything else will go smoothly now, planning to go back to FOS again
I didn't even have to use the fastboot commands to format, just sideloading the OOS file wiped everything anyway

Turns out the issue isn't actually fixed, "system" still appears unchecked in TWRP. Could the fact that I didn't actually format everything first have made a difference, given everything was wiped in the process anyway?
Looks like I'm going to be living the sideloading life...
Edit: Sideloading freedom OS failed, ended up having to restore from my TWRP backup. I don't know what I'm going to do, my main reason for using custom ROMs is installing a black theme, and OOS doesn't support Layers or Substratum fully so I can't stay on that

Is the thing that says "mount system as read-only" enabled in the mounts menu? /System isn't ever mounted when TWRP starts, you have to manually mount it, but as long as the updater-script tells /system to mount, it will. However, if that option to make it read-only is enabled, then nothing will ever write to /system. Last resort is deleting the .twrps file from /sdcard/TWRP folder to remove current TWRP preferences and then when you boot into TWRP, that first screen has the swiper to allow modifications, and you'll swipe that

frickinjerms said:
Is the thing that says "mount system as read-only" enabled in the mounts menu? /System isn't ever mounted when TWRP starts, you have to manually mount it, but as long as the updater-script tells /system to mount, it will. However, if that option to make it read-only is enabled, then nothing will ever write to /system. Last resort is deleting the .twrps file from /sdcard/TWRP folder to remove current TWRP preferences and then when you boot into TWRP, that first screen has the swiper to allow modifications, and you'll swipe that
Click to expand...
Click to collapse
It isn't set to read only, I have tried updating and resetting TWRP but nothing has helped, in fact it's got worse, I managed to sideload OOS but my attempted install of FOS failed so I tried to restore from a backup and that also failed, something which didn't happen back when I was on RR.

evilkitty69 said:
It isn't set to read only, I have tried updating and resetting TWRP but nothing has helped, in fact it's got worse, I managed to sideload OOS but my attempted install of FOS failed so I tried to restore from a backup and that also failed, something which didn't happen back when I was on RR.
Click to expand...
Click to collapse
Which version of TWRP are you running? The official 3.1.0-0 is good for OOS and OOS based ROMs only. Try eng.stk's version.

Use the latest eng-stk twrp.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
In recovery go to Wipe > Format data (this will wipe ALL in youre phone).
It's youre Data in F2FS? If yes you must change it to ext4, in recovery Wipe > Change file system. Reboot recovery. Check if it's changed.
Reboot to Bootloader (Fastboot). From PC reflash recovery.
Now copy Oos rom to the phone memory. Flash rom. Reflash recovery (the rom will overwrite the recovery). Reboot to recovery to see if it works. If not do it again.
I sugest to NOT restore old data. This way you'll have all new in youre phone.

tnsmani said:
Which version of TWRP are you running? The official 3.1.0-0 is good for OOS and OOS based ROMs only. Try eng.stk's version.
Click to expand...
Click to collapse
I was running 3.0.2-2 when the issue started, I updated to 3.0.3 and 3.1.0-0 but nothing changed. Thanks for the suggestion, I will give it a try

null0seven said:
Use the latest eng-stk twrp.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
In recovery go to Wipe > Format data (this will wipe ALL in youre phone).
It's youre Data in F2FS? If yes you must change it to ext4, in recovery Wipe > Change file system. Reboot recovery. Check if it's changed.
Reboot to Bootloader (Fastboot). From PC reflash recovery.
Now copy Oos rom to the phone memory. Flash rom. Reflash recovery (the rom will overwrite the recovery). Reboot to recovery to see if it works. If not do it again.
I sugest to NOT restore old data. This way you'll have all new in youre phone.
Click to expand...
Click to collapse
Help! I attempted to do this and the process failed, I didn't manage to wipe data because "/data could not be mounted as device or resource is busy"
Edit: Device now has nothing but TWRP and fastboot, no OS, no ADB, no data, no internal storage

If you can reflash twrp from PC. If not reflash recovery from twrp recovery : Instal > Image > Select Recovery (you must have TWRP.img in youre phone memory )

I managed to get hold of a few factory images and attempted to flash system.img through fastboot, resulting error was
"target reported max download size of 536,870,912 bytes" (system image is 3080 MB)
"invalid sparse file format at header magi"

null0seven said:
If you can reflash twrp from PC. If not reflash recovery from twrp recovery : Instal > Image > Select Recovery (you must have TWRP.img in youre phone memory )
Click to expand...
Click to collapse
I reflashed the modified TWRP successfully. The second suggestion wouldn't have worked, given my phone has no internal storage

You can't see internal storage because of the recovery does not work write.
If you have a working recovery you can do all you want.

null0seven said:
You can't see internal storage because of the recovery does not work write.
If you have a working recovery you can do all you want.
Click to expand...
Click to collapse
The recovery was working at this point, the issue turned out to be the data partition, system was formatted to ext4 but I didn't realise data was in f2fs which caused the problem in the first place. I formatted to ext4 and everything worked, I was able to install paranoid android and everything worked...
...until I flashed the wrong firmware and now I've hard bricked it! I'm going to try the hard brick toolkit
Edit: After 12 hours of being an unresponsive brick, the phone suddenly booted, system doesn't work but it has recovery. Unfortunately I seem to be back to square one, if I try to flash something it appears to succeed but then the phone doesn't boot up into system

So I am now back to the original issue of system not mounting, in terminal if I type "mount /system" I get following error:
"mounting /dev/block/sde20 on /system failed: Device or resource is busy"
Anyone know how to solve this?

I formatted everything, reflashed recovery and tried to flash OOS, got following error:
Code:
[FONT="Courier New"]"This package is for OnePlus3 devices, this is a oneplus3t" (it isn't)
"Updater process ended with ERROR: 7
Error installing zip file /sdcard/OOS3.2.6.zip" [/FONT]

Issue was "solved" by flashing PA, GApps and the correct firmware
Hopefully that's the end of all this drama, thanks to everyone for their suggestions

Hi, I'm pretty new at rooting and I seem to have a similar error. I'm getting the "can't mount /system" error in TWRP. I am able to boot into OOS 4.1.3 and run the nandroid backup but, I keep getting the same error and am unable to select "system" when choosing the mount option in TWRP.
Do I need to have all partitions in f2fs? My system partition is in ext4. Is this what solved your issue?
It seems my phone is functional even with the error active but, I've been trying to get systemless SuperSU and MagiskHide working and I think that's what is preventing me from doing so.

root problem after update to beta 19

hi,
my oneplus 3 has been rote since i got it (i bought it on launch day) but since i updated it to the beta 19, my phone is no longer rooted : when i put the phone in fastboot it says that my bootloader it unlocked but all the apps who requier root are saying that the phne is not rooted and i cant get twrp to work. i tryied with the official app on my phone and with a program called "tool all in one" (https://forum.xda-developers.com/on...ol-tool-one-driversunlocktwrpfactory-t3398993) and when i flash twrp from the program, i can boot into twrp but then i can't access my files and after i boot the phone, i can no longer boot to twrp
does anyone have a solution that doesn't involve me wiping the phone?

You loose root after updating. Try installing twrp again and then rooting it. Use the toolkit for oneplus 3. Simplifies the process

what do you mean by "then rooting it" ?
the program i use does the same thing as the toolkit and when i install twrp, as i said, it can boot on twrp one time and in twrp i can't access my files and after i boot the phone i can't get back to twrp ,i get the stock recovery

Unless your ROM has built-in root, after flashing TWRP, you have to flash SuperSU or Magisk to obtain root. Mere flashing of TWRP will not give you root.

I know but i can't get to the folder when the magisk file is : when in boot into twrp i cant see my files

Few details... it's quite difficult to help you.
What's the root method? Magisk, SuperSU or Kingroot? Which version?
Ps TWRP recovery is not depending by root, you just need to unlock bootloader (surely it's already unlocked) and flash the same recovery, from PC, via the command "fastboot flash recovery filename.img".
Now enter in TWRP:
1) Wipe /system and /cache;
2) Flash another time Open Beta 19;
3) Flash Magisk or SuperSU (be sure to have latest release);
4) Move TWRP img file from computer to device, then flash it another time (because firmware provides the OOS stock recovery);
5) Reboot and wait 5-10 minutes, because of cache rebuilding.
Tell me if you solve

I am using magisk
Yes my bootloader is unlocked
My problem is that when i flash twrp i cant access my files so i don't want to wipe system if i cant reflash something after
I think that I'll wait for the next update, maybe then it will work
But thank you for your help

Which version of TWRP do you have? Try eng.stk's latest version.

I tryied 3.1.1-2
The eng.stk is not available anymore

Your phone is encrypted, so you have to format data ( but your internal storage wiped by formating data, so back it up ,then only twrp read files in your storage)and flash custom kernel then boot restore backup .

how do you know that my phone is encrypted? i never encrypted it
i use titanium backup so i can't back my phone up until i get rot back

Whenever you flash stock ROM it encrypt if you boot into system directly . So twrp could not read internal storage. Whenever you flash stock ROM you must flash custom kernel or any other method to avoid encryption. This is happened to me and what I'd done is flash custom kernel before boot into rom
To save your data try this
https://forum.xda-developers.com/oneplus-3/how-to/unencrypt-oxygenos-loosing-data-t3412228

Who said that? Check this: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Edit: If you want to save items in internal storage, you can use ADB commands instead of TWRP. You can also simply copy and paste if your PC recognises the internal storage of your phone.

I succeeded but i had to clean everything and use the last backup i made a week ago
Thank you all for your help

[SOLVED] TWRP doesn’t let browse /sdcard files

I am having a problem it happened after I finally got to flash latest CosmicOS and set up a new password on my OP3. So, here’s what basically happened;
Once I got it up and running I noticed that home button and fingerprint sensor was completely disabled, then I tried to set up a new password (completely same password I used to decrypt my storage in TWRP 3.0.2-0) and fingerprint just in case but it didn’t react to me calibrating the fingerprint so I was like, ”alright, gladly I got a backup in TWRP”.
Once I rebooted to recovery it asked for a password as usually, once I typed that exact same password as before it just said wrong password, I tried it twice in case if I made a typo but still invalid password. And then I was panicing and pressed cancel and just rebooted back to OS.
I then removed all passwords there and booted back to recovery again, TWRP doesn’t ask for a password anymore but there’s a slider which says allow modifications or something similar and also there’s read only mode. When I slided the modification thing it just doesn’t show any of my files in sdcard folder when I go to ’Install’ tab but (0mb) instead. I even was able to browse and add files from my pc while phone was plugged in and in recovery mode, not anymore though.
Can anyone give me advice or help to get my oneplus 3 back in use? I have all the important files moved to my pc so I don’t mind losing files I have left in internal storage that much. Not if it’s necessary or easier workaround. thanks for reading this long-ass text :fingers-crossed:
EDIT: Issue SOLVED thanks to @AkR2014. I switched data partition from EXT4 to F2FS and then one more time back to EXT4 in TWRP's Wipe tab. (I was using latest blue_spark's TWRP-3.2.1-x version) and I was able to wipe data, system and both caches afterwards. After that I managed to flash new rom via USB-C to A with mounted USB flash drive on the other end and you know rest of the story. Do note that it WILL clear your internal storage so back up all the necessary files you need. And if you want to stay on F2FS data partition be sure to flash a ROM which supports it
EDIT2: There might be another way to mount your storage in TWRP but this is probably fail-proof method and worked for me

Oh and I couldn’t flash the Gapps in recovery after flashing the CosmicOs and nor I can’t now because of this haha. I can use my email though and send files through it from my another email if that helps

Vaahtopahvi said:
Oh and I couldn’t flash the Gapps in recovery after flashing the CosmicOs and nor I can’t now because of this haha. I can use my email though and send files through it from my another email if that helps
Click to expand...
Click to collapse
Try eng.stk's TWRP and clean flash ROM and Gapps.

tnsmani said:
Try eng.stk's TWRP and clean flash ROM and Gapps.
Click to expand...
Click to collapse
I couldnt find link for eng.stk TWRP, only people talking of it it. and what am I supposed to do with it once I get if you could explain? sorry for nooby questions

tnsmani said:
Try eng.stk's TWRP and clean flash ROM and Gapps.
Click to expand...
Click to collapse
Wait, I think I found it. But the question is can and do I need to update the latest eng.stk’s TWRP through fastboot? And if so, is there instructions topic somewhere?

So here's the latest update: I flashed twrp-3.1.1-2 via fastboot but once I go to recovery it still doesn't let me browse files in /sdcard and if I put new password in OS it doesn't match in TWRP. I have a OS where I can boot to but no Gapps installed.
People say formatting data in TWRP would work, I'm just scared if that doesn't work and won't let me boot to OS anymore (even though I have a TWRP back up which I made before wiping my OxygenOS system data and caches in my pc as well in my phone's storage atm) and I can't flash anything in recovery mode, is there anything I could do? I'm in desperate need of help right now.
In this CosmicOS i am using Android 8.1.0 and I'm afraid something isn't supporting it or so.

Vaahtopahvi said:
So here's the latest update: I flashed twrp-3.1.1-2 via fastboot but once I go to recovery it still doesn't let me browse files in /sdcard and if I put new password in OS it doesn't match in TWRP. I have a OS where I can boot to but no Gapps installed.
People say formatting data in TWRP would work, I'm just scared if that doesn't work and won't let me boot to OS anymore (even though I have a TWRP back up which I made before wiping my OxygenOS system data and caches in my pc as well in my phone's storage atm) and I can't flash anything in recovery mode, is there anything I could do? I'm in desperate need of help right now.
In this CosmicOS i am using Android 8.1.0 and I'm afraid something isn't supporting it or so.
Click to expand...
Click to collapse
As I said, flash eng.stk's TWRP. Simply flash the image to Recovery partition using the TWRP you already have. After that, wipe everything and clean flash the ROM. If anything goes wrong, you can use the Mega Unbrick guide method 2.
Here's the link to TWRP: https://forum.xda-developers.com/devdb/project/?id=15934#downloads

tnsmani said:
As I said, flash eng.stk's TWRP. Simply flash the image to Recovery partition using the TWRP you already have. After that, wipe everything and clean flash the ROM. If anything goes wrong, you can use the Mega Unbrick guide method 2.
Here's the link to TWRP: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Click to expand...
Click to collapse
Thanks for the reply and link. I understood most of the parts except flashing the image to Recovery partition. Am I supposed to find the eng.stk’s TWRP from my Install tab in my current TWRP? Because it doesn’t show any files there. Also do I download the latest 3.2.1-x TWRP from the link you provided?

Vaahtopahvi said:
Thanks for the reply and link. I understood most of the parts except flashing the image to Recovery partition. Am I supposed to find the eng.stk’s TWRP from my Install tab in my current TWRP? Because it doesn’t show any files there. Also do I download the latest 3.2.1-x TWRP from the link you provided?
Click to expand...
Click to collapse
You will find TWRP 3.2.1-x v8.61 in the link I provided. Download that to your phone and save it. Restart your phone in recovery mode and in the current TWRP that you have, click the 'Install' button. By default, you will be shown zip files,if any. TWRP comes as an img file. So click the 'show img files' button at bottom right in TWRP and navigate to where you saved it and select it. Slide the bottom bar to install, you will be asked where to install it to. Select 'Recovery' and again slide the bar. It will be installed. To confirm, restart in recovery mode and check the version number of TWRP.
eng.stk's TWRP is compatible with OOS and custom ROMS. The offficial one doesn't work with some custom ROMs.

tnsmani said:
You will find TWRP 3.2.1-x v8.61 in the link I provided. Download that to your phone and save it. Restart your phone in recovery mode and in the current TWRP that you have, click the 'Install' button. By default, you will be shown zip files,if any. TWRP comes as an img file. So click the 'show img files' button at bottom right in TWRP and navigate to where you saved it and select it. Slide the bottom bar to install, you will be asked where to install it to. Select 'Recovery' and again slide the bar. It will be installed. To confirm, restart in recovery mode and check the version number of TWRP.
eng.stk's TWRP is compatible with OOS and custom ROMS. The offficial one doesn't work with some custom ROMs.
Click to expand...
Click to collapse
he is unable to mount storage via twrp , i have the sol but it will format your whole data / internal storage if your wiling to .
1 ) Go to twrp
2 ) wipe - > Advance wipe > change system file partation
3) if your on F2FS change to ext 4 or vice versa .
4 ) you will be able to mount sdcard
and dont flash this rom again , faceed same issue while flashing some oreo rom .
P.S : do it at your own risk .

AkR2014 said:
he is unable to mount storage via twrp , i have the sol but it will format your whole data / internal storage if your wiling to .
1 ) Go to twrp
2 ) wipe - > Advance wipe > change system file partation
3) if your on F2FS change to ext 4 or vice versa .
4 ) you will be able to mount sdcard
and dont flash this rom again , faceed same issue while flashing some oreo rom .
P.S : do it at your own risk .
Click to expand...
Click to collapse
Thanks man :highfive: I have really nothing to lose anyways so I gotta try that lol. How can I know whether I am on F2FS or EXT 4 though? And once it’s done can I access to my phone storage while it’s in recovery mode and just paste new rom to internal storage? Or do I need to push the rom via adb while in fastboot mode? Thinking to try out Paranoid rom which is based on Nougat, right?

tnsmani said:
You will find TWRP 3.2.1-x v8.61 in the link I provided. Download that to your phone and save it. Restart your phone in recovery mode and in the current TWRP that you have, click the 'Install' button. By default, you will be shown zip files,if any. TWRP comes as an img file. So click the 'show img files' button at bottom right in TWRP and navigate to where you saved it and select it. Slide the bottom bar to install, you will be asked where to install it to. Select 'Recovery' and again slide the bar. It will be installed. To confirm, restart in recovery mode and check the version number of TWRP.
eng.stk's TWRP is compatible with OOS and custom ROMS. The offficial one doesn't work with some custom ROMs.
Click to expand...
Click to collapse
Thanks for clarification tnsmani, appreciate the time you put into it. But as the person who replied to your text, I cannot mount the storage in TWRP which would prevent me of flashing pretty much anything on phone in TWRP.

Vaahtopahvi said:
Thanks man :highfive: I have really nothing to lose anyways so I gotta try that lol. How can I know whether I am on F2FS or EXT 4 though? And once it’s done can I access to my phone storage while it’s in recovery mode and just paste new rom to internal storage? Or do I need to push the rom via adb while in fastboot mode? Thinking to try out Paranoid rom which is based on Nougat, right?
Click to expand...
Click to collapse
yap you will be able to access your internal storage as well flash any thing you want from internal storage , no need to push via adb , use deskinfo app from playstore to check
the format of your data partition. yah try Omni 8.1.0 really awsome rom i am currently using. :laugh:

Vaahtopahvi said:
Thanks for clarification tnsmani, appreciate the time you put into it. But as the person who replied to your text, I cannot mount the storage in TWRP which would prevent me of flashing pretty much anything on phone in TWRP.
Click to expand...
Click to collapse
If you are able to boot into fastboot mode, you can install TWRP through ADB.
But you can not copy, paste in TWRP.

AkR2014 said:
yap you will be able to access your internal storage as well flash any thing you want from internal storage , no need to push via adb , use deskinfo app from playstore to check
the format of your data partition. yah try Omni 8.1.0 really awsome rom i am currently using. :laugh:
Click to expand...
Click to collapse
Great to hear that. Though I don’t have Gapps installed. Accidentally tried to flash the wrong one before the mounting problem occurred and now you know rest of the story :laugh:
I’ll try to find another way to check it though. Oh and as well as the ROM

[9 SE] OTA update encrypted storage

Hi,
Everytime I try to OTA update de weekly rom, I get the message that says that my memory is encrypted and directs me to recovery.
In recovery when I select the ROM, it returns ERROR 7, I know that it is related with 2 command lines in the updater script.
My question is, how can I fix this problems so I can normally OTA update?
Xiaomi MI 9 SE
TWRP 3.5.0_9-0
xiaomi.eu weekly (it happens in all versions)
Thanks

Hi please be specific are you using custom rom (twrp,cynogen...?)
Which phone are you using?
otherwise no one will help you (just edit the first message with the necessary info

flairepathos.info said:
Hi please be specific are you using custom rom (twrp,cynogen...?)
Which phone are you using?
otherwise no one will help you (just edit the first message with the necessary info
Click to expand...
Click to collapse
You're right, I think this is a generic problem, that's why I've not specified the model.

vmlc said:
You're right, I think this is a generic problem, that's why I've not specified the model.
Click to expand...
Click to collapse
Ahh I see now,some phones are built with a custom recovery failsafe so updating straight from the phone won't work
Youre going to have to download the update file to the phone (usually ota.zip)
copy it to pc
Unzip it and check the code (installscript.sh, build.prop... all of them(use Notepad++)) and remove recovery what nots (mine had expect recoveryxa84883,and some other recovery partition nonsense) - this is so you dont lose your twrp
compress all the files and name the zip (anything you want)
copy the zip to your adb fastboot folder
Then make sure usb debugging is enabled and
on pc type in adb: adb reboot recovery
after twrp open select the sideload option and use the method of flashing update then your update will flash easy
or
flash your stock firmware recovery image from extsdcard (external sd card) recovery.img as recovery in twrp (surely you know how to tranfer files from pc to microsddard ..)
reboot to system when done and do normal update should work fine
then flash twrp image from pc flashing software into recovery

flairepathos.info said:
Ahh I see now,some phones are built with a custom recovery failsafe so updating straight from the phone won't work
Youre going to have to download the update file to the phone (usually ota.zip)
copy it to pc
Unzip it and check the code (installscript.sh, build.prop... all of them(use Notepad++)) and remove recovery what nots (mine had expect recoveryxa84883,and some other recovery partition nonsense) - this is so you dont lose your twrp
compress all the files and name the zip (anything you want)
copy the zip to your adb fastboot folder
Then make sure usb debugging is enabled and
on pc type in adb: adb reboot recovery
after twrp open select the sideload option and use the method of flashing update then your update will flash easy
or
flash your stock firmware recovery image from extsdcard (external sd card) recovery.img as recovery in twrp (surely you know how to tranfer files from pc to microsddard ..)
reboot to system when done and do normal update should work fine
then flash twrp image from pc flashing software into recovery
Click to expand...
Click to collapse
Thanks for your reply.
Your first method is what I have to do to update manually, delete the model verification in updater-script. But I have to do this every time I want to update. How can this prevent from happening next times?
The second method, I haven't understood, have to flash stock recovery every time I want to update?
My point is to prevent this from happening, I want to OTA update normally, without having to do this procedures every time.
Regards

vmlc said:
Thanks for your reply.
Your first method is what I have to do to update manually, delete the model verification in updater-script. But I have to do this every time I want to update. How can this prevent from happening next times?
The second method, I haven't understood, have to flash stock recovery every time I want to update?
My point is to prevent this from happening, I want to OTA update normally, without having to do this procedures every time.
Regards
Click to expand...
Click to collapse
Yes
and the second method, yes, flash stock recovery to OTA update (it'll think that everthing is fine)
you can keep stock update if dont need twrp anymore
to update normally you would have to modify your stock recovery to have an intergrated twrp
basically making "stock twrp recovery" mod
Or in the same manner add a partition or boot option for twrp in boot image in maybe boot to [normal, recovery, bootloader"fastboot", and twrp]
with enough dedication it is definitely possible

flairepathos.info said:
Yes
and the second method, yes, flash stock recovery to OTA update (it'll think that everthing is fine)
you can keep stock update if dont need twrp anymore
to update normally you would have to modify your stock recovery to have an intergrated twrp
basically making "stock twrp recovery" mod
Or in the same manner add a partition or boot option for twrp in boot image in maybe boot to [normal, recovery, bootloader"fastboot", and twrp]
with enough dedication it is definitely possible
Click to expand...
Click to collapse
So this is not fixable, keep TWRP and have OTA update?

vmlc said:
So this is not fixable, keep TWRP and have OTA update?
Click to expand...
Click to collapse
Yes but now that you mention if you could edit the twrp recovery_id to match that of the stock recovery ,it might work because the system/ ota file calls for a specific recovery_id