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
Related
****edit: It appears that the option "format /system" which is tucked away in a sub menu did the trick and erased the rom.
I am trying to completely delete a rom I have installed which is CyanogenMod 11 but it seems to stay no matter what, or I'm not doing it right.
First I go into recovery with the power+vol down and choosing recovery.
I have ClockworkMod 5.8.1.5.
From there I choose the wipe data/factory reset and also the wipe cache partition and wipe dalvik cache.
Then I choose the install zip from sd card to install Blackout_ICS_Incredible_v4.0.zip
After following the installer instructions and rebooting it goes back to CM11...
Any ideas how to wipe CM11 from my device?
Thanks :good:
Netanel1 said:
****edit: It appears that the option "format /system" which is tucked away in a sub menu did the trick and erased the rom.
I am trying to completely delete a rom I have installed which is CyanogenMod 11 but it seems to stay no matter what, or I'm not doing it right.
First I go into recovery with the power+vol down and choosing recovery.
I have ClockworkMod 5.8.1.5.
From there I choose the wipe data/factory reset and also the wipe cache partition and wipe dalvik cache.
Then I choose the install zip from sd card to install Blackout_ICS_Incredible_v4.0.zip
After following the installer instructions and rebooting it goes back to CM11...
Any ideas how to wipe CM11 from my device?
Thanks :good:
Click to expand...
Click to collapse
Try formatting with fastboot.
Boot your device into fastboot and type these commands
Code:
fastboot devices
Just to be sure ur devic is connected
Code:
fastboot format system
Code:
fastboot format data
Code:
fastboot format boot
If the above doesnt work, susbtitute
Code:
format
with
Code:
erase
4EXT Recovery 1.0.0.6 R2
try changing the recovery via bootloader, download latest 4ext recovery zip then rename it to PD98IMG and place it to your root directory of your sdcard. Then go into bootloader it will automatically detect zip file and will ask you for update, press volume up to start the update, reboot and your done. After flashing new recovery go into recovery and then wipe/format from there format all partitions except sd card. When done go back to main menu and select info to see the free space/size of all partitions.
Device: HTC Desire HD
ROM: CM11 M8.1
Recovery: 4EXT 1.0.0.6 R3 build 8
If it helped you then pressing then press the thanks button.
Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...
I have the same problem
Here the same but with CM14 after a wrong download & install now Recovery Loop
How to solve???
I had this problem too. Flash the Oxygen recovery OB7. It will update automatically and turn on. But be patient because it takes a lot.
sibmon said:
Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...
Click to expand...
Click to collapse
The way I found works is to start from scratch and yes you will lose all data on the phone. Had to do this yesterday because I messed a few things up.
Make sure you have the modified recovery (1.28), Beta 9 Full (1.3GB), and SuperSU (SR5) if you want root, on your computer. And you will need your computer for these steps.
1. Boot to TWRP > Wipe > Format Data. There's a warning screen you just type yes and press enter. This should set your /data partition to F2FS; all other partitions will remain EXT4. (The TWRP MTP didn't pop up on me so then I had to reflash twrp from fastboot). If your PC see's your device after this step, skip to step 9, but my guess is, when you format data, the required files for MTP disappears with it.
2. Power off your device.
3. Put device into fastboot mode (start device by holding volume up + power)
4. Connect device to PC.
5. fastboot flash recovery modded_twrp.img
6. Disconnect device from computer and shut down phone.
7. Load recovery (start device by holding volume down + power)
8. Connect to PC
9. TWRP MTP should be working; transfer the recovery file, beta9, and super SU (if you want root) to your internal storage.
10. I usually disconnect my phone from my PC at this point.
11. Go to Install > sdcard > media folder (your files should be here).
12. Flash Beta 9 zip.
13. Reflash modded TWRP (click Install Image button and you should see your TWRP file).
14. Reboot to Recovery (I noticed that click on Reboot and Recovery freezes TWRP on me, so you can manually power down by holding power button down).
15. Swipe to accept modifications
16. If you don't need root, you're all done. The first boot takes like 5 min.
For some reason for root, it doesn't work if you try without freeing up some space in the system folder. What you can do is:
1. In TWRP > Mount > tick off System > head back out to main menu
18. Advanced > File Manager > > system folder > app folder > and delete some google apps (ie. calendar, gmail, chrome; should be enough; can be downloaded from play store later)
19. Flash SuperSU SR5.
20. Wipe Cache and Dalvik, reboot.
I've noticed that if you don't root, your device will be encrypted on first boot of beta 9 (which causes some issues in TWRP not being able to mount the /data partition and decryption passwords not working in TWRP.
Same problem here, **** broken OB9 update.
EDIT: For those with the same problem, download stock recovery from here, flash it using adb, boot into recovery (might say that installation of update failed, it did for me) and then reboot to system.
Now it booted successfully and says that I have Open Beta 9. TWRP and SuperSU installations worked just fine after that.
I used twrp-3.0.2-22 to reflash beta 9 all is well.
I have same problem with twrp-3.0.2-1.28. Just boot into bootloader and flash twrp-3.0.2-22.
Can I flash that twrp-3.0.2-22 after I'm already on beta 9?
Nevermind I saw that it encrypts on first boot. I'll just wait for root again until after the final comes out.
No need for clean installation like hw4ng3r said.
I'll copy my other post's edit here if someone needs it.
For those with the same problem, download stock recovery from here, flash it using adb, boot into recovery (might say that installation of update failed, it did for me) and then reboot to system.
Now it booted successfully and says that I have Open Beta 9. TWRP and SuperSU installations worked just fine after that.
Click to expand...
Click to collapse
Got 145849 AnTuTu result with OB9. Might be able to get a better result if I were to clean install, but I've just dirty flashed every update since 3.2.5.
karliyo said:
No need for clean installation like hw4ng3r said.
Click to expand...
Click to collapse
Very true.
I interpreted the OP's comment as:
1. Already on TWRP
2. Tried full wipe and install (all data lost anyways)
---------- Post added at 12:23 PM ---------- Previous post was at 12:19 PM ----------
Tumpster said:
Can I flash that twrp-3.0.2-22 after I'm already on beta 9?
Nevermind I saw that it encrypts on first boot. I'll just wait for root again until after the final comes out.
Click to expand...
Click to collapse
I've read that .22 TWRP doesn't have decryption issues of the /data partition like .28 has, but don't take my word for it. And the encryption happened to me when I flashed Beta9 from TWRP .28 and rebooted system without flashing Super SU.
The decryption of the /data partition in TWRP seems to be an issue if the file system is F2FS on Beta 8 and Beta 9. I haven't had any issues with EXT4.
sibmon said:
Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...
Click to expand...
Click to collapse
Download stock recovery from OnePlus site (on very bottom) ,flash it using fastboot and than sideload new beta 9
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.
1. Download resources:
a. Download the rom UL USER, leave it there and do nothing to it yet.
b. Download the twrp.zip file https://mega.nz/#!l8BXgaDL!Y1AH5TM9jKI5r6LtEKFN_4Po105glHNR602yVDipfF8 (if you still have twrp installed beforehand)
c. Magisk 20.0 https://github.com/topjohnwu/Magisk/releases/download/v20.0/Magisk-v20.0.zip
2. Proceed:
Do not update the UL USER rom from the device's interface (SYSTEM UI), power off, boot into TWRP. Select install zip in the following order:
a. Rom UL USER
b. Twrp.zip
c. Magisk v20.0 (or exit the main menu, select Advanced, install root also)
Done, exit the main menu select advanced wipe, wipe cache, dalvik.
Reboot the device.
Done.
By chicken
This did not completely work for me going from .35 to .64. All the steps completed successfully but when I rebooted the phone, Magisk was not installed so I didn't have root. I was able to then boot to TWRP and successfully install Magisk, but I don't know why it didn't work the first time. Anyone else try this? Did it work as intended for you?
One other thing I noticed - TWRP no longer has an option to wipe the cache under wipe > advanced, only for Dalvik/ART cache. Why?
Wish I would have tried this before i updated and lost root, i flashed a root boot.img with fastboot now im bricked and don't know what to do.
EDIT: got twrp did a factory reset and im in now.
dungnghien said:
1. Download resources:
a. Download the rom UL USER, leave it there and do nothing to it yet.
b. Download the twrp.zip file https://mega.nz/#!l8BXgaDL!Y1AH5TM9jKI5r6LtEKFN_4Po105glHNR602yVDipfF8 (if you still have twrp installed beforehand)
c. Magisk 20.0 https://github.com/topjohnwu/Magisk/releases/download/v20.0/Magisk-v20.0.zip
2. Proceed:
Do not update the UL USER rom from the device's interface (SYSTEM UI), power off, boot into TWRP. Select install zip in the following order:
a. Rom UL USER
b. Twrp.zip
c. Magisk v20.0 (or exit the main menu, select Advanced, install root also)
Done, exit the main menu select advanced wipe, wipe cache, dalvik.
Reboot the device.
Done.
By chicken
Click to expand...
Click to collapse
In my experience after install back twrp reboot back to recovery (twrp) before flashing magisk .
Does this work when updating to A10?
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!