Database Users

[Q] Soft Brick help me please!!!

PLEASE READ EVERYTHING FOR BETTER UNDERSTANDING
Hey fellow LG Owner(s) I am writing this asking for some help. I know that majority of LG Phones use the same software and flashing tools regarding taking your phone back to stock. I currently own an LG G Flex (LS995 Sprint Variant) and I managed to soft brick my phone. I have posted this same message over at the LG G Flex Threads but so far I have gotten no one to provide me some sort of solution on how to un-brick or factory reset my phone.
The status of my phone before it got bricked was it had Root (IOROOT method), Busy-Box (by Jrummy), Build.Prop was edited to display as a Nexus 5, and boot-loader locked along with no custom recovery. If you’re wondering why my boot-loader was locked and why there wasn’t any type of custom recovery was due to the sad fact that Developers are having a hard time on cracking it.
Now to explain on how I soft bricked my phone. I was changing my font style by using a tool called ROM Toolbox (by Jrummy). I managed to change my font once and I attempted to change it a second time, since I was looking for something that displayed it wider and bolder. So as I applied install on the new font I got an automatic reboot.
The reboot consisted of the normal LG Logo display, followed by a black screen and staying as a black screen. On the upper left of my phone the notification indicator was flashing multiple colors (red, white, blue etc). This is the current state of my phone, black screen with a multicolor notification.
My attempts to fix:
- Simple reboot of the phone ((fail))
- Let the phones battery drain out then charge for a few minutes and restart ((fail))
- Managed to get into STOCK recovery and perform clean partition ((fail)
- Managed to get into STOCK recovery and apply factory reset ((fail))
- I got into some weird mode which also gave me the option to apply factory reset ((fail))
- I followed this tutorial (LG Flash Tool) on how to revert back to stock (by hyelton) ((fail))
Link to tutorial: http://forum.xda-developers.com/showthread.php?t=2644083
The tutorial by hyelton was almost successful to reverting back to stock firmware until I got to the last step (Number 6). The error that occurred by using the LG Flash Tool was when the tool attempted to flash the stock firmware it gave me a Download FAIL!! “Device Model is different“ notification (Images below). I did this tutorial at least seven times and I got no luck. Every single time that I attempted to do this I kept getting the same notification. I have now ran out if ideas on what to do.
My theory, I believe that by changing my build prop to display as a nexus 5 is the reason why I keep getting this fail notification. On the phone it-self when I put it into download mode it even displays as a Nexus 5 (Images below).
I was wondering since it’s possible to get into STOCK RECOVERY, I saw that it had an option for “ADB SIDELOAD” is it possible to push something thru ADB??? Any type of help is greatly appreciated and thanked. Please do not get upset that you see this in multiple LG threads, I am just trying to find a solution to UNBRICK this very expensive phone that I bought and I cannot afford to just use it as a paper weight. THANK YOU AND GOD BLESS
Here is a Link to all my files regarding STOCK tot,dll,lg flash tools,aboot, buildprop, lg usb drivers and adb drivers that are for my phone
Link: https://drive.google.com/folderview?id=0B1D8UNLjuTB6TWpCQ1pJME5qWk0&usp=sharing
i hope these files help anyone that are attempting to help me put my phone back to stock
Alright yall, I am almost official screwed. I purchased this phone about a month ago from Best Buy and they stated that I am out of there 15 day window so I cannot exchange or replace for the same phone. I then went to Sprint on whom I have phone insurance for and they stated that they cannot do anything and that I have to go to one of their Sprint repair stores. I went to one of the repair stores and the gentlemen that assisted me plugged my phone to his computer and immediately knew that my phone was rooted. So from there I played the dumb blonde card acting like I don’t know what he’s talking about and from there he directed me to call LG and see what they can do. So now the current status is I filed a repair request and now I am awaiting a reply from LG. Does anyone have any suggestion???
**SOLUTION** hey yall i got the solution to my problem and it was simply by downloading this universal custom .dll from
http://forum.xda-developers.com/show....php?t=2663369
and i managed to flash back to stock recovery using this guide. instead using the dll on the the guide i used the custom one.
*GUIDE BACK TO STOCK*
http://forum.xda-developers.com/show....php?t=2644083

BUMP

well not sure about g flex but for my g2 I had same problem when flashing back to stock it kept saying wrong firmware finally I found I downloaded an updated firmware and so did not match error, try downloading and flashing the firmware the phone came with but not updated, in my case my phone came with d80010d and I was trying to flash updated d80010o, downloaded d80010d and all went fine, not sure if it's the same for you I too changed my phone model in build.prop and my phone went into fastboot mode on restart. Hope it saves u too.
Sent from my LG-D800 using xda app-developers app

can you link me to where I can find the dll you are using?

XxZombiePikachu said:
can you link me to where I can find the dll you are using?
Click to expand...
Click to collapse
its the second oneeeeeeee
http://storagecow.eu/index.php?dir=Xda/LG+G+Flex/Stock/Sprint+LS995/

lingarajug said:
well not sure about g flex but for my g2 I had same problem when flashing back to stock it kept saying wrong firmware finally I found I downloaded an updated firmware and so did not match error, try downloading and flashing the firmware the phone came with but not updated, in my case my phone came with d80010d and I was trying to flash updated d80010o, downloaded d80010d and all went fine, not sure if it's the same for you I too changed my phone model in build.prop and my phone went into fastboot mode on restart. Hope it saves u too.
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
thanks for your response but unfortunately there is only one firmware for the sprint flex at the current moment.

christiam.coronado said:
its the second oneeeeeeee
http://storagecow.eu/index.php?dir=Xda/LG+G+Flex/Stock/Sprint+LS995/
Click to expand...
Click to collapse
ok then try this modified dll hopefully it will work https://www.dropbox.com/s/akcn2b3skv9h4pa/LGLS995_20140116_LGFLASHv151.dll
please do so at your own risk

XxZombiePikachu said:
ok then try this modified dll hopefully it will work https://www.dropbox.com/s/akcn2b3skv9h4pa/LGLS995_20140116_LGFLASHv151.dll
please do so at your own risk
Click to expand...
Click to collapse
same results "device model is different" didnt work. Im willing to try anything. please shoot me some more of your modifications

christiam.coronado said:
same results "device model is different" didnt work. Im willing to try anything. please shoot me some more of your modifications
Click to expand...
Click to collapse
ill see what else I can try I am basically just trying to find out which are all the parts of the dll that check the device which is kind of difficult especially since yours is no longer a part of the g family ill keep looking when I finish the next one I'll let you know

XxZombiePikachu said:
ill see what else I can try I am basically just trying to find out which are all the parts of the dll that check the device which is kind of difficult especially since yours is no longer a part of the g family ill keep looking when I finish the next one I'll let you know
Click to expand...
Click to collapse
wow thanks i greatly appreciate your help. i am open to trial and error and whatever you can think of i will try.

christiam.coronado said:
wow thanks i greatly appreciate your help. i am open to trial and error and whatever you can think of i will try.
Click to expand...
Click to collapse
what did you add to your build prop to make it think it was a nexus 5?

XxZombiePikachu said:
what did you add to your build prop to make it think it was a nexus 5?
Click to expand...
Click to collapse
all that i did to the build prop was change the model to Nexus 5. luckily i have copied my original build prop to my computer. here is the ling to my google drive which i have saved my original build prop
https://drive.google.com/file/d/0B1D8UNLjuTB6UVBGZnhIaWEwNjg/edit?usp=sharing

XxZombiePikachu said:
what did you add to your build prop to make it think it was a nexus 5?
Click to expand...
Click to collapse
attached below is an image of what my original build prop looked like with its original model as ro.product.model = LG-LS995
the LG-LS995 was the part that i replaced with Nexus 5

Why not try to restore your default build prop
Sent from my LT25i using xda app-developers app

harrymason37 said:
Why not try to restore your default build prop
Sent from my LT25i using xda app-developers app
Click to expand...
Click to collapse
how remember that my bootloader is still locked and this model does not have a custom recovery. but i am able to access the stock recovery with an option to ADB SIDELOAD. I got word from a DEV stating that:
"Factory recovery won't let you adb sideload a package without a LG verified updater script so it won't work." (by XDA justinswidebody)
but if he is incorrect i wouldn't mind attempting trial and error. what do you think???

okay so I tried a different approach I grabbed a d820(nexus 5 model) dll and replaced everything inside with info from the ls995 dll hopefully this works heres the link https://www.dropbox.com/s/kh9ns4gzw3i4gq3/d820_ls995.dll

XxZombiePikachu said:
okay so I tried a different approach I grabbed a d820(nexus 5 model) dll and replaced everything inside with info from the ls995 dll hopefully this works heres the link https://www.dropbox.com/s/kh9ns4gzw3i4gq3/d820_ls995.dll
Click to expand...
Click to collapse
ok ill try it out give me a minute

XxZombiePikachu said:
okay so I tried a different approach I grabbed a d820(nexus 5 model) dll and replaced everything inside with info from the ls995 dll hopefully this works heres the link https://www.dropbox.com/s/kh9ns4gzw3i4gq3/d820_ls995.dll
Click to expand...
Click to collapse
no didnt load onto the lgflashtool. these are the notification that i got, images are below
-Failed to load factory s/w
-Failed PreviousLoad ()

christiam.coronado said:
no didnt load onto the lgflashtool. these are the notification that i got, images are below
-Failed to load factory s/w
-Failed PreviousLoad ()
Click to expand...
Click to collapse
what's the version of your flash tool
edit: after some reading to flash nexus tots you need lg flash tool 1.8
re-edit: I believe that the dll needs to be modified so that it accepts the device as a nexus 5 but once it's done flashing it needs to make the device and ls995 again, but for now it's 1am and I need to be up early later so I'll work on something later, also just some extra information on ther stuff: as for flashing the build prop if you can manage to make it into a flashable update.zip(which also places it in corresponding directory) which is also signed and you can sideload it should flash or just give an error, and another thing that could work with above method is flashing a corrupted kernel which will throw your phone into fastboot mode and with correct files and commands you can repartition the entire device to stock(this one is very dangerous/risky would not recommend it)

XxZombiePikachu said:
what's the version of your flash tool
Click to expand...
Click to collapse
Setup_LGFlashTool_1.6.01.0529
its on my drive should i downgrade??? https://drive.google.com/file/d/0B1D8UNLjuTB6ekthOGRVMWE3ejA/edit?usp=sharing

Warning to any custom rom makers, Don't edit the model number

So it doesn't happen again like with the G2, if your making a custom rom. Please don't edit the model field in the build.prop. Why? Well if you change it from say F400L to F400 My cool rom mod v2. This phone will not be able to restore itself to an official rom using the KDZ flasher. So you can't flash tot flies or use the LG Mobile support recovery. You have quite an issue getting this phone back to stock. A big nightmare.
This happened to my G2 where I flashed a custom rom and then it boot looped. But because the flasher could not read the model it would not let me restore my phone. I hope this doesn't happen to people on the G3. :good:
So rom modders, please keep the build.prop model line free of edits

Hendrickson said:
So it doesn't happen again like with the G2, if your making a custom rom. Please don't edit the model field in the build.prop. Why? Well if you change it from say F400L to F400 My cool rom mod v2. This phone will not be able to restore itself to an official rom using the KDZ flasher. So you can't flash tot flies or use the LG Mobile support recovery. You have quite an issue getting this phone back to stock. A big nightmare.
This happened to my G2 where I flashed a custom rom and then it boot looped. But because the flasher could not read the model it would not let me restore my phone. I hope this doesn't happen to people on the G3. :good:
So rom modders, please keep the build.prop model line free of edits
Click to expand...
Click to collapse
Sorry but I disagree with you. I had an f400l and editing buildi prop I was abile to change firmware, reflashing it more than one time using tot and dll files

Hendrickson said:
So it doesn't happen again like with the G2, if your making a custom rom. Please don't edit the model field in the build.prop. Why? Well if you change it from say F400L to F400 My cool rom mod v2. This phone will not be able to restore itself to an official rom using the KDZ flasher. So you can't flash tot flies or use the LG Mobile support recovery. You have quite an issue getting this phone back to stock. A big nightmare.
This happened to my G2 where I flashed a custom rom and then it boot looped. But because the flasher could not read the model it would not let me restore my phone. I hope this doesn't happen to people on the G3. :good:
So rom modders, please keep the build.prop model line free of edits
Click to expand...
Click to collapse
I also agree with lukemo. I have reflashed my F400S at least 4 times now (and edited build.prop in 3 of em). Maybe elaborate on your description a little more. If a device is capable of connecting to a PC through USB Debugging, then pulling the build.prop and editing it for the purposes of (re)flashing should not be an issue. Also, it definitely does not hurt to keep a copy of it on hand as a spare (if push comes to shove and TOT, DLL combo is the only way to restore).

Ok maybe its not the case on the F400 now but myself and a few others ran into a big issue with this on the Korea G2 F320. Flashing one of the first roms a F320 CN V1 rom it did some build.prop edits and if you bricked it. It was a mission to get the phone back. A brick meaning boot loop and no other modes apart from download mode. KDZ did not let us flash it as it wanted that model in the edit.
It was all caused by edits to
ro.build.model
ro.build.version.incremental
ro.build.id
Might have messed with the boot.img, but i'm sure they didn't in the beginning.

Can somebody tell me what all needs to be edited in my build.prop to get it back to my original firmware, here is the summary of my case
I have F400K model, flashed VT V6 which changed my model to F400L, applied ART and it gave my android.system.com errors on boot, has do flash F400L stock TOT as F400K tot gave an error, I am now on F400L with VT V6 and want to go back to my 400K firmware.
Thanks in advance,

Bad luck since I saw this now, after I edited the build prop to make the LG G3 think it was an GTI9500 for the Samsung Gear 2 pairing, since I did it in the M8 i thought I could get away with it. Now the phone boots, LG logo comes on, then the screen goes dark fray and the notification light switches from color to color. Nothing happens, it seems as its booting but it never goes through. So I cannot TOT or similar since the phone does not boot up.
Can anyone advice? Is Odin an option? I am on D855 custom rom

Did you try flashing GTI9500 firmware? My 400k didn't take its tot as I was switched to 400k, I had to eventually flash 400l to boot it properly
Sent from my LG-F400L using Tapatalk

Diamond777 said:
Bad luck since I saw this now, after I edited the build prop to make the LG G3 think it was an GTI9500 for the Samsung Gear 2 pairing, since I did it in the M8 i thought I could get away with it. Now the phone boots, LG logo comes on, then the screen goes dark fray and the notification light switches from color to color. Nothing happens, it seems as its booting but it never goes through. So I cannot TOT or similar since the phone does not boot up.
Can anyone advice? Is Odin an option? I am on D855 custom rom
Click to expand...
Click to collapse
Edit the tot with a hex editor to match your build prob do it in lunix also make sure you have the dll that does with your phone.

D-FUSE said:
Edit the tot with a hex editor to match your build prob do it in lunix also make sure you have the dll that does with your phone.
Click to expand...
Click to collapse
Hi all thanks for the help.
As of now, the phone won't boot at all, its in a boot loop after the logo splash screen. So no MTP or CMD detection available to flash anything as of now. If I could access the build prop I can modify to leave it like it was, but its not seeming possible?

Diamond777 said:
Hi all thanks for the help.
As of now, the phone won't boot at all, its in a boot loop after the logo splash screen. So no MTP or CMD detection available to flash anything as of now. If I could access the build prop I can modify to leave it like it was, but its not seeming possible?
Click to expand...
Click to collapse
Open the tot file with a hex editor in ubuntu then do a search for your model number the 1st line will be it. Change that to what ever you changed the build.prob too then going to download mode and use flash tool like you would normally. I've done this 100 time on my g flex. It works man.

Hi
D-FUSE said:
Open the tot file with a hex editor in ubuntu then do a search for your model number the 1st line will be it. Change that to what ever you changed the build.prob too then going to download mode and use flash tool like you would normally. I've done this 100 time on my g flex. It works man.
Click to expand...
Click to collapse
I have the same problem and this HEX editor idea sounds good, I only have a PC so how to I get ubuntu?? and what hex editor would i use?

aviduser said:
I have the same problem and this HEX editor idea sounds good, I only have a PC so how to I get ubuntu?? and what hex editor would i use?
Click to expand...
Click to collapse
You're gonna have to Google ubuntu and install it along side windows and then get an hex editor in the software center

ok done that
D-FUSE said:
You're gonna have to Google ubuntu and install it along side windows and then get an hex editor in the software center
Click to expand...
Click to collapse
Have ubuntu now loaded on a usb. Can open the tot with hex editor but where do I search for my product model. When I search d800 I get a thousand results. I then click on one and I can see garbled text in the right hand display box of the hex editor.
Which hex editor do you use?is that important?
And what settings perhaps am I missing. Not used any of this before but ubuntu seems straight forward
Many thanks
Chris

Diamond777 said:
Hi all thanks for the help.
As of now, the phone won't boot at all, its in a boot loop after the logo splash screen. So no MTP or CMD detection available to flash anything as of now. If I could access the build prop I can modify to leave it like it was, but its not seeming possible?
Click to expand...
Click to collapse
Can u use adb? If the answer is yes i can show u how to restore build.prop...

Skin1980 said:
Can u use adb? If the answer is yes i can show u how to restore build.prop...
Click to expand...
Click to collapse
Hi, I can't do sh**!
I am stuck in bootloop, I cannot adb because it does not get detected???
This is stressful, thanks for your help

Diamond777 said:
Hi, I can't do sh**!
I am stuck in bootloop, I cannot adb because it does not get detected???
This is stressful, thanks for your help
Click to expand...
Click to collapse
What version of g3 have u got?
If someone can give me the original build.prop for your version i will make a flashable zip that u can flash in stock recovery

Skin1980 said:
What version of g3 have u got?
If someone can give me the original build.prop for your version i will make a flashable zip that u can flash in stock recovery
Click to expand...
Click to collapse
That would be like so awesome bro thanks. I am on d855 European version
Sent from my HTC One_M8 using XDA Premium 4 mobile app

Diamond777 said:
That would be like so awesome bro thanks. I am on d855 European version
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
give me 1 hour...

Diamond777 said:
That would be like so awesome bro thanks. I am on d855 European version
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
here u go... u have to:
1- go in recovery;
2- select update from adb;
3- from the pc
Code:
adb sideload restore-signed.zip
4- reboot
This will copy the original build.prop to ur device... if this not help write me pls.. we can find other way

A live cd/dvd of ubuntu or any linux distro should work too. Good hex editors to use are bless and 010.
010 runs on windows/linux/osx. You can try editing on windows, but I suggest only doing so if your pc is a good one.
And on the subject of the OP, one really shouldn't be editing the device model, build #, nor versioning of the rom.

[GUIDE] How to install Emotion AOSP on T-Mobile N910T/N910T3

[GUIDE] How to install Emotion AOSP on T-Mobile N910T/N910T3
I know a lot of you wanted to try Emotion AOSP on our T-Mobile Note 4, but it is not supported currently.
I have been able to flash it successfully to my N910T3 and having no issues what so ever, all works.
Here are the instructions:
1) Download the ROM from here:
http://forum.xda-developers.com/note-4/snapdragon-dev/rom-aokp-emotroid-team-t3317486
2) Download the gaps from OpenGaps, I prefer pico version.
3) Now you need to open the zip file using 7-Zip and extract following file:
META-INF\com\google\android\update-script
4) Edit the file in any Text Editor and remove the 1st line starting with keyword "assert", if you don't remove this line then you won't be able to flash it your N910T/N910T3.
5) Put the modified update-script back in the zip file using 7-zip.
6) To get the Data/Wifi working you need to download the data fix for N910T from below link:
http://forum.xda-developers.com/note-4/snapdragon-dev/marshmallow-6-0-1-ports-data-fixes-t3379978
7) Now this ROM will be ready to flash via recovery as usual like any other ROM.
8) Copy all 3 files to your phone internal/external memory.
9) Flash in below order:
Emotion-trltexx-MM.r21.Official-20160916-200804.zip
open_gapps-arm-6.0-pico-*.zip
LouForgiveNo_N910T_MM_Data_Fix.zip
ROM will take about 10-15 minutes to boot. Then you should be able to setup the phone as per your requirements.
Don't forget to thank @Pafcholini and @louforgiveno for their work.

