Tried to flash flash ob 10, but twrp said the zip was corrupted. I could not boot into the system anymore.
The problem is the system partition is ok ( verified from twrp file manager), but every time I choose reboot system, it will go back to twrp. I tried to re-flash ob 9, but twrp again reported another error. Log is attached. How should I solve the problem?
By the way, I wipe all data, including storage in twrp by mistake. Is there any way to recover the data? I am traveling now, just got several hundred pictures.:crying::crying: It seems to be impossible to do it on a computer in MTP mode, but I could not boot into the system neither.
Download the modded twrp from here and install it. Use it to flash community builds and all other roms from now on.
About the file recovering part, I wouldn't know.
You need to flash stock recovery, ADB sideload the official Open Beta, and boot into ROM.
By any chance, did you trigger an OTA update with TWRP installed?
zTweaked said:
Download the modded twrp from here and install it. Use it to flash community builds and all other roms from now on.
About the file recovering part, I wouldn't know.
Click to expand...
Click to collapse
I am always using the modified one. I am encountering a weird error.
The message is like
'E: unknown command [log]
........
script succeeded: result was [1.000000]'.
Update: flashing stock recovery seems to be effective ( of course, twrp does not exist anymore ).
SoybeanYoung said:
I am always using the modified one. I am encountering a weird error.
The message is like
'E: unknown command [log]
........
script succeeded: result was [1.000000]'.
Click to expand...
Click to collapse
Unknown command is a known and harmless issue on all 7.x.x roms. Just ignore it and go ahead.
And I think I saw 3.0.2-1 twrp version in your log.
---------- Post added at 09:20 AM ---------- Previous post was at 09:18 AM ----------
pmbabu said:
You need to flash stock recovery, ADB sideload the official Open Beta, and boot into ROM.
By any chance, did you trigger an OTA update with TWRP installed?
Click to expand...
Click to collapse
Open Beta builds can be flashed via modded twrp, no need to use stock recovery and adb sideloading. Plus even if he installed an OTA update, it won't get installed on twrp ~ and no harm will be done.
After you flash any rom, reflash recovery. Reboot to RECOVERY & then to system.
The red message it's on almoust every Nugat rom. And it's about some log .
zTweaked said:
Open Beta builds can be flashed via modded twrp, no need to use stock recovery and adb sideloading. Plus even if he installed an OTA update, it won't get installed on twrp ~ and no harm will be done.
Click to expand...
Click to collapse
He said he could only boot into twrp. That occurs (reboot to system will take it back to twrp over and over) only if someone tried an OTA update with twrp.
I don't think this is the case for you, but if you tried the other suggestions don't work try the below. I had a similar issue and found that my recovery partition was corrupted. However, an additional symptom I had was that my TWRP would hang completely when selecting reboot after any successful flash. I think modded TWRP does not like internal storage wipe from within TWRP (rather than through fastboot format userdata).
Boot to fastboot
Fastboot erase recovery
Fastboot flash recovery filename.img
Boot to recovery and flash your desired ROM+supersu which you can sideload via MTP (drag and drop from Windows) or adb push C:\SourceLocation\filename.zip /sdcard
I recommend ADB push over MTP.
Had the exact same problem as op, after some issues i was forced to use the unbrick method to get phone back as it wasn't even booting. Now im using beta 10 perfectly.
Did you manage to fix it? I have the same probem.
Related
Even simpler root than Invisiblek's method for the older versions: If you have already tried that method and now have broken wireless, see Post #2.
Note: A more detailed and user-friendly version of these instructions can be found at: http://www.oppoforums.com/threads/n5206-international-root-instructions.24159
Download http://lum.uk/n3/files/recmodn3.img and http://lum.uk/n3/files/Root_ColorOS_by_tantrums_v2.zip
Copy the rooter onto your SD card.
Boot into fastboot by holding volume up while powering on the phone.
fastboot oem unlock
fastboot flash recovery recmodn3.img
fastboot boot recmodn3.img
Flash the root coloros zip file, reboot and you're rooted.
Note: This is a modified stock recovery that can flash OTAs as well as zips not signed by Oppo. If you prefer TWRP then that is available here: https://dl.twrp.me/n3/. Note that at the time of writing TWRP is unable to flash OTAs.
Thanks to [email protected] for the original root method, Arvin A. [email protected] for the fixing SuperSU to work on ColorOS, and [email protected] for providing the modified N3 recovery.
Restoring stock firmware
Download your chosen firmware and recovery from this thread
Copy the firmware to the root of the internal storage
Take a nandroid backup using TWRP
Reboot to bootloader from within TWRP
Code:
fastboot flash recovery recovery_N3.img
fastboot reboot
adb reboot recovery
Use the stock recovery to flash your chosen firmware
If you are downgrading then wipe data and cache (you did remember to take a nandroid, right?)
Reboot
You are now on stock fimware. Follow the rooting instructions in post #1, and if you wiped you may optionally restore only the data partition from your nandroid backup.
Will memory be erased?
Hi,
So i'm looking forward to root my beautiful Oppo N3.
On my last Phones memory (data and so on) was erased alongside with unlocking the phone.
Will it be the same on this phone so that I have to backup all my data?
Your data will not be erased when rooting or unlocking. Also your warranty will not be invalidated like it is with other manufacturers.
It is, however, always wise to take a backup before anything like this, just in case something does go wrong.
Hi,
I tried rooting my N3 now but i made a mistake by not executing the commands after falshing SuperSU.
That's why my phone is always booting into TWRP. There i tried executing your commands, but apparently the shell refuses to su by throwing exception: "command not found"
Going on with mount-command, it is also giving back an error: "can't find /system in /proc/mounts"
Hope sb could help me now...
EDIT: Solved by installing stock recovery, booting system, and the reflash twrp.
Lum_UK said:
Even simpler root than Invisiblek's method for the older versions: If you have already tried that method and now have broken wireless, see Post #2
Download http://teamw.in/project/twrp2/282 and http://download.chainfire.eu/supersu
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery openrecovery-twrp-2.8.4.0-n3.img
fastboot reboot
adb reboot recovery
Flash Super SU from within TWRP. Then boot the OS
adb shell
su
mount -o remount,rw /system
echo "/system/xbin/su --daemon &" >> /system/etc/init.qcom.post_boot.sh
Reboot and you're rooted.
By default ColorOS doesn't let apps auto-start themselves, so go into security centre and allow SuperSU to auto-start, otherwise you won't get prompts for root when other apps need it.
Thanks to invisiblek for the original root method and babelmonk for the fix. I have shamelessly copied these and adapted them for the new firmware.
Click to expand...
Click to collapse
Quoted from your post in oppo forum
Wait for the phone to boot:
adb reboot recovery
It should boot into TWRP recovery flash the SuperSU zip you downloaded but do not reboot as we need to fix a small bug in SuperSU due to Oppo not using the expected startup scripts.
adb shell
su
mount -o remount,rw /system
echo "/system/xbin/su --daemon &" >> /system/etc/init.qcom.post_boot.sh
Reboot and congratulations. You are now rooted.
Sorry , quite new in fastboot command so i apologize if I misunderstood you but I'm running on N5206_EX_23_150208 , which should i follow ? to boot up after flashing SuperSU or not to boot up ?
It doesn't matter which way around you do it, just that root won't work outside of ADB until it's done.
I assume that XDA folk are more familiar with ADB etc. than on the Oppo forums so the instructions skip over more detail here.
Updated the method to use fastboot boot instead of fastboot flash.
This should work around the issue with phones that can't flash twrp, and also leave the stock recovery in place which is more useful to have until we get some custom roms.
Lum_UK said:
Updated the method to use fastboot boot instead of fastboot flash.
This should work around the issue with phones that can't flash twrp, and also leave the stock recovery in place which is more useful to have until we get some custom roms.
Click to expand...
Click to collapse
I was using modified boot.img to get root and then edit init.qcom.post_boot.sh. Now my wi-fi is broken. Can I fix it without wiping? Maybe flash some other boot img?
Anilexis said:
I was using modified boot.img to get root and then edit init.qcom.post_boot.sh. Now my wi-fi is broken. Can I fix it without wiping? Maybe flash some other boot img?
Click to expand...
Click to collapse
Fixed it by flashing boot.img from 150208, root still there due to script edit.
Updated the OP to use the modified stock recovery (Wmjan's recovery for the N5207) as this will be friendlier to noobs and also make it easier to install OTAs.
Anyone know where to get the root coloros file? Link doesn't seem to work for me...
http://www.oppoforums.com/attachment..._v2-zip.31142/
cowabunga said:
Anyone know where to get the root coloros file? Link doesn't seem to work for me...
http://www.oppoforums.com/attachment..._v2-zip.31142/
Click to expand...
Click to collapse
Sorry for the delay in replying. I've re-hosted the file for you.
http://lum.uk/n3/files/Root_ColorOS_by_tantrums_v2.zip
You could also try this. It worked on my girlfriend's R5 running a similar version of ColorOS. Didn't need modified recovery or anything, install it, run, click the root button, and it'll reboot to recovery and root for you.
http://lum.uk/n3/files/ForceRoot.apk
can this root work with Chines n5207
Hello,
I'm from Malaysia,
I got problem with my N3 / N5206 after update the newest version of software...now it cannot detect any line signal and open a wifi...what the problem,can u help me...
I can't make the WiFi to work again. Installed all versions of firmware and no luck....
Update: I was using the wrong tool to flash the firmware.
Don't update the phone with Msm8974DownloadTool !!!!
You have to download and install QPST_2.7.460 and place the phone in download mode by pressing volume + and power button and then in QPST load the firmware N5206EX_11_A.11_150528_SVN6225 or Oppo_N3_N5206_EX_11_A.13_151230 or N5206EX_11_A.10_150519_SVN6196
After flashing the wifi is working but you gonna loose the NV ram backup for the IMEI numbers..
Then you have to open dealpad with *#801# and anable Full-port ON
In QFIL(QPST) click on Tools then click QCN Backup Restore
Choose the qcn file and press restore.
Everything will work again after reboot the phone...
I have been trying to flash oxygen os open beta 9 on my oneplus 3
first i tried the official steps mentioned on the oneplus site
I flashed stock oxygen os recovery
but when i boot into recovery mode it asks for a pattern which upon entering does not decrypt
I then flashed official TWRP and tried to flash the full open beta .zip file but it shows this package is for oneplus 3 this is a ""
also if i try to flash the modified TWRP 28 then also it cannot decrypt the phone
I would prefer not to format the phone if at all possible
aaditya98 said:
I have been trying to flash oxygen os open beta 9 on my oneplus 3
first i tried the official steps mentioned on the oneplus site
I flashed stock oxygen os recovery
but when i boot into recovery mode it asks for a pattern which upon entering does not decrypt
I then flashed official TWRP and tried to flash the full open beta .zip file but it shows this package is for oneplus 3 this is a ""
also if i try to flash the modified TWRP 28 then also it cannot decrypt the phone
Click to expand...
Click to collapse
Hi, I think you should try to format data. Probabby via fastboot, then install TWRP.
Not sure which are the correct commands for the full format, so have a look around or someone else will help.
Otherwise there is the unbrick guide here in the forums to try.
I'm having a similar issue. So any advice would be great. Just updated to most recent unofficial TWRP (having been on a previous version). Now when entering my pin to decrypt it is not accepted. Would prefer not to have to format data.
aaditya98 said:
I have been trying to flash oxygen os open beta 9 on my oneplus 3
first i tried the official steps mentioned on the oneplus site
I flashed stock oxygen os recovery
but when i boot into recovery mode it asks for a pattern which upon entering does not decrypt
I then flashed official TWRP and tried to flash the full open beta .zip file but it shows this package is for oneplus 3 this is a ""
also if i try to flash the modified TWRP 28 then also it cannot decrypt the phone
I would prefer not to format the phone if at all possible
Click to expand...
Click to collapse
unfortunately no choice other than wiping everything.....
antisoma said:
I'm having a similar issue. So any advice would be great. Just updated to most recent unofficial TWRP (having been on a previous version). Now when entering my pin to decrypt it is not accepted. Would prefer not to have to format data.
Click to expand...
Click to collapse
I believe the decrypt is a known issue with TWRP and OB8/OB9 with F2FS /data partition. I don't think there's a work around at this time without formatting /data and rooting to prevent encryption.
Hw4ng3r said:
I believe the decrypt is a known issue with TWRP and OB8/OB9 with F2FS /data partition. I don't think there's a work around at this time without formatting /data and rooting to prevent encryption.
Click to expand...
Click to collapse
So do you think there would be workaround in future?
0xelectron said:
So do you think there would be workaround in future?
Click to expand...
Click to collapse
Hopefully there will be, but it doesn't look promising right now. @eng.stk is the one that was modding the TWRP, but has since stopped doing TWRP dev.
kipue said:
Hi, I think you should try to format data. Probabby via fastboot, then install TWRP.
Not sure which are the correct commands for the full format, so have a look around or someone else will help.
Otherwise there is the unbrick guide here in the forums to try.
Click to expand...
Click to collapse
But I'm on official 3.2.8 with ext4 partition
Do you guy know where to get the stock recovery for openbeta 9? I downloaded somewhere a file recovery_OBT8N.img, but it still shows dm-verity issue.
nqk said:
Do you guy know where to get the stock recovery for openbeta 9? I downloaded somewhere a file recovery_OBT8N.img, but it still shows dm-verity issue.
Click to expand...
Click to collapse
Fastboot Format system and data
Then fastboot flash stockrecovery
Then boot to system
Sideload rom
Then fastboot boot twrp28
Then wipe data and install superuser in one go
candiesdoodle said:
Fastboot Format system and data
Click to expand...
Click to collapse
you mean: fastboot erase userdata?
Btw, I just ignore the dm-verity message to enter stock recovery, and do adb sideload openbeta9.zip and when it boots up again, the dm-verity message is no longer there.
I would try to format (erase userdata) data and flash the modded twrp.
nqk said:
you mean: fastboot erase userdata?
Btw, I just ignore the dm-verity message to enter stock recovery, and do adb sideload openbeta9.zip and when it boots up again, the dm-verity message is no longer there.
I would try to format (erase userdata) data and flash the modded twrp.
Click to expand...
Click to collapse
Yeah fastboot Format userdata
But since you don't have the dm-verity you can skip the fastboot Format. Boot into the modd twrp and when it asks for password, hit cancel and then format data (you will have to type 'yes').
Then flash SuperSU or superuser in the same session without booting. This will ensure dm-verity doesn't come up again as it will start in enforcing mode, thanks to SuperSU/superuser.
You may be able to flash twrp afterwards but I haven't tried it.
Hi guys,
just nowadays I installed OxygenOS Open Beta 10.
I was upgrading from Open Beta 7, but since I unlocked bootloader after doing that, we can say that I did a clean install (everyone should know that fastboot oem unlock erase all data).
However, I'm having troubles both with stock recovery and TWRP v3.0.2-1.28: pattern won't to be recognized.
If I disable pattern requiring at bootup, in recovery I need to type "a password" (that obviously is wrong in any case).
I tried to reinstall more times the firmware, also did factory reset both via stock/TWRP recovery and fastboot commands.
But nothing has changed.
System is working, but I can't access to recovery anyway.
You could try with other TWRP versions? Say 3.0.2-22
It's a known issue
Use twrp v3.0.2-1.19
Works with no issues, except a mouse pointer in the middle of the twrp. It does not interfere with anything, it is just there (a bug).
Simone98RC said:
Hi guys,
just nowadays I installed OxygenOS Open Beta 10.
I was upgrading from Open Beta 7, but since I unlocked bootloader after doing that, we can say that I did a clean install (everyone should know that fastboot oem unlock erase all data).
However, I'm having troubles both with stock recovery and TWRP v3.0.2-1.28: pattern won't to be recognized.
If I disable pattern requiring at bootup, in recovery I need to type "a password" (that obviously is wrong in any case).
I tried to reinstall more times the firmware, also did factory reset both via stock/TWRP recovery and fastboot commands.
But nothing has changed.
System is working, but I can't access to recovery anyway.
Click to expand...
Click to collapse
go to fastboot..
fastboot erase recovery
fastboot flash stock recovery (Open Beta 8)
reboot to recovery
wipe data
flash OOS 4.0 via sideload
reboot..skip setup..reboot to fastboot
fastboot flash twrp (modified)
reboot to recovery
wipe data
advance wipe data to f2fs
reboot
No dm-verity and no encryption
If you are on f2fs and encrypted, the blu spark kernel dev released a new recovery that supports f2fs decryption in TWRP. It may save you all the hassle. All you need to do is flash that updated recovery from fastboot and then try to decrypt. It should work fine.
All you have to do is wipe data partition. Reformat it as f2fs, all in TWRP and then reboot system and proceed with setup. Done!
atulclassic said:
go to fastboot..
fastboot erase recovery
fastboot flash stock recovery (Open Beta 8)
reboot to recovery
wipe data
flash OOS 4.0 via sideload
reboot..skip setup..reboot to fastboot
fastboot flash twrp (modified)
reboot to recovery
wipe data
advance wipe data to f2fs
reboot
No dm-verity and no encryption
Click to expand...
Click to collapse
Cannot find Open Beta 8 Recovery on the download link mentioned above. Looked else where but cannot locate.
Also I flashed recovery_OBT7.img (presumably Open Beta 9 recovery) and followed as mentioned above but DM Verity error does not vanish and TWRP also still asks for password.
Password I hope can be managed with the new modified TWRP mentioned below by @abhibnl but I am more concerned with the dm verity message not going...
---------- Post added at 12:37 AM ---------- Previous post was at 12:30 AM ----------
jim262 said:
All you have to do is wipe data partition. Reformat it as f2fs, all in TWRP and then reboot system and proceed with setup. Done!
Click to expand...
Click to collapse
confirmed password request gone...
dm-verity still exist...
phone does not boot past oneplus logo..can boot into recovery or fastboot but no system loading..
---------- Post added at 12:40 AM ---------- Previous post was at 12:37 AM ----------
jim262 said:
All you have to do is wipe data partition. Reformat it as f2fs, all in TWRP and then reboot system and proceed with setup. Done!
Click to expand...
Click to collapse
confirmed password request gone...
dm-verity still exist...
phone does not boot past oneplus logo..can boot into recovery or fastboot but no system loading..
now i am sideloading os from twrp
mnishamk said:
You could try with other TWRP versions? Say 3.0.2-22
Click to expand...
Click to collapse
It's not working, because modded TWRP from .18 to .23 are designed for Marshmallow community builds.
dbabaev21 said:
Use twrp v3.0.2-1.19
Works with no issues, except a mouse pointer in the middle of the twrp. It does not interfere with anything, it is just there (a bug).
Click to expand...
Click to collapse
What I've said above (tried .19 too with same unsuccessful result).
atulclassic said:
go to fastboot..
fastboot erase recovery
fastboot flash stock recovery (Open Beta 8)
reboot to recovery
wipe data
flash OOS 4.0 via sideload
reboot..skip setup..reboot to fastboot
fastboot flash twrp (modified)
reboot to recovery
wipe data
advance wipe data to f2fs
reboot
No dm-verity and no encryption
Click to expand...
Click to collapse
Probably it would be risolutive, however I want to stay on latest Community Build.
I can say that sideload won't work with Open Beta 10: it can be flashed only via recovery (both TWRP and stock).
jim262 said:
All you have to do is wipe data partition. Reformat it as f2fs, all in TWRP and then reboot system and proceed with setup. Done!
Click to expand...
Click to collapse
That would be easy! The hoped behaviour
Obviously I've just tried with unsuccessful result.
abhibnl said:
If you are on f2fs and encrypted, the blu spark kernel dev released a new recovery that supports f2fs decryption in TWRP. It may save you all the hassle. All you need to do is flash that updated recovery from fastboot and then try to decrypt. It should work fine.
Click to expand...
Click to collapse
Are you referring to this recovery?
Yeah, I would be in love both with you and the developer, if it works properly
Tomorrow I should try, I'll keep you updated :good:
UPDATE: I've always loved Magisk, since v7 (when I've started using it).
Magisk is the workaround for encryption: just today I've flashed it together with Open Beta 10.
Now encryption is disabled, so goodbye to recovery troubles.
However the issue can't be considered solved because of a stupid workaround, this is not the right approach: I will try @abhibnl solution (re-enable encryption, then install latest blu_spark recovery).
Thanks all for answering.
badmaash said:
Cannot find Open Beta 8 Recovery on the download link mentioned above. Looked else where but cannot locate.
Also I flashed recovery_OBT7.img (presumably Open Beta 9 recovery) and followed as mentioned above but DM Verity error does not vanish and TWRP also still asks for password.
Click to expand...
Click to collapse
The recovery should be linked in the official OB10 download page @ oneplus.net
Simone98RC said:
Are you referring to this recovery?
Yeah, I would be in love both with you and the developer, if it works properly
Tomorrow I should try, I'll keep you updated :good:
UPDATE: I've always loved Magisk, since v7 (when I've started using it).
Magisk is the workaround for encryption: just today I've flashed it together with Open Beta 10.
Now encryption is disabled, so goodbye to recovery troubles.
However the issue can't be considered solved because of a stupid workaround, this is not the right approach: I will try @atulclassic solution (re-enable encryption, then install latest blu_spark recovery).
Thanks all for answering.
Click to expand...
Click to collapse
Yes i was referring to that recovery. 1 user has responded that it worked fine on his f2fs encrypted storage, so i believe it's worth trying. I am not on f2fs so i personally can't test it for you. But i would advise you to atleast give it a try. You never know when you by mistake boot right after a fresh stock rom install with stock kernel, and it will immediately encrypt your storage. So, you can't always just keep formatting internal memory. A proper TWRP recovery is indeed required for both ext4 and f2fs. All i am waiting for is updated kernel sources for recovery devs to work on.
For the many having issues, here's a step by step:
step by step install for OOS 4.0 and twrp-3.0.2-1.28-op3.img
Have OOS stock recovery installed on your phone. You must also have adb installed on your computer.
connect your phone to your computer via usb and open a dos command session on your computer.
On your phone, reboot into fastboot (bootloader).
From adb command on computer, type fastboot boot twrp-3.0.2-1.28-op3.img.
First make a backup and copy it to a safe location.
Now wipe everything - Internal, system, data, cache.
Reboot to Recovery. This is the stock OOS recovery!
Go to install from USB and then enter sideload mode.
On your computer dos prompt, type adb sideload (path)OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip
Allow the long and slow process to complete and reboot.
Upon reboot, it is encrypting the data partition as EMMC.
Upon bootup, enter setup and go through it quickly as you will have to enter it again so do not waste time configuring it.
Once setup is complete, reboot into fastboot.
From DOS command, enter adb and type command fastboot boot twrp-3.0.2-1.28-op3.img.
TWRP will boot up asking for encryption password. Hit cancel and then swipe to allow modifications.
Go into mount. Only the system and cache will appear. Back out and select WIPE.
select ADVANCED WIPE and data partition only.
Modify the data parition by selecting Repair or Change file system.
It will list the current mount point as emmc. Select Change File System.
Select F2FS and swipe.
This will wipe current data partition and reformat it.
Once you have done this, while in TWRP, select the ADVANCED button on the main menu.
Now select ADB SIDELOAD and swip to start sideload.
On your computer in ADB, type command adb sideload SR1-SuperSU-v2.79-SR1-20161221223537.zip.
Now reboot system and go through the usual setup and your done.
TWRP v11: the definitive solution
abhibnl said:
If you are on f2fs and encrypted, the blu spark kernel dev released a new recovery that supports f2fs decryption in TWRP. It may save you all the hassle. All you need to do is flash that updated recovery from fastboot and then try to decrypt. It should work fine.
Click to expand...
Click to collapse
FINAL UPDATE: the specified recovery is working with Open Beta 10 decryption.
Thanks all for answering :good:
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,
Everytime I try to OTA update de weekly rom, I get the message that says that my memory is encrypted and directs me to recovery.
In recovery when I select the ROM, it returns ERROR 7, I know that it is related with 2 command lines in the updater script.
My question is, how can I fix this problems so I can normally OTA update?
Xiaomi MI 9 SE
TWRP 3.5.0_9-0
xiaomi.eu weekly (it happens in all versions)
Thanks
Hi please be specific are you using custom rom (twrp,cynogen...?)
Which phone are you using?
otherwise no one will help you (just edit the first message with the necessary info
flairepathos.info said:
Hi please be specific are you using custom rom (twrp,cynogen...?)
Which phone are you using?
otherwise no one will help you (just edit the first message with the necessary info
Click to expand...
Click to collapse
You're right, I think this is a generic problem, that's why I've not specified the model.
vmlc said:
You're right, I think this is a generic problem, that's why I've not specified the model.
Click to expand...
Click to collapse
Ahh I see now,some phones are built with a custom recovery failsafe so updating straight from the phone won't work
Youre going to have to download the update file to the phone (usually ota.zip)
copy it to pc
Unzip it and check the code (installscript.sh, build.prop... all of them(use Notepad++)) and remove recovery what nots (mine had expect recoveryxa84883,and some other recovery partition nonsense) - this is so you dont lose your twrp
compress all the files and name the zip (anything you want)
copy the zip to your adb fastboot folder
Then make sure usb debugging is enabled and
on pc type in adb: adb reboot recovery
after twrp open select the sideload option and use the method of flashing update then your update will flash easy
or
flash your stock firmware recovery image from extsdcard (external sd card) recovery.img as recovery in twrp (surely you know how to tranfer files from pc to microsddard ..)
reboot to system when done and do normal update should work fine
then flash twrp image from pc flashing software into recovery
flairepathos.info said:
Ahh I see now,some phones are built with a custom recovery failsafe so updating straight from the phone won't work
Youre going to have to download the update file to the phone (usually ota.zip)
copy it to pc
Unzip it and check the code (installscript.sh, build.prop... all of them(use Notepad++)) and remove recovery what nots (mine had expect recoveryxa84883,and some other recovery partition nonsense) - this is so you dont lose your twrp
compress all the files and name the zip (anything you want)
copy the zip to your adb fastboot folder
Then make sure usb debugging is enabled and
on pc type in adb: adb reboot recovery
after twrp open select the sideload option and use the method of flashing update then your update will flash easy
or
flash your stock firmware recovery image from extsdcard (external sd card) recovery.img as recovery in twrp (surely you know how to tranfer files from pc to microsddard ..)
reboot to system when done and do normal update should work fine
then flash twrp image from pc flashing software into recovery
Click to expand...
Click to collapse
Thanks for your reply.
Your first method is what I have to do to update manually, delete the model verification in updater-script. But I have to do this every time I want to update. How can this prevent from happening next times?
The second method, I haven't understood, have to flash stock recovery every time I want to update?
My point is to prevent this from happening, I want to OTA update normally, without having to do this procedures every time.
Regards
vmlc said:
Thanks for your reply.
Your first method is what I have to do to update manually, delete the model verification in updater-script. But I have to do this every time I want to update. How can this prevent from happening next times?
The second method, I haven't understood, have to flash stock recovery every time I want to update?
My point is to prevent this from happening, I want to OTA update normally, without having to do this procedures every time.
Regards
Click to expand...
Click to collapse
Yes
and the second method, yes, flash stock recovery to OTA update (it'll think that everthing is fine)
you can keep stock update if dont need twrp anymore
to update normally you would have to modify your stock recovery to have an intergrated twrp
basically making "stock twrp recovery" mod
Or in the same manner add a partition or boot option for twrp in boot image in maybe boot to [normal, recovery, bootloader"fastboot", and twrp]
with enough dedication it is definitely possible
flairepathos.info said:
Yes
and the second method, yes, flash stock recovery to OTA update (it'll think that everthing is fine)
you can keep stock update if dont need twrp anymore
to update normally you would have to modify your stock recovery to have an intergrated twrp
basically making "stock twrp recovery" mod
Or in the same manner add a partition or boot option for twrp in boot image in maybe boot to [normal, recovery, bootloader"fastboot", and twrp]
with enough dedication it is definitely possible
Click to expand...
Click to collapse
So this is not fixable, keep TWRP and have OTA update?
vmlc said:
So this is not fixable, keep TWRP and have OTA update?
Click to expand...
Click to collapse
Yes but now that you mention if you could edit the twrp recovery_id to match that of the stock recovery ,it might work because the system/ ota file calls for a specific recovery_id