i just recently got an LG Optimus L7 (p705g), flashed it with homero's v10k rooted, unlocked bootloader, etc firmware. so now it says it is the p700. my question is, are there any custom roms that i can flash to my phone that will increase performance and keep root status with an unlocked bootloader? if so, please give me a simple tutorial on how to do so. currently my optimus l7 is running with an overclocked cpu maxed at 1.008 ghz. depending on what i have running in the background, i get up to 200 mb of ram, sometimes more. on top of all that, would it be better to just update to homero's v20a, rooted, unlocked bootloader, cwm, etc? and how would i do that safely without losing any data or having to make a backup?
please either post a tutorial and answer on this thread or kindly PM me the info i'm looking for.
thank you for your time.
UPDATE: i just flashed my optimus l7 with homero's v20a rooted rom and so far have had no problems. i'm keeping an average of 150 mb's of free ram at any given time, also still have my cpu clocked at 1.008 ghz all around. i was actually surprised with the flashing process, i meant to flash it through kdz and do a clean install (through emergency mode without the battery), and it successfully updated to homero's v20a and kept all my apps and data. still have over 1.9 gb's of interal storage left even after installing just about every rom manager i could find. very impressed. still looking for any custom roms that could further increase my performance (mainly the gpu)
Related
I have a rooted r800x phone with 2.3.3 running on it right now. The phone is cdma. I installed cwm on it via the xperia app from marketplace (locked bootloader still). My question is where csn i find compatible cfw for my phone and how do i go about installing it? also if there is anything else i need to know please feel free to mention. This is my first attempt at cfw on a phone. I really want to overclock the phone so any help is appreciated!
All firmware files can be found in the Dev section along with instructions (note the ones with CDMA in the titles).
http://forum.xda-developers.com/forumdisplay.php?f=1093
Unfortunately with a locked bootloader you limit yourself to only stock based ROMs, and it also rules out overclocking. The reason being is that for other firmwares (CM7, CM9, MIUI, etc) you need to flash a custom kernel (the kernels also what allows you to overclock along with some other low level tweaks) and you can't do that without unlocking your bootloader.
*EDIT* And since people keep telling you you need to flash a kernel to do anything, here's the first step:
http://forum.xda-developers.com/showthread.php?t=1322827
Read that, that's how you unlock your bootloader (it costs $24ish last I checked), you can't overclock without it, sorry, that's how it is, it's the only way. After that you still need to flash a kernel with fastboot, which is a process in itself. So read up, there be good information in these here threads.
ok so im not new to rooting or anything as my last phone was an ace (heaps of cool stuff for that phone)
i have my phone rooted now LG L5 E612 and have supeeruser installed last time i was here i seen that there was people saying no custom roms for this phone as bootloader is locked, now i return and i see a few for this phone just wondering how to install a rom and which one is the best one to use also ones that are eye candy or totally change the GUI
this rom is best in my view with no lags
hey i am using this cm 10.1 (4.2.2)rom since 1 year.its best in my view.it can be overclocked to 1Ghz.and ram can be increased by using ram expander.
chooky536 said:
ok so im not new to rooting or anything as my last phone was an ace (heaps of cool stuff for that phone)
i have my phone rooted now LG L5 E612 and have supeeruser installed last time i was here i seen that there was people saying no custom roms for this phone as bootloader is locked, now i return and i see a few for this phone just wondering how to install a rom and which one is the best one to use also ones that are eye candy or totally change the GUI
Click to expand...
Click to collapse
you need to unlock the bootloader and get a custom recovery, then you can easily install a custom rom
i am on cm11 beta 7.1, oc up to 1100mhz:laugh:
thanks guys i have looked around and all i can find is rooting tuts could anyone link me to a full tut from start to finish please?
ok so i tried several ways got cwm installed but phone keeps resetting
i used these ones
http://forum.xda-developers.com/showpost.php?p=38053729&postcount=1159
http://www.lg-phones.org/cwm-custom-recovery-for-lg-optimus-l5.html
http://www.lg-phones.org/unlock-bootloader-on-lg-optimus-l5-e610e612e615.html
still getting it resetting on me
also didnt back up my bootloader either.....................just tryed the e610 bootunlocker not resetting on me working ok now, now to find a tutorial to flash a rom
got it running the e610 cm10 working ok no reboots ect seems to be working ok now
I recently bought a used Lenovo A6000+. Using it for the first few hours did not reveal any major flaws. However, shortly afterwards I realized that the Phone used to switch off by itself when left unattended.
After verifying that my assumption is true, I proceeded to flashing the stock Lollipop ROM. I did so because I thought the problem was due to a flaw in the firmware. Plus, the 'About Phone' section in the Settings app showed clearly that my phone is a Lenovo A6000, with 8GB internal storage and 1GB RAM, while CPU-Z said that there is 16GB internal and 2GB of RAM, which tells that it is an A6000+.
The Lollipop ROM is worse than what I had anticipated. It lags like hell on the device, and is filled top to bottom with bloatware. Plus, the problem didn't get rectified even a bit. Worst, it started switching off even more regularly, and it wouldn't start unless I took out the battery and put it back in again.
If someone has devised a way of getting past this problem, be kind enough to mention it below.
@techfreak13, I don't know what's causing this issue but I can tell you that the stock Lollipop was a nightmare. Either you stay with stock KitKat or you can flash any of the other various ROMs available for this device. But, do note, that if you want to move from Lollipop (or Marshmallow or Nougat) based to KitKat based ROMs or vice versa, you'll first need to flash the stock ROM only. Then only you can flash the custom ROMs. Also different versions of TWRP are needed to work with the Kitakt and the other Lollipop/+ ROMs. TWRP 2.8.6 no image is for Kitkat while the latest verion 3.1.0 can be used for Lollipop+ Android versions. Since there is no unified thread for all the mods and roms. You'll have to dig deep into the forums to get the links. Good Luck to you. I hope you'll be able to solve the problem.
I've been running Cloudy G2.2 for a year an a half. It's given the phone enough legs to mostly make it through 2017. However, about every other week I have to restore my latest backup when Bluetooth stops working because it saw too many devices. This wouldn't be terrible if it wasn't for Authy refusing to sync my newer 2-Factor auth accounts. I think I've convinced myself that the G6 (US997) is my next phone, but now is a silly time to buy as the price should drop like a rock as the next wave of flagships come out.
I'm hoping to make it another couple months and was wondering anyone's experiences moving from Cloudy G2.2 (or other ROMs) to the latest lineage? From what I've read, it's very stable. However, I'm on Kit Kat bootloader, so it doesn't seem like this will be a straightforward process. I was hoping to get some experiences from people who made the same move before starting.
I currently have:
LG G2 D800
Root using stumproot (I think, it's been a while) with supersu installed
TWRP 2.7.0.0 installed by autorec
Cloudy G2.2 KOT49I
So, after some research, I set off to install LineageOS. In hindsight, this might have been a bad idea since it specifically only mentions the D802 in the title. However, it listed links for D800 builds, though they were crossed out.
I updated TWRP to this version by Blastagator and that was painless. I then wiped the phone, made a fresh backup and flashed the latest nightly of LineageOS, and the latest GApps (Mini) for 7.1. That was disappointing since I got the quick "LG logo" followed by a blank screen, that I later found was mentioned in the same Lineage post. Should've read farther.
I think the issue is that I'm on the wrong bootloader. I thought I was on KitKat which the post requires, but in order to enter recovery, I have to press enter three times (rather than using volume buttons to navigate), which indicates I'm on JellyBean bootloader.
So, this is the scary step that I was hoping to avoid. My big fear is that I run Linux on my desktop, so I can't use the LG Flash Tool. As long as I can keep a working recovery, I have backups, so I'm fairly safe. Following the Blastagator bootloader post, I'm not really sure how you go back and forth between bootloaders so easily as it suggests. Is that really as simple as loading the zip file on the phone and installing it in TWRP?
Is there a safer way to handle this?
From my experience, it is that easy. Simply install the zip file and you have loaded a new boot loader. Also, I was in the same boat as you with Cloudy rom and moved to Nougat with crDroid. However it's not stable and I am considering looking for something else more stable but fast like crDroid.
ernie young said:
I was in the same boat as you with Cloudy rom and moved to Nougat with crDroid
Click to expand...
Click to collapse
When you updated your bootloader, were you still able to run the Cloudy ROM before you switched to crDroid? Once I flash the KitKat bootloader, am I only able to use the Nougat ROMs? My big concern is that there might be something a bit off with my bootloader, so I won't be able to get back to TWRP.
I think there's something a bit off with my bootloader as is, because about a year ago I flashed back to stock Jellybean, and took all the OTA updates. However, when the phone tried to take the KitKat update, it softbricked, and could only be recovered using the LG Update Tool, which I don't have access to anymore. Because of this, I'm a little worried that just dropping on the Blastagator KitKat bootloader may have some atypical issues.
i m using it for a while. u know, on Los you won't be able to use lg features such as qslide, qmemo, plug&pop, knockcode etc. Only worth it if you want your phone to look a little bit fresher and lighter or you need a newer android version for some reason. Else, don't take the risk if you can't use flashtool. You can consider installing another kitkat rom. There are lots and they are nice :]
S YILDIRIM said:
or you need a newer android version for some reason.
Click to expand...
Click to collapse
My primary issue is that KitKat (or whatever Cloudy G2.2 is?) has the old Android bluetooth bug where once it sees too many devices, it stops connecting to anything. I have to make sure to turn off my phone if I go somewhere like an airport, and have been having to restore my clean Cloudy backup about once a month. It's getting pretty frustrating. On the other hand, I'm hoping to upgrade to an LG G6 (US997) in a month or two when the V30 release pushes down on prices. So, if it's a case of potentially hard-bricking my G2 at the worst possible time, I should hold off flashing.
I think you need hybrid bootstack for android 7.
WORF84 said:
I think you need hybrid bootstack for android 7.
Click to expand...
Click to collapse
That makes sense, but will I not be able to use my Cloudy 2.2 backup after that? It says that the hybrid bootstack will only boot CM 12.1, CM13, and LP stock roms.
superlou23 said:
That makes sense, but will I not be able to use my Cloudy 2.2 backup after that? It says that the hybrid bootstack will only boot CM 12.1, CM13, and LP stock roms.
Click to expand...
Click to collapse
These questions if this works with that or that are easier to answer for yourself by reading what goes with what.
Just Google LG G2 bootstack and you can probably find the ones you need for any available rom.
I use hybrid on Marshmallow 6.0.1 but I tried Nougat 7.1.2 too, it works.
I have moto g4 plus (2016) and want to install custom rom but I have some questions and without knowing about them i can't take the risk.so please answer sir.
1) There is 2 Twrp custom recovery one is 32 bit and second is 64 bit, so which is best ?
2) if I use 32 bit and flash 64 bit rom ,can it possible?
3) if No then if am use 64 bit Twrp and flash 32 bit rom accidentally ,can it will brick my device??
4) i am currently on stock rom android 7.0 , today most custom rom is based on 9.0 ,if I flash pie custom rom and after months i want revert back to stock or Oreo rom ,can i will do it? Because in some custom rom there is note that after flashing this rom you can not revert back lower version of rom.
5) where is rom take space if I flash it, means in ram ,internal storage???
Thanks in advance.i know this question is help for other noob:good:
keval3492 said:
I have moto g4 plus (2016) and want to install custom rom but I have some questions and without knowing about them i can't take the risk.so please answer sir.
1) There is 2 Twrp custom recovery one is 32 bit and second is 64 bit, so which is best ?
2) if I use 32 bit and flash 64 bit rom ,can it possible?
3) if No then if am use 64 bit Twrp and flash 32 bit rom accidentally ,can it will brick my device??
4) i am currently on stock rom android 7.0 , today most custom rom is based on 9.0 ,if I flash pie custom rom and after months i want revert back to stock or Oreo rom ,can i will do it? Because in some custom rom there is note that after flashing this rom you can not revert back lower version of rom.
5) where is rom take space if I flash it, means in ram ,internal storage???
Thanks in advance.i know this question is help for other noob:good:
Click to expand...
Click to collapse
64bit recoveries can handle 32bit roms too. Use a 64bit recovery and everything is fine.
You cannot downgrade your bootloader from stock Oreo to stock nougat(your current Rom). Custom roms won't flash bootloaders,only stock roms.
Your whole flash storage of your device is divided into several partitions like system, data, boot, recovery, internal storage. That's why you have to deal with less memory in your internal storage(10 out of 16 for example).
You cannot(yeah, but don't do it) modify the partition size cause it's used to met some requirements.
The rom will be flashed into system/data partition, not internal storage but also uses ram of course
Thanks man , but can you elaborate my question on if I flash today custom rom on pie base and that is rumor on moto g4 plus that oreo update will launch soon and I also wait for it.so can i get that update if I am on pie custom rom.sorry for your answer ,i not understand that .
keval3492 said:
Thanks man , but can you elaborate my question on if I flash today custom rom on pie base and that is rumor on moto g4 plus that oreo update will launch soon and I also wait for it.so can i get that update if I am on pie custom rom.sorry for your answer ,i not understand that .
Click to expand...
Click to collapse
Yes you can get official Oreo update if you are on Pie custom rom. You just need to go back to stock rom or flash the stock Oreo rom manually like the soak test.
Can you give me Twrp 64 bit link and also which custom rom do you prefer on gaming performance , battery performance and customisable wise? Thanks a lot...
keval3492 said:
Can you give me Twrp 64 bit link and also which custom rom do you prefer on gaming performance , battery performance and customisable wise? Thanks a lot...
Click to expand...
Click to collapse
Here's a link for the 64 bit TWRP https://forum.xda-developers.com/mo...recovery-twrp-3-2-1-unofficial-touch-t3722206 for flashing both 32 bit and 64 bit custom ROMs and TWRP flashables.
Of course, unlocking your bootloader and flashing a custom ROM via TWRP will unavoidably erase your device, so back up as necessary. Be also aware that flashing a custom ROM may necessitate flashing magisk as well, to get your device Google certified again.
As for a particular ROM, your best bet is to have a look at each custom ROM's page and particularly the first page and the last few pages. Both of those should give you information on how suitable the ROM is from other user's reports for your usage and also give you an idea how often the ROM is updated.
It is necessary for flashing magisk? Because magisk root my mobile and I don't want to do it right now.
keval3492 said:
It is necessary for flashing magisk? Because magisk root my mobile and I don't want to do it right now.
Click to expand...
Click to collapse
For some apps, like banking apps for example, these apps may not function properly if they detect an unlocked bootloader, or if your device does not pass Google Play Store certification. If you're wanting to flash a custom ROM or a TWRP flashable, then you may have to consider flashing magisk for magisk hide. Magisk hide helps to hide your unlocked bootloader status and thus may get your device certified to use these apps. Up to you - depends on if you use apps that won't work if they detect your device has an unlocked bootloader.
Thanks sir for get me guide .What is athens when I open xda moto g4 plus and what is kernel and how it is important ??
keval3492 said:
Thanks sir for get me guide .What is athens when I open xda moto g4 plus and what is kernel and how it is important ??
Click to expand...
Click to collapse
I'm guessing by Athens you mean athene? If so, athene is the device codename for the Moto G4/plus (2016). Custom ROMs and software designed for athene should work on our services, though please check the release dates of such software. That also means software built for another device codename may not work.
A kernel is part of the software communicating between the hardware and the software. Custom ROMs will come with one usually. If you choose to flash another kernel, ensure you flash the correct type of kernel - there are kernels for stock 7.0/6.0 (Motorola), 7.1 (custom) and kernels for custom 8.1/9.0 ROMs. These may not be cross compatible and as such if you flash the incorrect kernel to your device your device may fail to boot (buy then that's what TWRP backups are for). Due to the lack of source code for stock 8.1, I've not seen custom kernels built for the stock Motorola 8.1 stock ROM yet.
Thank you sir for guide me about athene and kernel ,so i choose custom rom only made for athene and kernel is also built in with custom rom.
I am on stock oreo on moto g4 plus ,it is same process in oreo for unlock bootloader??
keval3492 said:
I am on stock oreo on moto g4 plus ,it is same process in oreo for unlock bootloader??
Click to expand...
Click to collapse
Please search within the correct rom thread https://forum.xda-developers.com/mo...4-oreo-soak-test-update-t3871136/post78966322
I did not get proper answer from link you send ,please help for this..
keval3492 said:
I did not get proper answer from link you send ,please help for this..
Click to expand...
Click to collapse
Should be the same process to unlock your bootloader, provided your motherboard is the same and you've still got your IMEI and software channel.
Can you elaborate what you said about motherboard and IMEI ,i am getting that method is same as nought but after that line i don't understand.
keval3492 said:
Can you elaborate what you said about motherboard and IMEI ,i am getting that method is same as nought but after that line i don't understand.
Click to expand...
Click to collapse
When you unlock your bootloader, you need the unlock key. The unlock key is likely generated from and linked to your motherboard; if your motherboard had been changed, then you'd have to get a new unlock key.
If your IMEI is still present in your device and working, the unlock key should work. Some users with existing IMEI issues may not be able to unlock their bootloaders.
Basically, if your device is the same when you requested the unlock key, and everything is working okay, then unlocking should be the same as Nougat without any further steps. Back up, boot to fastboot and connect your device to your computer, then enter the unlock key command - with your key - on your computer in the minimal ADB terminal.
I changed my motherboard once and after that I unlock my bootloader also ,but I brick my device by installing 64 bit rom on 32 bit twrp version and after that I lock my bootloader and start as a fresh device till now.
Same key is still working for me as I want unlock my bootloader??
keval3492 said:
I changed my motherboard once and after that I unlock my bootloader also ,but I brick my device by installing 64 bit rom on 32 bit twrp version and after that I lock my bootloader and start as a fresh device till now.
Same key is still working for me as I want unlock my bootloader??
Click to expand...
Click to collapse
Should be - use the same key as you used to unlock your bootloader before (after you had your motherboard changed). Be aware you will not be able to re-lock your bootloader if you unlock your bootloader at the moment. We do not have the Oreo firmware to lock stock Oreo devices or devices previously updated to stock Oreo firmware.
Oreo firmware means coding in CMD ??