Phone stuck on loading screen on every rom (even stock) - Lenovo P2 Questions & Answers

When i install any ROM my phone is stuck on boot animation, even on stock.
Before flashing process end i got message: detected filesystem ext4 for /dev/block/bootdevice/by-name/system
then i got: Script succeed: result was 1.00000 and everything ends and when i reboot i'm getting stuck on bootloop, ive tried many versions of TWRP and roms and nothing help. Mounting system doesnt help. Please, help me.
Everytime when i flash the ROM the system filesystem changes to EXT4

you do know that the system file system has to be ext4 on most cases if you want to use a custom rom?..
WHEN MOVING TO CUSTOM ROMS NOW:
1. Boot to twrp. (Make sure it is pietwrp from telegram or the official 3.2.3 or later version)
2. Select WIPE menu option
3. Select data partition
4. Change file format to f2fs or anyother.
5. Go back to Start Menu of TWRP, choose Reboot Menu Option
6.Reboot to Recovery
7. Repeat Steps 2 and 3
8. This time select EXT4 when changing file format
9. Do Step 5 and 6
10. Wipe System,Cache and Dalvik-Cache partitions
(not needed anymore: 10.1 If you're on official twrp, you have to flash pietwrp now if you're going to use a pie Custom Rom.!)
11. Flash your Custom Rom, Gapps (optional) and latest Magisk(optional)
12. Wipe Cache and Dalvik-Cache
13. Reboot. First Boot might take a few minutes but never longer than 7minutes.
If it takes longer, you're encountering a so called bootloop.
Comment hear if that happens, containing information on your twrp-version, rom, gapps, magisk and mods(if present) you're using.

Related

TWRP Can't Mount /System - OP3 Bricks When Trying to Flash New ROM??

