Database Users

Oneplus Two Getting error 7 on several ROMs?

Hey everyone. I recently started messing with ROMs on my Oneplus Two, and for some reason I keep getting error 7 after trying to install ROMs.
I'm doing everything the exact same for every ROM I try, but it seems a third of the time I get error 7. I was wondering if there's something specific with my phone that could be causing this?
I've asked my friend to try out some of the same ROMs on his Nexus 6 and they seem to work fine.
One ROM in particular I'm having this problem with is Resurrection Remix.
I'm fairly sure I'm installing everything correctly, so any feedback on this issue would be great.
Thanks!

You need to use hybrid recovery. Look for garak twrp hybrid 3.0.2.0 and flash within twrp. Bootloader is set on lollipop and marshmallow ROM conflicting.

Change the Twrp version or go for Grarak's Twrp that will be fine

Akash1998 said:
Change the Twrp version or go for Grarak's Twrp that will be fine
Click to expand...
Click to collapse
http://forum.xda-developers.com/oneplus-2/general/recovery-twrp-3-0-2-hybrid-supports-oos-t3362904 is this a working recovery that will flash all ROMs to the oneplus 2? Or is Grarak's the only solution as of now? Thanks

I'm in Garak version on TWRP (Orange one) and currently on CM13. Now I'm trying to clean flash AOSPA but getting Error 7, Any way to fix this?
Edit : Tried flashing Official firmware OOS 3.0.2 and then flash again AOSPA but still same error.
Edit 2 : Flashed TWRP 3.0.2.0 and all is fine now.

FIXED!
Alright cool I ended up installing the hybrid twrp and it works great now! Thanks guys.

HELP regarding Upgrade to MM STOCK ROM OR CM 13.0 !!!

Hi guys, its been a few days since I joined here. [Read : I am a noob/newbie in Android related things, and I desperately need help.]
In July (maybe, I forgot), I rooted my ZE550KL, using exactly this method from the website of www-asus-zenfone-com. :cyclops:
Now that, my android seems aged, I wanna shift/upgrade to Marshmallow/Nougat, be it Stock or Custom ROM.
Few days earlier, I unlocked my Bootloader using the Unofficial Bootloader Unlocking Method, as found on this Forum.
I also installed TWRP Recovery, and I tried to flash CM-14.1 [7.1] Nougat-Nightly through TWRP, but, unfortunately, resulted in Status 7 Error. I tried to solve the problem by removing "asserts" section in Update-Binary text file, in the build. But, again, I seemingly worsened the problem; as I got Status 6 error thereby. So, I did factory reset, and I still retain root.
Now, today as I am going through the Official thread of CM 14.1 Nougat, I saw numerous users reporting Bugs of connection issues (something like Wifi to Mobile Data switch problem), which I would like to OBVIOUSLY AVOID, as I want a stable, bug-less build. So, I am thinking to go with the last snapshot build of CM 13.0 Marshmallow.
Here comes the my question : " SHOULD I FLASH CM 13.0 MM -- OR -- STOCK ROM OF MM -- OR -- RESURRECTION REMIX MM ROM?? "
In any of the case, please guide me through the process of doing so.
And, if I have to flash CM 13.0 MM, what would I do if I encounter Status Error 7 again ? :crying:

first you have to upgrade it to marshmallow using stock rom. Then you can flash cm13 or cm14.1

Devc100 said:
first you have to upgrade it to marshmallow using stock rom. Then you can flash cm13 or cm14.1
Click to expand...
Click to collapse
Please, like I said, guide me through how to do it. Thanks in advance, in case you help. :good:

