Database Info

Nexus 5 CWM problem?

So I'm trying to install custom ROM on my friend Nexus 5, should be a 2 minute job turns into 2 hours..
CWM is giving me a list of can't mount anything basically.
I tried fe-flashing the entire phone back to stock via fastboot, that went fine, flashed recovery again to CWM.. and can't mount anything again..
I need to be able to mount in order to install zip...
anybody can help??

now i got it to boot with purity ROM, telling me on startup with no google sign in... "
System UIDs Inconsistent. UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."

THE_KINGDOM said:
now i got it to boot with purity ROM, telling me on startup with no google sign in... "
System UIDs Inconsistent. UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
Click to expand...
Click to collapse
yup, you will need to wipe and reflash.

still can't mount sdcard in recovery..
so i can't do anything.. I had to sideload the ROM..

so i've done a bat flash all, restore to stock..
I don't get why everytime i flash CWM custom recovery I can't load anything.. how the hell do I install purity from stock if I can't install CWM ?!

THE_KINGDOM said:
so i've done a bat flash all, restore to stock..
I don't get why everytime i flash CWM custom recovery I can't load anything.. how the hell do I install purity from stock if I can't install CWM ?!
Click to expand...
Click to collapse
try twrp recovery

but i've been using CWM forever on every nexus device without problems..
I though process is simple.
1. Unlock bootloader
2. Fastboot flash recovery recovery.img (cwm)
3. wipe & install custom ROM (Purity)
4. gapps
5. start phone..
what am I missing???

so I tried installing the previous version of CWM 6.0.4.4 and CWM problems seems to be resolved.. clearly they must have issued with the latest version.
Now im able to read /sdcard and hopfully install purity ROM, gapps etc.
but I'm still getting the system UID's inconsistent issue...
what a colossal waste of time...

ok phone back to stock at again with a batch restore all file.. factory files...
how the ****ing hell do I install a custom ROM?!?!?!? Like iv'e done this a million times before.. what am I missing??????

anybody?????

THE_KINGDOM said:
ok phone back to stock at again with a batch restore all file.. factory files...
how the ****ing hell do I install a custom ROM?!?!?!? Like iv'e done this a million times before.. what am I missing??????
Click to expand...
Click to collapse
Put a custom ROM.zip and gapps package on storage, flash in recovery, flash SuperSU if necessary?

THE_KINGDOM said:
anybody?????
Click to expand...
Click to collapse
No bumping within 24 hours is the forum rule. I also believe they should set a punctuation limit. Chill out
Sent from my Nexus 5 using Tapatalk

Lethargy said:
Put a custom ROM.zip and gapps package on storage, flash in recovery, flash SuperSU if necessary?
Click to expand...
Click to collapse
this is what ive been doing.. when phone boots it doesn't ask for google login credentials and goes straight to android is upgrading as if I did a dirty flash and then tell me i have a UID mismatch, and to wipe data partition..
i've now reinstalled this phone close to 6 times.. I cannot figure this out

THE_KINGDOM said:
what am I missing??????
Click to expand...
Click to collapse
cwm recovery SUCKS. but if you are unwilling to try other recoveries, oh well..

THE_KINGDOM said:
this is what ive been doing.. when phone boots it doesn't ask for google login credentials and goes straight to android is upgrading as if I did a dirty flash and then tell me i have a UID mismatch, and to wipe data partition..
i've now reinstalled this phone close to 6 times.. I cannot figure this out
Click to expand...
Click to collapse
Well somewhere you're not wiping properly. Flash the factory images again using the flash-all.bat included in the compressed file as it'll wipe everything, then go from there.

Stock CWM always has issues. It's based on an outdated version of Android so it doesn't always play well with KitKat. I would recommend either TWRP or Philz Touch CWM.

Lethargy said:
Well somewhere you're not wiping properly. Flash the factory images again using the flash-all.bat included in the compressed file as it'll wipe everything, then go from there.
Click to expand...
Click to collapse
flashed factory img aroudn 6 times now.. every single time i got back to put on CWM and then flash the rom i get a UID mismatch, bunch of force closes etc..

