Keep getting the same error after trying to install HD_revolution, also tried cyaneogen mod 9 both give me that error, reboots into a bootloop.
Any reason why this is happening? I tried flashing TWRP then reflashing 4ext over it , used a different sd card.
Related
Maybe someone can help me here. Using TWRP 2.8.0.1 I am unable to fully install any rom.
I had slimkat on my phone and decided I wanted to try regular CM 11. So I wiped everything in advanced wipe so I could start fresh.
Put the Rom and Gapps on my phone then tried to flash.
However while installing CM, it just goes about its business until the progress bar hangs at updating partition details.
It also appears I cannot move files to the internal memory from the sd card.
Are my partitions messed up?
All that happens now is getting stuck at the samsung boot logo or rebooting into TWRP...
Any help?
Gorkytje said:
Maybe someone can help me here. Using TWRP 2.8.0.1 I am unable to fully install any rom.
I had slimkat on my phone and decided I wanted to try regular CM 11. So I wiped everything in advanced wipe so I could start fresh.
Put the Rom and Gapps on my phone then tried to flash.
However while installing CM, it just goes about its business until the progress bar hangs at updating partition details.
It also appears I cannot move files to the internal memory from the sd card.
Are my partitions messed up?
All that happens now is getting stuck at the samsung boot logo or rebooting into TWRP...
Any help?
Click to expand...
Click to collapse
Yes partitions could be mixed up but my first port of call would be to return to stock with odin and if that boots and works then start again and don't use twrp try PhilZ recovery.
If partitions are corrupt there are things you can try but I would first try to get your phone to boot then report back.
tallman43 said:
Yes partitions could be mixed up but my first port of call would be to return to stock with odin and if that boots and works then start again and don't use twrp try PhilZ recovery.
If partitions are corrupt there are things you can try but I would first try to get your phone to boot then report back.
Click to expand...
Click to collapse
Thanks for your help! Because of you I tried PhilZ, which then told me it couldn't successfully open/read the rom from the SD card. (Something twrp didn't tell me).
I then changed my SD card for another one I had laying around and it worked. (Strange the old one failed since I formatted it atleast a few times)
Once again, thanks for your tip!
This is now solved!
Hello!
I have a OnePlus One running CM13. Recently, I got into a boot loop and had to go to a backup I had made in TWRP v2.8.7.0, but after I did this, the SIM card was not detected. My friend told me this was a bug in versions 8.6.1 and later, and said I should flash 8.6.0, then go back to that backup. This made TWRP accessible, so I tried a factory reset. My phone rebooted and nothing happened. So I installed cyanogen recovery instead and reinstalled CM, but that didn't fix anything. I tried to flash TWRP again, and now neither recovery is accessible.
Now I have an extremely buggy CM that reboots automatically every 2 minutes with no recovery mode and my SIM isn't detected. I'm considering installing Ubuntu Phone or buying a Nexus, but what I really want is to install TWRP, get my SIM detected, and install CM13 release track.
What in the world should I do?
I've been trying to find a recovery fix short of flashing back to stock as the new version of TWRP flashed in flashify caused my device to not want to boot past the logo screen of the recovery mode for TWRP. I tried flashing the 2.8.7 version to no avail. The only recovery that partially works right now is the CM13 nightly I tried in order to factory reset and look at my options. Does anyone have any suggestions to get recovery working again?
EDIT:
fix was easier than I thought, simply factory reset in cm13 nightly, flashed 2.8.4 then 3.00 and good to go.
Had the same problem. Try removing the SD card, if you have one. That did it for me. You might have to reformat it in a computer to get it working again.
j4g3rb0mb3d said:
Had the same problem. Try removing the SD card, if you have one. That did it for me. You might have to reformat it in a computer to get it working again.
Click to expand...
Click to collapse
This fixed my problem. :good:
Hey all, so I decided to go from stock rooted to a custom rom, and see the progress since I last tried it and I encountered the following problem:
I formatted data and factory reset, and then I installed the custom rom, followed by the GAPPS.
Twrp rebooted every time I tried installing Gapps, so I was confused.
The following error occurred when before Aroma started:
"E:Legacy environment property did not initialize successfully. Properties may not be detected"
The next thing I did was I rebooted recovery, no cigar. I tried reinstalling the recovery, no cigar.
I tried formatting data again, and got the error that /data can't be mounted now. This started to worry me lol.
So I tried repairing it and then rebooting, and I tried updating to a newer TWRP but even there, the twrp version won't update. Its still the same number.
I'm too afraid to reboot and see if the rom boots or not, but when trying to flash even a stock rom ZIP it tells me the following:
"This package is for "Joan,h932" devices; this is a ""."
so twrp doesn't know what phone I have?
I am trying right now to restore my TWRP backup but it doesn't want to restore the data, so I'm trying without.
If you can help I would appreciate it very much!!
Here are the screenshots https://imgur.com/a/SLCPdIQ
EDIT: I finally figured it out. Hitting the reboot menu did nothing, because it was for some reason stuck and just rebooted into the same recovery version with the glitch.
I had to do a hard reset, and the finger dance again, and now everything is fixed.
hey guys just looking for some help. ive been modding and flashing phones from 2014, but its always gone really smoothly, so my diagnostic ability is lacking.
it started with flashing twrp. my bootloader is unlocked, usb debugging on, device is showing in adb and fastboot, and i can flash twrp without any issues. hoowever when i go to boot twrp, only the stock recovery boots. i tried to flash twrp using the XiaoMiTool v2, but the same thing happened. i eventually got around this by just booting twrp instead of trying to flash it. so i got in, took a full back-up and started installing a custom rom.
the first one i tried was ParanoidAndroid Quartz. i wiped cache, dalvik and storage then transferred it to my phone, tried to flash and got "zip verification failed". so i turn off zip verification and tried again. it flashed perfectly with zero errors. however, when i reboot the phone it would only boot to stock recovery and not twrp (expected) or the new rom. i tried that a few times, then tried LineageOS, and MSM Xtended 10. all of them had the same issue, the flashed without a hitch, then wouldnt boot.
i also tried flashing a new fw-vendor and it just straight up failed. Then i decided to cut my losses and restore my twrp backup, and that came back with the error, "extractTarFork() process ended with error: 255"
Software before i began these attempts was completely stock, so i dont know what is going wrong, but as of now, my phone is bricked, i cant install a new rom or restore my back-up.
any help is appreciated guys. thanks
You can figure out this problem with
1 Copy backup folder to computer
2- Format Data - Yes , Wipe Everything
3- Install ROM that you have installed before and boot
4- Go to TWRP, format data yes reboot recovery
5- Paste backup folder to internal storage and restore