How do I get back to 7.1 - Sony Xperia X Compact Questions & Answers

A month or two ago I put on AOSP 8.1 via this thread.
https://forum.xda-developers.com/x-compact/development/nougat-7-1-1-android-source-project-t3555510
I'd like to go back to where I was. I have a full twrp backup. I cannot restore that currently due to the aosp being encrypted. You get a bunch of errors.
What is the easiest way to get back to a place where I can simply restore my twrp backup?
TWRP is installed. 3.1.1 I'm assuming I should upgrade to 3.2.2. Curious if that will let me just restore from my twrp backup.
It was suggested I flash another .img file but I'm not sure which one.

j1tters said:
A month or two ago I put on AOSP 8.1 via this thread.
https://forum.xda-developers.com/x-compact/development/nougat-7-1-1-android-source-project-t3555510
I'd like to go back to where I was. I have a full twrp backup. I cannot restore that currently due to the aosp being encrypted. You get a bunch of errors.
What is the easiest way to get back to a place where I can simply restore my twrp backup?
TWRP is installed. 3.1.1 I'm assuming I should upgrade to 3.2.2. Curious if that will let me just restore from my twrp backup.
It was suggested I flash another .img file but I'm not sure which one.
Click to expand...
Click to collapse
You can flash N with Emma... Or, if you just flash a different boot img from a different rom, or update TWRP to 3.2, (it's official now), you should be able to restore backup.

levone1 said:
You can flash N with Emma... Or, if you just flash a different boot img from a different rom, or update TWRP to 3.2, (it's official now), you should be able to restore backup.
Click to expand...
Click to collapse
Emma? Where does one get that. I've always used xpirifirm and flashtool.
Oh seriously? I was kind of hoping that was the answer, that twrp 3.2.2 will be able to restore that.
Thanks

j1tters said:
Emma? Where does one get that. I've always used xpirifirm and flashtool.
Oh seriously? I was kind of hoping that was the answer, that twrp 3.2.2 will be able to restore that.
Thanks
Click to expand...
Click to collapse
https://developer.sony.com/develop/open-devices/get-started/flash-tool/download-flash-tool/

levone1 said:
You can flash N with Emma... Or, if you just flash a different boot img from a different rom, or update TWRP to 3.2, (it's official now), you should be able to restore backup.
Click to expand...
Click to collapse
So I got 3.2.2 installed. It will not restore my old backup.
Could not mount data unable to find crypto key. Also not cannot boot into working oreo.
Unable to mount /data
Unable to find file system
Error opening modem_fs1.emmc.win no such file.
At this point I can get to twrp 3.2.2 and I can get to fastboot.
Cant get emma to see phone.
Any suggestions?

I got emma working. I got it flashed back to nougat. I still cannot restore twrp.
I get this
unable to find file system (first period)
Error opening modem_fs1.emmc.win no such file.

j1tters said:
I got emma working. I got it flashed back to nougat. I still cannot restore twrp.
I get this
unable to find file system (first period)
Error opening modem_fs1.emmc.win no such file.
Click to expand...
Click to collapse
Hi, how did you get emma recognize your phone? I can't see my phone in it.

andry360 said:
Hi, how did you get emma recognize your phone? I can't see my phone in it.
Click to expand...
Click to collapse
In Emma I went to help, Product information. Then I chose my model. Booted phone into fastboot and plugged it in. Emma saw it from then on.

Related

Can't upgrade to MM. Getting 'Error' during process

I am unlocked and unrooted. I had previously upgraded to MM, but ran into some major problems after setting my SD card as internal, and ended up having to use the stock Lollipop tool. So, now i am running stock Lollipop and have received the OTA update. I try running it and it enters the stock recovery ok, the progress bar starts, then after a couple of minutes, i get the dead Andy icon and a quick 'Error' message. It reboots me back to Lollipop and tells me there is an update available and i can try (and fail) again if i want.
A few notes on things i tried to work around this issue (rather than solve it):
1) I have a nandroid i took while in Lollipop, I had it on my PC and i moved it to my sd card but TWRP can't see my SD Card still (E failure to mount SD card). I tried look for solutions to this, but nothing i found worked.
2) so i tried taking the stock MM ROM and moving it to my internal storage and flash that through TWRP, but I couldn't get it to appear in TWRP for selection. I tried look for solutions to this, but nothing i found worked.
3) I took my SD card out completely out, then tried taking the OTA update. Same result: "Error" then reboot.
So, any ideas on how i can get some info on what is causing the failure? Any thoughts on what i can try to resolve this?
chuck-fu said:
I am unlocked and unrooted. I had previously upgraded to MM, but ran into some major problems after setting my SD card as internal, and ended up having to use the stock Lollipop tool. So, now i am running stock Lollipop and have received the OTA update. I try running it and it enters the stock recovery ok, the progress bar starts, then after a couple of minutes, i get the dead Andy icon and a quick 'Error' message. It reboots me back to Lollipop and tells me there is an update available and i can try (and fail) again if i want.
A few notes on things i tried to work around this issue (rather than solve it):
1) I have a nandroid i took while in Lollipop, I had it on my PC and i moved it to my sd card but TWRP can't see my SD Card still (E failure to mount SD card). I tried look for solutions to this, but nothing i found worked.
2) so i tried taking the stock MM ROM and moving it to my internal storage and flash that through TWRP, but I couldn't get it to appear in TWRP for selection. I tried look for solutions to this, but nothing i found worked.
3) I took my SD card out completely out, then tried taking the OTA update. Same result: "Error" then reboot.
So, any ideas on how i can get some info on what is causing the failure? Any thoughts on what i can try to resolve this?
Click to expand...
Click to collapse
I was in the exact same predicament last night, for different reasons though. No matter what I did, I kept getting that same error. I gave up and just flash one of the Roms from this thread since it includes the kernel, radio and stuff http://forum.xda-developers.com/showthread.php?t=3262242.
Sent from my XT1575 using Tapatalk
I had the same issue when i downgraded to LP. There a file you need to flash if you downgraded from MM to LP. I'll post back as soon as I find it.
Sent from my XT1575 using Tapatalk
I have same issue like you guys. I want to root my Moto, and my Wi-Fi won't working. So I downgraded to LL using Restore-To-Stock-Tool and try to upgrade to MM unfortunatelly it isn't work. From OTA I received error, and from recovery also upgrade didn't work? Any ideas how to solve existing problem?
bulsara said:
I had the same issue when i downgraded to LP. There a file you need to flash if you downgraded from MM to LP. I'll post back as soon as I find it.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
That would be great- looking forward to trying out that file.
After running the restore to stock tool you need to flash a file named hlnos in the tools folder.
Sent from my Moto XPE
JoeNeckbone said:
After running the restore to stock tool you need to flash a file named hlnos in the tools folder.
Sent from my Moto XPE
Click to expand...
Click to collapse
I want to make sure i understand the exact files you're referring to. Are you talking about this restore to stock tool?
http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905
If so, I don't see a 'tools' folder in this zip file. So, i am obviously looking in the wrong place. Note: I do remember flashing an additional file at some point after my downgrade. I believe I flashed it when i learned that my wifi didn't work after downgrading to LP. So, if my wifi is now working, it MAY be possible that i already flashed the file you are referring to (though i can't remember what the name of that one was)
chuck-fu said:
I want to make sure i understand the exact files you're referring to. Are you talking about this restore to stock tool?
http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905
If so, I don't see a 'tools' folder in this zip file. So, i am obviously looking in the wrong place. Note: I do remember flashing an additional file at some point after my downgrade. I believe I flashed it when i learned that my wifi didn't work after downgrading to LP. So, if my wifi is now working, it MAY be possible that i already flashed the file you are referring to (though i can't remember what the name of that one was)
Click to expand...
Click to collapse
I'm a little confused, if your trying to go back to lollipop that is the correct modem file, I haven't tried it myself, but I read there should be a tools folder with a hlnos file. If still trying mm then here is the mm modem file.
http://forum.xda-developers.com/showthread.php?p=63574299
Edit: you should verify the md5 for all the files you are using, might have a bad download.
Edit 2: just downloaded the restore zip and took a look, there is no tools folder but filename is
NON-HLOS.bin for lollipop modem.
Sent from my Moto XPE
Sorry for the delay, this is the correct file you need to download NON-HLOS.bin. You can grab it from the link below and only need to flash that file. Hope this helps!
http://thunderztech.com/download-stock-android-6-0-marshmallow-for-moto-x-stylepure-edition-xt1575/
I am in the same issue, but I have the XT1572. Any thoughts?
bulsara said:
Sorry for the delay, this is the correct file you need to download NON-HLOS.bin. You can grab it from the link below and only need to flash that file. Hope this helps!
http://thunderztech.com/download-stock-android-6-0-marshmallow-for-moto-x-stylepure-edition-xt1575/
Click to expand...
Click to collapse
Thanks for trying to help, but that was the file I had originally flashed. I did try again and no luck still.
I just tried again to manually flash the MM ROM and still can't do it. I keep getting the error: "E:Cannot restore System -- mounted read only. " from TWRP. Looking around it seems like i'm sort of stuck. Other phone owners have had to resort to using ruu and restoring directly from their PC. I've done this in the past with my HTC M7, but don't know if things are different (or even applicable) with the MotoXPE, so i need to do some searching around.
If anyone has any thoughts on how to best install a ROM directly from my PC, please share your thoughts. I think this is sideloading, right? I've sideloaded files before, but never ROMs (expect for maybe when i did it with my old M7)
chuck-fu said:
Thanks for trying to help, but that was the file I had originally flashed. I did try again and no luck still.
I just tried again to manually flash the MM ROM and still can't do it. I keep getting the error: "E:Cannot restore System -- mounted read only. " from TWRP. Looking around it seems like i'm sort of stuck. Other phone owners have had to resort to using ruu and restoring directly from their PC. I've done this in the past with my HTC M7, but don't know if things are different (or even applicable) with the MotoXPE, so i need to do some searching around.
If anyone has any thoughts on how to best install a ROM directly from my PC, please share your thoughts. I think this is sideloading, right? I've sideloaded files before, but never ROMs (expect for maybe when i did it with my old M7)
Click to expand...
Click to collapse
Are you rooted and have custom recovery on your device?
Sent from my XT1575 using Tapatalk
bulsara said:
Are you rooted and have custom recovery on your device?
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
I'm not rooted, but i do have TWRP 2.8.7.1-clark on the device.
chuck-fu said:
I'm not rooted, but i do have TWRP 2.8.7.1-clark on the device.
Click to expand...
Click to collapse
You need to make sure you are on factory recovery.
1. downgrade again to moto 5.1 with stock recovery
2. from stock recovery factory reset your device
3. reboot bootloader and then flash the file again.
that should solve your issue.
chuck-fu said:
I'm not rooted, but i do have TWRP 2.8.7.1-clark on the device.
Click to expand...
Click to collapse
In twrp, settings, mount, is system checked or not checked? I checked mine and it is off by default and I don't switch it when flashing.
Sent from my Moto XPE
bulsara said:
You need to make sure you are on factory recovery.
1. downgrade again to moto 5.1 with stock recovery
2. from stock recovery factory reset your device
3. reboot bootloader and then flash the file again.
that should solve your issue.
Click to expand...
Click to collapse
I tried that with the same issue as the op to no avail, ended up going with one of the stock roms. Have another issue but I'll be making a new thread with that.
Sent from my XT1575 using Tapatalk
bulsara said:
You need to make sure you are on factory recovery.
1. downgrade again to moto 5.1 with stock recovery
2. from stock recovery factory reset your device
3. reboot bootloader and then flash the file again.
that should solve your issue.
Click to expand...
Click to collapse
Thanks for the advice. I'll try that here. Just to be sure, for step 1, I assume you mean to use this tool, correct: (http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905)
Or did you downgrade to moto 5.1 using a different method?
bulsara said:
You need to make sure you are on factory recovery.
1. downgrade again to moto 5.1 with stock recovery
2. from stock recovery factory reset your device
3. reboot bootloader and then flash the file again.
that should solve your issue.
Click to expand...
Click to collapse
Also- when you say: "3. reboot bootloader and then flash the file again." Are you suggesting that i should flash my stock MM Rom at that point? If so, just to be clear, i'll need to flash TWRP recovery again, move the MM ROM over, then flash it from inside TWRP, correct?
Or are you saying something different?
Edit: Well, I went ahead and loaded TWRP back on and tried restoring the stock MM Rom. Once again, i got the E: Failure to Mount error when trying to restore (interestingly, i can backup the existing ROM without issue). So, i went ahead and just booted up in hopes that i'd now be able to accept the OTA rom. I just downloaded it, and with stock recover in place, got the same Error and Dead Andy screen.
One note: When i first loaded TWRP, it asks if i want to leave things Read Only and receive OTAs or allow it to be writable. I think in the past i allowed it to be writable (which would've explain the OTA failures of the past), so this time I left it Read Only figuring that would fix my issue. No luck. It still failed.
Any additional ideas would be most welcome. I'm out of ideas here.
JoeNeckbone said:
In twrp, settings, mount, is system checked or not checked? I checked mine and it is off by default and I don't switch it when flashing.
Sent from my Moto XPE
Click to expand...
Click to collapse
Just checked this and system is not checked. I don't think i've ever changed it either.
Issue resolved-
I never figured out how to get around the Error during OTA install, but i did get on MM. I case this somehow helps anyone, here's what i ended up doing.
1) Used the Restore to 511 stock tool (non-rooted)
2) booted into 511 and set things up
3) reformatted my SD card for use (it had previously been set up to be used as internal storage when i had MM working a couple of weeks ago)
4) flashed TWRP 5.1.1
5) rooted using install of SU zip file (rather than TWRP's "do you want to root this device"
6) Rebooted? (maybe i did this. don't remember)
7) Loaded the stock MM rom onto my SD card
8) Went back into TWRP and made my internal partition writeable (Note: i initially tried to say yes to when TWRP asked me if i wanted to root, but this prevented the device from booting after i restored the MM Rom (in the next step), so i just said no to that. If i decide to root later, i will do so by installing SU from zip.
9) Restored the stock MM rom from the SD card
Now up and running on MM. Will not allow my SD card to be used as internal- which is what started this mess.
Currently don't seem to have wifi working. I had this issue when i downgraded to 5.1.1 and needed to flash the NON-HLOS.bin file. I am trying to find out if i need to do the same here.

