I have a little experience flashing roms but I'm far from an expert,
My Shield has had poor performance for over 2 yrs now and I thought I would give a new rom a try.
I've been trying to use Lineage OS 14.1, I think I followed the install guide but the tablet just stays on the boot animation of Lineage OS and has never booted past it. I'd post a link to the lineage os wiki but I'm new around here and the XDA forum won't let me.
I was running Nvidia's stock 5.4 rom until earlier today.
I was able to flash TWRP, 3.2.3-0 and it seems to be installed properly.
- it will flash roms and install zips etc.
I have good access to ADB, Fastboot, and recovery. I can access the Tablet through USB and transfer files from my Laptop. It's running ubuntu 16.04.
I just can't figure out what I've done wrong. Please can someone pass along some pointers?
Thanks
Related
Ideally back to CM11 but to stock would be fine also.
I made a bit of a mess of installing Firefox OS using multirom and now after playing with the recovery I've restored to factory settings hoping that would bring the stock rom back but it didn't. Now I'm left with a tablet with no functioning OS. I've done a bit of Googling but couldn't really find a straight forward guide, if someone could recommend one it'd be great. I looked in the FAQ here and found this thread but don't completely understand it, this is my first Android device so I'm not down with a lot of the terminology and such.
I've got access to a Mac primarily so if any software is required and there's Mac alternatives please suggest them but I can get access to a windows computer if it's required.
Thanks
Ethan795 said:
Ideally back to CM11 but to stock would be fine also.
I made a bit of a mess of installing Firefox OS using multirom and now after playing with the recovery I've restored to factory settings hoping that would bring the stock rom back but it didn't. Now I'm left with a tablet with no functioning OS. I've done a bit of Googling but couldn't really find a straight forward guide, if someone could recommend one it'd be great. I looked in the FAQ here and found this thread but don't completely understand it, this is my first Android device so I'm not down with a lot of the terminology and such.
I've got access to a Mac primarily so if any software is required and there's Mac alternatives please suggest them but I can get access to a windows computer if it's required.
Thanks
Click to expand...
Click to collapse
All you need to do is reflash your ROM, be it CM11 or stock or whatever you want. Download it, put it on your tablet, and flash it from TWRP.
I was trying to install Lineage OS on my Nextbit Robin. I have never done this before, which is why I messed it up. I install TWRP and unlocked my bootloader, but I did not put the Lineage OS ROM.zip file into my internal memory. Sideloading isn't working, and since Nextbit has been bought by Razer, the official stock ROMs don't work, etc. I need help in installing an OS (stock is fine). If you could also guide me through installing Lineage OS, that would also be appreciated.
Thanks!
Let me know if you need more info.
MyerFire said:
I was trying to install Lineage OS on my Nextbit Robin. I have never done this before, which is why I messed it up. I install TWRP and unlocked my bootloader, but I did not put the Lineage OS ROM.zip file into my internal memory. Sideloading isn't working, and since Nextbit has been bought by Razer, the official stock ROMs don't work, etc. I need help in installing an OS (stock is fine). If you could also guide me through installing Lineage OS, that would also be appreciated.
Thanks!
Let me know if you need more info.
Click to expand...
Click to collapse
Why do you use sideloading ?
Just boot into TWRP , go to mount and select enable MTP.
Then connect your phone to your PC and transfer the lineage os zip file ?.
There are unfortunately no ROMs specifically for this device yet, but has anyone tried to use a generic treble ROM on this device?
Thanks in advance
I have tried several treble ROMs, the majority don't even boot. Lineage os worked but was buggy. The more stable one was Havoc, if I remember correctly.
I was interested in the Q developer ROM but it didn't work. I'm back to the stock pie Rom, since there is no Netflix HD support on those treble roms.
gtaadicto92 said:
I have tried several treble ROMs, the majority don't even boot. Lineage os worked but was buggy. The more stable one was Havoc, if I remember correctly.
I was interested in the Q developer ROM but it didn't work. I'm back to the stock pie Rom, since there is no Netflix HD support on those treble roms.
Click to expand...
Click to collapse
Hi Mate, I've been trying to flash a working GSI rom but had no success so far(have an SM-T830). In the past have built ROMs for Tab A 10.1 and flashed them many times with TWRP and Odin so I just cannot understand am I retarded to not being able to flash a working one or what? Have managed to put TWRP 3.3.0.0 and TWRP 3.3.0.1 on the device. Have tried my own arm64_aonly image first. Then an original AOSP one, then a Lineage OS version, at the moment I am just downloading Havoc. The result (apart from the havoc) was always the same. The flashing went through successfully and when I rebooted into system the very fist image came up and boot looped from there. I am always able to go back to TWRP and try another image or through odin can restore the factory image but none of the GSI images seem to be working. So, here is my question. As you managed to get a Lineage and Havoc working, can you tell by looking at it what am I doing wrong please:
1.: OEM unlock
2.: TWRP install with odin
3.: Boot straight into TWRP to prevent being overwritten
4.: TWRP: format data
5.: Flash system image (arm64_aonly)
From here have tried so many things like,
- booting straight into system
- booting back to recovery
- flashing the force_decryptor or how the hell is that called
- formatted data again as the decryptor suggests
The result was always the same, boot looped from the very first image. It seems like that the image is not getting flashed and even if TWRP says was flashed right it is just not there. I'm literaly pulling my hair as it was so easy and straight forward with the Tab A 10.1, but with this ….. thanks for your answer in advance
anyone have any luck with treble GSIs? i can only get arrowos to boot and even then i cant install gapps.
droidbot1337 said:
anyone have any luck with treble GSIs? i can only get arrowos to boot and even then i cant install gapps.
Click to expand...
Click to collapse
I used AOSP 9.0 and LineageOS 16 with OpenGApps Pico and both work but are very buggy.
After hours of trying to figure this out myself i ended up finding two ROMs that work for me. I was running stock Android 9 with september's security updates when testing these out:
Roms that i tried, that did NOT work:
BlissOS
ArrowOS
Lineage16
The ROMs that DID work for me were:
phunsson's Treble Experimentations
microG ufOfficial
The only 2 bugs that i've seen so far have been a small graphical glitch of quickettings not staying within the bounds of the pulldown and MTP not working at all. These are both present in both ROMs (The microg ROM uses phhusson's rom as the base). Neither of these bother me all that and i'm very happy to be able to move to microg and not have all the google/samsung bloat hogging my tablet and constantly trying to ping their motherships.
Here's a great list of Generic System Image (GSI) ROMs that you can click scroll through and try downloading and flashing to your device to see if you have any luck.
My process of installing phunsson's GSI ROM:
Reboot to TWRP,
Do a factory reset (Wipe > "Swipe to Do Factory Reset")
Install Image
Reboot
Took about a minute and a half displaying the bootanimation before it got to the home screen for the first time. If it's loading for more than 5 minutes then that ROM definitely isn't going to work with your device.
Hope this helps someone out there trying to get away from their bloated Samsung One UI.
motomotomotoG said:
After hours of trying to figure this out myself i ended up finding two ROMs that work for me. I was running stock Android 9 with september's security updates when testing these out:
Roms that i tried, that did NOT work:
BlissOS
ArrowOS
Lineage16
The ROMs that DID work for me were:
phunsson's Treble Experimentations
microG ufOfficial
The only 2 bugs that i've seen so far have been a small graphical glitch of quickettings not staying within the bounds of the pulldown and MTP not working at all. These are both present in both ROMs (The microg ROM uses phhusson's rom as the base). Neither of these bother me all that and i'm very happy to be able to move to microg and not have all the google/samsung bloat hogging my tablet and constantly trying to ping their motherships.
Here's a great list of Generic System Image (GSI) ROMs that you can click scroll through and try downloading and flashing to your device to see if you have any luck.
My process of installing phunsson's GSI ROM:
Reboot to TWRP,
Do a factory reset (Wipe > "Swipe to Do Factory Reset")
Install Image
Reboot
Took about a minute and a half displaying the bootanimation before it got to the home screen for the first time. If it's loading for more than 5 minutes then that ROM definitely isn't going to work with your device.
Hope this helps someone out there trying to get away from their bloated Samsung One UI.
Click to expand...
Click to collapse
Did AOSP 10.0 work for you? I haven't been able to get it to boot. Strangely AOSP 9 and LOS 16 are the only ones I've had luck with.
@last1youlove whoa! You got LOS to work? What kind of magician are you? That one never booted for me. The only ROM I got working was ArrowOS and it has a few bugs. I really want to get HavocOS to work but it's a no-go!
droidbot1337 said:
@last1youlove whoa! You got LOS to work? What kind of magician are you? That one never booted for me. The only ROM I got working was ArrowOS and it has a few bugs. I really want to get HavocOS to work but it's a no-go!
Click to expand...
Click to collapse
Strange, How did you go about installing it?
last1youlove said:
Did AOSP 10.0 work for you? I haven't been able to get it to boot. Strangely AOSP 9 and LOS 16 are the only ones I've had luck with.
Click to expand...
Click to collapse
I have not. I just really wanted an AOSP based ROM and i had gotten to the point where i had reflashed the stock firmware 3 times through ODIN because I messed up 1 thing or another. So once i got a functional ROM that worked great I just decided to stick to it. Also I don't think Android 10 has Xposed support yet, and i need that in order to enable Signature Spoofing for MicroG's FakeStore.
Hello everyone,
A few weeks ago, I bought a reconditionned OnePlus 5T and installed /e/ on it. Now, I would like to install back OxygenOS.
My problem is that I can’t manage it.
As I couldn’t access to recovery (TWRP) anylonger (don’t know why, maybe something to do with the fact I flashed the 5.1.7 firmware a few days ago, I don't have a clue), I flashed an early Blu Spark one (3.2.1 as the 3.3.x ones won't work on my device). And it worked, I can access recovery through this one.
But when I try to install any OOS zip, via recovery Install menu or by sideloading it (downloaded from the OP website (the most recent one, or from the mirrors referenced on this xda forum, I tried several zips but don't really know which one is really relevant), it fails.
And the only thing I can do is installing back /e/. I tried several ways of doing it, following several guides but even the ones for the ultimate guide available on the One Plus Forum won't work (can't make it recognised by any device manager, maybe the fact that I'm running Ubuntu and not Windows).
So that, for the time being, I’m stuck with /e/OS (based on a LineageOSrunning Android 8.1).
There surely is a step or a file I missed, but which one... Any idea anybody ?
I finally got it working. Through the*********** 's guide.
donatienb said:
I finally got it working. Through the*********** 's guide.
Click to expand...
Click to collapse
Hi !
Im interested in going back to OxygenOS from /e/os because the new builds are on android 11, and my current /e/os build is on android 8.1
The idea is to get OxygenOS back, upgrade using OxygenUpdater, and then install de latest android 11 /e/ build.
So what was the name of that guide ?
Thanks
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.