I couldn't get it to work. Got an error message in TWRP.

Aivo7192 said:
I couldn't get it to work. Got an error message in TWRP.
Click to expand...
Click to collapse
That means you missed Step 3-4, it won't work without modifying the update-script file.

pvsgh said:
That means you missed Step 3-4, it won't work without modifying the update-script file.
Click to expand...
Click to collapse
Steps 3-4 did confuse me a bit. I did it a few times still no luck.

Once you have the ROM zip file ready, verify the update-script file again, it should NOT contain below line:
assert(getprop("ro.product.device") == "trltexx" || getprop("ro.build.product") == "trltexx" || getprop("ro.product.device") == "trltedt" || getprop("ro.build.product") == "trltedt" || abort("This package is for device: trltexx,trltedt; this device is " + getprop("ro.product.device") + ".");
This line check if you have one of those Note 4 variant.

Or you can do what i did...
Or you can replace all references to other devices with the T-Mobile name. For some reason kept getting code 6 when I removed the line, but when I replaced all the references to other devices worked like a charm. This method still requires you to extract, edit and compress again through 7-Zip.

pvsgh said:
[GUIDE] How to install Emotion AOSP on T-Mobile N910T/N910T3
I know a lot of you wanted to try Emotion AOSP on our T-Mobile Note 4, but it is not supported currently.
I have been able to flash it successfully to my N910T3 and having no issues what so ever, all works.
Here are the instructions:
1) Download the ROM from here:
http://forum.xda-developers.com/note-4/snapdragon-dev/rom-aokp-emotroid-team-t3317486
2) Download the gaps from OpenGaps, I prefer pico version.
3) Now you need to open the zip file using 7-Zip and extract following file:
META-INF\com\google\android\update-script
4) Edit the file in any Text Editor and remove the 1st line starting with keyword "assert", if you don't remove this line then you won't be able to flash it your N910T/N910T3.
5) Put the modified update-script back in the zip file using 7-zip.
6) To get the Data/Wifi working you need to download the data fix for N910T from below link:
http://forum.xda-developers.com/note-4/snapdragon-dev/marshmallow-6-0-1-ports-data-fixes-t3379978
7) Now this ROM will be ready to flash via recovery as usual like any other ROM.
8) Copy all 3 files to your phone internal/external memory.
9) Flash in below order:
Emotion-trltexx-MM.r21.Official-20160916-200804.zip
open_gapps-arm-6.0-pico-*.zip
LouForgiveNo_N910T_MM_Data_Fix.zip
ROM will take about 10-15 minutes to boot. Then you should be able to setup the phone as per your requirements.
Don't forget to thank @Pafcholini and @louforgiveno for their work.
Click to expand...
Click to collapse
pvsgh, everything works except for phone, am unable to make or receive calls. Any idea what the problem could be? Had to go back to 5.1.1 to get phone to work, a shame as everything else worked perfectly.

