Hello, i would like to clarify a few things before i start changing the firmware on an LG L5 E610, so that i don't break it.
I have tried to flash the pre-rooted v20d image from http://forum.xda-developers.com/showthread.php?t=2405357 , and can verify that this works
I would like to use that rom to go to cyanogenmod 10.1, are the roms from http://get.cm/?device=e610 ok? (should i use the latest?) which version of gapps should i use?
If there is a problem, will KDZ Updater always be able to recover the device, even after cyanogenmod is flashed?
I've seen a few threads, where it says that the only way to revive the phone is to flash v10d_downgrade.kdz - is this for older phones? Can i flash the pre-rooted v20d image instead of this?
How many times can the phone be flashed?
Anything else to worry about?
Sorry for the dumb questions, but this is my first smartphone, and i would'nt like to break it so soon
cmpl said:
I have tried to flash the pre-rooted v20d image from http://forum.xda-developers.com/showthread.php?t=2405357 , and can verify that this works
Click to expand...
Click to collapse
Did you flashed it or no? I think its better a pre-root and cwm already installed kdz.
I would like to use that rom to go to cyanogenmod 10.1, are the roms from http://get.cm/?device=e610 ok? (should i use the latest?) which version of gapps should i use?
Click to expand...
Click to collapse
That's not cyanogenmod 10.1, its cyanogenmod 10 (Android 4.1.2)
And gapps are from 2012-10-11 date (on the net you can find a variety of gapps for cm10, but the normal are lik "gapps-jb-20121011-signed.zip")
If there is a problem, will KDZ Updater always be able to recover the device, even after cyanogenmod is flashed?
I've seen a few threads, where it says that the only way to revive the phone is to flash v10d_downgrade.kdz - is this for older phones? Can i flash the pre-rooted v20d image instead of this?
Click to expand...
Click to collapse
If you NEVER touch phone partitions (i mean, re-partition, format is allowed, but not add/remove/modify partitions), you can flash a KDZ no matter what ROM you have (stock, cyanogenmod, paranoid android, etc)
Before a ROM is installed, its recommended to format/wipe (depends on rom) system, cache and dalvik, & data and data/media partitions (is secure... as long as you flash a rom immediately after) via CWM (even if you want to flash a stock KDZ)
If you CAN'T access to CWM and the ROM is corrupted, you have to use v10d_downgrade because internally wipes all i said before, and install russian v10d. Then you can start again
I dunno if the pre-rooted kdz will have the same effect than v10d_downgrade.
How many times can the phone be flashed?
Click to expand...
Click to collapse
I don't know if there is a limit. But i've already flashed A LOT of times (15+)
Anything else to worry about?
Click to expand...
Click to collapse
Do always a backup, store ALL of your info in the external sd card, have always a kdz and a computer ready to flash
To enter CWM you have to hold down vol -/+ (depends on lastest KDZ flashed, can be both, can be one of them, try) and power and home button UNTIL the phone vibrates. Some people complains because the let go the buttons before and nothing happend.
Sorry for the dumb questions, but this is my first smartphone, and i would'nt like to break it so soon
Click to expand...
Click to collapse
That's why these forums are
It's my first android smartphone too, i had this questions over time and now I'm ussing PecanCM cm10.2 and i love it
thank you very much for the reply. now that i know the kdz updater will get me out of trouble, i installed cm-10.2-20130928-UNOFFICIAL-e610.zip and it works great so far
btw i've found information that cyanogen 10 (which is 4.1.2) needs v10 baseband firmware (which is 4.0.3) and not v20 (which is 4.1.2). do you know why? are the cm kernels based on compleately different (much older) sources?
Related
Stock Android 2.1 Éclair Recovery Backup! V20E Baltic
This is a Recovery Backup of Android 2.1 V20E Baltic ROM. All files in this rom are freshly extracted from the V20E_00.kdz update file, converted from .mbn to .img, ready to be flashed using Clockwork Recovery. No mods, just untouched stock ROM ^_^ Also, Remember to Wipe/Data factory reset before flashing to AVOID BOOTLOOPS!
NOTE: THIS IS NOT COMPATIBLE WITH MODIFIED PARTITION SIZES
(If you flashed Mur4ik's 250MB Data KDZ, YOU CANNOT USE THIS BACKUP! You will need to flash a regular Fastboot ROM using KDZ Updater to reverse the partition size change.)
FAQ:
Q: I get stuck at the Android boot logo after I flashed this. Is my device bricked?
A: No, you ignored the above and forgot to factory reset. Go into recovery, factory reset and reboot. Your phone will now fully boot.
NOOB: THIS BACKUP BRICKED MY DEVICE! (Believe me, people say this-.-)
A: Not possible. I cannot brick your device with this. Go away.
Q: Are there any mods to this ROM?
A: No. It is 100% stock.
Q: Why don't I just downgrade using KDZ?
A: Because if your PC dies during flashing, congrats on your new brick (I know the chances are slim, but hey, better to be safe, right?)
Download:
Download from MegaUpload
Size: Roughly 110.39MB (Compressed .zip)
Roughly 222MB (Uncompressed)
MD5: b17bf5ee2ef91f58ab78d07ce6a59945
Any questions? Just ask below.
Jack
thanks flashed that before rma - accepted good to use as development soruce - good work,bro ! love that !
mikegapinski said:
thanks flashed that before rma - accepted good to use as development soruce - good work,bro ! love that !
Click to expand...
Click to collapse
No problems, thanks!
Also added information on how to get original partition sizes back.
Jack
JackG256 said:
Stock Android 2.1 Éclair Recovery Backup! V20E Baltic
This is a Recovery Backup of Android 2.1 V20E Baltic ROM. All files in this rom are freshly extracted from the V20E_00.kdz update file, converted from .mbn to .img, ready to be flashed using Clockwork Recovery. The only modification to this ROM is that I have added Cyanogen's APN list, which allows this ROM to be compatible, out of the box, with your Mobile Data and saves you having to your settings again. (Some carrier's settings may not be included, Check Cyanogen's APN list) Also, Remember to Wipe/Data factory reset before flashing to AVOID BOOTLOOPS!
NOTE: THIS IS NOT COMPATIBLE WITH MODIFIED PARTITION SIZES
(If you flashed Mur4ik's 250MB Data KDZ, YOU CANNOT USE THIS BACKUP! You will need to flash an original Fastboot ROM using KDZ Updater to reverse the partition size change.)
Download:
Download from MegaUpload
Size: 110.75MB (.zip)
Roughly 222MB (Uncompressed)
MD5: 8305e31a1bdb571fd59a7db787acb6c1
Any questions? Just ask below.
Jack
Click to expand...
Click to collapse
I know this is newer but why is it special? How is it different compared to other stock ROMs?
nibras_reeza said:
I know this is newer but why is it special? How is it different compared to other stock ROMs?
Click to expand...
Click to collapse
It's not special, It just includes bugfixes or other. It's just better to have the newer software I guess. Meh, I only made the recovery backup for people to get back to 2.1 if they want, Because using KDZ could brick your phone. (The chances are slim, but it happens.)
Jack
Slightly OT:
JackG256 said:
It's not special, It just includes bugfixes or other. It's just better to have the newer software I guess. Meh, I only made the recovery backup for people to get back to 2.1 if they want, Because using KDZ could brick your phone. (The chances are slim, but it happens.)
Jack
Click to expand...
Click to collapse
Do you know what I've never understood? What is a Baltic rom? And what is the difference ? LOL
Jamielawther said:
Slightly OT:
Do you know what I've never understood? What is a Baltic rom? And what is the difference ? LOL
Click to expand...
Click to collapse
The Baltic ROM was designed for the countries in the Baltic areas (Estonia, Latvia and Lithuania) but it can be used for all over the world. I used Baltic instead of CIS as Baltic doesn't come with the CIS apps (like Yandex or other crapware) also I don't know the real differences but I think that it is just bugfixes and such.
KDZ updater is a tool used by LG customer care, right? In that case, it would be safer than recovery.
I guess they updated the Kernel as well. In any case, am using Swiftdroid. Thanks for the recovery images though. xD
JackG256 said:
The Baltic ROM was designed for the countries in the Baltic areas (Estonia, Latvia and Lithuania) but it can be used for all over the world. I used Baltic instead of CIS as Baltic doesn't come with the CIS apps (like Yandex or other crapware) also I don't know the real differences but I think that it is just bugfixes and such.
Click to expand...
Click to collapse
Ah , Going back to Baltic now then
Also , Do you know how I could install a theme for 2.1? All the ones I have from 4.pda use Metamorph , which reboots my phone whilst replacing framework-res , is there any way I can stop this or not use metamorph? I think it's the enoch theme , but no theme has ever worked
nibras_reeza said:
KDZ updater is a tool used by LG customer care, right? In that case, it would be safer than recovery.
I guess they updated the Kernel as well. In any case, am using Swiftdroid. Thanks for the recovery images though. xD
Click to expand...
Click to collapse
No, LG use R&D Test tool (I think) but Test Tool/KDZ reflashes the bootloader whenever you use it. Whereas recovery doesn't, which makes it safer because if the phone dies when flashing an image in recovery, you can just reflash it as the bootloader goes un-touched, but if your phone or computer dies during a test tool or KDZ flash, you now have a brick with a screen and buttons. Recovery is much, much, much safer, but LG don't use it as it is un-official software. LG also use it because if they upgrade your phone from 1.6 to 2.1, the bootloader needs to be reflashed and updated.
Also, these images are useful if you want to create 2.1 roms or go back to 2.1, say if your phone's screen broke etc.
Jack
JackG256 said:
No, LG use R&D Test tool (I think) but Test Tool/KDZ reflashes the bootloader whenever you use it. Whereas recovery doesn't, which makes it safer because if the phone dies when flashing an image in recovery, you can just reflash it as the bootloader goes un-touched, but if your phone or computer dies during a test tool or KDZ flash, you now have a brick with a screen and buttons. Recovery is much, much, much safer, but LG don't use it as it is un-official software. LG also use it because if they upgrade your phone from 1.6 to 2.1, the bootloader needs to be reflashed and updated.
Also, these images are useful if you want to create 2.1 roms or go back to 2.1, say if your phone's screen broke etc.
Jack
Click to expand...
Click to collapse
True about dying during boot-loader flashing but boot loader is small and it usually gets flashed within a minute or so. As per recovery, there is a higher chance of errors when flashing. I agree about your point. As long as recovery and bootloader are working, no matter what happens to system or boot, you could fix it.
I tried to flash this, also wiped cache, data and dalvik, but I'm getting boot loops.. I made a backup before so I reverted the changes... here's what I did:
copied into clockwork's backup folder, rebooted into clockwork mode, flashed and wiped cache, data and dalvik.. result: boot loops
any help?
thanks
denzig said:
I tried to flash this, also wiped cache, data and dalvik, but I'm getting boot loops.. I made a backup before so I reverted the changes... here's what I did:
copied into clockwork's backup folder, rebooted into clockwork mode, flashed and wiped cache, data and dalvik.. result: boot loops
any help?
thanks
Click to expand...
Click to collapse
I know, I was going to fix it but forgot, i'll do it now. Just give me 20 mins to upload and that.
Jack
Fixed version now uploaded, turns out it was a problem with the boot.img, all is resolved.
Jack
Thank you for the backup!
Maybe I will flash it. CM7 is slow for me.
Thank you so much, will try it later and post the results..
I have the same problems than denzig, my phone restarts after the LG's logo. Does a solution exist ?
Mat11
Uploaded another fixed version-.- If this doesn't work I will cry myself to sleep (/facepalm). (Joking about the crying myself to sleep bit by the way.)
Enjoy!
Jack
I flashed this but I immediately flashed infernal kernel so didn't get any boot loops... I've now realised why I stopped using Baltic ROMs - Google Navigation insists on using the US TTS. It's a roundabout NOT a circle
Still nice to have in my "ROM museum" though - thanks Jack!
Hello everybody, I was wondering if you could help me with this problem.
I got an lg g2 D802, I was on the official kit kat rom with knock code, with Dorimanx kernel 7.1, everything was ok, Im using the right baseband from kit kat, but I changed the rom to Paranoid Android new version, doing a full wipe/ clean install. But the first hours of use I noticed that my phone was overheating, so I started to read bout that, and I realize that Dorimanx kernel wasn't for PA Roms, only for stock based, so I decided to change my kernel, I wasn't sure what kind of kernel I need, so I search a bit and a page says that PA Roms was AOSP based, then I downloaded Furnace Kernel 2.5.1, AOSP version, flashed it and when the phone reboots, it repeatedly say: com. android.phone process has stopped. So technically I wasn't able to do anything. I boot into recovery again and try to flash stock kernel for kit kat, and when the phone tries to boot, an lg logo appears and say: Security error. I reboot into recovery once again and try to re- flash Dorimanx kernel, because it was late night and I wanted to sleep, so I though, just need the phone to boot and tomorrow I will change the kernel to a correct one, but when the phone tries to boot, got stuck in lg logo and the led flashing, since that, I ve been trying to flash so many kernels, included furnace stock version and cm version, with no result, I tried too cloudyfa, auxilium, stock, PAEK and nothing seems to work.
I did my backup when I flashed PA, but cause first hours seemed to be ok , I deleted it for storage reasons, so now i cant restore any backup, and I know doing a full wipe /clean install again will solve this problem, but I don't want to lose all my files and photos and stuff from years ago, and I know that is possible to flash a kernel and boot with this rom because when I flash furnace AOSP the phone turn on and show my lock screen and desktop, but the com.android.phone has stopped problem appears and don't let me do anything.
So, I ask to you: What can I do to flash the right kernel and don't lose my stuff?
Thank you for your answers and sorry for my bad English.
@Delintg2 Why don't you just flash paranoid android again? Flashing the rom changes the kernel as well
Art Vanderlay said:
@Delintg2 Why don't you just flash paranoid android again? Flashing the rom changes the kernel as well
Click to expand...
Click to collapse
Ive tried too, with no result, stuck o lg logo, and now the adb sideload say sending package and when 100% nothing happens on the phone :S
Delintg2 said:
Ive tried too, with no result, stuck o lg logo, and now the adb sideload say sending package and when 100% nothing happens on the phone :S
Click to expand...
Click to collapse
You have to flash the sideload zip when that's done. If you still can't boot into your ROM then its back to stock town for you I'm afraid. We've all been there :highfive:
Art Vanderlay said:
You have to flash the sideload zip when that's done. If you still can't boot into your ROM then its back to stock town for you I'm afraid. We've all been there :highfive:
Click to expand...
Click to collapse
Ok backing to stock :S, ty anyway m8
Hey guys, definitely new to this, haven't flashed a rom since I had a HTC Droid Incredible about five years ago. My brother just helped me root my phone and install TWRP, except when we go to look at flashing a new rom it states that you need TWRP 2.8.6.3. We are currently running 2.8.5.1 I found the 39A bootstack which supposedly includes TWRP 2.8.6.3, but I'm lost when it comes to how to flash this bootstack with the updated TWRP. Can anybody provide instructions, or a link to a previous thread? I did try using the search bar, but when you search "how to flash bootstack" the results are overwhelming because almost every post has the word "how," "flash," or "bootstack."
Really appreciate the help!
amcleod1995 said:
Hey guys, definitely new to this, haven't flashed a rom since I had a HTC Droid Incredible about five years ago. My brother just helped me root my phone and install TWRP, except when we go to look at flashing a new rom it states that you need TWRP 2.8.6.3. We are currently running 2.8.5.1 I found the 39A bootstack which supposedly includes TWRP 2.8.6.3, but I'm lost when it comes to how to flash this bootstack with the updated TWRP. Can anybody provide instructions, or a link to a previous thread? I did try using the search bar, but when you search "how to flash bootstack" the results are overwhelming because almost every post has the word "how," "flash," or "bootstack."
Really appreciate the help!
Click to expand...
Click to collapse
Interested in this as well. I've just started with the LG G2 and am at the same point. How do we go about flashing a boot stack? Does, as @amcleod1995 stated, the boot stack include the newer version of TWRP? Can someone provide a step by step tutorial or a video maybe? Thanks in advance! Here are the steps below we took to root and add recovery.
We both have our phones rooted following:
1. Root - http://forum.xda-developers.com/andr...vices-t3049772
2. Recovery ( TWRP) - http://forum.xda-developers.com/veri...-twrp-t3053134
Deathscyth3 said:
Interested in this as well. I've just started with the LG G2 and am at the same point. How do we go about flashing a boot stack? Does, as @amcleod1995 stated, the boot stack include the newer version of TWRP? Can someone provide a step by step tutorial or a video maybe? Thanks in advance! Here are the steps below we took to root and add recovery.
We both have our phones rooted following:
1. Root - http://forum.xda-developers.com/andr...vices-t3049772
2. Recovery ( TWRP) - http://forum.xda-developers.com/veri...-twrp-t3053134
Click to expand...
Click to collapse
amcleod1995 said:
Hey guys, definitely new to this, haven't flashed a rom since I had a HTC Droid Incredible about five years ago. My brother just helped me root my phone and install TWRP, except when we go to look at flashing a new rom it states that you need TWRP 2.8.6.3. We are currently running 2.8.5.1 I found the 39A bootstack which supposedly includes TWRP 2.8.6.3, but I'm lost when it comes to how to flash this bootstack with the updated TWRP. Can anybody provide instructions, or a link to a previous thread? I did try using the search bar, but when you search "how to flash bootstack" the results are overwhelming because almost every post has the word "how," "flash," or "bootstack."
Really appreciate the help!
Click to expand...
Click to collapse
Very simple, update twrp manually from blastagator's website, reboot to recovery , flash bootstack zip, reboot to recovery and the flash anything that requires it (ie: CAF roms) . Now you're on the latest bootstack (bootloader, modem and everything else that comes with it).
I'm in twrp right now (wiped the system)
Choristav said:
Very simple, update twrp manually from blastagator's website, reboot to recovery , flash bootstack zip, reboot to recovery and the flash anything that requires it (ie: CAF roms) . Now you're on the latest bootstack (bootloader, modem and everything else that comes with it).
Click to expand...
Click to collapse
can I install blastgator bumped recovery from within current TWRP recovery (I've 2.6.3.3) ? and the install blasgator bumped bootstack - I want cm 12.1 so the 3rd link from here http://blastagator.ddns.net/bootloader.php
roberto32 said:
can I install blastgator bumped recovery from within current TWRP recovery (I've 2.6.3.3) ? and the install blasgator bumped bootstack - I want cm 12.1 so the 3rd link from here http://blastagator.ddns.net/bootloader.php
Click to expand...
Click to collapse
Sure can.
I've been having issues with my phone, and I'm not sure if this is a HW issue or not, but no matter what I do, either I lose recovery or get a security error. I poked around and found some instructions in the CloudyG3 thread. They're for 3.0 but I would guess 3.3 wouldn't be different enough to brick this thing. Can't remember who the quote is from, I just copy/pasted it, but here it is:
Some of you sent me a PM asking for the install instructions on D800 and this is how you install CloudyG2 3.0:
Downloads:
1. Download CloudyG2 3.0 - https://www.androidfilehost.com/?fid=95897840722646001
2. Download Patch - https://mega.co.nz/#!sVY0mRTb!qn7S9B...3m_QpMQkgzunn0
3. Download Signal Patch - https://dl.dropboxusercontent.com/u/...l_Variants.zip
4. Download LP Baseband - http://blastagator.ddns.net/modem.php - d800-30f-modem-blastagator-signed.zip
5. Download KK Bootstack - http://blastagator.ddns.net/bootloader.php - bootstack-d800-KK_20c-blastagator-signed.zip
6. Optional: Download JB Bootstack in case if you want to revert the installation process and go back to your current ROM - http://blastagator.ddns.net/bootloader.php - bootstack-d800-JB_10d-blastagator-signed.zip
Flashing Process:
1. Backup the existing ROM (including EFS, Modem, etc.) in TWRP - very important and copy it over to the computer, just in case!
2. Wipe System + Data + Cache + Dalvik Cache - Do NOT select internal storage as it contains all your downloaded files + backups!
3. Flash KK Bootstack (downloaded from Step 5)
4. Flash LP Baseband (downloaded from Step 4)
5. Flash CloudyG2 3.0 (downloaded from Step 1) - Leave the default in Aroma when you have to pick the variant. Do NOT reboot the device as the patch installation (next Step) is very important.
6. Flash Patch (dowloaded from Step 2) - Select your variant.
7. Flash Signal Patch (downloaded from Step 3)
8. Reboot
Enjoy!
Click to expand...
Click to collapse
I'm guessing I have the incorrect files, most of the links I found in the thread with these instructions didn't seem to work so I Googled for them, maybe I don't even have the correct files. I took a screenshot in cmd of the exact filesizes.
Any help would be greatly appriciated!
level5music said:
I've been having issues with my phone, and I'm not sure if this is a HW issue or not, but no matter what I do, either I lose recovery or get a security error. I poked around and found some instructions in the CloudyG3 thread. They're for 3.0 but I would guess 3.3 wouldn't be different enough to brick this thing. Can't remember who the quote is from, I just copy/pasted it, but here it is:
I'm guessing I have the incorrect files, most of the links I found in the thread with these instructions were dead mega.co.nz links so maybe I don't even have the correct files. I took a screenshot in cmd of the exact filesizes.
Any help would be greatly appriciated!
Click to expand...
Click to collapse
you want to install cloudy g2 3.3?
this is whati did
used to root http://www.droidviews.com/easily-root-lg-devices-using-the-one-click-root-script/ if you are on lollipop it gets stuck at 90% twice after 3 attemps same stuck at 90% rebooted and it was rooted
then on playstore i used autorec canat remeber if it says v2.. but for lollipop installed and it checked my device and its said it was ready. so i just clicked twrp and it installed twrp then i downloaded blastogator twrp and installed cloudy g2 3.3 on d800 unlocked... sorry if you were refferimg to another version of cloudy..
raptorddd said:
you want to install cloudy g2 3.3?
this is whati did
used to root http://www.droidviews.com/easily-root-lg-devices-using-the-one-click-root-script/ if you are on lollipop it gets stuck at 90% twice after 3 attemps same stuck at 90% rebooted and it was rooted
then on playstore i used autorec canat remeber if it says v2.. but for lollipop installed and it checked my device and its said it was ready. so i just clicked twrp and it installed twrp then i downloaded blastogator twrp and installed cloudy g2 3.3 on d800 unlocked... sorry if you were refferimg to another version of cloudy..
Click to expand...
Click to collapse
Coming off a fresh TOT flash, I root with towelroot, flash TWRP using AutoRec, flash bootloader, then flashed Cloudy. It will boot at first, but then I run into "black screen of death" or security errors or when trying to boot to recovery, I'll run into similar issues. Does Blastagator's TWRP make the difference here?
level5music said:
Coming off a fresh TOT flash, I root with towelroot, flash TWRP using AutoRec, flash bootloader, then flashed Cloudy. It will boot at first, but then I run into "black screen of death" or security errors or when trying to boot to recovery, I'll run into similar issues. Does Blastagator's TWRP make the difference here?
Click to expand...
Click to collapse
no not really, but i do know that we had to use 2871 cause newer version were wiping f2fs, so now latest build its working but i dont think it has something to do .... am sorry i just got mine like a week ago and mine was in lollipop.. so i know nothing about coming from other version of android. dont even know whatsa tot flash.. i still need to learn alot..
check here and see if you can find a way to fix this good luck
http://forum.xda-developers.com/lg-g2/general/05-10-index-guides-fixes-roots-t3218178
level5music said:
Coming off a fresh TOT flash, I root with towelroot, flash TWRP using AutoRec, flash bootloader, then flashed Cloudy. It will boot at first, but then I run into "black screen of death" or security errors or when trying to boot to recovery, I'll run into similar issues. Does Blastagator's TWRP make the difference here?
Click to expand...
Click to collapse
I had the exact problem happen to me ....... I got the black screen of death .... phone wouldnt boot ....... and when i used the kk bootloader i would lose recovery ..... I was coming from kk to CloudyG2 ....
This is how i solved.
1. Flashed back to stock, stumproot to root Autorec v1 for bootloader
2. used Flashify to upgrade to 2.8.7.1 ( its now 2.8.7.3)
3. Downloaded n used bumpted LP bootstack and flashed blastagator stripped rom (its in flashable zip and installs everythin including modem .... patches etc EVERYTHING) http://forum.xda-developers.com/att-g2/development/rom-stock-lollipop-30b-stripped-t3144195
4. Downloaded kk bootstack , CloudyG2 3.3 and clean flashed in recovery
I have been enjoying Cloudy ever since ...... D800
Thanks all, got it running! Cloudyfa has done some absolutely brilliant work here with this ROM, as well as xdabbeb with the advanced camera driver and xCam. I'm usually a vanilla-or-nothing guy with my Android ROMs but this one is quick and power efficient. The KitKat ROM that shipped with the phone was super bloated and gross, but I'll admit LG UX 4.0 isn't really that offensive, plus I like the goodies like Multi-Window and QuickRemote. Once I disabled/hid some of the remaining LG bloat, it's surprisingly pleasant and not really that far from AOSP aesthetically. Again, cheers to those who provided the assist on this one for me!
... now my only question is, should I try CloudyG3?
hello guys,
this is my first thread here on Xda forum.
it's my very first time i want to install a custom Rom on my smartphone. could someone please let me know which Rom is the most stable, less battery draining Rom to install?
thanks a lot!
gelie68 said:
hello guys,
this is my first thread here on Xda forum.
it's my very first time i want to install a custom Rom on my smartphone. could someone please let me know which Rom is the most stable, less battery draining Rom to install?
thanks a lot!
Click to expand...
Click to collapse
I am currently using DarkRom...great battery life and have not encountered any bugs as yet.
gelie68 said:
hello guys,
this is my first thread here on Xda forum.
it's my very first time i want to install a custom Rom on my smartphone. could someone please let me know which Rom is the most stable, less battery draining Rom to install?
thanks a lot!
Click to expand...
Click to collapse
LOS is pretty good on both fronts, Pure Fusion seems to be based on AOSP, good battery life; Nuclea was pretty good too.
Read EVERYTHING or you may DFU brick your phone (disassembly required) or even wipe your IMEIs. Remember that your phone model is the one on the back of the phone, NOT NECESSARILY the one that the system says!
For custom ROMs you'll need the UNIVERSAL BOOTLOADER, your corresponding MODEM FILE, an image of TWRP 3.1.1-0, and MAGISK on your phone. Reboot only after flashing everything, and after flashing the Universal Bootloader, select Install Image and select the TWRP image, then flash it to the recovery partition
Choose an username... said:
LOS is pretty good on both fronts, Pure Fusion seems to be based on AOSP, good battery life; Nuclea was pretty good too.
Read EVERYTHING or you may DFU brick your phone (disassembly required) or even wipe your IMEIs. Remember that your phone model is the one on the back of the phone, NOT NECESSARILY the one that the system says!
For custom ROMs you'll need the UNIVERSAL BOOTLOADER, your corresponding MODEM FILE, an image of TWRP 3.1.1-0, and MAGISK on your phone. Reboot only after flashing everything, and after flashing the Universal Bootloader, select Install Image and select the TWRP image, then flash it to the recovery partition
Click to expand...
Click to collapse
i have installed the TWRP 3.1.1.0 and rooted the phone. everything is ok till now!
i don't understand what you mean with the need for the universal bootloader, corresponding modem file.
thanks for your hellp!
gelie68 said:
i have installed the TWRP 3.1.1.0 and rooted the phone. everything is ok till now!
i don't understand what you mean with the need for the universal bootloader, corresponding modem file.
thanks for your hellp!
Click to expand...
Click to collapse
To install any custom ROM you first need to flash the A2017X_Universal_Bootloader.zip, then flash TWRP 3.1.1-0 (the universal bootloader installs an old version of TWRP which will appear after a reboot, you simply overwrite it by flashing the TWRP.img) then the modem file for your own model (for example A2017G_Modem.zip), then the ROM, then Magisk_14.3.zip.
The A2017X_Universal_Bootloader.zip and the modem files are in the LOS thread.
Choose an username... said:
To install any custom ROM you first need to flash the A2017X_Universal_Bootloader.zip, then flash TWRP 3.1.1-0 (the universal bootloader installs an old version of TWRP which will appear after a reboot, you simply overwrite it by flashing the TWRP.img) then the modem file for your own model (for example A2017G_Modem.zip), then the ROM, then Magisk_14.3.zip.
The A2017X_Universal_Bootloader.zip and the modem files are in the LOS thread.
Click to expand...
Click to collapse
i used the Axon7toolkit to flash recovery and root. it says i can use it to flash Roms...
anyway it's a new world to me and i feel lost here.
do you advise i read any beginner guide about Flashing roms and modding?
thanks a lot.
gelie68 said:
i used the Axon7toolkit to flash recovery and root. it says i can use it to flash Roms...
anyway it's a new world to me and i feel lost here.
do you advise i read any beginner guide about Flashing roms and modding?
thanks a lot.
Click to expand...
Click to collapse
Don't know about any guides, but basically read the posts entirely before actually trying to do anything. The axon7toolkit is nice and all but you just shouldn't use it for flashing stuff. If you have TWRP, you can simply forget about the toolkit for pretty much everything.
To install a ROM you have to use the Install button on TWRP. If you have an error 7 it probably means that your TWRP version is old, check that and install the latest TWRP image if that happens.
If the ROM asks for a pin on startup, go to Wipe then Advanced then Format data