Hi.
I've run into a bit of a problem.
I have unlocked the bootloader of my XC, and when I install TWRP 3.1.1 it boots fine if I just let it boot right after installation. If, however, I launch TWRP and reboots without doing anything, the phone gets stuck on Sony logo during boot.
I've tried flashing the XC Genesis kernel 1.06 first in fastboot, and then immediately after flash TWRP 3.1.1, which does the same. Boots fine if I don't launch TWRP, but as soon as it has been launched and rebooted, it gets stuck on Sony logo.
I've then tried to create a completely preflashed rom with PRF Creator, but that just bootlooped twice and switched the phone off.
Is there anything else to try? I really want to root my phone, to get rid of stupid bloatware and take control over my phone.
Thunderjew said:
Hi.
I've run into a bit of a problem.
I have unlocked the bootloader of my XC, and when I install TWRP 3.1.1 it boots fine if I just let it boot right after installation. If, however, I launch TWRP and reboots without doing anything, the phone gets stuck on Sony logo during boot.
I've tried flashing the XC Genesis kernel 1.06 first in fastboot, and then immediately after flash TWRP 3.1.1, which does the same. Boots fine if I don't launch TWRP, but as soon as it has been launched and rebooted, it gets stuck on Sony logo.
I've then tried to create a completely preflashed rom with PRF Creator, but that just bootlooped twice and switched the phone off.
Is there anything else to try? I really want to root my phone, to get rid of stupid bloatware and take control over my phone.
Click to expand...
Click to collapse
You have to run a modified kernel to be able to boot into custom recovery and allow modifications, else you end up in this bootloop. The proper procedure is flash the firmware you want, flash the kernel, then flash twrp and format data so that you can get rid of the encryption. From there you will be able to boot into the phone and twrp and can start flashing magisk and xposed.
kekistaneerefugee said:
You have to run a modified kernel to be able to boot into custom recovery and allow modifications, else you end up in this bootloop. The proper procedure is flash the firmware you want, flash the kernel, then flash twrp and format data so that you can get rid of the encryption. From there you will be able to boot into the phone and twrp and can start flashing magisk and xposed.
Click to expand...
Click to collapse
Thanks for the reply. I would prefer to use the stock firmware, but get it rooted. Would that still work? And when you say format, you mean after I've installed TWRP, I format the phone from there and wipe data, dalvik and cache, right? And a last question, can't I use SuperSU? I remember using xPosed once, and I wasn't that big of a fan.
Thunderjew said:
Thanks for the reply. I would prefer to use the stock firmware, but get it rooted. Would that still work? And when you say format, you mean after I've installed TWRP, I format the phone from there and wipe data, dalvik and cache, right? And a last question, can't I use SuperSU? I remember using xPosed once, and I wasn't that big of a fan.
Click to expand...
Click to collapse
This is the procedure for stock firmware, there isn't really anything other than stock firmware available for this phone. The way that I used the XC Genesis kernel was to use the no drm fix one and us ta_poc to put in my stock ta keys so that I have a completely stock phone with unlocked bootloader. The drm patch one should work the same however.
When I say format I'm not saying wiping, I mean format. There is a whole separate option in Wipe that is "format data", that is what you need to do since nougat automatically encrypts your data and doesn't allow modifications, you need to backup whatever you may have on internal memory before doing this. This is essentially a factory reset so do it before setting anything up.
And yes you can use SuperSu but its not recommended as its sold to a chinese company and no longer open source, Magisk is the new thing to root with and still lets you pass safetynet where as superSU does not.
kekistaneerefugee said:
This is the procedure for stock firmware, there isn't really anything other than stock firmware available for this phone. The way that I used the XC Genesis kernel was to use the no drm fix one and us ta_poc to put in my stock ta keys so that I have a completely stock phone with unlocked bootloader. The drm patch one should work the same however.
When I say format I'm not saying wiping, I mean format. There is a whole separate option in Wipe that is "format data", that is what you need to do since nougat automatically encrypts your data and doesn't allow modifications, you need to backup whatever you may have on internal memory before doing this. This is essentially a factory reset so do it before setting anything up.
And yes you can use SuperSu but its not recommended as its sold to a chinese company and no longer open source, Magisk is the new thing to root with and still lets you pass safetynet where as superSU does not.
Click to expand...
Click to collapse
Thank you very much for helping understand this. I will give it another go at some point, hoping I'll get it to work then. Thanks again.
Hello guys,
sorry for archeology but I got exaclty just the same problem.
Yesterday I decided to flash 34.3.A252 onto my XC. SO the soft itself works fine - later I decided to flash newest twrp for Kugo, 3.2.3-0.
So exactly as Thunderjew has said - after I enter TWRP once I got stuck on Sony logo.
So whats the right order of things here?
I flash stock rom -> then I flash kernel -> and then TWRP?
What about the Encryption - should I apply any? I'd very much like to have my device encrypted. Is it even possible?
But - anyone knows wher I can find working Kernel file for this firmware? Or which version from ggow would work?
Related
I bought this phone used and the person who had it before me it rooted and installed some of different ROMs on it. After getting my used moto x pure 2015 running android 6.0. I booted it up and tested all the functions (including downloading a few apps) Wi-Fi, camera, audio/charging jacks ext. Everything worked fine. So did normal factory reset (not using TWRP) just to make sure everything was clean before using it as my daily. Then, (BUM BUM BUM!) when I tried to start downloading all my apps. None of them would download even though the Wi-Fi was working. Error 492 I think.
I started trying custom ROMs because I was having two big issues (apps not downloading and incoming call not bringing up accept/decline screen) with my stock rom. and wanted to fix those issues with a fresh stock image.
This is all new to me and has not been as easy as anticipated. If anyone knows a clean factory image I could flash or a fail proof fix to error 492 that would be helpful. I really just want to return to fully working Motorola stock android, but the files I have used haven’t fixed the issue. I have searched for a factory image without finding one…
Is there a way to flash the Motorola image through TRWP?
Otherwise, maybe you can help me with my flashing method, and maybe tell me what I am doing wrong. I tried to flash multiple stock images all with the same issue. I have also tried to flash Resurrection Remix, and Brocken OS, both having resulted in a bootloop. I am starting to think I have done something wrong. The steps I have taken so far have been these:
My bootloader is unlocked status code 3.
My phone is not rooted. Do I need root?
First I downloaded adb and fastboot.
Then I flashed TWRP (3.0.2).
I never installed the official Motorola stock image because flashing it from fast boot wouldn’t work and it couldn’t be flashed with TWRP because it is a .gz not a .zip. (I knew a .gz needs to be flashed with fastboot but I knew TWRP was easer so I didn’t fuss with it)
After flashing TWRP to my phone, I downloaded (yes, I checked the md5) the various ROMs to my computer then transfered them to my phone via micro SD card.
Here are the file’s names if that matters:
moto_x_pure_edition_stock_x1575_mphs24.49-18-3_v1-odexed
(booted and Wi-Fi but play store won’t download apps)
moto_x_pure_edition_stock_x1575_mph24.49-18_v1-odexed
(booted but no Wi-Fi)
Broken-v4.9.1-clark-6.0.1-OFFICIAL-20160824 (with Broken_gapps_lp5.1.x_09172015)
(Brocken was the only non-stock that got past boot, but I still couldn’t get past set up without an error and never made it to the system.)
ResurrectionRemix-N-v5.8.0-20161220-clark (7.1 gapps failed to flash but I booted it anyway.)
(boot loop after both of my tries)
I got Wi-Fi working on one of the above stock ROMs (so I KNOW it works) but couldn’t even turn Wi-Fi on in all the others.
The method I used to flash all of the above files in TWRP was:
Wipe
Full wipe (davlik cache, data, system, cache)
(used for RR and Brocken)
Factory reset (using TWRP) (davlik cache, data , cache)
Used for the stock ROMs or even after flashing .zip file I got the error: no OS installed.
Install
Select file of ROM flash (gapps if needed) and flash
I can’t remember which ones but on some of them after flashing I again did a factory reset.
Then I rebooted
Thanks for reading. Sorry it was so long. I tried to add as much useful information as possible. Hopefully someone smarter than me will see my error(s) and help me get my phone into fully working order.
cont.
I really just want to return to fully working Motorola stock android, but the files I have used haven’t fixed the issue. I have searched for a factory image without finding one…
Is there a way to flash the Motorola image through TRWP?
Otherwise maybe you can help me out with my flashing method and maybe tell me what I am doing wrong. I tried to flash multiple stock images all with the same issue. I have also tried to flash Resurrection Remix, and Brocken OS, both having resulted in a bootloop. I am starting to think I have done something wrong. The steps I have taken so far have been these:
My bootloader is unlocked status code 3.
My phone is not rooted. Do I need root?
First I downloaded adb and fastboot.
Then I flashed TWRP (3.0.2).
I never installed the official Motorola stock image because flashing it from fast boot wouldn’t work and it couldn’t be flashed with TWRP because it is a .gz not a .zip. (I knew a .gz needs to be flashed with fastboot but I knew TWRP was easer so I didn’t fuss with it)
After flashing TWRP to my phone, I downloaded (yes, I checked the md5) the various ROMs to my computer then transfered them to my phone via micro SD card.
Here are the file’s names if that matters:
moto_x_pure_edition_stock_x1575_mphs24.49-18-3_v1-odexed
(booted and Wi-Fi but play store won’t download apps)
moto_x_pure_edition_stock_x1575_mph24.49-18_v1-odexed
(booted but no Wi-Fi)
Broken-v4.9.1-clark-6.0.1-OFFICIAL-20160824 (with Broken_gapps_lp5.1.x_09172015)
(Brocken was the only non-stock that got past boot, but I still couldn’t get past set up without an error and never made it to the system.)
ResurrectionRemix-N-v5.8.0-20161220-clark (7.1 gapps failed to flash but I booted it anyway.)
(boot loop after both of my tries)
I got Wi-Fi working on one of the above stock ROMs (so I KNOW it works) but couldn’t even turn Wi-Fi on in all the others.
The method I used to flash all of the above files in TWRP was:
Wipe
Full wipe (davlik cache, data, system, cache)
(used for RR and Brocken)
Factory reset (using TWRP) (davlik cache, data , cache)
Used for the stock ROMs or even after flashing .zip file I got the error: no OS installed.
Install
Select file of ROM flash (gapps if needed) and flash
I can’t remember which ones but on some of them after flashing I again did a factory reset.
Then I rebooted
Thanks for reading. Sorry it was so long. I tried to add as much useful information as possible. Hopefully someone smarter than me will see my error(s) and help me get my phone into fully working order.
I think this thread will help you: https://forum.xda-developers.com/showthread.php?t=3489110
Sent from my XT1572 using Tapatalk
Install stock firmware via fastboot... if that dont fix the issue, install TWRP make a full wipe, FULL, and install the stock firmware again, eventualy that sould fix the issue.
RK2116 said:
Install stock firmware via fastboot... if that dont fix the issue, install TWRP make a full wipe, FULL, and install the stock firmware again, eventualy that sould fix the issue.
Click to expand...
Click to collapse
I'm having a similar issue. Tried the TruPure rom but I want to switch back to stock. If I do a full wipe, would I be able to use the files that Motorola provides on their website and flash those throught fastboot? Or through TWRP? Any chance you have a link to a guide on how to do the latter option (installing through TWRP)? I'm just trying to get my device back to 100% stock so that I can receive OTA.
cdiaz8 said:
I'm having a similar issue. Tried the TruPure rom but I want to switch back to stock. If I do a full wipe, would I be able to use the files that Motorola provides on their website and flash those throught fastboot? Or through TWRP? Any chance you have a link to a guide on how to do the latter option (installing through TWRP)? I'm just trying to get my device back to 100% stock so that I can receive OTA.
Click to expand...
Click to collapse
Odexed one, install with TWRP, full wipe before doing that, no GApps, just ROM, them, install stock recovery vía fastboot. After that you Will be stock with OTAs.
https://forum.xda-developers.com/mo...t/rom-marshmallow-6-0-september-2016-t3536120
RK2116 said:
Odexed one, install with TWRP, full wipe before doing that, no GApps, just ROM, them, install stock recovery vía fastboot. After that you Will be stock with OTAs.
https://forum.xda-developers.com/mo...t/rom-marshmallow-6-0-september-2016-t3536120
Click to expand...
Click to collapse
Thank you for sharing that link. I think I get it but it seems too easy considering what I've tried so far. Just to make sure I get it:
I should download the odexed rom, go to twrp and wipe data, cache and dalvik then flash the odexed rom through the install function? And thats it? I've literally tried a ton of stuff so if this takes care of it, this is great!
cdiaz8 said:
Thank you for sharing that link. I think I get it but it seems too easy considering what I've tried so far. Just to make sure I get it:
I should download the odexed rom, go to twrp and wipe data, cache and dalvik then flash the odexed rom through the install function? And thats it? I've literally tried a ton of stuff so if this takes care of it, this is great!
Click to expand...
Click to collapse
Yes, also wipe system, make a backup before If you want, but remember, for the OTAs support you need yo flash the stock recovery via fastboot. Good luck.
RK2116 said:
Yes, also wipe system, make a backup before If you want, but remember, for the OTAs support you need yo flash the stock recovery via fastboot. Good luck.
Click to expand...
Click to collapse
This got me back to stock! You are the real MVP.
So I remember seeing a recovery.img file in the factory image that motorola posted on its site. Does it have to be a specific stock recovery or do I need a specific one to match with the file I just installed?
thanks again
cdiaz8 said:
This got me back to stock! You are the real MVP.
So I remember seeing a recovery.img file in the factory image that motorola posted on its site. Does it have to be a specific stock recovery or do I need a specific one to match with the file I just installed?
thanks again
Click to expand...
Click to collapse
Just a stock one, if Motorola have one use that.
RK2116 said:
Just a stock one, if Motorola have one use that.
Click to expand...
Click to collapse
So I'm on stock build 49-18-8 and flashed the recovery from 49-18-3. I went into fastboot and selected recovery. I got the android character with an !
I then did the power button and volume up and got into stock android recovery. Am I supposed to see the android character with ! each time I try to reach the recovery menu? Just wondering if I did this correctly.
Thanks again for pointing me to these resources!
cdiaz8 said:
So I'm on stock build 49-18-8 and flashed the recovery from 49-18-3. I went into fastboot and selected recovery. I got the android character with an !
I then did the power button and volume up and got into stock android recovery. Am I supposed to see the android character with ! each time I try to reach the recovery menu? Just wondering if I did this correctly.
Thanks again for pointing me to these resources!
Click to expand...
Click to collapse
Yes.
Greetings,
I tried to downgrade from Nougat to Marshmallow. If I install stock Nougat ROM via Odin it works. As soon as I install TWRP Recovery and lets say "KryxxOS" it just dont boot. No animated samsung logo just the first static logo and no progress.
If I flash a Nougat based ROM it boots perfectly again.
Anyone might help me there? Am I missing something that I cant downgrade ?
Thanks!
Robin
you can downgrade to Marshmellow.
First back uip your phone as you will lose everything on your phone to downgrade.
using TWRP, go into wipe - advanced and select all the partitions except microsd card.swipe to wipe.
It will delete all the operating system including bootloader and mode. Your phone will have no operating system and will just bootloop if you try to use it.
Then boot into download mode and flash your desired marshmellow rom.
Let odin reboot the phone and you should have a working marshmellow rom on your phone.
You will then need reload all your programs including TWRP.
Make sure that this what you want to do as this advise only and i take no responsibility if you decide to do it.
Cosmic Blue said:
you can downgrade to Marshmellow.
First back uip your phone as you will lose everything on your phone to downgrade.
using TWRP, go into wipe - advanced and select all the partitions except microsd card.swipe to wipe.
It will delete all the operating system including bootloader and mode. Your phone will have no operating system and will just bootloop if you try to use it.
Then boot into download mode and flash your desired marshmellow rom.
Let odin reboot the phone and you should have a working marshmellow rom on your phone.
You will then need reload all your programs including TWRP.
Make sure that this what you want to do as this advise only and i take no responsibility if you decide to do it.
Click to expand...
Click to collapse
Hay,
thanks. I did it exactly as you said. I am able to boot up stock marshmallpow but as soon as I try a custom ROM it just hangs. Tried 2 different...
mautz001 said:
Hay,
thanks. I did it exactly as you said. I am able to boot up stock marshmallpow but as soon as I try a custom ROM it just hangs. Tried 2 different...
Click to expand...
Click to collapse
what custom rtom are you trying to install and did you follow the rom maker instructions exactly.
All you may need to do after flash is do a simple data wipe or cache cleaning to allow the custom rom to work.
So I installed TWRP recovery using tuliptool and all that, but didn't bother with bootloader unlocking since it said it's not needed. So I tried to install Magisk using the instructions on their thread but after booting it asks me to reset my phone because the data got corrupted.
Luckily I had backed everything up beforehand, so I restored boot image and everything works fine again. Just wanted to know what I did wrong here. Did I miss any steps?
auxillium said:
So I installed TWRP recovery using tuliptool and all that, but didn't bother with bootloader unlocking since it said it's not needed. So I tried to install Magisk using the instructions on their thread but after booting it asks me to reset my phone because the data got corrupted.
Luckily I had backed everything up beforehand, so I restored boot image and everything works fine again. Just wanted to know what I did wrong here. Did I miss any steps?
Click to expand...
Click to collapse
You probably didn't miss anything if it's the "Your device is corrupt. It can’t be trusted and may not work properly” error, I get the same thing. You messed with the files in the boot partition so ZTE's "safety" features in the stock ROM automatically call them corrupted. I simply hit the power button and continue to boot, my device works fine (actually much better than before being rooted with Magisk). I'm the one who "corrupted" the phone on purpose, so I'm comfortable it's fine. If you're getting another message, I'm not entirely sure why. Maybe try ADB sideloading Magisk in TWRP, it's what "worked" for me.
marvelljones said:
You probably didn't miss anything if it's the "Your device is corrupt. It can’t be trusted and may not work properly” error, I get the same thing. You messed with the files in the boot partition so ZTE's "safety" features in the stock ROM automatically call them corrupted. I simply hit the power button and continue to boot, my device works fine (actually much better than before being rooted with Magisk). I'm the one who "corrupted" the phone on purpose, so I'm comfortable it's fine. If you're getting another message, I'm not entirely sure why. Maybe try ADB sideloading Magisk in TWRP, it's what "worked" for me.
Click to expand...
Click to collapse
What do you mean by "hitting the power button and continue to boot"? When I hit the power button on the "Decryption unsuccessful" screen it just locks and unlocks like normal, but stays there.
Ok I managed to install Magisk after factory reset, but after that my sdcard is not being recognized anymore (but is recognizable in TWRP). So I decided to restore the backup i had, and rebooted. But now I'm stuck on the ZTE logo during boot. I can still open TWRP, though. I've tried wiping system, data, and cache, then restoring the backup, also no good. For now I'm downloading the stock firmware and will try that. Any ideas on how I can fix this before I flash the stock firmware?
EDIT: Ok I managed to fix it by installing the no verity boot image instead. Boots again. I'll probably refrain from trying to root for now. Thanks for the help.
auxillium said:
Ok I managed to install Magisk after factory reset, but after that my sdcard is not being recognized anymore (but is recognizable in TWRP). So I decided to restore the backup i had, and rebooted. But now I'm stuck on the ZTE logo during boot. I can still open TWRP, though. I've tried wiping system, data, and cache, then restoring the backup, also no good. For now I'm downloading the stock firmware and will try that. Any ideas on how I can fix this before I flash the stock firmware?
EDIT: Ok I managed to fix it by installing the no verity boot image instead. Boots again. I'll probably refrain from trying to root for now. Thanks for the help.
Click to expand...
Click to collapse
Well, I wasn't much help, but it sounds like your overall problem was different than mine. My only advice is if you attempt to root with Magisk again, is to connect to your PC/Mac/etc with a cable, use the Advanced menu in TWRP, choose ADB sideload, and sideload Magisk from your PC/Mac/etc. You can find a more advanced explanations on various websites how to use ADB if you don't already know how. For some reason that worked for me and gave me full Magisk and phone functionality when nothing else did.
marvelljones said:
Well, I wasn't much help, but it sounds like your overall problem was different than mine. My only advice is if you attempt to root with Magisk again, is to connect to your PC/Mac/etc with a cable, use the Advanced menu in TWRP, choose ADB sideload, and sideload Magisk from your PC/Mac/etc. You can find a more advanced explanations on various websites how to use ADB if you don't already know how. For some reason that worked for me and gave me full Magisk and phone functionality when nothing else did.
Click to expand...
Click to collapse
Will this allow me to install magisk without a factory reset?
auxillium said:
Will this allow me to install magisk without a factory reset?
Click to expand...
Click to collapse
I didn't have to, but I can't guarantee it will work for you. I had previously factory reset my phone but at the time I sideloaded Magisk I had been using the phone for at least a week. Just make a backup of everything first to be safe. *edit* I am using the beta version of Magisk (16.4), not sure if that's making a difference.
My phone was rooted for the longest time without any problems, but some time ago (I'm assuming after the Treble update) apps would not detect root, although any app that was already using root could continue doing so.
I checked Magisk, which said root was not installed. I booted my phone into recovery, and somehow my phone had the stock recovery flashed on it. I tried flashing TWRP on it again, and it worked. Except, when I rebooted my phone into recovery later again, it went back to stock recovery.
I have no idea what's going on, and would really appreciate some help.
(PS: I do know how to update my phone without the phone reverting to stock recovery, I've done it many times before, so that can't be the problem)
update: I tried flashing TWRP again (through bootloader), and this time I jumped straight to recovery. It showed all the directories as if my phone had just been completely wiped. Internal memory 0M. No files anywhere. Didn't even have a downloads folder.
In a panic, I rebooted my phone, but my phone was actually untouched, no data wipe whatsoever. I'm even more confused about what the hell is happening now.
The stock OOS will automatically reflash the stock recovery if it detects it has changed to something else.
You have to boot into TWRP right after installing it and either let it mount /system read-write (likely to cause problems later) or install something like Magisk that will prevent overwriting the recovery.
TWRP was not able to read your data partition, which can happen depending on which kind of encryption you have. Try the BlueSpark TWRP, it supposedly supports encryption better than the official one.
It's the version. If I use 3.2.3.0 or 3.2.2.0 I get no files. But 3.2.1.1 works for some reason. You can also install pie now. There is a link in the one plus 5 forums here to hydrogen os. It's Chinese version but that doesn't matter. It is in English. You will need to uninstall a few Chinese bloatware apps and flash gapps. But besides that I don't see much difference. If anything the hydrogen os looks nicer. I'll add some screenshots . Developer options was enabled from first boot, with the advanced reboot menu I noticed.
Also, if you have root the TWRP app can flash recovery from in the OS.
Fif_ said:
The stock OOS will automatically reflash the stock recovery if it detects it has changed to something else.
You have to boot into TWRP right after installing it and either let it mount /system read-write (likely to cause problems later) or install something like Magisk that will prevent overwriting the recovery.
TWRP was not able to read your data partition, which can happen depending on which kind of encryption you have. Try the BlueSpark TWRP, it supposedly supports encryption better than the official one.
Click to expand...
Click to collapse
It's frustrating for sure. Lol
So far there's only a small sample, but I think there's enough of a pattern to constitute an issue. I've tried to flash the latest of both pixel experience (unofficial) and havoc, and each one sends me directly to either recovery or fastboot, depending on the order which I flash/wipe/factory reset. It's been a couple months since I've flashed anything other than an open beta update, but I never had any issues flashing ROMs.
For both I've tried:
Flash OOS. 9.0.13 (or OB13) in both slots
Flashed Twrp installer
Reboot to recovery
Flash custom ROM
Flash Twrp installer
Factory reset (tried full wipe as well)
It's at this point where I attempt to reboot to recovery to flash gapps (for havoc, not PE) I get sent to recovery or fastboot, depending on whether I reset or wipe data.
I can flash OOS and boot stable or open beta and boot into them with no problems. I've even allowed it to boot to the OOS welcome screen and went back to recovery to flash the custom ROM with the same outcome, doing a factory reset before I flash, after I flash, reboot to recover after flashing to factory reset. I've tried a full wipe in place of factory reset and all different combinations, all with the same result...
What am I missing?
lordcheeto03 said:
What am I missing?
Click to expand...
Click to collapse
I think I've had this issue also--it might be necessary to let the OOS ROM boot up as system--no need to setup the phone, then reboot yourself to TWRP and flash whatever else you want.
It was confusing to me too, and I didn't take notes, so don't know exactly what happened.
Also, maybe don't try to flash things to both partitions--just let the installers do their work as they are made to do without any extra steps.
Since you've already factory reset/wiped, it might help to skip this step also, as a trial.
Did you have Magisk before, and uninstall it first? Might help, as uninstalling restores system images or somesuch.
And, there are some occasions where a ROM flash won't reboot properly without first installing Magisk, but don't recall the incidentals of this either.
Regardless, we'll have a record if you post what steps succeeded in your case.
pbergonzi said:
I think I've had this issue also--it might be necessary to let the OOS ROM boot up as system--no need to setup the phone, then reboot yourself to TWRP and flash whatever else you want.
It was confusing to me too, and I didn't take notes, so don't know exactly what happened.
Also, maybe don't try to flash things to both partitions--just let the installers do their work as they are made to do without any extra steps.
Since you've already factory reset/wiped, it might help to skip this step also, as a trial.
Did you have Magisk before, and uninstall it first? Might help, as uninstalling restores system images or somesuch.
And, there are some occasions where a ROM flash won't reboot properly without first installing Magisk, but don't recall the incidentals of this either.
Regardless, we'll have a record if you post what steps succeeded in your case.
Click to expand...
Click to collapse
Everywhere I've read says to flash OOS to both partitions so if there's an issue with the custom ROM there's a fallback.. I don't flash the custom ROM to both partitions, only OOS. Also, I've tried letting OOS boot to the welcome screen, then back to recovery; I didn't do any setup.
I have magisk installed in OOS, though I haven't tried flashing it when flashing the ROMs. When flashing ROMs I've always flashed the ROM and Twrp, reboot straight to recovery, and flash gapps/Magisk. In my experience, I've been able to skip rebooting back to recovery to flash Magisk and gapps and just boot straight to the barebones ROM.
To reiterate, I use the exact same process to flash OOS and it works flawlessly; can flash the stable or open beta, no issues. It's only non-OOS that refuses to work correctly.
I'm wondering if I need to use the unbrick tool and start from a 100% clean slate .. something may be borked that an unbrick may fix, it's about the only option left that I can think of...
lordcheeto03 said:
Everywhere I've read
Click to expand...
Click to collapse
Good luck whatever you do.
pbergonzi said:
Good luck whatever you do.
Click to expand...
Click to collapse
Thank you for the ideas
I ran the unbrick tool and still encountered the issues, but I did learn something, and also finally got havoc to boot, although I'm still unsure exactly what I did. I'm not saying I figured out exactly what is wrong, and I can't say I know the exact solution, but I CAN say I believe the solution lies somewhere within this wall I'm typing.,..
I noticed this earlier but it didn't actually click until I still got the same error after the unbrick tool... I would always boot correctly to OOS on slot b, so after every successful boot, I'd go into recovery and try flashing.. now taking into account the fact that I flashed OOS in both slots is important because on a successful boot, which would be slot b, I'd go into recovery, still on slot b, so that's the first slot to get OOS. Change slots, flash to slot a, then boot to OOS. If I'm remembering how a/b partitions go, since slot A was the last slot to flash, it would automatically fall back to slot b to boot. Hence the successful boot. Go back to recovery, flash havoc on b, it would attempt to boot from a, and fail.. go back to recovery, I'm back on slot b to start the process over.
After still encountering the problem after the unbrick, I really began paying attention to the boot slots. Once I was paying attention to that, I attempted to manually boot from slot a after flashing OOS to both slots and I got sent to a screen that says Qualcomm crashdump mode. Power +vol up/dn to force a reboot, then volume down until the bootloader unlocked splash screen to go to recovery.
Now this is what I think I did... After figuring out it was the slot, I believe I formatted slot a, and due to the way it fell, slot b then began being the slot to mess up so i made sure to flash havoc/twrp installer in the slot a and it booted right up. Went back to recovery to flash magisk and gapps, and finally a factory reset. Boot from slot a, and here I am.
There were times where I would get stuck in fastboot, boot to recovery or system would just send me to fastboot.. I guess that also meant I was booting from the bad slot. I tried fastboot boot twrp.img, it would send it, but fail to authenticate. Fixed that by doing fastboot --set-active=b then I could restart back to recovery no problem.