Related
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.
Hi all,
so today I found a treble-enabled ROM of Android Pie and wanted to flash it. Thing is, I need to enable treble for me first. The treble check says that Treble is indeed supported, and so does the OnePlus website, but I don't have access to the vendor partition in TWRP. Using TWRP 3.2.3-1, by the way.
So, I read that MoKee enables Treble. Tried that, flashed the rom, flashed the radio and then the rom, factory wiped, flashed rom, factory wiped, flashed radio and rom, nothing. Still can't get Treble support. Then I tried kylothow's Trebliser, but nothing there either. I am realy at a loss here - I even reinstalled OOS (newest beta of course) and I couldn't get the vendor partition to show up, which is weird considering installing said trebliser actually states "Vendor partition found, good!" when installing, and then proceeds to in fact patch the vendor partition. It just doesn"t do anything, I can't install GSIs, can't even get the treble check to register that I do in fact have treble.
So this is where I turn to you guys. Do you have any idea what I could do in this situation? Please answer genuinely and don't post "just wait for an official android p".
Thanks!
Okay there's a few things remember here after flashing the mokee trebleize pack you should have had the addition of the vendor partition included in your TWRP file system if you have the blue spark TWRP version YOU SHOULD BE ABLE TO SEE THE ADDITION OF THE VENDOR PARTITION WHEN YOU GO TO MOUNT FOLLOWING THAT.
*** Make sure that after the trebleize is installed or whatever don't touch vendor partition ever just leave it alone you don't need to do anything to it it's fine if some ROM needs to update it you don't have to worry about wiping it first because it'll take care of that with the configuration script in the zip file. Even if you want to go back to a regular Android 8. 1 ROM you don't have to worry about the vendor partition the way it's set up the vendor partition that exist inside the one plus 5T that was created for Treble is not seen by any AOSP ROMs so it's going to create its own vendor folder inside of the system partition like it normally does and that you will not conflict because the fs tab does not Mount the new vendor. By leaving vendor alone and never touching it you're just ensuring that when you flashed yes eyes you're not missing something that's essential to the boot up process and it's one thing that you can from any potential uncertainty as to why a treble mage may or may not be booting.
Follow this....
Normal Android ROMs you would usually wipe system data cache D-cache if you were going to install a new ROM that wasn't just an upgraded version of the one that you were already running you'd have to start from scratch always. This is still what you should do it whenever you want to start and flash a fresh regular ROM or treble run always do that but it's how you proceed from here that is a little difference between the two.
With a regular ROM you would just go on to flash the ROM that you want to install followed by Gapps and so on.
When you want to flash a treble image you need to be on a clean fresh ROM that has treble support already good to go in that it can see that vendor partition that was made before and that it contains the binderized HALs needed as well. Because official treble support is still in beta with the OnePlus 5T the only officially supported treble Android 8. 1 ROM is mokee so you always want to start with a clean flash of the Mokee ROM because it also contains the supported kernel and ramdisk and other things as well.
Upon flashing a fresh version of mokee you want to go ahead and Flash no-dm-variety to ensure data is not encrypted because it will lead to a bootloop and the only way to get it to work will be to either format your SD card or to install the no variety which is the way to go just install it every time you flash mokee so that way you know everything is good.
**** I've only had experience using Android 8. 1 GSi so I'm not sure exactly how it would work concerning open G apps because I've only had to do it with two 8. 1 apps I'm not touching the Android P treble ROM until it's official so anything that I'm saying here has nothing to do with that if that's the image you're trying to install that I can't help you with it because I don't honestly know I remember reading something about that changing something different with it and I got to read up more on it.****
So next part depends on whether the GSI you're trying to flash comes with GFS included inside of it some do some don't I think most do but just make sure you read the instructions on the forms from where you download them from where they will tell you about the gf's the ones that I've installed that didn't have gf's on I would install mokee then I would flashed gf's to mokee but I've seen ones where people have flashed the gf's after flashing the treble images well and they didn't have any problem so just make sure you read into that one. obviously if the GS I can change the gf's then don't flash any before flashing or after as it will be flashed when we install it to the image and everything will be.
Which brings us to the last part if you did everything right up to this point then you should have no trouble installing the GSI through either TWRP or fastboot but before you do just make sure you go back to White and you just swipe to factory reset again so that we know that we cleaned out the data and we're on something clean after on encrypting the data if you did Flash no variety but remember don't wipe any partitions you want to make sure that you leave mokee on there. if you do it correctly you won't even need to wipe anything afterwards you should literally just need to be able to install the image into the system partition now and then reboot and it should work fine
It's your choice on how to go about doing it I've had success with TWRP but I've had more success using the fastboot method if for some reason you do try TWRP and it flashes and says success in 10 seconds then just reboot to fastboot mode in just flash it from there because you probably going to run into an issue just factory reset it again before you do it by swiping you don't have to wipe any of the partitions leave those alone.
So either go to the fastboot route which is put the phone in fastboot Point your terminal to the area where your GSI is located on your computer and then type fastboot flash system xxxGSI NAMEXXX.IMG.... OBVIOUSLY REPLACE THE FIRST PART WITH THE ACTUAL NAME OF YOURS. Next press enter and give it a few seconds and then you should see it's a success at which time you can reboot the phone and it should boot after a few short minutes.
If you wanted to use the twrp I believe I saw something about how you have to be on version 3.2.2 or above most likely for blue spark version as I use that one because it has treble support and I can see the vendor image even though I don't touch it. So if you flash it here you want to make sure instead of rebooting to fastboot like before you would just go to install and select image then find the image on your phone select it and then select the system images where you are installing it and then wipe the bar at the bottom for Flash and then upon it finishing you should hit reboot and let the phone boot up the first time set it up and then you can go back and you can go back to TWRP if you want to flash magisk or any other modules or TWRP Zips I've stated first then make sure you move the phone and go back and do all the modifying after otherwise you're getting stuck. I hope this helps feel free to contact me if you have any trouble.
theandroidas said:
Hi all,
so today I found a treble-enabled ROM of Android Pie and wanted to flash it. Thing is, I need to enable treble for me first. The treble check says that Treble is indeed supported, and so does the OnePlus website, but I don't have access to the vendor partition in TWRP. Using TWRP 3.2.3-1, by the way.
So, I read that MoKee enables Treble. Tried that, flashed the rom, flashed the radio and then the rom, factory wiped, flashed rom, factory wiped, flashed radio and rom, nothing. Still can't get Treble support. Then I tried kylothow's Trebliser, but nothing there either. I am realy at a loss here - I even reinstalled OOS (newest beta of course) and I couldn't get the vendor partition to show up, which is weird considering installing said trebliser actually states "Vendor partition found, good!" when installing, and then proceeds to in fact patch the vendor partition. It just doesn"t do anything, I can't install GSIs, can't even get the treble check to register that I do in fact have treble.
So this is where I turn to you guys. Do you have any idea what I could do in this situation? Please answer genuinely and don't post "just wait for an official android p".
Thanks!
Click to expand...
Click to collapse
Bro can u plz tell me how to get back to 8.1 oreo i am on 9.0 and didn't get treble support
My 18month old NX5 just switched off in my hand this morning and wouldn't boot past the Google logo.
After a quick Google I realised it was probably the dreaded boot loop; short version is after following an XDA guide to install a patched boot image that shuts down cores or something.
What I really want to know is that it? Will my phone get worse and worse? Should I start shopping around for a replacement?
@mattspew, you may try to start cleanly instead of BLOD patches:
format internal storage, wipe the other partitions, flash the latest firmware and let it boot... If it loops again, I would go shopping: the patched system is slow and may crash nevertheless.
I was running LineageOS when the phone first died; a full wipe and going back to stock was the first thing I tried.
Currently back on "patched" LineageOS and the phone does feel pretty slugging and lots of app crashes.
Thinking about buying a Pixel, or anything really, that I can install LineageOS on with reasonable specs.
Full wipe and formatting is different. I repaired a bootloop this way.
I'm not sure it's worth the effort; not even TWRP would boot until I installed the special patched version.
I'm also pretty sure installing stock using the Google provided script does format partitions.
EDIT: Did it anyway, format and installed stock ROM, still dead. IT'S DEAD JIM!
For what it's worth; I went bought an Oppo R15 today. Seems pretty nice with Nova Launcher.
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.
Hello, Sorry to bug you guys...I read multiple different fourms/how2s and I guess I'm a little mixed at what i should do. I Have the oneplus 7t (hd1505) with android 11 rooted, and after that I installed NikGapps after I had it rooted, then flashed nethunter. Was in the terminal as root, all was well..I believe It rebooted and would'nt boot to rom so i went and re'did magisk, may have used a different patched magisk? but now is stuck fastboot. Cant get it to boot.
Sorry for the maybes but I had brain surgry and my memories not the best. Everything was going fine so I didn't document things like normal. Anyways, Is there a program that helps with thiss? MSM somthing? or could anyone please point me in to a nice how2 or some quality links to assist? I really apprricate it, normally I'd just test till I get it, but I think I may be at a point where I could really mess it up.
5k1tz0 said:
Hello, Sorry to bug you guys...I read multiple different fourms/how2s and I guess I'm a little mixed at what i should do. I Have the oneplus 7t (hd1505) with android 11 rooted, and after that I installed NikGapps after I had it rooted, then flashed nethunter. Was in the terminal as root, all was well..I believe It rebooted and would'nt boot to rom so i went and re'did magisk, may have used a different patched magisk? but now is stuck fastboot. Cant get it to boot.
Sorry for the maybes but I had brain surgry and my memories not the best. Everything was going fine so I didn't document things like normal. Anyways, Is there a program that helps with thiss? MSM somthing? or could anyone please point me in to a nice how2 or some quality links to assist? I really apprricate it, normally I'd just test till I get it, but I think I may be at a point where I could really mess it up.
Click to expand...
Click to collapse
If you don't care about data then use msm tools to factory restore. Or you can flash boot image of the rom you were using (unpatched) in fastboot mode itself.
No need to keep data, I'd prefer to wipe device and start fresh instead of getting stuck on the concept of A/B partitions. I get the CMD getvar, but I'm not sure if i flashed the lineage OS to one or both...at 1 point i think i was booted in A, now its saying B. I got overeager and downloaded multiple ROMs and not sure which one worked. In the past I usually downloaded a few and the first one to work I used. Not smart...I know. If I wanted to wipe all and start fresh with gaspps and root, where/how should I do that? I can't just fasatboot oem unlock , could I? Would you recommend stock OS? Lineage? Thanks for your help BTW.
5k1tz0 said:
No need to keep data, I'd prefer to wipe device and start fresh instead of getting stuck on the concept of A/B partitions. I get the CMD getvar, but I'm not sure if i flashed the lineage OS to one or both...at 1 point i think i was booted in A, now its saying B. I got overeager and downloaded multiple ROMs and not sure which one worked. In the past I usually downloaded a few and the first one to work I used. Not smart...I know. If I wanted to wipe all and start fresh with gaspps and root, where/how should I do that? I can't just fasatboot oem unlock , could I? Would you recommend stock OS? Lineage? Thanks for your help BTW.
Click to expand...
Click to collapse
Go to this thread for MSM Tool download and instructions: Unbrick tool to restore your device to OxygenOS