Hi everyone, for quite some time I never had any issues upgrading mu phone MIUI, but recently the update process keeps failing, with Recovery Project 3.0.2-x complaining that the image zip (miui_MI5SPlusGlobal_9.6.27) is corrupted.
I started looking a bit more into it and it turns out my phone doesn't show as correctly rooted, so I was getting ready for doing a full root procedure, I backed everything up, get back to some tutorials and it seems like I should use TWRP and SuperSU.
It seems like SuperSU has been discontinued, so now I am kinda hanging, not being sure at all what I should do :S I would ideally want to upgrade to the latest MIUI
Any tip?
First Flash latest recovery.
https://dl.twrp.me/natrium/twrp-3.3.1-0-natrium.img
Download this latest Miui rom
https://sourceforge.net/projects/xi...5SPlus_V11.0.2.0.OBGCNXM_v11-8.0.zip/download
Do the wipes and install it.
For root you should flash magisk.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/
Related
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
jpp2109 said:
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
Click to expand...
Click to collapse
From what I've read about that issue is people have had to Odin back to stock then start over. Now maybe you could try installing another recovery like Philz maybe using Odin or try Goo for TWRP before you Odin back to mdk and go through all that.
Sent from my SCH-I545 using Tapatalk
I had a similar thing a few years ago, with what I know now I think the recovery is temporarily flashed with CWM to gain root and stock recovery is replaced after, I'd look for an actual CWM recovery to flash in.
Same applied to me using a ROM Manager, said it was v.xxx made a backup, flashed a ROM, turns out was left without a backup..... noob-old days
Bashing away at my HTC Desire C
Thank you for the solid replies, I'm interested in getting experience with the other recovery methods anyway so I'll try those and worse case I start from scratch.
I have pretty much this same issue. I was happily running 6.0.44 CWM, installed via CWM.
Then I happened to check and see there's an update to 6.0.47. I installed via ROM manager which reported success. Except that it isnt. I basically have 2 recoveries as far as ROM manager is concerned. It thinks I'm on 6.0.47, but 6.0.44 is what boots. I'm betting it's the same issue you have.
I re-flashed Twrp trying to fix it. Now twrp is what recovery always boots; but Rom manager still thinks 6.0.47 is installed. Rom manager shows BOTH recoveries in the "Recovery already installed" menu.
Seems the issue here is the 6.0.47 when flashed via Rom manager. It bugs the crap out of me that it seems like I have 2 recoveries installed somehow. Not sure how that's possible, but everything seems like it's functioning for me.
Compare the sizes of the recoveries, one thing I've come across is when you flash a new .img in because of the NAND chip process for writing/erasing I have had 'remnants' from previous files.
In one respect it is unlikely but I wouldn't rule it out until you check yourself. It could just be left on the list as a marker that it has previously been installed.
Personally I don't use ROM Managers now, it's into TWRP Recovery and backup from there
Bashing away at my HTC Desire C
Look Like I'll Have to Start From Scratch
I'm just getting back to this because work was crazy. No Matter what recovery I try always comes up with Android System Recovery 3e. Stock MDK and re-root it is.
Maybe try using GooManager to install TWRP after you've gone back to stock.
Well, it seems like I have ****ed up trying to flash Gapps onto my brand new Nubia Z5s (not the mini version)
The first thing I did was rooting it (using Vroot or Iroot) which worked perfectly. It installed Superuser just fine
Then I had some problems getting a custom recovery.
After ****ing up my recovery by flashing with the chinese tool most people seem to use, I finally got a working english CWM (using the program depicted in the first image of this thread http://forum.xda-developers.com/showthread.php?t=2749259).
At this point I should have made a backup, but I did not. Retarded me installed flashify and used it to flash Gapps. That's where it went wrong. When the phone rebooted, I got flooded with error messages about google processes that had stopped. I did manage to get into my settings screen, where I don't get flooded. From there I can alter USB debugging and all that stuff.
I then made a backup from CWM recovery of this situation, which is the one I currently am in. I did try to flash another Gapps zip over the Gapps I flashed with flashify, but that just sent my device into bootloop. I got out of bootloop by restoring the backup I made. I also tried flashing MIU (http://www.needrom.com/download/nubia-z5s-miui-v5-2/). It looked fine for the first minute, but then it suddenly started rebooting at random, and it turned out most apps woulden't open. So I restored to the backup once again.
Could anyone please help me figure out how to get Gapps working? I frankly dont care on which rom, as long as it doesn't have buggs (The stockrom didn''t have any either).
Topic can be closed or deleted, already solved the issue:
I flashed a rom from Needrom,. which is the stock Nubia OS with Gapps built in. Works perfectly now!
Hello,
These past two days have not been a good day for my phone lol. Some background:
BEFORE:
I had a 4.4.4 Custom ROM [Forgot the name...]
TWRP: 2.5.0.2
AFTER:
I clean flashed http://forum.xda-developers.com/gal...m-cyanogenmod-12-0-nightlies-verizon-t2998057
I cleared cache + Dalvik after the flash and it asked me if I wanted to fix root (From what I read before, you're never supposed to press Fix, rather you're supposed to prses Do not Fix and you'll still keep your root.
However, I accidentally pressed Fix Root and Now I lost my root. The ROM I flashed is glitchy because from what I read is because I have TWRP 2.5.0.2.
Now I'm stuck on this ROM, I have no idea how to upgrade to the latest TWRP and don't know how to get my root back . [Can't get TWRP Manager because I don't have Google apps (I tried flashing the GAPPS by Paranoid but it keeps crashing because I think it's the outdated TWRP)]. I tried to download TWRP manager on my phone via another site, but it doesn't install on my phone for some weird reason.
Thank you,
Jerry
Download, install and run the towelroot.apk file. This will root your phone, takes about 2 minutes
Hello there I have a couple questions regarding to the red honor boot logo and also on how to update from a stock rom with TWRP and root ( also a couple of system modifications ) to the new B331 update.
So heres the rundown, when I first got my honor 5x I did not spend too much time on the stock rom I went ahead and rooted my phone and installed TWRP then made a backup of my stock rom (B151) no modifications other than SuperSU being installed. After that I went ahead and installed CM13 nightlies and updated mostly everyday up until the build July-18-16. I had adoptable storage enabled with my 32GB SD card and I totally forgot to disable the adoptable option before I reverted to my stock backup so when I went onto TWRP and tried to restore my backup I always got an error where it said something along the lines " error; could not find system" but instead of it backing out it continued to restore and bricked my phone. I had a somewhat clever idea to flash any build of CM13 I had on my computer and guess what it booted then I disabled the adoptable storage and booted back onto TWRP restored my backup and everything was fine until it booted and I noticed the honor boot logo had a red "h". I found that weird since I have restored my backup previously and that never happened. Anyone knows what it could mean and how to fix it?
My second question is how should I go about updating to B331? Should I download the stock recovery B151 ( since that is what shipped with my phone and is what my backup is) then revert to my near stock backup, flash stock recovery and unroot then update through cslA's B331 instructions? Or should I somehow fix the red honor boot logo then go ahead with what I stated above or is this all done differently? I am not a newbie at these kind of things I just moved onto more important things in life and simply want to update my phone. My needs for flashing new roms daily are over and I just simply like huawei's UI as it just "works" for me. Thanks to anyone who responds anything is appreciated as I can't seem to get my old skills working again. Haha:laugh:
Fibgerprint aint working right? U cant go back to stock with just a normal twrp backup. Install an update.app through dload for your region and then apply the twrp backup.. Make sure you are on B151 Recovery!
Demian3112 said:
Fibgerprint aint working right? U cant go back to stock with just a normal twrp backup. Install an update.app through dload for your region and then apply the twrp backup.. Make sure you are on B151 Recovery!
Click to expand...
Click to collapse
No, my fingerprint is working... I just wanted to go back to stock ROM with root and that's what I got just now I have a red honor bootlogo. Now I want to update to marshmallow but I have a fear that even if I follow the steps onto reverting to stock I may brick it because of the red bootlogo.
So what you are saying is I should download my B151 recovery and firmware to revert to stock then update and from there I should root and install TWRP?
Hi all,
As I understand it is impossible to get OTA on rooted phone with costume recovery.
What is the solution for updating the phone?
As far as I can see the only solution is to flash complete ROM whenever it is released, but that means factory reset, re-installing the apps, and re-setting all the system settings to my liking everytime, and that just sucks.
Is there a better solution?
I remember that with the galaxy s3 I had it was possible to get flashable zip of the OTA updates, I couldn't find a similar thing for the Honor 9
Read this: Root with magisk while keeping stock recovery
https://forum.xda-developers.com/redmi-note-4/how-to/guide-root-using-magisk-stock-recovery-t3718203
I just installed the latest miui 9 beta ota in TWRP with no problems.
After flashing the beta (before rebooting) I flashed TWRP and majisk. When I finished flashing I cleared cache/dalvic and rebooted with no problems.
I accidentally posted it in the wrong forum (that what happens when you have 2 phones to manage I guess)
Was supposed to be in Honor 9 forum