Stuck in TWRP after pushed upgrade 28s

This morning I my phone pesented itself in TWRP.
Maybe this is because over the past days I repeatedly got notifications that a system upgrade wanted to install itself (I have a modified 26s X720 from Tora33).
I rejected those notifications.
Now I am stuck in TWRP and I cannot get around it. What I tried:
Reinstalling previous firmware (Tora33 26s) still on the phone
Restoring a TWRP backup from 6 months ago (TWRP didn't see it, maybe it's from a previous TWRP version, I now have v. 3.1)
Flash via fastbood factory image using Mauro's Tool All In One (error message "can't find file mke2fs.conf")
Wipe data, cache, dalvik cache, system; then install Mauro_V2.2 cleansed 23s firmware which I transferred to the phone
Every time it boots up in TWRP.
Your bricked you never flash ota with twrp you should read before doing anything.
The only thing that can help is ofil.
I suggest you study well before trying it.
Sent from my LEX720 using xda premium
mchlbenner said:
Your bricked you never flash ota with twrp you should read before doing anything.
The only thing that can help is ofil.
I suggest you study well before trying it.
Click to expand...
Click to collapse
Oh boy. Thanks anyway. OTA flashed itself, couldn't stop it. Maybe I made it worse by trying to fix.
The bootloader is not locked according to the AIO tool. I can flash succesfully any firmware, only after flashing the phone will still boot in TWRP. It is strange it still boots in TWRP. Is there no simpler trick like flashing the standard recovery and then flashing OFW?
You mention Ofil; do you think the guide described here work?
Wortelstok said:
Oh boy. Thanks anyway. OTA flashed itself, couldn't stop it. Maybe I made it worse by trying to fix.
The bootloader is not locked according to the AIO tool. I can flash succesfully any firmware, only after flashing the phone will still boot in TWRP. It is strange it still boots in TWRP. Is there no simpler trick like flashing the standard recovery and then flashing OFW?
You mention Ofil; do you think the guide described here work?
Click to expand...
Click to collapse
Yes, that QFIL guide is for the x720.
In my opinion, the best way to return stock is to push update.zip into phones main folder, then install stock recovery, then in this one install update zip then check that OS is working. If it is, then go into twrp and wipe. Can't do it?
I'll mention myself;
https://forum.xda-developers.com/le-pro3/how-to/guide-simple-to-return-to-stock-x720-t3618658
marik1 said:
In my opinion, the best way to return stock is to push update.zip into phones main folder, then install stock recovery, then in this one install update zip then check that OS is working. If it is, then go into twrp and wipe. Can't do it?
I'll mention myself;
https://forum.xda-developers.com/le-pro3/how-to/guide-simple-to-return-to-stock-x720-t3618658
Click to expand...
Click to collapse
If he was just going back stock that would work he flash 28s ota with twrp so this will not work.
Sent from my LEX720 using xda premium
No brick after OFW push 28s
The pushed (unvoluntary) update didn't brick my phone after all. This may be important for those that have modified stock ROMs with TWRP.
Not being able to restore OFW was a bug in Mauro's All-in-One tool which he fixed last night. After I could easily flash 20S or 26S stock from his repository. I would also recommend this as safest/easiest procedure. Afterwards you can just flash TWRP from the same tool and move from there.
By the way, immediately after flashing 20s the FW notified it wanted to update itself, again!
n my opinion, the best way to return stock is to push update.zip into phones main folder, then install stock recovery, then in this one install update zip then check that OS is working. If it is, then go into twrp and wipe. Can't do it?
Click to expand...
Click to collapse
Might have tried that