BirchBarlow said:
Stock CWM always has issues. It's based on an outdated version of Android so it doesn't always play well with KitKat. I would recommend either TWRP or Philz Touch CWM.
Click to expand...
Click to collapse
CWM is built from CM11 4.4.3 source code.. But yeah it has issues., lacks functionality and also is antiquated
Sent from my Nexus 5 using Tapatalk

THE_KINGDOM said:
flashed factory img aroudn 6 times now.. every single time i got back to put on CWM and then flash the rom i get a UID mismatch, bunch of force closes etc..
Click to expand...
Click to collapse
Don't know what to tell you, just try TWRP. I've had issues with CWM on every single device I've put a custom ROM onto (Xperia Arc S, HTC One M7, Galaxy S4, HTC One M8, Galaxy Note 3, Xperia Z, Nexus 5), and never had a single issue with TWRP on any.

gonna try Philz Touch CWM and if that doesn't work then TWRP

Bootloop, no matter what ROM

I decided recently, with the release of towelroot, to root my Transformer. I was having performance problems since the Jellybean update, but the optimizations I installed improved it. There was still some lag though, so I tried to flash a Cyanogenmod 11 nightly. There were no errors from CWM, but the tablet stalked at the bout animation. I tried an OmniROM homemade, same story. I flashed the newest OmniROM nightly, the GApps package listed on the OmniROM thread on here, and the US_epad-user-10.6.1.27.5 kernel, no soap. I can get Windows to detect the tablet when CWM is in sideload mode, but fastboot never connects, so I can't flash another recovery.
Sent from my Droid Ultra

What version of CWM you are using ?
Maybe you should update it via a flashable zip (no need to pc)
And a good advise, always wipe cache & dalvik cache after flashing rom and before reboot.

I'm using 6.0.4.7. I've been using a jump drive plugged into the dock to load ROMs, so I haven't connected directly to the computer for a while. I've wiped cache and dalvik before flashing nearly every time, and after several times.
Sent from my XT1080 using XDA Premium 4 mobile app

Ok if you still have the OmniROM image, try to flash it exactly as follow :
1- Wipe system, data, cache and dalvik cache
2- install OmniRom
3- install gapps
4- install kernel
5- wipe again cache and dalvik cache before reboot
6- reboot
Download links for latest gapps and kernel are in my signature (Geass is the best kernel IMO)

OK, I'll give it a shot. Probably ten minutes.
Sent from my Droid Ultra

Whenever I try to format /data, it says Error mounting /data! Would this be part of the trouble, perhaps?

It's all flashed, but it looks like it hung up during the boot sequence again. I'll let it sit a while longer, and see what happens.

OK, it did absolutely nothing. I haven't worked on it for a while, because between work and the rest of life, I haven't really needed it. It is the same state, though.

travisw495 said:
OK, it did absolutely nothing. I haven't worked on it for a while, because between work and the rest of life, I haven't really needed it. It is the same state, though.
Click to expand...
Click to collapse
Look up buster99's fix. I think that is what you need to do next.

Cyanogen Mod 6.0 for OPPO R7 PLUS

I apologize if this is posted, but we now have an official build of Marshmallow for our Oppo r7 Plus (F) Variant. link attachedhttp://download.cyanogenmod.org/?type=nightly&device=r7plus

Excellent! I am going to test it right now and will report!!!!
Update: I was on ColorOS, flashed cm13 recovery and done factory reset, formatting cache is taking around 8 minutes, is that normal?
Flashing ARM64 opengapps for 6.0 end up with error: E:Installation error in /sideload/package.zip (Status 255) - seems like recovery problem as many people report this issue. I only dont know if TWRP will work with CM13 rom

Personally I'm using a 12.1 recovery at the moment. The 13.0 recovery is still WIP AFAIK.
Gesendet von meinem R7plusf mit Tapatalk

Ok, will try cm12.1 recovery, what about gapps? Which one to use? Btw I have done factory reset again, flashed cm13 rom only, phone rebooted and loading apps (total of 87 I think), then done reboot, then only showing blue android logo for very long time, like 10 minutes followed with another "starting apps" screen with 21 left or so, now another reboot with blue android logo. Is this normal for MM roms? Still not finished.
EDIT: after another 5 minutes same screen appears with saying starting android... 21 apps left, blue android logo when done - seems to be as bootloop as it is going nowhere from here.
CM13 rom flashed fine over TWRP, flashing gaaps now seems to be alright as well (open_gapps-arm64-6.0-mini-20151218).

