Substratum "Could not fall back to rooted mode" - Redmi Note 8 Pro Questions & Answers

"Could not fall back to rooted mode" I have this problem not only with substratum but also with SuperSu, where it sends a similiar message.
My phone is rooted and i am really confused as to why they don't work. Maybe they need to be flashed with twrp? HELP

Related

Help getting back to stock on N5110

Edit: I'm editing this to show what I just posted in a comment elsewhere. I really wish someone would help me because I can't get answers.
"Can you please help me? I'm so lost. I've been at this for quite a few hours, so I'm sorry if I'm unclear, but my brain is fried. I started with the chainlink root (I don't know about unlocking bootloader, like you ask) and I forgot to confirm it was rooted. Installed xposed. Somewhere along the lines I either lost root or was just never rooted, because it doesn't show the pound symbol in terminal, but then I flashed my backup which was after chainlink and before xposed, but I'm stuck in a bootloop on that backup. I tried installing this with TWRP but it just failed and said "error executing updater binary in zip." I thought maybe it was TWRP so now I'm on CWM and it does the same thing. I then tried this but when I do the bootloader upgrade it says I need to, it fails and says SW REV. CHECK FAIL. DEVICE:2, BINARY:1 in red. I don't know what's going on, but I hope I'm not bricked. I just got this yesterday lol any help would be appreciated. I can't find any answers. I really just want the stock 4.4.2 with root and maybe the Boeffla kernel. Please help! Thanks!
Edit: now I unplugged and it's saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" and won't turn off. Queue freak out mode "

V410 7.0 LTE bricked

Ok guys I am pretty sure I fubar'd my tablet.
I am stuck in a recovery loop. When I start the tablet it just goes back into recovery. Which if I still had TWRP I think I could still do something, but I flashed cyanogen recovery trying to flash cm13 since I cold not get anything else to work. I cannot boot into download/firmware update screen. The screen just flickers a little and goes dark.
A little background:
Started when tablet forced install of 5.0 update and I was in a recovery loop. I flashed 410 test build, rooted, flashed twrp, installed stock rooted ROM. Everything was fine. Then tablet did it again, this time I just flashed rooted ROM and factory reset. Even took the steps to fix the white lines and storage issues. Was working fine. Got home a few days ago and I was in a recovery loop again. But now I don't have the bootloader screen/download mode/firmware update screen (whatever you want to call it) so last night i tried to download cm13, Gapps and cyanogen recovery with no avail.
I can access adb on my PC while in recovery, but when I try to access ADB shell I get unauthorized something or other. Because I cannot authorize USB debugging, because ROM won't boot. I tried to flash stock rooted ROM from cyanogen recovery and it says not signed or something like that.
Does anyone have any ideas? I really think I have screwed the pooch here.
sent from a device using an app
title
if you have a stock recovery image flashing it is easy, i had a LOT of troubles with my v410 and still am working with it. i have mine rooted, just with TWRP though, i cant use xposed framework, which negates why i rooted this in the first place. anyway, through much grit and determination flash your stock image after wiping what needs to be wiped and doing all other necessary things. Then, you must download kingo root, supersu, superuser. flashify would help with the flashing i hear, but it has troubles with the v410. kingo root was an apk i managed to find buried under a million viruses on the 34th page of google..or something. rooted mine in one click, from stock to reboot to twrp root.. many glitches.
I need help myself, deleted my "Phone" system app, causing me to lose connectivity with my data plan. cant seem to restore it, and flashify nor twrp has been able to flash a custom recovery, or a backup, im at a loss.
Help? We seek the same thing.
Ok but how do I flash the stock recovery image. I can't use fastboot. ADB says I am unauthorized.
sent from a device using an app
Anyone have any other ideas?
I am at a complete loss. I am by no means a developer, but I do know my way around. I really think I have FUBAR'd this one.
Kind of stinks, I give up. Anyone want a bricked v410?
Sent from my Galaxy Tab 2 using Tapatalk

'Unfortunately setup wizard has stopped' after trying to return to stock