Trying to understand what I broke. Corrupted /data

I'm just trying to understand what I did here. This is the first phone that's given me this much trouble.
Was running 7.1.1 stock. Finally got annoyed by that auto volume thing from sony that I had time to flash AOSP. I followed
https://forum.xda-developers.com/x-compact/development/nougat-7-1-1-android-source-project-t3555510
I used xperifirm/flashtool to update to newest UK firmware ( US has no fingerprint ) . I did NOT backup my drm keys. I have them from before when I rooted. Besides I didn't need them really. I use opencamera.
Followed that guide exactly. Everything worked. Then I flashed twrp 3.1.1 from adb. I think this is where I went wrong. I wanted to flash supersu and viper4android. As soon as I tried this I got twrp errors about mounting /data. Missing crypto footers. I also noticed that supersu binary always said it needed updating, and viper4android would not install drivers.
Did some googling. Saw I just had to format /data from twrp. TWRP was unable to format data with the same errors. More google, saw I had to recreate the /data from terminal from this link https://forum.xda-developers.com/xperia-sp/help/format-data-using-twrp-3-0-2-t3371137 .
Did that. Same errors in twrp. Ok had enough. Restored my twrp backup from 7.1.1 where everything worked. That went through and just hosed everything, due to not being able to read /data. After this finished I was stuck in a boot loop.
Got into fastboot and reran the original AOSP guide above. Now I'm there. Everything left exactly as it was. No twrp etc.
My question is what the heck did I break and how? And as a secondary question can I root this, if so how? The recovery that is flashed with that guide cannot mount /sdcard so I don't see a way to flash supersu for example.
Just trying to understand before I really break something.
j1tters said:
I'm just trying to understand what I did here. This is the first phone that's given me this much trouble.
Was running 7.1.1 stock. Finally got annoyed by that auto volume thing from sony that I had time to flash AOSP. I followed
https://forum.xda-developers.com/x-compact/development/nougat-7-1-1-android-source-project-t3555510
I used xperifirm/flashtool to update to newest UK firmware ( US has no fingerprint ) . I did NOT backup my drm keys. I have them from before when I rooted. Besides I didn't need them really. I use opencamera.
Followed that guide exactly. Everything worked. Then I flashed twrp 3.1.1 from adb. I think this is where I went wrong. I wanted to flash supersu and viper4android. As soon as I tried this I got twrp errors about mounting /data. Missing crypto footers. I also noticed that supersu binary always said it needed updating, and viper4android would not install drivers.
Did some googling. Saw I just had to format /data from twrp. TWRP was unable to format data with the same errors. More google, saw I had to recreate the /data from terminal from this link https://forum.xda-developers.com/xperia-sp/help/format-data-using-twrp-3-0-2-t3371137 .
Did that. Same errors in twrp. Ok had enough. Restored my twrp backup from 7.1.1 where everything worked. That went through and just hosed everything, due to not being able to read /data. After this finished I was stuck in a boot loop.
Got into fastboot and reran the original AOSP guide above. Now I'm there. Everything left exactly as it was. No twrp etc.
My question is what the heck did I break and how? And as a secondary question can I root this, if so how? The recovery that is flashed with that guide cannot mount /sdcard so I don't see a way to flash supersu for example.
Just trying to understand before I really break something.
Click to expand...
Click to collapse
I don't know if I know what went wrong, but I wonder, 1) why not Magisk, and 2) why not TWRP 3.2.1? Might be better off...
levone1 said:
I don't know if I know what went wrong, but I wonder, 1) why not Magisk, and 2) why not TWRP 3.2.1? Might be better off...
Click to expand...
Click to collapse
I've never really used magisk. Flashable zip? I'd need a working twrp since the recovery included with that rom can't mount /sdcard.
I think I just happened to grab 3.1.1, I must have missed the 3.2.1 version. At this point I'm not flashing anything until I know it works. I don't remember seeing it in nougat, but I see that under 8.1 the phone status shows as encrypted.
I'm a little leery of flashing anything currently since I currently have no root so I cant use titanium to backup. I also don't want to end up with a non working recovery again. I posted to that aosp thread seeing if anyone rooted it.
At this point I'd almost like to get a working twrp just to go back tro 7.1 where everything worked.
j1tters said:
I've never really used magisk. Flashable zip? I'd need a working twrp since the recovery included with that rom can't mount /sdcard.
I think I just happened to grab 3.1.1, I must have missed the 3.2.1 version. At this point I'm not flashing anything until I know it works. I don't remember seeing it in nougat, but I see that under 8.1 the phone status shows as encrypted.
I'm a little leery of flashing anything currently since I currently have no root so I cant use titanium to backup. I also don't want to end up with a non working recovery again. I posted to that aosp thread seeing if anyone rooted it.
At this point I'd almost like to get a working twrp just to go back tro 7.1 where everything worked.
Click to expand...
Click to collapse
Find twrp in rom forum here, and search xda for Magisk. Flash twrp, wipe everything, then flash rom, then flash Magisk. See if all better... Also, you can flash V4A modules, (and many others), through Magisk.
Twrp - https://forum.xda-developers.com/x-compact/development/ub-twrp-v3-2-1-xperia-x-compact-t3793837
Magisk - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
levone1 said:
Find twrp in rom forum here, and search xda for Magisk. Flash twrp, wipe everything, then flash rom, then flash Magisk. See if all better... Also, you can flash V4A modules, (and many others), through Magisk.
Twrp - https://forum.xda-developers.com/x-compact/development/ub-twrp-v3-2-1-xperia-x-compact-t3793837
Magisk - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Ok. So I'm reflashing the rom via fastboot just like that guide states. Just ignoring the recovery flash?
j1tters said:
Ok. So I'm reflashing the rom via fastboot just like that guide states. Just ignoring the recovery flash?
Click to expand...
Click to collapse
I have never flashed recovery with aosp, because it doesn't do anything. I haven't tried aosp O yet, though. Typically, yes, skip the recovery flash and flash twrp instead.
levone1 said:
I have never flashed recovery with aosp, because it doesn't do anything. I haven't tried aosp O yet, though. Typically, yes, skip the recovery flash and flash twrp instead.
Click to expand...
Click to collapse
I'll give it a whirl. One question though, since I've never run into this. What do you mean because it doesn't do anything? Granted this is the only aosp I've played with so far, so my knowledge is a bit limited.
j1tters said:
I'll give it a whirl. One question though, since I've never run into this. What do you mean because it doesn't do anything? Granted this is the only aosp I've played with so far, so my knowledge is a bit limited.
Click to expand...
Click to collapse
Stock recovery is usually limited to stock functions. If you want to customize, you need custom recovery.
levone1 said:
Stock recovery is usually limited to stock functions. If you want to customize, you need custom recovery.
Click to expand...
Click to collapse
Ohhh. right. I thought you meant recovery didn't do anything with aosp. Read that wrong, brain fart.
So nope. Twrp cannot read /data. Same error as before. Magisk seems to have installed.
My guess is this is all coming from the forced encryption, though I haven't done enough research.. I'm going to see if I can get viper running..
j1tters said:
Ok. So I'm reflashing the rom via fastboot just like that guide states. Just ignoring the recovery flash?
Click to expand...
Click to collapse
Just wanted to say thanks. Magisk and viper are installed and working. TWRP still errors out with not being able to read /data but I got viper and root, and thats all I wanted.
Thanks!
j1tters said:
So nope. Twrp cannot read /data. Same error as before. Magisk seems to have installed.
My guess is this is all coming from the forced encryption, though I haven't done enough research.. I'm going to see if I can get viper running..
Click to expand...
Click to collapse
Yeah, I guess still no custom kernels for O yet, so... Did you already try decrypt data with twrp?
Nope. I got what I wanted at this point. I'm leaving well enough alone. I don't see having to really do anything with TWRP in the near future. I'll miss being able to do a full backup, and I'm a little annoyed I cant restore my 7.1 backup but I can live with that. I see I can decrypt but I'm a little gun shy and don't want to break anything again.
At the end of the day AOSP + viper is really all I needed.
Thanks again for all the help.

