Hello, first of all I want to apologize for any grammatical mistake since I do not speak English and this text was translated through a web page. Let's start, for a long time I came with emotions to try custom roms on my device (motorola moto g7 play ((XT1952-2)), I decided to try the lineageOs and to my surprise I managed to make it work, but I did not have the Gapps so I wore To investigate to install them, after investigating, I tried to install them but everything went wrong, very bad, the cell phone had been soft bricked and I was about 5 hours trying to solve it since the bootloader had been blocked and there was no way to install ANYTHING, After solving it, I found that I cannot install LineageOS in any way, I spent about 4 hours testing and it always throws me an error and this affects the entire device since I have to use the Motorola assistant on every failed occasion ( Rescue and Smart Assistant), I attach one of the problems that I get when trying to install the OS. I hope a prompt solution, thank you very much
Instalando archivo zip
Buscando archivo digest...
Step 1/2
Error applying update: 28 (ErrorCode::kDownloadOperationExecutionError)
Proceso Updater terminó con ERROR : 1
Error instalando archivo zip
Actualizando detalles de la particion
I tried in all the ways I could but did not reach any solution, I only use the stock motorola firmware, but the fact of installing a custom rom rejects it anyway.
I will keep this simple and short but what did you use to flash Lineage, before the Gapps problem? What it sounds is your problem is one of two things, 1) are you wiping data partitions after each flash cause it will boot loop if you don't, and that leads to it then trying to switch to the other partition slot, and it still may see data (encryption) exists and from the stock rom, so it constantly reboots and trust the inactive slot the next time and on it goes. Check postings about booting twrp, flashing the rom, then boot twrp again, then wipe data and install Gapps. That should solve the problem. Oh, if you get stock running again and fix the boot loop, I recommend a full twrp backup to a safe place (external sd) to restore from. All this before the initial Lineage flash is best. This big thing is remember these phones have two slots, running the live instance in one slots, the other laying dormant for updates. When flashing Lineage twrp tells you the slot letter it's flashing too. After, always check for the slot when flashing Gapps, magisk. If not, you got switched up
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.
Hello,
It all began that i just wanted to restart my Oneplus3 unlocked with lineage 15.
But then back in Lineage15 i wasnt able to use my pin anymore + it restarted after few seconds...
Afterwards i ended up in a lineage bootloop.
Ok, then i thought then i do a fresh flash with new lineage 16.
I tried to flash but it said i need to install new modem firmware for Lineage16.
I downdloaded the new 9.0.5 modem + firmware and flashed it from here : https://forum.xda-developers.com/oneplus-3/how-to/op3-flashable-firmware-modem-zips-t3816066
Then i tried to flash LOS16 again but it failed due to some errors on unable to mount some partitions (cache , system, etc).
So i thought i need to wipe or reformat them, as some people suggested to switch from ext4 to fat and back to reinit the partition.
I did this for at least system and internal storage. ( i learned that it was a dumb idea )
Afterwards i was not able to push anything anymore through MTP in TWRP, but i was still able to sideload or push images via adb.
Afterwards i tried to flash LOS16 or LOS15 via TWRP again but it always ends up to a "unable to mount /system (invalid argument" error at some point of the installation.
I thought: Okey maybe i go back to stock as i messed up the internal file system somehow, and go back to LOS afterwards.
So i flashed the stock recovery for nougat which i got from here: https://www.****************/2017/0...th-latest-oxygen-os-firmware-complete-unroot/
Then i tried to flash various stock Oxygen roms with the stock recovery, by using wipe + system reset + adb sideload:
4.02, 4.51, 5.08, 9.0.5
4.02 and 9.0.5 didnt run until the end.
Flashing 5.08 works but ends up in a black screen when starting it.
Flashing 4.51 works but when i start it i run into a bootloop ( 2 Dots circuling forever )
I also tried to use the 4.51 version to flash LOS again but it did not work out
I just tried again to flash 4.51 but it also didnt work out anymore. :\
So, what do you think i could do to get a working OS on my system again?
Did i do something on the installation of LOS or Oxygen ?
Can i use a backup from a friends Oneplus3_T to get a working system partition / full OS again?
Should i unbrick the phone by using one of various guides to go back to fully stock? I am kind of afraid of this, as some people describe some final brick in the threads which may be caused by modem firmware problems (Sahara issue). https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/ or https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Thank you so much, i kind of getting mad about it
@julledd
Backup from 3T seems like a bad idea.
You may have a hardware issue.
Your best bet is to use one of the tools available in the various unbrick guides. If one doesn't work, try another.
Best of luck!
Hi thx for your help!
i tried different unbrick tools (9.0.5 / 3.1.2 / 4.0.5) and after several attempts i get it flashed to the phone. But in the end it still ends up in a bootloop, either at the android logo or the circuling dots. Via Sideload i am also not able to flash a new OS. It always breaks somewhen >50%.
In very rare cases i am then able to go to the OS, but when i go to "About Phone" to unlock it for TWRP, it freezes before showing anything. I guess there is internally something broken which forbids it to show the internal state of the phone. Every boot is different, and i cannot see any system in this failure of my phone.
Do you have any more hint?
I am already at a point where i want to exchange the main PCB.. Is this possible for the Oneplus3? Can i also exchange it with a Oneplus3T PCB?
Hello, I really missed the "how to install" section on [ArrowOS 10.0] and got screwed :c
Everytime I try to Install via TWRP I get the "E2001: Failed to update vendor image. Updater process ended with ERROR: 7", and I don't really know what's going on; I saw no TREBLE stuff on this post and went step-by-step on tutorials, but every single time it stops on this error. Actually, afaik having Treble wouldn't be a problem since I came from stock ROM.
The very first time I was on ZUI 4.0.199 and now I'm rolling ZUI 3.5.225 DEV through TWRP (which is the only stock thing I actually managed to install), am I missing something?
It might be something really simple and stupid, so if someone notice it please say it!
I suspect my phone didn't have the 3.5 firmware (which seems to be a requirement), right now I'm searching for the right file to flash.
What I did:
Unlocked Bootloader
USB Debugging
TWRP-3.3.1-0-z2_plus
Didn't go TREBLE or something
Tried wiping everything (Dalvik Cache, System, Data, Cache...)
Reason:
I tried flashing a Custom ROM due to few problems/bugs I had on ZUI 4.0.199 (my phone started rebooting and sometimes it kept rebooting until I charged it). It started annoying me when it kept forgetting WiFi passwords, but since it became almost useless due to rebooting I decided it was time to flash a new ROM and see if I could save my Zuk...
That's how I ended up in this mess, it seemed fairly simply to do but I got lost in the process.
Solution:
Installed 1.9.044 through QFIL, uptaded to 3.5.261 via OTA-Recovery and to 4.0.199 through normal OTA (System Update).
Unlocked bootloader, installed TWRP, did factory wipe and installed ArrowOS 10 (install + cache stuff wipe that appears after installation).
I'll proceed to back up, rooting and mods.
Case closed xD
Hello everyone! I need some help because i'm out of ideas how to resolve the softbrick on my old phone. First i'll explain how i got it in this state. Brace yourself, it's a long story
So i have 2 meizu note 8 i don't use anymore (one with broken touch and lcd, and the other was perfectly fine), and because of boredom and covid restrictions i had the "brilliant ideea" to mess with them and update to android 10 with GSI treble roms. The original android was flyme os 7.1.6.1 EU. First i unlock the bootloader on both and installed twrp recovery. No problems so far , everything worked fine with flyme os. Then i tried to install gsi android 10 with twrp on one of the phone (the one that does not have the screen broken). I had an error with system partition not mounting , so i did a full format in twrp (cache, data, system,internal storage, boot,vendor) and then i managed to flash it. Android 10 GSI (Havoc Os) booted up but with problems : First i got a message right after boot "There's an internal problem with your device. Contact your manufacturer for details" then the config wizard crashed constantly, but i managed to finish the process and android is working (sort of ).The problem wich i called it soft brick is the fact that wifi, data sim,bluetooth, gps, sound are not working (not detected, nada....).Both IMEI are correctly recognized, but the basic functions of the phone don't work.
Having another identical phone with original firmware, i made a full twrp backup (21 partitions..with system,data,cache, modem,kernel,vendor ....everything) and restored it on the culprit. Flyme os booted up but with the exact same symtoms as with GSI 10. It seems i messed up somewhere so i reverted back to stock flyme os recovery and flashed the original software (update zip form their website). Still the same symtoms. So I went further and got the flyme os files for QPST / QFIL flash tool. Flashed it successfully with QFIL but no improvements. I suspected the modem firmware being corrupt and flashed it separately, but i just can't get it to work.
So any ideas? I have the msm partion table and trying to pull everything with adb root and adb shell from the other phone, and restore it back to the other, but got stuck somewhere....(i'm doing more research).
I'm asking a moderator, please delete this post. Got it resolved and I have another post with an explanation.
Trimis de pe al meu Redmi Note 9S folosind Tapatalk
For almost a month now I have been happily using LOS 17.1 on my Xiaomi Redmi Note 8T (flashed via LOS recovery, everything working great), until yesterday all of a sudden the OS crashed (I actually don't know what happend, I put the phone away and when I wanted to use it again I just saw the boot screen). Now the phone wont boot to OS no matter what I do (restart, turn off and on, fastboot and back), but I can still enter recovery.
What the hell happened??
What I can do to fix it - e.g. reinstall LOS/install last update?
Will any of the steps to fix it remove the data on my phone?
lueromat said:
For almost a month now I have been happily using LOS 17.1 on my Xiaomi Redmi Note 8T (flashed via LOS recovery, everything working great), until yesterday all of a sudden the OS crashed (I actually don't know what happend, I put the phone away and when I wanted to use it again I just saw the boot screen). Now the phone wont boot to OS no matter what I do (restart, turn off and on, fastboot and back), but I can still enter recovery.
What the hell happened??
What I can do to fix it - e.g. reinstall LOS/install last update?
Will any of the steps to fix it remove the data on my phone?
Click to expand...
Click to collapse
1-delete the folder : data/system/dropbox
reboot,and when the system restarts , read logs in that folder to know what is happening
2-if you didn't remove any important system file, reinstall will fix nothing
3-in most cases,wiping data will fix the problem, just be prepared to it
your best shot would be making a twrp backup of data and explore it with 7z and try to restore your app + data when the system boots
thanks !
how can I access the dropbox folder if the system isn't booting? not finding the device in fastboot...
I don't have twrp, but lineage recovery - is that an issue? there are also some logs here, but probably not related to the system, I assume?
lueromat said:
how can I access the dropbox folder if the system isn't booting?
I don't have twrp, but lineage recovery - is that an issue? there are also some logs here, but probably not related to the system, I assume?
Click to expand...
Click to collapse
next time use "quote" or "reply" so i get a notification
i don't know if lineage recovery has a file manager or not, but i strongly recomand using orangefox recovery for multiple reasons ...
when you make a backup of data, browse to that folder and do what i said
and when your system is on you can restore your app + data using that backup and titanium backup app or copy paste if you know the path ...
so I ended up flashing LOS and pic GApps again, as per a suggestion on reddit, which didn't wipe my data:
https://www.reddit.com/r/LineageOS/comments/lotixs
it was suggested that the crash could have originated from some GApps error, but since those logs were overwritten with the reinstall I'll never find out
loopypalm said:
i don't know if lineage recovery has a file manager or not, but i strongly recomand using orangefox recovery for multiple reasons ...
Click to expand...
Click to collapse
I don't have a ton of experience with different recoveries, so far I have used TWRP and LOS recovery and have been moderately happy - orange fox looks like a great project, I'll make sure to give it a try next time
lueromat said:
so I ended up flashing LOS and pic GApps again, as per a suggestion on reddit, which didn't wipe my data:
https://www.reddit.com/r/LineageOS/comments/lotixs
it was suggested that the crash could have originated from some GApps error, but since those logs were overwritten with the reinstall I'll never find out
lueromat said:
so I ended up flashing LOS and pic GApps again, as per a suggestion on reddit, which didn't wipe my data:
https://www.reddit.com/r/LineageOS/comments/lotixs
it was suggested that the crash could have originated from some GApps error, but since those logs were overwritten with the reinstall I'll never find out
I don't have a ton of experience with different recoveries, so far I have used TWRP and LOS recovery and have been moderately happy - orange fox looks like a great project, I'll make sure to give it a try next time
Click to expand...
Click to collapse
I don't have a ton of experience with different recoveries, so far I have used TWRP and LOS recovery and have been moderately happy - orange fox looks like a great project, I'll make sure to give it a try next time
Click to expand...
Click to collapse
You shouldn't have flashed pic GApps coz of that it will go to same issue when the rom gets updated. Instead flash OpenGapps one of the best GApps for LineageOS. There was same issue with my Moto G3 Turbo(Merlin) when I flashed BitGapps, always use Trusted GApps by LineageOS. It is also available on the LineageOS Forum