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
Related
I'm currently running my OP3 on Resurrection Remix 5.7.4 (MM 6.01), the phone has the latest version of TWRP and I've flashed other ROMs in the past without any issue
RR has proven to be quite unstable for me, the system UI keeps crashing, which renders the phone unusable until after a reboot so I wanted to flash Freedom OS as that worked quite well for me previously. When I tried to flash the ROM in TWRP the ROM seemed to flash successfully but when I rebooted, only the boot logo showed and then the screen went black and the phone refused to respond at all for about two hours, after that exactly the same thing happened. I managed to boot into recovery and tried flashing a different ROM but the result was the same every time, the only way to get the phone to work normally was to flash RR again/restore from a Nandroid backup, either way, the result is the same, I'm stuck on an unstable ROM and I don't know why, the last time I flashed these ROMs they worked fine, I followed all of the instructions for flashing said ROMs to the letter, I have the latest version of TWRP, etc.
Also it seems TWRP can't mount /system, in TWRP under "mount", system is unchecked, I checked it and tried again but found that whenever I rebooted the phone or attempted to flash a new ROM, it would always uncheck itself and flashing the ROM would fail, however strangely flashing the same version of RR was always successful. Is this why the flashing keeps failing and does anyone know what the problem could be?
Thanks!
bronderb said:
Go into your bootloader and format system, cache, and userdata (This will wipe EVERYTHING so be sure to backup). Then latest official flash stock rom and reboot. This should fix it. If this helped hit thanks!
Click to expand...
Click to collapse
Bootloader? There is no option in the bootloader to delete everything as far as I can see, do you mean in recovery? And if I wipe everything off the phone, how do I get the stock ROM onto the phone to flash it? When you say wipe userdata do you mean wipe internal storage or am I misunderstanding and you're telling me to wipe the usual dalvik, cache and data as you would for a normal clean flash?
bronderb said:
No, go into fastboot and plug into pc. Open cmd and type "fastboot format userdata" "fastboot format cache" "fastboot format system"
Click to expand...
Click to collapse
Okay, thanks, and then what? Do I flash TWRP then push the stock ROM to the phone and flash that? And exactly how do I do that?
bronderb said:
You just go into twrp (no need to reflash) then adb sideload oxygen os
Click to expand...
Click to collapse
Thank you, I am now running OOS, hopefully everything else will go smoothly now, planning to go back to FOS again
I didn't even have to use the fastboot commands to format, just sideloading the OOS file wiped everything anyway
Turns out the issue isn't actually fixed, "system" still appears unchecked in TWRP. Could the fact that I didn't actually format everything first have made a difference, given everything was wiped in the process anyway?
Looks like I'm going to be living the sideloading life...
Edit: Sideloading freedom OS failed, ended up having to restore from my TWRP backup. I don't know what I'm going to do, my main reason for using custom ROMs is installing a black theme, and OOS doesn't support Layers or Substratum fully so I can't stay on that
Is the thing that says "mount system as read-only" enabled in the mounts menu? /System isn't ever mounted when TWRP starts, you have to manually mount it, but as long as the updater-script tells /system to mount, it will. However, if that option to make it read-only is enabled, then nothing will ever write to /system. Last resort is deleting the .twrps file from /sdcard/TWRP folder to remove current TWRP preferences and then when you boot into TWRP, that first screen has the swiper to allow modifications, and you'll swipe that
frickinjerms said:
Is the thing that says "mount system as read-only" enabled in the mounts menu? /System isn't ever mounted when TWRP starts, you have to manually mount it, but as long as the updater-script tells /system to mount, it will. However, if that option to make it read-only is enabled, then nothing will ever write to /system. Last resort is deleting the .twrps file from /sdcard/TWRP folder to remove current TWRP preferences and then when you boot into TWRP, that first screen has the swiper to allow modifications, and you'll swipe that
Click to expand...
Click to collapse
It isn't set to read only, I have tried updating and resetting TWRP but nothing has helped, in fact it's got worse, I managed to sideload OOS but my attempted install of FOS failed so I tried to restore from a backup and that also failed, something which didn't happen back when I was on RR.
evilkitty69 said:
It isn't set to read only, I have tried updating and resetting TWRP but nothing has helped, in fact it's got worse, I managed to sideload OOS but my attempted install of FOS failed so I tried to restore from a backup and that also failed, something which didn't happen back when I was on RR.
Click to expand...
Click to collapse
Which version of TWRP are you running? The official 3.1.0-0 is good for OOS and OOS based ROMs only. Try eng.stk's version.
Use the latest eng-stk twrp.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
In recovery go to Wipe > Format data (this will wipe ALL in youre phone).
It's youre Data in F2FS? If yes you must change it to ext4, in recovery Wipe > Change file system. Reboot recovery. Check if it's changed.
Reboot to Bootloader (Fastboot). From PC reflash recovery.
Now copy Oos rom to the phone memory. Flash rom. Reflash recovery (the rom will overwrite the recovery). Reboot to recovery to see if it works. If not do it again.
I sugest to NOT restore old data. This way you'll have all new in youre phone.
tnsmani said:
Which version of TWRP are you running? The official 3.1.0-0 is good for OOS and OOS based ROMs only. Try eng.stk's version.
Click to expand...
Click to collapse
I was running 3.0.2-2 when the issue started, I updated to 3.0.3 and 3.1.0-0 but nothing changed. Thanks for the suggestion, I will give it a try
null0seven said:
Use the latest eng-stk twrp.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
In recovery go to Wipe > Format data (this will wipe ALL in youre phone).
It's youre Data in F2FS? If yes you must change it to ext4, in recovery Wipe > Change file system. Reboot recovery. Check if it's changed.
Reboot to Bootloader (Fastboot). From PC reflash recovery.
Now copy Oos rom to the phone memory. Flash rom. Reflash recovery (the rom will overwrite the recovery). Reboot to recovery to see if it works. If not do it again.
I sugest to NOT restore old data. This way you'll have all new in youre phone.
Click to expand...
Click to collapse
Help! I attempted to do this and the process failed, I didn't manage to wipe data because "/data could not be mounted as device or resource is busy"
Edit: Device now has nothing but TWRP and fastboot, no OS, no ADB, no data, no internal storage
If you can reflash twrp from PC. If not reflash recovery from twrp recovery : Instal > Image > Select Recovery (you must have TWRP.img in youre phone memory )
I managed to get hold of a few factory images and attempted to flash system.img through fastboot, resulting error was
"target reported max download size of 536,870,912 bytes" (system image is 3080 MB)
"invalid sparse file format at header magi"
null0seven said:
If you can reflash twrp from PC. If not reflash recovery from twrp recovery : Instal > Image > Select Recovery (you must have TWRP.img in youre phone memory )
Click to expand...
Click to collapse
I reflashed the modified TWRP successfully. The second suggestion wouldn't have worked, given my phone has no internal storage
You can't see internal storage because of the recovery does not work write.
If you have a working recovery you can do all you want.
null0seven said:
You can't see internal storage because of the recovery does not work write.
If you have a working recovery you can do all you want.
Click to expand...
Click to collapse
The recovery was working at this point, the issue turned out to be the data partition, system was formatted to ext4 but I didn't realise data was in f2fs which caused the problem in the first place. I formatted to ext4 and everything worked, I was able to install paranoid android and everything worked...
...until I flashed the wrong firmware and now I've hard bricked it! I'm going to try the hard brick toolkit
Edit: After 12 hours of being an unresponsive brick, the phone suddenly booted, system doesn't work but it has recovery. Unfortunately I seem to be back to square one, if I try to flash something it appears to succeed but then the phone doesn't boot up into system
So I am now back to the original issue of system not mounting, in terminal if I type "mount /system" I get following error:
"mounting /dev/block/sde20 on /system failed: Device or resource is busy"
Anyone know how to solve this?
I formatted everything, reflashed recovery and tried to flash OOS, got following error:
Code:
[FONT="Courier New"]"This package is for OnePlus3 devices, this is a oneplus3t" (it isn't)
"Updater process ended with ERROR: 7
Error installing zip file /sdcard/OOS3.2.6.zip" [/FONT]
Issue was "solved" by flashing PA, GApps and the correct firmware
Hopefully that's the end of all this drama, thanks to everyone for their suggestions
Hi, I'm pretty new at rooting and I seem to have a similar error. I'm getting the "can't mount /system" error in TWRP. I am able to boot into OOS 4.1.3 and run the nandroid backup but, I keep getting the same error and am unable to select "system" when choosing the mount option in TWRP.
Do I need to have all partitions in f2fs? My system partition is in ext4. Is this what solved your issue?
It seems my phone is functional even with the error active but, I've been trying to get systemless SuperSU and MagiskHide working and I think that's what is preventing me from doing so.
Hi!
Does Magisk (including root, etc.) work flawlessly on a Pixel C with Android 8.1? Or is better to stay with 8.0 and wait a little bit?
Thanks in advance and kind regards,
star3141.
It works, initially it would force close but now seems stable. I used v14.5 beta.
On the other hand super su by chainfire does not work. Would flash but app missing. Downloading from play store and updating binaries through app causes boot loop.
v14.5 works perfectly here, no problems at all.
Hi!
Thanks for the replies. Maybe I will give it a try at Christmas or alternatively wait for the first update of 8.1 in January.
Hello!
Today, I gave it a try but unfortunately faced some kind of total reflection.
1. I downloaded and flashed the latest android factory image (ryu-opm1.171019.016 = 8.1 from Feb. 2018) from Google.
2. I downloaded and booted (without installing) twrp-3.2.1-0-dragon by means of "fastboot boot twrp-3.2.1-0-dragon.img"
3. In TWRP I mounted the system partition rw
However, after mounting the system partition rw, android won't boot into the system anymore. I am alway getting the green android guy laying on its back with "No command". When I boot into TWRP and mount /system in ro-mode, then will boot afterwards without any problems. So the problem must be related to mounting /system in rw-mode by TWRP.
I have also tried twrp-3.0.0-0-dragon-ryu-02112016-1.img, which worked on my previous 8.0 installation, but it won't work in this 8.1 release anymore.
Any ideas how to get rid of this problem?
Thanks in advance and kind regards,
star3141.
Hello!
I found a solution!
If someone else suffers from similar problems then try the following which hopefully will fix everything: :fingers-crossed:
1. Download and flash the latest (in my case Android 8.1 from Feb. 2018) android factory image from Google.
2. Complete the standard android setup procedure and, when the system is up and running, enable "USB debugging" in the "Developer Options".
3. Restart your device in bootloader mode by "adb reboot bootloader".
4. Format your /data partition by "fastboot format userdata" to remove the filesystem encryption.
5. Download the latest TWRP (in my case "twrp-3.2.1-0-dragon.img") and start it by "fastboot boot twrp-3.2.1-0-dragon.img".
6. In TWRP mount /system in rw-mode and just to be sure check if the /data partition can be accessed. If not, just wipe/format it as ext4 again.
7. Download the latest Magisk (in my case "Magisk-v15.3.zip") and sideload it by "adb sideload Magisk-v15.3.zip" in TWRP.
8. Reboot into the android system and install the Magisk app (in my case "MagiskManager-v5.5.5.apk")
9 Viola! Enjoy a working and rooted android 8.1. :victory:
Kind regards,
star3141.
didn't have any problems with magisk 15.3 on 8.1 but with 16.0 the pixel won't boot anymore (stays at the google logo, not even reaching the bootaniamtion). anyone else having this issue? after flashing boot-image and reinstalling magisk 15.3 it works fine again...
For me as well, get 16.0 not to run, Bootloop
Yep, same here, then I bricked it restoring a nandroid backup where it destroyed system, then I couldn't get past encryption password in TWRP. So it's been one of those days...
m+a+r+k said:
Yep, same here, then I bricked it restoring a nandroid backup where it destroyed system, then I couldn't get past encryption password in TWRP. So it's been one of those days...
Click to expand...
Click to collapse
did you already try "default_password" (without quotes of course)? had this issue too some time ago after restoring a nandroid – reflashing twrp via fastboot and decrypting with default_password helped
doumer said:
did you already try "default_password" (without quotes of course)? had this issue too some time ago after restoring a nandroid – reflashing twrp via fastboot and decrypting with default_password helped
Click to expand...
Click to collapse
Yes, tried that as well. I think I just corrupted the system, wiped data and system in trying to get around the Magisk problem.
m+a+r+k said:
Yes, tried that as well. I think I just corrupted the system, wiped data and system in trying to get around the Magisk problem.
Click to expand...
Click to collapse
Hm, as long as you still have fastboot access, I would try to manually flash partiotions (system, vendor etc), flash twrp, install masgisk 15.3, start from scratch and restore the apps with titanium backup (hopfully you have a backup!). as long as its not a hard brick, it's all fixable
doumer said:
Hm, as long as you still have fastboot access, I would try to manually flash partiotions (system, vendor etc), flash twrp, install masgisk 15.3, start from scratch and restore the apps with titanium backup (hopfully you have a backup!). as long as its not a hard brick, it's all fixable
Click to expand...
Click to collapse
Oh, I'm back to normal now. I couldn't get it to connect to PC as all I had was fastboot and recovery. I discovered the only way to get adb/fastboot connection from PC was to go into TWRP and ADB Sideload. Once that was established it made the connection and I installed 8.1 from the command line with the flash-all.bat.
Then I could restore the nandroid. All is well now, thanks.
good to hear!
Same problem here with 16.0. Seems to be either a bug or some kind of incompatibility with the pixel c.
Magisk 16 and Pixel C
Any word on resolution of the boot loop issue?
Reflash + downgrade to 15.3 seems the only working solution at the moment.
I have re-rooted using Magisk 15.3 from SuperSu. Am I OK updating to 16.0 through Magisk, or should I try 16.3?
mightywhites29111971 said:
I have re-rooted using Magisk 15.3 from SuperSu. Am I OK updating to 16.0 through Magisk, or should I try 16.3?
Click to expand...
Click to collapse
16.0 causes a boot loop. Somebody else had an issue with 16.3. I'd stay with 15.3. Just turn off update notifications and Magisk won't bother you.
Cheers
Hello,
I have a Mi Max 3 6GB/128GB which I got from the UK which arrived unlocked and with Global Stable ROM installed which actually updated to V10.3.3.0.PEDMIXM by OTA - I tested.
fastboot getvar anti shows failed, so I assume no Anti Rollback Protection, which I thought a little strange, it being MIUI 10 with (after OTA) June 2019 security patch.
I spent the last couple weeks setting up the phone to my liking (I have 300 apps installed) and finally finished yesterday.
Then I wanted to uninstall some Google/Facebook/Xiaomi bloatware using the excellent "Xiaomi ADB/Fastboot Tools".
I was pretty careful in my opinion to only remove the safe ones (the tool claims to only show you the safe ones) like Music, Video, MiPay, MiCloud, MiForum, MiSIM and all Facebook in the ADB section of the tool.
The I switched in fastboot and thought it would be a good idea to wipe Cache (nothing else).
Upon restart the Mi Max 3 first shows the black boot screen with unlock written at the bottom, then changes to the normal boot boot screen with MIU and the points at the bottom showing that it is busy booting. It stayed there for a while and I thought maybe it was rebuilding the cache and it took that long, but after 30 min still no luck.
Then I fired up the "Xiaomi ADB/Fastboot Tools" on my PC again and it told me the phone was in ADB mode, I could reboot into system mode, where the same thing happened - no progress in booting.
I cannot turn off my phone either, but I can switch from sastem boot (which gets stuck) into fastboot mode via ADB.
Would someone know what's wrong and what I can do to get my phone out of that bootloop while hopefully maintaining all my data and setups, on which I worked for weeks?
Thank you so much for your help!
P.S .: In case it could help: I could read out the phone properties of the Mi Max using the "Xiaomi ADB / Fastboot Tools" while it was softbricked, meaning the ro. init. persist. sys. and dalvik. values of the smartphone. I am happy to post them here, if requested.
Hi,
Do you have an SD card? If so, remove it, because as you cleared the cache, I think it might be a problem with encryption (lost reference).
In your case, I believe a reset will work again, but you will lose application configuration data. Via ADB you can backup files only.
If you do not have unlock bootloader, be very careful as you will not be able to flash TWRP or others.
Good luck!
Thanks, the phone came from the vendor with Global Stable ROM and unlocked. It may be an unofficial unlock, though I was able to install OTAs.
I don't have SDCard.
How can I do ADB backup?
I was able to flash official TWRP just a few minutes but it couldn't access data, maybe because it is encrypted. Now I think I will try and install latest Orange Fox r10 stable, which I think should be able to handle decryption, so that maybe I will be able to get at my date.
Any other advice?
Hi,
Now that you have TWRP, clear cache / dalvik from TWRP and try starting again, maybe start system.
About copy via adb follows a link below:
https://www.lifewire.com/use-minimal-adb-and-fastboot-4582201
in step 2
"
The command to move files from your computer to your phone is adb push.
To move files from your phone to your computer the command is adb pull.
"
Through TWRP you may also be able to back up. Go to (mount partitions) and select all partitions.
Make sure the TWRP MTP option is on, it will allow the device to be mounted via usb on your computer.
I use TWRP I use nijel8, it works very well.
https://forum.xda-developers.com/mi-max-3/development/recovery-twrp-3-2-3-1-nitrogen-t3866084
If you can't launch system, you will have to reinstall the Rom.
Good luck!
PS.
More help for adb.
https://forum.xda-developers.com/android/help/adb-fastboot-commands-bootloader-kernel-t3597181
Thanks for your advice!
I first used the official TWRP and I was able to flash it and start it.
But then the wipe of cache and dalvik failed.
And I could not mount data etc..
When I tried to repair the file system with TWRP I got error 255 - unable to repair data from fsck.f2fs.
Then I saw in your signature that you use nijel8's TWRP and I read that thread, and I started to understand, that my TWRP errors most likely originate from TWRP not being able to decrypt my partitions.
However, towards the end of the thread it seemed that nijel8 stopped working on that project and then Xiaomi once again changed the encryption in MIUI 10/Pie and so it was recommended first to use an obscure Chinese TWRP and then to move on to Orange Fox Recovery Project, which supposedly can handle the decryption better. So that's what I got and I am just about to install it and see if I can rescue or even repair anything.
If you have any other tips for me, I would be very grateful.
You have explored the possibilities well, at the moment I dont have more options regarding current system recovery / backup.
The encryption error resolves you by formatting the user partition by TWRP, in the option to format f2fs plus the installation of a custom Rom or Xiaomi.eu.
Look for tutorials and other reviews before testing these procedures.
Remember that there is a big achance of your ARB model as well.
Good luck.
PS. You can try dirty flash. Find an recovery Rom same version, and flash via TWRP.
Hi everyone, I was usually providing help on this forum, now i'm the one desperate for help after some unforeseen consequences.
Bear in mind I'm kind of a noob anyway.
I have seen the message on the telegram groups for our device regarding solving the los 17 problems with the ril and camera. So i have followed the steps. I flashed the last twrp 3.4 by jarl using the official twrp app and then rebooted to recovery, wiped everything beside the internal storage and tried flashing the last los 16 zip.
And then the disaster happened. firstly the log returned error 7 so i've rebooted to recovery again and attempted to flash the same zip again without wiping anything. well the flashing worked apparently but i couldnt boot into it as it showed me an infinite boot animation.
Then i rebooted to recovery and it prompted me with a decryption key request which i didn't set before. I cancelled the prompt and I moved forward and proceeded wiping everything including the internal storage thinking that was the problem. Maybe it was maybe it wasnt, now I'm no longer prompted by any decryption key, but I was hoping i could connect to my pc through mtp, transfer some zips and flash some functional rom. Even though I enable mtp and my pc detects the phone I can't access any storage nor the internal, nor the sd card.
I tried going through multiple versions of twrp as i can still access my bootloader and i can still flash recoveries through fastboot but i feel that i'm stuck and I dont know what i should try anymore.
Before trying all this I was on an older build of los16 with the oreo firmware.
First of all, use this TWRP: https://build.twrp.me/twrp-3.4.0-0-montana.img
Second of all, do not flash TWRPSARer (if you did). Make sure the LOS16 zip isn't corrupted (which normally causes error 7), then format system, data, cache, vendor and dalvik. Reflash LOS16 and boot
JarlPenguin said:
First of all, use this TWRP: https://build.twrp.me/twrp-3.4.0-0-montana.img
Second of all, do not flash TWRPSARer (if you did). Make sure the LOS16 zip isn't corrupted (which normally causes error 7), then format system, data, cache, vendor and dalvik. Reflash LOS16 and boot
Click to expand...
Click to collapse
I wasnt using the twrp sar, i was using the exact version you linked. And I can't flash any rom because i cant get the zip inside my internal memory.
You can try using adb sideload. adb sideload path/to/zip
worked like a charm. thanks a lot, Jarl.
And this, is the story of someone who didn't want to wait long enough for the ROM to boot
Nah JK, but long boot-times normally = Force Encrypt Enabled
Some random said:
And this, is the story of someone who didn't want to wait long enough for the ROM to boot
Nah JK, but long boot-times normally = Force Encrypt Enabled
Click to expand...
Click to collapse
it might have been the problem, but if it is it should be a disclaimer for that on the los16 page. the boot time is way longer than the usual.
Aythriel said:
it might have been the problem, but if it is it should be a disclaimer for that on the los16 page. the boot time is way longer than the usual.
Click to expand...
Click to collapse
Yes, I'll make sure to note that
Did standard unlock bootloader (went fine)
Moved a TWRP zip onto phone sd root directory (twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.zip)
adp fastboot boot twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img. (went fine)
But when I look for the zip file (or any system files) it does not show up , even in TWRP file manager.
Redid data wipe and it tells me "Failed to mount /system_root and /vendor
I am 99% sure that its just because these will not mount:
Does anyone have any idea what I can do to get these mounted to start a regular TWRP flash ?
Well I tried adjusting data format and ended up losing the Stock Rom.
And the stuff will still not mount.
UPDATE, rewiped data and got stock rom to load.
Now Data will load but vendor will not.
UPDATE : data and vendor will mount after data wipe. But still cannot see anything that is placed on device.
Such as the zip files I need to install.
UPDATE: now I sideloaded TWRP onto new phone, but now cannot get it to reboot into Rom.
Its odd after plugging it in , it went to a stock recovery even when TWRP was installed.
Found the issues, finally had to run MSM download tool and fix everything from there and start from scratch.
Ended up installing TWRP from fastboot flash recovery image.
Now to get root going on it and magisk.
What device do you have?
You're in the 7T forum but saying you used the 7 Pro twrp.
If you're using 7T, the reason why you don't see internal storage is because TWRP cannot decrypt on OOS (this is not because of a mounting error, this is simply due how oneplus has implemented their encryption).
And on 7T you don't need a zip of any sort to install twrp.
Reading the actual twrp thread would be a good start.
Lossyx said:
What device do you have?
You're in the 7T forum but saying you used the 7 Pro twrp.
If you're using 7T, the reason why you don't see internal storage is because TWRP cannot decrypt on OOS (this is not because of a mounting error, this is simply due how oneplus has implemented their encryption).
And on 7T you don't need a zip of any sort to install twrp.
Reading the actual twrp thread would be a good start.
Click to expand...
Click to collapse
Yes, I read though the threads, But got so bombarded with pages of stuff kind of lost track.
This is why I posted . Also it is a combined Christmas gift for my daughter that she cannot know I am working on. So I think I tried to rush it when she was in school.
Found out about the decryption part after I started the process. Then it was too late and ended up having to start over with tools.
It was a newb move to end up this far and try to rush it.
People did help me get back on track and now I am working on figuring out Magisk. (good help on magisk threads).
Thanks for your response.
eracet said:
Well I tried adjusting data format and ended up losing the Stock Rom.
And the stuff will still not mount.
UPDATE, rewiped data and got stock rom to load.
Now Data will load but vendor will not.
UPDATE : data and vendor will mount after data wipe. But still cannot see anything that is placed on device.
Such as the zip files I need to install.
UPDATE: now I sideloaded TWRP onto new phone, but now cannot get it to reboot into Rom.
Its odd after plugging it in , it went to a stock recovery even when TWRP was installed.
Found the issues, finally had to run MSM download tool and fix everything from there and start from scratch.
Ended up installing TWRP from fastboot flash recovery image.
Now to get root going on it and magisk.
Click to expand...
Click to collapse
Magisk IS your root