pvsgh said:
That means you missed Step 3-4, it won't work without modifying the update-script file.
Click to expand...
Click to collapse
After changing assert line ...I can flash but the ROM never goes beyond boot animation. Waited more than 20 minutes .I dint flash datafix...was planning to do that If rom boots

Manan79 said:
After changing assert line ...I can flash but the ROM never goes beyond boot animation. Waited more than 20 minutes .I dint flash datafix...was planning to do that If rom boots
Click to expand...
Click to collapse
vanemburghj said:
pvsgh, everything works except for phone, am unable to make or receive calls. Any idea what the problem could be? Had to go back to 5.1.1 to get phone to work, a shame as everything else worked perfectly.
Click to expand...
Click to collapse
What model you guys are using? and what is the version of your bootloader? I have the latest EPG2.

pvsgh said:
What model you guys are using? and what is the version of your bootloader? I have the latest EPG2.
Click to expand...
Click to collapse
Same... 910t on epg2...

Manan79 said:
Same... 910t on epg2...
Click to expand...
Click to collapse
Did you install at least the gapps package? That is a required install. I would suggest you to install all 3 files mentioned in OP.

pvsgh said:
Did you install at least the gapps package? That is a required install. I would suggest you to install all 3 files mentioned in OP.
Click to expand...
Click to collapse
Will do...and update you

