Related
So I downgraded my Oneplus 3 from 3.5.2 to 3.2.6 and this was kind of a painful process, so I decided to share my experience with you.
If you follow this guide you will successfully downgrade from the latest Community Build to the newly released stable.
Note: Just because this worked for me, doesn't mean that it will work for you! Use this guide on your own risk and always use backups!
You'll need:
- Oneplus with OOS 3.5.2 and modified TWRP
- OxygenOS 3.2.6 Full ROM
- Latest official TWRP
- AndroidSDKSlim (needs Oneplus 3 USB drivers installed)
- SuperSU 2.78 SR1
- Xposed Framework (optional)
- Debloat Script (optional)
Downgrade:
Before you start, please create a COMPLETE backup of all your data.
You will factory reset your phone during the process.
1. Copy OOS 3.2.6 Full ROM, SuperSU, Xposed, Debloat Script to your Oneplus
2. Flash modified TWRP if you haven't already
3. Boot into modified TWRP
4. Select Wipe -> Advanced Wipe -> Select all but internal storage -> Swipe to Wipe
5. Install OOS 3.2.6 Full ROM
6. Reboot into system and use the installation wizard to setup your phone (do not setup fingerprints, or any device PIN)
7. Reboot into bootloader
8. Connect your phone to a PC/Notebook
9. Extract AndroidSDKSlim to your Desktop and copy twrp-3.0.2-1-oneplus3.img into \AndroidSDKSlim\android-sdk-windows\platform-tools
10. Run CMD with admin rights and navigate to \AndroidSDKSlim\android-sdk-windows\platform-tools
11. Run "fastboot flash recovery twrp-3.0.2-1-oneplus3.img" to revert to official TWRP recovery
12. Disconnect your phone and boot into recovery
13. Dirty flash OOS 3.2.6 again (this might sound stupid but it's mandatory)
14. Still in recovery, flash SuperSU, Xposed and Debloat Script
15. Wipe Dalvik & Cache
16. Reboot into system and setup your phone
Thanks for your guide !
Can you just please detail how to revert back to a custom ROM like RR or Nuclear when we come from Oxygen OS 3.5.2 community build ?
darkbash said:
Thanks for your guide !
Can you just please detail how to revert back to a custom ROM like RR or Nuclear when we come from Oxygen OS 3.5.2 community build ?
Click to expand...
Click to collapse
You're welcome.
Unfortunately, I can't provide guides for procedures I never went through.
But I asume that you could just flash any Custom ROM after you completely wiped your phone in step 4. So instead of flashing OOS 3.2.6 afterwards, just flash a custom ROM. Be sure that you have all zips you need on your internal storage and a backup to revert back to, if anything goes wrong. Otherwise you will have to use ADB sideload to install a ROM.
Ok, so I have a Modified TWRP installed already. Question is If I want to flash other ROMS after wiping system,dalvik/cache,data etc. Do I have to Flash official TWRP first followed by firmware,ROM, etc?
or firmware first then ROM and lastly official TWRP?
it's quite confusing.
I made a mistake and I installed the modified recovery installed the 3.5.2 rom and before booting I decided to restore my nand backup so I flashed the official twrp recovery and now I can't go to recovery anymore and the phone doesn't boot.
I imagine I have to sideload the modified twrp again but how do I do that? How do I reboot to bootloader ?
This is the only sign of life
gigeaky said:
I made a mistake and I installed the modified recovery installed the 3.5.2 rom and before booting I decided to restore my nand backup so I flashed the official twrp recovery and now I can't go to recovery anymore and the phone doesn't boot.
I imagine I have to sideload the modified twrp again but how do I do that? How do I reboot to bootloader ?
This is the only sign of life
Click to expand...
Click to collapse
Flash modified TWRP, and the recovery will return. then, follow the guide. it happened to me too.
darkbash said:
Thanks for your guide !
Can you just please detail how to revert back to a custom ROM like RR or Nuclear when we come from Oxygen OS 3.5.2 community build ?
Click to expand...
Click to collapse
First flash modified TWRP than install official 3.2.4 than flash CM ROM or custom ROM
uniQ191 said:
So I downgraded my Oneplus 3 from 3.5.2 to 3.2.6 and this was kind of a painful process, so I decided to share my experience with you.
If you follow this guide you will successfully downgrade from the latest Community Build to the newly released stable.
Note: Just because this worked for me, doesn't mean that it will work for you! Use this guide on your own risk and always use backups!
You'll need:
- Oneplus with OOS 3.5.2 and modified TWRP
- OxygenOS 3.2.6 Full ROM
- Latest official TWRP
- AndroidSDKSlim (needs Oneplus 3 USB drivers installed)
- SuperSU 2.78 SR1
- Xposed Framework (optional)
- Debloat Script (optional)
Downgrade:
Before you start, please create a COMPLETE backup of all your data.
You will factory reset your phone during the process.
1. Copy OOS 3.2.6 Full ROM, SuperSU, Xposed, Debloat Script to your Oneplus
2. Flash modified TWRP if you haven't already
3. Boot into modified TWRP
4. Select Wipe -> Advanced Wipe -> Select all but internal storage -> Swipe to Wipe
5. Install OOS 3.2.6 Full ROM
6. Reboot into system and use the installation wizard to setup your phone (do not setup fingerprints, or any device PIN)
7. Reboot into bootloader
8. Connect your phone to a PC/Notebook
9. Extract AndroidSDKSlim to your Desktop and copy twrp-3.0.2-1-oneplus3.img into \AndroidSDKSlim\android-sdk-windows\platform-tools
10. Run CMD with admin rights and navigate to \AndroidSDKSlim\android-sdk-windows\platform-tools
11. Run "fastboot flash recovery twrp-3.0.2-1-oneplus3.img" to revert to official TWRP recovery
12. Disconnect your phone and boot into recovery
13. Dirty flash OOS 3.2.6 again (this might sound stupid but it's mandatory)
14. Still in recovery, flash SuperSU, Xposed and Debloat Script
15. Wipe Dalvik & Cache
16. Reboot into system and setup your phone
Click to expand...
Click to collapse
worked like magic. Thankyou for this education. it didnt work when i followed other folks. Much appreciated.
So it seems I have booted with 3.5.2 and modified recovery. Now my question is: can I reboot in recovery at step 7 and install the original twrp recovery? Or can I use flashify? As I don't have access to a pc
I did ok but cant use adaway do you have a fix for it?
Enviado do meu ONEPLUS A3003 através de Tapatalk
I'm trying to return to 3.2.6 after trying 3.5.2.
However, after flashing and booting 3.2.6, I boot into fastboot mode and the official TWRP refuses to flash. It reports that it's failed and then I'm left with no recovery until I reflash the modified TWRP.
I could try restoring my Nandroid backup of 3.2.6 with the modified TWRP, but I'd prefer to return to the official TWRP before doing this.
Any suggestions?
Edit: Fixed it. I downloaded the official TWRP again and it flashed. The first download must have been corrupted.
I followed a different method and successfully downgraded today to a former nandroid. I was rooted without xposed.
3.2.6 to 3.5.2 dirty flash
- installed modded twrp
- performed backup on 3.2.6
- installed modded 3.5.2 (the only that flashes in twrp)
- installed root SR1
- wiped caches only
- reboot
3.5.2 to 3.2.6 restore
- downloaded 3.2.6
- boot to modded twrp, wipe both caches, data, system
- flashed 3.2.6 stock and root SR1
- restored 3.2.6
- wiped caches
- reboot
- enjoying my LTE again
Without first installing stock, after a restore my phone was boot locking right after the oneplus white logo (capacitive buttons would light up, but it would not boot to red logo). Had to press vol down and power to force it to boot menu to select recovery and get back to twrp
Hope this helps someone, it's a bit easier than swapping twrps and no need to boot up/flash 3.2.x twice.
So if I am on the CB and want to go back to 3.2.6
I can flash 3.2.6 with the modded TWRP
Then flash Official TWRP and boot?
If I have official recovery, no root, and locked bootloader, can I downgrade from 3.5.3 to 3.2.6 without any problems, just by sideloading the zip in ADB? Thankss
popab said:
If I have official recovery, no root, and locked bootloader, can I downgrade from 3.5.3 to 3.2.6 without any problems, just by sideloading the zip in ADB? Thankss
Click to expand...
Click to collapse
i would also like to know this please
bigup7 said:
i would also like to know this please
Click to expand...
Click to collapse
I did it and it does work perfectly. Just make sure to wipe data from recovery after flashing.
I was on Comunity Build v.3.5.4. I want it back FreeDom v.1.6.
I did:
1. Flash Twrp-3.0.2-19-oneplus3.img.zip. Somebody sugested original twrp 3.0.2.1 from twrp site. For me did NOT work. Phone not booting in recovery with 3021.
2. Advanced wipe. Wipe dalvik cache/cache/system/data
3. Flash Freedom v.1.6. Clean Flash it's safer & better.
Done. System works. Recovery works.
null0seven said:
I was on Comunity Build v.3.5.4. I want it back FreeDom v.1.6.
I did:
1. Flash Twrp-3.0.2-19-oneplus3.img.zip. Somebody sugested original twrp 3.0.2.1 from twrp site. For me did NOT work. Phone not booting in recovery with 3021.
2. Advanced wipe. Wipe dalvik cache/cache/system/data
3. Flash Freedom v.1.6. Clean Flash it's safer & better.
Done. System works. Recovery works.
Click to expand...
Click to collapse
I am on CB Freddom os
I want to go back either to stock or to op3lite.
I cant reboot to recovery.
But adb works yet.
What to do plz suggest.
Sent from my ONEPLUS A3003 using Tapatalk
1. If system don't boot. Reboot to fastboot.
- Flash recovery.img. If PC don't see youre phone option 2.
2. If system boots, open phone like normal.
- Extract recovery img. Put it on the TWRP file on phone sd card.
- Download Flashify from play. Open it, flash img of recovery. Open recovery to chech if it works.
Try with both recovery (3.0.2.0 or modified 3.0.2.-19). One of those will work.
Im getting system partition has unexpected contents after OTA update after installing step 5 ????
Backup your stock recovery per this post. If you are too lazy, I can upload my backup from .104 build (C432) to Mega.
Download twrp_bkl_0.7.img from this post and place it in same directory with your ADB.
After successful backup as precaution disable any locks like pattern/PIN/password/fingerprint, reboot to bootloader (fastboot):
Code:
adb reboot bootloader
Then flash new TWRP recovery:
Code:
fastboot flash recovery_ramdisk twrp_bkl_0.7.img
After successful flash reboot device and immediately after confirming command below unplug USB cable and HOLD and keep holding VOLUME UP button, if you won't the new recovery will be overwritten by stock and you can try again.
Code:
fastboot reboot
Tested by myself on Honor 10 8.1.0.104 (C432) with unlocked bootloader and installed already Magisk 16.4 with Magisk manager 5.7.0, Magisk ramdisk persisted after installing TWRP recovery, system boots normal.
Next step after unlocking BL, installing Magisk, installing TWRP recovery -> flashing GSI AOSP, LOS or RR. Only reason I bothered with installing TWRP was that GSI image of LOS and RR don't include opengapps, only AOSP does, so without TWRP you can't have opengapps with these two GSI ROMS.
PeterMarkoff said:
Backup your stock recovery per this post. If you are too lazy, I can upload my backup from .104 build (C432) to Mega.
Download twrp_bkl_0.7.img from this post and place it in same directory with your ADB.
After successful backup as precaution disable any locks like pattern/PIN/password/fingerprint, reboot to bootloader (fastboot):
Code:
adb reboot bootloader
Then flash new TWRP recovery:
Code:
fastboot flash recovery_ramdisk twrp_bkl_0.7.img
After successful flash reboot device and immediately after confirming command below unplug USB cable and HOLD and keep holding VOLUME UP button, if you won't the new recovery will be overwritten by stock and you can try again.
Code:
fastboot reboot
Tested by myself on Honor 10 8.1.0.104 (C432) with unlocked bootloader and installed already Magisk 16.4 with Magisk manager 5.7.0, Magisk ramdisk persisted after installing TWRP recovery, system boots normal.
Next step after unlocking BL, installing Magisk, installing TWRP recovery -> flashing GSI AOSP, LOS or RR. Only reason I bothered with installing TWRP was that GSI image of LOS and RR don't include opengapps, only AOSP does, so without TWRP you can't have opengapps with these two GSI ROMS.
Click to expand...
Click to collapse
Nice work. ?
tried to install GSI RR OS, but ending in bootloop, also even after resizing system partition to maximum (TWRP / wipe / resize) opengapps still showing error 70 about insufficient space (which makes no sense, so they really seem to have wrong detection of A/B instead of A for Huawei/Honor devices), though these gzr gapps seem to install successfuly, now if I could figure out the damn bootloop
potential reasons for bootloop - previously installed magisk, wiped also system not only data/cache, installed through fastboot while TWRP there and not only stock recovery, ???
edit: i guess will try flash GSI through TWRP again, quite a waste time to wait each time like 9-10 minutes to find out it can't boot
edit 2: so even flashing through TWRP doesn't help, just stuck on android animation for 10 minutes and then it restarts (and even if you do fatory reset through huawei erecovery it doesnt change anything). maybe can try to restore everything and not wipe system before installing, just factory reset through TWRP (though I remember I read somewhere it's not reliable and it is better to do it through system, but I think that one wipe also internal storage which I wanna avoid)? back to rooted EMUI with TWRP for now, don't have time to try various combinations
edit 3: flashing over TWRP backup without wiping system doesn't help, so it seem it's gonna be magisk or replaced stock recovery i guess, otherwise no idea
BTW the lack of feedback here and trying from other users it's very depressing. they boasted million phone sales and i am the only one in the whole world trying to install TWRP and GSI ROM on this phone?
PeterMarkoff said:
BTW the lack of feedback here and trying from other users it's very depressing. they boasted million phone sales and i am the only one in the whole world trying to install TWRP and GSI ROM on this phone?
Click to expand...
Click to collapse
Don't be disappointed the lack of feedback from users is not many power users have got their hands on this model.
And also we are having different builds.
From the day one I am trying to rebrand my device but no success .
Once I have rebranded to EU I will try and let you know.
Did you flash open gapps nano package through twrp in gsi image?
Did it give you the same error?
tried just pico opengapps as on all phones i flash, that's the smallest, but always end up with error 70 not enough space despite resized system partition in TWRP and many GB available, the other unofficial GZR zero gapps build i mentioned seem to be flashed successful in TWRP, but in any case no luck with booting
PeterMarkoff said:
tried just pico opengapps as on all phones i flash, that's the smallest, but always end up with error 70 not enough space despite resized system partition in TWRP and many GB available, the other unofficial GZR zero gapps build i mentioned seem to be flashed successful in TWRP, but in any case no luck with booting
Click to expand...
Click to collapse
Did you format your phone before trying GSI ?
Try formatting phone and remove some system apps and then flash gapps it will mostly solve the problem.
PeterMarkoff said:
BTW the lack of feedback here and trying from other users it's very depressing. they boasted million phone sales and i am the only one in the whole world trying to install TWRP and GSI ROM on this phone?
Click to expand...
Click to collapse
Don't be upset – e.g. I didn't receive my Honor 10 yet. You won't be the only one for sure, you're just the first one to do it, which is super nice for others because it motivates them to do so as well!
Just wondering: does it make a difference for TWRP wether I own the 6gb or 4gb version?
miststudent2011 said:
Did you format your phone before trying GSI ?
Try formatting phone and remove some system apps and then flash gapps it will mostly solve the problem.
Click to expand...
Click to collapse
I did factory reset (data, both cache) and also wiped system partition, gapps would be the least issue, as I said that GZR should work, but my system doesn't boot, no matter how times I wipe everything through TWRP or stock recovery after flashing system.img, since they say it's normal to hang at first boot and then wipe and then it should boot, but it doesn't work for me. also of course tried to power off phone since some people said it helps to do it after flashing. what I haven't done it's fastboot -w which should be some better wipe. some people say also you should remove magisk ramdisk, though I forgot to back up original, backed up just stock recovery. and also I haven't tried to flash everything with stock recovery, though first flash I did was through fastboot anyway and not through TWRP and it didn't make difference
so last few things left to try:
- fastboot -w for total wipe of data (better than TWRP? though it should be same as Format data in TWRP which wipe everything including internal storage which I wanna avoid since backing up 15GB TWRP backup file it's kinda annoying and my system has problem to do it)
- flash with stock recovery (I have backup, no big deal)
- remove magisk ramdisk and flash with stock ramdisk (forgot to make backup, can't replace)
though I am tired of it for now, spend last night like 4 hours dealing with it until 2AM and I also need to take care of children
vollkornbaguette said:
Don't be upset – e.g. I didn't receive my Honor 10 yet. You won't be the only one for sure, you're just the first one to do it, which is super nice for others because it motivates them to do so as well!
Just wondering: does it make a difference for TWRP wether I own the 6gb or 4gb version?
Click to expand...
Click to collapse
I don't think RAM has something to do with anything, but that sounds like Chinese version since EU has always 4GB and only difference is storage, so you will have different ROM
PeterMarkoff said:
(...)
so last few things left to try:
- fastboot -w for total wipe of data (better than TWRP?)
- flash with stock recovery (I have backup, no big deal)
- remove magisk ramdisk and flash with stock ramdisk (forgot to make backup, can't replace)
Click to expand...
Click to collapse
So I just read more about the GSI/Treble stuff and it said somewhere that modifications like Magisk probably lead to problems with the GSI flash.
Which is why I would try to get rid of the magisk ramdisk first.
I'm not an expert in this at all but maybe this helps.
---
PeterMarkoff said:
I don't think RAM has something to do with anything, but that sounds like Chinese version since EU has always 4GB and only difference is storage, so you will have different ROM
Click to expand...
Click to collapse
Indeed I bought the chinese 6gb RAM Version (hope this won't turn out as a big mistake)
vollkornbaguette said:
So I just read more about the GSI/Treble stuff and it said somewhere that modifications like Magisk probably lead to problems with the GSI flash.
"Your device is free of any heavy modifications such as the
Click to expand...
Click to collapse
yeah, now if someone could extract for me from 0.104 firmware for C432 that stock ramdisk, because I have some problems with mega to download it and I just need the stock ramdisk, nothing else, I have stock recovery backup but forgot to make ramdisk backup
edit: completely forgot there is option to "Completely uninstall" in Magisk manager, so tried it though even after restart with magisk manager missing i could still use root apps, so not sure how exactly this "complete uninstall" works, but anyway giving it a try after this and wiping data, installed system.img again, again wiped, rebooted and as usual loading and loading and nothing, seem can't further continue without copy of stock ramdisk to flash, tried downloading the big update from mega to extract it but it always fail for me to download, same with trying to copy my TWRP backup because for sure ain't gonna doi fastboot -w and setting up everything from scratch in case even this doesn't help, if I knew it works for sure and it will load new system which I will have to set up then no problem, but in this case...
edit 2: tried to replace magisk ramdisk with ramdisk from Honor View 10 BKL09 (same as our working TWRP) but it seem I end up after flashing it, wiping and flashing system.img in TWRP/erecovery bootloop, it's not showing android booting logo like before (but hey at least no need to wait 10 minutes to find it's fail) and either go to huawei ercovery, if I perform factory reset there then it boots to TWRP, but can't boot anywhere else besides these two
pass
I requested this image. Recovery has been established. When I enter the recovery, it requires a password to decrypt the system partition, I enter it (the same after switching on the phone), but a message is displayed that the password is incorrect. help me please.
told you in OP disable all passwords before flashing
PeterMarkoff said:
yeah, now if someone could extract for me from 0.104 firmware for C432 that stock ramdisk, because I have some problems with mega to download it and I just need the stock ramdisk, nothing else, I have stock recovery backup but forgot to make ramdisk backup
edit: completely forgot there is option to "Completely uninstall" in Magisk manager, so tried it though even after restart with magisk manager missing i could still use root apps, so not sure how exactly this "complete uninstall" works, but anyway giving it a try after this and wiping data, installed system.img again, again wiped, rebooted and as usual loading and loading and nothing, seem can't further continue without copy of stock ramdisk to flash, tried downloading the big update from mega to extract it but it always fail for me to download, same with trying to copy my TWRP backup because for sure ain't gonna doi fastboot -w and setting up everything from scratch in case even this doesn't help, if I knew it works for sure and it will load new system which I will have to set up then no problem, but in this case...
edit 2: tried to replace magisk ramdisk with ramdisk from Honor View 10 BKL09 (same as our working TWRP) but it seem I end up after flashing it, wiping and flashing system.img in TWRP/erecovery bootloop, it's not showing android booting logo like before (but hey at least no need to wait 10 minutes to find it's fail) and either go to huawei ercovery, if I perform factory reset there then it boots to TWRP, but can't boot anywhere else besides these two
Click to expand...
Click to collapse
If you want, i have all the files of the C432 update but idk in wich .zip, folder the ramdisk is stored.
I can send on several clouds.
PeterMarkoff said:
told you in OP disable all passwords before flashing
Click to expand...
Click to collapse
Hey did you restore your device are you still struck at boot screen?
If yes try this method.
https://forum.xda-developers.com/huawei-p20/development/rebrand-huawei-p20-eml-l29-eml-l09-t3779283
How to GO back to stock emui(India) after i flash a treble rom? Do i need to backup using some tool?
PLease someone tell me
srharshajava said:
PLease someone tell me
Click to expand...
Click to collapse
The problem is currently we don't have full
ROM to revert to stock and if we brick our device there is no proper way to revert to stock.
Our model even doesn't have SD card support.
Just wait for some time for someone to provide proper way.
When i flash a treble rom, I have a bootloop. I returned back with eRecovery directly on the phone.
miststudent2011 said:
The problem is currently we don't have full
ROM to revert to stock and if we brick our device there is no proper way to revert to stock.
Our model even doesn't have SD card support.
Just wait for some time for someone to provide proper way.
Click to expand...
Click to collapse
We do have a way to download full ROM.
http://pro-teammt.ru/firmware-database/?firmware_model=COL-L29C432
1. Search here for your exact model (change numbers after C432 to find ROM for your phone) and search for your rom version (B104 or B120)
2. Double click on "filelist" on the same row as FullOTA-MF
3. From filelist link menu download update.zip file (it should be really big, like 2+GB)
3. Extract UPDATE.APP file somewhere (eg. Desktop)
4. In settings of HuaweiUpdateExtractor (link: https://forum.xda-developers.com/showthread.php?t=2433454) uncheck "verify header checksum" and open UPDATE.APP
5. Extract any img (Be it ramdisk.img, ramdisk_recovery.img or system.img) file that you need from UPDATE.APP via HuaweiUpdateExtractor
You just got whoole stock rom and img files that you can flash. Tested by myself with flashing back original ramdisk, ramdisk_recovery and system.img and everything worked well.
After a long time I was finally able to unlock my Redmi Note 7.
I realized that flashing and other things on this device are a little bit more complex than on other devices I have had in the past.
Therefore I want to know what are the do's and dont's of this device and maybe make a comprehensive list so that everyone can avoid BRICKING or running into trouble while messing around with their phone.
I have seen things such as:
- never wipe system (which i'm not sure is true btw)
- dm-verity and vbmeta stuff (when to do it and what is it for? - some do it, some don't... which is confusing)
etc.
As you can tell I'm a newbie with this device.
Would be cool if you guys could give some input in order to create a comprehensive list.
Thanks!
Yeah Same thing here !!!
I've been using this phone for a month, i'm not an expert but if it can help around.
-Most custom ROM have they steps to flash and are usually the same for a clean flash (Wipe Cache, Dalvik/Art Cache, Data and System)
-If the custom ROM need it you will need to flash Vbmeta, usually the most ROM already have it inside, and a few have it as an external zip, this is only needed "once" you are coming from MIUI to a custom ROM, otherwise you don't.
-Other custom ROM will ask you to flash global firmware and that's just a 60MB zip that you will found in the ROM links usually, as I said most of the Custom ROM post have their steps.
-Dm-verity is something i haven't had to face as a problem so far so can't help abot that, but following the steps have never cause me any trouble.
What to do?
-First read the post of the Custom ROM including their answers, as it always help before flashing something because you will read if it have any kind of problem or etc from users feed back, and of course the OP info.
-Always have a backup of your stock ROM and personal data to avoid any lost.
-The break-the-glass solution in case of any problem will be always to know which version of phone do you have and have a Fastboot ROM for emergencies or if you are returning to MIUI stock, and the MIFlashTool from MIUI site.
-Always clean flash when you are going to another rom.
What not to do:
-Wiping and formating things you don't know what are you messing with, eg. Vendor partition.
-Never do a dirty flash over another custom ROM or stock, only do dirty flash in the same ROM type if the Dev says is possible to "update" that rom with that method, otherwise do a clean flash.
-Never flash another MIUI ROM that's not your type (China, Global, EEA, Rus, etc) with the MIFlashTool.
-Never flash or use the MIUI Tool with low battery
This might be the common and global things that always someone can tell you, if not the much but i hope it might help
never wipe system, unless you're planning to install another rom after that.
/system is where your OS (ROM) is located, wiping it is wiping your OS from your phone.
IDK much about disable DM-v and vbmeta, all I know is we need these two for disabling android's verified boot, secure boot thingy from google. yay.
AFAIK, we have 3 ways to disable DM-V
Using ofox, open settings > ota > mark on 'disable dm-v' before flashing ROM
by flashing disable dmv zip
by flashing magisk because it's included in magisk.
just do one of them but you can do all three, it doesn't really matter.
and vbmeta is needed only if you're on MIUI and about to flash AOSP rom.
but lately most custom AOSP already zipped with vbmeta so you don't need to worry about that.
here's how I flash ROMs
format data,
reboot recovery,
wipe cache, dalvik, system, data, internal,
flash firmware
flash ROM
flash gapps (optional)
flash kernel (optional)
flash magisk
reboot
hope this helps.
Wipe system if you are installing another rom otherwise you will end in bootloop because there is no system to boot.
Get a latest flashable firmware for your Note7 and place it in your mobile in case you get bootloop.
Install Recovery have every thing always backup.
Use Titanium backup for your apps even system apps should be backedup if you are going to modified system apps or delete them .
I just got the device 2 hours ago already making an optimized/rooted/debloated stock rom for it .
vexa said:
never wipe system, unless you're planning to install another rom after that.
/system is where your OS (ROM) is located, wiping it is wiping your OS from your phone.
IDK much about disable DM-v and vbmeta, all I know is we need these two for disabling android's verified boot, secure boot thingy from google. yay.
AFAIK, we have 3 ways to disable DM-V
Using ofox, open settings > ota > mark on 'disable dm-v' before flashing ROM
by flashing disable dmv zip
by flashing magisk because it's included in magisk.
just do one of them but you can do all three, it doesn't really matter.
and vbmeta is needed only if you're on MIUI and about to flash AOSP rom.
but lately most custom AOSP already zipped with vbmeta so you don't need to worry about that.
here's how I flash ROMs
format data,
reboot recovery,
wipe cache, dalvik, system, data, internal,
flash firmware
flash ROM
flash gapps (optional)
flash kernel (optional)
flash magisk
reboot
hope this helps.
Click to expand...
Click to collapse
Mmm, I used to flash custom ROMs like this way:
- wipe cache, dalvik, system, data, internal,
- format data,
- reboot recovery,
- flash firmware (never did it)
- flash ROM
- flash gapps (optional)
- flash kernel (optional)
- flash magisk
- reboot
What do you mean by flashing a firmware before custom rom? (red)
CrashOverride93 said:
Mmm, I used to flash custom ROMs like this way:
- wipe cache, dalvik, system, data, internal,
- format data,
- reboot recovery,
- flash firmware (never did it)
- flash ROM
- flash gapps (optional)
- flash kernel (optional)
- flash magisk
- reboot
What do you mean by flashing a firmware before custom rom? (red)
Click to expand...
Click to collapse
this firmware, because some roms require certain firmware version (usually the latest stable one)
vexa said:
this firmware, because some roms require certain firmware version (usually the latest stable one)
Click to expand...
Click to collapse
Ohh didn't know. Thanks for letting it me know.
I only flashed, until now, RR and AEX. Now I'm back on Xiaomi.eu ROM But never had any problem.
Since in my last post I made a complete mess out of my first time trying to root my K20 and install lineage I wanted to my make a separate post so that I can list all the steps I need to take to correctly setup my phone how I want it.
What I actually want
A rooted device
Lineage OS
Minimal excess files (A clean Install)
Current Steps
Unlock and flash recovery
Backup
Format Data! (It's important if you come from Miui)
Install Q Firmware + vendor
Install LineageOS followed by gapps
Reboot into system and setup device.
Reboot into recovery and flash magisk
Profit???
Feel free to tell me how stupid I am and what I need to add to the list or steps I should take to make this process better.
I also dont know if its possible to get recovery and rom on android 10 versions.
Thanks
Did these steps not work?
Sent from my Redmi K20 Pro using Tapatalk
BJack0 said:
Since in my last post I made a complete mess out of my first time trying to root my K20 and install lineage I wanted to my make a separate post so that I can list all the steps I need to take to correctly setup my phone how I want it.
What I actually want
A rooted device
Lineage OS
Minimal excess files (A clean Install)
Current Steps
Flash a custom recovery
Create a backup
Root???
Install LineageOS
Profit???
Feel free to tell me how stupid I am and what I need to add to the list or steps I should take to make this process better.
Thanks
Click to expand...
Click to collapse
1. Unlock and flash recovery
2. Backup
3. Format Data! (It's important if you come from Miui)
4. Install Q Firmware + vendor
5. Install LineageOS followed by gapps
6. Reboot into system and setup device.
7. Reboot into recovery and flash magisk
You could also check LOS thread: Here and here
Remember:
Chinese firmware: Widevine L3 and NFC support
Indian firmware: Widevine L1 but no NFC support
ishaqtkr said:
Did these steps not work?
Sent from my Redmi K20 Pro using Tapatalk
Click to expand...
Click to collapse
They may work as it but I was just wondering if anyone could go into more detail or if there was a better approach and from what Kollachi said there clearly is a better way that what I said.
Since I'm in stock ROM and haven't ever flashed AOSP ROM in this phone I'll just back off lol
Sent from my Redmi K20 Pro using Tapatalk
Kollachi said:
1. Unlock and flash recovery
2. Backup
3. Format Data! (It's important if you come from Miui)
4. Install Q Firmware + vendor
5. Install LineageOS followed by gapps
6. Reboot into system and setup device.
7. Reboot into recovery and flash magisk
Click to expand...
Click to collapse
I like the details steps but I have a few questions.
(Unlock and flash recovery) From what I can tell there are two recovery's Orange fox and TWRP
(Format data) Just format data or are there other sections I should format/wipe
(Install Q Firmware + Vendor) I have no idea what Q firmware is or what vendor you are referring to
(Install Lineage + gapps) Is there a specific version from the Mi 9T pro since the official site doesn't list it
Any of the two recoveries will work. Q firmware means Android Q. Wile data/cache dalvik that's it. Regarding firmware, there's a clear topic of Lineage OS in K20 Pro forum which is still in unofficially state
Sent from my Redmi K20 Pro using Tapatalk
BJack0 said:
I like the details steps but I have a few questions.
(Unlock and flash recovery) From what I can tell there are two recovery's Orange fox and TWRP
(Format data) Just format data or are there other sections I should format/wipe
(Install Q Firmware + Vendor) I have no idea what Q firmware is or what vendor you are referring to
(Install Lineage + gapps) Is there a specific version from the Mi 9T pro since the official site doesn't list it
Click to expand...
Click to collapse
1. You can take what you want. Orangefox is based on TWRP.
2. Format data is needed if you come from miui. If you did it you are good to go. But it wouldn't be false to wipe system, dalvic, cache
3.https://downloads.akhilnarang.me/MIUI/raphael/ --> Take 10.4.6.0 or 10.4.8.0 (Android 10 = Q)
4. No there is no specific version.
BJack0 said:
I like the details steps but I have a few questions.
(Unlock and flash recovery) From what I can tell there are two recovery's Orange fox and TWRP
(Format data) Just format data or are there other sections I should format/wipe
(Install Q Firmware + Vendor) I have no idea what Q firmware is or what vendor you are referring to
(Install Lineage + gapps) Is there a specific version from the Mi 9T pro since the official site doesn't list it
Click to expand...
Click to collapse
I would recommend the latest TWRP from here
https://forum.xda-developers.com/k2...icial-twrp-xiaomi-redmi-t3944363/post79823568
The dev is an official TWRP dev, so this version, or something very close to this, is likely to become official in the future.
OrangeFox is a heavily modified TWRP and has a lot of added functionality specific to MIUI. If you wanted to stay on stock MIUI, but debloat and have root, etc. then OF would be the better choice, as it has functionality that lets it play nicely with MIUI (it can remain installed when OTA updates are installed)
As someone new to flashing on Android, I would suggest downloading a 10.4.x fastboot ROM from the site I pointed to in your other post, then follow the same procedure to flash the ROM.
Make your choice based on Kollachi's info and what's important to you (HD Netflix - choose Indian, or a working NFC - choose Chinese)
However you MUST change the flash option to 'clean all'.
At this point you've got a nice squeaky clean starting point.
Boot into the ROM at least once, though it's not necessary to go through all the setup.
After that follow Kollachi's steps but you can now ignore the step to flash vendor and firmware as it's all part of the fastboot ROM already flashed.
Wipe cache and dalvik, format data.
There is no official LOS for this phone yet. Hopefully it will go official in the future.
For now just get the current Android 10 based LOS from here.
https://forum.xda-developers.com/k20-pro/development/rom-lineageos-17-0-t3976469/post80406191
Robbo.5000 said:
I would recommend the latest TWRP from here
The dev is an official TWRP dev, so this version, or something very close to this, is likely to become official in the future.
OrangeFox is a heavily modified TWRP and has a lot of added functionality specific to MIUI. If you wanted to stay on stock MIUI, but debloat and have root, etc. then OF would be the better choice, as it has functionality that lets it play nicely with MIUI (it can remain installed when OTA updates are installed)
As someone new to flashing on Android, I would suggest downloading a 10.4.x fastboot ROM from the site I pointed to in your other post, then follow the same procedure to flash the ROM.
Make your choice based on Kollachi's info and what's important to you (HD Netflix - choose Indian, or a working NFC - choose Chinese)
However you MUST change the flash option to 'clean all'.
At this point you've got a nice squeaky clean starting point.
Boot into the ROM at least once, though it's not necessary to go through all the setup.
After that follow Kollachi's steps but you can now ignore the step to flash vendor and firmware as it's all part of the fastboot ROM already flashed.
Wipe cache and dalvik, format data.
There is no official LOS for this phone yet. Hopefully it will go official in the future.
For now just get the current Android 10 based LOS from here.
Click to expand...
Click to collapse
When ever I think I have the process memories and I follow the steps on my screen I still somehow **** this up and I cant understand how.
My current steps include
Flash the fastboot with the ROM that you linked me in my first post
Flash the recovery with TWRP (Every time I have then tried going back into TWRP is failed to work and prompted the original MIUI recovery)
Install the TWRP zip from custom recovery to try and fix the issue above (Only had this work once on orangefox and then never had success again)
So now I try to just flash the recovery and boot to it using CMD and it works fine
Move the lineageOS files from my PC to the phone SDCard
If I wipe data and the caches as suggested then the lineageOS zip is now go and I am back to flashing the fastboot ROM to restart the process
I know this might seem like im either stupid or just not getting it but could you or anyone else please make a bullet pointed list with links to what I have to download in order to actually achieve this since I cant do anything correctly even when trying to follow the steps.
(Im going to sleep since I have been trying to do this for hours now and I will check reply's in the morning.
Thanks for the help so far EVERYONE
BJack0 said:
When ever I think I have the process memories and I follow the steps on my screen I still somehow **** this up and I cant understand how.
My current steps include
Flash the fastboot with the ROM that you linked me in my first post
Flash the recovery with TWRP (Every time I have then tried going back into TWRP is failed to work and prompted the original MIUI recovery)
Install the TWRP zip from custom recovery to try and fix the issue above (Only had this work once on orangefox and then never had success again)
So now I try to just flash the recovery and boot to it using CMD and it works fine
Move the lineageOS files from my PC to the phone SDCard
If I wipe data and the caches as suggested then the lineageOS zip is now go and I am back to flashing the fastboot ROM to restart the process
I know this might seem like im either stupid or just not getting it but could you or anyone else please make a bullet pointed list with links to what I have to download in order to actually achieve this since I cant do anything correctly even when trying to follow the steps.
(Im going to sleep since I have been trying to do this for hours now and I will check reply's in the morning.
Thanks for the help so far EVERYONE
Click to expand...
Click to collapse
I just told you what I have done and I'm running it so far without issues.
Robbo just said you should flash the whole Chinese or indian rom but I don't like his steps because:
1. File is much bigger
2. MiFlash is just meh
3. If you forgot to change the flash process you are bricked if you don't take the correct firmware for your phone.
Default option in Miflash is set to "Clean all and lock". Every time you use it, you will need to change it into "clean all" or something other.
Kollachi said:
I just told you what I have done and I'm running it so far without issues.
Robbo just said you should flash the whole Chinese or indian rom but I don't like his steps because:
1. File is much bigger
2. MiFlash is just meh
3. If you forgot to change the flash process you are bricked if you don't take the correct firmware for your phone.
Default option in Miflash is set to "Clean all and lock". Every time you use it, you will need to change it into "clean all" or something other.
Click to expand...
Click to collapse
Yes flashing the whole fastboot ROM does add the risk, if you forget to change the flash option, but you are guaranteed a clean slate and so less likely to have any niggling issues that nobody else has. I would bet large sums of money that many of the issues you see on here, where only one person has some problem and everyone else is fine, would be solved by fastboot flashing MIUI before installing the ROM of choice.
If you know what you're doing and know when you'll be OK with what you've got and know when it's best to start clean, then going with the vendor and firmware is easier.
But if your unsure and new to flashing on Android phones, I will always suggest go with the overkill and know you've got the clean slate to start with.
---------- Post added at 10:56 AM ---------- Previous post was at 10:36 AM ----------
BJack0 said:
When ever I think I have the process memories and I follow the steps on my screen I still somehow **** this up and I cant understand how.
My current steps include
Flash the fastboot with the ROM that you linked me in my first post
Flash the recovery with TWRP (Every time I have then tried going back into TWRP is failed to work and prompted the original MIUI recovery)
Install the TWRP zip from custom recovery to try and fix the issue above (Only had this work once on orangefox and then never had success again)
So now I try to just flash the recovery and boot to it using CMD and it works fine
Move the lineageOS files from my PC to the phone SDCard
If I wipe data and the caches as suggested then the lineageOS zip is now go and I am back to flashing the fastboot ROM to restart the process
I know this might seem like im either stupid or just not getting it but could you or anyone else please make a bullet pointed list with links to what I have to download in order to actually achieve this since I cant do anything correctly even when trying to follow the steps.
(Im going to sleep since I have been trying to do this for hours now and I will check reply's in the morning.
Thanks for the help so far EVERYONE
Click to expand...
Click to collapse
It's sounds like the main issue is stock recovery is being restored. This is something that MIUI will do when it boots up.
When you first install TWRP you cannot boot into MIUI before booting to TWRP as you instantly lose TWRP. So you need to boot into TWRP first in order to do something to prevent it being overwritten.
Options are
1
Code:
fastboot boot TWRP.img
2 Use the button combo whilst still in fastboot - power and vol+, hold both until the phone vibrates and the initial logo appears.
Now to keep TWRP you need to either flash a custom ROM, flash Magisk or flash the dm-verity script.
In your case you want to flash LOS, so now you've booted into TWRP go ahead and continue with the steps given.
Also, wait until after you've formatted data before copying everything over. You can access the phone as an MTP device when in TWRP, so you'll be able to connect it to a PC and drag everything across, or you can stick everything on a USB OTG pen, if you have one, TWRP can read data from them too.
It's sounds like the main issue is stock recovery is being restored. This is something that MIUI will do when it boots up.
When you first install TWRP you cannot boot into MIUI before booting to TWRP as you instantly lose TWRP. So you need to boot into TWRP first in order to do something to prevent it being overwritten.
Options are
1
Code:
fastboot boot TWRP.img
2 Use the button combo whilst still in fastboot - power and vol+, hold both until the phone vibrates and the initial logo appears.
Now to keep TWRP you need to either flash a custom ROM, flash Magisk or flash the dm-verity script.
In your case you want to flash LOS, so now you've booted into TWRP go ahead and continue with the steps given.
Also, wait until after you've formatted data before copying everything over. You can access the phone as an MTP device when in TWRP, so you'll be able to connect it to a PC and drag everything across, or you can stick everything on a USB OTG pen, if you have one, TWRP can read data from them too.
Click to expand...
Click to collapse
The exact problem I have is that I cant transfer any files to the device after formatting the data. I follow the steps correctly and I get into TWRP successfully and then everyone has told me to format the data then install lineage but I cant install the OS if formatting the data removes it.
Get device into fastboot
Flash revocery with TWRP
power the device off
hold volume up and power
boot into custom recovery
format data
move lineageOS onto my device
install lineageOS
reboot
done.
This is the list of exact actions I am doing with no results is there something I am missing or something that is in the wrong order.
BJack0 said:
The exact problem I have is that I cant transfer any files to the device after formatting the data. I follow the steps correctly and I get into TWRP successfully and then everyone has told me to format the data then install lineage but I cant install the OS if formatting the data removes it.
Get device into fastboot
Flash revocery with TWRP
power the device off
hold volume up and power
boot into custom recovery
format data
move lineageOS onto my device
install lineageOS
reboot
done.
This is the list of exact actions I am doing with no results is there something I am missing or something that is in the wrong order.
Click to expand...
Click to collapse
You connect your phone to computer while in recovery to transfer the OS zip
Sent from my Redmi K20 Pro using Tapatalk
BJack0 said:
The exact problem I have is that I cant transfer any files to the device after formatting the data. I follow the steps correctly and I get into TWRP successfully and then everyone has told me to format the data then install lineage but I cant install the OS if formatting the data removes it.
Get device into fastboot
Flash revocery with TWRP
power the device off
hold volume up and power
boot into custom recovery
format data
move lineageOS onto my device
install lineageOS
reboot
done.
This is the list of exact actions I am doing with no results is there something I am missing or something that is in the wrong order.
Click to expand...
Click to collapse
After format data, reboot your device into recovery again and transfer LOS, gapps and all files you need.
Format data kills the storage.
I always used to reboot from TWRP back in to TWRP after formatting data, but I've recently seen someone saying that they just unmount data then remount it again. I haven't tried it myself but it certainly makes sense and would be quicker too.
Robbo.5000 said:
I always used to reboot from TWRP back in to TWRP after formatting data, but I've recently seen someone saying that they just unmount data then remount it again. I haven't tried it myself but it certainly makes sense and would be quicker too.
Click to expand...
Click to collapse
Yes I did that and it worked, unmounting and remounting helps detect the storage in PC
Sent from my Redmi K20 Pro using Tapatalk
Robbo.5000 said:
I always used to reboot from TWRP back in to TWRP after formatting data, but I've recently seen someone saying that they just unmount data then remount it again. I haven't tried it myself but it certainly makes sense and would be quicker too.
Click to expand...
Click to collapse
Yes that works. Tried it myself but prefer to reboot into recovery again.:laugh:
Finally Successful
After a long post I have finally finished the process successfully. This was pretty educational for me since I didn't understand any of this at the start I would like to thank everyone who reply's and all the information that you have provided.
need help guys, i stuck in bootloop.
- fastboot rom global china V10.3.17.0 PFKCNXM
- fastboot twrp 3.3.1
- format data
- flash vendor image cn 10.4.6.0
- wipe cache/dalvik
- flash lineage os
- flash gapps nano
- reboot
- stuck bootloop
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