Device empty after attemting to install Lineage OS - Google Pixel Questions & Answers

I attempted to install lineage os on my google pixel, but somehow ended up with completely empty storage. I managed to get TWRP to boot using fastboot, but can't copy the factory image onto the device to reinstall it (whenever I try, a window comes up that says "preparing to copy" with a progress bar and it just sits there or it errors and doesn't copy at all). Does anyone know how to fix this?

nevermind, I got it to work.

Related

TWRP won't mount anything

apologies if this has been covered already.
I have an Asus Transformer Infinity TF700T, I installed cynogenmod 10 and gapps, and then wouldnt boot past splash screen, so I found out to install a new bootloader. after I did that, I could boot into Android, but it was like a brand new installation. My apps were all gone (which may or not be normal). I had to install a file manager and I found that my files are still there, so I wanted to reattempt a google app installation because I didn't have any google apps. When I booted, It requested a password. I have no idea what this password is supposed to be, and I can't find any info anywhere. so i gave up and hit cancel and nothing is mounted. I tried to mount stuff, but the screen seem unresponsive when i click those areas. I cant clear any data or anything because it isnt mounted, I cant restore my backup because nothing is mounted.
Please help me. Thanks in advance
I may have found something. Im using goomanager to install a later version I think
Ok, that fixed it. I just wish I could get all of the apps.

Problems when updating a previously rooted Nvidia Shield Tablet [MOVED HERE]