Ph4nToM_Z3rO said:
Hi guys, its been a few days since I joined here. [Read : I am a noob/newbie in Android related things, and I desperately need help.]
In July (maybe, I forgot), I rooted my ZE550KL, using exactly this method from the website of www-asus-zenfone-com. :cyclops:
Now that, my android seems aged, I wanna shift/upgrade to Marshmallow/Nougat, be it Stock or Custom ROM.
Few days earlier, I unlocked my Bootloader using the Unofficial Bootloader Unlocking Method, as found on this Forum.
I also installed TWRP Recovery, and I tried to flash CM-14.1 [7.1] Nougat-Nightly through TWRP, but, unfortunately, resulted in Status 7 Error. I tried to solve the problem by removing "asserts" section in Update-Binary text file, in the build. But, again, I seemingly worsened the problem; as I got Status 6 error thereby. So, I did factory reset, and I still retain root.
Now, today as I am going through the Official thread of CM 14.1 Nougat, I saw numerous users reporting Bugs of connection issues (something like Wifi to Mobile Data switch problem), which I would like to OBVIOUSLY AVOID, as I want a stable, bug-less build. So, I am thinking to go with the last snapshot build of CM 13.0 Marshmallow.
Here comes the my question : " SHOULD I FLASH CM 13.0 MM -- OR -- STOCK ROM OF MM -- OR -- RESURRECTION REMIX MM ROM?? "
In any of the case, please guide me through the process of doing so.
And, if I have to flash CM 13.0 MM, what would I do if I encounter Status Error 7 again ? :crying:
Click to expand...
Click to collapse
While flashing CM13 if that error 7 includes "asus.verify trustzone failed..." Then its bcoz of need to update modem files (LP to MM)....
Easy way to overcome it is..... download MM modem ZIP from second post of OFFICIAL CM13 thread (120MB) and flash it using TWRP (If you are using twrp).... THEN you can flash cm13 hopefully without error 7....
If you are using stock recovery then Either u can flash twrp and use above method... OR... Download ASUS ZE550KL firmware zip file from ASUS site (1.6GB) .... Put it in SDCARD... Then boot to stock recovery and use "apply update from sdcard" option... select ZIP... Alongwith firmware Ur Modem files will also update to MM... and now u can flash twrp and then cm13...
sorry.. I know if i am lazy to post direct links...
Try it.. I will help if i can

aadi50 said:
While flashing CM13 if that error 7 includes "asus.verify trustzone failed..." Then its bcoz of need to update modem files (LP to MM)....
Easy way to overcome it is..... download MM modem ZIP from second post of OFFICIAL CM13 thread (120MB) and flash it using TWRP (If you are using twrp).... THEN you can flash cm13 hopefully without error 7....
If you are using stock recovery then Either u can flash twrp and use above method... OR... Download ASUS ZE550KL firmware zip file from ASUS site (1.6GB) .... Put it in SDCARD... Then boot to stock recovery and use "apply update from sdcard" option... select ZIP... Alongwith firmware Ur Modem files will also update to MM... and now u can flash twrp and then cm13...
sorry.. I know if i am lazy to post direct links...
Try it.. I will help if i can
Click to expand...
Click to collapse
Thanks, dude. One question, should I get CM 13.0 or Resurrection Remix ?

Ph4nToM_Z3rO said:
Thanks, dude. One question, should I get CM 13.0 or Resurrection Remix ?
Click to expand...
Click to collapse
We have both stable RR and CM13.
CM is simple and clean and less loaded.... RR is most feature rich Custom rom we have alongwith stability...
Rest depends on what type of user, u are... If u like trying differnt ROMs... Start with CM13...
If u just want to have a feature rich longtime setup, U can use RR directly without wasting time... It is based on CM, So it obviously have everything CM has.... :good:

Ph4nToM_Z3rO said:
Please, like I said, guide me through how to do it. Thanks in advance, in case you help. :good:
Click to expand...
Click to collapse
Latest Stock Marshmallow:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-21.40.1220.1877-user.zip
Stock RecoveryRestore it using TWRP)
https://drive.google.com/open?id=0B2BGto29cXq1NjYySjRES21yOTg
Last Lollipop Software:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-1.17.40.1531-user.zip
First Lollipop Software:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-1.11.40.299-user.zip
First Do A nandroid backup of your phone. So that if any thing goes wrong, U can recover it.
Then Download both the Stock MM and Recovery file named TWRP.zip.
Extract TWRP.zip.
Then take both the MM software and Xtracted TWRP folder in a memory card.
Then Open TWRP recovery in ur phone and restore the stock recovery.
Then Erase Every Thing including System.
Then Restart The recovery. Now you will see that the recovery has gone back to the stock recovery.
Now flash the stock marshmallow from your memory card.
Then flash TWRP from fastboot and thn u can flash any supported custom Android MM or Android N.
N.B. If it dosent work. Then you have to first install the last lollipop Zenfone 2 Laser(Z00LD) software then install the marshmallow.

After replacing my display touch are not responsive.

My screen is entirely broken.. so i replace display at market and then almost all custom rom boot very well but after screen lock touch are note working.. we have to reboot device and first time touch working but after screen lock it's not responsive..
Resurrection Remix treble with moun kernel & stock rom working fine..
Any other rom are not working after screen lock.
Please any one help for this problem??

