Since the last beta OnePlus (Pie 9 for OP5) have been released, I have continued blocking and rebooting the system (using custom rom principally, but also stock rom).
Recently, I was able to replicate the problem I have with all the new pie rom (I tried LineageOs, Dirti, Omni and even stock); in practice, by opening more applications (8/10 or more) and then turning off the screen, the system freeze (with blue LED on); at other times, reboot instantly.
Can someone help me understand what the problem may be? Eventually, do you have any suggestions?
I state that I format/wipe each partition; here the complete sequence I use to format and install custom roms (a real madness!):
*Format Data and Wipe all
Flash 5.1.3 Full
*Wipe Davilk and cache
Boot OS (to create Vendor Partition)
Bootloader - fastboot flash recovery recovery.img
*Wipe Davilk and cache
OpBeta 22 firmware + vendor
*Wipe Davilk and cache
OpBeta 23 firmware (o latest)
*Wipe System, Data, Davilk and cache
Bootloader - fastboot format userdata - fastboot erase cache - fastboot flash recovery recovery.img
*Wipe Davilk and cache
Flash custom rom
*Wipe Davilk and cache
Flash OpenGapps
*Wipe Davilk and cache
Flash NoVerity
Flash Magisk
*Wipe Davilk and cache
Boot OS (finally )
I also attach some tests done with GFBench (the hardware does not seem to have problems)
Thank you, very much.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I could not understand what the problem was; anyway and for now, I solved installing the ROM stock without Magisk (among other things, I had tried different versions: 17 / 17.2 / 17.3 / 18 ... I have always had problems).
You made this way too complicated. Download the newest beta on to phone. Get total commander from play store, use it to enter(not extract) the firmware zip and delete the compatibility zip inside. Ensure magisk is on your device. Boot to twrp. Wipe EVERYTHING except internal. Now flash newest one beta, once it finishes flash magisk. It might fail. Just try again and it will work. Reboot. Now you are on pie with magisk and kept twrp. Also magisk is no verity. But you should flash decrypt before first boot if you are gonna go in and play with stuff.
Thanks, but I did that procedure just to figure out what the problem was. Magisk gave me several problems, in the meantime I try for a few days ... then I'll try.
Merry Christmas
mascian said:
Thanks, but I did that procedure just to figure out what the problem was. Magisk gave me several problems, in the meantime I try for a few days ... then I'll try.
Merry Christmas
Click to expand...
Click to collapse
OB23 with magisk 17.1 is working fine for me.
strongst said:
OB23 with magisk 17.1 is working fine for me.
Click to expand...
Click to collapse
LOL... that version is the only one I have not tried ??
Related
Hi, I don't exactly know since when it's showing wrong, but I believe it has to do something with my latest "activities".
First here my storage of my 16 GB N4 device:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Okay, I decided to fully wipe my device and go back to stock 4.2.2 before flashing latest AOKP PUB rom.
Therefore I went into fastboot and used following commands to erase old data
fastboot erase cache
fastboot erase boot
fastboot erase userdata
fastboot erase system
fastboot erase recovery
Then I started with stock factory image 4.2.2 (JDQ39)
Flashed userdata, boot, system and a customrecovery (TWRP 2.4.2.0)
Rebooted phone, downloaded supersu 1.10 zip, AOKP PUB rom, and Trinity Kernel (TF107)
Booted into recovery --> wiped cache/dalvik cache --> factory reset --> flashed AOKP and TF107 --> rebooted --> set up wifi etc
Booted into recovery --> flashed supersu --> rebooted installed busybox --> rebooted into recovery and fixed permissions.
Now I was starting to set up everything like my apps etc. until I noticed my storage is too small.
What is the problem and what can I do to get my storage back?
The only unusal thing which I never did before, was the erasing stuff, could this be the problem?
Thanks!
Hi,
I think you should take a look here: [url=" http://forum.xda-developers.com/showthread.php?p=35119185'' ]
[HOW-TO] Fix internal storage if 16GB now shows 8GB[/url]
Restart from scratch... Weird it's what you done apparently...
viking37 said:
Hi,
I think you should take a look here:
[HOW-TO] Fix internal storage if 16GB now shows 8GB
Restart from scratch... Weird it's what you done apparently...
Click to expand...
Click to collapse
okay thanks, started from scratch again and with all stock it's working now.
I'll try to flash my custom recovery, rom and kernel again and hopefully it works this time.
laba86 said:
okay thanks, started from scratch again and with all stock it's working now.
I'll try to flash my custom recovery, rom and kernel again and hopefully it works this time.
Click to expand...
Click to collapse
Same thing happened to me. A total pain in the ass...
Sent from my Nexus 4 using xda premium
All I did was back up my sdcard, boot into recovery, format the sdcard, then copy everything back on to it.
Worked for me.
Anyone have a XT1575 7/19/2016 update TWRP package?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please post if you do, my rooted phone now enters boot-loop because I accidentally hit "Yes, I am in"....
Thanks in advance!!!
I had the boot loop too. Went to twrp and wiped dalvik and cache and no more boot loop.
captainmalcolm said:
I had the boot loop too. Went to twrp and wiped dalvik and cache and no more boot loop.
Click to expand...
Click to collapse
Do you still have root, etc.?
captainmalcolm said:
I had the boot loop too. Went to twrp and wiped dalvik and cache and no more boot loop.
Click to expand...
Click to collapse
HeatR216 said:
Do you still have root, etc.?
Click to expand...
Click to collapse
Yes i would like to know! I would love to be able to run the OTA update without causing issues, and if all i have to do is wipe dalvik n cache on boot after the OTA update that would be awesome!
Sorry should have been more clear, the update does not work. Wrong signing keys. It sends the system into a boot loop. You boot back into the O's but after about 30 seconds it begins applying the update again and send you into twrp and updates fails, reboot, wait 30 apply again twrp, etc. Etc. The way I got out of the loop was wiping dalvik and cache and now I can use the phone again without boot loop. We need to wait until someone creates a twrp zip for the update.
Mine is full wipe >> flash stock 24.49-18-3 >> update 24.49-18-4 via OTA then flash Su 2.62-3 >> Done.
captainmalcolm said:
Sorry should have been more clear, the update does not work. Wrong signing keys. It sends the system into a boot loop. You boot back into the O's but after about 30 seconds it begins applying the update again and send you into twrp and updates fails, reboot, wait 30 apply again twrp, etc. Etc. The way I got out of the loop was wiping dalvik and cache and now I can use the phone again without boot loop. We need to wait until someone creates a twrp zip for the update.
Click to expand...
Click to collapse
I still dont get you, first you say the update does not work, then you said it worked after you cleared dalvik and cache in twrp after it had been applied making it work?
Not TWRP flashable, but someone posted the full firmware here.
I could not get the OTA to go on my phone, kept failing.
I just fastboot flashed everything in that zip according to the flash script that came with the zip except recovery and didn't wipe userdata. Booted into new system to confirm everything was ok, then TWRP flashed systemless supersu and Frankenclark. All is good. Not as simple as TWRP flashable, but way less disruptive than restoring to bare bones stock to take an OTA.
How long does it usually take on a new twrp zip?
oh someone please get this going! i hate this annoying update notification every day! twrp zip would be awesome!
nd4spdbh said:
oh someone please get this going! i hate this annoying update notification every day! twrp zip would be awesome!
Click to expand...
Click to collapse
yep. just waiting for twrp zip.
I have a problem flashing LineageOs and other zip ROMs on my galaxy S5, TWRP 3.1.0-1; I also tried CWM and a previous versionof TWRP. I can instead install stock firmware with Odin. Before wiping cache, dada, system, dalvik I flash the rom from SD card but the progress bar remain stuck and nothing happen, have to remove the battery to boot the phone in recovery again.
now when booting to recovery it returns this error: Failed to mount '/system' (Invalid argument).
how do I do to solve and install Lineage?
remus1101 said:
I have a problem flashing LineageOs and other zip ROMs on my galaxy S5, TWRP 3.1.0-1; I also tried CWM and a previous versionof TWRP. I can instead install stock firmware with Odin. Before wiping cache, dada, system, dalvik I flash the rom from SD card but the progress bar remain stuck and nothing happen, have to remove the battery to boot the phone in recovery again.
now when booting to recovery it returns this error: Failed to mount '/system' (Invalid argument).
how do I do to solve and install Lineage?
Click to expand...
Click to collapse
I've had problems with Aroma installers and TWRP abode the last 2.x.
Regarding system, try to format it via TWRP.
I know there are issues with Aroma installer. LineageOs does not require it so I think this is not the problem. Anyway I used TWRP 2.3 but I have the same problem. Installing process does not success.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Inviato dal mio SM-G900F utilizzando Tapatalk
remus1101 said:
I have a problem flashing LineageOs and other zip ROMs on my galaxy S5, TWRP 3.1.0-1; I also tried CWM and a previous versionof TWRP. I can instead install stock firmware with Odin. Before wiping cache, dada, system, dalvik I flash the rom from SD card but the progress bar remain stuck and nothing happen, have to remove the battery to boot the phone in recovery again.
now when booting to recovery it returns this error: Failed to mount '/system' (Invalid argument).
how do I do to solve and install Lineage?
Click to expand...
Click to collapse
TWRP getting a fail on mounting the system partition is strange. So I suggest you re-flash a stock samsung rom first and make sure it is working properly. Meaning it boots up ok and does not hang / freeze whatever during a good few minutes of use (maybe 15 min or so).
Then I would flash the img.tar of TWRP 3.0.2-0 from here. That is the version I use. It works just fine (with aroma too). Reboot to recovery and go from there.
Thanks for your response.
After a system wipe the mounting fail is gone.
I already flashed the stock ROM with Odin and it works fine. Then trying to install lineage from recovery (making the for wipes) I got the same results.
So I decided to flash a ported ROM (that uses Aroma installer) and installation was fully functional.
So I think this problem shows up only with LineageOs and also RR.
Is it possible that there are still some files from a previous installation of LO that cause a conflict and make the installation just not to continue?[emoji28]
Hey everyone,
So I have been using Oreo beta B12 on my A2017U for a few weeks and wanted to check out Lineage and after having some qualms about Oreo and stability, decided to go for Lineage 14.1.
Using TWRP I wiped (standard wipe) and flashed the bootloader, modem, lineage, gapps, and Magisk. In that order. Upon finish and reboot it tells me, Decryption unsuccessful, I must reset my phone. But when it goes to wipe it fails, i see the following:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It seems to be stuck like this, and I don't know what to do to proceed. I could try some things, but I don't want it to get worse because I wiped something crucial.
Thanks in advance.
Tre916 said:
Hey everyone,
So I have been using Oreo beta B12 on my A2017U for a few weeks and wanted to check out Lineage and after having some qualms about Oreo and stability, decided to go for Lineage 14.1.
Using TWRP I wiped (standard wipe) and flashed the bootloader, modem, lineage, gapps, and Magisk. In that order. Upon finish and reboot it tells me, Decryption unsuccessful, I must reset my phone. But when it goes to wipe it fails, i see the following:
It seems to be stuck like this, and I don't know what to do to proceed. I could try some things, but I don't want it to get worse because I wiped something crucial.
Thanks in advance.
Click to expand...
Click to collapse
Flash B12 Beta again and flash 3.2.1-8 and decrypt data (format data )with 3.2.1-8 and flash LOS14.1( bootloader.modem,los,twrp 3.2.2-0 ) you must install twrp before reboot system.
atakan33 said:
Flash B12 Beta again and flash 3.2.1-8 and decrypt data (format data )with 3.2.1-8 and flash LOS14.1( bootloader.modem,los,twrp 3.2.2-0 ) you must install twrp before reboot system.
Click to expand...
Click to collapse
Thanks, that worked. I appreciate your help!
atakan33 said:
Flash B12 Beta again and flash 3.2.1-8 and decrypt data (format data )with 3.2.1-8 and flash LOS14.1( bootloader.modem,los,twrp 3.2.2-0 ) you must install twrp before reboot system.
Click to expand...
Click to collapse
So, would you mind explaining what actually went wrong? Did I just fail to decrypt/format the data before imaging? Should I just be sure to format /data every time I flash a new rom?
Tre916 said:
So, would you mind explaining what actually went wrong? Did I just fail to decrypt/format the data before imaging? Should I just be sure to format /data every time I flash a new rom?
Click to expand...
Click to collapse
in oreo you must decrypt data with 3.2.1-8 thats it ( if you are encrypted )
I'm currently on RR Nougat (7.1.2) and I want to upgrade to the official OOS 9.0.0.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Recovery: blu_spark TWRP
Storage:Encrypted
What's my way to go?
Wipe everything, flash the official zip and done?
uhlme said:
I'm currently on RR Nougat (7.1.2) and I want to upgrade to the official OOS 9.0.0.
Recovery: blu_spark TWRP
Storage:Encrypted
What's my way to go?
Wipe everything, flash the official zip and done?
Click to expand...
Click to collapse
Backup everything off your device including internal storage.
You need to wipe everything and flash official OxygenOS 5.1.4 and then 5.1.7 with additional format of internal storage and then follow the instructions for clean flash here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040
Don't update your twrp recovery to the newest before you are on OxygenOS 9.0.1!
strongst said:
Backup everything off your device including internal storage.
You need to wipe everything and flash official OxygenOS 5.1.4 and then 5.1.7 with additional format of internal storage and then follow the instructions for clean flash here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040
Don't update your twrp recovery to the newest before you are on OxygenOS 9.0.1!
Click to expand...
Click to collapse
With "wipe everything" you also mean internal storage including data? Do I need to disable/uninstall Magisk before wiping? I reckon it doesn't matter if I'm wiping everything anyway.
uhlme said:
With "wipe everything" you also mean internal storage including data? Do I need to disable/uninstall Magisk before wiping? I reckon it doesn't matter if I'm wiping everything anyway.
Click to expand...
Click to collapse
Exactly, but internal storage wipe is obsolete cause you FORMAT internal storage afterwards, so wiping system, data and cache is enough.
Uninstall magisk is also not necessary if you wipe partitions mentioned above