sideload installation keeps failing.

I'm trying to revert my oneplus 5 back to stock. I done all the steps got stock recovery installed. When I attempt to sideload original oos through adb sideload it keeps failing at 46%. Any advice would be very appreciated.. I've read so much and tried so many different things. I am completely stuck.
TENlll423 said:
I'm trying to revert my oneplus 5 back to stock. I done all the steps got stock recovery installed. When I attempt to sideload original oos through adb sideload it keeps failing at 46%. Any advice would be very appreciated.. I've read so much and tried so many different things. I am completely stuck.
Click to expand...
Click to collapse
Which rom do you want to flash and from which rom are you coming? Maybe there are some updates between you're missing...
strongst said:
Which rom do you want to flash and from which rom are you coming? Maybe there are some updates between you're missing...
Click to expand...
Click to collapse
I got the phone from a friend and it has been completely wiped and formatted through TWRP. He did have a nougat custom ROM on it prior to that.
I tried to sideload to it with TWRP and it wouldn't work. I followed directions from a website that explains how to revert your op5 back to stock using stock recovery. I was trying to put the original oxygen OS ROM on it that came with the phone using the stock recovery and adb and fastboot. I'm thinking maybe I possibly downloaded the wrong OOS version. Who knows. Lol .
It had nougat Pure FusionOS 7.1.2. encrypted...SuperSU root and TWRP blue spark.
Now all it has is stock recovery with No OS
Would like to get OOS pie on it eventually.
TENlll423 said:
I got the phone from a friend and it has been completely wiped and formatted through TWRP. He did have a nougat custom ROM on it prior to that.
I tried to sideload to it with TWRP and it wouldn't work. I followed directions from a website that explains how to revert your op5 back to stock using stock recovery. I was trying to put the original oxygen OS ROM on it that came with the phone using the stock recovery and adb and fastboot. I'm thinking maybe I possibly downloaded the wrong OOS version. Who knows. Lol .
It had nougat Pure FusionOS 7.1.2. encrypted...SuperSU root and TWRP blue spark.
Now all it has is stock recovery with No OS
Would like to get OOS pie on it eventually.
Click to expand...
Click to collapse
Do you want to have root along with your new rom? And which rom do you want?
strongst said:
Do you want to have root along with your new rom? And which rom do you want?
Click to expand...
Click to collapse
New OOS 5.1 7. With Magisk v18 would be great.
TENlll423 said:
New OOS 5.1 7. With Magisk v18 would be great.
Click to expand...
Click to collapse
You need to flash 5.1.4 at first to create the vendor partition like described here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003 then you can flash 5.1.7. If that fails you need to flash 5.1.5 and 5.1.6 after 5.1.4 and before 5.1.7. You'll find older versions here
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
Also you need an actual(latest codeworkx for example) twrp recovery https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
Please report back
strongst said:
You need to flash 5.1.4 at first to create the vendor partition like described here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003 then you can flash 5.1.7. If that fails you need to flash 5.1.5 and 5.1.6 after 5.1.4 and before 5.1.7. You'll find older versions here
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
Also you need an actual(latest codeworkx for example) twrp recovery https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
Please report back
Click to expand...
Click to collapse
Thank you... can I do all that by installing TWRP with fastboot and then sideload 5.1.4?
TENlll423 said:
Thank you... can I do all that by installing TWRP with fastboot and then sideload 5.1.4?
Click to expand...
Click to collapse
There's no need of sideload anything when you flashed twrp through fastboot. Just copy the roms on the device and flash through twrp
strongst said:
There's no need of sideload anything when you flashed twrp through fastboot. Just copy the roms on the device and flash through twrp
Click to expand...
Click to collapse
Ok I'll give it a try thanks. And merry Christmas
strongst said:
There's no need of sideload anything when you flashed twrp through fastboot. Just copy the roms on the device and flash through twrp
Click to expand...
Click to collapse
How can I transfer 5.1.4 to phone from pc? My phone is completely wiped. Computer won t recognize phone in PC file explorer? Also, Will I have to fastboot flash recovery twrp img to get new twrp to work? Sorry for all the questions.
strongst said:
There's no need of sideload anything when you flashed twrp through fastboot. Just copy the roms on the device and flash through twrp
Click to expand...
Click to collapse
Keep getting failed to mount/system/ invalid argument in thwrp. Can't transfer rom from pc. Its showing up in PC file explorer but won't transfer
strongst said:
You need to flash 5.1.4 at first to create the vendor partition like described here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003 then you can flash 5.1.7. If that fails you need to flash 5.1.5 and 5.1.6 after 5.1.4 and before 5.1.7. You'll find older versions here
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
Also you need an actual(latest codeworkx for example) twrp recovery https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
Please report back
Click to expand...
Click to collapse
Can't copy anything to phone. says there's no system and I even tried sideloading rom and said it corrupt
I think it's done. It's beyond me.. I've read so much trying to get this thing fixed I can't even see straight.. lol
It lets me copy small files over like magisk v18. It works. When I attempt to copy 5.1.4 rpm over it says device stopped not responding. Crazy
TENlll423 said:
It lets me copy small files over like magisk v18. It works. When I attempt to copy 5.1.4 rpm over it says device stopped not responding. Crazy
Click to expand...
Click to collapse
You need to mount internal storage, not system. Is your twrp updated to latest codeworkx?
I'm redownloading 5.1.4
I tried to copy over another ROM I had and it started to copy over so it is the file that was corrupted.
Thanks again I really appreciate it ?
strongst said:
You need to mount internal storage, not system. Is your twrp updated to latest codeworkx?
Click to expand...
Click to collapse
Second to latest... I have
TWRP-3.2.3-0-20181031-codeworkx installed.
Latest one wouldn't boot.
It won't install no vendor to mount or something. I'm done... Thanks for everything anyway.
When I reboot to recovery. This what it says.
TENlll423 said:
Second to latest... I have
TWRP-3.2.3-0-20181031-codeworkx installed.
Latest one wouldn't boot.
Click to expand...
Click to collapse
I'm using twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img
You have the same? The vendor partition will be created with 5.1.4.
You can go(in twrp) to mount - > vendor. But the recovery should mount it automatically when it's created by flashing 5.1.4.
strongst said:
I'm using twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img
You have the same? The vendor partition will be created with 5.1.4.
You can go(in twrp) to mount - > vendor. But the recovery should mount it automatically when it's created by flashing 5.1.4.
Click to expand...
Click to collapse
Yeah that's the same one I'm using I'm thinking maybe I don't have TWRP setup right is there any settings I'm supposed to go into?
Even when I check off everything in advanced wipe and do a wipe it comes up fine all the way to the end and then it says failed to mount vendor (invalid argument)
I liked everything again in TWRP I went to flash 514 and it works all the way up to the end and fails to mount vendor invalid argument.
Somehow I need to activate the vendor partition or something.
well I'm going back to reading like a madman and figure out if anybody else had this problem online. Lol thanks

