Recently I tried the Open Gapps Aroma Installer where after installation, my phone was only rebooting into recovery. Fastboot was not working and also the rom was not booting. The Screen flash 2 times and again and again it was booting into recovery. So I tried to install a ROM again (Clean method) and it was giving me Error7. Only the stock ROM I was able to install but it didn't worked, again it boot into recovery mode (I was using orange fox). Then I force shut down the device by holding power button for 10sec and it then successfully booted into OS. That's it! If anyone face the same problem, don't PANIC!
Its a known issue with Aroma gapps.... Just mount /system before installing aroma gapps...
Related
Hi,
After flashing CM10 successfully, I apparently flashed the wrong GAPPS zip, so I got the endless "Unfortunately, Setup Wizard has stopped" loop, through which I can only access the time functions using the dropdown.
I tried re-wiping and reflashing, but that apparently just leads to the 0/0/0 nesting issue, and doesn't seem to actually wipe/reflash.
"adb devices" only reads when I'm in recovery mode, and doesn't appear to accomplish anything.
Does anyone have any advice?
Thanks,
Erik
1) Flash the latest CWM or TWRP via fastboot to avoid further "0 folder" issues
2) Go into the recovery
3) Do a full wipe (system, cache, dalvik)
4) Flash the CM10 ROM again or any other ROM you already have on your sdcard and ready to be flashed
5) Flash the correct Gapps if you already have it on your sdcard, or just reboot into the CM10 then download the correct Gapps to flash later via Goo Manager app which finds the correct version of Gapps automatically.
Hope this works
Ok so I got my E980 rooted via towelroot, then used the freegee app to install loki, then I used flashify to install the CM recovery listed below, planning to flash the matching cyanogenmod rom:
snapshot Download: cm-12.1-20151007-SNAPSHOT-YOG4PAO332-e980.zip (243.15 MB)
sha1: 9a4773d2fca0658edb2683079ce96307863a9fd0 Download: cm-12.1-20151007-SNAPSHOT-YOG4PAO332-e980-recovery.img
sha1: 1095ea774ff2347fb3a2884045aa4a47e6833893 2015-10-07 02:08:36
I rebooted into the recovery and it wouldn't flash the cyanogenmod 12.1 rom at first, saying that I had an incompatible system installed, so I did a factory reset and then tried again and it installed the CM 12.1 ROM without errors, however it wont boot into it. All I can access is the CyanogenMod recovery and the factory wipe screen, I cant seem to boot into a rom even when it installs without errors, I cant get into download mode no matter what combo of keys/plugging in I do, even though it worked fine before.
Any thoughts or Ideas? I am totally lost here.
When turn on the phone it says:
Secure booting Error! Cause : Device Unlock!, so Boot Success!!
When I try to flash the TWRP zip that is floating around (2.8.1 I think) it says:
Finding update package.....
Opening update package...
Verifying update package...
E:Footer is wrong
E:Signature verification failed
Installation aborted.
When I turn on ADB mode through CyanogenMod recovery
Adb devices: Lists the device (99d3b89c sideload)
Adb usb: Error : closed
I have tried CyanogenMod 10.2.0, 11-20141115, and 12.1-20151007, and tried them before and after every kind of wipe available through this recovery, and they all install without error then reboot back to the recovery.
Is there another flashable recovery around for this phone I could try? I just don't see many in zip format.
Finally got it working. Threw every flashable recovery I could find at it, finally got Phillz touch to install and work from the CyanogenMod recovery. Phillz wouldnt install a working rom, but Phillz did allow me to flash CWM 6 something, which allowed me to install 2.8.1 TWRP, which couldnt see my microSD card, but it did allow me to copy 12.1 CM to my internal SD card from my computer via USB and to flash it and have it actually work. After I booted into CM 12.1 I had to fight gapps for a while, the open gapps pico and nano for 5.1 arm didnt work, but I got the Gapps from the slim rom to work after rewiping the system to remove the open gapps.
After that I finally manager to get flashify, supersu, and busybox from the store. Used flashify to upgrade to 3.0 TWRP. I still cant get into download mode, but pretty much everything else is working now.
I had formatted all things including internal storage using twrp. After that I flashed oxygen os 4.0 with USB using twrp.Installation is successfull.But when I rebooting the system it still boots into TWRP screen.I am not able to see one plus boot logo as it always boots to twrp screen even after successfully installation.I am wondering why even after succesfull flashing still the phone always boot into twrp screen.Pls help in resolving the issue
Flashing a lower version and then the 28 version back helped me... Had the same problem
jaganmohans said:
I had formatted all things including internal storage using twrp. After that I flashed oxygen os 4.0 with USB using twrp.Installation is successfull.But when I rebooting the system it still boots into TWRP screen.I am not able to see one plus boot logo as it always boots to twrp screen even after successfully installation.I am wondering why even after succesfull flashing still the phone always boot into twrp screen.Pls help in resolving the issue
Click to expand...
Click to collapse
1 ) flash stock recovery and sideload full zip of 3.2.8 oxygen os
2) boot to system
3) reboot to stock recovery
4) sideload full zip of 4.0.1
5) boot to system
6) boot to bootloader and flash twrp -28 recovery (adb fastboot flash)
7) after flashing boot to twrp recovery from bootloader
8) flash SU SR2 v2.79 and boot to system
Hey there I cannot install any Custom ROM on my honor 5x(kiwi)Everytime I install any custom ROM, be it cyanogenmod, xenonHD or resurrection remix. I follow the exact same steps posted everywhere.
Here are the steps I followed(using TWRP):
put both gApps and ROM file on Sd card
boot into recovery mode
select wipe>advanced wipe> selected(Dalvik/Art Cache+cache+data+system+(tried wiping internal storage once too)
swipe to wipe
go on home
select install select Custom ROM +(selected gApps once with ROM zip and once separately)
swipe to confirm flash> clear dalvik/cache
reboot system
Phone goes into bootloop everytime
tries going into recovery again>wipe>advanced wipe>select dalvik/ART cache+cache
swipe to wipe
reboot
phone is still in bootloop no matter how much time I leave it.
PLease help I'm stuck
You might have flashed bad recovery try re downloading twrp and reflash that might fix it.
Hello,
I have a strange problem with Galaxy A5 2017 after installing twrp + lineage 18.1. I will explain the problem in sub points.
1) in January on stock software I installed (according to instructions from XDA forum) root, twrp (via ODIN) and bypass with memory decryption. Then I installed Lineage 18.1, Gapps, Magisk and debloater on it to remove unnecessary apps.
2) The phone worked fine until mid-April. Some update was installed and the phone died.
3) The phone wouldn't boot up after the update and only the TWRP logo was looping (logo kept flashing).
4) the phone couldn't boot up, but after I found the only way to get the system to boot up was to enter command "adb reboot bootloader" from windows console. The system booted, but after another reboot unfortunately it was the same thing - the TWRP logo was looping.
5) I managed to upload Lineage Recovery via ODIN, but unfortunately this didn't change anything. Phone was booting to recovery only (but it was working). I tried to update via ADB Sideload from recovery - also without success. Interestingly, the only way to fix it was to fully format with the system partition from recovery and re-upload the system. This worked, and Lineage booted into the android interface, but on the next reboot I unfortunately only had the Lineage loading logo visible for 10-15 minutes - then a reboot into recovery. I had to repeat the formatting and re-upload the system.
6) Interestingly, when I used the combination - lineage recovery, full format, twrp 3.6.1 (via ODIN) - TWRP booted normally and I could install LineageOS. The system would only boot once, and after the next reboot the TWRP logo would loop again.
7) The last problem I noticed is that if I load Lineage system, gaaps package and magiska via TWRP or Lineage Recovery, the system will never boot - either it will loop the logo (if using Lineage Recovery) or the phone will not load the system, it will reset and loop the TWRP logo indefinitely (if using TWRP recovery).
Does anyone know a solution how to restore the phone? Will it still work or for example NAND memory is dead and nothing can be done? Best regards