I'm currently running my OP3 on Resurrection Remix 5.7.4 (MM 6.01), the phone has the latest version of TWRP and I've flashed other ROMs in the past without any issue
RR has proven to be quite unstable for me, the system UI keeps crashing, which renders the phone unusable until after a reboot so I wanted to flash Freedom OS as that worked quite well for me previously. When I tried to flash the ROM in TWRP the ROM seemed to flash successfully but when I rebooted, only the boot logo showed and then the screen went black and the phone refused to respond at all for about two hours, after that exactly the same thing happened. I managed to boot into recovery and tried flashing a different ROM but the result was the same every time, the only way to get the phone to work normally was to flash RR again/restore from a Nandroid backup, either way, the result is the same, I'm stuck on an unstable ROM and I don't know why, the last time I flashed these ROMs they worked fine, I followed all of the instructions for flashing said ROMs to the letter, I have the latest version of TWRP, etc.
Also it seems TWRP can't mount /system, in TWRP under "mount", system is unchecked, I checked it and tried again but found that whenever I rebooted the phone or attempted to flash a new ROM, it would always uncheck itself and flashing the ROM would fail, however strangely flashing the same version of RR was always successful. Is this why the flashing keeps failing and does anyone know what the problem could be?
Thanks!
bronderb said:
Go into your bootloader and format system, cache, and userdata (This will wipe EVERYTHING so be sure to backup). Then latest official flash stock rom and reboot. This should fix it. If this helped hit thanks!
Click to expand...
Click to collapse
Bootloader? There is no option in the bootloader to delete everything as far as I can see, do you mean in recovery? And if I wipe everything off the phone, how do I get the stock ROM onto the phone to flash it? When you say wipe userdata do you mean wipe internal storage or am I misunderstanding and you're telling me to wipe the usual dalvik, cache and data as you would for a normal clean flash?
bronderb said:
No, go into fastboot and plug into pc. Open cmd and type "fastboot format userdata" "fastboot format cache" "fastboot format system"
Click to expand...
Click to collapse
Okay, thanks, and then what? Do I flash TWRP then push the stock ROM to the phone and flash that? And exactly how do I do that?
bronderb said:
You just go into twrp (no need to reflash) then adb sideload oxygen os
Click to expand...
Click to collapse
Thank you, I am now running OOS, hopefully everything else will go smoothly now, planning to go back to FOS again
I didn't even have to use the fastboot commands to format, just sideloading the OOS file wiped everything anyway
Turns out the issue isn't actually fixed, "system" still appears unchecked in TWRP. Could the fact that I didn't actually format everything first have made a difference, given everything was wiped in the process anyway?
Looks like I'm going to be living the sideloading life...
Edit: Sideloading freedom OS failed, ended up having to restore from my TWRP backup. I don't know what I'm going to do, my main reason for using custom ROMs is installing a black theme, and OOS doesn't support Layers or Substratum fully so I can't stay on that
Is the thing that says "mount system as read-only" enabled in the mounts menu? /System isn't ever mounted when TWRP starts, you have to manually mount it, but as long as the updater-script tells /system to mount, it will. However, if that option to make it read-only is enabled, then nothing will ever write to /system. Last resort is deleting the .twrps file from /sdcard/TWRP folder to remove current TWRP preferences and then when you boot into TWRP, that first screen has the swiper to allow modifications, and you'll swipe that
frickinjerms said:
Is the thing that says "mount system as read-only" enabled in the mounts menu? /System isn't ever mounted when TWRP starts, you have to manually mount it, but as long as the updater-script tells /system to mount, it will. However, if that option to make it read-only is enabled, then nothing will ever write to /system. Last resort is deleting the .twrps file from /sdcard/TWRP folder to remove current TWRP preferences and then when you boot into TWRP, that first screen has the swiper to allow modifications, and you'll swipe that
Click to expand...
Click to collapse
It isn't set to read only, I have tried updating and resetting TWRP but nothing has helped, in fact it's got worse, I managed to sideload OOS but my attempted install of FOS failed so I tried to restore from a backup and that also failed, something which didn't happen back when I was on RR.
evilkitty69 said:
It isn't set to read only, I have tried updating and resetting TWRP but nothing has helped, in fact it's got worse, I managed to sideload OOS but my attempted install of FOS failed so I tried to restore from a backup and that also failed, something which didn't happen back when I was on RR.
Click to expand...
Click to collapse
Which version of TWRP are you running? The official 3.1.0-0 is good for OOS and OOS based ROMs only. Try eng.stk's version.
Use the latest eng-stk twrp.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
In recovery go to Wipe > Format data (this will wipe ALL in youre phone).
It's youre Data in F2FS? If yes you must change it to ext4, in recovery Wipe > Change file system. Reboot recovery. Check if it's changed.
Reboot to Bootloader (Fastboot). From PC reflash recovery.
Now copy Oos rom to the phone memory. Flash rom. Reflash recovery (the rom will overwrite the recovery). Reboot to recovery to see if it works. If not do it again.
I sugest to NOT restore old data. This way you'll have all new in youre phone.
tnsmani said:
Which version of TWRP are you running? The official 3.1.0-0 is good for OOS and OOS based ROMs only. Try eng.stk's version.
Click to expand...
Click to collapse
I was running 3.0.2-2 when the issue started, I updated to 3.0.3 and 3.1.0-0 but nothing changed. Thanks for the suggestion, I will give it a try
null0seven said:
Use the latest eng-stk twrp.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
In recovery go to Wipe > Format data (this will wipe ALL in youre phone).
It's youre Data in F2FS? If yes you must change it to ext4, in recovery Wipe > Change file system. Reboot recovery. Check if it's changed.
Reboot to Bootloader (Fastboot). From PC reflash recovery.
Now copy Oos rom to the phone memory. Flash rom. Reflash recovery (the rom will overwrite the recovery). Reboot to recovery to see if it works. If not do it again.
I sugest to NOT restore old data. This way you'll have all new in youre phone.
Click to expand...
Click to collapse
Help! I attempted to do this and the process failed, I didn't manage to wipe data because "/data could not be mounted as device or resource is busy"
Edit: Device now has nothing but TWRP and fastboot, no OS, no ADB, no data, no internal storage
If you can reflash twrp from PC. If not reflash recovery from twrp recovery : Instal > Image > Select Recovery (you must have TWRP.img in youre phone memory )
I managed to get hold of a few factory images and attempted to flash system.img through fastboot, resulting error was
"target reported max download size of 536,870,912 bytes" (system image is 3080 MB)
"invalid sparse file format at header magi"
null0seven said:
If you can reflash twrp from PC. If not reflash recovery from twrp recovery : Instal > Image > Select Recovery (you must have TWRP.img in youre phone memory )
Click to expand...
Click to collapse
I reflashed the modified TWRP successfully. The second suggestion wouldn't have worked, given my phone has no internal storage
You can't see internal storage because of the recovery does not work write.
If you have a working recovery you can do all you want.
null0seven said:
You can't see internal storage because of the recovery does not work write.
If you have a working recovery you can do all you want.
Click to expand...
Click to collapse
The recovery was working at this point, the issue turned out to be the data partition, system was formatted to ext4 but I didn't realise data was in f2fs which caused the problem in the first place. I formatted to ext4 and everything worked, I was able to install paranoid android and everything worked...
...until I flashed the wrong firmware and now I've hard bricked it! I'm going to try the hard brick toolkit
Edit: After 12 hours of being an unresponsive brick, the phone suddenly booted, system doesn't work but it has recovery. Unfortunately I seem to be back to square one, if I try to flash something it appears to succeed but then the phone doesn't boot up into system
So I am now back to the original issue of system not mounting, in terminal if I type "mount /system" I get following error:
"mounting /dev/block/sde20 on /system failed: Device or resource is busy"
Anyone know how to solve this?
I formatted everything, reflashed recovery and tried to flash OOS, got following error:
Code:
[FONT="Courier New"]"This package is for OnePlus3 devices, this is a oneplus3t" (it isn't)
"Updater process ended with ERROR: 7
Error installing zip file /sdcard/OOS3.2.6.zip" [/FONT]
Issue was "solved" by flashing PA, GApps and the correct firmware
Hopefully that's the end of all this drama, thanks to everyone for their suggestions
Hi, I'm pretty new at rooting and I seem to have a similar error. I'm getting the "can't mount /system" error in TWRP. I am able to boot into OOS 4.1.3 and run the nandroid backup but, I keep getting the same error and am unable to select "system" when choosing the mount option in TWRP.
Do I need to have all partitions in f2fs? My system partition is in ext4. Is this what solved your issue?
It seems my phone is functional even with the error active but, I've been trying to get systemless SuperSU and MagiskHide working and I think that's what is preventing me from doing so.

Takes too much time in every reboots

I got one problem on every rom
Whenever i reboot my phone it takes too much time in booting up
I think every time i reboot cache wiped automatically
Any solution for this sorry for my bad english
best thing to do is just start again - the following steps will erase all user data on internal storage - backup photos documents or anything else you need first
put your phone into fastboot and connect to pc via usb
open a terminal/cmd window where you have your fastboot files
type
Code:
fastboot erase userdata
now go into twrp recovery
goto wipe
advanced wipe
format the following paritions
system
data
cache
art/delvik cache
goto home screen of twrp
mounts
mount the partitions you just wiped
goto home screen of twrp
install
select rom zip
dont restart
goto home screen of twrp
select nano gapps downloaded from http://opengapps.org/
you need arm 7.1 nano
optional
if using lineageos or rom based on it
goto home screen of twrp
install
select suaddon zip (see lineageos instructions for link or get from lineageos website)
Final step
after flashing of the last zip
wipe delvik/art cache from the option after flashing zip
restart
if you have flashed any other zips or modded in any other way it may have an impact on startup
first boot can take up to 10mins
normal boots after take up to around 2mins from power on
TheFixItMan said:
best thing to do is just start again - the following steps will erase all user data on internal storage - backup photos documents or anything else you need first
put your phone into fastboot and connect to pc via usb
open a terminal/cmd window where you have your fastboot files
type
now go into twrp recovery
goto wipe
advanced wipe
format the following paritions
system
data
cache
art/delvik cache
goto home screen of twrp
mounts
mount the partitions you just wiped
goto home screen of twrp
install
select rom zip
dont restart
goto home screen of twrp
select nano gapps downloaded from http://opengapps.org/
you need arm 7.1 nano
optional
if using lineageos or rom based on it
goto home screen of twrp
install
select suaddon zip (see lineageos instructions for link or get from lineageos website)
Final step
after flashing of the last zip
wipe delvik/art cache from the option after flashing zip
restart
if you have flashed any other zips or modded in any other way it may have an impact on startup
first boot can take up to 10mins
normal boots after take up to around 2mins from power on
Click to expand...
Click to collapse
Same process i tries but the problem is it takes too much time
And i didn't flash any other zip currently i am on viper os
Normal boot also takes around 10 mins
jatintomar said:
Same process i tries but the problem is it takes too much time
And i didn't flash any other zip currently i am on viper os
Normal boot also takes around 10 mins
Click to expand...
Click to collapse
Not used that rom
I just use lineageos

Stuck in Twrp reboot loop

I recently installed twrp and for my moto g5 then I did format data later on went for reboot system then I found no os installed so I installed a custom Rom later rebooted the system then I got stuck in twrp loop. I went through all the solution but it did not work so please help. Thank you
If you're on stock rom you need to remove dm-verity for it to boot (read faqs on twrp thread!)
For custom rom flash it correctly
Wipe
Advanced wipe
Wipe system data cache
Install
Select rom zip
Select gapps zip
Select root zip (optional)
Wipe cache
Restart
What architecture rom and twrp are you using?

Can't install MIUI custom ROM on Mi A2 Lite

I'm trying to instal MIUI 11 from this link: https://forum.xda-developers.com/mi-a2-lite/development/rom-daisy-miui-11-hybridos-stable-t4003651
However after flashing the ROM the recovery says there's no OS at all. If I reboot it bootloops.
The only way I can go back to recovery is by using adb commands and flashing a IMG. Then TWRP says it can't open destination log file.
What can I do? Thanks!
I'm not sure what you've done with your device and I'm not sure if you know how to read (because there are a LOT of guides throughout the forum), but here we go :
1 - Flash stock ROM (check the forum again on how to do it or Google it.). Do this before you're trying to flash any ROM, really.
2 - Unlock the bootloader and boot TWRP from your PC.
3 - On TWRP go to Wipe and choose Wipe Data, type 'yes' and confirm it to wipe data.
4 - Now you're gonna need to boot into TWRP again, because TWRP sometimes breaks after wiping data, simply go to Reboot section and choose 'Bootloader' in TWRP. This will get you to Fastboot mode, you will need to boot TWRP from your PC again.
5 - Once you get into TWRP, flash the ROM, flash the TWRP.zip if you want.
6 - Go into Reboot section in TWRP and check your boot slot and change it. (If A make it B, if B make it A) and reboot into system.
7 - If you want to install Magisk or any other mod through TWRP, :
7a - if you've installed TWRP.zip previously, reboot into recovery and install your mods/Magisk and then boot into system
7b - if you didn't install TWRP.zip, reboot to Bootloader/Fastboot and boot TWRP, then flash your mods/Magisk. Finaly boot into system.
marstonpear said:
I'm not sure what you've done with your device and I'm not sure if you know how to read (because there are a LOT of guides throughout the forum), but here we go :
1 - Flash stock ROM (check the forum again on how to do it or Google it.). Do this before you're trying to flash any ROM, really.
2 - Unlock the bootloader and boot TWRP from your PC.
3 - On TWRP go to Wipe and choose Wipe Data, type 'yes' and confirm it to wipe data.
4 - Now you're gonna need to boot into TWRP again, because TWRP sometimes breaks after wiping data, simply go to Reboot section and choose 'Bootloader' in TWRP. This will get you to Fastboot mode, you will need to boot TWRP from your PC again.
5 - Once you get into TWRP, flash the ROM, flash the TWRP.zip if you want.
6 - Go into Reboot section in TWRP and check your boot slot and change it. (If A make it B, if B make it A) and reboot into system.
7 - If you want to install Magisk or any other mod through TWRP, :
7a - if you've installed TWRP.zip previously, reboot into recovery and install your mods/Magisk and then boot into system
7b - if you didn't install TWRP.zip, reboot to Bootloader/Fastboot and boot TWRP, then flash your mods/Magisk. Finaly boot into system.
Click to expand...
Click to collapse
Step 1 is wrong, miui ports have base stock in built, no need to make a clean flash
Step 5 is wrong, miui ports have twrp in built, you don't need flash twrp zip
Step 6 is wrong, miui ports need to be installed in the current active slot, no needed change slot
If your device have unlock bootloader and enable usb debugging, only boot twrp.img, only boot no flash, like the OP did it (fastboot boot twrpname.img)
Wipe> format data> yes
Install> install miui.zip
Install> install magisk (optional)
Reboot>system

Pixel Experience 11 Bootloop

Hi,
i was using LineageOS 17.1(Android 10) on my pixel Xl (32 gb storage)
when android 11 came out, I thought I would switch to pixel experience. So I went to their official website and downloaded the android 11 version of pixel XL
There was an instruction guide provided by the developers on how to install android 11
So I followed that and even after applying update from the adb, there was no issue at all
but when I pressed "Reboot to system" Bootloop is happening
Note: I didn't noticed the official instruction first so i installed twrp to flash the rom just like I flashed LineageOS, but in the advance wipe section, there was only 4 option available
-Dalvik / ART cache
-System
-Data
-Internal Storage
there was no cache option
I formatted the data and wiped all of them and tried to both install and sideload the rom but every time during the installation, an error (code 28) occurs
Then I downloaded the rom again hoping that the previos 1 was corrupted and i saw the instruction guide this time.
So I followed the guide and installed their recovery image, flashed recovery partition and flashed the rom using sideload.
But after rebooting the system, Bootloop keeps occurring
*sorry for any misspell or grammatical mistake*
ROM and Recovery image Downloaded from - https://download.pixelexperience.org/marlin (Android 11, 2021/04/16)
ROM and Recovery image installation guide - https://wiki.pixelexperience.org/devices/marlin/install/
I'm having the same issue. Did you flash the repartition zip?
I ended up reflashing stock rom https://developers.google.com/android/images#marlin
Try doing that and restarting the process
GalaxyWhy said:
I'm having the same issue. Did you flash the repartition zip?
I ended up reflashing stock rom https://developers.google.com/android/images#marlin
Try doing that and restarting the process
Click to expand...
Click to collapse
I actually solved the problem a few moments ago
What i did wrong was, when i sideload the rom rom file with twrp i always cleared the dalvik and cache file
let me make a little guide for you..hope that will help
1. install twrp recovery
2. go to wipe section -> advanced wipe -> wipe all 4(Dalvik/ART cache, System, Data, Internal Storage)
3. do a factory reset and format data
4. go to mount section and check all the boxes (system, data, vendor)
5. sideload the repartition zip according to your storage and device model (mine was pixel xl 32gb)
6. after sideload is done reboot the system..it will reboot into recovery again
7. then again sideload the rom file (don't check the clear cache and dalvik boxes)
8. after that is done, go back to main menu and go to reboot-> switch to slot B-> Reboot into system
Hopefully you're done
Note: don't skip any step regarding how minor it is
and if you wish you can also follow the official instruction: https://wiki.pixelexperience.org/devices/marlin/install/
Let me know if it works for you
Best of luck!

Categories

Resources