I was trying to clean install Oxygen OS 4.0 onto my OnePlus 3. I did a huge mistake of formatting my entire data off of my OnePlus 3 using Wipe > Format Data > Yes in TWRP and now I cannot use my phone.
I don't know how to install the OS on the phone again and I am stuck. I don't even have a spare phone right now.
Can someone please help me? I tried checking the other forums, but they were confusing and I didn't understand anything. Please help me.
I tried downloading the software from OnePlus's website, but I couldn't install it through ADB cause the file is for some odd reason corrupt.
Please, somebody help me. I can't even send it back to OnePlus cause I am in a different country ATM.
I had trouble with OB10 and adb. Said it couldn't read the file. I instead flashed TWRP and enabled mtp from there. I then pushed the full ROM to internal storage. Fastboot flashed the stock recovery and used 'upgrade from internal'. That flashed it fine. Then I reinstalled TWRP and SuperSU.
yasinmys said:
I was trying to clean install Oxygen OS 4.0 onto my OnePlus 3. I did a huge mistake of formatting my entire data off of my OnePlus 3 using Wipe > Format Data > Yes in TWRP and now I cannot use my phone.
I don't know how to install the OS on the phone again and I am stuck. I don't even have a spare phone right now.
Can someone please help me? I tried checking the other forums, but they were confusing and I didn't understand anything. Please help me.
I tried downloading the software from OnePlus's website, but I couldn't install it through ADB cause the file is for some odd reason corrupt.
Please, somebody help me. I can't even send it back to OnePlus cause I am in a different country ATM.
Click to expand...
Click to collapse
Have you downloaded the full ROM? Make sure you download the full rom from oneplus's website or any of the mirrors available on various forums on xda. Flash it normally like you flash a custom rom. It will work as I have done it a lot of times. Your file must have been corrupt.
yasinmys said:
I was trying to clean install Oxygen OS 4.0 onto my OnePlus 3. I did a huge mistake of formatting my entire data off of my OnePlus 3 using Wipe > Format Data > Yes in TWRP and now I cannot use my phone.
I don't know how to install the OS on the phone again and I am stuck. I don't even have a spare phone right now.
Can someone please help me? I tried checking the other forums, but they were confusing and I didn't understand anything. Please help me.
I tried downloading the software from OnePlus's website, but I couldn't install it through ADB cause the file is for some odd reason corrupt.
Please, somebody help me. I can't even send it back to OnePlus cause I am in a different country ATM.
Click to expand...
Click to collapse
Go to: h*t*t*p*://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.2.8/ (REMOVE STARS) download both stock recovery and rom of OOS v3.2.8 (located at the bottom of the page). Flash stock recovery via fastboot (I hope you know how to). After it was flashed, disconnect the cable, turn off the device in fastboot (power off). Then hold power and volume down keys down to boot into recovery. From there ADB sideload the stock OOS v3.2.8. Let it boot up and update to OOS 4.0 via OTA.
P.s. If you need the actual steps, let me know. I'll update it in this post.
nine5raptor said:
I had trouble with OB10 and adb. Said it couldn't read the file. I instead flashed TWRP and enabled mtp from there. I then pushed the full ROM to internal storage. Fastboot flashed the stock recovery and used 'upgrade from internal'. That flashed it fine. Then I reinstalled TWRP and SuperSU.
Click to expand...
Click to collapse
I had an issue with custom twrp + Freedom OS v2.0 (OOS v4.0). No xposed, a lot of battery issues with performance and toggling settings issues too. So I decided to stick with Freedom OS 1.7 (OOS v3.2.8) until OnePlus fixes the issues, with xposed available for Nougat and official twrp being released to support Nougat. Also, whenever I flashed custom twrp, which was recommended by the dev, it always asked me for a password. I did have PIN code with fingerprint option, a pattern option or none at all. All of which did not help bypass it, even using "default_password". I was stuck with OOS v4.0, somehow, with no twrp to work with as it locked my data. I backed my files before flashing from OOS v3.2.8 to OOS v4.0, lucky me. I managed to do what I have explained in the first response.
Hello,
[Sorry: can't edit title]
I've been trying to install Lineage 14.1 on my Samsung Galaxy Tab Pro (SM-T520), and haven't been successful.
I keep getting the message "Google Services Framework keeps stopping", sometimes alternating with the message "android.process.media has stopped".
I've used the following installation procedure:
1. Starting with the stock Samsung Android v4.4.2, I used Odin v3.1.2, to root the device, by installing
CF-Auto-Root-picassowifi-picassowifixx-smt520.tar.md
2. I used Odin to install picassowifi TWRP v2.8.7.0. I didn't use the latest v3.1.1-0, because it reboots the
device while making Nandroid backups. Available here
https://eu.dl.twrp.me/picassowifi/
3. I copied several versions of Lineage OS amd Gapps (see below) to the device's SD card
4. I used TWRP to wipe the cache/dalvic/data/system each time, using the Wipe->Advanced option
5. I used TWRP to install the Lineage OS amd Gapps as an atomic operation on the device
6. After installation, I rebooted from TWRP:
- without rooting: I get the message "Google Services Framework keeps stopping"
- with rooting, by installing SuperSU: The device enters into a boot loop, displaying the sliding Lineage logo
I followed the same procedure to update my Samsung Galaxy S4 Mini, and it worked flawlessly.
I tried the following Lineage OS versions, available here:
https://download.exynos5420.com/LineageOS-14.1/n2awifi/
lineage-14.1-20170506-UNOFFICIAL-n2awifi.zip
lineage-14.1-20170715-UNOFFICIAL-n2awifi.zip
I also tried the folowing Lineage OS versions, available here:
https://download.lineageos.org/n2awifi
lineage-14.1-20170608-nightly-n2awifi-signed.zip
lineage-14.1-20170713-nightly-n2awifi-signed.zip
I tried the following versions of Gapps, available here (32-bit arm, Android v7.1, stock variant):
http://opengapps.org/?api=7.1&variant=stock
open_gapps-arm-7.1-stock-20170505.ziip
open_gapps-arm-7.1-stock-20170711
I tried several combinations of these 2 packages. With all the combinations I tried, I got the results summarised above.
This post suggests installing Lineage OS alone without Gapps, and then install Webview Implementation, if not installed:
http://www.lineageosrom.com/2017/02/how-to-fix-google-play-services-error.html
When I tried this and reboot, I get the messages "android.process.media" has stopped, followed by the message "clock has stopped". When I click away these messages, and click on next on the Lineage OS screen, the device enters into a boot loop displaying the sliding Lineage logo. This agrees with the Lineage recommendation, that both packages need to be installed at the same time:
https://wiki.lineageos.org/devices/n2awifi/install
Can anyone please help? I really don't want to go back to Android v4.4.2 on my SM-T520.
Hello so to get rid of the error I would suggest downloading samsung kies 1 not 2 or 3 and flashing completely back to stock then try rooting and flashing rom should get rid of system errors and force closes. Kies will ask you for model and serial number. Serial is found on back of the tablet. As another suggestion I would try resurrection remix by cosmox. It is very stable everything works. I just posted a link in that thread with a link to download samsung kies for a 64 bit windows and other relevant files if you need. Let me know if you need any other help. Also closer inspection of your links. I think for sm-t520 u should be using twrp Picassowifi, not n2awifi so idk if that will work or not. Not sure about that part though because they may have made it work on Picasso.
Thanks paintball.
I confirm that I had used picassowifi TWRP. I've edited the original post to indicate this.
I've also tried what you suggested - I reinstalled the original stock Samsung firmware using Odin, and used TWRP to again install Lineage. Same result, still displaying the same Google Service errors.
I'll look at the Resurrection remix.
Paul
paintball,
I've found a solution, that I thought I'd post here in case anyone else has the same problem.
I wiped the cache/dalvic after each step of the installation:
Wipe-> Advanced -> wipe cache / data / dalvic / system
Install -> flash Lineage -> wipe cache/dalvic
Install -> flash Gapps -> wipe cache/dalvic
Reboot -> don't install SuRoot
I got a Music closed error during the first boot, which hasn't appeared since.
Afterwards, I used Odin to install CF-Auto-Root. The device rebooted twice after this step, but now appears to be OK.
A final problem I had was that it couldn't find my wifi SSID. I solved this by setting wifi region to Europe.
ppmoore said:
Thanks paintball.
I confirm that I had used picassowifi TWRP. I've edited the original post to indicate this.
I've also tried what you suggested - I reinstalled the original stock Samsung firmware using Odin, and used TWRP to again install Lineage. Same result, still displaying the same Google Service errors.
I'll look at the Resurrection remix.
Paul
Click to expand...
Click to collapse
I suggested using Samsung kies which I'm positive works, not Odin, but I'm glad you got it fixed.
ppmoore said:
Hello,
[Sorry: can't edit title]
I've been trying to install Lineage 14.1 on my Samsung Galaxy Tab Pro (SM-T520), and haven't been successful.
I keep getting the message "Google Services Framework keeps stopping", sometimes alternating with the message
<snip>
Click to expand...
Click to collapse
I'm having a similar issue. Mine differs in the following ways.
I was able to successfully install and run LineageOS with OpenGApps full, but reverted to a nandroid backup because I needed some information from the original install. Since then, I have been unable to get past the initial couple of screens for setting things up--and this with the constant "Google Services Framework keeps stopping" error.
I have tried most of the "fixes" I've found but to no avail. I notice that, (1) when I go to the drop-down menu and setup WiFi, as soon as the device connects to the Internet, I go to the Lineage bootup animation and get stuck there. If I hard boot from there, I can get in up to the point where I connect to the Internet (not just router, but actually get through to the Internet) and (2) I cannot enable Developer options--when I try, no matter how many times I click on the Build number, I get no indication of the options being enabled.
I have tried several permutations of Lineage OS nightlies along with various flavors of OpenGApps, with and without root, wiping cache/dalvik/data/system, wiping only some, wiping none.
I also cannot restore the backup of the running LOS that I had up (I did take a backup before going back to the original setup). When I try, I get the same results as above--as if I had backed-up an un-instantiated setup.
Any thoughts?
eckster said:
I'm having a similar issue. Mine differs in the following ways.
I was able to successfully install and run LineageOS with OpenGApps full, but reverted to a nandroid backup because I needed some information from the original install. Since then, I have been unable to get past the initial couple of screens for setting things up--and this with the constant "Google Services Framework keeps stopping" error.
I have tried most of the "fixes" I've found but to no avail. I notice that, (1) when I go to the drop-down menu and setup WiFi, as soon as the device connects to the Internet, I go to the Lineage bootup animation and get stuck there. If I hard boot from there, I can get in up to the point where I connect to the Internet (not just router, but actually get through to the Internet) and (2) I cannot enable Developer options--when I try, no matter how many times I click on the Build number, I get no indication of the options being enabled.
Any thoughts?
Click to expand...
Click to collapse
Hi Eckster,
I have exactly the same problem on a LG G2 with LOS 14.1. It ran July version perfectly but I didn't make a backup and now I'm stuck. Did you ever manage to fix this?
Thanks,
Kevin
Managed to solve it. I formatted all partitions _including_ data (which means you'll also loose all zips you wanted to install so make sure that adb is working). Then rebooted into the recovery. Installed as usual, worked.
detlef25 said:
Managed to solve it. I formatted all partitions _including_ data (which means you'll also loose all zips you wanted to install so make sure that adb is working). Then rebooted into the recovery. Installed as usual, worked.
Click to expand...
Click to collapse
how did you format the partitions? I can only find "format data".. thx
detlef25 said:
Managed to solve it. I formatted all partitions _including_ data (which means you'll also loose all zips you wanted to install so make sure that adb is working). Then rebooted into the recovery. Installed as usual, worked.
Click to expand...
Click to collapse
:thumbsup: I was on lineage 14, all was well. I tried an old stock rom NK2, that was fine. I tried to restore lineage backup via twrp, got this problem with the framework crashing. No amount of re-flashing twrp nor lineage, gapps, modem, bootloader, etc nothing worked; always crashed right after boot to lock screen. Finally twrp "format data" - yes. Now lineage boots to welcome, no crash; restore backup - after copying it back to internal - and all is good.
I'm glad it works but why is it needed in this case to remake the filesystem on data - does it work by removing some bad file or does it work by rebuilding the ext4 and security context? this is with latest twrp twrp-3.2.1-0-klte.
Hi,
don't know if you solved it eventually, or maybe helpful for other people with the same problem. I had the same problem, spent 6 days digging around on the internet why the framework keeps stopping and crashing.
I eventually found out that:
- TWRP 3.0.2.0 is WAY more stable than 3.1.1.0 (which never succeeded in installing gapps without crashing)
- Wiping system, data, dalvik recovery and internal storage is not the only thing that needs to be done. You also need to use the 'FORMAT DATA" button (everything will be wiped from your tablet, so, as always, backups )
- After that, install the lineageOS binary, after the installation, wipe dalvik/cache, go back and install the appropriate GApps package, wipe dalvik/cache and reboot
Say whatever you need to whatever deity you prefer and wait for the tablet to boot.
I hope to be of some help to other people having the same problem
Code:
Sent from my SM-S920L using Tapatalk
grammar
detlef25 said:
Managed to solve it. I formatted all partitions _including_ data (which means you'll also loose all zips you wanted to install so make sure that adb is working). Then rebooted into the recovery. Installed as usual, worked.
Click to expand...
Click to collapse
Was going crazy trying to figure out why LineageOS was encountering so many ANRs. The first time I flashed Lineage it worked beautifully but every time after that it just went nuts. This fixed it for me, thanks dude!
Note to others who may end up here, after formating data I had to install a stock ROM, then wipe and install Lineage. Lineage wouldn't install due to Updater process ended with ERROR: 7 which was because there was some bit of information that was on the data partition that showed the install script that the phone was actually a Note II. Formating data blows that info away but installing stock puts it back on.
LievenVanh said:
I eventually found out that:
- TWRP 3.0.2.0 is WAY more stable than 3.1.1.0 (which never succeeded in installing gapps without crashing)
- Wiping system, data, dalvik recovery and internal storage is not the only thing that needs to be done. You also need to use the 'FORMAT DATA" button (everything will be wiped from your tablet, so, as always, backups )
- After that, install the lineageOS binary, after the installation, wipe dalvik/cache, go back and install the appropriate GApps package, wipe dalvik/cache and reboot
Click to expand...
Click to collapse
Coming into this thread after a few hours of struggle with an old GS4 I can say that this method instantly worked for me as well.
Thanks!
Thanks for the help to resolve my issue of installation. Do you have a solution for Zoom , where my audio (cannot hear other speakers) and video is missing. Did enable access for Mic, Camera etc in App permission.
Look at this thread: https://forum.xda-developers.com/ga...-t520-unofficial-lineage-14-1-t3538770/page86 -- last two posts
hamudistan said:
Look at this thread: https://forum.xda-developers.com/ga...-t520-unofficial-lineage-14-1-t3538770/page86 -- last two posts
Click to expand...
Click to collapse
That solution didn't work. My Zoom audio still not working.
Disclaimer: I am no developer just someone who has done a ton of research in the last day
This may be a long post due to my extensive troubleshooting issues, so here's some background.
OP5T is the first android I've owned and I have had it for about a year. I rooted it right after I received it and haven't updated it since. With the release of Oreo, I entertained the idea of updating my firmware, which I knew meant that I'd need to factory reset my device. Yesterday was the day I decided to do it and man I regret it. Long story short, I fully uninstalled Magisk through the app, attempted to fully remove the root by means of 'full unroot' in the SuperSU app, which failed. I then was stupid enough to fully wipe my device using TWRP (I think I checked the box for every partition in 'advanced wipe'). I was then stuck in a boot loop. Eventually, I managed to use fastboot to boot recovery to TWRP. I have been stuck in this state ever since.
I am currently using 3.2.1-x | blu_spark v8.61 and previously used Magisk.
The main ROM I have been attempting to flash is OnePlus5TOxygen - 5.1.5
- https://www.oneplus.com/support/softwareupgrade/details?code=7
- https://forum.xda-developers.com/oneplus-5/how-to/oxygen-os-5-1-5-signed-zip-t3832336 (not sure how
these are different but their filenames differ so I have tested both
The errors I have received in my troubleshooting process:
- The most infamous: Error 7
- E1001: Failed to update system image
- no file_contexts
- and a host of others I have weeded out using xda as a resource, such as many partition errors, vendor issues,
etc.
- Failed to read command: No error (terminal result when attempting to flash some ROMS through ADB)
The steps I have taken to remedy these errors:
Let me just say I have consulted tons of xda threads regarding error 7, and none work for me. I have attempted to flash using several of the latest versions of TWRP, finding the most success with blu_spark. I have attempted to sideload the ROMS, push them using ADB, and directly place them in the internal storage and no method works. I always get Error 7, with the exception below.
I have attempted to flash stock ROMS for OOS versions 5.1.4, 5.1.5, custom ROMS recommended by xda threads pertaining to the same issue, and many variations of these. Since there are no assert statements in the update_script found in the stock ROMS, which many people mentioned on the forums, I have attempted to approach error 7 from a different angle.
- Each stock ROM starts with this function, which when deleted gets rid of the 'vendor partition is not existed'
error getprop("ro.display.series") == "OnePlus 5T" || abort("E3004: This package is for
"OnePlus 5T" devices; this is a "" + getprop("ro.display.series") + "".");
is_part_existed("/dev/block/bootdevice/by-name/vendor") || abort("vendor partition is not existed, exit
ota!!");
- Even when deleting that, I found there to be two more errors that would appear every time I attempted to
flash, caused by two block_image_update functions that result in errors E1001 and E1002: These both have to do
with updating the system or vendor image.
I have attempted to delete any combination of these. If I don't delete all three functions, I will get an error pertaining to the function I didn't delete. If I do delete them, the ROM will install up to 47% every time and it will cancel (no error). This has happened for all stock ROMS I have flashed, and I have swapped to the latest stock recovery multiple times with no luck.
Additionally, I reformatted data multiple times, set the system partition to ext4, attempted to fix the file system, attempted to mount system in read only to see if that would fix the system update error, all to no avail. I also delete the cache after each ROM flash attempt as well.
I have spent at least 10 hours trying every troubleshoot option I came across on the forums and nothing has helped, which is why I am making this now. I have attempted to flash the current firmware for OP5T with every flash attempt ending with the string '...done' in the terminal, even though nothing has been changed or installed. Every time I try to reboot, it still tells me that I have no OS installed, and I can tell since my internal storage is currently using only around 100MB of usable memory. I have also locked my bootloader, wiped the device, switched to stock recovery, and attempted to clean flash the latest OS with no luck.
In conclusion, it seems that I have deleted my OS so there is nothing to boot to (I go straight to bootloader), there is an error or something missing in my filesystem that is preventing me from fully installing any ROM, and I have tried everything suggested on these forums for similar issues with very limited success. I have done much more than what I mentioned here, and if anything useful comes to mind I will update this post.
(I am also a Computer Science college student that needs a working phone drastically and have already spent so much time diagnosing this issue rather than study that I am ashamed)
I am on the brink of contacting OnePlus, even though I feel as though they wouldn't be much help, or sending this to a repair shop.
Any suggestions/ideas would be greatly appreciated. I will attempt to be as active as possible on this forum as well.
Read my post in this thread, second post. You are fine, as you can still get into TWRP, you are just using a really old version of TWRP, and further complicating things by trying to flash treble ROMs.
Update to the latest version of Bluesparks TWRP which you can flash from your current TWRP, then reflash the full factory ROM. Note it will replace recovery if it is successful.
^^ +1. As long as you can boot into recovery, you are fine. The trick is installing a ROM that is compatible with your TWRP.
I am using codeworkx TWRP 20180822 and running the last Oreo build of Omnirom. First update your TWRP image, then find your OREO rom and install that. You may need to format data with the new TWRP first.
Hello, I really missed the "how to install" section on [ArrowOS 10.0] and got screwed :c
Everytime I try to Install via TWRP I get the "E2001: Failed to update vendor image. Updater process ended with ERROR: 7", and I don't really know what's going on; I saw no TREBLE stuff on this post and went step-by-step on tutorials, but every single time it stops on this error. Actually, afaik having Treble wouldn't be a problem since I came from stock ROM.
The very first time I was on ZUI 4.0.199 and now I'm rolling ZUI 3.5.225 DEV through TWRP (which is the only stock thing I actually managed to install), am I missing something?
It might be something really simple and stupid, so if someone notice it please say it!
I suspect my phone didn't have the 3.5 firmware (which seems to be a requirement), right now I'm searching for the right file to flash.
What I did:
Unlocked Bootloader
USB Debugging
TWRP-3.3.1-0-z2_plus
Didn't go TREBLE or something
Tried wiping everything (Dalvik Cache, System, Data, Cache...)
Reason:
I tried flashing a Custom ROM due to few problems/bugs I had on ZUI 4.0.199 (my phone started rebooting and sometimes it kept rebooting until I charged it). It started annoying me when it kept forgetting WiFi passwords, but since it became almost useless due to rebooting I decided it was time to flash a new ROM and see if I could save my Zuk...
That's how I ended up in this mess, it seemed fairly simply to do but I got lost in the process.
Solution:
Installed 1.9.044 through QFIL, uptaded to 3.5.261 via OTA-Recovery and to 4.0.199 through normal OTA (System Update).
Unlocked bootloader, installed TWRP, did factory wipe and installed ArrowOS 10 (install + cache stuff wipe that appears after installation).
I'll proceed to back up, rooting and mods.
Case closed xD
So after years of never needing to create an account.....I am stuck. Hoping yall can help me out.
I HAD lineage OS installed and everything was working fine. I wanted to revert back to stock so that I could get the google photos unlimited upload back.
I HAD lineage recovery installed but now I am soft-bricked and cant get into recovery.
My bootloader is unlocked and fastboot is working.
When recovery was working, I tried to install the full OTA and that failed so that lead me to the Full Factory Image.
I try to run the flash-all.sh script and it does all sorts of failing. (See flashAllLog.txt) I believe the crux of this is:
When I installed LineageOS, my phone started identifying as a Pixel 3 which was strange but whatever. When I am trying to run this flash-all basically it says that my bootloader is newer and it needs an older version.
So then I thought well maybe I need to erase the slots (eraseLog.txt). Those all worked fine but I still couldnt flash all
So then I was thinking maybe if I just flash the bootloader manually (manualBootFlashLog.txt). But that failed as well.
Am I just boned here or is there an android wizard out there who can point me in the right direction. Please let me know of ANY other information I could possibly provide
Here are 4 options, there's more even tedious stuff you could try but Id start with these
1.) Have you tried to just use fastboot to BOOT into the recovery.img file from the factory image zip (not flash it) and then you can sideload the OTA from there?
2.) You can also try to edit the flash-all file so it doesn't re-flash the bootloader. Just flash system, data partitions etc.
3.) Try another factory image. I assume you tried to flash the latest Android 10 full factory image, maybe try an older one? Maybe even Android 8 or 9 and the just take the OTA update in settings.
4.) Also can try to boot (not flash) lineageos recovery to see if you can at least flash back into LineageOS (or maybe a different custom ROM, PixelExperience for example enables the unlimited Google Drive storage) to get a working device again.