Could someone please help me to put a custom rom on my Lg G3 D855TR, 2 gb ram / 32 storage?
My version is: Android 5, v20n-global-si
Kernel stock: 3.4.0
What guide do I have to read to do that?
Thanks
Olofaiolo said:
Could someone please help me to put a custom rom on my Lg G3 D855TR, 2 gb ram / 32 storage?
My version is: Android 5, v20n-global-si
Kernel stock: 3.4.0
What guide do I have to read to do that?
Thanks
Click to expand...
Click to collapse
Hi there, I happen to own the same phone (d855TR, Android 5, v20n-global-si, Kernel stock: 3.4.0) and I've been trying for some days... But today, I have succeeded.
That's how I've got it done, finally:
1.) Root your phone using KingRoot
(I've used version 5.3.8, but the app will anyway update automatically, if you are connected to Wifi)
(I've tried a lot of other rooting strategies, too: LG One Click Root, Towelroot, Stumproot, but for this specific phone, they all failed.)
2.) Install "AutoRec"
(Initially, I left away this step, but this resulted in a "Secure Boot Error" while rebooting and the following steps failed, then. Installing TWRP manually, via official app or via ADB failed at this step, too. But after installing "AutoRec" everything went fine.)
3.) "AutoRec" automatically installs TWRP, but it is an older version (2.8.7.), so you should update TWRP to the latest version.
4.) Having done this, you should be able to install any CustomROM. I've installed LineageOS 16.0 and up to now, everything seems to be O.K.
Basically, I followed this guide:
https://forum.xda-developers.com/showpost.php?p=67602605&postcount=749
(Here you will also find a download link for "AutoRec".)
I applied this guide successfully to the d855TR variant, inspite of the warning in the disclaimer not to use it for any other phone than d855. According to this guide, it was designed for 30b-firmware, but my version was 20n and it worked.
Good luck!
Zymomonas said:
Hi there, I happen to own the same phone (d855TR, Android 5, v20n-global-si, Kernel stock: 3.4.0) and I've been trying for some days... But today, I have succeeded.
That's how I've got it done, finally:
1.) Root your phone using KingRoot
(I've used version 5.3.8, but the app will anyway update automatically, if you are connected to Wifi)
(I've tried a lot of other rooting strategies, too: LG One Click Root, Towelroot, Stumproot, but for this specific phone, they all failed.)
2.) Install "AutoRec"
(Initially, I left away this step, but this resulted in a "Secure Boot Error" while rebooting and the following steps failed, then. Installing TWRP manually, via official app or via ADB failed at this step, too. But after installing "AutoRec" everything went fine.)
3.) "AutoRec" automatically installs TWRP, but it is an older version (2.8.7.), so you should update TWRP to the latest version.
4.) Having done this, you should be able to install any CustomROM. I've installed LineageOS 16.0 and up to now, everything seems to be O.K.
Basically, I followed this guide:
https://forum.xda-developers.com/showpost.php?p=67602605&postcount=749
(Here you will also find a download link for "AutoRec".)
I applied this guide successfully to the d855TR variant, inspite of the warning in the disclaimer not to use it for any other phone than d855. According to this guide, it was designed for 30b-firmware, but my version was 20n and it worked.
Good luck!
Click to expand...
Click to collapse
Thank you very much, I will try this.
Initially, I've installed TWRP without the official TWRP App and I managed to install LineageOS 16 as CustomROM. But as I installed the official TWRP App later, strange things happened: Suddenly, I wasn't able any more to boot the system, and only the start of the CustomROM showed up, but then the phone automatically rebooted into recovery (TWRP).
So maybe, it will be safer not to install the TWRP App on the d855TR. TWRP without the "Official TWRP App" is doing fine (after re-installation).
Zymomonas said:
Hi there, I happen to own the same phone (d855TR, Android 5, v20n-global-si, Kernel stock: 3.4.0) and I've been trying for some days... But today, I have succeeded.
That's how I've got it done, finally:
1.) Root your phone using KingRoot
(I've used version 5.3.8, but the app will anyway update automatically, if you are connected to Wifi)
(I've tried a lot of other rooting strategies, too: LG One Click Root, Towelroot, Stumproot, but for this specific phone, they all failed.)
2.) Install "AutoRec"
(Initially, I left away this step, but this resulted in a "Secure Boot Error" while rebooting and the following steps failed, then. Installing TWRP manually, via official app or via ADB failed at this step, too. But after installing "AutoRec" everything went fine.)
3.) "AutoRec" automatically installs TWRP, but it is an older version (2.8.7.), so you should update TWRP to the latest version.
4.) Having done this, you should be able to install any CustomROM. I've installed LineageOS 16.0 and up to now, everything seems to be O.K.
Basically, I followed this guide:
https://forum.xda-developers.com/showpost.php?p=67602605&postcount=749
(Here you will also find a download link for "AutoRec".)
I applied this guide successfully to the d855TR variant, inspite of the warning in the disclaimer not to use it for any other phone than d855. According to this guide, it was designed for 30b-firmware, but my version was 20n and it worked.
Good luck!
Click to expand...
Click to collapse
I can confirm this works with no problems. Already updated to 3.5.1
Related
I have a Moto G4 Athene (not Plus, and not Play).
I did the following:
unlocked bootloader
flashed TeamWin recovery
installed SuperSu 2.79 SR3 from TeamWin install
The phone no longer boots. Just a black screen. Flashing notification light if put on USB.
I can still get into the bootloader, and from there into TeamWin recovery, but I'm not having any luck beyond that.
Sadly, I didn't create a backup.
I tried installing LineageOS 14.1, pushing with ADB in recovery, and then installing with TeamWin. Even though I can add the file to the phone and I can run the install, a reboot returns a black screen.
Any advice? I'm afraid this isn't looking too good.
By the way, you can just work with twrp after installing that... stock recovery (fastboot adb) doesn't belong anymore. At first I would suggest that you post the details which are shown in your bootloader.
Furthermore I would recommend just to flash stock rom and testing that case.
Sent from my Moto G (4) using XDA Free mobile app
Ferwerda said:
I have a Moto G4 Athene (not Plus, and not Play).
I did the following:
unlocked bootloader
flashed TeamWin recovery
installed SuperSu 2.79 SR3 from TeamWin install
The phone no longer boots. Just a black screen. Flashing notification light if put on USB.
I can still get into the bootloader, and from there into TeamWin recovery, but I'm not having any luck beyond that.
Sadly, I didn't create a backup.
I tried installing LineageOS 14.1, pushing with ADB in recovery, and then installing with TeamWin. Even though I can add the file to the phone and I can run the install, a reboot returns a black screen.
Any advice? I'm afraid this isn't looking too good.
Click to expand...
Click to collapse
First of all, if you read their corresponding threads, you need to do the following when rooting:
- Unlock bootloader/flash TWRP (you did)
- Flash a custom kernel (Vegito or ElementalX)
- And then wipe ART/Dalvik Cache
Second, for LineageOS- you cannot dirty flash custom ROMs, EVER EVER EVER! By this I mean you have to wipe system/data/cache/dalvik etc.- you can ignore Internal Storage and the SDCard/OTG.
You may (should) have to flash the Moto G4 Nougat radio that's floating around XDA somewhere. LOS worked fine for me without doing that, but I know other ROMs require it.
Finally, as a quick heads up, all Moto G4 Plus ROMs work fine with the G4, including any stock ROMs/backups.
Edit: I heavily suggest Magisk or phh SU over SuperSU- Magisk allows you to use SnapChat and Pokemon Go, and phh's is open source.
Thanks for the responses.
I was able to restore the phone with a stock rom I found on these boards. After that, I received two OTA, one to 6.0.1 and then the current to 7.0.0.
I have the same problem than you... Can you send me the link that you use to fix it?
Ferwerda said:
Thanks for the responses.
I was able to restore the phone with a stock rom I found on these boards. After that, I received two OTA, one to 6.0.1 and then the current to 7.0.0.
Click to expand...
Click to collapse
raulcalaca said:
I have the same problem than you... Can you send me the link that you use to fix it?
Click to expand...
Click to collapse
Just flash ElementalX 1.04 kernel (after flashing SuperSu or Superuser or Magisk) when trying to root STOCK Nougat 7.0 as it's designed to thwart any root attempt.
Ferwerda said:
Thanks for the responses.
I was able to restore the phone with a stock rom I found on these boards. After that, I received two OTA, one to 6.0.1 and then the current to 7.0.0.
Click to expand...
Click to collapse
can you please give the step by step guide you followed to recover your phone!!!
I've had my 6P since Nov of 15, and I have always run it with a stock rom that is rooted. I've used Heisenberg's guide since day one, and never run into any considerable trouble.
Today though, after not updating the rom for a while, I am running into two issues. I went from angler nmf26f to the most current one, n2g47o.
Thing 1 - after I install twrp through fastboot, I can load into it and everything is fine. However, after I reboot, I can no longer load it again. When I go into the bootloader and select Recovery, after a few moments I get a screen saying 'No command'
I have reinstalled twrp a few times but it has done nothing to help.
Thing 2 - Root is no longer working. I have installed the newest SuperSU through twrp and while the app is present on the phone, it says root undetected.
Any of you folks run into anything similar? The phone/rom works fine otherwise. Thanks!
I had the same issue from 7.0 and forward. SUpersu causes a bootloop even on a fresh rom. You could give Magisk a try it worked for me at least.
DirtyHennessy said:
I had the same issue from 7.0 and forward. SUpersu causes a bootloop even on a fresh rom. You could give Magisk a try it worked for me at least.
Click to expand...
Click to collapse
Thanks! I will try that.
Seamus1 said:
I've had my 6P since Nov of 15, and I have always run it with a stock rom that is rooted. I've used Heisenberg's guide since day one, and never run into any considerable trouble.
Today though, after not updating the rom for a while, I am running into two issues. I went from angler nmf26f to the most current one, n2g47o.
Thing 1 - after I install twrp through fastboot, I can load into it and everything is fine. However, after I reboot, I can no longer load it again. When I go into the bootloader and select Recovery, after a few moments I get a screen saying 'No command'
I have reinstalled twrp a few times but it has done nothing to help.
Thing 2 - Root is no longer working. I have installed the newest SuperSU through twrp and while the app is present on the phone, it says root undetected.
Any of you folks run into anything similar? The phone/rom works fine otherwise. Thanks!
Click to expand...
Click to collapse
Have you made sure to update your radio, bootloader and vendor to the most recent version? Make sure to also try flashing twrp again but do everything through fastboot flash commands on your pc.
Seamus1 said:
I've had my 6P since Nov of 15, and I have always run it with a stock rom that is rooted. I've used Heisenberg's guide since day one, and never run into any considerable trouble.
Today though, after not updating the rom for a while, I am running into two issues. I went from angler nmf26f to the most current one, n2g47o.
Thing 1 - after I install twrp through fastboot, I can load into it and everything is fine. However, after I reboot, I can no longer load it again. When I go into the bootloader and select Recovery, after a few moments I get a screen saying 'No command'
I have reinstalled twrp a few times but it has done nothing to help.
Thing 2 - Root is no longer working. I have installed the newest SuperSU through twrp and while the app is present on the phone, it says root undetected.
Any of you folks run into anything similar? The phone/rom works fine otherwise. Thanks!
Click to expand...
Click to collapse
Flash root in TWRP before your first boot into the stock rom. On Nougat 7.0+, stock recovery replaces TWRP on boot if you do not. This solves both of your problems. When you clean flash and install a custom rom, with or without root, TWRP will remain. If you just use stock unrooted, then you should flash root before first boot each month when you update.
Sent from my Nexus 5X using Tapatalk
SuperSu 2.80 & 2.81 broke root for most phones - including mine. I had to flash 2.79 SR3 to get root again. Chainfire released 2.82 this morning but I haven't tried it yet.
https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
If you boot to twrp first time mount system and use the filemanager to delete recovery-from-boot.p under system. Use magisk instead of supersu for root.
Hello,
I've installed twrp on my lg g2 802. Using twrp i tried to install lineageos, but on reboot the screen remains black. I see the monitor on but nothing happens. I have to force the reboot. I can still go into recovery but i don't understand where is the problem.
I already tried to wipe everything, and i installed latest nightly of lineageos (no gapps).
Da you have an idea?
I have this same exact problem. I hope a solution is out there!
i installed from a kitkat. Maybe this can be a problem? Should i install lineage from a lollipop?
Flash this
https://forum.xda-developers.com/lg-g2/development/boot-g2-hybrid-bootstacks-t3183219
I got LineageOS to work!
It was a long grind of reading various posts on here and looking up other info on google, but I finally got my phone to run LineageOS.
The three things that I think are key are:
Making sure your phone is starting off with kitkat. I wasn't able to root my phone with lollipop. Stumproot, towelroot, and ioroot all didn't work. Once I downgraded to kitkat, I rooted successfully with ioroot.
After getting TWRP, updating it to 3.1.0. I had to first get an older version and then flash 3.1.0
Change the bootloader to kitkat if it isn't on it already. I used Bootloader Changer.
emilio84music said:
i installed from a kitkat. Maybe this can be a problem? Should i install lineage from a lollipop?
Click to expand...
Click to collapse
Yes u need lp bootstacks. Or you can simply get to the stock lollipop using flashtool and then flash lineage os
Thank you for support. Now it works
Followed this youtube guide --> How to Root Moto G4 Plus, Unlock Bootloader and Install Recovery!
(his youtube is gizmoddict, xda is restricting the link)
On last step I had to install the zip, and it would reboot into the phone, except it didn't.
xt1625 moto g4 is now stuck in a twrp bootloop and I have no idea what to do, help is appreciated.
If this is the guide in question: https://www.youtube.com/watch?v=dK2uacpjGwc then are you running stock Nougat 7.0 on your device?
If so, that guide is too old to be useful - the stock Nougat kernel appears to be much stricter with being rooted on and so you must use a custom kernel (e.g. ElementalX or vegito) to root successfully on stock Nougat. If you were running Marshmallow as in the guide, then it should have worked (though depending on the version of SuperSU you flashed).
I would try to copy a custom kernel to your device and attempt to flash that via TWRP, see if you can get your device to boot.
echo92 said:
If this is the guide in question: then are you running stock Nougat 7.0 on your device?
If so, that guide is too old to be useful - the stock Nougat kernel appears to be much stricter with being rooted on and so you must use a custom kernel (e.g. ElementalX or vegito) to root successfully on stock Nougat. If you were running Marshmallow as in the guide, then it should have worked (though depending on the version of SuperSU you flashed).
I would try to copy a custom kernel to your device and attempt to flash that via TWRP, see if you can get your device to boot.
Click to expand...
Click to collapse
Yes that would be the link to the video, and I believe it came stock as 7.0 nougat? (not 100% on that)
Currently searching XDA for the custom kernel you mentioned, sounds like it should be easy to get working thank you.
echo92 said:
If this is the guide in question: then are you running stock Nougat 7.0 on your device?
If so, that guide is too old to be useful - the stock Nougat kernel appears to be much stricter with being rooted on and so you must use a custom kernel (e.g. ElementalX or vegito) to root successfully on stock Nougat. If you were running Marshmallow as in the guide, then it should have worked (though depending on the version of SuperSU you flashed).
I would try to copy a custom kernel to your device and attempt to flash that via TWRP, see if you can get your device to boot.
Click to expand...
Click to collapse
In twrp and checked on pc to see that there is only twrp on internal storage, attempting to install ElementalX-G4-2.00.zip right now.
It worked thank you (atleast I think it is), currently selecting the MHz for the cpu frequency (obvious choice of stock). Appreciate the help.
NVM not working, now it won't boot into twrp. Not sure what in the world is going on anymore with this phone :/
NVM to that as well, 3rd time is the charm in twrp is back again.
Figured it out I think, it says "No OS Installed! Are you sure you wish to reboot?" after installing that zip file. Why does it say that?
Ok lineage OS is installed, super happy about it, thanks for suggesting that kernel thing otherwise I'd not have found this. Super easy to get rolling.
I really try to do stuff on my own without having to make other people repeat themselves a million times but this process is just so complicated and confusing that it's giving me a headache.
My goal: Be able to boot up LineageOS 16.
Code:
httpsforum.xda-developers.comnote-4snapdragon-devrom-lineageos-16-0-t3900807
It says it requires MM firmware and TWRP 3.2 or higher.
I have the retail 900V Note 4.
So far I have managed to downgrade to 5.1.1 and unlock the bootloader. (It says MODE: Developer)
From there I was able to install TWRP 3.0.2.
But now what?
Right now I have a phone that won't boot because there is no OS on it.
1. I can't get Odin to flash any other TWRP besides the 3.0.2 version. Odin just freezes halfway through and never completes. I'm assuming this might be because I'm not on an unlocked MM build yet. Currently still on LP.
2. I'm unsure how to get root back once I upgrade to a MM build. (I only have access to WiFi atm and this guide says it will disable it.)
Code:
https://forum.xda-developers.com/note-4-verizon/development/howto-bootloader-unlock-upgrade-to-t3398144
Any help is greatly appreciated.
I'm no expert so some of the things I'll suggest may not work.
As a first thought have you tried installing Lineage from TWRP 3.0.2
I'd suggest
1. downloading the OEM MM ROM from Sammobile and install that first so at least you have an OS to start with.
2. after setting it up install the official TWRP App update to the latest version of TWRP
3. ensure SuperSU is on the internal drive although I've not had problems installing it from a MicroSD and install it from TWRP Recovery. You should now have a rooted phone on the latest version of TWRP
4. put the Lineage ROM on the internal drive although again I've not had problems installing from a MicroSD (although it does take longer) and after 'Wiping' the system (it should tell you what steps are required from the Lineage guidance) install it.
5. After setup you will probably have to install SuperSU again or Magisk assuming there's no trace of SuperSU left on the system.
Hopefully someone will jump in and comment if I've missed something obvious or got it all wrong. Although I've rooted all 3 of my SM-N910Fs and SM-N910C at least once and installed various ROMs I don't consider myself particularly knowledgable. So far I've not bricked any of my phones or Tablets.
I really appreciate the reply.
Currently I am trying to flash 5.1.1 stock onto the phone and Odin just freezes about 25% into system.img.ext4
I have tried a dozen times.
I believe what makes my phone so difficult to flash is the stock bootloader is locked.