Recovery Question (TWRP 3.0.0-1) - Nexus 6P Q&A, Help & Troubleshooting

Quick question:
I am very used to flashing so this isn't new to me. I recently updated to android build MHC19I. I'm use to the "lock your bootloader" warning, but now that I'm on TWRP 3.0.0-1, I'm also receiving the "your device is corrupt" warning. Now this doesn't seem to affect day to day use, so I don't seem to care, but am I doing something wrong? I usually wouldn't receive that message.
Thanks!

dbroer91884 said:
Quick question:
I am very used to flashing so this isn't new to me. I recently updated to android build MHC19I. I'm use to the "lock your bootloader" warning, but now that I'm on TWRP 3.0.0-1, I'm also receiving the "your device is corrupt" warning. Now this doesn't seem to affect day to day use, so I don't seem to care, but am I doing something wrong? I usually wouldn't receive that message.
Thanks!
Click to expand...
Click to collapse
Have you flashed SuperSU since flashing this version of TWRP? I haven't been able to pinpoint the cause of this message, but I believe it occurs when you have a modified /system partition (from installing TWRP). If I recall correctly (I had it a while ago) flashing SuperSU seemed to get rid of it. Could be a coincidence but that was my experience.

Heisenberg said:
Have you flashed SuperSU since flashing this version of TWRP? I haven't been able to pinpoint the cause of this message, but I believe it occurs when you have a modified /system partition (from installing TWRP). If I recall correctly (I had it a while ago) flashing SuperSU seemed to get rid of it. Could be a coincidence but that was my experience.
Click to expand...
Click to collapse
Here is the crazy thing.
So I hadn't flashed anything but TWRP, didn't modify the system partition at all, and that message would come up. I then flashed the latest Pure Nexus (actually then removed Root) and the message is now back to just the relock the bootloader message. I checked what build was used in that rom, and it is some crazy build (MHC19J) which isn't even available on the the Android Factory Images site. So I don't really know. As of now though, I'm just back to the normal lock your bootloader message.

dbroer91884 said:
Here is the crazy thing.
So I hadn't flashed anything but TWRP, didn't modify the system partition at all, and that message would come up. I then flashed the latest Pure Nexus (actually then removed Root) and the message is now back to just the relock the bootloader message. I checked what build was used in that rom, and it is some crazy build (MHC19J) which isn't even available on the the Android Factory Images site. So I don't really know. As of now though, I'm just back to the normal lock your bootloader message.
Click to expand...
Click to collapse
TWRP itself modifies the system partition in order to persist through reboots, I believe this is what causes the message to appear.

I think the Warnung is only red then the vendor image with the cert.check goes wrong the mhc19j is the last march build from the nexus5x and the devs changed the Rom for the angler- so try to flash the vendor image Märchen from Angler the mhc19i and the Rom certificate check goes right and the yellow Warnung is back.....i had for a few days the same Problem.... Download the vendor in the Rom thread and flsh it with wugs toolkit and then reboot.... Sry for my terrible english

Related

TWRP prevents Marshmallow?

