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
Related
Hi. I've just updated CM13 to the latest nightly using TWRP, but now the system just boots into TWRP - that's whether I select boot system, recovery, or bootloader. I tried restoring from a TWRP backup or another copy of the nightlies zip - it all seems to work fine but doesn't solve the problem. I can connect to the 'recovery' device using adb but adb restart bootloader just loads TWRP again. I've tried wiping first the dalvik/cache, then everything but the internal card, then finally everything but nothing seems to work.
I did get something a little bit like this a few days ago because SuperSU was complaining that I needed to update the binary. I let it do it the way that it suggested one does when TWRP is installed and afterwards couldn't reboot into system, but after a few minutes of frustration sorted things by wiping various partitions.
I attempted to load the full system restore files (cm-13.1-ZNH2KAS29G-crackling-signed-fastboot-74bb753396.zip) using TWRP but that didn't work (I imagine because they're designed to be run via fastboot). I tried loading them via the ADB sideloader option included in TWRP but it failed after a few seconds (I think the message was 'transmitting 0.0x'
I opened that zip and copied the various files to the external card, but I then baulked at installing the image files manually because the only partition option I'm given is boot and my understanding is that each image file should go into its own partition.
The only other potentially pertinent information I can think of:
TWRP keeps reporting "E: Unable to find partition size for '/recovery'"
Has anyone got any ideas please? I had been musing that my next phone would have OTG and NFC, but I wasn't planning to upgrade just yet if I don't absolutely have to.
Have you got it fixed? And if yes - how? I am stuck in a similar situation and can't find a solution for it. Tnx in advance.
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,
Whenever i encrypt my phone on DU, when i set the lock screen Password it asks me if i want the phone to ask it to be able to boot, but then, the phone refuses to boot and says that the Password is wrong.
But when i boot into twrp the Password works and i can decrypt the data partition.
I already had the issue but with the phone accepting the boot pin but twrp not.
This is on a fresh DU install with previously formated data partition.
DO NOT encrypt via custom roms: it's cause of troubles and compatibility issues, especially when returning to OxygenOS.
So:
1) Put device in bootloader mode, plug it to computer, type fastboot format userdata via ADB terminal.
2) Go in TWRP and wipe all the partitions (be sure to have /cache formatted in ext4, otherwise change its filesystem):
3) Always from TWRP, flash latest OOS firmware (4.1.6 or OB19);
3) Reboot and configure setup with your PIN required at bootup;
4) After completing wizard, reboot in TWRP;
5) Now you can wipe anything and flash your rom.
Now device should require your PIN even at first boot of DU.
Ps until doing another fastboot format userdata, device will keep encryption.
Simone98RC said:
DO NOT encrypt via custom roms: it's cause of troubles and compatibility issues, especially when returning to OxygenOS.
So:
1) Put device in bootloader mode, plug it to computer, type fastboot format userdata via ADB terminal.
2) Go in TWRP and wipe all the partitions (be sure to have /cache formatted in ext4, otherwise change its filesystem):
3) Always from TWRP, flash latest OOS firmware (4.1.6 or OB19);
3) Reboot and configure setup with your PIN required at bootup;
4) After completing wizard, reboot in TWRP;
5) Now you can wipe anything and flash your rom.
Now device should require your PIN even at first boot of DU.
Ps until doing another fastboot format userdata, device will keep encryption.
Click to expand...
Click to collapse
Thanks for the answer, do you know why custom rom encryption doesnt work ? I used to to this on my old s5 and it worked perfectly
nikexv2 said:
Thanks for the answer, do you know why custom rom encryption doesnt work ? I used to to this on my old s5 and it worked perfectly
Click to expand...
Click to collapse
Maybe if you give his post a thumbs up he might continue helping you out , I mean that's the least you could do ......
Xceeder said:
Maybe if you give his post a thumbs up he might continue helping you out , I mean that's the least you could do ......
Click to expand...
Click to collapse
If members had to wait for thumbs up before they answer to someone's post then they wouldn't answer most of them.
What kind of **** philosophy is this, i hope for you that's not your way of thinking everyday.
And even, that's none of your business, maybe i forgot to like his post ?
Come on, do not vent on XDA, do not make useless quarrels ?
@nikexv2 sorry, but technically speaking, I don't know the reason of problematic encryption on custom roms.
Just enable encryption with official firmware and there's no other compatibility issue.
Encryption still remains when you full wipe device via recovery.
Have a good day.
nikexv2 said:
If members had to wait for thumbs up before they answer to someone's post then they wouldn't answer most of them.
What kind of **** philosophy is this, i hope for you that's not your way of thinking everyday.
And even, that's none of your business, maybe i forgot to like his post ?
Click to expand...
Click to collapse
It works like this - you ask for help and if someone gives you good advice or helps you out in any way then a quick thumbs up is appreciated , it's just courtesy but anyway I hope you get your phone sorted out ...
nikexv2 said:
Hello,
Whenever i encrypt my phone on DU, when i set the lock screen Password it asks me if i want the phone to ask it to be able to boot, but then, the phone refuses to boot and says that the Password is wrong.
But when i boot into twrp the Password works and i can decrypt the data partition.
I already had the issue but with the phone accepting the boot pin but twrp not.
This is on a fresh DU install with previously formated data partition.
Click to expand...
Click to collapse
Not sure what's wrong with your set up but I came from OOS OB19 to DU, wiped userdata to switch data to ext4, flashed DU + beans gapps (recommended for DU) then booted up, encrypted my phone via Settings > Security and set ask pin on booting device, same pin has worked on all ROMs, even tried some OOS based ones like Freedom OS CE, now on Omni + open gapps, I'm using blu spark latest recovery.
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
got unlucky (or dumb) during an attempt to install pixel experience. something like a detective story
firstly i wrote vbmeta and twrp. ive got smth like a fastboot loop. i used different twrp and it booted into it well. tho noticed that the folders in "install" menu turned into something you get when you fall asleep on a keyboard (names like "303ujdw09ejcf09ejf"). the phone memory was inaccessible from pc.
so i wiped internal memory and it got fine. except the inability to mount system and stuff. trying to flash a room gave me errors like "failed to mount /system (np such directory)" etc.
then i tried different twrp build and it worked well and i even managed to flash pixel experience 12.
formatted and was happy as never. pressed a button to load into sys. but it took me to fastboot where it was reloading itself infinitely. an attempt to load into recovery gave me a twrp logo flickering screen.
i feel like there’s a tiny stupid mistake that i make
btw sorry for my partial incompetence. im much more of a front end dev rather then that deep end stuff
i woulld be very thankful for any reply, the whole situation gives such a frustration and sadness
the original stystem was RMX2063_11_A.51
then i maneged to upgrade to PixelExperience_RMX2061-12.0-20220121-1131-UNOFFICIAL
but now i only have the flickering screen with twrp logo
human_person2402 said:
the original stystem was RMX2063_11_A.51
then i maneged to upgrade to PixelExperience_RMX2061-12.0-20220121-1131-UNOFFICIAL
but now i only have the flickering screen with twrp logo
Click to expand...
Click to collapse
Use Ofox A11+.
Format data either from recovery or using fastboot -w.
debdeep98 said:
Use Ofox A11+.
Format data either from recovery or using fastboot -w.
Click to expand...
Click to collapse
thanks for reply
but theres a problem with ofox installation. when i tried to flash it from twrp it automaticly restarts and i just get to fastboot where it restarts itself over and over. im simply not able to load into anything
human_person2402 said:
but theres a problem with ofox installation. when i tried to flash it from twrp it automaticly restarts and i just get to fastboot
Click to expand...
Click to collapse
Flash it from fastboot.
Boot into ofox.
Flash the ROM.