Prince parth said:
My screen is entirely broken.. so i replace display at market and then almost all custom rom boot very well but after screen lock touch are note working.. we have to reboot device and first time touch working but after screen lock it's not responsive..
Resurrection Remix treble with moun kernel & stock rom working fine..
Any other rom are not working after screen lock.
Please any one help for this problem??
Click to expand...
Click to collapse
I have this exact same problem. I tried with LiquidRemix and didn't check any other ROMs. Thought it was some kind of hardware problem but after reading your comment i guess it wasn't, as you said its working in RR. Thanks for finding that out. Now i am going to try each and every ROM available to check which one works and which one don't. I also think this must be a kernel problem as there are no hardware issues. Can you flash moun kernel in different ROMs to check whether it works or not?

ImSSin said:
I have this exact same problem. I tried with LiquidRemix and didn't check any other ROMs. Thought it was some kind of hardware problem but after reading your comment i guess it wasn't, as you said its working in RR. Thanks for finding that out. Now i am going to try each and every ROM available to check which one works and which one don't. I also think this must be a kernel problem as there are no hardware issues. Can you flash mourn kernel in different ROMs to check whether it works or not?
Click to expand...
Click to collapse
Yes I checked lineage os, all android pie based ROMs but it didn't work.. currently I'm using Miui10 port and it's working fine??

Prince parth said:
Yes I checked lineage os, all android pie based ROMs but it didn't work.. currently I'm using Miui10 port and it's working fine
Click to expand...
Click to collapse
Cosmicdan's Twrp is not working for me. Only mohancm's twrp 3.2.1-2 is working but after locking and relocking the screen in TWRP.
Just flashed RR non treble and the touch is not working after the screen lock
How did you flash RR treble if the cosmicdan's twrp is not working. Was your device already partitioned for treble or is there any workaround?

ImSSin said:
Cosmicdan's Twrp is not working for me. Only mohancm's twrp 3.2.1-2 is working but after locking and relocking the screen in TWRP.
Just flashed RR non treble and the touch is not working after the screen lock
How did you flash RR treble if the cosmicdan's twrp is not working. Was your device already partitioned for treble or is there any workaround?
Click to expand...
Click to collapse
Yes Cosmicdan's Twrp not working but if you install stock ROM and then install Cosmicdan's Twrp then it will work for sure..

Prince parth said:
Yes Cosmicdan's Twrp not working but if you install stock ROM and then install Cosmicdan's Twrp then it will work for sure..
Click to expand...
Click to collapse
Hmm i'll try that in a bit (making backups 1st). Can you please guide me how you got MIUI 10 working as I am not able to do so. Should i flash stock nougat ROM 1st and then flash MIUI 10? I tried following the steps stated in the forum but i am always getting bootloops.
Sorry for bugging you with my nooby questions :silly:

ImSSin said:
Hmm i'll try that in a bit (making backups 1st). Can you please guide me how you got MIUI 10 working as I am not able to do so. Should i flash stock nougat ROM 1st and then flash MIUI 10? I tried following the steps stated in the forum but i am always getting bootloops.
Sorry for bugging you with my nooby questions :silly:
Click to expand...
Click to collapse
Don't need to flash stock ROM I'm on Resurrection Remix treble ROM and for flashing I followed steps stated in forum.. it's work for me no bootloops.
First fastboot flash userdata userdata.img and then boot into Twrp and flash ROM zip that's all.

ImSSin said:
Hmm i'll try that in a bit (making backups 1st). Can you please guide me how you got MIUI 10 working as I am not able to do so. Should i flash stock nougat ROM 1st and then flash MIUI 10? I tried following the steps stated in the forum but i am always getting bootloops.
Sorry for bugging you with my nooby questions :silly:
Click to expand...
Click to collapse
Userdata.img is not necessary, just install the rom and format data(must) then reboot

Thnx for the help guys but after spending hours flashing different ROMs, TWRPs and kernels, I finally found the solution for the touch screen bug.
eXtreme kernel is the only kernel that was able to fix the screen completely. Its working in all of the custom ROMs (tried on LOS15.1 & 16, RR, LR Oreo and pie, etc.)
The stock versions of francokernel, void kernel are able to fix the touch screen but it breaks WiFi so they are not a complete fix.
And btw stock versions of Franco,extreme,void kernels work on the stock ROM.

my touch doesnt work on pin screen and in twrp **help** after flash from stock oreo to this rom exl. format data /system and cache..
must i calibrate this or?? when i pres 1 touch meen 9 homebuttons too
is my touch broken or its a bug??
//after flash oreo 8.1 with mi flash ... touch doesnt work

yasars said:
my touch doesnt work on pin screen and in twrp **help** after flash from stock oreo to this rom exl. format data /system and cache..
must i calibrate this or?? when i pres 1 touch meen 9 homebuttons too
is my touch broken or its a bug??
//after flash oreo 8.1 with mi flash ... touch doesnt work
Click to expand...
Click to collapse
have you tried flashing the extreme kernel?