I may be doing something stupid, but I've tried various options...
I had an original 5.1.1 build that I let OTA to 6.0. Everything was working fine. I wanted to root, so I installed TWRP... and then the machine wouldn't reboot; it stuck at the "powered by Android" screen and never went into the standard animation screens. I could reboot into TWRP recovery easily enough and using that I could see the filesystem data, but the OS wouldn't boot.
So I reflashed back to 5.1.1 (using http://www.andromods.com/download-files/xt1575-stock-firmware-moto-x-2015-pure-edition.html ), let that OTA to 6.0, installed TWRP... same result.
Third attempt; started at 5.1.1 then installed TWRP (which worked) and then did OTA to 6.0... but this went into a reboot loop.
(Of course during all this I've lost my configs, but I can rebuild that)
Has anyone been able to install TWRP onto an X-Pure 2015 that's running 6.0 ?
What TWRP version are you installing? Make sure it's 2.8.7.1 https://dl.twrp.me/clark/
Sent from my XT1575 using Tapatalk
Sorry, yes, I should have mentioned that; twrp-2.8.7.1-clark.img
Did you install TWRP as read only? I did this and now system recovery is overwriting TWRP and I have no idea how to get out of it.
I had the same problem a couple days ago and posted about it in the 'Android 6.0 Update rolling out! Pure Edition' thread:
"I keep running into a problem after doing the MM update when I flash TWRP (either 2.8.7.0 or 2.8.7.1) where it won't boot into system, just sits there where the animation part should start. Booted/rebooted fine a few times after finishing the MM update, even after flashing the unlocked bootloader logo fix, but as soon as I flash recovery it won't boot system. "
Tried it several times with both TWRP 2.8.7.0 and 2.8.7.1 with no success. Also tried sideloading the OTA per the manual steps in this thread but still couldn't boot to system. Only by already having TWRP installed on 5.1.1 am I able to flash a custom 6.0 ROM successfully. Haven't seen a really clear statement yet that someone has flashed TWRP on fully stock MM with no problem..
EVR_PR said:
Did you install TWRP as read only? I did this and now system recovery is overwriting TWRP and I have no idea how to get out of it.
Click to expand...
Click to collapse
First time I let /system be read-write and second time I let /system be RO. However this likely isn't related to recovery overwriting TWRP; it's documented that on first boot the OS may rewrite the recovery data meaning you'd need to install TWRP again.
Dahenjo said:
I had the same problem a couple days ago and posted about it in the 'Android 6.0 Update rolling out! Pure Edition' thread
...
Haven't seen a really clear statement yet that someone has flashed TWRP on fully stock MM with no problem..
Click to expand...
Click to collapse
Thanks; at least I know it's not me being stupid then (or if I am, then I'm not alone ).
sweh said:
First time I let /system be read-write and second time I let /system be RO. However this likely isn't related to recovery overwriting TWRP; it's documented that on first boot the OS may rewrite the recovery data meaning you'd need to install TWRP again.
Click to expand...
Click to collapse
I have flashed TWRP twice and even rebooted to recovery from recovery and system recovery still overwrites TWRP after booting to system.
Only way I can access TWRP is either flashing it or booting into from the fastboot folder using the fastboot boot command.
Doesn't matter what I do, the option for changing TWRP from read-write to read only doesn't show up anymore.
sweh said:
Thanks; at least I know it's not me being stupid then (or if I am, then I'm not alone ).
Click to expand...
Click to collapse
Well, at age 65 I do put my socks on backwards sometimes..... :silly:
Read on a fairly-detailed post that using adb to flash recovery and rebooting into it should actually work fine!
Could anyone confirm? Is it even possible?
P.S. I'm on XT1572 Indian stock 6.0, and very eager for twrp
I had the exact same problem. I used adb. Stuck on loading screen and then suddenly black. Not able to boot the phone. I'd like to make a nandroid and after that I'd like to use systemless root. If I'm correct, I'll still receive ota's while using systemless root.
Same for me. Returned to stock EU 5.1.1, got update, installed it. Later unlocked bootloader and installed latest TWRP. And now I am stuck on booting up image.
So stock Marshmallow cant be used with TWRP?
BooBzi said:
Same for me. Returned to stock EU 5.1.1, got update, installed it. Later unlocked bootloader and installed latest TWRP. And now I am stuck on booting up image.
So stock Marshmallow cant be used with TWRP?
Click to expand...
Click to collapse
That seems to be the case since I have yet to hear of anyone freshly setting up TWRP for clark/MXPE on purely stock MM without it failing to boot to system afterwards. If you already have TWRP on 5.1.1 you can install a custom MM ROM and then TWRP works normally (ie boots to system), but so far that's the only way I'm aware of to get it functional on MM.
I see you started another thread on this, which may help it get noticed, but maybe also post in the TWRP thread. I posted there on this issue over a week ago but have had zero response from OP, but if others keep doing so maybe that will help.
IMVHO, TWRP for MXPE isn't being supported well - this problem, the version being incorrect for several weeks causing confusion w/dozens of unnecessary posts (this alone could likely be fixed in 2 minutes), as well as the 'SD as internal storage' issue(s) which may be more involved but are still the type of thing those maintaining it are supposed to address. Even some acknowledgement that the issues are recognized and being worked on would be nice, but thus far not even that.
Dahenjo said:
That seems to be the case since I have yet to hear of anyone freshly setting up TWRP for clark/MXPE on purely stock MM without it failing to boot to system afterwards. If you already have TWRP on 5.1.1 you can install a custom MM ROM and then TWRP works normally (ie boots to system), but so far that's the only way I'm aware of to get it functional on MM.
I see you started another thread on this, which may help it get noticed, but maybe also post in the TWRP thread. I posted there on this issue over a week ago but have had zero response from OP, but if others keep doing so maybe that will help.
IMVHO, TWRP for MXPE isn't being supported well - this problem, the version being incorrect for several weeks causing confusion w/dozens of unnecessary posts (this alone could likely be fixed in 2 minutes), as well as the 'SD as internal storage' issue(s) which may be more involved but are still the type of thing those maintaining it are supposed to address. Even some acknowledgement that the issues are recognized and being worked on would be nice, but thus far not even that.
Click to expand...
Click to collapse
Thanks for reply, I did listen to you and post on TWRP thread.
Dahenjo said:
That seems to be the case since I have yet to hear of anyone freshly setting up TWRP for clark/MXPE on purely stock MM without it failing to boot to system afterwards. If you already have TWRP on 5.1.1 you can install a custom MM ROM and then TWRP works normally (ie boots to system), but so far that's the only way I'm aware of to get it functional on MM.
I see you started another thread on this, which may help it get noticed, but maybe also post in the TWRP thread. I posted there on this issue over a week ago but have had zero response from OP, but if others keep doing so maybe that will help.
IMVHO, TWRP for MXPE isn't being supported well - this problem, the version being incorrect for several weeks causing confusion w/dozens of unnecessary posts (this alone could likely be fixed in 2 minutes), as well as the 'SD as internal storage' issue(s) which may be more involved but are still the type of thing those maintaining it are supposed to address. Even some acknowledgement that the issues are recognized and being worked on would be nice, but thus far not even that.
Click to expand...
Click to collapse
I was on pure stock mm and sideloaded twrp without any issues. I use the twrp app (requires root) to reboot into recovery without any problems.
ccic2491 said:
I was on pure stock mm and sideloaded twrp without any issues. I use the twrp app (requires root) to reboot into recovery without any problems.
Click to expand...
Click to collapse
Hello, is it possible to get step by step tutorial?
Later will try on Style with stock MM.
Thanks!
ccic2491 said:
I was on pure stock mm and sideloaded twrp without any issues. I use the twrp app (requires root) to reboot into recovery without any problems.
Click to expand...
Click to collapse
Did you not use the Fastboot Install Method on the TWRP site? We are unable to reboot back into system after using this on stock MM, which always worked fine on stock LP. If you used a different method that worked could you please share what that was?
I am using twrp 2.8.7.1 on my Moto X Style XT1572 Asia retail without any trouble for past two weeks.
I normally flashed it using the fastboot and never ran into trouble.
gulshanstrider said:
I am using twrp 2.8.7.1 on my Moto X Style XT1572 Asia retail without any trouble for past two weeks.
I normally flashed it using the fastboot and never ran into trouble.
Click to expand...
Click to collapse
Just to confirm - when you flashed TWRP you were completely stock after installing the 6.0 OTA (not still on 5.1.1 before taking the OTA), correct?
Dahenjo said:
Just to confirm - when you flashed TWRP you were completely stock after installing the 6.0 OTA (not still on 5.1.1 before taking the OTA), correct?
Click to expand...
Click to collapse
Here is what I did:-
1) I was in Stock 5.1.1 (had unlocked bootloader)
2) I took the OTA.
3) Flashed the twrp 2.8.7.1 using fastboot
So yes I was completely stock 6.0 when I flashed the TWRP for MM

[marmite] Official Wileyfox Swift 2+ Updates (also for root) - Repository