vanemburghj said:
pvsgh, everything works except for phone, am unable to make or receive calls. Any idea what the problem could be? Had to go back to 5.1.1 to get phone to work, a shame as everything else worked perfectly.
Click to expand...
Click to collapse
I tested the phone call immediately after install and it worked for me without issues. So in your case only phone call is not working, what about data and wifi?

pvsgh said:
I tested the phone call immediately after install and it worked for me without issues. So in your case only phone call is not working, what about data and wifi?
Click to expand...
Click to collapse
ok , so for me , it did boot after following the exact 3 steps...i m testing the rom now , will report if any issues.. thanks for the OP
1. only H+ instead of LTE i get
2. camera does not work , just shows blank screen
I am gonna go back to norma note 7 port... however, very nice that i can load the rom and test it. thx again

pvsgh said:
I tested the phone call immediately after install and it worked for me without issues. So in your case only phone call is not working, what about data and wifi?
Click to expand...
Click to collapse
phone calling not working for me. It shows dialing but nothing happen.

pvsgh said:
What model you guys are using? and what is the version of your bootloader? I have the latest EPG2.
Click to expand...
Click to collapse
SM-N910T and bootloader is EPE3.
---------- Post added at 05:44 PM ---------- Previous post was at 05:40 PM ----------
pvsgh said:
I tested the phone call immediately after install and it worked for me without issues. So in your case only phone call is not working, what about data and wifi?
Click to expand...
Click to collapse
Data and wifi work, which is why I did not realize I had problems with the phone. Started receiving voice mails, thought I had the volume down and that wasn't it. Tried calling the house and it just said dialing for 5 minutes. Again, a shame as I liked the ROM, but need the phone to work.

