I'm having difficulty getting TWRP 3.3 working on my z3c. I'm not new to the process, and have done it a few times on a few phones. Right now my z3c has TWRP 3.0.2-1-z3c. I'm wanting to try the new Android 10 ROM that came out, but it requires TWRP 3.3 to work. So I got the TWRP provided in the thread. I'm flashing from Linux, so I did run
Code:
./fastboot flash recovery twrp 3.3.1-1-A10.0-z3c.img
When I reboot and hold the power down button it skips over TWRP and just boots the ROM I have installed.
Okay, so I downgrade to TWRP 3.0.2-1 and reboot...hold volume down...TWRP boots just fine.
Flash TWRP 3.3 again....no joy. It just boots straight to ROM.
RNZL3R said:
I'm having difficulty getting TWRP 3.3 working on my z3c. I'm not new to the process, and have done it a few times on a few phones. Right now my z3c has TWRP 3.0.2-1-z3c. I'm wanting to try the new Android 10 ROM that came out, but it requires TWRP 3.3 to work. So I got the TWRP provided in the thread. I'm flashing from Linux, so I did run
Code:
./fastboot flash recovery twrp 3.3.1-1-A10.0-z3c.img
When I reboot and hold the power down button it skips over TWRP and just boots the ROM I have installed.
Okay, so I downgrade to TWRP 3.0.2-1 and reboot...hold volume down...TWRP boots just fine.
Flash TWRP 3.3 again....no joy. It just boots straight to ROM.
Click to expand...
Click to collapse
Same. Couldnt find a proper answer to this. Still have trouble with this? I'm on CR6.1, that's android 8.1 and I'd like to try later versions (lineage os or maybe CR7.0)
liberteus said:
Same. Couldnt find a proper answer to this. Still have trouble with this? I'm on CR6.1, that's android 8.1 and I'd like to try later versions (lineage os or maybe CR7.0)
Click to expand...
Click to collapse
Screwed badly with the systems to the point where I softbricked the phone, and had to revert to stock. Will try going straight to 3.3.1 instead now.
Edit: I used adb to go to fastboot (adb reboot bootloader), from there I tried all the different twrp images I have, including latest Android 10 one using the fastboot boot image.img (replace image by name of image, I name them A8, A9, A10 to match android version).
All of them booted, which means I can flash them without issues. I don't know which version I want to install though for now, and I don't want to be stuck again on a version that I won't be able to upgrade later on... so will probably go straight to A10 and Lineage 17 even if it's quite buggy.
liberteus said:
Same. Couldnt find a proper answer to this. Still have trouble with this? I'm on CR6.1, that's android 8.1 and I'd like to try later versions (lineage os or maybe CR7.0)
Click to expand...
Click to collapse
did you found a solution? i have the same issue...
Okay. Am currently on MIUI 11.0.3 (the latest one available for RaphaelIN)
So, the problem am facing is that, when i flash a custom rom, my phone gets rebooted to recovery and sometimes to fastboot(this happens occasionally) and i just simply cant get the rom to load.
Sometimes my phone gets into a state which resembles hardbrick (none of the buttons work, even holding the power button for 10secs doesn't) and after sometimes, usually 15 to 20 mins it restarts itself. This has happened thrice till date and all while booting to system.
The Roms i have tried-
-Pixel experience (unofficial) (android Q)
- Lineage OS 17 (unofficial)
- Havoc OS (both official and unofficial) (both pie and Q versions)
-MIUI (European rom)
I have also tried flashing the chinese, indian and global vendor (all done separately) thinking it was a vendor issue, but it also doesn't work.
Recovery is TWRP latest version, have also used orange fox recovery
Bootloader unlocking was done through the official method and the official app.
Any solutions for this problem and has anyone faced these problems or is it only me?
Astrek said:
Okay. Am currently on MIUI 11.0.3 (the latest one available for RaphaelIN)
So, the problem am facing is that, when i flash a custom rom, my phone gets rebooted to recovery and sometimes to fastboot(this happens occasionally) and i just simply cant get the rom to load.
Sometimes my phone gets into a state which resembles hardbrick (none of the buttons work, even holding the power button for 10secs doesn't) and after sometimes, usually 15 to 20 mins it restarts itself. This has happened thrice till date and all while booting to system.
The Roms i have tried-
-Pixel experience (unofficial) (android Q)
- Lineage OS 17 (unofficial)
- Havoc OS (both official and unofficial) (both pie and Q versions)
-MIUI (European rom)
I have also tried flashing the chinese, indian and global vendor (all done separately) thinking it was a vendor issue, but it also doesn't work.
Recovery is TWRP latest version, have also used orange fox recovery
Bootloader unlocking was done through the official method and the official app.
Any solutions for this problem and has anyone faced these problems or is it only me?
Click to expand...
Click to collapse
Consider this an overkill solution that always works for me if I run into issues with other methods. It will wipe everything so backup your data and apps.
Download the latest fastboot Indian MIUI ROM (for anyone else reading this download the ROM that is the same region as your phone)
Fully extract the ROM and flash it - make sure, if you use the Mi Flash Tool, that you change the flash option to 'clean all'
Boot into MIUI once, you don't need to actually go through the set-up, just let it fully load.
Boot the phone into fastboot and install TWRP - I recommend the latest mauronofrio TWRP.
After installing TWRP boot immediately into TWRP.
Format the data partition - don't skip this step.
Wipe cache and dakvik - don't wipe anything else.
In TWRP goto the mount menu and unmount the data partition then mount it again - others would suggested rebooting back into TWRP, either way works, you just need to make sure the data partition is properly mounted after formatting it.
Install the ROM of your choice - either have the ROM on a USB OTG stick, or copy it onto the phone from a PC whilst still in TWRP.
If your ROM doesn't include Google apps and services and you want Google, then install GApps - at the time of writing this Android 10 GApps is still in beta and packages bigger than nano may cause issues, so stick with pico or nano, assuming your installing an Android 10 ROM.
Boot into the ROM.
If you want Magisk, once the ROM has loaded, boot back into TWRP and flash the latest Magisk installer - it is possible to flash Magisk without booting into the ROM first and you'll probably be OK, but occasionally it can cause problems, I can't remember the details, but for the sake of 30 seconds I now boot into the ROM before flashing, just to be on the safe side.
At the time of writing this people have recently reported issues flashing GApps immediately after flashing Havoc 3.0 and recommend booting Havoc before flashing GApps. Although others say they've not had any problems. So if you choose to install Havoc you 'might' have problems if you install GApps without booting into Havoc at least once first.
I've never had problems when following this method.
You didn't format data that's why your rom doesn't boot. Follow Robbos nice guide and you are good to go.:good:
Robbo.5000 said:
Consider this an overkill solution that always works for me if I run into issues with other methods. It will wipe everything so backup your data and apps.
Download the latest fastboot Indian MIUI ROM (for anyone else reading this download the ROM that is the same region as your phone)
Fully extract the ROM and flash it - make sure, if you use the Mi Flash Tool, that you change the flash option to 'clean all'
Boot into MIUI once, you don't need to actually go through the set-up, just let it fully load.
Boot the phone into fastboot and install TWRP - I recommend the latest mauronofrio TWRP.
After installing TWRP boot immediately into TWRP.
Format the data partition - don't skip this step.
Wipe cache and dakvik - don't wipe anything else.
In TWRP goto the mount menu and unmount the data partition then mount it again - others would suggested rebooting back into TWRP, either way works, you just need to make sure the data partition is properly mounted after formatting it.
Install the ROM of your choice - either have the ROM on a USB OTG stick, or copy it onto the phone from a PC whilst still in TWRP.
If your ROM doesn't include Google apps and services and you want Google, then install GApps - at the time of writing this Android 10 GApps is still in beta and packages bigger than nano may cause issues, so stick with pico or nano, assuming your installing an Android 10 ROM.
Boot into the ROM.
If you want Magisk, once the ROM has loaded, boot back into TWRP and flash the latest Magisk installer - it is possible to flash Magisk without booting into the ROM first and you'll probably be OK, but occasionally it can cause problems, I can't remember the details, but for the sake of 30 seconds I now boot into the ROM before flashing, just to be on the safe side.
At the time of writing this people have recently reported issues flashing GApps immediately after flashing Havoc 3.0 and recommend booting Havoc before flashing GApps. Although others say they've not had any problems. So if you choose to install Havoc you 'might' have problems if you install GApps without booting into Havoc at least once first.
I've never had problems when following this method.
Click to expand...
Click to collapse
Thnx for the guide. i will do this within a day or two and update you if it worked or not.
Kollachi said:
You didn't format data that's why your rom doesn't boot. Follow Robbos nice guide and you are good to go.:good:
Click to expand...
Click to collapse
I did format the data partition coz that's one thing I and my friends always do when flashing new rom. I don't exactly remember but i think, the pseudo hardbrick thingy started after i formatted the system, data, cache & internal storage.
I will follow Robbos guide adn keep you guys updated on what happened.
Astrek said:
I did format the data partition coz that's one thing I and my friends always do when flashing new rom. I don't exactly remember but i think, the pseudo hardbrick thingy started after i formatted the system, data, cache & internal storage.
I will follow Robbos guide adn keep you guys updated on what happened.
Click to expand...
Click to collapse
Format data = (you will need to type in "yes")
Note: Format data or wipe data isn't the same thing.
Robbo.5000 said:
Consider this an overkill solution that always works for me if I run into issues with other methods. It will wipe everything so backup your data and apps.
Download the latest fastboot Indian MIUI ROM (for anyone else reading this download the ROM that is the same region as your phone)
Fully extract the ROM and flash it - make sure, if you use the Mi Flash Tool, that you change the flash option to 'clean all'
Boot into MIUI once, you don't need to actually go through the set-up, just let it fully load.
Boot the phone into fastboot and install TWRP - I recommend the latest mauronofrio TWRP.
After installing TWRP boot immediately into TWRP.
Format the data partition - don't skip this step.
Wipe cache and dakvik - don't wipe anything else.
In TWRP goto the mount menu and unmount the data partition then mount it again - others would suggested rebooting back into TWRP, either way works, you just need to make sure the data partition is properly mounted after formatting it.
Install the ROM of your choice - either have the ROM on a USB OTG stick, or copy it onto the phone from a PC whilst still in TWRP.
If your ROM doesn't include Google apps and services and you want Google, then install GApps - at the time of writing this Android 10 GApps is still in beta and packages bigger than nano may cause issues, so stick with pico or nano, assuming your installing an Android 10 ROM.
Boot into the ROM.
If you want Magisk, once the ROM has loaded, boot back into TWRP and flash the latest Magisk installer - it is possible to flash Magisk without booting into the ROM first and you'll probably be OK, but occasionally it can cause problems, I can't remember the details, but for the sake of 30 seconds I now boot into the ROM before flashing, just to be on the safe side.
At the time of writing this people have recently reported issues flashing GApps immediately after flashing Havoc 3.0 and recommend booting Havoc before flashing GApps. Although others say they've not had any problems. So if you choose to install Havoc you 'might' have problems if you install GApps without booting into Havoc at least once first.
I've never had problems when following this method.
Click to expand...
Click to collapse
Ohhh *****...!!!! It ****ing worked!!!! Though i made some mistakes like clean all and lock in first step, but was able to unlock bootloader almost instantly, no idea why but i can almost instantly unlock certain mi phone's bootloader instantly. But a lot of thanx for taking your time and writing this up... You really saved me from being stuck in MIUI forever!
A lot of thnx.... and also happy new year... 1st day of 2020 went quite well for me all thnx to you and i hope yours goes well too.!
Robbo.5000 said:
Consider this an overkill solution that always works for me if I run into issues with other methods. It will wipe everything so backup your data and apps.
Download the latest fastboot Indian MIUI ROM (for anyone else reading this download the ROM that is the same region as your phone)
Fully extract the ROM and flash it - make sure, if you use the Mi Flash Tool, that you change the flash option to 'clean all'
Boot into MIUI once, you don't need to actually go through the set-up, just let it fully load.
Boot the phone into fastboot and install TWRP - I recommend the latest mauronofrio TWRP.
After installing TWRP boot immediately into TWRP.
Format the data partition - don't skip this step.
Wipe cache and dakvik - don't wipe anything else.
In TWRP goto the mount menu and unmount the data partition then mount it again - others would suggested rebooting back into TWRP, either way works, you just need to make sure the data partition is properly mounted after formatting it.
Install the ROM of your choice - either have the ROM on a USB OTG stick, or copy it onto the phone from a PC whilst still in TWRP.
If your ROM doesn't include Google apps and services and you want Google, then install GApps - at the time of writing this Android 10 GApps is still in beta and packages bigger than nano may cause issues, so stick with pico or nano, assuming your installing an Android 10 ROM.
Boot into the ROM.
If you want Magisk, once the ROM has loaded, boot back into TWRP and flash the latest Magisk installer - it is possible to flash Magisk without booting into the ROM first and you'll probably be OK, but occasionally it can cause problems, I can't remember the details, but for the sake of 30 seconds I now boot into the ROM before flashing, just to be on the safe side.
At the time of writing this people have recently reported issues flashing GApps immediately after flashing Havoc 3.0 and recommend booting Havoc before flashing GApps. Although others say they've not had any problems. So if you choose to install Havoc you 'might' have problems if you install GApps without booting into Havoc at least once first.
I've never had problems when following this method.
Click to expand...
Click to collapse
thanks for help
but no work for me
after flash rom and reboot booting to twrp auto..
Kollachi said:
Format data = (you will need to type in "yes")
Note: Format data or wipe data isn't the same thing.
Click to expand...
Click to collapse
many times the tiniest msg has the greatest significance. thanks mate!!!
Guys i need your help,, i flashed my phones custom Rom tecno 7cs using sp flashing tool.
That worked and it showed the tick icon on my pc.
The problem is that it does nothing to my phone because the software issues are still there
my phone keeps restarting itself almost all the time and sometimes won't even boot it takes longer to boot,,, apps keep on crushing and many more.AM tired am going to break it and throw it if i don't get solutions asap!
So the flashing process only wiped data on the phone nothing else whatsoever.
tecno 7cs p121 Bi safaricom ke 20151111
Hello there,
I'm using the Xiaomi.eu latest Beta rom ATM. I'm trying to flash other roms (like lineage OS 17.1 for example) but it seems to reboot to fastboot everytime. I've tried doing a clean flash, formatting data, dirty flashing. Nothing seems to help it boot into the new rom.
Clearly I'm doing something wrong. If I try flashing the recommended Chinese vendor firmware (stable version), I get an error 7..but my TWRP is up to date as recommended.
If anyone has any idea where I'm going wrong, that would help a lot.
Thanks
therightperson_630 said:
Hello there,
I'm using the Xiaomi.eu latest Beta rom ATM. I'm trying to flash other roms (like lineage OS 17.1 for example) but it seems to reboot to fastboot everytime. I've tried doing a clean flash, formatting data, dirty flashing. Nothing seems to help it boot into the new rom.
Clearly I'm doing something wrong. If I try flashing the recommended Chinese vendor firmware (stable version), I get an error 7..but my TWRP is up to date as recommended.
If anyone has any idea where I'm going wrong, that would help a lot.
Thanks
Click to expand...
Click to collapse
Don't know what your doing wrong, but this is my failsafe method should nothing else work.
Flash the latest Chinese 11.0.5 fastboot ROM. Make sure you don't lock the bootloader if using the Mi Flash Tool.
Boot into MIUI once to allow it to finalise the install, you don't need to do the initial phone setup once it boots into MIUI.
Boot into fastboot and install TWRP. I recommend the latest from mauronofrio which should be 3.1.1-32
Boot immediately into TWRP. I use the volume up button while powering up the phone.
Perform a factory reset in TWRP (using the swipe button), then format data (need to type 'yes' to confirm).
Reboot into TWRP using the TWRP boot menu, this ensures the newly formatted data partition is correctly mounted.
Copy over the ROM you want and GApps if needed, then flash.
Boot into your new ROM, everything should be OK. Then boot back into TWRP to install Magisk if you want root.
Yep that seems to have done the trick. At first I was getting frustrated because I thought I was downloading the right Chinese ROM, turns out I was downloading the recovery version instead of the fastboot one.
I think it wasn't working because I was on the beta channel. Switching over to the stable channel meant I had to go through a fastboot flash apparently. I've seen this before on my OP3.
Got lineage OS loaded, thanks for your help!
So i already did some searching, but nothing yet, maybe i' m overlooking something
Soi did a full recovery with mi flash tool, no dice, then took the persist out of it and flashed it with twrp, no dice, so now i reverted back to Lineage since i can't stand MIUI, but yeah, now i still don't have sensors running
The fastboot image i used is 11.8, which is the euro image as far as i know (got my device here in europe), is there something i'm completely overlooking?
Had this issue with my Pixel Experience rom - do sensors work in Miui? If so, perhaps your method of flashing is dodgy/ the rom has issues.
Flash the permissive zip. It happens sometimes when it's set to enforcing. People were talking about it on Syberia 3.6 post, check it out, there's a link to download there.
I had this same issue as well. I solved it by reflashing back to stock with MiFlash tool and using V11.0.5.0 Stock MIUI ROM.
After that boot the phone and go through the initial phone setup process.
Then you can flash TWRP Recovery (twrp-3.3.1-0-cepheus.img).
In TWRP flash vbmeta.img. After that you can flash and boot your Custom ROM with sensors working.
Do not flash any other firmware file in TWRP. I have seen other ROM threads mentioning the need to flash a fw file but don't do that.
Here are somethings I struggled with unlocking the bootloader, installing a custom ROM and the apps.
If you are trying to unlock your bootloader with the Mi Unlock Tool and it seems to randomly fail, make sure you are not using a Ryzen processor. It fails everytime. Use an intel based machine if you can.
Ryzen processors also make it impossible to use fastboot correctly. I could not install or boot into TWRP. Once again, use an intel based machine.
One thing I could not get working after unlocking my phone is flash TWRP to the recovery. It never worked. It said it worked in the Fastboot CLI but it didn't. I could boot to the TWRP image and do everything I needed to from there. Anyone know why this is?
I also could not install Opengapps after installing the OS. They just would not show up at all.
I made sure to install Magisk after OpenGapps and everything seemed to work fine but the launcher kept crashing. I found that it must have the items installed in this order:
OS, Magisk, OpenGapps
Now everything is working and stable. I'm not sure as to why this works (or doesn't in my attempts) but it does. I have read a lot of scattered forums on this issue and the best I can come up with is the correct partitions are not mounted/unmounted when OpenGapps is installed but doing Magisk first mounts and unmounts the correct partitions.
Does anyone know the actual answer to this?
TL;DR
Don't use Mi Unlock or ADB/Fastboot on Ryzen, use intel.
Install OS, Magisk, OpenGapps on TWRP, in that order.