Hi all
Thanks for a great Forum!!
I have a minor issue
Specs: LG G2 D802 32GB - Love that phone! :good:
I have been running it stock for the last 4 years but recently many of my favorite apps does not support kitkat no more, so time to upgrade i thought
I read several post in here and watched a bunch of videos on youtube and gave it a try.
So... First, rooted my phone with IOroot - OK
Installed Autorec and TWRP 2.7.0.0 - OK
upgraded TWRP to 3.2.1.0 - OK
Downloaded Lineage 14.1 D802 and Gapps 7.1 mini - OK
Booted to TWRP and Wiped Dalvik, System, Data and Cache - OK
installed Lineage 14.1 - OK
Wiped Dalvik - OK
Installed Gapps - OK
Wiped Dalvik - OK
Rebooted to System - Not OK :crying:
As far as I can read in here, The problem lies in the boot loader, but herein lies my question. Autorec according to one post in here, downgrades the bootloader to JB but the FAQ Q12, in this thread tells me that Autorec keeps/installs the KK bootloader...
And according to Lineage OS, I need the KK bootloader to run. And alot of posts/threads recommends NOT to use hybrid bootloaders etc...
So, what did I do wrong??? Do I still have the KK bootloader or do I have the JB Bootloader?? If I have the JB and would like to upgrade to KK - how would I go about it in my current situation where Im stuck at LG logo. Or do I have an entirely different problem?
Btw, TWRP works fine and I have all the backups - But Im not interested in reverting back to stock because then Im back with the unsupported phone/apps issue...
Best regards
Dutchmhk
dutchmhk said:
Hi all
Thanks for a great Forum!!
I have a minor issue
Specs: LG G2 D802 32GB - Love that phone! :good:
I have been running it stock for the last 4 years but recently many of my favorite apps does not support kitkat no more, so time to upgrade i thought
I read several post in here and watched a bunch of videos on youtube and gave it a try.
So... First, rooted my phone with IOroot - OK
Installed Autorec and TWRP 2.7.0.0 - OK
upgraded TWRP to 3.2.1.0 - OK
Downloaded Lineage 14.1 D802 and Gapps 7.1 mini - OK
Booted to TWRP and Wiped Dalvik, System, Data and Cache - OK
installed Lineage 14.1 - OK
Wiped Dalvik - OK
Installed Gapps - OK
Wiped Dalvik - OK
Rebooted to System - Not OK :crying:
As far as I can read in here, The problem lies in the boot loader, but herein lies my question. Autorec according to one post in here, downgrades the bootloader to JB but the FAQ Q12, in this thread tells me that Autorec keeps/installs the KK bootloader...
And according to Lineage OS, I need the KK bootloader to run. And alot of posts/threads recommends NOT to use hybrid bootloaders etc...
So, what did I do wrong??? Do I still have the KK bootloader or do I have the JB Bootloader?? If I have the JB and would like to upgrade to KK - how would I go about it in my current situation where Im stuck at LG logo. Or do I have an entirely different problem?
Btw, TWRP works fine and I have all the backups - But Im not interested in reverting back to stock because then Im back with the unsupported phone/apps issue...
Best regards
Dutchmhk
Click to expand...
Click to collapse
I know we've already spoken on another post about this but I'll reply here for thoroughness incase somebody else runs into the same problem. All the above was correct except you missed the bootloader.
flash Daniel Stuarts CAF bootstack. Available here------> https://github.com/danielstuart14/hybrid_caf_bootstacks/tree/LG-CAF/d802
Then flash the Rom.
Then flash Gapps
Then reboot and enjoy.
As a sidenote, it's worth reading the notes on installing. Lineage is a continuation of Cyanogen and as such they are compatible. However, you can't go from cyanogen 13 to lineage 14. To get to lineage 14 you will need either cyanogen 14 or lineage 13. Details can be read here---->https://www.lineageosroms.org/forums/topic/update-lineage-os-13-14-1-on-cyanogenmod-13-14-1-rom/
blueplasticsoulman said:
I know we've already spoken on another post about this but I'll reply here for thoroughness incase somebody else runs into the same problem. All the above was correct except you missed the bootloader.
flash Daniel Stuarts CAF bootstack. Available here------> https://github.com/danielstuart14/hybrid_caf_bootstacks/tree/LG-CAF/d802
Then flash the Rom.
Then flash Gapps
Then reboot and enjoy.
As a sidenote, it's worth reading the notes on installing. Lineage is a continuation of Cyanogen and as such they are compatible. However, you can't go from cyanogen 13 to lineage 14. To get to lineage 14 you will need either cyanogen 14 or lineage 13. Details can be read here---->https://www.lineageosroms.org/forums/topic/update-lineage-os-13-14-1-on-cyanogenmod-13-14-1-rom/
Click to expand...
Click to collapse
Thanks buddy :good:
Gave it a go yesterday and it worked like a charm !!
only thing that bothers me a bit is the knock on knock off code....it´s not like it used to be, but i´ll do some more reading on that subject - and who knows maybe someone found/made a solution for that as well
Btw, Antutu bech = 60871
Dutchmhk
Related
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.
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.
Hello thanks for letting me join this forum i have two stock kitkat 4.4.4 s3 basic mobiles that need updating any help would be appreciated in doing this as ive never done this before have tried to flash but dont seem to work ive got root gapps etc .looked at twrp etc but it wont update cleared cache etc can anyone point me in the right direction as i am a complete noob at this .Thanks .OK guys ive updated one to 5.1 have you any recommendations next operating system can i flash twrp flashify windows 10 a nightmare with sp flash tools got there in the end thanks.
Yeah, I had the same problem too. I'm using: [ROM] [6.0.1] Unofficial Sandstrangers LineageOS/CyanogenMod13 , Haven't had any problems so far, and it seems just as fast as the stock ROMS.
Assuming the lollipop ROM you flashed is the same as mine, you should be able to flash any new ROMs directly from TWRP now.
I don't know if there are a tread about this I did not see one. Every time I flash android 11 I can't get the wifi to work any advice would be greatful thanks.
First give some info about Which rom or kernel you had installed, how you installed clean flashed or dirty flashed, flashed oos before flashing custom rom. Last have you followed flashing rule,p because of so many things are experiencing by people when flashing custom roms,
kmr168401 said:
First give some info about Which rom or kernel you had installed, how you installed clean flashed or dirty flashed, flashed oos before flashing custom rom. Last have you followed flashing rule,p because of so many things are experiencing by people when flashing custom roms,
Click to expand...
Click to collapse
I flashed latest oss to both slots reboot to the welcome screen then reboot to recovery flashed
[OFFICIAL] KekHunter-420 - A Pentesters ROM for OnePlus 6/6T format data reboot no wifi but about 90% of android 10 or 11 roms has no wifi
dude1981 said:
I flashed latest oss to both slots reboot to the welcome screen then reboot to recovery flashed
[OFFICIAL] KekHunter-420 - A Pentesters ROM for OnePlus 6/6T format data reboot no wifi but about 90% of android 10 or 11 roms has no wifi
Click to expand...
Click to collapse
Sorry to say this I think I remembered someone also have same problem, so better post it in that forums and ask for help from the developer, may be he will help, he is actually respond to each and every questions, so I think he can help you to solve this issue.
Best of luck.
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.