Related
Hi,
I got stuck while flashing cyanogenmod 11.
My story:
- I successfully followed this manual http://forum.xda-developers.com/showpost.php?p=54124313&postcount=1
- I finally installed openrecovery-twrp-2.8.5.0-otter.img
- as a ROM a put cm-11-20141112-SNAPSHOT-M12-otter.zip and these gapps gapps-kk-20140606-signed.zip (~157 MB)
- I successfully booted and everythinng seems ok, until I found there are some gapps applications like google+ and email, but no google store and google play services.
- I found on another thread it should be because gapps package is too large for this device and there is another gapps package called small. (~87 MB) I donwloaded it do the device
- I went to TWRP recovery and done factory reset. and then again try to install same package of cm11. Installation seemed to start ok, but it took to long and never finished. Concole is now stuck on a line you see on a screen, progress bar animation is moving and a battery status is changing. I keep it running all night but nothing happened.
My question is: How to safely cancel installation process?
There is no stop button and I don`t know how to cancel installation. Could you please help me how to stop it and how to correctly prepare device for another flash process? As I mentioned, rom and everthing is same as on my first try before, only gapps package is another, but I got no chance to install it.
mefi_cz said:
Could you please help me how to stop it and how to correctly prepare device for another flash process? As I mentioned, rom and everthing is same as on my first try before, only gapps package is another, but I got no chance to install it.
Click to expand...
Click to collapse
Solution for info, if somebody will have same problem. I held power button long for some time, the device turned off and after restart, normally started booting.
As more Lineage OS builds come on line and multiple "nightly" update builds for devices start to appear, one of the issues users may face is the how and why of installing them. The Lineage UPDATER states that it will reboot to the device's recovery to install the update, but that doesn't guarantee anything. If that recovery happens to be, for example, TWRP 3.0.2.0 on an LG v410 tablet, all that might happen is you might find yourself, as I did, staring at a TWRP screen with NOTHING happening. The goal of this thread is to give Lineage users a place to consolidate their experience-based knowledge of how to handle this - other than re-flashing the whole thing -for whatever device(s) they may have.
It will probably be the same as for my L900 with CM13 were I have to download the update, reboot into TWRP and update manually.
Sent from my SM-G900T using Tapatalk
nezlek said:
As more Lineage OS builds come on line and multiple "nightly" update builds for devices start to appear, one of the issues users may face is the how and why of installing them. The Lineage UPDATER states that it will reboot to the device's recovery to install the update, but that doesn't guarantee anything. If that recovery happens to be, for example, TWRP 3.0.2.0 on an LG v410 tablet, all that might happen is you might find yourself, as I did, staring at a TWRP screen with NOTHING happening. The goal of this thread is to give Lineage users a place to consolidate their experience-based knowledge of how to handle this - other than re-flashing the whole thing -for whatever device(s) they may have.
Click to expand...
Click to collapse
Are you able to navigate to the download directory in TWRP?
/data/data/org.lineageos.updater/app_updates
This is far from the worst thing that has ever happened, but WHAT, for instance WOULD be the recoveries that DO allow for automated updates? In my case, I downloaded the new nightly to the root directory my SD Card and let fly, and everything worked, but that seems rather not elegant.
nezlek said:
This is far from the worst thing that has ever happened, but WHAT, for instance WOULD be the recoveries that DO allow for automated updates? In my case, I downloaded the new nightly to the root directory my SD Card and let fly, and everything worked, but that seems rather not elegant.
Click to expand...
Click to collapse
Automated updates work fine for me. It automatically boots onto TWRP, applies the update, and reboots.
Might be a device-specific issue. I am on the OnePlus One, and the same TWRP version (of course made for my device).
I am guessing that perhaps there is an issue reading or writing the recovery script.
Interesting. Sure didn't work for me this a.m. but as I said, far from the end of the world. I also think the "nightly" is going to morph into the "weekly" and that will be fine, too. I have yet to find anything that doesn't work to my satisfaction aside from not automatically picking up my Wi-Fi at boot - not exactly a deal breaker
nezlek said:
Interesting. Sure didn't work for me this a.m. but as I said, far from the end of the world. I also think the "nightly" is going to morph into the "weekly" and that will be fine, too. I have yet to find anything that doesn't work to my satisfaction aside from not automatically picking up my Wi-Fi at boot - not exactly a deal breaker
Click to expand...
Click to collapse
BTW, are you able to navigate to that directory in TWRP?
Oops. Right after I clicked on send I realized I didn't answer your question!!
Yes, and the zip file is there, but nothing happened. As I said, far from fatal.
I updated my opo (Bacon) with the nightly ota download and most recent twrp, after reboot I had lost my home screen (2 of 3 pages remained) and several of the apps that I had dragged to those screens.. didn't work well for me. I let the ota reboot into twrp and it seemed to proceed without troubles until the opo came back to life. (finished booting)
Galaxy S5 SM-G900T here. Wiped my phone and installed lineage-14.1-20170131-nightly-klte-signed.zip with open_gapps-arm-7.1-stock-20170131 the day it came out and it has been good so far, no crashes or freezes and all apps work good except FolderMount, no biggie. Tried to install lineage-14.1-20170207-nightly-signed.zip and is giving me an "error 7 can't install this package on top of incompatible data". Any way to fix this without factory reset? Doesn't make sense to factory reset every week for an update.
Update: Tried to reflash lineage-14.1-20170131-nightly-klte-signed.zip and got the same error. So something must have changed. The only thing I can think of is I have SU 2.79 installed.
Update 2: Removed root, restored boot and same continues. I dont want to wipe on every update.
Sent from my SM-G900T using Tapatalk
Well, now semi-automatic at any rate.
Are you able to navigate to the download directory in TWRP?
/data/data/org.lineageos.updater/app_updates
First, sincere THANKS to jhedfors for this priceless bit of wisdom
Getting better. Still no "automatic update" but the latest "nightly" build did fire up TWRP, and put the update zip file into the aforementioned folder, and after that, installing it was the proverbial snap. I can't speak for everyone, but I would find no horror in the folks at Lineage giving in to reality and calling the "WEEKLY" as opposed to "NIGHTLY" builds.
Hey, since the only device I happen to have running Nougat at the moment also happens to be the OLDEST device I use on a regular basis, the Complaint Department shall remain CLOSED on this one. :angel:
I have an LG G3 (d855) with working LineageOS. The updater downloads OK and the zip is indeed in /data/data/org.lineageos.updater/app_updates, but TWRP refuses to do anything about it on reboot. I can browse to the folder manually, but it does feel that something isn't firing to get TWRP to perform the install automatically.
What is the trigger for TWRP to install a specific Zip on reboot?
D
For me, One Plus 3, automatic updates don't work. Also manually installing the latest
https://mirrorbits.lineageos.org/full/oneplus3/20170214/lineage-14.1-20170214-nightly-oneplus3-signed.zip gives me an error:
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Zip file is corrupt!
Updating partition details...
...done
Any idea?
I did a migration via experimental build coming from cm13 then updated to lineage 14, which worked OK.
But since then I cannot update the daily builds.
I have the "same" issue on a Nexus 6.
The updater tells me I have an update, I ok it to download. Once done, I click install, gets into recovery and stops.
Still in the recovery, if I try to manually install from the downloaded location (data/data/...), it says zip failed.
I reboot and try opening that zip on a PC and sure enough, Windows thinks it is corrupt also.
If I re-download manually from "https://download.lineageos.org/shamu" that copy opens fine on the PC and when moved to the phone (data/data/...) installs fine.
There is something corrupting the zip when the updater does its thing. ;-(
Note: This isn't a migration, I have just been updating "nightlies".
Stuck in the TWRP...
Hi everyone, in trouble :/...I have got an LG d802 and updated TWRP from 2.8.7 to 3.0.2-1, then did a boot/system backup of the current cm 13.0 and after that the "experimental" update (as described in the recent update & builds post on lineageos) from cm 13.0 to lineage 14.1 which worked.
I decided to use lineage updater to go to the latest nightly as described which must have failed (booted in TWRP an did nothing...). When installing the 14.1 nightly manually, TWRP 3.0.2-1 showed two error lines with "unknown command".
Since then I'm stuck in TWRP.
Restore of cm 13.0 backup was not possible with neither TWRP 3.0.2-1 nor 2.8.7, no errors, just wouldn't boot. I can't even find any cm 13 build... to try to back which would be an option of course.
I did wipe the system then, lineage expermental + nightly or just nightly can be installed "successfully" with TWRP 3.0.2-1 and 2.8.7 with no errors there anymore, but also the system won't boot.
Please, please help (and/or redirect me to the right thread), what can I do? Thank you!
First, you can ignore the two errors in TWRP
I've gotten them with each update I've installed, but in my case - an LG v410 tablet - I have successfully, if manually, installed three updates so far, with a few peculiarities. "Automatic" is just a nine-letter word concerning updates at this point. I can live with that.
One - it is going to download it to /data/data in the tablet's storage no matter WHAT I do. I can live with that.
Two - I seem to have to download the update at least two times before the Lineage updater accepts the fact that it is there. I can live with that, too.
Three - a "getting there and almost what I want with no major glitches" Nougat build is much preferred to a KitKat build that LG couldn't give a rat's rear end about supporting, and I can DEFINITELY live with that.
But, back to YOUR problem with being stuck in TWRP. Worst case disaster recovery scenario - ANY chance you have a non-Lineage ROM you can revert to and start over from THERE? Realize what a pain that is going to be, but... When I still had CM 12.1 on it, I once did that out of desperation when nothing else seemed to be able to get it to boot. WHY such a laborious process fixed it I have NO IDEA, but better to have a working mystery than a well understood paperweight.
I ASSUME you have respectable backups of your data, etc.. so that loss of TIME is your major issue ?? Also assume you've wiped the caches, etc..?? You COULD try offloading your data, wiping data, and reloading.
It also seems to take a LONG time to reboot after an update. Can I assume you are at least getting to the Lineage animated LOGO screen or are you hanging in TWRP itself?
nezlek said:
I ASSUME you have respectable backups of your data, etc.. so that loss of TIME is your major issue ?? Also assume you've wiped the caches, etc..?? You COULD try offloading your data, wiping data, and reloading.
It also seems to take a LONG time to reboot after an update. Can I assume you are at least getting to the Lineage animated LOGO screen or are you hanging in TWRP itself?
Click to expand...
Click to collapse
I'm hanging in TWRP, also did wipe data before. I found a full 13.0 backup, selected all but Data because of storage space..."successful"...still system won't boot...
(Power Off in TWRP doesn't even work, just reboots, if that is of any help...)...A wild guess...file system issue maybe?
Yikes
As reasonable a guess as any, I suppose. I admit I've never had TWRP refuse to power off if nothing else, no matter how badly I had screwed things up (often spectacularly) elsewhere.
ASSUME you've tried the hold the power button until it shuts off, after which it should have booted to Android when powered on trick. Or, assuming you can do so, pull the battery?
Perhaps your bootloader is the culprit. Can you just re-flash that?
I got stuck in TWRP Recovery Boot-Loop. Already had the issue before with cm14.1 beginning of december. Didn't they fix the bug or is it another one?
For the specs: I got a Nexus 4 - mako.
I did this FIX and it booted up again as it was before: https://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386
What's now correct update? Download and dirty install manually in TWRP?
Thanks for the post
:good:
I've NEVER encountered that issue so glad to see someone has figured out a more elegant solution. I suspect your CM 14.1 problem is / was device (build for it) specific, as NONE of my CM / Lineage devices has ever done any such thing and they've all been updated several times in the last month.
In every case, however, I 've had to MANUALLY install the update zip file from within TWRP. Far worse things have happened and since I drive a stick shift car anyway, what the problem?
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.
Hello, I am in need of assistance on rooting/my pixel C device.
I was trying to follow the steps outlined in this webpage: https://forum.xda-developers.com/pixel-c/general/guide-unlock-bootloader-install-custom-t3307183/page27
The tablet by itself had 8.1 to start out.
The steps I did so far is
1. Successfully unlocked the bootloader (the 30 second boot time and the beeping noise)
2. Installed TWRP
3. Installed superSU via TWRP
4. flashed the AOSP kernel from this link https://forum.xda-developers.com/pixel-c/development/rom-t3569215
5. Upon system reboot, I noticed two issues:
Issue 1: The apps is pretty empty, including no google play store. I am guessing this was by design, to keep things simple. In addition, I think the original author was saying to install opengapps manually.
Issue 2: Every time I boot to system, I get the message "google connectivity service stopped" error in the beginning (that wording might not be precise). I was able to connect to wifi and bluetooth with no problem, but maybe the connectivity service is responsible for something else, and it is concerning.
6. Another thing I noticed is an issue is when I boot back into TWRP, my internal storage is 0mb. In research it sounds like I need to implement some sort of passcode, as it might be due to the internal storage being encrypted (although I didn't set up any manual encryption myself).
However, when I boot back into system and look, there is no way to set up a screen lock passcode. There is a method to encrpyt the tablet data, but I didn't pursue that, because it projected a long wait time. (If this will indeed fix the problem I will do so)
If I format data through the twrp system, the internal storage comes back.
7. Nonetheless, I was hoping I can still navigate through the system if I just install opengapps. Therefore, I went to opengapps.org, and chose the arm64, 7.1 stock file to download, as this was the default choice it offered (and I couldn't find 8.1- please let me know what the correct one to install is)
8. I then used adb sideload to install the gapps. (As I couldn't access the internal storage)
9. Now, when I try to reboot to system, the TWRP recovery keeps on coming up, every time. Essentially a TWRP bootloop.
My wish is to just get back to the stock 8.1 os with root. Even if I go through a format erase on twrp, the aosp design defaults. Maybe it isn't completely erased?
I have been working days and nights. Maybe it is because I am a novice and a total newb on the pixel C, but looking everywhere it shows similar yet different suggestions, and hasn't been giving me what I am looking for.
Any insight/advice you can give me will be greatly appreciated.
Thank you for reading my long post.
I think I found the correct gapps just by a Google search. It is unfortunate that they're not just out there in plain view on the OpenGapps site. So you flashed the 7.1 apps, and did you get an error message while trying to flash them via TWRP?
To be quite honest, I had a lot of difficulty rooting and flashing a ROM on the Pixel C, myself. The process took me a couple days. I really had to play around with the drivers and the SDK...the latest wouldn't install to my computer unless I installed it using Android Studio. Once I finally had everything set up right, which I can't even remember how I had it set up, it worked. One ROM I flashed didn't boot, and the Lineage one did. Now, I'm on Resurrection Remix, my favorite ROM ever! Hope this helps!
---------- Post added at 08:05 AM ---------- Previous post was at 08:03 AM ----------
I found a link for some gapps for you
https://sourceforge.net/projects/unofficial-opengapps-8-1/files/arm64/20180227/
sabrdawg said:
I think I found the correct gapps just by a Google search. It is unfortunate that they're not just out there in plain view on the OpenGapps site. So you flashed the 7.1 apps, and did you get an error message while trying to flash them via TWRP?
To be quite honest, I had a lot of difficulty rooting and flashing a ROM on the Pixel C, myself. The process took me a couple days. I really had to play around with the drivers and the SDK...the latest wouldn't install to my computer unless I installed it using Android Studio. Once I finally had everything set up right, which I can't even remember how I had it set up, it worked. One ROM I flashed didn't boot, and the Lineage one did. Now, I'm on Resurrection Remix, my favorite ROM ever! Hope this helps!
---------- Post added at 08:05 AM ---------- Previous post was at 08:03 AM ----------
I found a link for some gapps for you
https://sourceforge.net/projects/unofficial-opengapps-8-1/files/arm64/20180227/
Click to expand...
Click to collapse
Hi, I have a suggestion for ya, You can either flash your tablet with the stock rom : https://developers.google.com/android/images , change the recovery to twrp and root your system with supersu Or you can install lineage 15.1 (oreo) + opengapps oreo 8.1 + supersu/magisk15 don't forget to change the vendor image and the boot image also if you want to have access on your internal storage on twrp. Hope that it will help you.
Thanks guys. Since this time, I was able to try different things and was able to get things rooted and erased using a combination of twrp and the original stock rom.
However, during this process, the TWRP recovery was overwritten with the stock one, and when I try to re-flash the twrp recovery using adb (at the Fastboot, using command: Fastboot flash recovery twrp.img ), command line just stalls with no progress.
Has anybody else encountered this before? Any way to re-flash the twrp file? thanks in advance.
I was trying to update the OS on my Nexus 7 2013. I was able to connect it to my PC and unlock it and erase user data using adb commands. But after that it will not go past the Google logo in Recovery or regular Start mode. When I run "adb devices" it does not show up, though my computer does see it since I can run the lock/unlock adb commands and they work. I have uninstalled/reinstalled different adb drivers for the devices. I've tried using 2 different PCs. I can not get adb to fully recognize the device. I tried the Skipsoft Android Toolkit, and it too reports "no device detected".
Have I completed bricked the device? Or is there some way out of this that I haven't though of/found on the internet yet?
I hope someone here can help me!
Thanks!
Assuming you're on stock, try flashing a factory image from Google themselves. This reflashes everything, like stock OS, recovery, bootloader, etc. I'd choose the latest version found here: https://developers.google.com/android/images#razor As long as you understand that this wipes data, then give this a shot and let us know the results!
I found the "Nexus Root Toolkit" windows app. It was able to communicate with the Nexus 7 and restore the factory ROM and I could get it to boot! Now, I've tried about a dozen times to install LIneage, but it keeps getting an error the point of trying to install the ROM, and I haven't figured out what the error means or how to correct it. I've tried multiple TWRP versions and Lineage OS versions. It's driving me nuts!
adamwsh said:
I found the "Nexus Root Toolkit" windows app. It was able to communicate with the Nexus 7 and restore the factory ROM and I could get it to boot! Now, I've tried about a dozen times to install LIneage, but it keeps getting an error the point of trying to install the ROM, and I haven't figured out what the error means or how to correct it. I've tried multiple TWRP versions and Lineage OS versions. It's driving me nuts!
Click to expand...
Click to collapse
Are you trying to install the official version of 17.1? If so, you'll need to look at the install guide on the LineageOS website here: https://wiki.lineageos.org/devices/flox/install
As far as I can tell, you cannot use TWRP, or at least the official TWRP, with this image. You'll need to use the LOS 17.1 Recovery found on the downloads page. If you haven't already, you're going to need to repartition the device with the instructions found on the install guide that I linked.
If this isn't the ROM in question check out the thread for that ROM and see if anyone else has any issues with installation.
NTGDeveloper said:
Are you trying to install the official version of 17.1? If so, you'll need to look at the install guide on the LineageOS website here: https://wiki.lineageos.org/devices/flox/install
As far as I can tell, you cannot use TWRP, or at least the official TWRP, with this image. You'll need to use the LOS 17.1 Recovery found on the downloads page. If you haven't already, you're going to need to repartition the device with the instructions found on the install guide that I linked.
If this isn't the ROM in question check out the thread for that ROM and see if anyone else has any issues with installation.
Click to expand...
Click to collapse
Thank you! I did manage to get 18.1 to flash and load, after using a repartiion tool I found. However, I can't get GAspps to load, saying there isn't enough room on the partition. Now, I'm trying to use NRT to get back to stock (like I was able to do earlier) but now it is getting stuck at the Android 6 startup animation (4 round icons). I'm wondering if it is because I ran the partition update and somehow have to put that back to get the stock ROM to work.
The only suggestion that I would have is to flash the smallest GApps package possible, and before flashing LOS 18.1, wiping pretty much everything, then flashing LOS and GApps. Since OpenGApps doesn't make an Android 11 package yet, I don't know much about the other package providers, but that's all that I can think of. Hope this helps!
NTGDeveloper said:
The only suggestion that I would have is to flash the smallest GApps package possible, and before flashing LOS 18.1, wiping pretty much everything, then flashing LOS and GApps. Since OpenGApps doesn't make an Android 11 package yet, I don't know much about the other package providers, but that's all that I can think of. Hope this helps!
Click to expand...
Click to collapse
I wound up flashing Stock Android 5.0 and it worked. Now I'm updating to 6 via the software upgrade in the OS itself. I feel like this thing is just too old and not large enough memory to handle a custom OS.