I didn't have to do anything but flash in TWRP. I'm on epg2

Poll - Is root working for you? (T-Mobile Variant ONLY)

I want to take a poll, and this will be for T-Mobile variants ONLY. Being that the thread has people from all different carriers posting results, i think it's rather confusing to anyone reading along trying to decide whether or not to give it a shot.
So, have you successfully rooted/TWRP'd your TMOBILE variant LGv20?

thatisandwas said:
I want to take a poll, and this will be for T-Mobile variants ONLY. Being that the thread has people from all different carriers posting results, i think it's rather confusing to anyone reading along trying to decide whether or not to give it a shot.
So, have you successfully rooted/TWRP'd your TMOBILE variant LGv20?
Click to expand...
Click to collapse
Yes I have. Full root access with working TWRP and supersu. No issues as of yet but I've not tried anything other than TB.

I got it rooted with twrp be warned though my other lg I flashed a file and now bootloop

bambam126 said:
I got it rooted with twrp be warned though my other lg I flashed a file and now bootloop
Click to expand...
Click to collapse
what file?

czerdrill said:
what file?
Click to expand...
Click to collapse
Build prop edit and google assistant..: /

bambam126 said:
Build prop edit and google assistant..: /
Click to expand...
Click to collapse
Ah ok, i thought i saw someone say earlier the google assistant thing worked for them, but they might have manually edited the build prop.