TWRP-Flashable stock ROM? [Lavender Global]

Hello,
I'm interested in going back to stock after having some issues with xiaomi.eu ROMs. However, the one time I tried it, I had an error mid-flash (with MiFlashTool) and the phone got wiped. Thankfully I was able to re-flash TWRP and flash Xiaomi.eu ROM from there. But I want to return to stock now. However, I don't want to have to use MiFlashTool as last time I did that, the phone almost got bricked. Xiaomi's tools are horrible anyway.
Is there a way to get the latest stable Global ROM for Lavender in a .ZIP file that I'd be able to flash from TWRP?
Any help is appreciated.
rottensong said:
Hello,
I'm interested in going back to stock after having some issues with xiaomi.eu ROMs. However, the one time I tried it, I had an error mid-flash (with MiFlashTool) and the phone got wiped. Thankfully I was able to re-flash TWRP and flash Xiaomi.eu ROM from there. But I want to return to stock now. However, I don't want to have to use MiFlashTool as last time I did that, the phone almost got bricked. Xiaomi's tools are horrible anyway.
Is there a way to get the latest stable Global ROM for Lavender in a .ZIP file that I'd be able to flash from TWRP?
Any help is appreciated.
Click to expand...
Click to collapse
Every zip from the official MIUI download page are flashable via TWRP. Remember to make a full backup with TWRP and also backup your internal sdcard as the global rom will reset the official recovery and encrypt your data again (that's what happened in my case).
thunderteaser said:
Every zip from the official MIUI download page are flashable via TWRP. Remember to make a full backup with TWRP and also backup your internal sdcard as the global rom will reset the official recovery and encrypt your data again (that's what happened in my case).
Click to expand...
Click to collapse
Thank you so much! I really don't care much about the data, the phone is new, I just want it to work.
I'll get on this ASAP. Thanks again!
thunderteaser said:
Every zip from the official MIUI download page are flashable via TWRP. Remember to make a full backup with TWRP and also backup your internal sdcard as the global rom will reset the official recovery and encrypt your data again (that's what happened in my case).
Click to expand...
Click to collapse
I get a "zip treble" compatibility error with the stock .zip
rottensong said:
I get a "zip treble" compatibility error with the stock .zip
Click to expand...
Click to collapse
Which TWRP version are you using?
thunderteaser said:
Which TWRP version are you using?
Click to expand...
Click to collapse
V. 3.3.0-0
thunderteaser said:
Which TWRP version are you using?
Click to expand...
Click to collapse
Just in case, I flashed https://forum.xda-developers.com/re...very-unofficial-twrp-touch-recovery-t3921637/ and got the same result.
It did not happen in my case as I was already on global. Maybe you should look for a guide to switch from Xiaomi.eu to global
thunderteaser said:
It did not happen in my case as I was already on global. Maybe you should look for a guide to switch from Xiaomi.eu to global
Click to expand...
Click to collapse
All guides point to using Fastboot flash and that's what almost killed my phone last time.
I've flashed xiaomi.eu Stable now, and did a /data format and full wipe. Let's see if this isn't better. I honestly just want stuff to work at this point.
Thank you for your help.
It took me hours to fix it as ADB wouldnt work with me for some reason...
BUT there is allways an indian guy who does tutorials:
https://www.youtube.com/watch?v=kr3kUJF6d0Y
WORKED FLAWLESS!
Hope i can help some ppl in the future that googled like me

Categories

Resources