H918 - Mass Process Crashes at Welcome Screen - LG V20 Questions & Answers

I have a rooted H918 (T-Mobile) and decided to finally update it to Oreo. After flashing, wipe cache, etc. and then rebooting, I get the "Welcome" screen where I would normally start setting up the phone. Unfortunately, the phone is unusable due to an endless loop of processes stopping popups.
There is an utter barrage of "Unfortunately, the process X has stopped" where X is any one of the following processes...
com.android.phone
Multi-line Service
Second screen
Google Services Framework
T-Mobile Name ID
Tapping on "Close app" just brings up another message.
I've tried reflashing to a fresh 10u but the same crashes happen. I've wiped/formatted data/reflashed all with the same results. I even tried older versions of TWRP to see if that made a difference in the flashing process. Nope.
I'm at a loss and welcome any assistance.

Ok, Install twrp and then wipe the partitions
system, vendor, data and wipe the caches.
Put in flash mode and flash stock rom again
Should work

Akhil99 said:
Ok, Install twrp and then wipe the partitions
system, vendor, data and wipe the caches.
Put in flash mode and flash stock rom again
Should work
Click to expand...
Click to collapse
Yup...done that with both 10u and 20h with the same results.
I have been copying the ROMs to my SD card and flashing from within TWRP. When you say "put it in flash mode and flash stock rom" are suggesting reflashing the firmware outside of TWRP?

Related

[Q] Bootloop after failed rom install