czerdrill said:
Ah ok, i thought i saw someone say earlier the google assistant thing worked for them, but they might have manually edited the build prop.
Click to expand...
Click to collapse
Yeah maybe I'm trying to get out this loop

bambam126 said:
Yeah maybe I'm trying to get out this loop
Click to expand...
Click to collapse
You're not going to get out of it without restoring your backup or manually placing the normal build prop inside recovery

jthrasher47 said:
You're not going to get out of it without restoring your backup or manually placing the normal build prop inside recovery
Click to expand...
Click to collapse
I can't restore I did a factory wipe and didnt work I'm on lg support tool but upgrade recovery says no items to fix and lgup sees phone as unknown but my non looping v20 it sees just fine
Idk what to do lg mobile support tool gives me up but says no items to fix

You did not do a backup in twrp before flashing your file? You may have to exchange your phone you should always make a backup especially with things this new

Unlocked and rooted with no problems. I flashed a systemless hosts file for ad away in twrp and everything was fine. For assistant, I manually edited the build.prop file and restarted, which worked great. I almost feel guilty as to how easy this whole process has been.

jthrasher47 said:
You did not do a backup in twrp before flashing your file? You may have to exchange your phone you should always make a backup especially with things this new
Click to expand...
Click to collapse
what can i do with that backup I cant get into twrp...

