It's been quite some time since I put TWRP on my phone, but I used it to flash a "light weight" rom on my V10 and to install Xposed as well, so it most certainly is(was) on there. I just went to boot into it to remove the Xposed framework and ended up doing a full recover of my phone. No harm no foul since all of my stuff is backed up, but I was wondering if anyone else has experienced their TWRP install basically removing itself, until I find the time to re-install it I'm stuck with the rom I have.
How did you manage to install TWRP on your H900? Please tell me
i flashed i rooted stock for my lg h900 but get twrp to install... help
Related
I am caught in a bootloop after attempting to root using the following process.
Using Odin3 v3.10.6, I flashed the following:
n915t-cwm-recovery-6.0.5.1(1128).tar - THIS MAY HAVE BEEN AN ERROR. SHOULD I HAVE USED "openrecovery-twrp-2.8.1.1-trltetmo.img.tar"
I did a full backup to my phone's external SD card from cwm-recovery-6.0.5.1.
I then flashed both the files below without rebooting in between. I did not wipe any cache or data.
Emotion-TW-nightly-r23-RC1-SM-N915T
UPDATE-SuperSU-v2.46
The phone locked when I rebooted and would not move past the first black screen.
I pulled the battery and rebooted to recovery.
I did a restore of my backup that appeared to complete successfully.
I got a message asking to root the phone. I said yes, then rebooted.
Now stuck in a bootloop.
Hoping I can recover from this?
Root only with extra Kernel
When recovery asks to install root at the end, hit no. Thats your issue. You already installed supersu, so you've already got root. Personally I prefer stock kernel, with the latest beta supersu, you can still get root. With Universal init.d app, you can still get init.d support. With a custom build of xposed for Samsung lollipop, you can still get xposed. There's even a special version of viper audio. So yeah all you lose is the overclock ability.
Thank you. I ended up reflashing the firmware and got it working again. I'm still in the same situation, without root. My goal is to install a custom rom but I'm concerned about trying The Root process again. I read that a security patch was done in November for lollipop. Could that have impacted my ability to root and cause me to get into a boot loop? Wondering if there is a more current root method than the one I used.
rootnooby said:
Thank you. I ended up reflashing the firmware and got it working again. I'm still in the same situation, without root. My goal is to install a custom rom but I'm concerned about trying The Root process again. I read that a security patch was done in November for lollipop. Could that have impacted my ability to root and cause me to get into a boot loop? Wondering if there is a more current root method than the one I used.
Click to expand...
Click to collapse
There have been reports that the emotion r23 kernel is finicky, some work soem dont. Try another kernel or older version. That could be toir problem.
Sent from my SM-N915T using Tapatalk
Hello
I have a problem with my Mate. I will try and list the things i did to get to this problem and I hope the information helps solve it.
I wanted to install xposed (first thing I did wrong) so I rooted using King Root (ver 4.8.2) successfully
then unlocked the bootloader using Huawei website
Using Flashy, I flashed TWRP recovery to install xposed (regrets).
After creating back up on TWRP, I tried to flash xposed, didnt work.
I gave up and rebooted phone to android, and i saw i had lost Nav buttons and Notification bar.
Booted back into TWRP and tried to restore my backup. It kept failing at 33% (would post logs but I lost them), I then thought a factory reset would help and it did.
I got the navigation and notification bar, but I soon realised I cannot install apps. I couldn’t install from my SD (apk’s) or from the Play Store.
I can’t install anything on it now. I’ve learnt my lesson not to mess with the inner workings of my device but now I am stuck with EMUI (no Nova or other 3rd party launcher).
Is there any way I can get it back to installing apps as usual? I saw another thread with similar problem (can’t install apps) but I wasn’t sure if I should post there (its old and unattended thread). If I should post this in another thread please point me in the right direction and thank you in advance.
:crying:
I would clear cache and Dalvik cache in recovery then flash back to a stock kitkat recovery, put the correct stock complete kitkat ROM in the dload folder in SD card and do a force update from stock recovery. Once it runs properly again, update to the right ROM you want to run, in the correct order of updates, make sure bootloader is unlocked, root the correct way (not kingroot, use ADB) then seek guidance on what mods work with what ROM. Do not try to root without unlocked bootloader! That ruined it I think.
If you want Xposed, it only partially works in Kitkat, not at all in Lollipop. What do you need with Xposed? I'm running B331 Lollipop now, no Xposed and no real need for it. I do have unlocked bootloader, root and Viper4android and it runs great. I use Smart Launcher Pro but kept Huawei Home (launcher) and theming apps installed so the system is happy but it looks how I want and is good to use.
Thanks for your quick response RobboW, will try that method and let you know if I make any improvement to my situation.
So I have to get a stock KitKat recovery and stock KitKat ROM for that recovery. Do I force an update from TWRP or what? I'll read up on recovering stock Roms and let you know if I make any progress. Thank you for the response though.
Force update with a stock ROM needs to be done from stock recovery. TWRP stops the phone from updating the stock way. The bootloader can stay unlocked if it already is.
It worked exactly like you said. I'm back on Lollipop B324. I can install apps and got the motion control settings back.
Thank you so much RobboW!
You're welcome
OS faults are not so bad if you have access to recovery. It's the ones that make using recovery and ADB difficult that cause the big dramas.
So after more or less randomly trying different things, and fearing that I might only have made matters worse, I hope someone can help:
I have got a Huawei Honor 6 H60-L04 (bootloader unlocked and rooted) and was, until two days ago, running KitKat with the B114 build and cwm recovery. Since Marshmallow has officially benn available for the Honor 6 for a while now, I decided to finally update.
I flashed stock recovery and updated to Marshmallow build B820 via update.app on sdcard. Booting worked fine, however I was unrooted (ofc) so I decided to flash SuperSU (2.76 [latest stable]).
So I flashed twrp 3.0.2.0. and so far all good. Still no problems booting. Then I flashed SuperSU (according to twrp successfully) and rebooted, just to find myself stuck on bootscreen. That is not the first one you get in bootloop but the animated honor logo. Well ****.
Since then I tried many things, wiped multiple times (data is unimportant, but unfortunately I don't have a working twrp backup, please don't lecture me on this, i know -.-), flashed almost any stock ROM I could get my hands on. In twrp I get this Error:
Could not find 'META-INF/com/google/android/update-binary' in the zip file". >"Error installing zip file". "Failed"Somewhere on the way I got
error! Func NO : 9 (FUNC_BOOT_KERNEL) Error NO : 2while booting, that's gone though.
I'm at the point now where I can install B820 via update.app on sdcard, see the installation progress succeed to 100%, reboot, and again, find myself stuck on animated honor logo.
I honestly have no idea what I can do, I hope someone here does. I'll happily provide any further information you might need.
Try and wipe everything, then reflash TWRP. Good luck ?
Sent from my Samsung Galaxy S7 Red using XDA-Developers mobile app
I did that, I lost count how many times. I wiped everything, clean twrp flash, still get the "meta-inf" error message. Maybe someone can provide me with a clean twrp backup for B820? that might actually work.
Ok, after making a fool of myself, I finally found the culprit. Turns out I have to wait a couple of minutes after a new installation for my phone to boot. And all the time I thought it was soft bricked -.-
However, I does get soft bricked whenever I try to flash SuperSU. Root = bricked. Unroot = unbricked. Anyone got an idea how to get SuperSU to work? I really don't want to go back to unrooted...
I used supersu 2.62 with MM.
After install i update supersu with Google play.
Supersu update itself the binary to 2.76.
It works with B820 ans now with B860.
hagehagen said:
Ok, after making a fool of myself, I finally found the culprit. Turns out I have to wait a couple of minutes after a new installation for my phone to boot. And all the time I thought it was soft bricked -.-
However, I does get soft bricked whenever I try to flash SuperSU. Root = bricked. Unroot = unbricked. Anyone got an idea how to get SuperSU to work? I really don't want to go back to unrooted...
Click to expand...
Click to collapse
Haha, next time give the phone a couple minutes.
Sent from my Samsung Galaxy S7 Red using XDA-Developers mobile app
Hi hello guys I really need a help.
I downloaded the Saftetynet fix zip, that must be flashed in Magisk only. I forgot and flashed it in TWRP, my phone is on the bootloop, I don't know what to do.
I really need the help now because I'm busy and need the phone.
Re-flash phone's Stock ROM to get rid off of all the mods you applied.
Hi there, I'm having no luck finding a solution to my problem anywhere.
I'm using a Galaxy S7 running Oreo (I know, old school), and like many phones, it came with a bunch of apps that can't be uninstalled unless you have root access. So, I installed TWRP, and then Magisk v23, and then I installed a root uninstaller in order to remove the apps in question.
However, I use Revolut and an app for the bank I'm with, and so while my device is rooted, I am locked out of both.
What I want is to have the disable-only apps gone, and my device unrooted and back to normal so I can use Revolut and said banking app.
I believe uninstalling Magisk should unroot the device, but without Magisk installed, I can't boot into the system because of TWRP and the whole dm-verity thing. So, I want to replace TWRP with the stock recovery, which, if I'm correct, should achieve the desired outcome.
I downloaded the exact firmware for my phone from sammobile, and the recovery file can be extracted from it easily, but I don't really know how to go about flashing said file, or even if I can. Odin isn't working for me.
I tried flashing the whole "AP" file via Odin (the latest version), but that restored the device back to it's factory state, disable-only apps and all.
So can anyone help me with this? Or is what I want to do here even possible? I'd really appreciate some input / advice. Thanks!
P.S. maybe you can tell, but I'm kind of a noob, so apologies if I'm overlooking something obvious.
Android's recovery where it doesn't matter whether it's Stock or Custom can't be used to unroot Android if it got rooted by TWRP and/or Magisk this because phone's boot.img got tampered by those: you'ld have to completely re-flash phone's Stock ROM to get rid off of all modifications you applied so far.
Okay then, thanks for explaining.
Just to be clear, what you're saying is that it isn't possible to unroot a device and then restore just its stock recovery (to replace TWRP). You cannot undo modifications made to boot.img and therefore must re-flash the stock firmware?
What I do with unwanted system apps on other android phones is to remove the .apk from /system by booting into recovery and using the shell/adb with u**x commands (actually move them somewhere they can't be seen by the O/S with mv command).
Also when faced with dm-verity, Magisk just modified the boot.img
and changes fstab to take out verify from system mount & patches init and removed /verity_key.
I was able to uninstall Magisk (only phone mod was unlocked boot loader allowing custom boot over usb).