Hi!
As Wileyfox issued another OTA today and the last time I had a hard time to find the proper information, I thought I'd start a thread that contains the update information and links for ALL OTAs in one place right at the start.
But first of all: This would not be possible without linuxct and mdosch who delivered this information in a combined effort. I added only a few things, like the new updates and put everything in one place.
1. The official update links from Wileyfox (partially from here, here and myself):
TOS118C (Recovery Image)
TOS163B (Recovery Image) Deleted by Wileyfox
TOS208G (Recovery Image) Deleted by Wileyfox
TOS249H (Recovery Image)
TOS319I (Recovery Image) Deleted by Wileyfox
TOS373J missing
UOS224B missing
UOS273C (Recovery Image)
TOS118C (Fastboot Image) Deleted by Wileyfox
TOS163B (Fastboot Image) Deleted by Wileyfox
TOS208G (Fastboot Image) Deleted by Wileyfox
TOS249H (Fastboot Image)
TOS319I (Fastboot Image)
TOS373J (Fastboot Image)
UOS224B missing
UOS273C missing
TOS089A to TOS118C (OTA Update)
TOS118C to TOS163B (OTA Update)
TOS163B to TOS208G (OTA Update)
TOS208G to TOS249H (OTA Update)
TOS249H to TOS319I (OTA Update)
TOS319I to TOS373J (OTA Update)
TOS373J to UOS224B (OTA Update to OREO 1)
UOS224B to UOS273C (OTA Update)
TOS373J to UOS273C (OTA Update to OREO 2)
2. The instructions how to make the OTA links work (taken from here):
If you directly click it, it will return an Error 404, but that is not true since the file actually exists... But requires a special HTTP header to be visible. Since I wanted to grab the OTA link now that, for once, I finally got an OTA in this phone after always upgrading through fastboot images, I used wireshark to determine the server where it fetches it and the full file route. It turns out the header sends a special UA string as you can see in the picture attached: rsotaua 1.0, which is, most probably, a randomly generated string. Now here's the thing: if you want to switch the UA you'll need an extension to do so. linuxct has used this one and on Firefox I used this one. As soon as it's installed, go to the Options of the extension and add it like here:
Code:
WILEYFOX rsotaua 1.0 Chrome Replace WF
Once the string is inserted, switch to it and hit the URL. The OTA should be downloadable now.
As I just found out: The "User Agent Switcher" for Chrome works just as fine.
3. The instructions how to update a rooted phone (taken from here):
I'll write down what I did to get it finally work, but be aware you might brick your phone. I did this with Windows 7 and 10 successfully with fastboot and adb installed.
3.1. Download and unzip the fastboot image from point 1. Then switch to fastboot mode and flash boot, recovery and system.
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
3.2. Boot to stock recovery and choose "apply update from adb". Then sideload the update.
Code:
adb sideload wf-marmite-aa4d5d86bc-to-8eec3af77b-signed.zip
This is, of course, an EXAMPLE! You have to put in the name of the actual update you want to do.
3.3. After successful install wipe cache and dalvik/arts cache and reboot to system. If you have issues with "dm verity" do it with the following command (I myself didn't need to do it):
Code:
adb reboot "dm-verity enforcing"
3.4. When the update is configured let the phone switched on for a while (I don't know why, but mdosch ended in a bootloop and had to start again when he instantly rebooted, I myself didn't need to wait). Here you can already put the SuperUser ZIP-file onto your phone via USB (or do it later via sideload).
3.5. Then boot to bootloader and BOOT (not flash) TWRP
Code:
fastboot boot twrp-3.1.1-0-marmite.img
3.6. If you have the SuperUser ZIP-file already on the phone flash it, otherwise go to "ADB -> Sideload" and install there
Code:
adb sideload superuser.zip
3.7. Wipe cache and dalvik/arts cache and finally reboot. Again, if you have issues with "dm verity" do it with the following command (I myself didn't need to do it)::
Code:
adb reboot "dm-verity enforcing"
This is how it worked for me in Windows 7 and 10 on my Wileyfox Swift 2 Plus. Neither did I brick my phone, nor did I loose ANY(!) data, neither from storage nor from any app. But as I don't know what you did with yours I won't issue any warranties here...
BTW: If you ever wondered, when you do the OTA the phone saves the zip here: data/data/com.android.providers.downloads/cache
So, linuxct and mdosch thank you very much again and I hope you don't mind about what I did with your input. :fingers-crossed:
And also thanks to image45 and DIMICH666 for getting hold of some more of the image links.
Thanks, wish I had found this 2 hours earlier! I had been downloading the OTA update but it was failing to install. Spent ages searching my phone for the location of the download without success. Eventually connected my phone to my laptop and did 'adb logcat' - found the URL of the OTA File download "http:\/\/ota-files.wf.bsp.ninja\/marmite\/wf-marmite-8eec3af77b-to-0fcf4099d0-signed.zip". Changed 'User Agent' as described, put the URL in the address bar and hit enter and hey presto! Good to have a repository to refer to.
Hi
I'm already on TOS163B. Can I just sideload the TOS208G OTA zip? Without reflashing the boot, recovery and system images from TOS163B?
The images from TOS208G are not available.?
Thanks for this.
I managed to grab the TOD208G OTA. Flashing the zip in TWRP did not work though. I got an unexpected fingerprint error (6.0.1 instead of 7.1.2). I flashed the last available debloater on TOS163B (which worked fine), but that probably has got me in trouble now. Is there any way to fix this easily, without having to root and remove all the debloat stuff manually?
(... I dream about Lineage 14.1)
H2Oxide said:
Thanks for this.
(... I dream about Lineage 14.1)
Click to expand...
Click to collapse
We all do, I tried an unofficial build however no WiFi yet :crying:
Even with an official build we would still have the unlocked bootloader warning screen and the dm-verity screen that threatens to switch your phone off in 30 seconds if power not pressed. I am sure it only gave you 5 seconds then just continue to boot when running on the Cyanogen ROMs
I am sure there is some ADB the resolve this for the oneplusone phones.
After initial boot the ROM got stuck on the white splash screen. After I installed Magisk via TWRP flashable zip it worked so must need dm-verity switch off.
I never updated back at the end of 2016 because I was unsure if it was a good idea but now I've become annoyed by it constantly asking me to (OTA UK). Should I update to cm-marmite 460.6 MB like it's asking me to? And then I suppose it will pick up and ask me to install the updates since? Thanks.
quixoticduck said:
Should I update to cm-marmite 460.6 MB like it's asking me to? And then I suppose it will pick up and ask me to install the updates since? Thanks.
Click to expand...
Click to collapse
It needs to be what you want, I flashed the cm-13.1.4-ZNH2KAS5RM-marmite-signed-5175bd793a.zip then removed the cm updater to stop it prompting me to move to the next update as it would eventually have you on current build if you accept all the updates.
I flashed cm-13.1.4 as I found it the most stable Cyanogen Marshmallow 6.0.1 ROM and I wanted xposed framework.
However like I said at start of post what do you need from your phone/ android version?
image45 said:
It needs to be what you want, I flashed the cm-13.1.4-ZNH2KAS5RM-marmite-signed-5175bd793a.zip then removed the cm updater to stop it prompting me to move to the next update as it would eventually have you on current build if you accept all the updates.
I flashed cm-13.1.4 as I found it the most stable Cyanogen Marshmallow 6.0.1 ROM and I wanted xposed framework.
Click to expand...
Click to collapse
Thanks, I see what you mean, about it being personal preference. The last couple years I've stepped away from rooting and flashing roms, so right now I suppose all I really want is a stable safe version. Back in 2016 I remember people being worried about the OTA update released right after Cyanogenmod's end, with people thinking the new update might be suspicious (why I never updated, and then stopped following things). So if it turned out that the OTA update was fine then I suppose the easiest and safest way to stop it bugging me about the update might just be to update xD as long as there's no risks (besides the basic risk that any update could bring). Probably makes it easier for any further updates too if any appear.
I hadn't heard of the xposed framework, sounds interesting, I'll look into that just in case I want to use it.
quixoticduck said:
I hadn't heard of the xposed framework, sounds interesting, I'll look into that just in case I want to use it.
Click to expand...
Click to collapse
You need an unlocked bootloader and custom recovery to install xposed framework. However I can jump between any of the Swift 2 ROMs when ever I wish of course.
Currently on the update right before that one, with TWRP and Magisk installed. I found the zip as instructed. Has anybody had success with Flashfire for a small OTA update like this or do you absolutely have to use adb sideload?
Don't know whether I can post links to other sites but there are instruction on how to update to 7.1.2 using the OTA file for both rooted and non-rooted devices at
http://www.stechguide.com/install-android-7-1-2-nougat-on-wileyfox-swift-2/
H2Oxide said:
Thanks for this.
I managed to grab the TOD208G OTA. Flashing the zip in TWRP did not work though. I got an unexpected fingerprint error (6.0.1 instead of 7.1.2). I flashed the last available debloater on TOS163B (which worked fine), but that probably has got me in trouble now. Is there any way to fix this easily, without having to root and remove all the debloat stuff manually?
Click to expand...
Click to collapse
Any thoughts on this? Can I force a sideload or would that be unwise...
der_dkw said:
So, linuxct and mdosch thank you very much again and I hope you don't mind about what I did with your input. :fingers-crossed:
Click to expand...
Click to collapse
Sure that's fine.
I really appreciate you collected all the information and created this overview.
Well I finally managed to try the adb sideload and this is what I got.
What's wrong here?
I'm using TOS163B (7.1.2) so I don't know why it says I have 6.0.1 test keys. I'm trying to sideload TOS208G
Any help is much appreciated
Jack3volution said:
What's wrong here?
Click to expand...
Click to collapse
You are using TWRP not stock recovery.
The OTA zips check your device for not being altered (like rooting or using custom recovery) this is why you have to go to a plain stock rom while flashing boot, recovery and system from the fastboot image (not the complete image as it will erase your data as well I assume).
After you have done this boot to stock recovery and adb sideload the first OTA zip then reboot and so on until you are on the latest.
Then you can boot twrp (I recommend booting instead of flashing as for me it complained about my device being altered when I flashed twrp) and root again (as root was lost during this update process).
Thanks! my mistake. Yeah I still have stock recovery
Cheers
mdosch said:
Then you can boot twrp (I recommend booting instead of flashing as for me it complained about my device being altered when I flashed twrp) and root again (as root was lost during this update process).
Click to expand...
Click to collapse
What's the actual different between booting TWRP and flashing please?
image45 said:
What's the actual different between booting TWRP and flashing please?
Click to expand...
Click to collapse
Booting means you boot TWRP temporarily without replacing your stock recovery. Flashing means you replace the stock recovery with TWRP.
mdosch said:
You are using TWRP not stock recovery.
Click to expand...
Click to collapse
Hmm it didn't work in stock recovery either
Jack3volution said:
Hmm it didn't work in stock recovery either
Click to expand...
Click to collapse
Did you apply the OTA zips in the correct order?
Did you alter your devices in any way like rooting or installing magisk?
You are on TOS163B you said. Did you start your device before booting to recovery? For me after sideloading the TOS163B, sideloading of TOS208G failed when I tried to install it instantly so I cleared the cache/dalvik cache booted to Android, then rebooted to (stock) recovery again and successfully sideloaded TOS208G.

[mini-GUIDE] BRICKED / DOWNGRADE / SAME / UPGRADE - also ALTERNATIVE to RSDlite

I am not responsible for your bricked phone or pigeon poo on your toupe. Do at your own risk.
Many thanks to @SupahCookie for idea and motivation!
INTENTIONALLY DOES --NOT-- LOCK BOOTLOADER!!!
Get factory images here:
https://forum.xda-developers.com/mo...ock-images-t3736767/post75236696#post75236696
THIS GUIDE IS FOR FACTORY/STOCK ROMs - NOT YOUR AVERAGE CUSTOM ROM which may not have bootloaders!!! (thanks!!!!! @echo92 )
FIX:
IF YOU ARE ABLE TO GET TO FASTBOOT THIS SHOULD WORK.
IF YOU HAVE 8.x bootloaders AND ARE DOWNGRADING TO 7, use "Alternative to RSDlite" below.
1 boot to win - 7 or 10 works fine.
2 boot phone to fastboot, and connect phone to computer.
3 start RSDlite
pick a ROM. I believe I used a 7.1.1 rom
3Nov9-ADDISON_NPNS26.118-22-2-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
RSDlite installed it and fixed the problem.
- -
I was then able to use RSDlite to install @rafikowy 's signed 8.0 . - going up from 7 to 8.
- -
- -
If you are on 8.x bootloaders and want to go to 7.x bootloaders, use this (RSDlite throws an error and stops):
ALTERNATIVE TO RSDlite:
1 I used 7zip to extract that 7.1.1 zip (or any ROM zip) into a folder x,
2 add all the adb and fastboot junk to folder x,
3 add the attached file (rename it to flash.bat) to folder x.
4 boot phone to fastboot and connect to computer.
5 click on flash.bat - it throws a lot of "slot" errors but works just fine.
6 reboot your phone if it hasn't already and go through the 7.x install stuffs.
7 you will not show an IMEI if you are coming from an 8.x bootloader. However, it IS there.
NOTE: you may need to add a line to the flash.bat if there are more/less sparsechunk's in your FACTORY/STOCK ROM...
THIS IS NOT FOR CUSTOM ROMs!!!!!!!
EDIT: 3-8-19: I just did this myself to go back very briefly to 7.1 - be sure you don't flash TWRP to it if your going to take OTAs - it will brick it. boot to TWRP if you need TWRP briefly: fastboot boot twrpimg.img
----------
If you can boot to fastboot screen, you can do anything.
Never OTA a ROM if you have modified recovery (TWRP, etc) or if magisk is present.
https://forum.xda-developers.com/mo...p-flashing-t3813498/post77011495#post77011495
I changed the attached file to add pause and reboot and exit to make it slightly more automated.
I have successfully used this many times going back and forth. If you can boot to fastboot screen, you can save your phone and flash anything you want.
You may wish to advise users that if they downgrade to Nougat not to use Nougat OTA updates. The reason being that a downgraded stock Oreo device may still have the Oreo bootloader on it. Thus, attempting to use Nougat OTA updates may hard brick their device (as the bootloader is likely corrupted, meaning no fastboot).
Users could either use the Feb 2018 NPN26.118-22-2-17 firmware from your link https://mirrors.lolinet.com/firmware/moto/addison/official/RETAIL/ as that was the last Nougat firmware (and thus no Nougat OTA updates) or avoid using OTA updates whilst downgraded.
echo92 said:
You may wish to advise users that if they downgrade to Nougat not to use Nougat OTA updates. The reason being that a downgraded stock Oreo device may still have the Oreo bootloader on it. Thus, attempting to use Nougat OTA updates may hard brick their device (as the bootloader is likely corrupted, meaning no fastboot).
Users could either use the Feb 2018 NPN26.118-22-2-17 firmware from your link https://mirrors.lolinet.com/firmware/moto/addison/official/RETAIL/ as that was the last Nougat firmware (and thus no Nougat OTA updates) or avoid using OTA updates whilst downgraded.
Click to expand...
Click to collapse
Interesting. I used the above GUIDE to go up and down a number of times on my phone (about 20 total) , installing and running on both 7 and 8, and then went down to a Nov 7.1.1 and let it ota all the way up to 8.0 and that is what I am using now. I found that when i used a factory zip, and the above procedure, it corrected the bootloaders to the appropriate version that i was flashing - either RSDlite or the more manual path which ignores the errors worked for me.
Using the above procedure , you get the correct bootloaders, which are in the zip.
Please correct me if i am wrong!
KrisM22 said:
Interesting. I used the above GUIDE to go up and down a number of times on my phone (about 20 total) , installing and running on both 7 and 8, and then went down to a Nov 7.1.1 and let it ota all the way up to 8.0 and that is what I am using now. I found that when i used a factory zip, and the above procedure, it corrected the bootloaders to the appropriate version that i was flashing - either RSDlite or the more manual path which ignores the errors worked for me.
Using the above procedure , you get the correct bootloaders, which are in the zip.
Please correct me if i am wrong!
Click to expand...
Click to collapse
That's intriguing - we saw previously on Z Play that users downgrading their stock firmware (e.g. https://forum.xda-developers.com/moto-z-play/help/hard-brick-moto-z-play-patch-abril-t3782927 )and then using OTA updates hard bricked their device (hence the number of users asking for a blankflash, as fastboot no longer works). I don't know if these users hard bricked by downgrading their firmware too far and then flashed an OTA radically different to their previous firmware, or whether it's a risk that's taken by any downgrading of firmware.
When you used fastboot, did you see any 'security downgrade errors' when you flashed the bootloader, and is your bootloader version now C180, as you've flashed the Oreo OTA?
echo92 said:
That's intriguing - we saw previously on Z Play that users downgrading their stock firmware (e.g. https://forum.xda-developers.com/moto-z-play/help/hard-brick-moto-z-play-patch-abril-t3782927 )and then using OTA updates hard bricked their device (hence the number of users asking for a blankflash, as fastboot no longer works). I don't know if these users hard bricked by downgrading their firmware too far and then flashed an OTA radically different to their previous firmware, or whether it's a risk that's taken by any downgrading of firmware.
When you used fastboot, did you see any 'security downgrade errors' when you flashed the bootloader, and is your bootloader version now C180, as you've flashed the Oreo OTA?
Click to expand...
Click to collapse
YES - that's why I wrote these 3 guides - before, it was quite possible to wind up with a bootloader mix - esp depending on the zip you use! - factory/stock only!!!
I added a line to the guide saying that it is only intended to be used for the factory/stock zips as these have (I believe) the bootloaders appropriate to the ROM.
Many thanks for pursuing this! - I wonder if we'll have to exclude certain ROMs that are in the factory lists?????
echo92 said:
That's intriguing - we saw previously on Z Play that users downgrading their stock firmware (e.g. https://forum.xda-developers.com/moto-z-play/help/hard-brick-moto-z-play-patch-abril-t3782927 )and then using OTA updates hard bricked their device
Click to expand...
Click to collapse
If you have TWRP (or I assume any custom recovery) present when you try to ota, it can download just fine and then reboot to the update. I had TWRP and wound up in a situation where my phone would only boot to twrp no matter what I flashed or restored. I booted phone to fastboot, RSDlite'ed that 11-09-17 factory zip and all was well. In that particular case I did not fully install 7.x but immediately RSDlite'ed rafikowy's 8.0 signed stock and went on with my testing. Since then I always boot to TWRP rather than intalling it and do my thing. (thanks @jceballos )
When you used fastboot, did you see any 'security downgrade errors' when you flashed the bootloader, and is your bootloader version now C180, as you've flashed the Oreo OTA?
Click to expand...
Click to collapse
Sorry - since it throws a million errors I never look at it if it works.
The particular build I am on at the moment - is BL: C1.82
This one started from that Nov '17 build and ota'ed all the way to 8.0 Apr.
I root and unroot as needed per rafikowy's method but using a boot to TWRP - never an install TWRP.
I'll put up a new guide ref ota and recovery and brick.
KrisM22 said:
If you have TWRP (or I assume any custom recovery) present when you try to ota, it can download just fine and then reboot to the update. I had TWRP and wound up in a situation where my phone would only boot to twrp no matter what I flashed or restored. I booted phone to fastboot, RSDlite'ed that 11-09-17 factory zip and all was well. In that particular case I did not fully install 7.x but immediately RSDlite'ed rafikowy's 8.0 signed stock and went on with my testing. Since then I always boot to TWRP rather than intalling it and do my thing. (thanks @jceballos )
Sorry - since it throws a million errors I never look at it if it works.
The particular build I am on at the moment - is BL: C1.82
This one started from that Nov '17 build and ota'ed all the way to 8.0 Apr.
I root and unroot as needed per rafikowy's method but using a boot to TWRP - never an install TWRP.
I'll put up a new guide ref ota and recovery and brick.
Click to expand...
Click to collapse
1) If you have TWRP, then using an OTA will fail - as you've not got stock recovery (and likely other modifications, including possibly a system partition set to read-write status). As you noted, having TWRP seems to cause a bootloop when rebooting - I'm not sure if the OTA sets a boot flag to stay in recovery until the update is completed. For the G4/Plus, there's a possible solution by wiping the misc partition but I don't know if there's a similar partition for Z Play devices: https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
The only other solution I've seen is a clean flash of the stock ROM to get your device booting properly.
Booting to TWRP rather than flashing would mean your stock recovery is still present on your device. The only downside is if you need to make modifications, you'd need your computer to boot to TWRP.
2)BL C1.82 seems to be the bootloader provided by the Oreo April 2018 security patch update, so your device looks to be on the right bootloader. It's still curious that the Nov 2017 firmware worked whereas countless other 'factory' stock ROMs caused hard bricks when downgraded to and then OTA updates were installed.
As you mentioned, custom ROMs don't have bootloaders and thus don't care about your bootloader version usually (though I've seen some ROMs require a certain bootloader). However, stock ROMs and stock OTA updates do have bootloaders, which is why downgrading can be risky.
echo92 said:
1) If you have TWRP, then using an OTA will fail - as you've not got stock recovery (and likely other modifications, including possibly a system partition set to read-write status). As you noted, having TWRP seems to cause a bootloop when rebooting - I'm not sure if the OTA sets a boot flag to stay in recovery until the update is completed. For the G4/Plus, there's a possible solution by wiping the misc partition but I don't know if there's a similar partition for Z Play devices: https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
The only other solution I've seen is a clean flash of the stock ROM to get your device booting properly.
Booting to TWRP rather than flashing would mean your stock recovery is still present on your device. The only downside is if you need to make modifications, you'd need your computer to boot to TWRP.
2)BL C1.82 seems to be the bootloader provided by the Oreo April 2018 security patch update, so your device looks to be on the right bootloader. It's still curious that the Nov 2017 firmware worked whereas countless other 'factory' stock ROMs caused hard bricks when downgraded to and then OTA updates were installed.
As you mentioned, custom ROMs don't have bootloaders and thus don't care about your bootloader version usually (though I've seen some ROMs require a certain bootloader). However, stock ROMs and stock OTA updates do have bootloaders, which is why downgrading can be risky.
Click to expand...
Click to collapse
Downgrading is a piece of cake if you don't use RSDlite - it throws an error and stops. Using the bat file it can happily throw all the errors it wants and all I care is at the end I have what I want.
It does indeed change the entire environment when you bat file the zip contents. You can bat file to get from 8 to 7 and then use RSDlite to flash a different 7 OR 8 zip file. There is no resulting difference in whether you RSDlite it or bat file it - the bat file simply comes from the .xml file that is within the zip. There is very little or no difference between that among addison factory/stock zips. Other zips are different (custom ROMs.)
Grab any factory/stock zip for addison and expand it and you will see modems, bootloaders, indeed absolutely everything you would find on that phone if you went to a store and bought it. SupahCookie simply added a couple lock command lines because it was intended for folks who somehow thought that if phone was locked they could take it back to the store and get their money back. Or some such. I found that ATT folk didn't care if you were on CM or whatever if you just needed to swap SIMs or whatever.
I DON'T want to lock the phone as it prevents me from modifying forever. Oh yeah that reminds me I was going to post the obligatory guide (again) about how to flash a white boot logo so you don't get that message - it's still there LOL but since the font is in white, you can't see it.
I have a Moto Z2 Play and used this to get out of a rather sticky situation.. My IEMI shows 0 now and I'm curious if there's a way to fix this? Also, You say you've done OTA updates? My phone is telling my I have some, is it safe to try?
Necrowr said:
I have a Moto Z2 Play and used this to get out of a rather sticky situation.. My IEMI shows 0 now and I'm curious if there's a way to fix this? Also, You say you've done OTA updates? My phone is telling my I have some, is it safe to try?
Click to expand...
Click to collapse
Thanks for feedback and great on success.
IMEI will show zero if using oreo, It will show again if using N. Remember that if you go from O to N you need to use the "Alternative to RSD" as RSD will simply throw an error and stop.
If you have TWRP and/or Magisk you must get rid of them before ota - if twrp present you will soft brick and have to do alternative again - flash a stock recovery. Simply uninstalling/flash magisk will probably not be enough - it will likely d/l but error part way through update. If you are sitting on rafikowy's stock oreo, and haven't modified it, you should be fine. I know Apr and June are out there. I flashed his stock 8.0 and took June fine. Z2 should be no different though of course I can't guarantee it
If you have success, let us know what you have done so others looking in will know. Thanks!
KrisM22 said:
Thanks for feedback and great on success.
IMEI will show zero if using oreo, It will show again if using N. Remember that if you go from O to N you need to use the "Alternative to RSD" as RSD will simply throw an error and stop.
If you have TWRP and/or Magisk you must get rid of them before ota - if twrp present you will soft brick and have to do alternative again - flash a stock recovery. Simply uninstalling/flash magisk will probably not be enough - it will likely d/l but error part way through update. If you are sitting on rafikowy's stock oreo, and haven't modified it, you should be fine. I know Apr and June are out there. I flashed his stock 8.0 and took June fine. Z2 should be no different though of course I can't guarantee it
If you have success, let us know what you have done so others looking in will know. Thanks!
Click to expand...
Click to collapse
I actually flashed to this: ALBUS_C_7.1.1_NPS26.118-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Which is a 7.1.1 variant and it is showing 0 when I check settings and when I dial *#06#. However upon connecting to the computer and running mfastboot getvar imei it returned a value. I only did the steps above which would mean I don't have TWRP or Magisk (when I fastboot and click recovery I get "no command")
****** Additional information *********
XT1710-01 Duel Sim Variant
I started your steps, only being able to access fastboot. The device would throw an error (I don't recall exactly but it ended up showing me them in the bootloader logs) whenever I tried to start it, or go to recovery. #DefinitelyThoughtItWasDead
Necrowr said:
I actually flashed to this: ALBUS_C_7.1.1_NPS26.118-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Which is a 7.1.1 variant and it is showing 0 when I check settings and when I dial *#06#. However upon connecting to the computer and running mfastboot getvar imei it returned a value. I only did the steps above which would mean I don't have TWRP or Magisk (when I fastboot and click recovery I get "no command")
****** Additional information *********
XT1710-01 Duel Sim Variant
I started your steps, only being able to access fastboot. The device would throw an error (I don't recall exactly but it ended up showing me them in the bootloader logs) whenever I tried to start it, or go to recovery. #DefinitelyThoughtItWasDead
Click to expand...
Click to collapse
What rom was on phone when you got it and what have you done to it? Has it ever run 8.x?
original country of phone?
The bat file will always throw a lot of slot errors.
https://mirrors.lolinet.com/firmware/moto/albus/official/RETUS/
or
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
might have some stock ROMs of interest...
KrisM22 said:
What rom was on phone when you got it and what have you done to it? Has it ever run 8.x?
original country of phone?
The bat file will always throw a lot of slot errors.
might have some stock ROMs of interest...
Click to expand...
Click to collapse
It had 7.1.1 stock. I rooted it, and then flashed Resurrection Remix (which was yes 8.1 I believe) and the upgraded bootloader. I then found out my service wouldn't work with that.. so I attempted to flash back to stock which gave me a flurry of issues.. eventually getting to nothing but fastboot working. Flashed back to working with your guide to 7.1.1
If it helps in in fastboot it tells me BL: C0.CD
Necrowr said:
It had 7.1.1 stock. I rooted it, and then flashed Resurrection Remix (which was yes 8.1 I believe) and the upgraded bootloader. I then found out my service wouldn't work with that.. so I attempted to flash back to stock which gave me a flurry of issues.. eventually getting to nothing but fastboot working. Flashed back to working with your guide to 7.1.1
If it helps in in fastboot it tells me BL: C0.CD
Click to expand...
Click to collapse
Custom ROMs won't usually update the bootloader (even if they are newer) as stock ROMs typically only have the bootloader firmware.
You could look into flashing the stock Oreo albus 8.0 ROM https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-oreo-retail-via-fastboot-t3786153 or the 8.0 June 2018 firmware https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-albusretail8-0-0opss27-76-t3822195 but please check that firmware has been released for your device variant.
I don't know if updating your baseband to stock Oreo formally may fix your IMEI issue.
Necrowr said:
It had 7.1.1 stock. I rooted it, and then flashed Resurrection Remix (which was yes 8.1 I believe) and the upgraded bootloader. I then found out my service wouldn't work with that.. so I attempted to flash back to stock which gave me a flurry of issues.. eventually getting to nothing but fastboot working. Flashed back to working with your guide to 7.1.1
If it helps in in fastboot it tells me BL: C0.CD
Click to expand...
Click to collapse
"BL: C0.CD" even right after flashing that albus 7.1.1 using "alternative" above?
What happens if you flash one of the oreo roms from the links I gave you above?
Yeah, RR wouldn't change bootloaders... so you upgraded bootloaders independendently?- that could easily lead to a soft brick... -
I read RR on Z2 and it says nothing about bootloaders even though it says 8.1 based, so i wonder if it needs 7.x bootloaders? I did not read entire thread...
In a reverse, I would wonder if you put an 8 on there if you wouldn't see your IMEI. (On the Z if you flash 8 You won't see the IMEI until you return to 7.)(wondering if z2 is reversed)
KrisM22 said:
"BL: C0.CD" even right after flashing that albus 7.1.1 using "alternative" above?
What happens if you flash one of the oreo roms from the links I gave you above?
Yeah, RR wouldn't change bootloaders... so you upgraded bootloaders independendently?- that could easily lead to a soft brick... -
I read RR on Z2 and it says nothing about bootloaders even though it says 8.1 based, so i wonder if it needs 7.x bootloaders? I did not read entire thread...
In a reverse, I would wonder if you put an 8 on there if you wouldn't see your IMEI. (On the Z if you flash 8 You won't see the IMEI until you return to 7.)(wondering if z2 is reversed)
Click to expand...
Click to collapse
Yes, right after flashing that is the BL that fastboot is showing me. I don't recall updating the bootloader so to speak, however RR did require an updated variant of twrp which I flashed 3.2.2 I believe to get (unsure if that would have changed the bootloader or not). I also tried flashing a stock Oreo (which you've stated stock Roms usually only have the bootloaders so maybe somewhere during this process I updated it?). I wish I had all the notes for what I did to give more precise information, but I'm in a position where I really need my phone so I kinda just panicked and started flashing things when my service wouldn't work.
I'm highly considering trying to run an OTA (though very afraid of bricking). - On a side note though, it wouldn't even tell me I had OTA's until I did the steps in the original post here (doing the different 7.1.1. and 8.0 flashes, it wouldn't ever tell me I had updates, and now it does).
*** Edit ***
Looks like I'm able to enter stock recovery, which makes me believe everything is stock at the moment.
Necrowr said:
Yes, right after flashing that is the BL that fastboot is showing me. I don't recall updating the bootloader so to speak, however RR did require an updated variant of twrp which I flashed 3.2.2 I believe to get (unsure if that would have changed the bootloader or not). I also tried flashing a stock Oreo (which you've stated stock Roms usually only have the bootloaders so maybe somewhere during this process I updated it?). I wish I had all the notes for what I did to give more precise information, but I'm in a position where I really need my phone so I kinda just panicked and started flashing things when my service wouldn't work.
I'm highly considering trying to run an OTA (though very afraid of bricking). - On a side note though, it wouldn't even tell me I had OTA's until I did the steps in the original post here (doing the different 7.1.1. and 8.0 flashes, it wouldn't ever tell me I had updates, and now it does).
*** Edit ***
Looks like I'm able to enter stock recovery, which makes me believe everything is stock at the moment.
Click to expand...
Click to collapse
If you flashed a stock O that would have changed bl to O, but doing the above with the stock 7.1.1 would have changed them back to N. No matter (other than academic) that you don't remember the path - flashing a stock anything reverts it to that point in time. However, IMEI may have been moved - don't know. It will likely show on EITHER 7.x or 8.x stock - just don't know which.
If you flash a stock 8.x from those links I gave you above, it should offer you ota, ASSUMING there are any at this point in time(Z has 2). Adding Magisk at any point seems to hose you for receiving any more ota's - don't understand why, even with magisk uninstall, so that would mean going back to the latest stock and losing what you have (which is why I try to take a TBPro and copy that backup to PC (because re-flashing 8.x stock will likely reset internal storage.).
yes, if you enter stock recovery, you are likely at stock, though you could reflash the latest 7 or 8 stock to be sure, depending on which you want to use as base. Since 8 is having security fixes released, I choose 8 and will likely have no more interest (no time!) in 7.
So, ran the OTA and it was fine running the update and staying on N. I also downloaded the OTA for Oreo, when trying to update the recovery error'd out. It looked like the error said "Error in modem unexpected results" or something similar.
Necrowr said:
So, ran the OTA and it was fine running the update and staying on N. I also downloaded the OTA for Oreo, when trying to update the recovery error'd out. It looked like the error said "Error in modem unexpected results" or something similar.
Click to expand...
Click to collapse
did it offer to let you d/l it again? you could try that.
However, there exist O stock zips in those links I gave you so you could just flash the latest...

[Help] Recovery broken/bricked

So, after buying my OP5, I rooted it and pretty much left it at that. Haven't accepted any OTA updates out of laziness and not wanting to reroot. After 2 years, I decided to finally update. Went and did a nandroid backup, then looked to flash the latest version of the OTA update. Got an error that said something along the lines of "file is for 'Oneplus 5' but device is ' ' ".
Did some googling and saw people recommend a newer version of TWRP, so I went and downloaded and flashed it through TWRP. When I tried to reboot into recovery, nothing happened. Black screen and a permanent bluish-white notification light. Was still able to hard shutdown and boot back into regular OS. Tried to flash via the TWRP app and adb - same result both times, black screen + notification light.
Does anyone know how to restore my recovery and get the OTA update to flash properly? Any help is massively appreciated.
christmas_time said:
So, after buying my OP5, I rooted it and pretty much left it at that. Haven't accepted any OTA updates out of laziness and not wanting to reroot. After 2 years, I decided to finally update. Went and did a nandroid backup, then looked to flash the latest version of the OTA update. Got an error that said something along the lines of "file is for 'Oneplus 5' but device is ' ' ".
Did some googling and saw people recommend a newer version of TWRP, so I went and downloaded and flashed it through TWRP. When I tried to reboot into recovery, nothing happened. Black screen and a permanent bluish-white notification light. Was still able to hard shutdown and boot back into regular OS. Tried to flash via the TWRP app and adb - same result both times, black screen + notification light.
Does anyone know how to restore my recovery and get the OTA update to flash properly? Any help is massively appreciated.
Click to expand...
Click to collapse
Rooted phone and skipped 2 years of updates... That fail for sure and really hard to ota without data loss.
What was your last running rom version, twrp version, magisk version, encryption status of internal storage?
Thanks for getting back to me, I appreciate it.
Last ROM version: OOS 4.5.8
TWRP: 3.1.1-1
Magisk: 17.1
Encryption status: encrypted
How screwed am I?
christmas_time said:
Thanks for getting back to me, I appreciate it.
Last ROM version: OOS 4.5.8
TWRP: 3.1.1-1
Magisk: 17.1
Encryption status: encrypted
How screwed am I?
Click to expand...
Click to collapse
Oh, I recommend to backup everything with titanium backup and Google along with local backups of your internal storage.
OTA is really not a convenient way and you'll face issues so my recommendation is to clean flash if you want to save time.

Soft brick on oneplus 6T after version upgrade from Lineage OS

Hi there,
So I unknowingly did something kinda risky and of course, it backfired. I used the in-system update feature of linage OS to upgrade my version on my Oneplus 6T. Can't exactly remember which one the old version was, but it was at least 4 versions older than the newest nightly one. Afterward, the phone got stuck in a boot loop. Also, in recovery, it can't bind/ mount the system, because there is no file directory. "E:Failed to bind mount /mnt/staging/emulated/media/0 to /storage/emulated: No such file or directory." I tried the following:
- went into recovery, factory reset the device, then flashed new clean lineage os [multiple different versions]. Gets back to boot loop afterward. (note that Fastboot shows no bootloader version or baseband version)
- tried unlocking the bootloader via fastboot flashing unlock. It fails with error code: (remote: Unrecognized command flashing unlock)
- tried copying the contents of slot a to b, in case one was severely outdated as the cause for the soft brick as stated in this guide. Didn't change mentioned issue after flashing os.
- installed Qualcomm USB drivers, to get the PC to detect the phone as a USB device
- after that, tried using the ms-downloader tool to reset and re-flash the phone. It does not get detected and the downloader tool waits for the full 15s before returning the error for no detected device.
- tried unlocking the bootloader itself via fastboot flashing unlock_critical. same error as with normal unlock: (remote: Unrecognized command flashing unlock)
Maybe overwriting the possibly corrupt bootloader would be a good bet, but as mentioned, I cannot unlock the device to make the command for that useable.
Hey, so I am not really knowledgeable enough to help fix this, but I did notice one thing: Why are you using the wiki page from Lineage for the OnePlus 6 (enchilada) instead of the 6t (fajita)?
state_azure said:
Hey, so I am not really knowledgeable enough to help fix this, but I did notice one thing: Why are you using the wiki page from Lineage for the OnePlus 6 (enchilada) instead of the 6t (fajita)?
Click to expand...
Click to collapse
I didn't even notice it was for enchilada, but iirc the file I loaded was only to copy the contents of slot a to slot b. I could search for a fajita version of this. Still, thanks for your reply.
Hi there,
I have the exact same problem. After updating my OP 6T, the cell phone was broken. It's stuck in a reboot loop. Which surprises me, however, because the documentation for this device type recommends that the update be carried out using the system's internal update process. I also noticed that some OTA updates work and some don't. Unfortunately, this is the only way to make use of it very little fun because you never know if the phone is working again when you update. And the security weaknesses show that updates are also important for Lineageos. thanks for the feedback
Zak0r said:
Hi there,
So I unknowingly did something kinda risky and of course, it backfired. I used the in-system update feature of linage OS to upgrade my version on my Oneplus 6T. Can't exactly remember which one the old version was, but it was at least 4 versions older than the newest nightly one. Afterward, the phone got stuck in a boot loop. Also, in recovery, it can't bind/ mount the system, because there is no file directory. "E:Failed to bind mount /mnt/staging/emulated/media/0 to /storage/emulated: No such file or directory." I tried the following:
- went into recovery, factory reset the device, then flashed new clean lineage os [multiple different versions]. Gets back to boot loop afterward. (note that Fastboot shows no bootloader version or baseband version)
- tried unlocking the bootloader via fastboot flashing unlock. It fails with error code: (remote: Unrecognized command flashing unlock)
- tried copying the contents of slot a to b, in case one was severely outdated as the cause for the soft brick as stated in this guide. Didn't change mentioned issue after flashing os.
- installed Qualcomm USB drivers, to get the PC to detect the phone as a USB device
- after that, tried using the ms-downloader tool to reset and re-flash the phone. It does not get detected and the downloader tool waits for the full 15s before returning the error for no detected device.
- tried unlocking the bootloader itself via fastboot flashing unlock_critical. same error as with normal unlock: (remote: Unrecognized command flashing unlock)
Maybe overwriting the possibly corrupt bootloader would be a good bet, but as mentioned, I cannot unlock the device to make the command for that useable.
Click to expand...
Click to collapse
Whatever you do in your device,they will not touch critical partition such as bootloader and many more of it, do u still have twrp or other recovery on your device?
Prinçe çharming ap said:
Whatever you do in your device,they will not touch critical partition such as bootloader and many more of it, do u still have twrp or other recovery on your device?
Click to expand...
Click to collapse
I still got the stock recovery. Booting from TWRP image didn't work on my last try, I don't remember the exact specifics anymore. I'll try again.
Zak0r said:
I still got the stock recovery. Booting from TWRP image didn't work on my last try, I don't remember the exact specifics anymore. I'll try again.
Click to expand...
Click to collapse
Zak0r said:
I still got the stock recovery. Booting from TWRP image didn't work on my last try, I don't remember the exact specifics anymore. I'll try again.
Click to expand...
Click to collapse
Tell me the exact problem you with your phone and maybe i can help
once again,
today got informed via updater that a new update is available. I try do install it, but now i stuck again in recovery. And the only think i can do is a factory reset and everything is lost.
can anybody give an info if it is safe to update the 6T trough OTA? It doesn't look like that.
zero4one said:
once again,
today got informed via updater that a new update is available. I try do install it, but now i stuck again in recovery. And the only think i can do is a factory reset and everything is lost.
can anybody give an info if it is safe to update the 6T trough OTA? It doesn't look like that.
Click to expand...
Click to collapse
Oof, I thought mine only got bricked because I tried to upgrade across 4 versions. It seems as though even normal updates now cause soft bricks, neat.
I tried again today but there seems to be a connection to the error. I had an update pending, which could be installed without any problems. After the restart, I was informed that there was another update, after installing this update there was a total failure again. Could it be that this is somehow related to slot A / B?
zero4one said:
I tried again today but there seems to be a connection to the error. I had an update pending, which could be installed without any problems. After the restart, I was informed that there was another update, after installing this update there was a total failure again. Could it be that this is somehow related to slot A / B?
Click to expand...
Click to collapse
Why don't you try to flash Stock rom on both slots via MSM tool and then just try ota to update to latest build for you specific device
How can i verify if there is an difference between slot a and slot b?
If i flash the stock rom i will be back on oos and that is not what i want i will continue using los, or do we have an idea missmatch there?
thanks for help
zero4one said:
How can i verify if there is an difference between slot a and slot b?
If i flash the stock rom i will be back on oos and that is not what i want i will continue using los, or do we have an idea missmatch there?
thanks for help
Click to expand...
Click to collapse
What do you exactly want ?

Categories

Resources