Very exited, good job

so far I am getting the boot-loop also. will wait to here what Nexus5-32GB will post (if any success with the cyanogen recovery) before reverting back

Sadly "Androis is starting... Starting apps" is last message I can see, the soft reboot then followed wit this bootloop. Same when flashed with and without gapps from TWRP, cm12.1 and cm13 recoveries.
When doing factory reset in CM12.1 recovery I get this:
-- Wiping data...
Formating /data...
E:Failed to start /data/data/org.cyanogenmod.audiofx
Formating /cache...

Guy's I got it to boot up and install so far everything seems to work okay (Minus minor distortion when automatically switching to landscape, portrait and at start up) . I am going to post a picture if I can. I believe the issues arise when we try updating to Marshmallow from lollipop and we have made major modifications. (for example I had lolli viper and a host of other customization's). I had to do a factory reset wipe and format. I then installed a backup that was untouched bone dry cyanogen mod (no g apps yet). let that boot-up and rebooted into recovery. I then downloading the nightly form (today) the 18th from the website with the marshmallow G-apps. Pushed to my sd card, wiped cache and installed the nightly and installed the correct marshmallow G-apps (ARM 64 6.0) right away. After this,I rebooted phone (it will take a while; almost as long as it did when the first nightly for lollipop came out and we flashed from color OS). It's up and running on my phone. I also still have and used the twrp recovery.

Nexus5-32GB said:
Sadly "Androis is starting... Starting apps" is last message I can see, the soft reboot then followed wit this bootloop. Same when flashed with and without gapps from TWRP, cm12.1 and cm13 recoveries.
When doing factory reset in CM12.1 recovery I get this:
-- Wiping data...
Formating /data...
E:Failed to start /data/data/org.cyanogenmod.audiofx
Formating /cache...
Click to expand...
Click to collapse
check out my post after this (well before now)

coled3 said:
Guy's I got it to boot up and install so far everything seems to work okay (Minus minor distortion when automatically switching to landscape, portrait and at start up) . I am going to post a picture if I can. I believe the issues arise when we try updating to Marshmallow from lollipop and we have made major modifications. (for example I had lolli viper and a host of other customization's). I had to do a factory reset wipe and format. I then installed a backup that was untouched bone dry cyanogen mod (no g apps yet). let that boot-up and rebooted into recovery. I then downloading the nightly form (today) the 18th from the website with the marshmallow G-apps. Pushed to my sd card, wiped cache and installed the nightly and installed the correct marshmallow G-apps (ARM 64 6.0) right away. After this,I rebooted phone (it will take a while; almost as long as it did when the first nightly for lollipop came out and we flashed from color OS). It's up and running on my phone. I also still have and used the twrp recovery.
Click to expand...
Click to collapse
going to give this a go, but I was doing factory reset and format as well, is that mean the factory reset doesnt work as it should? Flashing cm 12 rom first to be able to boot to cm13 rom later is very strange way when you think about it

Nexus5-32GB said:
going to give this a go, but I was doing factory reset and format as well, is that mean the factory reset doesnt work as it should? Flashing cm 12 rom first to be able to boot to cm13 rom later is very strange way when you think about it
Click to expand...
Click to collapse
indeed i agree 100%. I really think it boils down to if we have any customization. I had the same error (in regards to the audio FX) You should try installing a fresh clean cyanogen nightly without g-apps or any mods. Let it boot-up and try the steps i mentioned. do you have an audio customization or any that might have changed something (it shouldn't matter but I'm considering any and everything)? If this is the case the recovery might need tweaking as that would mean somehow or someway it doesn't allow us to properly wipe and format (another consideration). I really hope you and everybody else can also update. I'm trying to upload screenshots of my phone

