I live in Taiwan and order my oneplus3 from China, but not from the official seller
Jindong or oneplus site but form 3rd party seller on Taobo, which is in Shenzhen.
Thay have sold hundreds of oneplus3 and have most high praise in Taobo- Shenzhen
My oneplus3 take over 7 days shipping to my hand.
While I 1st unbox my oneplus on 9/6 , it has already bootloader unlock and TWRP 3.2.0 installed. As you know, the 3 party seller sold me the used device, but it's not fake, it has full package and correct IMEI with it, I also cheked IMEI on oneplus official site.
I have no choice but jut to accept a used device with new-one price.
I immediately update to official TWRP 3.2.1 and install freedomOs CB 1.6, XPOSED, rooted, everything looks fine.
But after 4 days uesd, while I change system font with ifont and it won't boot to system, jut stuck at 1+ boot screen, after
a dozen of secnods , automatically boot into TWRP , it even can't boot into TWRP , just hang on TWRP logo,
Fastboot flash other version of TWRP, still can't boot into both system and TWRP.
After fastboot flash stock recovery, it can boot into recovery, and then flash TWRP -> boot in TWRP. But still can't mount system/data/cache, some boots even unable to mount internal storage.
(While on stock recovery, ADB sideload OTA.zip from official site always stuck at 47%)
Fastboot erase usersdata and TWRP format still don't work, no lucky, can't mount system/data/cache.
I ask my colleague hand carry my oneplus3 during his business trip, return it to the 3rd party seller. The 3rd party seller only took 3 days to ship to oneplus to fix it and return to them, and .. return to my colleague.
While my colleague got the phone, it work fine with bootloader lock, Chinese H2 OS for more then one week.=>( So that it's not the hardware issue, not internal SD Corrupt?)
I ask he to test it as he can, after 2weeks. He come to Taiwan and bring it to me. He dose not find any problem with daily use on bootloader locked H2 OS.
When I got the "return" oneplus 3 ,
fastboot unlock booloader->
Decrypt follow this: Decrypt OxygenOS without losing data
i also see this:SOLVED][TWRP]Unable to Decrypt Storage
I think is might be CB rom Unstable and encryption issue.
So I install FreedomOS 1.6 and decrypt data this time.
But guess what happen!?
It have happen again and again more then 5 times -
no flash anything, no reboot, just in system used-> got lag->got black screen-> got reboot->unable to reboot system-> unable to mount/wipe/restore data/system/cache in official TWRP.
The only solution seems to "fastboot format users data" , then I can mount/restore/format data/cache/system , till now, i am confused, I don't know if its software or hardware issue, I just spent too many hours on it!
Please help, any advise is welcome...and.. sorry for my English, tried my best.
This issue is really weird.
Can you share the logs given by TWRP, with the kernel log of your twrp recovery.
To do:
Code:
adb shell
dmesg > /tmp/dmesg.log
exit
adb pull /tmp/recovery.log <path_on_your_computer>
adb pull /tmp/dmesg.log <path_on_your_computer>
All theses things needs to be done directly in twrp, adb is needed.
If you want to boot into system after decrypting it, you have to flash supersu, otherwise OOS will encrypt itself at next boot, causing a brick. Also try the modded version of twrp.
NevaX1 said:
This issue is really weird.
Can you share the logs given by TWRP, with the kernel log of your twrp recovery.
To do:
Code:
adb shell
dmesg > /tmp/dmesg.log
exit
adb pull /tmp/recovery.log <path_on_your_computer>
adb pull /tmp/dmesg.log <path_on_your_computer>
All theses things needs to be done directly in twrp, adb is needed.
Click to expand...
Click to collapse
Dear Sir,
Done it Immediately, thank you!!
ArisLi said:
Dear Sir,
Done it Immediately, thank you!!
Click to expand...
Click to collapse
I can't see any errors here, can you try to capture the log after you get the same error in your twrp.
NevaX1 said:
I can't see any errors here, can you try to capture the log after you get the same error in your twrp.
Click to expand...
Click to collapse
Sure, I believe it will happen during this weekend or on Monday.
aadityarulez said:
If you want to boot into system after decrypting it, you have to flash supersu, otherwise OOS will encrypt itself at next boot, causing a brick. Also try the modded version of twrp.
Click to expand...
Click to collapse
For more information: I didn't try to decrypt data before my oneplus3 return to China, I did decrypt it after it return form China, and I only flash freedom OS 1.6 with systemless SU t and stock (patch) kernel, than flash EX kernel, i believe both of them is patched, disable force decrypting.
My decrypt sequence: Unlock bootloader->fastboot format users data-> flash freedom1.6 with systemlessSU let it boot without configuration ->work fine for 3 days and brick after 4 days used with serval times of booting.(less then 5 times)
Every time before my oneplus3 get this type of in-system-used-brick, I see some root access issue or permission issue, that is V4A driver lost, I have no permission to move my files in media storage( for example, move some files from download folder to XpoasedInstaller folder), or Dolby atom crash....
The latest brick, I used my phone on bed for more than 2 hours with no issue, suddenly Dolby ATOM crash, unable to open it and V4a lost its driver, then I try to boot into TWRP to make a boot/system/data backup, but it fail to mount data and system partition.
Even on system-mode SU, It still happen two times of in system brick.
So now i set SELunx permission and do frequently TWRP and Ti-back, I believe It would brick again few days later. At least after many times of Try/error, I can confirm "format uesers data then I can use TWRP for system/data partition.
NevaX1 said:
I can't see any errors here, can you try to capture the log after you get the same error in your twrp.
Click to expand...
Click to collapse
It happen again while this morning I get up and updating two apps,
It freeze then reboot to recovery, unable to mount system/data again.
I have the latest nandroid data/system/boot backup last night, i believe it finally would be brick again.
Here is the log.
I will keep it in the state, please help, I won't "fastboot format usersdata" this time, till we know the cause, and have your instruction.
EDIT： upload the video, you can see it unable to boot in sysytm, in TWRP can't mount system/data/cache , unable to back/restore/install anything
https://youtu.be/KM4gX16sEHQ
What happened when you went completely stock?
aadityarulez said:
What happened when you went completely stock?
Click to expand...
Click to collapse
My friend test with completely stock/ bootloader lock for more one week in Chian (oneplus
service Centre in Shenzhen recoverey it ), every thing is fine just without google service.
Yesterday,I just re-flash freedom 1.6.1 on cleanest status, fastboot formate userdata-> TWRP format (without this both nandroid or new flas rom won't boot up)-- BOOT
After two days used, every things is fine, but just half hours ago my phone brick with all cache/system/data partition encryption while I am in system uesing , I will report detail at night while I have time, i believe I have found the root cause.
Follow this guide
http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-decryption-ultimate-guide-t3497940
Hello everyone,
i found something, at least for me interesting, while formating my OnePlus 3 via fastboot.
I used fastboot format for userdata, system, cache and saw little message on my terminal:
"Couldn't parse erase-block-size '0x'."
"Couldn't parse logical-block-size '0x'."
I'm kinda interested what this means and why these two lines appeared.
What i've done before formating:
I used Paranoid Android 7.3.1 and Arter's TWRP 3.1.1.0 (fastboot image) for F2FS data and cache partition. I wanted to revert back to ext4, installed Stock Recovery, sideloaded the OOS 4.5.1 OTA and locked bootloader again, because i thought i should give OOS another try... For one day. I unlocked the bootloader again, flashed latest TWRP (3.2.1.0) and Magisk 15.2. To get rid of OOS encrytion i followed the steps mentioned in the Paranoid Android Thread, then noticed the two lines i mentioned above.
A nice person at the Paranoid Android Group on Telegram told me i should load up the official TWRP format data, change data partition to ext4 and back to F2FS, which is what i've done. I was interested if the message is gone, so formated again via fastboot, but it wasn't. So again: Repeated the TWRP steps, wiped, flashed AOSPA and OpenGapps. That's the chase for now.
Like i said, i am interested what this means and why it appears, but also if i should be worried.
I have OnePlus 3 with OxygenOS 5, unencrypted and rooted with Magisk. In recovery, TWRP cannot access /sdcard. With ADB, when I try to get a shell into /sdcard, I get "I/O Error". When I system boot, it goes into bootloop half the time.
Except those two problems, I get random reboots, almost five per day. I have those problems since a few days, and I did not do any updates at this time.
When I succeed to boot, I am able to access my data in /sdcard.
I had a few problems with my LCD screen that was not responding, but the problem disappeared by itself.
Any idea what I can do? Could it be weirdly related to my previous touch screen problem? Thanks!
Dear XDA-Developers, after installing August 2020 update for my Pixel 2 XL and possibly applying incorrect Magisk bootloader version, my phone doesn't boot anymore and is constantly stuck in bootscreen animation.
What I have tried so far to no result:
- Re-flashing both May 2020 (previous working version) and August 2020 without -w flag to preserve my data that I would ideally like to recover.
- Side-loading May 2020 and August 2020 OTA versions through TWRP
- Creating and booting from Magisk-core only image as per guide called "How to Create & Boot from a Magisk Core-Only Image to Fix a Bootloop Without Custom Recovery" (since I cannot post links in here).
While unpacking and repacking Magisk-core image I noticed that "BOARD_OS_PATCH_LEVEL 2020-05" indicating that I might have had the wrong version applied to it.
So looks like my only hope is finding magisk_patched.img file for August 2020 Pixel 2 XL (image-taimen-qq3a.200805.001) and trying to patch it to disable Magisk upon startup. Would anybody be so kind to post one here?
I have also tried to make data backup using TWRP, but it fails mounting /data partition and shows that it's 0 Mb.
Any other ideas to how to save the phone without wiping all the data would be greatly appreciated.
Thank you all very much for whatever suggestions you might have to help me!
hencrow said:
So looks like my only hope is finding magisk_patched.img file for August 2020 Pixel 2 XL (image-taimen-qq3a.200805.001) and trying to patch it to disable Magisk upon startup. Would anybody be so kind to post one here?
Click to expand...
Click to collapse
Magisk doesn't touch the bootloader, only modifying the boot image. Given your description of the issue, I don't believe Magisk to be the culprit here. Based upon personal experience, flashing a stock image using flash-all.bat, whether the -w flag is present or absent, totally removes Magisk as the stock boot image overwrites the modified version created by Magisk.
It's clear though that you have an issue, but how much of it is brought about by misconceptions and incorrect knowledge is unknown and at this point irrelevant. So what do you do now? Try backing up your data using the instructions here. But be prepared for the very real possibility that you have already lost all your data, and only a stock ROM install with the -w flag present will restore the device to working order.
Strephon Alkhalikoi said:
So what do you do now? Try backing up your data using the instructions URL. But be prepared for the very real possibility that you have already lost all your data, and only a stock ROM install with the -w flag present will restore the device to working order.
Click to expand...
Click to collapse
Thanks for getting back. I'm a little confused how can adb backup can work though if the only thing I can boot into is TWRP and even it fails to decrypt /data partition (it just shows "Could not mount /data and unable to find crypto footer" upon startup).
And with my very limited Android debugging experience wondering if things are really that hopeless that it's not possible to simply copy and decrypt user data partition or there aren't even any logs from failed Android boot attempts that can be looked at to at least diagnose the issue.
hencrow said:
Thanks for getting back. I'm a little confused how can adb backup can work though if the only thing I can boot into is TWRP and even it fails to decrypt /data partition (it just shows "Could not mount /data and unable to find crypto footer" upon startup).
And with my very limited Android debugging experience wondering if things are really that hopeless that it's not possible to simply copy and decrypt user data partition or there aren't even any logs from failed Android boot attempts that can be looked at to at least diagnose the issue.
Click to expand...
Click to collapse
It may not work, and in fact it probably won't, especially if TWRP can't mount the data partition. That's why I said you should be prepared for the very real possibility that you have lost all your data. As for getting logs to diagnose the issue, the only certain way to get a catlog is to record the logcat from the device on your PC as you boot it, via USB Debugging. Something that likely will not be of much help now, given what you have tried doing to resolve the issue.
At this point, in your position I would simply cut my losses and install a factory image and let it wipe the data. Once you are back up and running, you want to get into the habit of backing up app data. There are many apps that can do this, but regardless of the app used, backing up the app data to internal storage or to a location like Mega or Dropbox will make life easier if you ever encounter this again.
An update if anybody is wondering what happened - flashing Android 11 Beta 3 brought the phone back to life with all the data intact. All versions of Android 10 haven't even reached the booting stage where adbd was started and showed no logs.
Hey,
I am having a bootloop after a pretty normal Android usage. All I did was:
browsing Internet, moving some photos, deleting file, moving some videos to Shelter (workprofile)
using Instagram inside Shelter, uploading a video
then I rebooted (in order to update my shelter file directory), and I suddenly got a system message that my workprofile was locked and requested my security code, I entered it several times but the workprofile including all shelter apps and files stayed inaccessible, it would keep requesting the code
so I rebooted again and since then the phone gets stuck at the Redmi logo, then boots into twrp recovery
I am running crDroid 9.2 on a Redmi Note 8. I have been running that system for at least two months now, only minor issues (never a bootloop). I was not really messing with any system settings/files.
Booting into TWRP, I am not being asked for decryption of the data, so maybe the system is even corrupt on that level... What can I do
I am running latest twrp 3.7.0-12.1
Do you have any ideas of what could be the least invasive procedure to fix this bootloop (i.e. without losing any data)?
Thanks in advance!