Hello, It's Honor 5x.
Everytime I install a custom rom after finishing installing, Rom's boot logo appears then restarts, and keep restarting without doing anything.
I tried cyanogenmod 13 'downloaded their latest official rom' and tried AOSP-CAF But still have the same issue.
All I do is taking a backup, Then wiping all data, system and cache then flashing the zip.
How can I fix this?
Forgot to mention, I was getting error 7 while flashing the zip but fixed it by editing script file.
Any thoughts?
iAhMedZzz said:
Any thoughts?
Click to expand...
Click to collapse
make sure boot img is correct and being pushed correctly, just my thoughts, don't own the device
Must I have stock MM update installed before installing any MM custom rom ?
Related
Hello.
I have only been able to install ViperX+ 1.08 ROM successfully. I wanted to experience other ROMs in comparison and have found ROMs specifically for this model, HTC One X Plus International, only to have them fail to fully install successfully. I have read up here on how to go about it and followed the steps dutifully but to no avail.
Does it make a difference on which Recovery you have installed for it to be successful or not? I currently have the latest TWRP 2.5.0.0 for my model. I have tried installing CyanogenMod and AOKP. CyanogenMod never makes it pass the installation because it fails right after attempting to install. AOKP installs but hang at the opening picture, and yes, I tried flashing the boot.img in Fastboot thinking that would solve it but it continued hanging anyway. Anyone have any help they can offer me? Thanks.
Jussi31 said:
Hello.
I have only been able to install ViperX+ 1.08 ROM successfully. I wanted to experience other ROMs in comparison and have found ROMs specifically for this model, HTC One X Plus International, only to have them fail to fully install successfully. I have read up here on how to go about it and followed the steps dutifully but to no avail.
Does it make a difference on which Recovery you have installed for it to be successful or not? I currently have the latest TWRP 2.5.0.0 for my model. I have tried installing CyanogenMod and AOKP. CyanogenMod never makes it pass the installation because it fails right after attempting to install. AOKP installs but hang at the opening picture, and yes, I tried flashing the boot.img in Fastboot thinking that would solve it but it continued hanging anyway. Anyone have any help they can offer me? Thanks.
Click to expand...
Click to collapse
The aokp uses the 4.2 kernal so you will have to instal that. But I'm not sure on the recovery .. maybe it might be worth trying clockwork as if the twrp you are useing is especially for the viper Rom? Have a go at installing the different recovery maybe that will help and double check what you have to do to install on the thread hope this helps
Ilike the viper Rom... But if I get time tomorrow I will try for myself ... If no one else helps you out by the time I do it I will update you on how I done it and any problems I faced maybe I will end up in the same situation.
Sent from my HTC One X+ using xda premium
Appreciate it. Insofar as the Recovery is concerned, the initial Recovery that I installed from the All-In-One kit when installing ViperX+ is different from the one I have now. Unless it is just a newer version, I now have Venom TWRP 2.5.0.0., just FTR. Thanks again, I will be interested to hear what happens for you.
Jussi31 said:
Appreciate it. Insofar as the Recovery is concerned, the initial Recovery that I installed from the All-In-One kit when installing ViperX+ is different from the one I have now. Unless it is just a newer version, I now have Venom TWRP 2.5.0.0., just FTR. Thanks again, I will be interested to hear what happens for you.
Click to expand...
Click to collapse
TWRP is the ideal solution for our HOX+ - at least as of now.
I hope you are doing the following:
1. Wiping Data & System.
2. Installing boot.img.
The Venom customized TWRP does not have any issues because I also used it for some time (as of now I am back on the official TWRP).
You can download the lastes verison from here:
http://techerrata.com/browse/twrp2/enrc2b
And install it using Hox+ All in one toolkit by hasoon.
Make sure you wipe data & system before you install the ROM.
I also changed from ViperX 1.08 to ARHD, InsertCoin & Elegancia.. no issues
Hmmm. I'll have to putz around with it some more and see what happens. Thanks.
Here's a brief summary of what I attempted to do.
I wiped Delvik Cache; I wiped Cache; I did Factory Reset; I wiped System.
Next I tried installing CyanogenMod and received the following error messages:
assert failed: getprop
E: error executing updater binary in zip
Error flashing zip
So I wiped everything again and tried installing AOKP. It successfully installs. I try rebooting prior to flashing boot.img. It hangs on horse picture opening screen. So I flash the boot.img in Fastboot and reboot after erasing cache. When rebooting it hangs on opening white screen.
I'm baffled. What am I doing wrong?
Jussi31 said:
Here's a brief summary of what I attempted to do.
I wiped Delvik Cache; I wiped Cache; I did Factory Reset; I wiped System.
Next I tried installing CyanogenMod and received the following error messages:
assert failed: getprop
E: error executing updater binary in zip
Error flashing zip
So I wiped everything again and tried installing AOKP. It successfully installs. I try rebooting prior to flashing boot.img. It hangs on horse picture opening screen. So I flash the boot.img in Fastboot and reboot after erasing cache. When rebooting it hangs on opening white screen.
I'm baffled. What am I doing wrong?
Click to expand...
Click to collapse
I guess your recovery is not able to detect that your phone is one x+.. that's why assert failed error.. try changing the recovery( maybe CWM) and try again
Through trial-and-error, and reading hard, I figured out I had to install a compatible Kernel. I then was able to install, successfully, AOKP and it seems to work very smoothly. I'm just learning the ins-and-outs of everything. Thanks for your help.
Jussi31 said:
Through trial-and-error, and reading hard, I figured out I had to install a compatible Kernel. I then was able to install, successfully, AOKP and it seems to work very smoothly. I'm just learning the ins-and-outs of everything. Thanks for your help.
Click to expand...
Click to collapse
:good::good::good:
that is cool!
Hi all, Am new to the Nexus9, I picked one up quite cheap and thought I would have a go at flashing a decent Rom. I am having no problems flashing a rom but every time I try and flash Gapps the Tablet gets stuck in a bootloop. I have tried lots of versions of Gapps but mostly arm64. I managed at one stage to flash one via the internal memory that seemed to work but then couldnt get Play sevices to work. Tried another but stuck in bootloop again.
At the moment I am trying a version of Slimrom and have tried Lineage 14.1. Anyone got any suggestions?
I normally flash a new rom in this order if the new rom is in my Download folder:
- TWRP Wipe advanced, tick System,Data,Cache.
-Back
-Install, go to sdcard/Download
-Select rom.zip
-after finish go back
-Select gapps64.zip
-after finish installing I press clean Dalvik and Cache
- Reboot system.
Wait a while and install as new device.
This should work.
With a normal update of a rom I simply install the update without wiping my system.
johhnyhotrocks said:
Hi all, Am new to the Nexus9, I picked one up quite cheap and thought I would have a go at flashing a decent Rom. I am having no problems flashing a rom but every time I try and flash Gapps the Tablet gets stuck in a bootloop. I have tried lots of versions of Gapps but mostly arm64. I managed at one stage to flash one via the internal memory that seemed to work but then couldnt get Play sevices to work. Tried another but stuck in bootloop again.
At the moment I am trying a version of Slimrom and have tried Lineage 14.1. Anyone got any suggestions?
Click to expand...
Click to collapse
If you're using opengapps, they are having trouble booting on a fresh install on slim and LineageOS. Try an older build of slim or lineage, boot up and set up, then update to newest build.
Solution
johhnyhotrocks said:
Hi all, Am new to the Nexus9, I picked one up quite cheap and thought I would have a go at flashing a decent Rom. I am having no problems flashing a rom but every time I try and flash Gapps the Tablet gets stuck in a bootloop. I have tried lots of versions of Gapps but mostly arm64. I managed at one stage to flash one via the internal memory that seemed to work but then couldnt get Play sevices to work. Tried another but stuck in bootloop again.
At the moment I am trying a version of Slimrom and have tried Lineage 14.1. Anyone got any suggestions?
Click to expand...
Click to collapse
I had the same issue with my NEXUS 9 wifi, but this solution mentioned here worked for me!
I am using:
lineage-14.1-20180920-nightly-flounder-signed
open_gapps-arm64-7.1-mini-20180923
Vendor Version: n9f27m
wanderweg you are my hero!
Mods make this stickie in the first posts....
If the system doesn't start after flashing with gapps just do this...
After flashing, mount system from TWRP, go to the "Advanced" tab, click on Terminal and type the following command:
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
Just killed 2 days trying to figure it out and that's all it was.
P.S. Maybe roms can be updated to include the fix?
MOCKBA said:
wanderweg you are my hero!
Mods make this stickie in the first posts....
If the system doesn't start after flashing with gapps just do this...
After flashing, mount system from TWRP, go to the "Advanced" tab, click on Terminal and type the following command:
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
Just killed 2 days trying to figure it out and that's all it was.
P.S. Maybe roms can be updated to include the fix?
Click to expand...
Click to collapse
It's a gapps issue not a ROM issue. Every now and then the setup wizard is weird in opengapps.
basically i installed a magisk module that caused bootloop, uninstalled that module in twrp. wiped cache/dalvik just in case. phone got stuck on boot (not bootloop) with just the three 'thinking' dots above the android logo.
waited for about an hour before deciding something was up, so flashed magisk uninstaller.zip to remove the lot, wiped cache/dalvik again. (btw, the bad module was the only module i'd flashed)
now i'm stuck at the boot screen again, has been this way for coming up an hour, should i wait longer, is it optimizing my installed apps? or should i just resign to having to flash a rom again and reinstall all apps/settings etc?
foolishly i forgot to backup data before flashing the module. didn't expect this kind of headache!!
any advice please
its a bootloop. reinstall firmware.
Yep, firmware flash was the only way
Mohd Haikal said:
its a bootloop. reinstall firmware.
Click to expand...
Click to collapse
Reinstall firmware means i just have to flash MIUI 9.2.25 vendor firmware for pie by Akhil Narang, or I have to flash entire stock Miui by downloading the zip?
Just the vendor firmware. Depending on what ROM you have, you can install a newer version than 9.2.25. I use 9.3.25 with PE.
clonechill said:
Reinstall firmware means i just have to flash MIUI 9.2.25 vendor firmware for pie by Akhil Narang, or I have to flash entire stock Miui by downloading the zip?
Click to expand...
Click to collapse
You can try flashing only the boot.img file from the currently installed ROM's zip file
Hi all, this is my first question here.
I reverted to the stock ROM (11.2.0 Global), which I got from here, from LineageOS 17.1, but when I reinstall LineageOS, the phone shuts down during the first boot, and in subsequent reboots the phone shuts down after a few seconds, making it impossible to complete the setup process.
I followed all the steps, including formatting data and then doing an advanced wipe of /system and /cache in TWRP before installing LineageOS, and there were no error messages during the installation.
Thankfully, the stock ROM works fine, but I'd like to reinstall LineageOS.
Can anyone please help me with this?
Update: the same issue occurs with Pixel Experience.
The same happened to me too, for me I fixed it by flashing permissiver zip after flashing rom.
This was only needed only once after switching to custom rom from stock, after that you can flash roms normally i.e without permissiver.
Happend to me too ,after many tries got it fixed by flashing LOS 16 then clean flashed LOS 17.1 without cleaning the vendor partition. But for me PE was working fine only LOS 17.1 had issue like constant shutdown after installation when its boot up.
Ghoul2077 said:
The same happened to me too, for me I fixed it by flashing permissiver zip after flashing rom.
This was only needed only once after switching to custom rom from stock, after that you can flash roms normally i.e without permissiver.
Click to expand...
Click to collapse
Could you please provide a link?
Hi, I've recently repaired my mido with a new screen after a fall. After this I tried some custom roms. Initially I managed to install lineage 18.1. After I switched to dotOS. From this point on, the phone restarts a few seconds after the launcher appears. To fix this I used MiFlah to install latest MIUI, formatted data, wiped everything, tried TWRP and Orangefox, tried other custom roms with no changes. Now only stock MIUI11 works. Other custom roms (included lineage) gets the phone continuously rebooting. Could be an hardware problem? What am I doing wrong? It is the first time in ages I have problems flashing ROMS .-.
Thanks.
gabritb01 said:
Hi, I've recently repaired my mido with a new screen after a fall. After this I tried some custom roms. Initially I managed to install lineage 18.1. After I switched to dotOS. From this point on, the phone restarts a few seconds after the launcher appears. To fix this I used MiFlah to install latest MIUI, formatted data, wiped everything, tried TWRP and Orangefox, tried other custom roms with no changes. Now only stock MIUI11 works. Other custom roms (included lineage) gets the phone continuously rebooting. Could be an hardware problem? What am I doing wrong? It is the first time in ages I have problems flashing ROMS .-.
Thanks.
Click to expand...
Click to collapse
The vendor partition could have some code/ file that persists stock ui or system
and make sure your phone was rooted before flashing custom rom
and also via twrp flashing. from what Ive seen flash in twrp before flash custom rom( https://www.google.com/search?client=firefox-b-d&q=disable+encryption+treble ) then flash the "verity and encryption disabler ,theres another one to re enable encyption only " then flash custom rom
after flashing custom rom reboot poweroff(switch phone off via twrp)
reboot into twrp and flash whatever else you need
now reboot to system and your phone should work fine
Thanks, it worked!
I did:
Flash last miui with miflash
Flash recovery
Flash you suggested zip
Format data
Flash lineage 17.1 (android10)
WIpe system, data, cache, art cache
Flash any android 11 ROM
gabritb01 said:
Thanks, it worked!
I did:
Flash last miui with miflash
Flash recovery
Flash you suggested zip
Format data
Flash lineage 17.1 (android10)
WIpe system, data, cache, art cache
Flash any android 11 ROM
Click to expand...
Click to collapse
Holy **** how did you come up with this.
Either the zip with Magisk somehow fixed it or installing the android 10 rom somehow. Either way doesn't make sense
flairepathos.info said:
The vendor partition could have some code/ file that persists stock ui or system
and make sure your phone was rooted before flashing custom rom
and also via twrp flashing. from what Ive seen flash in twrp before flash custom rom( https://www.google.com/search?client=firefox-b-d&q=disable+encryption+treble ) then flash the "verity and encryption disabler ,theres another one to re enable encyption only " then flash custom rom
after flashing custom rom reboot poweroff(switch phone off via twrp)
reboot into twrp and flash whatever else you need
now reboot to system and your phone should work fine
Click to expand...
Click to collapse
Didn't work for me,
- did all the steps , exactly - flashed stock fastboot , then flashed Android 10 based rom crDroid + pico gapps. worked fine for 2 hours or so .
but interesting enough , phone freezes then shutdown without restarting , then i would go and trun it back on , but fingerprint not working now
heroboy107 said:
Didn't work for me,
- did all the steps , exactly - flashed stock fastboot , then flashed Android 10 based rom crDroid + pico gapps. worked fine for 2 hours or so .
but interesting enough , phone freezes then shutdown without restarting , then i would go and trun it back on , but fingerprint not working now
Click to expand...
Click to collapse
i think somewhere in the process the persist partition gets damaged .
heroboy107 said:
i think somewhere in the process the persist partition gets damaged .
Click to expand...
Click to collapse
so if you have magisk you can use a zip file to chmod 744 or 644 (it may be "chmod root 744" )the /persist partiton and thatll mean only true root has access
so 7 is read write execute 6 is read and write 4 is read only 5 is read execute i forgot which number was execute only 1 maybe?
so play with the permissions or look in the root folder for boot.p or permissions.sh then you can modify in there the permissions, it can cause bootloop , so always keep an original copy or youll hae to reflash(DISCLAIMER)
so you can pull the file using adb+root / or a root explorer
Copy it to phone then edit then copy to SDCARD
reboot to twrp then use shell/terminal "chmod 777" the partition where the file is / or read write everything
then copy the file and overwrite the original