coled3 said:
indeed i agree 100%. I really think it boils down to if we have any customization. I had the same error (in regards to the audio FX) You should try installing a fresh clean cyanogen nightly without g-apps or any mods. Let it boot-up and try the steps i mentioned. do you have an audio customization or any that might have changed something (it shouldn't matter but I'm considering any and everything)? If this is the case the recovery might need tweaking as that would mean somehow or someway it doesn't allow us to properly wipe and format (another consideration). I really hope you and everybody else can also update. I'm trying to upload screenshots of my phone
Click to expand...
Click to collapse
I was on ColorOS while ago, went to TWRP and done manual wipe of Dalvik, System, Data and Cache. Installed latest cm12.1 rom without any gapps and let it boot up to home screen. Went back to TWRP and done same wipe as before. Installed cm13 without any gapps and this time I got little further than ussualy, I could see message "finishing boot" but again end up in bootloop as before. So no luck in my case...
About the error in TWRP: yes I was using viper4android before and it seems the TWRP recovery doesnt wipe the device right way - well actually not even CM recoveries can I think.

Nexus5-32GB said:
I was on ColorOS while ago, went to TWRP and done manual wipe of Dalvik, System, Data and Cache. Installed latest cm12.1 rom without any gapps and let it boot up to home screen. Went back to TWRP and done same wipe as before. Installed cm13 without any gapps and this time I got little further than ussualy, I could see message "finishing boot" but again end up in bootloop as before. So no luck in my case...
About the error in TWRP: yes I was using viper4android before and it seems the TWRP recovery doesnt wipe the device right way - well actually not even CM recoveries can I think.
Click to expand...
Click to collapse
The events you listed I went through the same exact sequence. Keep trying it took for me; after a painstaking install experience of course. Also you're right Cyanogen recovery doesn't allow full wipe and install.

coled3 said:
The events you listed I went through the same exact sequence. Keep trying it took for me; after a painstaking install experience of course. Also you're right Cyanogen recovery doesn't allow full wipe and install.
Click to expand...
Click to collapse
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research

Nexus5-32GB said:
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Click to expand...
Click to collapse
let me know if it ends up working. I also had to hold power button to restart a couple of times after installing 13 and eventually took. Fingers crossed for you!!!!! "GO NEXUS.. GO ..GO.. GO NEXUS " HEHE

coled3 said:
let me know if it ends up working. I also had to hold power button to restart a couple of times after installing 13 and eventually took. Fingers crossed for you!!!!! "GO NEXUS.. GO ..GO.. GO NEXUS " HEHE
Click to expand...
Click to collapse
am not gonna mess with restarts and so on. What I just did was, I installed the cm12.1 and tried to run system update which downloaded the cm13 rom and flashed it in twrp ending with same bootloop. I dont really know how devs could make this working on their phones at all.

Nexus5-32GB said:
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Click to expand...
Click to collapse
pls help me with the stock recovery ..before flashing stock recovery should i clean wipe using twrp..what all should i select for a clean wipe..i had issues with flashing stock recovery..when i selected wipe data and cache in oppo stock recovery it wipes for a secnd and then swithc off..could not get beyond that..after many twrp boot loops now i have a cm12 working ..but battery is very poor..so i want to go back to stock..please tell the steps..