Full root,twrp,l speed... Loving it
Sent from my LG-H918 using XDA-Developers mobile app

kibmikey1 said:
Unlocked and rooted with no problems. I flashed a systemless hosts file for ad away in twrp and everything was fine. For assistant, I manually edited the build.prop file and restarted, which worked great. I almost feel guilty as to how easy this whole process has been.
Click to expand...
Click to collapse
LOL wanna make a video? I'm gonna do it tonight, i am just nervous.

AT&T Tried Yet ?

bambam126 said:
I can't restore I did a factory wipe and didnt work I'm on lg support tool but upgrade recovery says no items to fix and lgup sees phone as unknown but my non looping v20 it sees just fine
Idk what to do lg mobile support tool gives me up but says no items to fix
Click to expand...
Click to collapse
I assume the build prop edit changes the device name. Therefore lg up won't recognize it. You will need a custom .dl file with the name edited. At least that is what used to happen back in the day when I was working with these phones. There used to be a program that made it possible to edit the .dl file.

justinswidebody said:
I assume the build prop edit changes the device name. Therefore lg up won't recognize it. You will need a custom .dl file with the name edited. At least that is what used to happen back in the day when I was working with these phones. There used to be a program that made it possible to edit the .dl file.
Click to expand...
Click to collapse
LG sees it as the v20 but can't do anything cause no software updates or whatever

bambam126 said:
LG sees it as the v20 but can't do anything cause no software updates or whatever
Click to expand...
Click to collapse
Have you tried to fast boot flash the stock system img
---------- Post added at 05:36 PM ---------- Previous post was at 05:33 PM ----------
bambam126 said:
LG sees it as the v20 but can't do anything cause no software updates or whatever
Click to expand...
Click to collapse
If that doesn't work, you should be able to put the system IMG on SD card and DD command it

justinswidebody said:
Have you tried to fast boot flash the stock system img
Click to expand...
Click to collapse
What's the command I tried something it says remote command failed or something

bambam126 said:
What's the command I tried something it says remote command failed or something
Click to expand...
Click to collapse
When in fast boot type fastboot flash system then drag the image in the command prompt

delete this thread

Please delete this thread.

Instead of working on your own, I suggest to help our main devs. @BadDaemon and @crpalmer.

I don't see anyone else working on 8.0.0 for this phone lol. Or if they are, they're doing it incognito.
If I have to work alone, I can make progress on my own. I'm helping to give people a base to go off of.

