i had installed a layers theme on my rooted nexus 6p running pure nexus rom. After i rebooted the phone it went into bootloop.
So i got into twrp recovery and factory reset the phone . Flashed the necessary files but it still continued to bootloop. I formatted the internal storage and flashed Chroma Rom but the issue persists. Kindly Help
Hey,
I'm visiting from the Nexus 6 forums and I myself also run the Pure Nexus ROM. The normal would fix this is reflashing the system partition, as that is where the layers are stored. No need to touch any other partitions or even format system (although you can, I don't think this is necessary.) In additon to that, you can go into TWRP, Advanced > File Manager > /system/vendor/overlay/ and remove the bad overlay apk. Since it sounds like you have flashed another ROM over it, I would have thought this would have fixed this issue. Perhaps you can find it in /system through TWRP or try reflashing Pure Nexus after formatting system. I find it odd that it still persists after a reflash and format but, try to give that a shot. Best of luck to you and I hope I could provide a little guidance.
Layers is stored in the vendor partition, so you need to flash that which will clear any Layers data. You'll find a link to recovery flashable vendor zips in the first post of the Pure Nexus thread.
Layers is stored in the separate vendor partition on this device, which is why it's probably best not to give advice for a device that you're not familiar with. Good intentions of course, but each device is different.
Related
Hi guys, hoping you can help me out. Noob, yup.
Nexus 7 2012 Wifi.
My Nexus was getting slow, so I successfully converted my system, data, and cache to F2FS with SlimKat.
In the process of this, I converted my Cache, System, and Data to F2FS.
The SlimKat F2FS rom was working fine. All was well.
Here's where I made a series of errors...
I decided to restore the Nexus back to factory settings/stock 4.4.4. I had some problems with my nandroid files, so I decided just to convert things back manually in TWRP. My thought process was to: A. convert Data and Cache back to ext4, B. Install factory rom from System, C. convert System back to ext4.
My thought process was apparently wrong.
Here's what I did:
1. I copied the 4.4.4 Factory Image (.tgz) to the sdcard (first mistake. I assumed the official download was a .zip but it was a .tgz).
2. In TWRP, i converted the Cache and System to ext4.
3. Tried to install stock 4.4.4 rom but couldn't install it because it was .tgz.
4. Not knowing what else to do, I converted the Data to ext4 as well. So in my eyes, everything was "put back" to ext4 like it was before. Since everything was "back to normal", I thought Nexus Root Toolkit could take me the rest of the way back to normal.
5. In Nexus Root Toolkit, I tried to "Flash Stock + Unroot", but it gave me errors (picture is attached)
6. Now I'm in bootloader. Trapped. I can't even get back into TWRP anymore (and I don't understand why).
Sorry for the noob trouble. Hopefully there is still hope for my Nexus.
Thanks in advance for any help.
In fastboot mode (i.e. Bootloader), use fastboot to flash the latest TWRP or a factory image
thunderdust said:
Hi guys, hoping you can help me out. Noob, yup.
Nexus 7 2012 Wifi.
My Nexus was getting slow, so I successfully converted my system, data, and cache to F2FS with SlimKat.
In the process of this, I converted my Cache, System, and Data to F2FS.
The SlimKat F2FS rom was working fine. All was well.
Here's where I made a series of errors...
I decided to restore the Nexus back to factory settings/stock 4.4.4. I had some problems with my nandroid files, so I decided just to convert things back manually in TWRP. My thought process was to: A. convert Data and Cache back to ext4, B. Install factory rom from System, C. convert System back to ext4.
My thought process was apparently wrong.
Here's what I did:
1. I copied the 4.4.4 Factory Image (.tgz) to the sdcard (first mistake. I assumed the official download was a .zip but it was a .tgz).
2. In TWRP, i converted the Cache and System to ext4.
3. Tried to install stock 4.4.4 rom but couldn't install it because it was .tgz.
4. Not knowing what else to do, I converted the Data to ext4 as well. So in my eyes, everything was "put back" to ext4 like it was before. Since everything was "back to normal", I thought Nexus Root Toolkit could take me the rest of the way back to normal.
5. In Nexus Root Toolkit, I tried to "Flash Stock + Unroot", but it gave me errors (picture is attached)
6. Now I'm in bootloader. Trapped. I can't even get back into TWRP anymore (and I don't understand why).
Sorry for the noob trouble. Hopefully there is still hope for my Nexus.
Thanks in advance for any help.
Click to expand...
Click to collapse
Instead of doing these whole procedure via .bat file plss try it manually yourself and install latest twrp and then format your system and other partitions with desired format and then flash manually system.img and other stuff manaually
Solved!
Hey guys, thanks for the help.
Here's what got me through it:
1. Learn how to fastboot, adb, etc. WITHOUT Nexus Root Toolkit so you understand what's going on.
2. Don't assume that any USB port or laptop will give you the same results. My attempts to flash the system with a custom rom failed time and time again. On the advice of other threads, I tried the same thing again via a different USB port, and voila it worked! Perhaps it was not a 2.0 port.
In summary, I needed to fastboot erase, then fastboot flash the partitions. And most of all, I had to try it on a different USB port if it failed unexpectedly.
Hope this helps somebody else!
Hello! I installed Pure Nexus and that went great. That is until I left the house and had no data. Did some searching and all the recommendations say install the latest vendor image. So I did and flashed the mmb29q vendor image and I still don't have data. I'm not sure whats wrong and if someone could atleast point me in the right direction I'd appreciate it.
Has nothing much to do with data. It highly likely that your device storage is encrypted.
On a clean install like: wipe data, system, cache, delvik cache, flash rom, flash gapps, flash sprint data fix zip, reboot. Do a Google search its in Nexus 5 forums. It is the fix and it works but must be used on a clean install at end of flash. @mechlior
Sent from my Nexus 6P using Tapatalk
Hi guys, i'm stuck in Rock and a hard place here and couldn't figure this one out. I've installed CyanogenMOD previously but that was a while ago and different process. What happened is I installed LineageOS 2 days ago and everything worked fine except No Sim Card is detected so I can't make phone calls and log into my Google account to sync.
Hence to resolve the Sim Card issue, what i did is to attempt to flash Bootloader, System , Radio images but it didn't work when i try to flash and also install LineageOS zip file. And in order to try resolving Mount issue, I proceed to Advanced Wipe -> checked System, Data, Cache -> Repair and Change File System -> changing ext4 to ext 2 . This formated all my User data which includes the ROM zip file i needed to install and load. I tried using Nexus Root Toolkit to restore into stock but it says no Fastboot/ ADB detected. And my computer couldn't detect my Nexus 6p.
Please provide solutions. Desperate here.
@Psuche To fix the no sim bug in Oreo you simply turn off lockscreen security once and reboot. Your phone is probably boogered because you switched to a filesystem the 6p isn't compatible with. Similar thing happened to me switching to f2fs without compatible kernel. So hopefully if you have and can still boot into twrp can repair filesystem in there back to EXT4. Obviously selecting ExT4 instead of F2FS.
Exodusche said:
@Psuche To fix the no sim bug in Oreo you simply turn off lockscreen security once and reboot. Your phone is probably boogered because you switched to a filesystem the 6p isn't compatible with. Similar thing happened to me switching to f2fs without compatible kernel. So hopefully if you have and can still boot into twrp can repair filesystem in there back to EXT4. Obviously selecting ExT4 instead of F2FS.
Click to expand...
Click to collapse
Thank you for replying Exodusche. But i have switched back to EXT 4 and finds the system formatted and user data deleted! Plus my computer is unable to recognize my phone while i'm stuck at Bootloop =( Talk about difficult situations. So i'm unable to test your no sim solution at this point. Need to retrieve deleted files or at least push files from Desktop to Phone.
Any ideas?
Ok have a ZTE Axon 7 can't flash any thing because of it instantly encryption and I get recovery and then game over any one have a Cure for this......... thanks in advance.
You have to do a factory wipe, to remove encryption. Then when setting up the phone again when it prompts you to set a security pin or finger sprints skip that part.
chairmanmarv said:
You have to do a factory wipe, to remove encryption. Then when setting up the phone again when it prompts you to set a security pin or finger sprints skip that part.
Click to expand...
Click to collapse
Tried that and it didn't work.....it doesn't matter what I flash stock ROMs tell me my password is correct but memory is corrupt and need to be wiped and when I flash a custom ROM it doesn't boot just two flashes of the led and that's it.
Which TWRP recovery are you on?
What I mean by Factory reset is a full Factory wipe your whole internal is erased. It is like a clean slate new phone.
You should have all the necessary files for your flash on your sd card there is an option to select storage to flash from there.
So when I first swapped from Stock Nougat to AEX I was encrypted on 5/4 ROM my internal was locked by encryption and could only dirty flash roms. it was annoying so I factory wiped and flashed latest AEX from there and didn't set up security right away so no encryption.
I realised my TIBU back ups were all on internal so had to basically start from scratch oops lol.
It is a little outdated now with the official Oreo roms but user @Oki 's guide helped me a lot and has clear steps and guides to get you all rooted and sorted on custom roms.
https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-custom-oreo-roms-newbies-t3786693
chairmanmarv said:
Which TWRP recovery are you on?
What I mean by Factory reset is a full Factory wipe your whole internal is erased. It is like a clean slate new phone.
You should have all the necessary files for your flash on your sd card there is an option to select storage to flash from there.
So when I first swapped from Stock Nougat to AEX I was encrypted on 5/4 ROM my internal was locked by encryption and could only dirty flash roms. it was annoying so I factory wiped and flashed latest AEX from there and didn't set up security right away so no encryption.
I realised my TIBU back ups were all on internal so had to basically start from scratch oops lol.
It is a little outdated now with the official Oreo roms but user @Oki 's guide helped me a lot and has clear steps and guides to get you all rooted and sorted on custom roms.
https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-custom-oreo-roms-newbies-t3786693
Click to expand...
Click to collapse
Just found out that the phone has bricked itself it would play any video or sound so did a hard reset now just getting a constant boot loop trying to get it in to EDL as we speak.....got EDL flashed stock ROM in miflasher now stuck on splash screen.......been on the splash screen for 10 minutes now.......
chairmanmarv said:
Which TWRP recovery are you on?
What I mean by Factory reset is a full Factory wipe your whole internal is erased. It is like a clean slate new phone.
You should have all the necessary files for your flash on your sd card there is an option to select storage to flash from there.
So when I first swapped from Stock Nougat to AEX I was encrypted on 5/4 ROM my internal was locked by encryption and could only dirty flash roms. it was annoying so I factory wiped and flashed latest AEX from there and didn't set up security right away so no encryption.
I realised my TIBU back ups were all on internal so had to basically start from scratch oops lol.
It is a little outdated now with the official Oreo roms but user @Oki 's guide helped me a lot and has clear steps and guides to get you all rooted and sorted on custom roms.
https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-custom-oreo-roms-newbies-t3786693
Click to expand...
Click to collapse
Ok now got the thing back was able to reunlock the bootloader and installed recovery flashed candy rom with one issue could not mount system so now just flashed Oreo stock rom so all good again....... thanks for the help
The stock ROM encrypts by default, and formatting data partition in twrp is the only way to remove it. But to prevent the encryption before it happens, you have a few options:
1. If you dont plan to root, flash @jcadduono's no verity opt encrypt zip (Google it)
2. Magisk and SuperSU can optionally disable encryption before it happens. Magisk Manager has a config option if you're installing from the app. You can use Aroma SuperSU config if SuperSU is your root method of choice.
Hope that helped!
I would like to note that AOSP/Lineage/CM-based ROMs dont encrypt by default. though Im sure it could be enabled if you wanted to. This seems to be unique to the stock ROMs, mainly because Google insists that phone OEMs should go for higher security by enabling encryption as the default.
AnonVendetta said:
The stock ROM encrypts by default, and formatting data partition in twrp is the only way to remove it. But to prevent the encryption before it happens, you have a few options:
1. If you dont plan to root, flash @jcadduono's no verity opt encrypt zip (Google it)
2. Magisk and SuperSU can optionally disable encryption before it happens. Magisk Manager has a config option if you're installing from the app. You can use Aroma SuperSU config if SuperSU is your root method of choice.
Hope that helped!
I would like to note that AOSP/Lineage/CM-based ROMs dont encrypt by default. though Im sure it could be enabled if you wanted to. This seems to be unique to the stock ROMs, mainly because Google insists that phone OEMs should go for higher security by enabling encryption as the default.
Click to expand...
Click to collapse
Yep this is the problem I am having now....... can't find much info about it.
im having big problems about vendor. for start im giving some info:
device: mi a1 (tissot)
current os: lineage OS 17.1
root: yes
twrp: can install or use just booting .img
i unlocked my device and installed twrp. there is no problem.
i wanted flash lineage OS and i wiped my device. gives error about cannot mount /vendor
i installed treble supported twrp and installed lineage OS. flashed magisk. installed microg...
then i tried flash mapsv1.zip which is recommended for microg. then booom. another /vendor error.
now i can boot device. i can use everything except gps. google maps app cannot found location. yandex maps can found and i can use it until lock screen or going main screen (or another app). then it starts stopping everytime until i clen its data and cache. then again... in chrome when i open google maps and try found my location chrome stops.
i tried to change /vendor/etc/gps.conf. its still same.
what to do now guys? im worrying about if i try re-flash rom it doesnt flash and device bricked. any solution without re-flash rom? what causes to cannot mount /vendor after solved it?
What exactly did you wipe? I think you wiped vendor, or bumped your O.S. from an old firmware. However, wiping system, data and Dalvik was more than enough.
To solve this, the worst thing to do is trying to hook around. Just reflash the latest original firmware and start again.
Keep in mind that you might need to backup your stuff first.
Use adb pull and push commands in case your device is rebooting too much. Check if device works well this time.
Next, open adb access from device and reboot fastboot to reflash your custom recovery, then reboot recovery and wipe just these items. Finally, complete Rom flashing procedure, depending of your needs.
KaaMyA said:
What exactly did you wipe? I think you wiped vendor, or bumped your O.S. from an old firmware. However, wiping system, data and Dalvik was more than enough.
To solve this, the worst thing to do is trying to hook around. Just reflash the latest original firmware and start again.
Keep in mind that you might need to backup your stuff first.
Use adb pull and push commands in case your device is rebooting too much. Check if device works well this time.
Next, open adb access from device and reboot fastboot to reflash your custom recovery, then reboot recovery and wipe just these items. Finally, complete Rom flashing procedure, depending of your needs.
Click to expand...
Click to collapse
Dalvik cache , system, data, and cache. My device is not rebooting too much. Sory if i couldn't explain. Everything working fine except when an app tries use my location, app stops running, i cant flash anything right now.
İ thought anyone knows mapsv1.zip file(microg.org) and which files are replaced or added by this file when flash it. And can i do it manually? Btw i can read and write /vendor file with solid explorer
İf needed to re-flash rom thats ok but i think lineage OS was perfect for me until this error. And a last thing: can i backup my settings. (İ already took backup of everything in stock when unlocked bl)
Thank you for help
Edit: gps problems started when i tried flash mapsv1
ROM could be perfect, but what I doubt is how perfectly you followed the procedure. Again, better start from zero, being sure you have all the prerequisites (latest firmware included). My humble opinion.
KaaMyA said:
ROM could be perfect, but what I doubt is how perfectly you followed the procedure. Again, better start from zero, being sure you have all the prerequisites (latest firmware included). My humble opinion.
Click to expand...
Click to collapse
Okey ilk try it and share the result night. But is it possible to backup settings of phone?
Well, that's why in step 0 is always recommended to backup you phone. At this level you should have nothing in settings, since you wipe it all... However, that's better, that's the goal of a Clean Install after all. Each ROM has its own flavour and is not recomendable to overwrite these values from a backup, if you're changing ROMs. What you could do, was to backup your apps and some settings with a third app like Swift Backup, or older Titanium Backup, before starting it all, or else, making a complete backup from recovery, in case you end with a problem with newly installed ROM (recommendation here is disable any screen security lock before doing Backups).
KaaMyA said:
Well, that's why in step 0 is always recommended to backup you phone. At this level you should have nothing in settings, since you wipe it all... However, that's better, that's the goal of a Clean Install after all. Each ROM has its own flavour and is not recomendable to overwrite these values from a backup, if you're changing ROMs. What you could do, was to backup your apps and some settings with a third app like Swift Backup, or older Titanium Backup, before starting it all, or else, making a complete backup from recovery, in case you end with a problem with newly installed ROM (recommendation here is disable any screen security lock before doing Backups).
Click to expand...
Click to collapse
İ did it all. Step by step. But i realized something. That errors doesnt matter on my device. Bcs when i flashing stock mi flash tool said failed but i booted system and everything working fine. İ installed persistent twrp. Same error. Then wiped. Same error but wipe completed. Than i flashed this zips single and booted everytime: lineage os, magisk, backup of migrate. Everytime it said cannot mount vendor but all of this apps and os and recovery working fine
Thank you for your helps
[Helping alone ]
Nurullah44 said:
İ did it all. Step by step. But i realized something. That errors doesnt matter on my device. Bcs when i flashing stock mi flash tool said failed but i booted system and everything working fine. İ installed persistent twrp. Same error. Then wiped. Same error but wipe completed. Than i flashed this zips single and booted everytime: lineage os, magisk, backup of migrate. Everytime it said cannot mount vendor but all of this apps and os and recovery working fine
Thank you for your helps
[Helping alone ]
Click to expand...
Click to collapse
if you didn't treblized your device then its not a problem. I have this error too but that's because there is no vendor partition to mount. as been said by unipo:
https://forum.xda-developers.com/mi...-3-3-1-0-tissot-manager-t3976117/post81326153
portox said:
if you didn't treblized your device then its not a problem. I have this error too but that's because there is no vendor partition to mount. as been said by unipo:
https://forum.xda-developers.com/mi...-3-3-1-0-tissot-manager-t3976117/post81326153
Click to expand...
Click to collapse
Are you sure? Bcs i can view and change /vendor in root path. Treblizing is updating and repairing system partitions right? İ am using treble support twrp, flashed stock rom via mi flash(said error but worked fine) then how to treblize a device? And is this required for anything(like a rom, an app)?