Nexus5-32GB said:
am not gonna mess with restarts and so on. What I just did was, I installed the cm12.1 and tried to run system update which downloaded the cm13 rom and flashed it in twrp ending with same bootloop. I dont really know how devs could make this working on their phones at all.
Click to expand...
Click to collapse
Well, I took my 12.1 installation without any wipe, went to CM recovery from 12.1, installed my (self compiled at that time) build + opengapps (it's important to install those before booting M for the first time), booted, done. I don't have any /system mods though.
I guess I'll try the nightly and see what happens there. Did anybody of you get a logcat of the failed boot attempts?
Gesendet von meinem R7plusf mit Tapatalk

unni84kollam said:
pls help me with the stock recovery ..before flashing stock recovery should i clean wipe using twrp..what all should i select for a clean wipe..i had issues with flashing stock recovery..when i selected wipe data and cache in oppo stock recovery it wipes for a secnd and then swithc off..could not get beyond that..after many twrp boot loops now i have a cm12 working ..but battery is very poor..so i want to go back to stock..please tell the steps..
Click to expand...
Click to collapse
Just follow this quide with flashing twrp, only instead of twrp flash the stock recovery image. http://forum.xda-developers.com/showpost.php?p=63189590&postcount=5 Sorry, there is only boot command, you should type "fastboot flash recovery stock.recovery.img" - when "stock.recovery.img" is a filename of your stock recovery downloaded on your computer.
No need for wipe when installing recovery. I recon to install stock recovery and then install stock ColorOS from it, let it boot, install twrp later and do what you want then.

Looks like it's broken for everyone. I tried multiple recoverys, full wipes including /system and no joy. Guess we'll just have to wait!

Bootloop upon flashing Open Gapps in CyanogenMod 13

Hello!
I could not find any other threads related to this issue, so my apologies if this is a "duplicate" thread
So I found my old Samsung Galaxy Tab 2 10.1 (Model GT-P5113 in Samsung ROM, identified as Galaxy Tab 2 in CyanogenMod) in a cabinet doing nothing, so I thought I would flash CyanogenMod on it and get some use out of it. And so I did; I flashed the nightly build of CM 13 in the "espresso wifi" image. Now, that worked just fine, but when I tried to flash open gapps (open_gapps-arm-6.0-nano-20161217.zip to be exact), I got some sort of boot loop; the device starts and gets into the App Preparer thing (pardon my ignorance) and begins preparing the google apps, and once it does all 16 apps, it starts preparing some other cyanogen mod apps, or at least I believe they are cyanogen mod apps, and then the app preparer just closes, and the boot animation restarts. If I wait long enough, it will once again get to the app preparer and begin flashing 2 apps, I could not see the first one, and the 2nd was the Google app. It would then begin flashing the cyanogen mod apps and then it would close, and the cycle would restart. I flashed Gapps right after flashing cyanogenmod; I did NOT boot into the rom upon installing open gapps. Does anyone know how to resolve this issue? I will provide more information if it is needed. All help is appreciated.

You should only flash gapps RIGHT AFTER you flash CM13. If you flashed it after Cm13 boots up, you will face some issues. (Like bootloops, force closes, etc)
Sent from my espresso3g using XDA Labs

Lightracer said:
You should only flash gapps RIGHT AFTER you flash CM13. If you flashed it after Cm13 boots up, you will face some issues. (Like bootloops, force closes, etc)
Click to expand...
Click to collapse
Hi, Lightracer, thanks for the reply! I did not boot up the tablet after installing CyanogenMod; however the same result occurs whether I flash it with or without a boot up in between (I needed to reflash CM multiple times)

What recovery are you using? Are you sure you're flashig the right opengapps package? (6.0 nano/pico work just fine)
Sent from my espresso3g using XDA Labs

Lightracer said:
What recovery are you using? Are you sure you're flashig the right opengapps package? (6.0 nano/pico work just fine)
Click to expand...
Click to collapse
Yes, I am using the right package; arm 6.0 nano with TWRP recovery

What happens if you let it complete rebuilding the ART cache (app preparer)? Does it do that everytime? Also, did you do a clean flash? (Wiping System, data, cache, art cache, and then flashing the rom? I never had issues like that with installing gapps :silly:
Sent from my espresso3g using XDA Labs

chompy33 said:
Yes, I am using the right package; arm 6.0 nano with TWRP recovery
Click to expand...
Click to collapse
which version of twrp??

smart-t78 said:
which version of twrp??
Click to expand...
Click to collapse
TWRP version 2.8.5.0 (I apologize, I would have said this in the above post, however, I was not home at the time so I was unsure)

Lightracer said:
What happens if you let it complete rebuilding the ART cache (app preparer)? Does it do that everytime? Also, did you do a clean flash? (Wiping System, data, cache, art cache, and then flashing the rom? I never had issues like that with installing gapps :silly:
Sent from my espresso3g using XDA Labs
Click to expand...
Click to collapse
I think I wiped it, however, I may have not wiped everything that was required. I will try this and post back.

chompy33 said:
TWRP version 2.8.5.0 (I apologize, I would have said this in the above post, however, I was not home at the time so I was unsure)
Click to expand...
Click to collapse
thats the cause of your problem. wrong twrp version. go to andi34.github.io and download the latest common twrp (3.0.2-8). choose the zip. you can install it with your current twrp. then reboot back into recovery and reinstall rom and gapps.

smart-t78 said:
thats the cause of your problem. wrong twrp version. go to andi34.github.io and download the latest common twrp (3.0.2-8). choose the zip. you can install it with your current twrp. then reboot back into recovery and reinstall rom and gapps.
Click to expand...
Click to collapse
That worked, thanks! I was initially following CyanogenMod's guide for the specific Galaxy Tab 2 Models (P5100,P5110/P5113), which included older CM images and the older TWRP, but flashed the espresso wifi image upon realizing that the guide was out of date. Also, the newest version of TWRP I could find for the Galaxy Tab 2 was version 3.0.0.0, but it still worked fine.
Thanks to everyone who participated in this thread!

chompy33 said:
That worked, thanks! I was initially following CyanogenMod's guide for the specific Galaxy Tab 2 Models (P5100,P5110/P5113), which included older CM images and the older TWRP, but flashed the espresso wifi image upon realizing that the guide was out of date. Also, the newest version of TWRP I could find for the Galaxy Tab 2 was version 3.0.0.0, but it still worked fine.
Thanks to everyone who participated in this thread!
Click to expand...
Click to collapse
You could download the common twrp which works for every samsung galaxy tab 2 model. The newest version is 3.0.2-8 which is found on andi34.github.io under recoveries. This could be useful if you want to flash newer roms.
Sent from my espresso3g using XDA Labs

Miui-v10.3.3.0.pdgmixm global stable

New official rom

Hi,
Not sure it's the right place to post, tell me if not.
I received the notification for update yesterday and would like to install it. But I'm bootloader unlocked, rooted and with TWRP installed.
I've tried to install it "the normal way" anyway, but after downloading the update via OTA and rebooting, the phone reboots in TWRP and does not install the update through it...
Is there a way to install the update without loosing TWRP, root and data ?

S377 said:
Hi,
Not sure it's the right place to post, tell me if not.
I received the notification for update yesterday and would like to install it. But I'm bootloader unlocked, rooted and with TWRP installed.
I've tried to install it "the normal way" anyway, but after downloading the update via OTA and rebooting, the phone reboots in TWRP and does not install the update through it...
Is there a way to install the update without loosing TWRP, root and data ?
Click to expand...
Click to collapse
Not update OTA with twrp recovery
You're need:
Download full zip rom
Flash it by twrp recovery without wipe.

heobanhki said:
Not update OTA with twrp recovery
You're need:
Download full zip rom
Flash it by twrp recovery without wipe.
Click to expand...
Click to collapse
Ok, so I could just do the following steps ?
- Download the ROM by the MIUI updater (which stores the full zip in "downloaded_rom" folder")
- Reboot to TWRP
- Wipe Dalvik/ART and Cache
- Flash the downloaded zip
- Optionally : Flash Magisk to retrieve root
- Reboot
Since my post, I've found this thread for Mi Mix 2 (not 2s) which talk about a LazyFlasher zip...
Isn't it needed ?

subboxcb said:
New official rom
Click to expand...
Click to collapse
Missprint in that update note? My Global 10.3.3.0 PDGMIXM got the security patch from May 1 :S
Update: Nvm, said May patch a line down...
Sent from my MIX 2S using XDA Labs

S377 said:
Ok, so I could just do the following steps ?
- Download the ROM by the MIUI updater (which stores the full zip in "downloaded_rom" folder")
- Reboot to TWRP
- Wipe Dalvik/ART and Cache
- Flash the downloaded zip
- Optionally : Flash Magisk to retrieve root
- Reboot
Since my post, I've found this thread for Mi Mix 2 (not 2s) which talk about a LazyFlasher zip...
Isn't it needed ?
Click to expand...
Click to collapse
Someone can tell me please ?

S377 said:
Someone can tell me please ?
Click to expand...
Click to collapse
Don't upgrade!! There's no twrp for the new rom
I'll wait some days to see if a working twrp appears else I'm flashing 10.2.2 again (which is a PITA since it needs "flash_all" = reinstall everything)

xumixu said:
Don't upgrade!! There's no twrp for the new rom
I'll wait some days to see if a working twrp appears else I'm flashing 10.2.2 again (which is a PITA since it needs "flash_all" = reinstall everything)
Click to expand...
Click to collapse
Hi !
Please define "no twrp for the new rom"
I'm running V10.3.3.0 with official twrp (3.3.0) and can boot into twrp and install things from there.
(didn't test things like backup/restore though)
kr

flushbeer said:
Hi !
Please define "no twrp for the new rom"
I'm running V10.3.3.0 with official twrp (3.3.0) and can boot into twrp and install things from there.
(didn't test things like backup/restore though)
kr
Click to expand...
Click to collapse
Did you do any workaround for installation? I installed it as usual and it gets deleted at reboot (after flashing from 10.2.2 to 10.3.3).

xumixu said:
Did you do any workaround for installation? I installed it as usual and it gets deleted at reboot (after flashing from 10.2.2 to 10.3.3).
Click to expand...
Click to collapse
copy ROM to any other folder (e.g. from /sdcard/downloaded_rom to /sdcard), then ROM will not get deleted.
(or even better OTG if you have)

flushbeer said:
copy ROM to any other folder (e.g. from /sdcard/downloaded_rom to /sdcard), then ROM will not get deleted.
(or even better OTG if you have)
Click to expand...
Click to collapse
i mean twrp get deleted from the recovery partition on reboot
and i didnt used the "update" zip, but the full rom from miui download site

xumixu said:
i mean twrp get deleted from the recovery partition on reboot
and i didnt used the "update" zip, but the full rom from miui download site
Click to expand...
Click to collapse
oh, I misunderstood.
this behaviour I had with EVERY update. Just installed twrp again and everything working again.

Same here, but in this last update it gets reverted when I reboot, Whether I let it restart right after flashing twrp or if get into it after flashing. Is also noteworthy that it doesn't prompt me the "partition modification" message.
Is there any "settings" or cache for twrp that can be cleaned to have a "fresh" install? It remembers the time zone so I think it should save some things somewhere

Hm. weird. what I did was fastboot into TWRP and from there install as image from internal storage (or OTG).
(Might be, that I tried another version (v14? v15? from this forum) because I tested a few things because of my phone freezing problems. But I guess this should not make any difference.)
So no black magic here.
The only thing i know: I have it running.

Ok, thanks to both of you for your response.
I'll try to install it and will let you know for TWRP !
@xumixu : have you tried to "reboot to recovery" from TWRP once you've installed it and boot to it from adb ?

S377 said:
Ok, thanks to both of you for your response.
I'll try to install it and will let you know for TWRP !
@xumixu : have you tried to "reboot to recovery" from TWRP once you've installed it and boot to it from adb ?
Click to expand...
Click to collapse
No issues reboting into recovery after twrp installation. But once i get into system, recovery partition is factory restored to mi-recovery 3.0

All went good for me !
I've done the following steps :
- Download the full ROM (~1.9 GB) on the official MIUI website
- Reboot to TWRP
- Wipe Dalvik/ART and Cache
- Flash the downloaded zip
- Wipe Dalvik/ART and Cache
- Flash Magisk to retrieve root
- Wipe Dalvik/ART and Cache
- Reboot TO RECOVERY !
- Reboot to system
I've done this going from MIUI v10.2.2.0 to v10.3.3.0 and using the official TWRP 3.2.3.0

S377 said:
All went good for me !
I've done the following steps :
- Download the full ROM (~1.9 GB) on the official MIUI website
- Reboot to TWRP
- Wipe Dalvik/ART and Cache
- Flash the downloaded zip
- Wipe Dalvik/ART and Cache
- Flash Magisk to retrieve root
- Wipe Dalvik/ART and Cache
- Reboot TO RECOVERY !
- Reboot to system
I've done this going from MIUI v10.2.2.0 to v10.3.3.0 and using the official TWRP 3.2.3.0
Click to expand...
Click to collapse
tried all those steps and I still end up bootlooped (with magisk 19 and 19.3).
ill back up important data, and make a clean 10.3.3 installation. If it doesnt work with 10.3.3, I'll rollback to 10.2.2

Seems that my rom "setup" was the culprit. Made a clean 10.3.3 install (fastboot mode flash_all.bat), reinstalled twrp, magisk and it booted ok (and twrp stayed togheter with encryption support).
No idea what happened in the update from my 10.2.2 to 10.3.3, but twrp works ok on 10.3.3 with a clean installation

Ok, weird... But good to know that all is ok now