Check this out in lineage thread.
https://forum.xda-developers.com/ho...-1-pre-official-kiw-l24-t3528488/post73885702

dave71670 said:
Check this out in lineage thread.
https://forum.xda-developers.com/ho...-1-pre-official-kiw-l24-t3528488/post73885702
Click to expand...
Click to collapse
I've seen his work and looked into it before posting this. There were a quite a few mistakes in some of the files so I didn't touch them. And I don't see any reference to any of their work on xda. They may be working towards something completely different that is just lineage based. Until I can speak with them myself to verify the purpose, I would rather not use their project.

Travisholt92 said:
I don't see anyone else working on 8.0.0 for this phone lol. Or if they are, they're doing it incognito.
If I have to work alone, I can make progress on my own. I'm helping to give people a base to go off of.
Click to expand...
Click to collapse
I actually know one person working incognito mode. He'll only release it when he's ready. If you want to talk to him, drop by my inbox.

Lineage 15
look, https://androidfilehost.com/?fid=962021903579482541

ljukigrobar said:
look, https://androidfilehost.com/?fid=962021903579482541
Click to expand...
Click to collapse
You tested this?

ljukigrobar said:
look, https://androidfilehost.com/?fid=962021903579482541
Click to expand...
Click to collapse
error 7 for me, will try again

itisiryan said:
You tested this?
Click to expand...
Click to collapse
I've just tried to install it on kiw-l21 and twrp gives me error 7, it can't find device model (twrp returns . for some reason).

culler said:
I've just tried to install it on kiw-l21 and twrp gives me error 7, it can't find device model (twrp returns . for some reason).
Click to expand...
Click to collapse
Well that's a bit expected since it's not released yet publicly.

itisiryan said:
Well that's a bit expected since it's not released yet publicly.
Click to expand...
Click to collapse
I've figured, but also, I tried to do dirty flash over xenonhd so that was the reason probably
Anyway, by removing asserts from updater script, installed in twrp and got stuck on honor logo.

culler said:
I've figured, but also, I tried to do dirty flash over xenonhd so that was the reason probably
Anyway, by removing asserts from updater script, installed in twrp and got stuck on honor logo.
Click to expand...
Click to collapse
We're seeing some movements, we may get O in 3 months.

Because it builds as lineage-kiwi twrp has to be updated to support it

Does this error 7 mean it will not install using twrp or other recoveries as well? Has anyone gotten this to install?

boxlink said:
Does this error 7 mean it will not install using twrp or other recoveries as well? Has anyone gotten this to install?
Click to expand...
Click to collapse
Error 7 comes from assert in update script. Just remove it for flash.
Chinnu:
Try to remove the first line starting with assert and then flash it.
Do this.
Extract zip . Goto META-INF/com/google/Android/undater-script. Remove the first line in updater script and save the file. Repack the zip and flash
Remove this line
assert(getprop("ro.product.device") == "kiwi" || getprop("ro.build.product") == "kiwi" || abort("E3004: This package is for device: kiwi; this device is " + getprop("ro.product.device") + ".");

rodolphe06 said:
Error 7 comes from assert in update script. Just remove it for flash.
Chinnu:
Try to remove the first line starting with assert and then flash it.
Do this.
Extract zip . Goto META-INF/com/google/Android/undater-script. Remove the first line in updater script and save the file. Repack the zip and flash
Remove this line
assert(getprop("ro.product.device") == "kiwi" || getprop("ro.build.product") == "kiwi" || abort("E3004: This package is for device: kiwi; this device is " + getprop("ro.product.device") + ".");
Click to expand...
Click to collapse
Have you done this with success? @culler mentions getting stuck on the honor logo even with removing asserts. I currently am on stock 6.0 so I wouldn't be installing over a custom rom.

boxlink said:
Have you done this with success? @culler mentions getting stuck on the honor logo even with removing asserts. I currently am on stock 6.0 so I wouldn't be installing over a custom rom.
Click to expand...
Click to collapse
No this is just to bypass twrp flash error.
ROM bootloop

Travisholt92 said:
Because it builds as lineage-kiwi twrp has to be updated to support it
Click to expand...
Click to collapse
So our main TWRP has to be updated too?

itisiryan said:
So our main TWRP has to be updated too?
Click to expand...
Click to collapse
It was needed updated on every other device I've seen 8.0.0 on. Removing lines from an update script tells it to skip a step that is probably needed. And to wonder why it bootloops lol. Don't try flashing files that you know nothing about, that is how phones get bricked or bootloader viruses.