Hello, I now have 8 days note 10 lite today I unlocked bootloader, installed TWRP via adb after that I installed lineage os and wiping data etc. After that I faced a bootloop and lineageos bootscreen doesnt go away after 15 minutes.
So I tried to reflash the rom again, but twrp isnt able to reinstall the rom. I then used miflash to get original rom again.
Started all over installed twrp, flashed lineage os after this install after reboot I get everytime back into TWRP and looked on my pc and all files suddenly are encrypted on my phone and cant get lineage os rom again on my phone..
So I used miflash again and decided to ask here first. Does anybody know if I maybe use a wrong TWRP or missed a step?
I really dont understand it, I tried it for a 3th time. Here is exactly what I did.
- installed TWRP through ADB (TWRP-3.4.0-0_Android11_Roms_AndroidHQ254)
- In TWRP put rom on my internal storage
- Wipe Dalvik, data and cache
- Install rom (TWRP-3.4.0-0_Android11_Roms_AndroidHQ254)
- data wipe (where I had to type yes to confirm)
- Reboot to system and then it doesnt do anything and goes back into TWRP where I cant do anything, and I have to flash original rom back through MiFlash.
I run now MIUI 12.0.2
Android 10
Try using orangefox recovery. And i think you have to wipe data before installing rom, not after it.
ApexPrime said:
Try using orangefox recovery. And i think you have to wipe data before installing rom, not after it.
Click to expand...
Click to collapse
Thank you, I was able to do it with Orangefox.
Related
So here is my situation: I have a 3GB kenzo model with 6.3.24 EU ROM and ZCX TWRP 3.0.0-0. Of course bootloader in unlocked. Since the TWRP is pretty old, I updated it to RedWolf V3.1.
What I did:
Wipe: Dalvik/System/Data/Cache
Install Beta 7.9.22 or Stable 8.5.6.0 Kenzo firmware (tried with both)
Install RR image: RR-N-v5.8.5-20170924-kenzo-Final.zip
Install open gapps ARM64 7.1 (or not)
Wipe caches (also tried without wiping it)
Reboot
Bootloop
I know the first boot can take some time, so I let it run for 30+ minutes, still, only bootloop happened. Tried it a couple times, changing firmware, wiping caches at the end, ditching gapps etc. Images checked for md5 checksum on the phone, they are not corrupted. I was able to restore the EU ROM, but I really want to try out ResurrectionRemix. What could possibly the problem be?
Same here...i flash all nougat rom and got bootloop..now i stay in mm only...:C
Reflash newest stock image, than hack the emmc bootloader of it and try again
reemar said:
Reflash newest stock image, than hack the emmc bootloader of it and try again
Click to expand...
Click to collapse
So you mean to flash the latest stock ROM, won't it remove TWRP and lock the bootloader? And how to "hack" the emmc bootloader? Sorry, I'm a newbie
Just wait for at least 15 minutes after flashing
DdroidTHEGAMER said:
Just wait for at least 15 minutes after flashing
Click to expand...
Click to collapse
What do you mean, wait in TWRP for 15 minutes or when booting up the OS? As I said, I waited for 30+ minutes while it booted up.
Try installing ROM without flashing the firmware
Minions007 said:
Try installing ROM without flashing the firmware
Click to expand...
Click to collapse
That was the first thing I did (I didn't know a firmware was needed so I only flashed the RR ROM). Same bootloop
You could try to format data partition. Then wipe system,data,cache,dalvik cache and internal partition. After that Copy actually firmware, rom and opengapps arm64 pico in internal memory (Download all files again. Maybe archiv was damaged). Then flash firmware, rom, gapps and do wipe Cache/dalvik and reboot. Then report.
SpeRator said:
You could try to format data partition. Then wipe system,data,cache,dalvik cache and internal partition. After that Copy actually firmware, rom and opengapps arm64 pico in internal memory (Download all files again. Maybe archiv was damaged). Then flash firmware, rom, gapps and do wipe Cache/dalvik and reboot. Then report.
Click to expand...
Click to collapse
Did it, same result. Wiped everything, copied zips to internal storage, flashed from there and boom, bootloop
Hmm strange. You could test a good modified rom of rr.
Try this Rom:
https://www.androidfilehost.com/?fid=673791459329049490
And these Gapps:
https://www.androidfilehost.com/?fid=673791459329049438
If it all not Work, you have to flash actually official Rom to restore all with edl.
I have the exact same problem. Cant flash any ROM without getting bootloop. The bootloop though isnt a standard one, i think. I get the logo of the ROM and the phone starts to give Tiny vibrations in regular periods of time. I also left the phone for a long time hoping it'll eventualy boot. No luck. Tried flashing stock ROM with miflashtool and edl. Didnt help as well. I wonder if it could be the fault of any previous roms i had installed.
Twrp:
-are you sure you are not in read mode? Change to writemode.
-All relevant partitions mounted?
SpeRator said:
Twrp:
-are you sure you are not in read mode? Change to writemode.
-All relevant partitions mounted?
Click to expand...
Click to collapse
Changed to writemode.. default options selected in the mounts screen.
unable to flash any Nougat roms- stuck in boot animation.
is it because the bootloader was unlocked unofficially via lollipop fastboot ROM 7.1.8??
All right, got it working.
I flashed the latest official MIUI ROM with the official flashing tool with the option "clear all". Then I had to open the bootloader again, then flash TWRP, then flash RR, and it works! Looks like something was wrong with the previous installation, the clearing everything did the job.
Were your bootloader unlocked officially?
aldhi said:
Were your bootloader unlocked officially?
Click to expand...
Click to collapse
Unlocked Unofficially via this method https://www.youtube.com/watch?v=2FmaCdnLi58
tonyrulez said:
So here is my situation: I have a 3GB kenzo model with 6.3.24 EU ROM and ZCX TWRP 3.0.0-0. Of course bootloader in unlocked. Since the TWRP is pretty old, I updated it to RedWolf V3.1.
What I did:
Wipe: Dalvik/System/Data/Cache
Install Beta 7.9.22 or Stable 8.5.6.0 Kenzo firmware (tried with both)
Install RR image: RR-N-v5.8.5-20170924-kenzo-Final.zip
Install open gapps ARM64 7.1 (or not)
Wipe caches (also tried without wiping it)
Reboot
Bootloop
I know the first boot can take some time, so I let it run for 30+ minutes, still, only bootloop happened. Tried it a couple times, changing firmware, wiping caches at the end, ditching gapps etc. Images checked for md5 checksum on the phone, they are not corrupted. I was able to restore the EU ROM, but I really want to try out ResurrectionRemix. What could possibly the problem be?
Click to expand...
Click to collapse
Backup all of your data from internal storage and flash latest fastboot developer ROM and setup it. This will fix all issues regarding ROMs, zips, bootloops and firmware and any other. After that flash latest ZCX recovery as RedWolf recovery causes problems for flashing ROMs and zips as per my experiance. Then simply flash RR and gapps and boot and wait for 15 minutes and till then don't restart device.
Hello,
I had already a custom ROM on my phone (AOSP Extended). When I opened TWRP and wiped everything (including system, data and internal), TWRP couldn't install my ROM because of some error code 7 (but that's not the main problem here). When I opened fastboot on my phone, I installed twrp into my phone using fastboot. The TWRP did boot up just fine. But when I clicked "install" and selected the custom ROM, TWRP simply closes, reboots the phone and TWRP starts again asking me if I want to allow changes. I noticed that this isn't because of my custom ROM. I tried also other things such as Gapps and TWRP does the same thing.. I don't know how to fix this. Can you please help? Thank you!
My twrp 3.2.1-0 is constantly crashing while i'm trying to install/flash any rom. I don't know what just happened. I actually tried to install chris bal greece's lineage os experimental and also installed his version of twrp but it crashed then, so I had to revert back to my own twrp and i'm facing the problem now also. please someone help, and do something quickly. I'm in India so technically there is no service center. You guys are my last hope. It's the only device I have got in my whole house. I hope you guys understand my problem and help me.
Format all data in TWRP then try to flash another ROM via ADB sideload. You can easily google it, how that works...
Heyyo, before installing a ROM from EUI ROM? I always recommend having a PC handy or a usb drive with the ROM and gapps and firmware of choice and then go into TWRP > wipe > format data > yes.
Next reboot to recovery and wipe dalvik, system and cache and then reboot to recovery again.
Then copy firmware, ROM and gapps to your phone and flash firmware, ROM then gapps and then reboot to system.
For TWRP version? Please ensure for CBG TWRP you have the version with quota support.
Hey all, so it appears that I screwed my phone, I am not sure how.
I was running LineageOS, and wanted to update to Android 10 one, so I followed the steps, and I think I screwed the sideloading part, so... long story short now when rebooting from OrangeFox RecoveryProject it says no OS detected, and when it boots it says encryption unsuccessful, I tried wiping and installing DisableForceEncryption_Treble_v17.2 and restarting, and the same thing happens.
I tried to flash through recovery both, and did not work:
https://xiaomifirmwareupdater.com/firmware/beryllium/
https://xiaomifirmwareupdater.com/archive/vendor/beryllium/
And when trying to flash through miFlash it doesn't work:
I go to fastboot in poco, hit refresh in miflash, it shows a device in the list, but the phone goes dark with 'something key to shutdown` written in the top left corner and if I hit the flash button nothing happens.
Can anyone assist with that please?
kishikaisei said:
Hey all, so it appears that I screwed my phone, I am not sure how.
I was running LineageOS, and wanted to update to Android 10 one, so I followed the steps, and I think I screwed the sideloading part, so... long story short now when rebooting from OrangeFox RecoveryProject it says no OS detected, and when it boots it says encryption unsuccessful, I tried wiping and installing DisableForceEncryption_Treble_v17.2 and restarting, and the same thing happens.
I tried to flash through recovery both, and did not work:
https://xiaomifirmwareupdater.com/firmware/beryllium/
https://xiaomifirmwareupdater.com/archive/vendor/beryllium/
And when trying to flash through miFlash it doesn't work:
I go to fastboot in poco, hit refresh in miflash, it shows a device in the list, but the phone goes dark with 'something key to shutdown` written in the top left corner and if I hit the flash button nothing happens.
Can anyone assist with that please?
Click to expand...
Click to collapse
This happened to me when I accidentally deleted the OS when flashing the latest MIUI 11 build (using TWRP). THIS IS HOW I FIXED IT.
Find a full firmware of whatever you wanted to flash, either Lineage or MIUI 11. Then flash via your recovery (you said you have orangefox). Use an external sd card, external USB or HDD since you technically wouldn't have access to your internal data. After flashing, same process as most updates, clear cache and dalkiv. Then flash a newer DFE (if you still want to decrypt, there is a page here in xda with it. Or go to miui forums Happybuddhist, the mod there, made a new one prebuilt with Magisk). Then reboot into recovery to make sure you keep your custom recovery. Once booted to recov. Boot to system. Should fix the issue.
You could check my guide here on how to unbrick your pocophone:
https://forum.xda-developers.com/poco-f1/how-to/unbrick-flashing-stable-rom-pocophone-t3901152
mecoromeo said:
This happened to me when I accidentally deleted the OS when flashing the latest MIUI 11 build (using TWRP). THIS IS HOW I FIXED IT.
Find a full firmware of whatever you wanted to flash, either Lineage or MIUI 11. Then flash via your recovery (you said you have orangefox). Use an external sd card, external USB or HDD since you technically wouldn't have access to your internal data. After flashing, same process as most updates, clear cache and dalkiv. Then flash a newer DFE (if you still want to decrypt, there is a page here in xda with it. Or go to miui forums Happybuddhist, the mod there, made a new one prebuilt with Magisk). Then reboot into recovery to make sure you keep your custom recovery. Once booted to recov. Boot to system. Should fix the issue.
Click to expand...
Click to collapse
I tried that, now I am a step forward I think, I flashed the stock firmware I found, and installed the latest stock ROM, rebooted (doesn't say no os anymore), but the only thing I see is a DELETE ALL DATA button and at the bottom 'Encryption was interrupted and can't be completed. As a result, the data on your phone is no longer accessible.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google account.'
Darklouis said:
You could check my guide here on how to unbrick your pocophone:
https://forum.xda-developers.com/poco-f1/how-to/unbrick-flashing-stable-rom-pocophone-t3901152
Click to expand...
Click to collapse
I have an issue with the MiFlash part, it seems that it doesn't work as I mentioned...
Aight all, formatting data partition to ext4 worked, now it is booting
kishikaisei said:
Aight all, formatting data partition to ext4 worked, now it is booting
Click to expand...
Click to collapse
Works now?
mecoromeo said:
Works now?
Click to expand...
Click to collapse
So I had an OS-less phone that don't get recognised in MiFlash, and I had orangeFox recovery.
The steps to fix were:
- Flash a full stock Firmware
- Flash the stock ROM
- Flash DFE
- Format data to ext4
- Reboot and it works
So thanks all for your help
Hi, I've recently repaired my mido with a new screen after a fall. After this I tried some custom roms. Initially I managed to install lineage 18.1. After I switched to dotOS. From this point on, the phone restarts a few seconds after the launcher appears. To fix this I used MiFlah to install latest MIUI, formatted data, wiped everything, tried TWRP and Orangefox, tried other custom roms with no changes. Now only stock MIUI11 works. Other custom roms (included lineage) gets the phone continuously rebooting. Could be an hardware problem? What am I doing wrong? It is the first time in ages I have problems flashing ROMS .-.
Thanks.
gabritb01 said:
Hi, I've recently repaired my mido with a new screen after a fall. After this I tried some custom roms. Initially I managed to install lineage 18.1. After I switched to dotOS. From this point on, the phone restarts a few seconds after the launcher appears. To fix this I used MiFlah to install latest MIUI, formatted data, wiped everything, tried TWRP and Orangefox, tried other custom roms with no changes. Now only stock MIUI11 works. Other custom roms (included lineage) gets the phone continuously rebooting. Could be an hardware problem? What am I doing wrong? It is the first time in ages I have problems flashing ROMS .-.
Thanks.
Click to expand...
Click to collapse
The vendor partition could have some code/ file that persists stock ui or system
and make sure your phone was rooted before flashing custom rom
and also via twrp flashing. from what Ive seen flash in twrp before flash custom rom( https://www.google.com/search?client=firefox-b-d&q=disable+encryption+treble ) then flash the "verity and encryption disabler ,theres another one to re enable encyption only " then flash custom rom
after flashing custom rom reboot poweroff(switch phone off via twrp)
reboot into twrp and flash whatever else you need
now reboot to system and your phone should work fine
Thanks, it worked!
I did:
Flash last miui with miflash
Flash recovery
Flash you suggested zip
Format data
Flash lineage 17.1 (android10)
WIpe system, data, cache, art cache
Flash any android 11 ROM
gabritb01 said:
Thanks, it worked!
I did:
Flash last miui with miflash
Flash recovery
Flash you suggested zip
Format data
Flash lineage 17.1 (android10)
WIpe system, data, cache, art cache
Flash any android 11 ROM
Click to expand...
Click to collapse
Holy **** how did you come up with this.
Either the zip with Magisk somehow fixed it or installing the android 10 rom somehow. Either way doesn't make sense
flairepathos.info said:
The vendor partition could have some code/ file that persists stock ui or system
and make sure your phone was rooted before flashing custom rom
and also via twrp flashing. from what Ive seen flash in twrp before flash custom rom( https://www.google.com/search?client=firefox-b-d&q=disable+encryption+treble ) then flash the "verity and encryption disabler ,theres another one to re enable encyption only " then flash custom rom
after flashing custom rom reboot poweroff(switch phone off via twrp)
reboot into twrp and flash whatever else you need
now reboot to system and your phone should work fine
Click to expand...
Click to collapse
Didn't work for me,
- did all the steps , exactly - flashed stock fastboot , then flashed Android 10 based rom crDroid + pico gapps. worked fine for 2 hours or so .
but interesting enough , phone freezes then shutdown without restarting , then i would go and trun it back on , but fingerprint not working now
heroboy107 said:
Didn't work for me,
- did all the steps , exactly - flashed stock fastboot , then flashed Android 10 based rom crDroid + pico gapps. worked fine for 2 hours or so .
but interesting enough , phone freezes then shutdown without restarting , then i would go and trun it back on , but fingerprint not working now
Click to expand...
Click to collapse
i think somewhere in the process the persist partition gets damaged .
heroboy107 said:
i think somewhere in the process the persist partition gets damaged .
Click to expand...
Click to collapse
so if you have magisk you can use a zip file to chmod 744 or 644 (it may be "chmod root 744" )the /persist partiton and thatll mean only true root has access
so 7 is read write execute 6 is read and write 4 is read only 5 is read execute i forgot which number was execute only 1 maybe?
so play with the permissions or look in the root folder for boot.p or permissions.sh then you can modify in there the permissions, it can cause bootloop , so always keep an original copy or youll hae to reflash(DISCLAIMER)
so you can pull the file using adb+root / or a root explorer
Copy it to phone then edit then copy to SDCARD
reboot to twrp then use shell/terminal "chmod 777" the partition where the file is / or read write everything
then copy the file and overwrite the original