Related
Hi, I seem to have a few problems rooting my Lg optimus L5. I am on android version 4.1.2
I have tried the Framaroot method, as suggested in this tread. The app opens and I select the Gandalf exploit, as suggested by the maker of this app, but after I select my exploit, the app just closes.
I have also tried the method on this tread but after I open root.bat, it runs a few lines, says there are errors with a few ones and closes itself. I have tried this method 2 or 3 times
I think I tried another method, but I can't seem to find it, I'll post here if I eventually do find it.
Edit: I found the other method(all I had to do was look at my desktop, there was still a folder with the name of the method there... silly me!)
The other method is Super One Click, and that didn't work either...
Also, can someone explain to me what does V20D mean? Is it a rom, a kernel version?
P.S.: Please forgive me for beeing such a noob, but I really did search through the forums (maybe not well enough...) and didnt find any method that works
Sadly, there is only 1 method available to get lg l5 4.1.2 rooted.
Install a pre-rooted firmware (and, that's what v20a or b or d is) using kdz.
akshay95 said:
Sadly, there is only 1 method available to get lg l5 4.1.2 rooted.
Install a pre-rooted firmware (and, that's what v20a or b or d is) using kdz.
Click to expand...
Click to collapse
Thank you for the answer, could you link me to a guide? Also, will this"wipe" all my apps and their data?
4.1.2 pre-rooted. Flash any one using kdz updater.
http://forum.xda-developers.com/showthread.php?t=2275969
1. Install supersu.
2. Install ROM manager, select e610 as your device and flash cwm (or twrp) recovery.
Here's a guide to do the same. (use the rom from the first link, since the link to the rom is broken in the second link)
http://forum.xda-developers.com/showthread.php?t=2230679
IMPORTANT : If your phone is e612, download the recovery.img (for clockworkmod) of e610 only. Otherwise, you will get bootloops.
Yes, it will delete all your applications and data. It will delete all the contents of your internal sd card.
akshay95 said:
4.1.2 pre-rooted. Flash any one using kdz updater.
http://forum.xda-developers.com/showthread.php?t=2275969
1. Install supersu.
2. Install ROM manager, select e610 as your device and flash cwm (or twrp) recovery.
Here's a guide to do the same. (use the rom from the first link, since the link to the rom is broken in the second link)
http://forum.xda-developers.com/showthread.php?t=2230679
IMPORTANT : If your phone is e612, download the recovery.img (for clockworkmod) of e610 only. Otherwise, you will get bootloops.
Yes, it will delete all your applications and data. It will delete all the contents of your internal sd card.
Click to expand...
Click to collapse
God dammit, my phone wont enter emergency mode!
Thanks, my phone is now rooted! Funny fact: My data was not wiped, I still have all my apps, and I have checked with root checker if I have root , and I have, so thank you :good:
Wut?
Using kdz update tool, wipes all data...
How did yours not get wiped?
I guess, flashing a v20 on another v20 doesn't wipe the phone
Hey everybody! I'm new into this community and I've gotta say it was great to find a place like this, let me explain my situation:
So, I have the LG L5 E610 which came with the ICS as default, I decided to install Jelly Bean 4.1.2 on it and I've been using it for about 4 months now, no problems at all, but then I heared about Cyanogenmod which I've got really interested with (it's supposed to be faster and run fluider?).
So I have followed some tutorials and I've tried a bunch of different CM versions but I can't seem to get pass trough the part when I'm using KDZ Updater, as it pops up the following error:
Error: Wparam 100
----------------------------
Error: Lparam 1002
Any idea about how to fix this? and also as your personal opinion, should I change from my current Jelly Bean 4.1.2 to Cyanogenmod?
By the way, I'm from Spain and I'm using Orange, if you're aware about any compatibility errors with that company, tell me about them please.
Thanks in advice !
Sherbox said:
Hey everybody! I'm new into this community and I've gotta say it was great to find a place like this, let me explain my situation:
So, I have the LG L5 E610 which came with the ICS as default, I decided to install Jelly Bean 4.1.2 on it and I've been using it for about 4 months now, no problems at all, but then I heared about Cyanogenmod which I've got really interested with (it's supposed to be faster and run fluider?).
So I have followed some tutorials and I've tried a bunch of different CM versions but I can't seem to get pass trough the part when I'm using KDZ Updater, as it pops up the following error:
Error: Wparam 100
----------------------------
Error: Lparam 1002
Any idea about how to fix this? and also as your personal opinion, should I change from my current Jelly Bean 4.1.2 to Cyanogenmod?
By the way, I'm from Spain and I'm using Orange, if you're aware about any compatibility errors with that company, tell me about them please.
Thanks in advice !
Click to expand...
Click to collapse
First of all, is your phone rooted?Because the error you are showing has to do with KDZ updater.Also do you have CWM recovery installed?
Try this guide: http://forum.xda-developers.com/showthread.php?t=2405357
and then get into CWM recovery to flash the rom you want!
is not about root, i had it not rooted when i flashed kdz ICS on my phone. i was e610v and changed to e610 , because i couldn`t root the e610v
so it might be another problem
Sherbox said:
So I have followed some tutorials and I've tried a bunch of different CM versions but I can't seem to get pass trough the part when I'm using KDZ Updater, as it pops up the following error:
Error: Wparam 100
----------------------------
Error: Lparam 1002
Click to expand...
Click to collapse
He says he's trying to flash CM rom but stuck with KDZ updater.
What does KDZ updater has to do with CM roms?CWM recovery doesn't work?
Amathagma said:
He says he's trying to flash CM rom but stuck with KDZ updater.
What does KDZ updater has to do with CM roms?CWM recovery doesn't work?
Click to expand...
Click to collapse
Yep! I already have the phone rooted, and I also tried downloading ROM Manager and using CWM, but everytime I choose it to reboot in recovery mode, it just gets stuck in the LG logo and I have to extract the battery and restart it again and once I do this, my contacts, apps, etc. are deleted and it shows up the initial android options to set up everything (language and all those things).
Amathagma said:
First of all, is your phone rooted?Because the error you are showing has to do with KDZ updater.Also do you have CWM recovery installed?
Try this guide: http://forum.xda-developers.com/showthread.php?t=2405357
and then get into CWM recovery to flash the rom you want!
Click to expand...
Click to collapse
Thank you very much (and all the users who also helped me), the tutorial worked! Cyanogenmod 10.1 is now installed in my LG L5 E610!! :victory: :victory: :victory:
Just one more question! if I want to try some other ROM's, shall I follow the same tutorial?
Sherbox said:
Thank you very much (and all the users who also helped me), the tutorial worked! Cyanogenmod 10.1 is now installed in my LG L5 E610!! :victory: :victory: :victory:
Just one more question! if I want to try some other ROM's, shall I follow the same tutorial?
Click to expand...
Click to collapse
CWM- wipe data, cache, dalvik cache, flash the ROM
I tried updating the bootstack on my LG G2 since it was having WiFi disconnect issues. After updating it with the Lollipop bootstack on a Lollipop ROM (Dirty Unicorns 5.1.1) I couldn't use the camera and flash light.
I then decided to just flash the stock LG G2 Lollipop KDZ and start afresh.
However, my phone became bricked into fastboot mode but I got out of it by flashing all the img files through fastboot. Now it is getting stuck at the LG logo and I can't enter fastboot or recovery now... I can access download mode but it says it's still rooted and when I go to flash a new KDZ (tried multiple versions) it says phone disconnected, or force closes the support tool.
I've been in this situation before but I can't remember how I got out of it...
I'm running Windows 8.1 and have read that you can't flash KDZ through the support tool on Windows 8/8.1 so I'm in the process of installing a Windows 7 virtual machine.
reeper250 said:
I tried updating the bootstack on my LG G2 since it was having WiFi disconnect issues. After updating it with the Lollipop bootstack on a Lollipop ROM (Dirty Unicorns 5.1.1) I couldn't use the camera and flash light.
I then decided to just flash the stock LG G2 Lollipop KDZ and start afresh.
However, my phone became bricked into fastboot mode but I got out of it by flashing all the img files through fastboot. Now it is getting stuck at the LG logo and I can't enter fastboot or recovery now... I can access download mode but it says it's still rooted and when I go to flash a new KDZ (tried multiple versions) it says phone disconnected, or force closes the support tool.
I've been in this situation before but I can't remember how I got out of it...
I'm running Windows 8.1 and have read that you can't flash KDZ through the support tool on Windows 8/8.1 so I'm in the process of installing a Windows 7 virtual machine.
Click to expand...
Click to collapse
Oh my god.. What happend to you g2 ?
First, don't give up, sooner or later you are gonna unbrick your G2 in the end. I have been there too.
If you can get into download mode, you are very lucky.
Just Ignore root thing, it has nothing to do with flashing KDZ/TOT.
You got to learn how to use LG flashtool first.
http://forum.xda-developers.com/showthread.php?t=2432476
My suggestion is that just stick to TOT tool instead of KDZ tool. Sometimes KDZ tool fails during flashing without proper reason.
And that problem often happens when you are going back to stock rom from CM12.1 roms like DU, BlissPop...
But one thing to remember, TOT tool would wipe out your internal memory.
Unplugging you external SD memory is recommended while doing KDZ/TOT flashing.
If you still fail with TOT tool.... It's no good. You may have to try short-circuit method.
Good luck.
ailing said:
Oh my god.. What happend to you g2 ?
First, don't give up, sooner or later you are gonna unbrick your G2 in the end. I have been there too.
If you can get into download mode, you are very lucky.
Just Ignore root thing, it has nothing to do with flashing KDZ/TOT.
You got to learn how to use LG flashtool first.
http://forum.xda-developers.com/showthread.php?t=2432476
My suggestion is that just stick to TOT tool instead of KDZ tool. Sometimes KDZ tool fails during flashing without proper reason.
And that problem often happens when you are going back to stock rom from CM12.1 roms like DU, BlissPop...
But one thing to remember, TOT tool would wipe out your internal memory.
Unplugging you external SD memory is recommended while doing KDZ/TOT flashing.
If you still fail with TOT tool.... It's no good. You may have to try short-circuit method.
Good luck.
Click to expand...
Click to collapse
Failed everything except TOT. The TOT took about 6-8 hours to download...
Flashed TOT and it booted fine, then updated to stock Lollipop with KDZ. It's currently working EXCEPT....
Camera doesn't work still, can't send a text because the "Messaging" app force closes, don't have the flash light, and I can't seem to start ABD to root it.
SD Card is working fine though. Using a 64GB formatted to FAT32 and restored all my pictures, music, etc.
The main thing is the camera and messaging app, plus the flash light is really handy when working on my car.
At least I have a working phone
Managed to get it recognised in device manager and ADB but when rooting it stops at 45%...
reeper250 said:
Managed to get it recognised in device manager and ADB but when rooting it stops at 45%...
Click to expand...
Click to collapse
Oh... I think there's possibility your camera hardware has gone out of order.
When you are in LG stock rom, and still experience problem... well I guess it's not software problem.
Because TOT flashing is complete software factory reset. It revert everything to out of factory state.
And for rooting, sometimes it just get stuck. but suddenly it just get rooted. I can't explain the reason.
But you should remember one thing in mind, don't initialize V3. It's anti virus program, and it blocks rooting.
When you boot for the first time, you maybe was asked if you agree with V3 software, just choose don't agree and skip it.
If you still fail rooting, just flash KDZ/TOT again to go back to KitKat. When you're done with flashing KDZ/TOT, just stay there and don't update KK version because KK update could block rooting.
Of course you should not agree with V3 software install.
Use towel root, it's the most easiest way. go to towelroot.com and download apk. (click logo)
Root your G2 and use KitKat version of autorec to install TWRP.
ailing said:
Oh... I think there's possibility your camera hardware has gone out of order.
When you are in LG stock rom, and still experience problem... well I guess it's not software problem.
Because TOT flashing is complete software factory reset. It revert everything to out of factory state.
And for rooting, sometimes it just get stuck. but suddenly it just get rooted. I can't explain the reason.
But you should remember one thing in mind, don't initialize V3. It's anti virus program, and it blocks rooting.
When you boot for the first time, you maybe was asked if you agree with V3 software, just choose don't agree and skip it.
If you still fail rooting, just flash KDZ/TOT again to go back to KitKat. When you're done with flashing KDZ/TOT, just stay there and don't update KK version because KK update could block rooting.
Of course you should not agree with V3 software install.
Use towel root, it's the most easiest way. go to towelroot.com and download apk. (click logo)
Root your G2 and use KitKat version of autorec to install TWRP.
Click to expand...
Click to collapse
Got root eventually. Not sure why but it worked after like the 6th time...
Is it the bootstack or something that's causing the camera and flash to stop working?
It only started having those issues when I installed the new bootstack.
I'm about to throw this stupid phone against the wall...
I cleared Cache and Dalvik Cache after successfully installing TWRP and it came up with "Security Error" and I can't boot
reeper250 said:
I'm about to throw this stupid phone against the wall...
I cleared Cache and Dalvik Cache after successfully installing TWRP and it came up with "Security Error" and I can't boot
Click to expand...
Click to collapse
I can guarantee TOT flashing would revert everything to factory default state. So Even if bootstack has caused problem, after flashing TOT, everything should be back to normal. Because TOT flashing includes bootstack.
Tot flashing completely wipe out your G2 and rewrite EVERYTHING.
I am 100 percent sure that camera's malfunction has nothing to do with bootstack.
BTW, which version of autorec did you use ? There are two versions of autorec. You should not be mistaken.
Because KitKat autorec would destroy Lollipop's kernel and cause security error.
To my knowledge, XDA forum has only KK version which made by cloudyfa.
Even if you had security error, It's too early to give up.
First, Power off, and holding vol.up and connect USB. If you are lucky again, you would see download mode.
Or try to get into recovery by pressing vol.up and power.
At worst case, you can't get into recovery nor download mode, either.
But That doesn't mean you should throw out g2. You can still revive G2.
Recently I made how to revive bricked G2 (only F320 specific) in Korean. It's already known method.
You have to open back cover and disassemble to try short-circuit.
If you really want to try short-circuit method, I would make short translated version for you.
G2 is really hard to brick. So don't throw up until G2 is real dead.
Good luck
ailing said:
I can guarantee TOT flashing would revert everything to factory default state. So Even if bootstack has caused problem, after flashing TOT, everything should be back to normal. Because TOT flashing includes bootstack.
Tot flashing completely wipe out your G2 and rewrite EVERYTHING.
I am 100 percent sure that camera's malfunction has nothing to do with bootstack.
BTW, which version of autorec did you use ? There are two versions of autorec. You should not be mistaken.
Because KitKat autorec would destroy Lollipop's kernel and cause security error.
To my knowledge, XDA forum has only KK version which made by cloudyfa.
Even if you had security error, It's too early to give up.
First, Power off, and holding vol.up and connect USB. If you are lucky again, you would see download mode.
Or try to get into recovery by pressing vol.up and power.
At worst case, you can't get into recovery nor download mode, either.
But That doesn't mean you should throw out g2. You can still revive G2.
Recently I made how to revive bricked G2 (only F320 specific) in Korean. It's already known method.
You have to open back cover and disassemble to try short-circuit.
If you really want to try short-circuit method, I would make short translated version for you.
G2 is really hard to brick. So don't throw up until G2 is real dead.
Good luck
Click to expand...
Click to collapse
I probably installed the wrong AutoRec then...
Flashed the KDZ again and booted but it's saying "System UI has stopped", com.android.phone has stopped", etc.
I guess I have to TOT flash again and start over... again...
reeper250 said:
I probably installed the wrong AutoRec then...
Flashed the KDZ again and booted but it's saying "System UI has stopped", com.android.phone has stopped", etc.
I guess I have to TOT flash again and start over... again...
Click to expand...
Click to collapse
In normal case, after flashing TOT, there should not be any problem at all. Because It's in factory default condition. I mean, it's like the first time you open up the package right after you buy.
As for your case, I think something is seriously wrong.
Make sure you flashed right TOT matched to your F320. As you already know, there are 3 variants, F320S, F320K, F320L.
Ah.. I almost forgot. If you want to try aosp roms other than LG stock rom, you can try when you are in KitKat, too. While you are in KK, don't update KK version. Because updated KK version blocks rooting.
Right after flashing KK tot/kdz, try towel root. It's the easiest rooting tool.
You can download it at towelroot.com
After rooting, install supersu and use KK autorec (which made by cloudyfa) to install TWRP.
But In my opinion you should figure out why stock rom has system UI crash.
In authorized LG service center, engineer uses the same TOT tool. In theory you can't have any problem after flashing TOT. unless there are some damaged hardware.
This is all I can help. Hope you solve the problem.
ailing said:
In normal case, after flashing TOT, there should not be any problem at all. Because It's in factory default condition. I mean, it's like the first time you open up the package right after you buy.
As for your case, I think something is seriously wrong.
Make sure you flashed right TOT matched to your F320. As you already know, there are 3 variants, F320S, F320K, F320L.
Ah.. I almost forgot. If you want to try aosp roms other than LG stock rom, you can try when you are in KitKat, too. While you are in KK, don't update KK version. Because updated KK version blocks rooting.
Right after flashing KK tot/kdz, try towel root. It's the easiest rooting tool.
You can download it at towelroot.com
After rooting, install supersu and use KK autorec (which made by cloudyfa) to install TWRP.
But In my opinion you should figure out why stock rom has system UI crash.
In authorized LG service center, engineer uses the same TOT tool. In theory you can't have any problem after flashing TOT. unless there are some damaged hardware.
This is all I can help. Hope you solve the problem.
Click to expand...
Click to collapse
TOT is for my F320S, just flashed it again and it worked.
Installed AutoRec LP and it worked. Ended up installing Dirty Unicorns 5.1.1 which worked.
Camera and flash still don't work.
I remember this happened to me ages ago but I can't remember how I fixed it
ailing said:
In normal case, after flashing TOT, there should not be any problem at all. Because It's in factory default condition. I mean, it's like the first time you open up the package right after you buy.
As for your case, I think something is seriously wrong.
Make sure you flashed right TOT matched to your F320. As you already know, there are 3 variants, F320S, F320K, F320L.
Ah.. I almost forgot. If you want to try aosp roms other than LG stock rom, you can try when you are in KitKat, too. While you are in KK, don't update KK version. Because updated KK version blocks rooting.
Right after flashing KK tot/kdz, try towel root. It's the easiest rooting tool.
You can download it at towelroot.com
After rooting, install supersu and use KK autorec (which made by cloudyfa) to install TWRP.
But In my opinion you should figure out why stock rom has system UI crash.
In authorized LG service center, engineer uses the same TOT tool. In theory you can't have any problem after flashing TOT. unless there are some damaged hardware.
This is all I can help. Hope you solve the problem.
Click to expand...
Click to collapse
Hello it is easy to provide me links to f320s .tot and .dll ?
LG g2 d802 not accepting fastboot commands
reeper250 said:
I tried updating the bootstack on my LG G2 since it was having WiFi disconnect issues. After updating it with the Lollipop bootstack on a Lollipop ROM (Dirty Unicorns 5.1.1) I couldn't use the camera and flash light.
I then decided to just flash the stock LG G2 Lollipop KDZ and start afresh.
However, my phone became bricked into fastboot mode but I got out of it by flashing all the img files through fastboot. Now it is getting stuck at the LG logo and I can't enter fastboot or recovery now... I can access download mode but it says it's still rooted and when I go to flash a new KDZ (tried multiple versions) it says phone disconnected, or force closes the support tool.
I've been in this situation before but I can't remember how I got out of it...
I'm running Windows 8.1 and have read that you can't flash KDZ through the support tool on Windows 8/8.1 so I'm in the process of installing a Windows 7 virtual machine.
Click to expand...
Click to collapse
if anyone can help me. I dont know if it'is a hard brick or not, but i can go to the fastboot mode only. when i try to erase some partitions tho i get this error FAILED (remote: failed to erase partition) and my phone says Failure sending erase group start command to the card(RD;2).
I've tried to flash files too but nothing seems to work since everything leads me to an error and the phone says this when i try to flash it :Failure sending write group start command to the card(RD;2).
if anyone is able to help me, i would very much appriciate
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?
guys I have a question
what is the simple solution if my phone doesnt recognise my sim card
im using Korean version F320S and Im not in korea
once I faced this problem
some people took my phone and Flashed variety of stock roms
finally my phone recognises Sim card but I cant use 3G network
before I tried to flash LP roms I was able to use 3g
jordan0111 said:
Yeah I know but I'm sorry
The reason why I wrote to this thread is I'm looking forward to flashing this this rom to get over my problem
Click to expand...
Click to collapse
Since the condition of your phone is unknown:
- go back to stock KK firmware - kdz
http://forum.xda-developers.com/showthread.php?t=2432476
- root and install TWRP recovery - AutoRec
http://forum.xda-developers.com/showthread.php?t=2715496
(update recovery to blastagator's TWRP 2.8.7.3, if you want
http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705
Don't flash latest 3.0.0.1, Aroma Installer not working properly)
- follow installation instructions - CloudyG2
http://forum.xda-developers.com/showthread.php?t=2783192
Just read carefully the corresponding threads and instructions.
Val D. said:
Since the condition of your phone is unknown:
- go back to stock KK firmware - kdz
http://forum.xda-developers.com/showthread.php?t=2432476
- root and install TWRP recovery - AutoRec
http://forum.xda-developers.com/showthread.php?t=2715496
(update recovery to blastagator's TWRP 2.8.7.3, if you want
http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705
Don't flash latest 3.0.0.1, Aroma Installer not working properly)
- follow installation instructions - CloudyG2
http://forum.xda-developers.com/showthread.php?t=2783192
Just read carefully the corresponding threads and instructions.
Click to expand...
Click to collapse
ThanksThanks I'll try