Hello,
need a lot of help trying to get my EU HTC 10 working again.
Im very new with this kind of stuff and have obviously messed something up on my device. I was running LeeDroid on my HTC 10, (bootloader unlocked, twrp recovery installed), however i wanted to return to stock and followed guides on xda.
I flashed a twrp recovery backup and rebooted my device, i then flashed stock recovery and re-locked the bootloader. After rebooting my device again a message pops up onto the screen saying 'unfortunately setup wizard has stopped'. I cannot get past this message and do not have twrp installed anymore to re-flash any rom, and do not have usb debugging enabled in settings and cant enable as i cant get into device.
I have tried using an RUU.exe to restore phone how ever the installer give me error 170 (device not detected). I have also tried to ruu.zip from my sd card however i get error '19 RU-MAIN-VER-FAIL os-version in android-info missing or i'.
anyone have any ideas on how to proceed.
Thank you!
orangeali said:
Hello,
need a lot of help trying to get my EU HTC 10 working again.
Im very new with this kind of stuff and have obviously messed something up on my device. I was running LeeDroid on my HTC 10, (bootloader unlocked, twrp recovery installed), however i wanted to return to stock and followed guides on xda.
I flashed a twrp recovery backup and rebooted my device, i then flashed stock recovery and re-locked the bootloader. After rebooting my device again a message pops up onto the screen saying 'unfortunately setup wizard has stopped'. I cannot get past this message and do not have twrp installed anymore to re-flash any rom, and do not have usb debugging enabled in settings and cant enable as i cant get into device.
I have tried using an RUU.exe to restore phone how ever the installer give me error 170 (device not detected). I have also tried to ruu.zip from my sd card however i get error '19 RU-MAIN-VER-FAIL os-version in android-info missing or i'.
anyone have any ideas on how to proceed.
Thank you!
Click to expand...
Click to collapse
I've never wanted to return to stock, especially after running leedroid. So not 100% but have you tried a factory reset?
squ89r97 said:
I've never wanted to return to stock, especially after running leedroid. So not 100% but have you tried a factory reset?
Click to expand...
Click to collapse
Yes i have tried a factory reset but i still cannot get past the 'unfortunately, setup wizard has stopped' screen.
Thanks for the fast reply!
Any other ideas?
Ok Solved!
used official ruu.zip like in a thread on here.
Running nougat on stock.
Thanks for your help!

"Error occurred while updating..." Think I have bricked while attempting to downgrade

"Error occurred while updating..." Think I have bricked while attempting to downgrade
Please help.
I was attempting to root and SIM unlock the SM-G925T. It was already on Nougat 7.0 (and November 2017 security/patch).
CF Auto Root would not work. Neither did an attempt to manually flash TWRP (although attempting one of those two tripped KNOX).
I thought I'd downgrade to Marshmallow and then re-attempt root/unlock. Downloaded "G925TUVU5EQC2" from gsm-firmware and tried to execute via Odin.
I am left with a permanent blue screen with that "!" reading I need to use Smart Switch's Emergency Recovery. That, btw, does not work either (and neither does re-attempting after reinstalling device drivers from within SS).
Could someone please suggest what I should do? Pressing and holding power/home/vol- keeps taking me back to this blue screen. Unable to get to the recovery or anywhere for that matter.
Ok, so... Despite not seeing any other screen, I went ahead with reflashing the Marshmallow ROM via ODIN. Worked this time and the phone rebooted.
Interestingly, now, my unlock request was approved by the Device Unlock software (didn't need to use other means). However, I am stuck on Marshmallow and the device won't update to Nougat (get the error "phone not registered", despite it being unlocked). Hilarious. But at least the phone is functioning now.
Followed the same ODIN method and flashed the latest 7.0 image (Nov 2017 patch). Thankfully, it retained the unlock. Not sure if it can upgrade (I don't see the "not registered" error) but I won't know till there is a release.
Briefly got an annoying "com.sec.vsimservice stopped working" error - booted into Android recovery, wiped cache and did a factory reset. Working now!
Had already tried rooting this version (using both CF Auto Root and TWRP), but in vain, so not harbouring hopes now. Will get back to it later.

Moto z2 force t-mo update failed

Hi, I was rooted Magisk and twrp installed, I kept getting a notification of an update but just kept ignoring it. About the same time my phone started dropping signal all the time so I thought it might have something to do with the update. I went back to full stock 27.1 . When I try to get the update it downloads it and when it gets ready to install it says working in the background it shows a progress bar for a sec then pops up a screen telling me that something went wrong and update failed and nothing was changed and i just click ok. I get no type of error messages or any thing explaining what the problem is. As of right im not rooted or any custom rom or recovery installed just bootloader unlocked, SO what did I do wrong and how do I fix it???
When you say you went back to stock, do you mean you factory reset or you went as far as doing the flash-all?
Unseeablething said:
When you say you went back to stock, do you mean you factory reset or you went as far as doing the flash-all?
Click to expand...
Click to collapse
I did the flash-all...
I too did a flash all after installing the OTA, now I can't install the OTA anymore.

Categories

Resources