Stuck on bootanimation after OB3 update | Data Loss - OnePlus 5 Questions & Answers

Hello,
I recently updated to OB3 update on Oneplus 5.
Phone stuck on bootanimation for 30 minutes. I restarted it, same result !
Went into stock recovery only to see all data gone , some random folders are showing (check attachments).
Immediately flashed TWRP.
I have not tried anything as of yet so as to preserve data.
I have access to ADB , recovery(blu_spark's TWRP) and fastboot.
Please tell me how to proceed and save the data.
Link https://imgur.com/kh4igMY
Pic :-
{
"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"
}

itzcoke13 said:
Install stock recovery, flash stable OOS 5.0 (using adb sideload) and wipe cache (this worked for me)
PD: Sorry for my English
Click to expand...
Click to collapse
What about this guide ??
GUIDE
Is it any good ? Seems to be doing very good for people out there.
My concern is guide says Stable N --> Stable O
I was on Open Beta.

Related

[Q] Unfortunately, LGSetupWizard has stopped

{
"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 always get this message when installing a ROM on my D805 (except the AOSP).
this message comes right back to the start of the initial configuration, and not leave it!
someone has gone through this?
OBS: can I install any ROM D802 I have this same message!
sorry for the google translator: (
how do you go to stock rom, is it purely stock or custom?
try factory reset lol. will lose all data.
wipe the app that fc data\caches.
in recovery fix permisions, only if you have a recovery on phone. if you do have update it
on aosp its not there.
Do you do clean installs
The only one that actually helped me out is deleting the lg setup*.apk from the flashable zip.
Yes I always got this when installing a new rom on d802. was really annoying and i had to uninstall the setupwizard.apk and odex from system/app. i returned my phone to stock original then rerooted and installed blackpearl and this has gone away however.
Thank you, excluding LGStartupwizard.apk had worked to install the ROM.

TMO D801 V20E Update

Hello all,
I have tried to make a flashable zip to where I do not have to flash the KDZ but also make it deodex'd, zipaligned, etc, etc...all that good stuff...but I have failed...
So now I'm reaching out for assistance...kernels are my forte...not so much ROM stuffs...
Here is a dump of the ROM from the KDZ...
https://mega.co.nz/#!JExxEKCZ!0-w1xfwB8TaOgo0S_43L6i2g03KmH3U2nJVr4TWd-TU
And here is a flashable zip for the baseband...It works with Cloudy G3...as that's what I'm currently using...
https://mega.co.nz/#!sEgnEQ6J!h1HzF8hELUJUwr0nxbuzCryPf-sURA2wpIF7KvvRORY
Any suggestions and help are welcomed!...there was a thread with a template but we do not have cust.bin...i tried some of those rom kitchens...but it doesn't account for lokifying boot.img...i've tried to update the updater-script...the furthest I've gotten was to the tmobile boot screen and then it stops there...I'm thinking it's the kernel...I've tried using my personal kernel from V20E source but i get the blinking lights but nothing else...
I'm stumped... *sigh*
It was easier to flash the KDZ > ran TowelRoot > installed SU > ran Autorec > rebooted...I did get the white lines...so I switched to my custom stock kernel...with the stock ramdisk...pushed that to my phone while in TWRP...time to freeze/remove the bloat...and set up xposed...
Cheers...
{
"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"
}
Sent from my LG-D801 using Tapatalk

vbmeta error after updating magisk

Hi,
I flashed my S10+ with Magisk a while ago and today I went into the Magisk manager and it showed that theres an update available, so I went ahead and updated it through direct install method (recommended).
Now my phone restarted and is stuck in download mode and shows this:-
{
"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 tell me how can i fix this without losing my data as I don't have any backup. Stupid, i know!
Thank you!
iamsyh said:
Hi,
I flashed my S10+ with Magisk a while ago and today I went into the Magisk manager and it showed that theres an update available, so I went ahead and updated it through direct install method (recommended).
Now my phone restarted and is stuck in download mode and shows this:-
Please tell me how can i fix this without losing my data as I don't have any backup. Stupid, i know!
Thank you!
Click to expand...
Click to collapse
Just to update anyone else having this issue, I flashed my phone with TWRP using ODIN and that seems to have fixed it!
I didn't have to reflash my firmware or lose my data using this

need help installing custom rom

im trying to install a custom rom on my mi 9t. its not the first time that ive done this, but now its all gone wrong. I have unlocked the device, flashed twrp, and got the rom/gapps ready to go, but when i go to install it i get 2 errors, "E:unhandled flag: wrappedkey" and "E:unable to decrypt fbe device". and just to make things worse, i came to the brilliant conclusion that the errors were from the old rom interferring with the new one that i was trying to install, so i deleted the system partition and wiped my os.
feel free to call me as many names as you like, so long as you also provide some help aswell haha.
thanks guys
{
"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"
}
If you have twrp I stalled, then you just need to factory reset in recovery, format partition, flash dmverity, flash ROM and optionally root. There is nothing you could do wrong if you choose proper ROM for your device - each ROM has instruction what you need for it to work properly

Question Slot A unbootable

Hi all, I am trying to get my Nothing update to 1.1.3, I did restore image in magisk -->(didn't press reboot), then download the OTA update --> (didn't press reboot as well), lastly I used the install to inactive slot(After OTA) --> (pressed reboot), so according to what I know my phone should now boot into partition A since I am currently in partition B. After reboot, I found my device is still in 1.1.2, my partition A is become unbootable. Anyone got an idea any approach I can do? Thankyou.
{
"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"
}
switch to partition that boots and do local update to 1.1.3
see how to install via Local System Update wizard
gwolfu said:
switch to partition that boots and do local update to 1.1.3
see how to install via Local System Update wizard
Click to expand...
Click to collapse
Oh can I do this if I am rooted?
layz1319 said:
Oh can I do this if I am rooted?
Click to expand...
Click to collapse
while in theory, yes, I would restore stock boot.img and do it then

Categories

Resources