Hey guys! I am running 6.0.1 AOKP ROM on my A6000 plus, and wanted to revert to KitKat for a few days. I found this site
http://www.techolite.com/34431/lenovo-a6000plus-pure-stock-rom-recovery.html
And downloaded Lenovo A6000 plus KitKat stock Rom. However, while flashing this ROM via TWRP, I got an error that the zip is corrupted. So I downloaded it again, but it gave me the same error What's the problem? I did factory reset and wipe all cache and Dalvik cache before flashing, so why won't it flash?
ProBlast said:
Hey guys! I am running 6.0.1 AOKP ROM on my A6000 plus, and wanted to revert to KitKat for a few days. I found this site
http://www.techolite.com/34431/lenovo-a6000plus-pure-stock-rom-recovery.html
And downloaded Lenovo A6000 plus KitKat stock Rom. However, while flashing this ROM via TWRP, I got an error that the zip is corrupted. So I downloaded it again, but it gave me the same error What's the problem? I did factory reset and wipe all cache and Dalvik cache before flashing, so why won't it flash?
Click to expand...
Click to collapse
I too always have some problem while reverting back to stock kitkat. Try this cwm recovery. Flash the stock KK using this. It'll surely work.
And, in case, you can flash this recovery, just boot into it at once by using
"fastboot boot recovery.img" in adb and fastboot tool on pc.
And then wipe system, data, cache, dalvik cache and flash ROM
I was trying to convert my system, data and cache to F2FS but after the conversion I can't use Data anymore (apparently it cannot mount data and system anymore).
Could be a problem LinkedIn to the grarak modded 3.0.2 I'm using for Exodus 6?
Any feedback is welcome!
Up
Most probably as the official one from twrp supports f2fs natively.
I would recommend to go back to official twrp convert to f2fs properly from there and then flash the modified one, do this if you are brave enough, i havent tried this method but it should work. If all fails stay on ext4 till garak or twrp updates their twrp versions.
Thanks for you answer... I thought the same... I'll try as the new phone will come and let you know...
IlD4nX said:
I was trying to convert my system, data and cache to F2FS but after the conversion I can't use Data anymore (apparently it cannot mount data and system anymore).
Could be a problem LinkedIn to the grarak modded 3.0.2 I'm using for Exodus 6?
Any feedback is welcome!
Click to expand...
Click to collapse
I got the same error for my Redmi Note 3 ... tried 3.0.0.0, 3.0.2.2, but nothing. then a guy suggested this:
https://www.androidfilehost.com/?fid=24591000424943818
and it worked. Now I can't boot on f2fs, just trying to make it work on 6.0.1 Mokee rom
Hi,
I have a problem installing 8.1 oreo roms on my phone. I follow standard procedure: wipe dalvik, cache, system, data -> install rom + gapps -> wipe cache. After my phone restarts, it displays rom logo, but doesn't load (even after 15-20 minutes of waiting). All I can do is load in fastboot and restore my backup. I use twrp 3.2.1-0, unofficial 8.1 pico gapps from 2018/01/30.
So far I tried:
-Installing rom and gapps separately.
-Installing rom, rebooting, installing gapps.
-Installing rom + gapps, then wiping data.
-Installing rom + gapps, then not wiping anything.
-Factory reset, then install rom + gapps.
-Installing rom + different gapps versions.
Additional notes:
-At one point I successfully installed NitrogenOS (about a month ago) and it is my current rom and backup. But I can't clean flash it again.
-When I install rom only (without any gapps) it boots up fine without errors or long loading.
Can anyone help?
Same problem I am also facing. Using Pixel experience ROM but now not able to flash cosmic official rom...remaining on bootanimation
Hi buddy .
TWRP
Wipe Data, Dalvik, Cache , System, Internal Storage
Flash
Rom
Gapps
Wipe to factory reset
Reboot
Done ! That's the only way it worked for me
metro20 said:
Hi buddy .
TWRP
Wipe Data, Dalvik, Cache , System, Internal Storage
Flash
Rom
Gapps
Wipe to factory reset
Reboot
Done ! That's the only way it worked for me
Click to expand...
Click to collapse
Thanks for answer. I tried that method too, but it still didn't work for me. I recently tried clean flash with gapps from https://forum.xda-developers.com/xiaomi-redmi-3s/development/rom-lineageos-15-1-t3718757 and it worked flawlessly. So maybe it's an issue with some gapps packages?
I also have the exact same problem.
Flashing ROM without gapps works perfectly.
adding gapps package, no matter if its pico aroma or mini, it results in stuck on boot animation.
wiping after flashing also did not work.
once made pixel experience boot, using it since...ota update worked without a problem.
any other suggestions?
devito666 said:
I also have the exact same problem.
Flashing ROM without gapps works perfectly.
adding gapps package, no matter if its pico aroma or mini, it results in stuck on boot animation.
wiping after flashing also did not work.
once made pixel experience boot, using it since...ota update worked without a problem.
any other suggestions?
Click to expand...
Click to collapse
Try this nano package https://androidfilehost.com/?fid=889964283620771808. It's the only one that worked for me.
sanchez8096 said:
Try this nano package https://androidfilehost.com/?fid=889964283620771808. It's the only one that worked for me.
Click to expand...
Click to collapse
Thanks for the Link!
But unfortunately still Not booting...tried atomic official and teammexs Rom...
metro20 said:
Hi buddy .
TWRP
Wipe Data, Dalvik, Cache , System, Internal Storage
*then tap back, FORMAT DATA and confirm by typing "yes"
Flash
Rom
Gapps
Magisk stable (if preferred if not next >>>)
Magisk beta (always flash after stable)
Busybox flashable zip (if needed)
Mods such as MIUI cam mod
Font package
Wipe to factory reset
Reboot
After 1st boot
Reboot to TWRP
Install Magisk modules ( USN or Viper4android etc)
Reboot system
Done ! That's the only way it worked for me
Click to expand...
Click to collapse
ftfy. But before this ensure that:-
1. Non corrupted ZIPs. Avoid if possible from using mobile data. A slower yet stable WiFi yields better success rate.
2. Currently this unofficial opengapps' builds works better and are more current.
Suo.Eno said:
ftfy. But before this ensure that:-
1. Non corrupted ZIPs. Avoid if possible from using mobile data. A slower yet stable WiFi yields better success rate.
2. Currently this unofficial opengapps' builds works better and are more current.
Click to expand...
Click to collapse
I didn't need to format data on Oreo nos
As mentioned in other threads on this topic, I just wanted to mention here as well that I am also affected by these Oreo boot loops and haven't found a solution yet. I somehow managed to get PixelExperience to install once, but downgraded now to a Nougat build for other reasons (better battery and GCamMod compatibility).
sanchez8096 said:
Thanks for answer. I tried that method too, but it still didn't work for me. I recently tried clean flash with gapps from https://forum.xda-developers.com/xiaomi-redmi-3s/development/rom-lineageos-15-1-t3718757 and it worked flawlessly. So maybe it's an issue with some gapps packages?
Click to expand...
Click to collapse
Use twrp 3.2.1-0 bcoz some Oreo ROMs aren't flash able by 3.1.1
Sunny Za said:
Use twrp 3.2.1-0 bcoz some Oreo ROMs aren't flash able by 3.1.1
Click to expand...
Click to collapse
I am using 3.2.1-0 twrp. Rom itself flashes fine, it's the gapps that create infinite boot.
Exact Same issue Here...
I have same problem too .. can't boot in to any Oreo ROM with Gapps .. really isn't any solution here?
This might not be a proper solution, but here's what I did:
1) Wipe data, cache, dalvik, system
2) Flash rom + gapps(I used NitrogenOS and pico gapps)
3) Wipe data again and restore data from backup(I restored data from previous build of NitrogenOS, so I don't know if restoring from different rom will be ok)
4) Boot into rom, ignore any "stopped working" errors and go to Settings-System-Reset options-Erase all data(Not sure if this will erase internal storage, backup just in case)
After that phone booted up and and did first time installation.
sanchez8096 said:
This might not be a proper solution, but here's what I did:
1) Wipe data, cache, dalvik, system
2) Flash rom + gapps(I used NitrogenOS and pico gapps)
3) Wipe data again and restore data from backup(I restored data from previous build of NitrogenOS, so I don't know if restoring from different rom will be ok)
4) Boot into rom, ignore any "stopped working" errors and go to Settings-System-Reset options-Erase all data(Not sure if this will erase internal storage, backup just in case)
After that phone booted up and and did first time installation.
Click to expand...
Click to collapse
Can someone upload me some backup? Pixel Experience would be a best ! Thanks a lot
Anyone have an idea what the problem might be?
I'm facing the same problem. I have a Redmi 3S (international, 3GB version). Doesn't matter what Oreo ROM I try (clean install), they all get stuck in bootloop on boot animation. It doesn't get far enough in the boot process to do a logcat with ADB, so I'm not able to post it.
I'm using TWRP 3.2.1-0 but have tried Red Wolf recovery as well and it yields the same results... I don't think it's a gapps issue since I've tried booting several ROMS without installing gapps.
I have rebooted several times while it's still in the boot process, remounted system in TWRP, wiped everything, ...
If anyone has an idea to get the logs, fire away. Can't boot so can't install liveboot or something like that.
bump
any solution?
The Problem still occurs...
Flashed PE successfully once, but since i went Back to official Nougat lineage os, No Oreo Roms can be booted with gapps
***Problem Solved***
Hello All,
First of all, Iam a newbie in custom roms so i hope it's not a stupid question...
Couple of months ago i rooted my LG G2 en installed TWRP and after that i flashed Lineageos 14.1.
But i wanna try something else.
I flashed AOSP and works like a charm.
So i decided to flash another one.
But now my phone is stuck on a TWRP loop.
I aleady update twrp to a new version: 3.2.1.0 but it still not work.
What did i do:
Iam going to wipe.
Advanced wipe and wipe:
Dalvik/ART cache
System
Data
And cache
After that iam going to Install:
select the rom and the OpenGapps. (ARM 7.1 Nano)
And confirm flash.
After the flash i wipe Cache and Dalvik and then reboot..
But it's only starting in recovery again and again.
I have tried this roms:
Lineageos
ASOP
CRdroid
Paranoid Android
MK
Ressurection remix
But none of the roms will work
I also tried to wipe Internal storage but unfortunatly that also doesnt work
What iam doing wrong?
Or what can i do to get one of this roms to work?
Thank you
***Problem Solved***
I Found it!!
By Terminal i have to type a code and then another code.
My phone is working again.
I flashed TWRP recovery I used last week, to install SparkOS and I do remember following a tutorial that said wipe Dalvik, Cache, Data, System and Vendor, which I did successfully and installed the custom rom. I didn't last much and reverted to Stock Rom.
Cut to yesterday I flashed the same recovery as last time, and when I went to wipe the partitions I didn't find Vendor. Checked Mount menu clicked on Vendor it didn't show up under Wipe.
Should I ignore this and continue with installing my custom rom after wiping (Dalvik, Cache, Data and system only) or this is a problem and I am not able to install any custom rom until I wipe Vendor Partition?
It may cause problem or maybe not. Try Orange Fox recovery or any other recovery which supports to wipe vendor data and then flash your Custom Rom correctly as in tutorial.
ai.Sanaul said:
It may cause problem or maybe not. Try Orange Fox recovery or any other recovery which supports to wipe vendor data and then flash your Custom Rom correctly as in tutorial.
Click to expand...
Click to collapse
I followed it step by step, but I'm gonna try different versions and see if shows up. Otherwise I'll revert back to stock and hang my hat.
ai.Sanaul said:
It may cause problem or maybe not. Try Orange Fox recovery or any other recovery which supports to wipe vendor data and then flash your Custom Rom correctly as in tutorial.
Click to expand...
Click to collapse
Updating the TWRP version from 3.3.1 to 3.6 fixed the problem. Thank you for the help.
Ikarisdruig said:
Updating the TWRP version from 3.3.1 to 3.6 fixed the problem. Thank you for the help.
Click to expand...
Click to collapse
welcome