[This was already posted, I just moved it to the Shield Q&A.]
As many of you may know, Nvidia has recalled their Shield Tablets. I'll be getting a replacement soon. I'll be rooting it as soon as possible when I get it, but first I have a few questions.
First of all, I rooted my tablet using a guide at IBTimes (that used info from XDA forums) installing CWM recovery.
After rooting I installed Link2SD, pretty much the reason I rooted, to save up some space on my internal memory. Everything was going fine, until I received the recall notice. I moved all my app files back to the internal memory, deleted Link2SD, ran a full unroot on SuperSU, (after a while of hanging on the "Please Wait" screen the app just crashed, it wouldn't load up and Root Checker said I had no root access after rebooting.
I don't know whether this was supposed to happen or whether it should have gone more smoothly, please give me an answer to this and tell me if it affected my system in any way) and fastboot flashed the stock recovery.img.
However when I tried to install the update, I got a red triangle error. After checking the log I got an error saying "Package expects build fingerprint of ... or ..., this device has ...."
I can't remember what the fingerprints were, but the first one was something that began with "nvidia/", had a bunch of numbers in the middle followed by an underscore, then it ended with "/release-keys".
However the device's current build fingerprint was exactly the same as the first, except that it cut off halfway through, right after the numbers and the underscore.
I tried resetting my cache, I tried a wipe of the user data. The only way to fix this for me was to re-install a bunch of stock images - recovery.img, boot.img, system.img, etc.
I don't want to wipe my data next time. So I ask for this in my answer:
- An explanation of what the error means
- How this error is caused
- A way to fix this error without wiping my device
- How to prevent this error
- If what happened to SuperSU in my case is normal and if it affected my device in some way
- And, if possible, a way to install the update successfully without getting this error and without having to unroot or remove CWM, and details on how to do this method and any risks.
Thanks in advance. An answer soon would be appreciated.
Quick answer:
- You don't need to restore to full stock before updating to the latest OTA. This is what I did, running a rooted stock system with TWRP recovery:
-- Go to Settings > About tablet > System updates and continue to click Check Now until the update has been found. I had to click like 4 or 5 times before it was found. It'll download automatically to your device (not your SD card), but I forget where that download location is... XD
-- once you've found your downloaded OTA.zip, copy it to a location you can easily find from your custom recovery.
-- reboot into custom recovery, flash OTA.zip, reflash superSU.zip, wipe cache NOT DATA, reboot
-- wait until device boots up, wait until the Optimizing blah blah process is done.
-- enjoy!
Additional thoughts:
- I've tried the Link2SD app, but I think it messes with my system in a way I don't like; personally I'd rather delete the apps I never use via custom recovery (see THIS THREAD on how to debloat your tablet for yourself!
- I think your error happened when you flashed stock recovery on top of the custom one. To prevent this next time, simply wait for either a flashable zip in THIS OTHER THREAD, or you can check to see if nVidia released any OTA3.1 recovery images if you want that full-stock experience.
Hope this helps!

Help: files pushed with adb are now almost completely invisible

I have been using Nitrogen OS on my OnePlus 3T. I decided to try a Pie ROM, didn't like it, and wanted to revert back. I was having issues with TWRP mounting storage, so I decided to back everything up and wipe.
I used adb to pull the entire sdcard to my computer and verified all the files. I did a complete wipe in TWRP, then pushed the entire sdcard directory back to the phone. I verified everything was there with TWRP, then used it to restore from my last backup, and rebooted. Everything was totally normal.
Now, a day later, I've noticed that my files are not appearing in file managers. I don't know when this happened, whether it was first restart or what. They are on the phone, and taking up space, as can be verified with DiskUsage app, but they are just listed as 40 GB of "System data." See attached screenshot. My Files app can actually show some files, but they are listed as "Unsuccessful" and have no other info. See other attached screenshot. They no longer list in TWRP file manager either.
What gives? How did my files get turned invisible and "unsuccessful"? And can I get them back into usable files? Should I wipe, push backup file, restore, then push the rest?
Side note: TWRP now constantly asks about system modification, despite ticking the box to never ask again every time.

Help on how to install Lineage OS 14.1 on HTC ONE S

I would like to install Lineage OS 14.1 on my HTC ONE S, I believe this is the latest version available for this phone. I state that I am not an expert so I kindly need your help. Before installing Lineage OS I have to delete everything in the device, the fact is that this phone has no microsd so if I do a wipe advance and select internal storage it deletes everything including the lineage OS ROM file that I transferred … What should we do then? Also because I noticed that the phone when it is in TWRP is not seen by the PC so I cannot transfer the ROM file again and if I also delete the internal storage I cannot start the phone and I cannot even put the new ROM file ... I ask you how proceed in this case .. Thanks.
Update on the situation, practically I had to install windows 7 in dual boot as with windows 10 it was impossible, so to solve and be able to install an updated version of TWRP and do all the procedure that I am writing to you below, unfortunately I was able to install lineage os 14.1 but the apps don't work well .. Practically the first app I tried is Aurora store which however does not load well and as soon as I write an app to look for it crashes, I also tried aptoide and I see that it also works badly, it does not crash like the aurora store, but it does not load all the graphics of the app icons and then if I try to install it gives me an error to access the internal memory even though I gave it permission, in short, there seems to be some general problem .. Here is what I did before installing Lineage OS, I practically had an old version of TWRP 2.6 and I updated to 3.6 after which I did an advance wipe (Davilk / Art Cache, Cache, Data, Internal Storage and system) and this appeared to me that found in the first screen attached, where it says in yellow, "stock theme version does not match TWRP version" in practice from what I understand it says that the wipe was done with a different version of TWRP than when you are installed the ROM, did I understand correctly? Is this a problem? So I only made a wipe advance of what I wrote above, did I also have to do a format data or is it already included in what I did? After that I transferred the ROM lineage OS 14.1 (ville) on the internal memory and I made the flash. When the phone starts up, the red writing appears at the bottom. Is it normal that it appears even if I do not have root? Because before I had root I had it and now that I have put lineage but without root I see it anyway .. I do not know if it is normal ... what do you advise me to do to solve the problem of apps that work badly? I haven't tried other apps but I think these 2 are already enough to understand that there is a problem. Thanks a lot to those who want to help me.
u need hboot 2.16 for lineage os 14.1

7 Pro stuck in boot after removing Magisk

I've been having a bunch of problems recently with my rooted 7 Pro including Magisk Manager constantly "keeps stopping", not being able to access Hide to add new applications, banking apps starting to detect that I'm rooted and camera issues: the camera app not starting, the camera not popping up automatically and the image being usually reversed and occasionally upside down as well, depending on the app I'm using.
Given that Magisk appears to be dead/dying, having lost its developer to Google, I thought I'd start by getting rid of that and then performing a firmware upgrade in necessary to see if that fixes the other issues.
I uninstalled the Manager then ran the uninstall zip within TWRP. Rebooting though hangs on the initial "ASUS" screen.
I can get back to TWRP ok so I guess I'm not bricked yet. My next thought was to try a system upgrade but I seem to need to know the exact version I need, which, seemingly, I can only get via a working phone?
From the back, it says only model I002D along with SN and IMEIs.
I've done a TWRP backup to the external uSD card, and I have a syncthing copy of all of the internal memory that I can access without root.
My questions:
1. Is there something there which can help my figure out which firmware I need to download?
2. Is there any way to install this without wiping the phone?
Please see this post.
When I try to burn rom with TWRP, img burns but it doesn't start and zip gives an error and cannot burn.
When I first burned custom ROM (unofficial AEX), it did not start, so when I deleted the data from TWRP, it seems that I deleted things that should not be erased, so even if I burn it from the zip file, with the error message in the image below I...
forum.xda-developers.com

Categories

Resources