So I have installed the stock Sammy 5.1.1 rom and flashed the alpha TWRP (available here on xda in the orginal development section) and its working great
I flashed super su 2.46 and now I'm stuck on boot
well at least the recovery is working
so if anyone want to try it go a head no risk
thank you and sorry for my bad english
Yeah installed twrp also today and seems to work fine, damn i love twrp recovery
Related
When I first upgraded from 4.4 to 5.1 I couldn't find any guide on how to upgrade my phone(without bricking it ) but I tried and it worked and it's very simple.
I'm using moto e xt1022 Indian version.
Previously I had:
-Official Kitkat 4.4 version with root
-TWRP 2.7.2.0 recovery
How I upgraded (and can you) to Official Lollipop 5.1 Rom:
1. I updated the recovery to [RECOVERY][Condor] TWRP 2.8.7 touch recovery [2015-05-05] . I used Flashify app to install recovery.
2. choose a flavour of lollipop roms from this post [ROM][5.1][STOCK][FLASHABLE ZIP] Stock Motorola Lollipop ROM Collection by lost101. I personally liked the Untouched version (459mb) because Xposed framework runs smoothly on this Rom so, I debloated it( to 280 MB) and flashed it.
2.1 this Rom is NOT ROOTED but when you successfully flash this ROM via TWRP 2.8.7, at the end of flashing TWRP will ask to root this ROM SELECT YES, that's how I rooted it.
3 phone booting will take some time.
4. After bootup, update your SU app to the latest version to avoid any problem.
optional: I also updated my Radio to Lollipop Radio Firmware from the same Lollipop ROM Collection thread. (but this Radio is entirely optional) I just wanted to test it and it's working fine so far..
XposedFramework Part
5. flash xposed-v7*-sdk22-arm-by-romracer-20150816.zip from twrp recovery [UNOFFICIAL] Xposed for Android 5.1
6. booting up will take some time.
7. open Xposed installer app in phone; download the GravityBox App from Download menu; install it then tick the app in Module option and restart. GravityBox will work flawlessly
I've also tried several other modules and they are working properly.
Hope this little guide will help new seekers
Cheers
Can you tell me lollipop radio version & any issues, thanks.
This was development section meant to be posting ROMs kernels, mods etc, Help guides are basically posted on general section.
saintmonte said:
Can you tell me lollipop radio version & any issues, thanks.
Click to expand...
Click to collapse
I haven't faced any issues with radio yet.
I tried to install 7.1.1 MAD in some different versions of TWRP and none of them worked (error 7). Can anybody share the TWRP version that works fine? Thanks. (Sorry for my english if i have mistakes)
TouceDTV said:
I tried to install 7.1.1 MAD in some different versions of TWRP and none of them worked (error 7). Can anybody share the TWRP version that works fine? Thanks. (Sorry for my english if i have mistakes)
Click to expand...
Click to collapse
You can use the MAD TWRP for install the new stable 7 N 7.1.1
Search in his thread
Link for TWRP needed:
http://www.mediafire.com/?062n97ps38h5rf4
Sent from my S3 using Tapatalk
Fix it in ROM and not with diffrent TWRP!
It is only M.A.D. bull****!
If you use the buggy MAD TWRP you have the same problems again if you switch to a non MAD ROM
https://forum.xda-developers.com/showthread.php?t=2522762
Fixed!
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
hello guys. i need a stock rom unrooted for twrp or rom manager if this exist or if some1 know any good custom rom with working magisk safenet etc. thanks for ur time guys.
atm i use a vibe custom rom that works pretty good with venom kernel and when i try to update magisk i got bootloop. i try lineage os but half safenet not works. same with remixos
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.