extreme kernel v11 not working only V8 working for me.
What about you guys??

only with kernal 4.9 based custom roms, i have touch issues as described in here. and yeah i had screen replacement too.
now i can't flash any new pie roms as they all are based on 4.9 kernals and i can't find the old pie roms based on 3.18(link dead)..right now on los15.1
:crying::crying::crying::crying::crying::crying::crying:

Same problem here
ImSSin said:
have you tried flashing the extreme kernel?
Click to expand...
Click to collapse
ImSSin
Were you able to solve this problem? Can you put the link to download the kernel?

GT-I9505: Best Custom ROM and what order of installation?

Hello,
I have a GT-I9505 with an untouched Android 5.0.1 and I want to use a Custom ROM. Questions:
1. Which ROM is currently the best one available?
2. Can Anyone provide me a foolproof instructions / order of installing everything?
Thanks in advance

There are many tutorials on XDA on flashing a custom rom, it`s easy once you know how. YouTube also has some great vid`s to watch step by step.
My advice is 1st install a custom recovery like TWRP, concentrate on that first, you will need to download Odin software to flash TWRP to your phone, after that it`s as simple as downloading a zip rom to your sd card and flashing to your phone through TWRP recovery.
ALWAYS BACKUP your current working setup and read the entire rom description as SOME may have a few functions not working.
So far I have flashed about 5 diffrent rom`s to my i9505, all of which have been great, im currently using - [JDCTeam] Aosp Extended Pie Release 2.91 [9.0.0_r21] [unofficial] - with no problems.

Has anyone managed to get any custom ROM to work on a SM-A405FN/DS ?

Hello !
Has anyone actually managed to get any custom ROM to work on a Samsung Galaxy A40 SM-A405FN/DS ?
Mine is currently running the current latest stock ROM (SM-A405FN_2_20211030045838_jg43vcqbiw_fac) downloaded with Frija and I managed to install TWRP from here : https://forum.xda-developers.com/t/recovery-a40-teamwinrecoveryproject-3-6-x-unofficial.4364575/
However, ANY custom ROM that I try to install :
https://forum.xda-developers.com/t/a11-r-arm64-a40-lineageos-18-1-unofficial-by-kevios12.4335409/
https://sourceforge.net/projects/eurekaroms/files/Samsung/A40/R/lineage/
GSI
maybe others that I forgot
will either bootloop or end up with a black screen.
Looking at the following threads, I'm starting to wonder if the SM-A405FN/DS is custom-ROM-compatible at all ?
https://forum.xda-developers.com/t/help-my-a405fn-wont-boot-any-custom-rom.4337041/
https://forum.xda-developers.com/t/samsung-a40-black-screen.4354421/
https://forum.xda-developers.com/t/galaxy-a40-infinite-loop-impossible-to-turn-on.4337343/

Im running CrDroid 7.13 without any issues with root and gapps. Many custom roms bootloop because of your newer firmware with Bit/SW REV.
Security Patch Lvl. being 4 and those custom rom were built on the older firmware with probably patch level 3. I had installed DotOS fan edition fully working like a year ago, then I tried some new custom roms, which somehow broke my system so the system couldnt start up even after reflashing original boot image, so I reflashed to the newest firmware which was working, then I tried flashing older one and it wouldnt boot, it just shows black screen with error bit/sw 3 boot 4. So you have to flah roms, whose are built on the newer bit level to boot up, the best is CrDroid and now the newest ALT-F4 version 0.0.3 from this forum: https://forum.xda-developers.com/t/rom-oneui-3-1-a40-alt-f4-v0-0-1-updated-2021-12-18.4373813/
I tried it myself and it is the best for this phone, it is fully debloated and pre-rooted stock rom. I also tried CrDroid 8x, everything works for me, but it fells slow and the ram is almost maxed out. I also recommend upgrading to this TWRP: https://forum.xda-developers.com/t/recovery-official-twrp-for-galaxy-a40-a405fn.4025587/
The unofficial twrps had some bugs for me. I hope this helps and happy flashing!

THANK YOU for your comprehensive reply !! I'll give ALT-F4 a try as soon as I can !

breversa said:
THANK YOU for your comprehensive reply !! I'll give ALT-F4 a try as soon as I can !
Click to expand...
Click to collapse
Good luck!

Well, luck has not been enough: after updating TWRP to the official version, I tried yesterday to install ALT-F4 0.0.3 but got the exact same result: black screen, need to reflash the stock ROM to make it boot (even to recovery !!) again.
Would you have any other idea ?
EDIT:
I actually tried crDroid in the past, to no avail either.