Hello XDA Community.
I wanted to flash a Resurrection Remix for my Galaxy J5 2015 (SM-J500F). I have downloaded it, copied to phone memory and I turned on TWRP. I wiped data, cache and dalvik. And I choosed Install option and choosed my RR ROM.
Zip signature verification disabled. I began flashing RR (Zip file). And on 75% flashing progress phone is rebooting and I go back to the TWRP, and I need to install official Android for my phone (this I'm doing through Odin). Why I can't flash RR???? Resurrection Remix is so amazing!
Information:
Phone: SM-J500F
TWRP: Uploaded through Odin
Resurrection Remix: Zip file
I tried 2 RR Roms, both failed.
If you need more info just ask me for it.
Thank you very much for your help.
Try to flash a newer version of TWRP and proceed with the ROM flash afterwards.
Thank you very much man! You saved my life . For you all: Resurrection Remix is really amazing!
I had the same problem a few days ago. Glad I could help !
Related
Hello. This is my first thread on xda. I downloaded the CM 13 unofficial ROM by mygalaxya (filename - "cm13.020160319unofficiala3ltexx.zip") for my Galaxy A300H running on Lolipop v5.0.2 (build number LRX22G.A300HXXU1BOK6). I successfully downloaded the ROM and placed it in my SDcard. I then booted into recovery mode in order to install it (TWRP 2.8.7.0). Then I wiped EVERYTHING (in wipe/advanced wipe) except sdcard. Then I tried to install the rom. Then it throws up an error (error executing updater binary in *filename.zip*). So I decided to replace the 'updater-binary' and 'updater-script file' in the zip file itself. I have another rom which works 'perfectly'. But it had a LOT of broken apps and it wouldn't let my phone charge. But it would install and boot up perfectly on my phone. So I extracted these two files from that old rom (which is the cm12.1 rom which weighs 294mb. It's also created by same developer 'mygalaxya'). I replaced the 2 files in new rom (cm13) and saved the zip file. I then moved it to the sdcard. Then I booted into recovery and tried to flash the cm13 again. It seemed to install without any problem. I turned on the phone normally. Then the glowing CM logo animation plays. I know that the first boot takes some time (on my old cm12.1 rom it was max. 5 minutes). I waited more than 20 mins, but nothing happened. The boot animation was continuously playing but it wasn't booting up. I tried wiping cache and dalvik cache in the recovery mode. I even tried to factory reset but that also DIDN'T help. Now what should I do? Reply ASAP. Any reply is really appreciated
cm 13 for a3 a300h
Hey bro. you need to be on twrp 3 for installing cm 13.1st istalll latest twrp 3 .which is available on XDA for Galaxy a3 a300h .then install cm 13
zuhaibsarwar said:
Hey bro. you need to be on twrp 3 for installing cm 13.1st istalll latest twrp 3 .which is available on XDA for Galaxy a3 a300h .then install cm 13
Click to expand...
Click to collapse
Thanks m8. Using TWRP 3.0.0-0 worked!
zuhaibsarwar said:
Hey bro. you need to be on twrp 3 for installing cm 13.1st istalll latest twrp 3 .which is available on XDA for Galaxy a3 a300h .then install cm 13
Click to expand...
Click to collapse
Thanks m8. Using TWRP v3 worked!
Hey folks,
I'm no noob,And I did search tons of post n treads before deciding to making one.
More than 6 months ago, I have tried Resurrection Remix, though I was aware it require JB Bootloader,so had flashed Loki Bootstacks.
Steps were;
-Downloaded RR zip, GApps,Loki Bootstacks(md5 checked)
-Flashed Loki Bootstacks
-Rebbot recovery
-Flash RR zip
-Flash GApps
-Wipe Cache n Dalvik
-Reboot System.
Upon reboot Screen got black! That's was the first time ever any of My Android brick!
Connected it to PC n saw bunch of Partitions( Qualcomm HSUSB_BULK 9006) immediately understood that it got Bricked!
Took sometime to learn n in under night, get back up n running with help of tools n appropriate guidelines.
After that Rooted again as it was back to Stock 20C took OTA zip from 20C > final KK build.
Few days I have played around with bunch of ROMs, tried every single ones available, and than one day exactly week later from first brick tried Resurrection Remix again.
Actually flashing ROM this time let me setup device n after updating SuperSU binary, prompt me to Reboot System, that's where all happen.:crying:
This time around it Bricked without showing any partition but Real Hard Bricked!! QHSUSB_BULK 9008
So my question to active flashaholic, what went wrong?
Why My G2(D800) got bricked only on Resurrection Remix OS and not any other ROM?
My G2 is still dead! Really hoping for some legitimate answer, why other ROMs didn't brick n only RR?
I've had many roms flashed on my op2 through twrp, but now whenever i try to flash any rom(cm, exodus, aicp etc.) I get error 7. I tried deleting asserts line on "updater-script" but no luck...
Current rom: Resurrection remix 5.6.9
shahark86 said:
I've had many roms flashed on my op2 through twrp, but now whenever i try to flash any rom(cm, exodus, aicp etc.) I get error 7. I tried deleting asserts line on "updater-script" but no luck...
Current rom: Resurrection remix 5.6.9
Click to expand...
Click to collapse
Hi, If you already have twrp recovery and you can boot into twrp recovery, then you need to download stock oxygen os 2.2.1 ota.
when you download oxygen os 2.2.1 ota, flash it via twrp recovery, after that wipe factory data reset, then you flash your custom roms later. this will bypass the error 7 and you will have to resume enjoying your custom roms.
Here's what happens, when u totally erases the system, data, and formats everything with twrp recovery, custom roms don't run again, i think they kinda need some basic files from the stock rom to enable them to run. i experienced this myself with aicp and this is how i fixed it. so go on, look for the oxygen 2.2.1 ota.zip, download, flash, then wipe data fastory reset, then you can now have your custom roms flashed and working. again.
Right!! but oos 3.0 official is also working
shahark86 said:
I've had many roms flashed on my op2 through twrp, but now whenever i try to flash any rom(cm, exodus, aicp etc.) I get error 7. I tried deleting asserts line on "updater-script" but no luck...
Current rom: Resurrection remix 5.6.9
Click to expand...
Click to collapse
It's there to protect you from flashing a ROM incompatible with your current bootloader (there's two of them, pre oos3 and oos3 bootloader/fastboot).
So if you want to flash a ROM which is Lollipop (or using Lollipop bootloader like easier versions of Graraks and Seraph08s builds) you will have to restore your phone to oos2.x.x first. Same goes the other way around, and also your recovery system must be compatible with respective bootloader.
This info should be force-feeded to every noob checking in on this forum hoping for an easy swapping of ROMs on this phone, which is not gonna happen because of this.
Hello!
I have an S5 that was running CM 14.1. I had moved from 13.0 to 14.1 with out whipping everything, so things were not perfect.
I wanted to move to Lineage 14.1 with a clean install.
I booted in recovery (Cyanogenmod Recovery) and whipped as much as possible.
When trying to Apply Update with the Lineage OS 14.1 nightly .zip, I got the "failed to verify signature" error. I have redownloaded the rom a second time to make sure I did not have a corrupted .zip.
I ended up reinstalling CM 13 because that is what I had not to far and needed a working phone.
So my question is about the recovery and the error I got with the Lineage rom.
Do I get the error because the type of recovery I have or does the Lineage OS .zip is known for generating this error (since it's still all very new)?
If the recovery is the problem, can I use the Official TWRP App to switch from Cyanogenmod recovery to TWRP ?
I have already tried to replace the recovery in download mode but Heimdall 1.4 generated an error as well regarding the "PIT file" so the process got interrupted.
Thank you in advance for any input!
bump!
Surely someone can answer this simple question!
thanks!
Hello guys,
i'm having the problem that whatever custom rom i'm trying to install with TWRP it will boot forever(>15min).
The stock OxygenOS boots just fine.
Rom's i've tried LineageOS 14.1, Resurrection Remix 5.8.3, ViperOS and some inofficial CM/LOS 13 versions.
Of course i tried to install all of them cleanly.
Once the installation failed or was corrupted and I had to use this unbrick guid to get access to my phone again: https://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Things i've tried so far: Reinstall TWRP, try different versions of each ROM and TWRP
Do you have any suggestions? Thanks in advance!
UPDATE: With clean install of newest OxygenOS(3.5.8) SimCard isnt being recognized.
bump