Hi all, I'm not really sure if this is correct section to post this but has anyone else had issues with installing the latest (2016-03-16) CM13 release on their Nexus 7 flo device?
The steps I used to flash are as follows:
1. I used WugFresh NRT "Root" option with "Also flash custom recovery selected" to root my stock android 6.0.1 install and install TWRP 3.0.0.0
2. I then booted into recovery and copied over the CM13 zip and the (2016-03-16) version of OpenGapps Micro to the device.
3. I then did a factory reset from within recovery and flashed the CM13 zip which installed as expected.
4. Then I tried to flash the openGapps zip. I selected the zip and swiped to install and it stayed on "no md5 file found" for about 15 minutes. After this it installed and everything seemed to be fine until I rebooted into the OS.
5. When the tablet booted up for the first time and finished optimizing 96 apps* it came up with the CyanogenMod setup has stopped working error.
I know there is a work around for this but, as I had CM13 installed on this device before with no issue, I decided to dig a little deeper...
1. I downloaded TWRP 3.0.0.0 manually and flashed using fastboot. RESULT: Exact same thing with the long pause when installing Gapps followed by the CM setup error
2. I downloaded CM Recovery and manually flashed using fastboot. RESULT: Cannot install Gapps at all this time due to it not be compatible with CM recovery
3. I tried to ADB sideload using TWRP 3.0.0.0. RESULT: CM13 installed normally, but again, the same long pause with Gapps install followed by the CM setup error
4. By this point I'm fairly sure there is some issue with Gapps so I check the MD5 of the file and its fine so I download an older version and try to flash that... RESULT: Same thing as before
5. Next step, different Gapps version... So I download the "mini" version of Gapps instead of the "micro" one, check the MD5 and then try to flash. RESULT: Again huge pause during install follow by "Error 70: Insufficient space"
6. I setup a gapps config file on the tablet to tell the Gapps installer to install the Micro package in test mode so nothing should change. RESULT: This file is apparently completely ignored and I get the same result as before.
7. Finally I decide to fastboot flash TWRP 2.8.7.0 and voila! RESULT: CM13 installs and the Gapps micro install loads straight up installs everything at the expected speed. When the tablet reboots there are no error and everything seems to perfectly okay.
* As an aside I have a LG G3S/Beat which has been flashed with CM13 and OpenGapps Mini using TWRP 3.0.0.0 with no issue as all. When this device booted up it only optimised something like 24 apps. Can someone explain why my nexus 7 has to optimize 95 and the LG G3S only has to do 24?
TLDR; TWRP 3.0.0.0 doesn't like Gapps on the Nexus 7 flo
So has anyone else had any issue like this with their devices?
Regards
Nathan
Related
Ok so I got my E980 rooted via towelroot, then used the freegee app to install loki, then I used flashify to install the CM recovery listed below, planning to flash the matching cyanogenmod rom:
snapshot Download: cm-12.1-20151007-SNAPSHOT-YOG4PAO332-e980.zip (243.15 MB)
sha1: 9a4773d2fca0658edb2683079ce96307863a9fd0 Download: cm-12.1-20151007-SNAPSHOT-YOG4PAO332-e980-recovery.img
sha1: 1095ea774ff2347fb3a2884045aa4a47e6833893 2015-10-07 02:08:36
I rebooted into the recovery and it wouldn't flash the cyanogenmod 12.1 rom at first, saying that I had an incompatible system installed, so I did a factory reset and then tried again and it installed the CM 12.1 ROM without errors, however it wont boot into it. All I can access is the CyanogenMod recovery and the factory wipe screen, I cant seem to boot into a rom even when it installs without errors, I cant get into download mode no matter what combo of keys/plugging in I do, even though it worked fine before.
Any thoughts or Ideas? I am totally lost here.
When turn on the phone it says:
Secure booting Error! Cause : Device Unlock!, so Boot Success!!
When I try to flash the TWRP zip that is floating around (2.8.1 I think) it says:
Finding update package.....
Opening update package...
Verifying update package...
E:Footer is wrong
E:Signature verification failed
Installation aborted.
When I turn on ADB mode through CyanogenMod recovery
Adb devices: Lists the device (99d3b89c sideload)
Adb usb: Error : closed
I have tried CyanogenMod 10.2.0, 11-20141115, and 12.1-20151007, and tried them before and after every kind of wipe available through this recovery, and they all install without error then reboot back to the recovery.
Is there another flashable recovery around for this phone I could try? I just don't see many in zip format.
Finally got it working. Threw every flashable recovery I could find at it, finally got Phillz touch to install and work from the CyanogenMod recovery. Phillz wouldnt install a working rom, but Phillz did allow me to flash CWM 6 something, which allowed me to install 2.8.1 TWRP, which couldnt see my microSD card, but it did allow me to copy 12.1 CM to my internal SD card from my computer via USB and to flash it and have it actually work. After I booted into CM 12.1 I had to fight gapps for a while, the open gapps pico and nano for 5.1 arm didnt work, but I got the Gapps from the slim rom to work after rewiping the system to remove the open gapps.
After that I finally manager to get flashify, supersu, and busybox from the store. Used flashify to upgrade to 3.0 TWRP. I still cant get into download mode, but pretty much everything else is working now.
I had CM13 on my Oneplus 3, and saw that there was an update. Turns out it was for CM14 and it wiped out my recovery(after further googling, I found out that it's a known issue - http://forum.xda-developers.com/onep...icial-t3497425). So I flashed the custom TWRP recovery from that.
Then I proceeded to flash my last working update of CM13, and the ARM64 6.0 Nano GApps immediately after. I then wiped my dalvic cache and rebooted. It started booting up and the preparing apps screen started loading. But when it finished and I was at the phone setup screen(the screen you get when you first buy a phone and have to choose language, wifi etc), it shows me an error named - "unfortunately the process android.process.media has stopped one plus 3 boot"
I looked the error up online and all results are to go into settings and modify google sync settings, or delete gallery cache etc. But I never even get to reach that point to try it. I flashed CM14 and ARM64 7.1 Nano Gapps to see if maybe that would work, but got the same error. Then I downloaded the last snapshot from CM site with their recovery, but same error.
Can anyone please help me?
Metrotor said:
I had CM13 on my Oneplus 3, and saw that there was an update. Turns out it was for CM14 and it wiped out my recovery(after further googling, I found out that it's a known issue - http://forum.xda-developers.com/onep...icial-t3497425). So I flashed the custom TWRP recovery from that.
Then I proceeded to flash my last working update of CM13, and the ARM64 6.0 Nano GApps immediately after. I then wiped my dalvic cache and rebooted. It started booting up and the preparing apps screen started loading. But when it finished and I was at the phone setup screen(the screen you get when you first buy a phone and have to choose language, wifi etc), it shows me an error named - "unfortunately the process android.process.media has stopped one plus 3 boot"
I looked the error up online and all results are to go into settings and modify google sync settings, or delete gallery cache etc. But I never even get to reach that point to try it. I flashed CM14 and ARM64 7.1 Nano Gapps to see if maybe that would work, but got the same error. Then I downloaded the last snapshot from CM site with their recovery, but same error.
Can anyone please help me?
Click to expand...
Click to collapse
Go back to TWRP --> FULL WIPE (also internal storage - save needed files on your pc before wiping) --> Clean installation of the favourited rom and you should be fine.
LS.xD said:
Go back to TWRP --> FULL WIPE (also internal storage - save needed files on your pc before wiping) --> Clean installation of the favourited rom and you should be fine.
Click to expand...
Click to collapse
I wiped everything except internal memory. And although it gave me some error, I was able to reflash CM13 and Gapps to get the phone working again. Thank you so much!
Hello everyone!
My oneplus3 is actually running no OS and I'm having a boot loop.
I will try to explain what happened to me with the most details I can.
Before I ****ed everything up, I think I was running OxygenOS 3.28, not really sure about it but im 100% sure it was below 4.0, and it was rooted with TWRP 3.0.2 installed.
1) Today I had a pop up saying OxygenOS 4.0.2 was available (the official one that pops on the screen on boot) "Yay so coooool Nougat!"
1.1) I downloaded it, 1.4Go, then I pressed install
1.2) TWRP showed up, I didn't know what to do and that's where I ****ed up, I set my phone "factory new" in TWRP.
1.3) Phone restarted fresh new, I thought I had 4.0.2 but naaaaah would've been too easy so the official pop up showed again, I was still 3.28 I think.
1.4) Downloaded it once more, TWRP opened again, this time i was looking for the update i just downloaded in the "install" section. I browsed for quite a while and couldn't find it.
1.5) Master ****-up here: I tried to restore a backup. Then the bootloop happened. The black screen with "Oneplus" written in white. I was able to go back in TWRP by pressing power + volume down
1.6) Tried every kind of restore unsuccessfully, and tried ADB but it wouldn't load. Also TWRP said that I was running no OS when I wanted to turn off my phone for example.
2) I downloaded 4.0.2 from one plus website on my mac, and i flashed the official recovery instead of TWRP.
2.1) Transferred the update from my mac to my PC (seems important to me) and installed ADB & everything on both PC/O+3.
2.2) so adb worked in forceboot, i've been able to flash official recovery, tried once more to wipe & everything, but clearly I have no OS now, as TWRP said.
2.3) so i had the update in a folder (not a zip, probably due to the download being done from a mac), I made it a .ZIP with winrar, but "adb sideload update.zip" crashed at 0% everytime
2.4) looked at the archive then i noticed it was first a folder "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883" then inside it i had the content like "boot.img" & everything. So i zipped it again but without that first folder because I thought it was the problem, but it kept on crashing 0%.
2.5) restarted my PC, looked on several forums, but i couldn't find any fix. Now adb can't even open update.zip anymore, it fails even before 0%.. I tried naming it .zip.zip, keeping the name "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip", using a third party app to allow more RAM to the cmd app...
I've been trying hard for 4 hours but I still have a O+3 without any OS... My last idea is downloading "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip" from my PC so it downloads it directly .zip unlike on my mac...
I hope I said everything, sorry for the long post but i'm desperate.. thanks for your attention,
Valentin
Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Let me know if it works.
EDIT: See FAQ #1, 2, 4, 12, 14 and 17.
dbabaev21 said:
Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Let me know if it works.
EDIT: See FAQ #1, 2, 4, 12, 14 and 17.
Click to expand...
Click to collapse
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Try to install the new official TWRP version i think it is 3.0.3-0 through fastboot. Boot up TWRP, wipe every partiton and copy the update.zip onto the phone. You can copy it by connecting it normaly via USB(like you would do in OOS) and install the zip file afterwards.
Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
install stock recovery and then try installing official OS. Or install modded twrp 3.0.2-1.28 and then try installing Freedom OS 2.3 via sideload or through internal storage.
Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
Stop fiddling with the ROM. Download the ROM afresh directly to your Windows PC/laptop. Check the md5. Then start experimenting with the other suggestions but don't again meddle with the ROM!
Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
I read your post again and here are a few things:
* Don't update Stock OOS via "System updates" in Settings if you are rooted and have TWRP
* Back up your data before updating, wiping or doing something with your phone.
* For the ADB error, see the FAQ #17 in the guide I provided.
Now, try this:
Flash TWRP via fastboot > boot to TWRP > connect your phone to your PC and copy the full Stock OOS v4.0.2 OTA to your phone > reboot to fastboot and flash Stock Recovery.
It didn't touch the internal storage. So, try to install from internal storage when you are in Stock Recovery.
Let me know if it worked.
Hello
i would like try Lineageos, I went from BenzoRom To lineage-15.1-20181114-nightly-marlin-signed
I follow this link
https://www.xda-developers.com/google-pixel-xl-lineageos-15-1/
but when a reboot twrp 3.2.3-1 ( marlin in the slot A ) it say
" NO os installed ! ..... "
Where am i wrong?
Lele
Ps I can see lineage recovery mode
Which benzo room did you come from?
If you came from a 9.0 rom you may have to flash factory 8.1 before going to lineage 15.1.
Download lineage 16, wipe system/cache/data, install lineage 16 and twrp, reboot to recovery, install gapps, reboot, profit
It says that, doesn't mean it's true. Happens to me as well.
Sorry I did not get the notification!!!
Thank i will try
Leel
I am having a very similar problem with my Google Pixel (model G-2PW4100, not XL). After spending many hours attempting to install LineageOS 15.1 (LOS) and executing just about every possible permutation of installation steps, I am at a loss for why it is failing. I get the "No OS installed", yet sometimes when I reboot after installing the LOS zip file via TWRP I am able to boot to the LOS 15.1 recovery; however, a subsequent reboot always takes me back to the bootloader menu.
I am using the following files:
(Google OTA stock 8.1.0 (OPM4.171019.021.P1, Jul 2018)): sailfish-ota-opm4.171019.021.p1-9fe2c539.zip
(LOS-zip): lineage-15.1-20181229-nightly-sailfish-signed.zip
(TWRP-img): twrp-3.2.3-1-sailfish.img
I start by booting to the bootloader menu (POWER+VOLUME DOWN from OFF). With the phone connected to USB, on the host machine I execute
Code:
fastboot boot twrp-3.2.3-1-sailfish.img
which boots into TWRP recovery. There I use
Code:
adb push sailfish-ota-opm4.171019.021.p1-9fe2c539.zip /sdcard/
to push the stock Google image, and then I use TWRP's install from zip file. It successfully reboots to the stock Android and I can go through the phone setup and everything works fine. Next, I power off the phone and then boot to the bootloader menu. I repeat the fastboot command above to load TWRP recovery. In TWRP, I use adb push to push the LOS zip file. I follow the LOS wiki "sailfish" installation instructions precisely from that point, but I am never able to boot into a working LOS system. It either loads the custom LOS 15.1 recovery one time, after which it reboots to the bootloader, or it just reboots to the bootloader. I have tried repeating these steps in an attempt to install the same software on both slots A and B in case that is an issue, but it does not make any difference.
Can someone help me figure out what I am doing wrong?
Now the phone is unable to boot to system, I have no idea what I could do to fix it as there is no way to use adb or fastboot command…
I remember that the stock rom version is S11a, it have some problems when I tried to root it, and failed to flash recovery even I've got the root permission (response "write error: no space left")
------↑solved by using LG flashtool↑------
Now I am facing the problem that unable to install TWRP recovery using dd, it responds “ write error: No space left on device” I’ve reinstall the LG drivers, reboot the phone, reboot the computer, unroot and root again, but the problem still occurs.
----- update ------
solved by using flashify, and TWRP version 3.3.1 instead of latest 3.6.1, so that it won’t have “secure boot error” warning, and boot to recovery successfully.
But there is a new problem now, when I tried to sideload MindTheGapps after installed LOS 18.1 successfully, it warns me “could not mount /mnt/system! Aborting”. This is the third phone that having this warning for me, and I still couldn’t figure out which step goes wrong.
Nothing goes wrong after flashed to lineage recovery, installed MindTheGapps now.
--update--
I also tried to flash lineage recovery from TWRP on my D855, it also works, I installed MindTheGapps and everything works fine. So this is the problem of TWRP? Or reinstall the recovery is the solution? Maybe I would have a test later.