So i was switching from M.O.A.R. and trying to install Allience on my SM-G900P, I backed MOAR in TWRP, did factory reset, wiped cache and dalvik, then tried to flash Allience, it failed, then when i reboot, it is back to stock loading screen, which afdter a few seconds it reboots and does it all over again. I can restore boot and recovery, but it fails toward the end of restoring system 'after 'formatting system using make_ext4fs function' it says restore complete, but then it also says 'failed' in red right below that.
Also on boot it says ;'kernal is not SEANDROID enforcing' and 'set warranty bit: kernal'
I can access both downloader and twrp, just dont know what to do from here...
Thanks
Ki11ian said:
So i was switching from M.O.A.R. and trying to install Allience on my SM-G900P, I backed MOAR in TWRP, did factory reset, wiped cache and dalvik, then tried to flash Allience, it failed, then when i reboot, it is back to stock loading screen, which afdter a few seconds it reboots and does it all over again. I can restore boot and recovery, but it fails toward the end of restoring system 'after 'formatting system using make_ext4fs function' it says restore complete, but then it also says 'failed' in red right below that.
Also on boot it says ;'kernal is not SEANDROID enforcing' and 'set warranty bit: kernal'
I can access both downloader and twrp, just dont know what to do from here...
Thanks
Click to expand...
Click to collapse
Well crap, i just needed to mount my internal storage instead of sd card. I then allowed me to flash MOAR back on. Does anyone know of a more feature filled rom for the P Varient then what I am using? I really liked the features of phoenix and allience, but mine is not supported...
Ki11ian said:
So i was switching from M.O.A.R. and trying to install Allience on my SM-G900P, I backed MOAR in TWRP, did factory reset, wiped cache and dalvik, then tried to flash Allience, it failed, then when i reboot, it is back to stock loading screen, which afdter a few seconds it reboots and does it all over again. I can restore boot and recovery, but it fails toward the end of restoring system 'after 'formatting system using make_ext4fs function' it says restore complete, but then it also says 'failed' in red right below that.
Also on boot it says ;'kernal is not SEANDROID enforcing' and 'set warranty bit: kernal'
I can access both downloader and twrp, just dont know what to do from here...
Thanks
Click to expand...
Click to collapse
First of all, you have to flash Alliance over the Rom Customizer (Goldie clearly describes in the instruction).
Well, knox 0x1... tripped by custom kernel probably from Alliance...no return, you have to live with it. TWRP trips as well.
Personally, I like CMW more.
I guess, you can enter to TWRP/CMW...
Have you been trying to reflash the box with another kernel, compatible with your model (I don't know the 900P version, I work with F)?
Full wipe etc.
One time, I was facing the problem (I'm not sure, if it was CMW/TWRP) with the wrong version of it.
I had change the stuff to another one, then I was able to flash the ROM properly. The download mode helps...
You should have reverted to a stock ROM before moving to a different custom ROM. Transitioning between custom ROMs can have unexpected results as you found out.
I agree with the poster above in that it sounds like you missed some steps in installing the Alliance ROM as well. Although I strongly prefer TWRP over CWM. The Phoenix ROM says up front that it is configured for the 900F. But reports are that everything works on the 900P except perhaps data and the stock SMS app. You could probably resolve the data issue if you put your mind to it.
.
.
Isn`t it for flashing a rom enough if you :
- data factory reset
- wipe cache and dalvik cache
- format system
- flash the rom
- data factory reset
- reboot.
Just saying, haven`t flashed a custom rom yet on the S5 so not 100% sure.

Restored Backup not booting properly? "#### has stopped"

Guys,
I have an S5 running Cyanogen Lollipop and Philz Touch 6.26.2 as the recovery. I was experimenting with flashing a new camera .ZIP earlier today but BEFORE doing so I used Philz to create a backup. The flash of the .zip for the camera went wrong and ended up prompting the phone to hang on boot.
I booted into Recovery and restored my backup...restarted the phone and it then booted as normal BUT as soon as Android had booted, it was unusable as I just kept getting the "##### has stopped" error messages, one after the next - the launcher doesn't appear and the phone is completely unusable.
I have tried a 'Factory Reset' and wiping the Dalvik cache, on boot it optimises all apps but then does precisely the same.
Please help as I'm travelling tomorrow and need to sort this tonight!!
Cheers
sergeantash said:
Guys,
I have an S5 running Cyanogen Lollipop and Philz Touch 6.26.2 as the recovery. I was experimenting with flashing a new camera .ZIP earlier today but BEFORE doing so I used Philz to create a backup. The flash of the .zip for the camera went wrong and ended up prompting the phone to hang on boot.
I booted into Recovery and restored my backup...restarted the phone and it then booted as normal BUT as soon as Android had booted, it was unusable as I just kept getting the "##### has stopped" error messages, one after the next - the launcher doesn't appear and the phone is completely unusable.
I have tried a 'Factory Reset' and wiping the Dalvik cache, on boot it optimises all apps but then does precisely the same.
Please help as I'm travelling tomorrow and need to sort this tonight!!
Cheers
Click to expand...
Click to collapse
Backup restore also system apps and sometimes there are problems. I think you must flash the rom without backup.
davyleggend said:
Backup restore also system apps and sometimes there are problems. I think you must flash the rom without backup.
Click to expand...
Click to collapse
Ok, this has given me an idea - I have flashed fresh Cyanogen and now I'm attempting to restore just the 'data' and 'cache' elements of my backup by using the Philz 'Custom Restore' feature...fingers crossed!
So, my idea worked...my phone is now back up and running, what a relief!

Cannot wipe with TWRP

Hi,
I have G935F, installed TWRP 3.0.0.0 and rooted, WITHOUT wiping. System boots correctly, but I cannot do factory reset or wipe with TWRP, because I got some messages like "Cannot mount Data" and "Failed crypto loader". I understand that it has to do with encryption. Can someone please enlight me, and give me tips about the issue?
Thank you
Polemos82 said:
Hi,
I have G935F, installed TWRP 3.0.0.0 and rooted, WITHOUT wiping. System boots correctly, but I cannot do factory reset or wipe with TWRP, because I got some messages like "Cannot mount Data" and "Failed crypto loader". I understand that it has to do with encryption. Can someone please enlight me, and give me tips about the issue?
Thank you
Click to expand...
Click to collapse
You have to download dm-verity and force encryption disabler from here , put it to SD card, reboot into TWRP, FORMAT DATA (not wipe) and flash that file (dm-verity and force encryption disabler). All your data will be erased.
No way to unencrypt without loosing you data for the moment(
"All your data will be erased" means that after boot I'll find a clean system installation (as factory reset)?
I hope not to be posing stupid questions, I'm completely new to this world
Thank you very much
Yes just as a factory reset
Sent from my SM-G935W8 using Tapatalk
Ok, thank you all!!! ???
s it very important to wipe data?
Can I first flash the twrp ,second back up the rom by TWRP recovery
and then after factory reset ,I restore thw rom by twrp??
IS IT possible?
AGU PENG said:
Can I first flash the twrp ,second back up the rom by TWRP recovery
and then after factory reset ,I restore thw rom by twrp??
IS IT possible?
Click to expand...
Click to collapse
No, you cannot perform a backup, because your data is encrypted by default and the only way to disable it is to format your data.
I have a unique problem. I have a HTC Desire 612 from Verizon and I decided to revive it to playe PoGo. But it was stuck in a boot loop and I couldn't get any custom ROM.
Finally a gentle soul here gave me the stock rom and I flashed it vide TWRP and played PoGo for weeks. Then yesterday the phone bro led and when it came up it was stuck in a boot loop.
So I decided to flash the stock ROM again. But before that I tried to factory reset. I could go to TWRP, select wipe data, enter yes and the wiping was successful, then clear dalvic and cache and system beforehand finally I flashed the stock ROM.
Surprise surprise is NOTHING happens. The phone boots without the apps telling me they are installing. Then I get back the exact same data in my phone including my selected wallpaper and apps. Before I can do anything the phone restarts.
Point is wiping and restoring the stock ROM does NOTHING to the phone yet the processes are successful. Can somebody help?
vooks said:
I have a unique problem. I have a HTC Desire 612 from Verizon and I decided to revive it to playe PoGo. But it was stuck in a boot loop and I couldn't get any custom ROM.
Finally a gentle soul here gave me the stock rom and I flashed it vide TWRP and played PoGo for weeks. Then yesterday the phone bro led and when it came up it was stuck in a boot loop.
So I decided to flash the stock ROM again. But before that I tried to factory reset. I could go to TWRP, select wipe data, enter yes and the wiping was successful, then clear dalvic and cache and system beforehand finally I flashed the stock ROM.
Surprise surprise is NOTHING happens. The phone boots without the apps telling me they are installing. Then I get back the exact same data in my phone including my selected wallpaper and apps. Before I can do anything the phone restarts.
Point is wiping and restoring the stock ROM does NOTHING to the phone yet the processes are successful. Can somebody help?
Click to expand...
Click to collapse
HTC?? Wrong thread.
B3311 said:
HTC?? Wrong thread.
Click to expand...
Click to collapse
It really is about TWRP failing to wipe

Cleared cache, now phone doesn't boot and goes to recovery

A friend just cleared cache and dalvik cache from TWRP on his OP5 and now when the phone turns on, it shows the spinning OOS boot screen and after about 30 seconds it starts the recovery.
We tried flashing the ROM again but it didn't change a thing. We tried flashing it from the stock recovery but clicking "Install from internal storage" didn't work and ADB sideloading is not possible.
I'm running out of ideas.
Try doing adb sideload from linux instead of windows. You can also choose to load the rom from a pendrive using otg.
just flash twrp again, flash oos, boot. might ask for a password, at that point you will restart back to recovery (will be oos recovery now) and just select you dont know the password and it will wipe your phone and then turn on. then go back and reinstall twrp again.
my guess is he accidentally clicked clear system, clearing cache doesnt break anything. clearing system on oos breaks it and you have to start fresh. that or install a custom rom.... but oos is better, so id spend the time and just do it right.

Sanity Check on Flashing Stock 5.1.4

Ok, so I am not new to flashing rom but for some reason I am having huge issues trying to install clean stock OOS 5.1.4 rom. Just want to double check I am not doing anything stupid since I mainly been flashing custom roms (xXx rom mainly).
So I simply wipe dalvik/ART cache, cache, system and data (want to start off completely clan) then flashed the OnePlus5Oxygen_23_OTA_037_all_1807181258_7b4b6.zip file in TWRP.
I am currently on the latest blue TWRP and after flashing, it will try to boot but reboots back into TWRP. I have tried the zip file from a number of sources and they all do the same. Am I missing something here?
UPDATE: I did do something stupid after all. I forgot that my Oneplus was decrypted. So all I had to do was go into TWRP and go to Wipe and format data to re-encrypt it.
Z-Blade said:
Ok, so I am not new to flashing rom but for some reason I am having huge issues trying to install clean stock OOS 5.1.4 rom. Just want to double check I am not doing anything stupid since I mainly been flashing custom roms (xXx rom mainly).
So I simply wipe dalvik/ART cache, cache, system and data (want to start off completely clan) then flashed the OnePlus5Oxygen_23_OTA_037_all_1807181258_7b4b6.zip file in TWRP.
I am currently on the latest blue TWRP and after flashing, it will try to boot but reboots back into TWRP. I have tried the zip file from a number of sources and they all do the same. Am I missing something here?
Click to expand...
Click to collapse
When starting fresh, wiping of internal storage should be considered. I recommended 2 guides here https://forum.xda-developers.com/on...nos-beta-1-android-oreo-t3710003/post77205633

Categories

Resources