Related
On my phone, can not boot into recovery mode. No matter how many times I try to use the home and power button. I even went to youtube to watch a video on it to make sure I was doing it right.
I have installed clockwork recovery via fastboot many many times, using different versions. I also have tried it with different roms installed.
I wonder if it is because the first rom I installed was superfast froyo, which says recovery is not working. I also installed swiftdroid 2.0, which also wouldn't let me use recovery. Though I forgot to try to reboot into recovery from the android menu when I had swiftdroid installed.
It's not a big deal anymore, since I accomplished what I wanted. I installed Froyo Optimum V3 with data2system via fastboot, and it worked fine. I now have 245mb on the phone so it is all good. When I installed it I just installed boot.img, cache.img, and system.img each to their respective partition, and data.img to userdata partition. So far, everything works fine.
However, it does bother me a little that recovery isn't currently working, I'm sure I'll find the answer sooner or later. Anyone have any ideas?
Hello as I can see you recently uppdated from stock 2.1? Then something went wrong and you used a rom that does not support recovery. Please tell what .kdz you flashed
EDIT: http://forum.xda-developers.com/showpost.php?p=13205397&postcount=26
lavero.burgos said:
Hello as I can see you recently uppdated from stock 2.1? Then something went wrong and you used a rom that does not support recovery. Please tell what .kdz you flashed
EDIT: http://forum.xda-developers.com/showpost.php?p=13205397&postcount=26
Click to expand...
Click to collapse
All Fastboot ROMs support recovery regardless of their version.
Try this:
Go into fastboot and open a Command Prompt and type:
Code:
cd <location of SDK Tools>
fastboot erase recovery
fastboot flash recovery nameofrecoveryimage.img
fastboot reboot
This fixed my problem I had when I first flashed fastboot onto my GT540, don't know if it will work for you or not, but its worth a try
Hope it helps,
Jack
Original poster here. Changed name for obvious reasons.
I think something did go wrong during the initial upgrade to 2.1. I forgot to mention a couple of things now that I think about it.
I used this link for most of my information:
http://forum.xda-developers.com/showthread.php?t=1032744
I first installed the european rom listed in that thread via KDZ. I never get an LG screen during boot up. I don't remember if the stock 1.6 had an LG screen or not. I think upgraded to what was then called "super fast froyo 2.2." I then wanted to install a rom with data2system, when was when I realized restore wasn't working. I then tried to downgrade back to the european rom via KDZ. It didn't work. Whenever I booted the phone, all I got was a black screen similar to the fast boot screen. I re-installed the european rom via KDZ, same results. Installed "swift droid 2.0" via fast boot, no recover. Then I installed I installed Froyo Optimum V3 with data2system, via fastboot, which is where I am now, still with no lg screen during boot-up.
Thanks you for your help, and i will try the link posted by JackG256 when I have time.
typci said:
Original poster here. Changed name for obvious reasons.
I think something did go wrong during the initial upgrade to 2.1. I forgot to mention a couple of things now that I think about it.
I used this link for most of my information:
http://forum.xda-developers.com/showthread.php?t=1032744
I first installed the european rom listed in that thread via KDZ. I never get an LG screen during boot up. I don't remember if the stock 1.6 had an LG screen or not. I think upgraded to what was then called "super fast froyo 2.2." I then wanted to install a rom with data2system, when was when I realized data to system wasn't working. I then tried to downgrade back to the european rom via KDZ. It didn't work. Whenever I booted the phone, all I got was a black screen similar to the fast boot screen. I re-installed the european rom via KDZ, same results. Installed "swift droid 2.0" via fast boot, no recover. Then I installed I installed Froyo Optimum V3 with data2system, via fastboot, which is where I am now, still with no lg screen during boot-up.
Thanks you for your help, and i will try the link posted by JackG256 when I have time.
Click to expand...
Click to collapse
Actually the link you see was the one posted by me lol i recently posted on my reference guide thread aboutcases when you brick your phone and possible fixes, there is one for your problem.
Also as i have read plenty about this kind of things i can assure that not all the kdz with fastboot support recovery that is a myth , there is a recovery_rom.kdz, there is out.kdz and other .kdz roms that has a purpose.
My theory is that not all the LG GT540 are the same thing, why? because simple if you read all the threads of users that have had issues with their phone saying this ROM worked for me and then another user saying that it didnt for him but other rom did the job. There are so many .kdz ROMS and even more are been released, but modified to support fastboot and recovery.
So if you do a bit more of research you can find original stock .kdz roms and their modified version requested by many users marginalized because of their location.
Hope you fix yor phone with the one posted in my thread, good luck! you will need it.
I think you are correct about not all gt540 are the same. I have an "international version." When I was installing drivers, it was a very complicated issue, and most of the drivers I found didn't work. I had to use the drivers supplied by LG via their lgmobile update program, to get my phone interact correctly with my computer. Luckily, I have alot of experience with flashing and custom roms for other electronic devices. So I know how to handle bad flashes, and other problems for the most part. Right now, my gt540 is fine, no recovery, but the custom rom is working just fine. Next time I want to swap out custom roms, probably when the android 3.3 builds become very stable, I'll play around with some KDZs and try to get recovery working.
Thanks for your help.
If you want to try with more kdz then you should try with one modified by mur4ik for data2system method.
Sent from my GT540 using XDA App
I got a bootloop after flashing a recovery, it would it bootloop at the and flash the recovery splash screen.
I can't boot into the phone
Which method do I use to switch recoveries?
This G2 is my pride and joy, and I am panicking quite a bit :/
I have additional info on the last post here V
http://forum.xda-developers.com/lg-...1-0-materialised-splash-t2926322#post56459568
To whoever finds me the solution, I will buy you a lunch!!
Hello. The only way of switching recoveries when you can't access your current custom recovery is by going back to stock using the "how to go back to stock" method that's stickied in the G2 General section.
Make sure you download the right firmware for your device, that you have the right drivers installed and that your phone (and computer is charged).
Everything else you might need can be found here: http://forum.xda-developers.com/showthread.php?t=2432476
LAF NUKER wipes your Download mode and let you use Fastboot instead.:
Do this on your own responsibility, if you bricked your phone in some weird way then don't look at me.
But with this simple thing you can't brick your phone only if you flashed the wrong zip which wasn't from me.
This is more meant for developers/testers.
Click to expand...
Click to collapse
I was getting irritated that my Fastboot mode dissapeared everytime when I flashed some lollipop stock based rom as those all included bootloader files, so I had to first attempt to get into the rom itself or recovery to wipe it again over and over. So I thought by myself why won't I make something easy and flashable?
This lightweight flashable zip from 2-4KB is tested by me multiple times so after you flashed it I HIGHLYsuggest that you need to test or you can enter download mode and see if it shows now fastboot. If so then everything succeeded like it should, it has an succes rate of 100% as nothing could actually go wrong with this.
This script/method should also work for the G3 and some other LG devices which have this partition:
Code:
/dev/block/platform/msm_sdcc.1/by-name/laf
For the one's who care the shell script is located in the update-binary, updater-script is just dummy.
If you want to revert back, just flash the jb/kk/lp bootloader files.
Download:
https://docs.google.com/uc?authuser=0&id=0B1u3mnq0nstfZVN1eVQ3bEw5ODQ&export=download
Mirror:
https://www.androidfilehost.com/?fid=23991606952610950
Credits:
Jackpotclavin for the method to get into fastboot mode
Chainfire for the shell updater-script method
osm0sis for the guide about the shell updater-script
wulsic said:
LAF NUKER wipes your Download mode and let you use Fastboot instead.:
I was getting irritated that my Fastboot mode disapeared everytime when I flashed some lollipop stock based rom as those all included bootloader files . . . .
Click to expand...
Click to collapse
My question is somewhat off-topic but I'm having a hard time understanding how bootloaders and ROMs work with the G3.
When I had a G2 I learned about the difference between Kitkat and Lollipop bootloaders the hard way when I tried to restore a Kitkat nandroid backup over stock lollipop and hard bricked the phone. My impression was that since the KK backup did not include a compatible bootloader I needed to flash one or restore to stock KK.
Now you are suggesting that ROMs for the G3 *include* bootloaders, which is news to me. Does this mean I can go back and forth between Kitkat and Lollipop ROMs without worrying about bootloaders? Or restore nandroid backups without the same concern? I don't want to have to downgrade to Kitkat every time I want to try a new ROM or restore a backup.
Thanks.
No most roms don't include bootloaders but some stock roms do, especially in the g2 community as I made this first for G2 but I also found out that it would also work on the G3. I guess g3 is the same as the G2 in terms of flashing. Lollipop stock roms need lollipop bootloader related files to properly boot but the bootloader is from kitkat with the g3 because else bump and flashing doesnt work. Only on the g3 tmobile version as that version has an unlocked bootloader. Just read the op's from the threads good and you will know what you need to flash here in the g3 community. But download mode might not always properly work as solution I have this laf nuker so you can flash the good kernel and or recovery if you softbricked your phone. If you hardbrick your G3 you can still fix it as far as I know so don't worry.
wulsic said:
. . . Only on the g3 tmobile version as that version has an unlocked bootloader. Just read the op's from the threads good and you will know what you need to flash here in the g3 community. But download mode might not always properly work as solution I have this laf nuker so you can flash the good kernel and or recovery if you softbricked your phone. If you hardbrick your G3 you can still fix it as far as I know so don't worry.
Click to expand...
Click to collapse
I have the T-Mobile version of the G3. How does that make things different?
It cost me $45 to fix a hard brick on a G2 which I later found out was still under financing with T-Mobile so I returned it. It was an expensive little device.
channeledbymodem said:
I have the T-Mobile version of the G3. How does that make things different?
It cost me $45 to fix a hard brick on a G2 which I later found out was still under financing with T-Mobile so I returned it. It was an expensive little device.
Click to expand...
Click to collapse
Well as far as I know the t mobile version has an unlocked bootloader so more freedom for flashers. I also hard bricked my G2 but before I hard bricked it there was a shortening method guide on how to hard unbrick your g2. Could also work on the g3 perhaps. Well that sucks that you needed to pay $45 lets just hope for you that it won't happen again.
If you want 100% clarification about the bootloader and different roms then you might want to ask it in the Q&A or a rom thread as I am a G2 user. But short story as far as I know. Lollipop bootloader related files for lollipop stock roms. And kitkat bootloader related files for custom aosp roms like euphoria cyanogenmod etc.
I don't know if the guy I paid (who fixed it the day he got it so it couldn't have been so hard for him) had to open it to short the pins but after watching a video showing it done I wasn't going to chance it. It was like repairing a watch. Plus I tried the sw method of viewing the borked partitions in Linux and then replacing them but I couldn't see them to replace so I paid for the repair. And I only had the damn phone for a month before I discovered the problem with T-Mobile and sent it back.
I must say the G2 was a *very* finicky device compared to the Optimus G Pro I had before. And that phone never worked properly with any AOSP ROM. I don't know why I'm so loyal to LG. Must be because the phones are cheaper and I really don't like Samsung any more.
Of course the Verizon Motorola Droid Ultra I bought for my wife used is even worse. It's completely locked down. You can't root Lollipop on it and you can't downgrade to Kitkat once you've taken the OTA update.
Until somebody can explain switching ROMs on the G3 to me like I'm five I think I'm just going to always go back to stock Kitkat, re-root and re-install TWRP. Seems the safest thing to do.
I found a used LG G4 that was locked to Koodo for a friend of mine. I researched to make sure that it supports the AWS 1700/2100 band since my friend is on Eastlink (similar to Freedom Mobile). At first everything worked fine, but now he is getting intermittent disconnections from the network where it says "no service." I had him choose the option without LTE, and at first he got service again, but then he didn't get mobile data, and the connection randomly dropped anyway (for calls and texts).
I had him open the service menu via *#*#4636#*#* to turn off the radio, but as soon as he goes to "Phone Information," he gets the message "This application does not work on this device." So Koodo blocked the menu. Wonderful.
At this point, I'm really not sure what to do. Has anyone had similar issues? I've rooted and installed custom ROMs on my own phones several times before. Would installing a custom ROM help? Or maybe just flashing another modem file?
If anyone could help, it would be greatly appreciated. I was trying to help my friend save some money. His old phone was 8 years old and was a cheapo that was laggy from the start. I recommended a "higher end" used phone rather than another cheapo. He's running a business and has 9 kids, so... I would really like to get this working for him.
Edit:
Problem is solved. My friend is no longer experiencing intermittent "no service'" or anything. Here is what I did:
1. Followed these instructions to unlock the bootloader.
2. Flash stock Nougat zip (instructions also say "After that and while still in TWRP: Choose Reboot -> RECOVERY ! This should ensure TWRP will not be overwritten on Android boot")
3. Flash Nougat modem zip
4. Flash my model's baseband (again; was already done during bootloader unlock)
I realize now that I might have not needed to unlock bootloader at all, and could have used LG Up (new) to flash a kdz. But oh well, it's all done, and now my friend has Nougat (the Canadian variant abandoned updates before Nougat).
threehappypenguins said:
I found a used LG G4 that was locked to Koodo for a friend of mine. I researched to make sure that it supports the AWS 1700/2100 band since my friend is on Eastlink (similar to Freedom Mobile). At first everything worked fine, but now he is getting intermittent disconnections from the network where it says "no service." I had him choose the option without LTE, and at first he got service again, but then he didn't get mobile data, and the connection randomly dropped anyway (for calls and texts).
I had him open the service menu via *#*#4636#*#* to turn off the radio, but as soon as he goes to "Phone Information," he gets the message "This application does not work on this device." So Koodo blocked the menu. Wonderful.
At this point, I'm really not sure what to do. Has anyone had similar issues? I've rooted and installed custom ROMs on my own phones several times before. Would installing a custom ROM help? Or maybe just flashing another modem file?
If anyone could help, it would be greatly appreciated. I was trying to help my friend save some money. His old phone was 8 years old and was a cheapo that was laggy from the start. I recommended a "higher end" used phone rather than another cheapo. He's running a business and has 9 kids, so... I would really like to get this working for him.
Click to expand...
Click to collapse
Assuming he's carrier unlocked, if he's using an old sim card from a previous carrier, he should purchase a new sim card from his current carrier.
If he hasn't already tried this, suggest he do a network reset: Settings > Backup & reset > Network settings reset.
If no go, his alternatives are to (assuming he's not bootloader unlocked): try a factory reset; next, re-flash his appropriate kdz in LGUP-NEW. He should backup his userdata first.
If bootloader unlocked (UsU) he could re-flash his modem.bin or modem.img file from a SALT extract of his appropriate kdz.
sdembiske said:
Assuming he's carrier unlocked, if he's using an old sim card from a previous carrier, he should purchase a new sim card from his current carrier.
If he hasn't already tried this, suggest he do a network reset: Settings > Backup & reset > Network settings reset.
If no go, his alternatives are to (assuming he's not bootloader unlocked): try a factory reset; next, re-flash his appropriate kdz in LGUP-NEW. He should backup his userdata first.
If bootloader unlocked (UsU) he could re-flash his modem.bin or modem.img file from a SALT extract of his appropriate kdz.
Click to expand...
Click to collapse
I've already done a factory reset of the phone. Is a network reset necessary, or would the factory reset cover that? His bootloader is not unlocked... yet. I will attempt re-flashing his kdz and/or just the modem if the network reset at this point is unnecessary. I'm looking at lg-firmwares.com and don't see Koodo on that list (the phone was originally put out by Koodo), so I assume Telus (Koodo's parent network) would be a safe one to use (MM)?
I found a bigger list here. I found the link in this guide.
threehappypenguins said:
I've already done a factory reset of the phone. Is a network reset necessary, or would the factory reset cover that? His bootloader is not unlocked... yet. I will attempt re-flashing his kdz and/or just the modem if the network reset at this point is unnecessary. I'm looking at lg-firmwares.com and don't see Koodo on that list (the phone was originally put out by Koodo), so I assume Telus (Koodo's parent network) would be a safe one to use (MM)?
Click to expand...
Click to collapse
Network reset is your first & best option. Re-flashing the kdz is your last option.
Use this site for the kdz download and scroll down to and use this Telus kdz ( H81220z_00_0327.kdz: it does work on Koodo as well): https://lg-firmwares.com/lg-h812-firmwares/firmwares/
Refer to this link for flashing with LGUP-NEW: https://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
As a 'Senior Member" you should know that it is an XDA courtesy to use the Thanks button - you should have learned to use it by now - bottom right of the post
sdembiske said:
Assuming he's carrier unlocked, if he's using an old sim card from a previous carrier, he should purchase a new sim card from his current carrier.
If he hasn't already tried this, suggest he do a network reset: Settings > Backup & reset > Network settings reset.
If no go, his alternatives are to (assuming he's not bootloader unlocked): try a factory reset; next, re-flash his appropriate kdz in LGUP-NEW. He should backup his userdata first.
If bootloader unlocked (UsU) he could re-flash his modem.bin or modem.img file from a SALT extract of his appropriate kdz.
Click to expand...
Click to collapse
sdembiske said:
Network reset is your first & best option. Re-flashing the kdz is your last option.
Use this site for the kdz download and scroll down to and use this Telus kdz ( H81220z_00_0327.kdz: it does work on Koodo as well): https://lg-firmwares.com/lg-h812-firmwares/firmwares/
Refer to this link for flashing with LGUP-NEW: https://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
As a 'Senior Member" you should know that it is an XDA courtesy to use the Thanks button - you should have learned to use it by now - bottom right of the post
Click to expand...
Click to collapse
Thanks! I am getting him to do a Network settings reset right now. I'll wait and see if that resolves the issue. If it doesn't I will attempt flashing.
I do have a question about the bootloader. You said that it is required to be unlocked. But I read that on the H812 you can't unlock the bootloader. So how does that work? Can I just flash a Marshmallow kdz onto the existing MM OS? I see that his current software version is H81220z. I thought that since there is no root (and no bootloader unlock?) for MM, that I have to downgrade to Lollipop (as explained in these instructions). I thought an unlocked bootloader is always a prerequisite?
Aha! I searched and searched and eventually found this key post. It points to this thread here about (kind of, sort of) unlocking the bootloader and also recommends a backup with SALT.
threehappypenguins said:
Aha! I searched and searched and eventually found this key post. It points to this thread here about (kind of, sort of) unlocking the bootloader and also recommends a backup with SALT.
Click to expand...
Click to collapse
Yes, quite a number of us now have unlocked our bootloader, thanks to the unwavering steadfastness of @steadfasterX, author of the UsU unlock method.
Ensure you do upgrade to the latest Telus 1220z MM kdz (even though he is on it already), I linked first with LGUP-NEW to see if the network connection is restored and then do a SALT backup as recommended before unlocking. It is very important you read the OP in the USU unlock thread thoroughly, making sure you understand it complete;y, to avoid easily avoidable screw-ups. You should make sure your friend understands the process and risks as well before proceeding.
steadfasterX has also prepared custom roms for our unlocked H812's and I can recommend both the ASOCP N and the Lineageos O roms for your H812, if your friend doesn't rely on any LG stock proprietary apps, otherwise you can flash him a special stock Nougat LG rom (all available in the Downloads section in the UsU thread).
sdembiske said:
Yes, quite a number of us now have unlocked our bootloader, thanks to the unwavering steadfastness of @steadfasterX, author of the UsU unlock method.
Ensure you do upgrade to the latest Telus 1220z MM kdz (even though he is on it already), I linked first with LGUP-NEW to see if the network connection is restored and then do a SALT backup as recommended before unlocking. It is very important you read the OP in the USU unlock thread thoroughly, making sure you understand it complete;y, to avoid easily avoidable screw-ups. You should make sure your friend understands the process and risks as well before proceeding.
steadfasterX has also prepared custom roms for our unlocked H812's and I can recommend both the ASOCP N and the Lineageos O roms for your H812, if your friend doesn't rely on any LG stock proprietary apps, otherwise you can flash him a special stock Nougat LG rom (all available in the Downloads section in the UsU thread).
Click to expand...
Click to collapse
My friend's phone says that it's MM and software version is H81220z, so he should be good there.
I'm interested in Lineage Oreo, and I'm a little confused about the instructions, if you don't mind enlightening me. So first off, I understand that UsU is required first. In the UsU instructions, it says:
Flash the baseband package now: <model>_UsU_baseband_flash-in-twrp.zip
Click to expand...
Click to collapse
But in the Lineage O instructions, it says:
If you have ever flashed the UsU baseband package: Clean flash the modem partition from your backup in TWRP.
Click to expand...
Click to collapse
So I assume that I'm supposed to just skip flashing the baseband in the UsU instructions? What about installing SuperSU afterwards? Is flashing that new baseband required?
I guess what I'm wondering is, should I flash the baseband, like in UsU instructions, then revert back to the original baseband, like in the Lineage O instructions, or should I just skip flashing the baseband in the first place?
threehappypenguins said:
My friend's phone says that it's MM and software version is H81220z, so he should be good there.
I'm interested in Lineage Oreo, and I'm a little confused about the instructions, if you don't mind enlightening me. So first off, I understand that UsU is required first. In the UsU instructions, it says:
But in the Lineage O instructions, it says:
So I assume that I'm supposed to just skip flashing the baseband in the UsU instructions? What about installing SuperSU afterwards? Is flashing that new baseband required?
I guess what I'm wondering is, should I flash the baseband, like in UsU instructions, then revert back to the original baseband, like in the Lineage O instructions, or should I just skip flashing the baseband in the first place?
Click to expand...
Click to collapse
The reason you should re-flash the same kdz, is to see if it gets the network connectivity issue solved before proceeding with anything else as you may find the problem still exists.
If you are planning to go the the LG Nougat stock rom, the baseband should be flashed. If you're going to the H812 Lineage O rom, just flash the modem.bin file from the SALT backup you do - you can always flash the baseband later if there is a problem and it is needed. Flash SuperSu after.
You're still forgetting the Thanks button, eh ... ? Hint: It's a good habit to get into when receiving help from other members.
sdembiske said:
The reason you should re-flash the same kdz, is to see if it gets the network connectivity issue solved before proceeding with anything else as you may find the problem still exists.
If you are planning to go the the LG Nougat stock rom, the baseband should be flashed. If you're going to the H812 Lineage O rom, just flash the modem.bin file from the SALT backup you do - you can always flash the baseband later if there is a problem and it is needed. Flash SuperSu after.
You're still forgetting the Thanks button, eh ... ? Hint: It's a good habit to get into when receiving help from other members.
Click to expand...
Click to collapse
Well, I successfully unlocked the bootloader using UsU. I flashed the the baseband package, because I figure I will first re-flash the same kdz. I also decided I will flash stock Nougat because I figure it will be more stable for my friend. Unfortunately, I only got as far as flashing the baseband package and SuperSU.zip. When I try to boot into the OS, it just hangs on the "LG Life's Good" logo forever. Should I go ahead and flash the MM kdz using LG Up new anyway? I already tried a factory reset, and it didn't make a difference.
threehappypenguins said:
Well, I successfully unlocked the bootloader using UsU. I flashed the the baseband package, because I figure I will first re-flash the same kdz. I also decided I will flash stock Nougat because I figure it will be more stable for my friend. Unfortunately, I only got as far as flashing the baseband package and SuperSU.zip. When I try to boot into the OS, it just hangs on the "LG Life's Good" logo forever. Should I go ahead and flash the MM kdz using LG Up new anyway? I already tried a factory reset, and it didn't make a difference.
Click to expand...
Click to collapse
If you want to hard brick your friend's phone and possibly lose a friend, sure, ignore the UsU thread OP warnings ... i.e., DO NOT flash with LGUP-NEW now that the phone is unlocked. If you're going to the stock Nougat, flash the N modem from the UsU thread. If that doesn't work, flash the MM modem from a SALT extraction of a clean Telus H81220z kdz.
Suggest you read the OP in the UsU thread fully, i.e., all of it including the FAQ's and make sure you understand it all this time.
I finally figured out why I'm so confused. Original, when you said this:
sdembiske said:
If no go, his alternatives are to (assuming he's not bootloader unlocked): try a factory reset; next, re-flash his appropriate kdz in LGUP-NEW.
Click to expand...
Click to collapse
I misread. I thought you said "assuming he's bootloader unlocked." So I kept thinking that in order to do ANYTHING (flash the kdz), his bootloader had to be unlocked.
I read the OP over and over, and didn't see the part about never kdz flashing with LGUp, coupled with my misunderstanding that I had to be bootloader unlocked in order to flash with lgup. But I finally found what you're talking about in the FAQ.
You can't! At least for the KDZ flashing part: not yet.
SALT will allow flashing of KDZ files with the upcoming version 4.0 but until then do not flash with lgup and do not use the LG Android internal updater --> You WILL 100% brick your device.
Click to expand...
Click to collapse
I realize all this is a risk to my friend's phone, it's just that I was the one who talked him into buy a used decent phone, rather than buying a new cheapo crappy phone. I just wish I didn't misread what you had said and tried flashing with LGUp *before* I bootloader unlocked.
It's been a long week.
P.S. - I wouldn't lose him as a friend over this. He is very technologically challenged, and keeps thanking me over and over for helping him with all his previous phones, for giving his wife one of our used old phones (she previously had no phone), for helping set up his network with a Tomato firmware router and OpenDNS so he can know what in the world his kids are doing online and have control over the network, etc. So if I bricked his phone, I would just buy another one used for him. He wouldn't care. He just needs a half decent, inexpensive phone to run his small business. Right now, he's just using his old phone for the time being. It's a MotoE that he's had for the last 8 years and he says, "I need to upgrade." Lol
I searched and searched for the Nougat modem (at this point, I might as well upgrade to Nougat), and this is what I found. Is this correct? Or is there another version that I need because that one isn't compatible with my phone? I also assume that the modem zip is flashable via TWRP? I see the "META-INF" folder.
This is the stock Nougat I was going to flash (with TWRP? It looks like a flashable zip). My ARB is 0. My GPT compatibility is H811.
I see in the N stock that there is already a modem.bin file. So should I first flash the stock N zip, and THEN flash the separate N modem? Also, the instructions say:
16) I just wanna flash Nougat STOCK. Are there any worry free UsU downloads for it available?
Sure: here
After flashing ensure you flash your model baseband package!
After that and while still in TWRP: Choose Reboot -> RECOVERY ! This should ensure TWRP will not be overwritten on Android boot
Click to expand...
Click to collapse
So, in summary:
1. Flash stock Nougat zip
2. Flash Nougat modem zip
3. Flash my model's baseband (again)?
And if none of that works:
flash the MM modem from a SALT extraction of a clean Telus H81220z kdz
Click to expand...
Click to collapse
?
threehappypenguins said:
I searched and searched for the Nougat modem (at this point, I might as well upgrade to Nougat), and this is what I found. Is this correct? Or is there another version that I need because that one isn't compatible with my phone? I also assume that the modem zip is flashable via TWRP? I see the "META-INF" folder.
This is the stock Nougat I was going to flash (with TWRP? It looks like a flashable zip). My ARB is 0. My GPT compatibility is H811.
I see in the N stock that there is already a modem.bin file. So should I first flash the stock N zip, and THEN flash the separate N modem? Also, the instructions say:
So, in summary:
1. Flash stock Nougat zip
2. Flash Nougat modem zip
3. Flash my model's baseband (again)?
And if none of that works:
?
Click to expand...
Click to collapse
Yes. Refer to FAQ #22 in the UsU thread and the Stock N report by @grantdb.
The reason why you get intermittent service because the phone you found had been blacklisted by the original owner
deltadiesel said:
The reason why you get intermittent service because the phone you found had been blacklisted by the original owner
Click to expand...
Click to collapse
It was locked to Koodo, and the original owner told me that. I called Koodo, gave the IMEI, and they gave me the Network unlock code. If it was blacklisted, wouldn't Koodo have said something?
sdembiske said:
Yes. Refer to FAQ #22 in the UsU thread and the Stock N report by @grantdb.
Click to expand...
Click to collapse
I flashed stock Nougat, then Nougat modem, then the H812 baseband, then rebooted directly back to TWRP. Then I booted up the phone and it was in Spanish. So I changed that to English. Then I had rebooted the phone again (adding a SIM card for testing), and it was in Spanish again, so I changed it back to English. Then I rebooted the phone again, and it was in Russian, so I changed it back to English, and also deleted all the extra keyboards which included Spanish and Russian (at least, it looked like it was Russian). Rebooted the phone a couple more times, and it stays in English.
So far, everything is working.
Thanks again for your help! Will report back if the intermittent issue comes back, or if everything continues to work well, in case anybody with the same issue is looking for a fix.
On another note, out of curiosity, I tried *#*#4636#*#* on the Phone's dial pad to open the service menu, and noticed that Phone Information is still blocked. Just curious... is that a ROM thing? Or a baseband/modem thing?
threehappypenguins said:
I flashed stock Nougat, then Nougat modem, then the H812 baseband, then rebooted directly back to TWRP. Then I booted up the phone and it was in Spanish. So I changed that to English. Then I had rebooted the phone again (adding a SIM card for testing), and it was in Spanish again, so I changed it back to English. Then I rebooted the phone again, and it was in Russian, so I changed it back to English, and also deleted all the extra keyboards which included Spanish and Russian (at least, it looked like it was Russian). Rebooted the phone a couple more times, and it stays in English.
So far, everything is working.
Thanks again for your help! Will report back if the intermittent issue comes back, or if everything continues to work well, in case anybody with the same issue is looking for a fix.
On another note, out of curiosity, I tried *#*#4636#*#* on the Phone's dial pad to open the service menu, and noticed that Phone Information is still blocked. Just curious... is that a ROM thing? Or a baseband/modem thing?
Click to expand...
Click to collapse
Not sure about the language issue as I haven't used the stock N rom but if it continues to hold, no problem. Make sure you do a TWRP backup when you have it where you want it.
The 'secret' menu accessed from the dial pad hasn't worked for me in AOSCP N or Lineage O so it may be a rom thing. *#546368#*812# is the dial pad code that should be tried in any event.
I just wanted to report that my friend no longer has any more issues with no service. Everything is working well. I will edit my first post to state that the problem is solved and what I did.
Is this do-able with out unlock.bin??
I've tried using adb/fastboot. ADB reports the device OK; fastboot can't see the device.
I've tried all manner of drivers to load........ I know there are separate drivers for adb and fastboot.
This is driving me nuts.
Finally, are there different SUB-variants of the 996?? One generic and one US Sprint??
Thanks
You must use dirtysanta to root
[Guide][Tutorial] Root TWRP LG V20 using Dirtysanta[Most Variants][Noobfriendly]
Good day, Here's the modified dirtysanta method to root LG V20 and install TWRP. This guide will help you in rooting your device with much easier situation. Before you begin: (Your phone's internal storage will be wiped or simply formatted or...
forum.xda-developers.com
ROMSG said:
You must use dirtysanta to root
[Guide][Tutorial] Root TWRP LG V20 using Dirtysanta[Most Variants][Noobfriendly]
Good day, Here's the modified dirtysanta method to root LG V20 and install TWRP. This guide will help you in rooting your device with much easier situation. Before you begin: (Your phone's internal storage will be wiped or simply formatted or...
forum.xda-developers.com
Click to expand...
Click to collapse
The only issue with that response: The DirtySanta thread you link to lists the following devices, admonishing that any others will get bricked:
- Verizon (VS995)
- Sprint (LS997)
- ATT (H910)
- Korean(F800L)
- USS996 (BPT, UCL)
- Canadian (H915)
Unless there's a typo in it, the USS996 is NOT the same as the US996. The US996 is a carrier unlocked US variant. The other US996 is locked to US Cellular. A bit of clarity is necessary here...
Graf_Eberstein said:
The only issue with that response: The DirtySanta thread you link to lists the following devices, admonishing that any others will get bricked:
- Verizon (VS995)
- Sprint (LS997)
- ATT (H910)
- Korean(F800L)
- USS996 (BPT, UCL)
- Canadian (H915)
Unless there's a typo in it, the USS996 is NOT the same as the US996. The US996 is a carrier unlocked US variant. The other US996 is locked to US Cellular. A bit of clarity is necessary here...
Click to expand...
Click to collapse
I found this some of the Links are broken.
V20 [H915|US996] DirtyElf Bootloader Unlock and Root guide
Firmware
US99610f_00_1205.kdz
usb drivers for windows
Terminal Emulator for Android "f-droid Download APK at bottom of page"
Before you flash the KDZ to downgrade your firwmare make a DUMP backup of ALL files first it will have your EFS and that's very very important it has your IMEI number. You don't need to dump system or cache.
Darnrain1 said:
I found this some of the Links are broken.
V20 [H915|US996] DirtyElf Bootloader Unlock and Root guide
Firmware
US99610f_00_1205.kdz
usb drivers for windows
Terminal Emulator for Android "f-droid Download APK at bottom of page"
Before you flash the KDZ to downgrade your firwmare make a DUMP backup of ALL files first it will have your EFS and that's very very important it has your IMEI number. You don't need to dump system or cache.
Click to expand...
Click to collapse
Thank you! I am looking that over. One question I do have for you: Is that dump backup needed for anything beyond the EFS to get the IMEI? Asking only because I was able to extract the IMEI already. I'm not physically working on this till the weekend, so I'm going to read up/download stuff in the interim and go from there. If I end up with questions (and I just might from the bit I've read so far*), I'll append this post or reply to it.
* This is an example of where the uncertainty sets in: "For official US996 model owners that do not want to void their warranty, follow the Dirtysanta Sprint(LS997) method but make sure to flash a US996 Stock rom instead." I'm assuming "official" applies to an actual V20 model US996, regardless of carrier/unlock status. I'm extrapolating that the H915 is an US996 with a differently configured kernel. Since the LS997 is only mentioned separately, is the 997 a CDMA version of the (GSM) 996?
LTE is inferred, GSM is for distinction, so I'm assuming the 915 and 996 are GSM devices. I also know Sprint is/was a CDMA carrier. CDMA hardware would infer different modules would be loaded by the kernel, than for GSM, and could therefore hang or brick the device. At least that's where the rail line used by my train of thought takes me. Or, does the difference between CDMA and GSM versions not matter?
You are correct about the broken links: Tilde88's US996 100% Stock deODEXEd Rom, which is listed in the linked article, is a bad link. I did some fairly general "looking" for that ROM elsewhere, found a couple of articles when Google-searching, but haven't had a chance to check those out (that will have to wait until tomorrow). If it turns out that there is no alternate link to the ROM, are there any other ways of getting it, short of looping @Tilde88 in?
Graf_Eberstein said:
Thank you! I am looking that over. One question I do have for you: Is that dump backup needed for anything beyond the EFS to get the IMEI? Asking only because I was able to extract the IMEI already. I'm not physically working on this till the weekend, so I'm going to read up/download stuff in the interim and go from there. If I end up with questions (and I just might from the bit I've read so far*), I'll append this post or reply to it.
* This is an example of where the uncertainty sets in: "For official US996 model owners that do not want to void their warranty, follow the Dirtysanta Sprint(LS997) method but make sure to flash a US996 Stock rom instead." I'm assuming "official" applies to an actual V20 model US996, regardless of carrier/unlock status. I'm extrapolating that the H915 is an US996 with a differently configured kernel. Since the LS997 is only mentioned separately, is the 997 a CDMA version of the (GSM) 996?
LTE is inferred, GSM is for distinction, so I'm assuming the 915 and 996 are GSM devices. I also know Sprint is/was a CDMA carrier. CDMA hardware would infer different modules would be loaded by the kernel, than for GSM, and could therefore hang or brick the device. At least that's where the rail line used by my train of thought takes me. Or, does the difference between CDMA and GSM versions not matter?
You are correct about the broken links: Tilde88's US996 100% Stock deODEXEd Rom, which is listed in the linked article, is a bad link. Since I haven't gotten past the first post yet, I'm going to see if I can find that elsewhere and report back.
Click to expand...
Click to collapse
Sometimes downgrading your firmware to root your phone will corrupt your EFS on the phone and you have to restore it to get cell service working again or to bring back your IMEI number.
There are four files that are your EFS.
With the phone powered off, hold the down vol and plug in usb to computer to restore EFS.
fastboot flash fsg fsg_COM6
fastboot flash misc misc_COM6
fastboot flash modemst1 modemst1_COM6
fastboot flash modemst2 modemst2_COM6
fastboot reboot
Darnrain1 said:
Sometimes downgrading your firmware to root your phone will corrupt your EFS on the phone and you have to restore it to get cell service working again or to bring back your IMEI number.
There are four files that are your EFS.
With the phone powered off, hold the down vol and plug in usb to computer to restore EFS.
fastboot flash fsg fsg_COM6
fastboot flash misc misc_COM6
fastboot flash modemst1 modemst1_COM6
fastboot flash modemst2 modemst2_COM6
fastboot reboot
Click to expand...
Click to collapse
Thank you.
FYI, I just amended my prior response (above) re. the ROM as well.
Graf_Eberstein said:
Thank you.
FYI, I just amended my prior response (above) re. the ROM as well.
Click to expand...
Click to collapse
Your welcome,
Stock Oreo Rom, flash in order But there are a lot more roms for the Lgv20 you can look around if you want.
LG V20 ROMs, Kernels, Recoveries, & Other Developm
US996 DIrtysanta Rom
ezV2020 kernel for Oreo link
Magisk-v21.4.zip
Latest version of twrp link
Darnrain1 said:
I found this some of the Links are broken.
V20 [H915|US996] DirtyElf Bootloader Unlock and Root guide
Firmware
US99610f_00_1205.kdz
usb drivers for windows
Terminal Emulator for Android "f-droid Download APK at bottom of page"
Before you flash the KDZ to downgrade your firwmare make a DUMP backup of ALL files first it will have your EFS and that's very very important it has your IMEI number. You don't need to dump system or cache.
Click to expand...
Click to collapse
Ok, so I finally got to where I'm able to run that dump backup. I've been at it for the better part of 8 man hours, and it keeps crashing. Finally got everything backed up except SYSTEM IMAGE. Whenever I try to back up that segment, the backup crashes. You said I don't need to do this against CACHE, which I get. There's both a SYSTEM and a SYSTEM IMAGE, so now I'm wondering if you meant the latter instead of the former... If not, how do I get past this obstacle?
FWIW, I'm writing to an otherwise empty, brand new 32 GB Class 10 card. Initially I was using a surplus 16 GB card, then realized that I was coming up around 4 GB short, and pegged the failure on that. But the same happens on the larger card. In case it matters, the backup gets to about 60% before failing...
Graf_Eberstein said:
Ok, so I finally got to where I'm able to run that dump backup. I've been at it for the better part of 8 man hours, and it keeps crashing. Finally got everything backed up except SYSTEM IMAGE. Whenever I try to back up that segment, the backup crashes. You said I don't need to do this against CACHE, which I get. There's both a SYSTEM and a SYSTEM IMAGE, so now I'm wondering if you meant the latter instead of the former... If not, how do I get past this obstacle?
FWIW, I'm writing to an otherwise empty, brand new 32 GB Class 10 card. Initially I was using a surplus 16 GB card, then realized that I was coming up around 4 GB short, and pegged the failure on that. But the same happens on the larger card. In case it matters, the backup gets to about 60% before failing...
Click to expand...
Click to collapse
Your phone is rooted great.
DUMP backup with LGUP. Might not be to late. Just hold vol up and plug in usb to phone and computer. Go into LGUP and choose DUMP all files. You don't need to dump system or cache. This will save all the files on your computer. Back the files up like google drive or something.
Take battery out and put back in. Then you want to boot into twrp and do a format.
Then your ready to install an OS on your phone. Why don't you check out my rom I made it's stock Oreo debloated. There are some good guides on there also you can follow. link
If you need any more help just ask. I don't mind.
I just wanted to thank you for the guidance to date. Great news: After many fits, starts, wrong turns, interruptions, and muckups both real and imagined, my V20 now has Oreo Lemondrop installed, and I presume it is also rooted.
With the initial hurdle overcome, it's time for new questions (see photos for the first three):
* The device reports no S/N. Normal?
* The OS reports no kernel version. Normal?
* The device still boots to the red triangle before loading Lemondrop. I was under the impression that would go away now, or am I wrong?
* A lot of games and other crud is being installed by Mobile Services Manager. Is that because I missed something?
The latter may not matter much: I'm going to move the SIM from my regular phone to the V20 to see if it will make/receive calls. If it does, it'll get a SIM of its own, so I can use it as a second line. If it doesn't work (I've seen posts about bands not working, etc), I'll be done with it altogether.
However, should the phone work, what'll make this whole enterprise a complete success, will be to install a more current Android release; I'm expecting 10 or 11, but would be tickled if it's 12 or 13. But first things first...
Graf_Eberstein said:
I just wanted to thank you for the guidance to date. Great news: After many fits, starts, wrong turns, interruptions, and muckups both real and imagined, my V20 now has Oreo Lemondrop installed, and I presume it is also rooted.
With the initial hurdle overcome, it's time for new questions (see photos for the first three):
* The device reports no S/N. Normal?
* The OS reports no kernel version. Normal?
* The device still boots to the red triangle before loading Lemondrop. I was under the impression that would go away now, or am I wrong?
* A lot of games and other crud is being installed by Mobile Services Manager. Is that because I missed something?
The latter may not matter much: I'm going to move the SIM from my regular phone to the V20 to see if it will make/receive calls. If it does, it'll get a SIM of its own, so I can use it as a second line. If it doesn't work (I've seen posts about bands not working, etc), I'll be done with it altogether.
However, should the phone work, what'll make this whole enterprise a complete success, will be to install a more current Android release; I'm expecting 10 or 11, but would be tickled if it's 12 or 13. But first things first...
Click to expand...
Click to collapse
Yeah no SN and no Kernel is normal. It's also normal to have the boot screen come up, it's because your phone is rooted now.
I have to run Oreo because LTE is not working in crDroid or Lineage os. There are proprietary drivers that are in Oreo to make LTE work and they are not in any other android os. But if all you need is 4G then maybe another os would work for you. In the USA they did away with 4G only LTE now. So I thought I would make the Lemon Drop rom, if I have to use Oreo why not make it fast. Plus most everything works in Lemon Drop. Like second screen and so on. I have used crDroid before it's good I will link the files for you.
Update: I found and removed Mobile Services Manager in the latest version of Auto_Debloat. Thanks for bringing this to my attention.
crDroid 11 just format and flash in twrp reboot.
also flash Magisk-v21.4.zip so you can have root.
you may have to flash twrp also I am not sure, it's been awhile before I install crDroid. You can always flash twrp in fastboot mode if you have to.
Take Care.
Darnrain1 said:
Yeah no SN and no Kernel is normal. It's also normal to have the boot screen come up, it's because your phone is rooted now.
I have to run Oreo because LTE is not working in crDroid or Lineage os. There are proprietary drivers that are in Oreo to make LTE work and they are not in any other android os. But if all you need is 4G then maybe another os would work for you. In the USA they did away with 4G only LTE now. So I thought I would make the Lemon Drop rom, if I have to use Oreo why not make it fast. Plus most everything works in Lemon Drop. Like second screen and so on. I have used crDroid before it's good I will link the files for you.
Update: I found and removed Mobile Services Manager in the latest version of Auto_Debloat. Thanks for bringing this to my attention.
crDroid 11 just format and flash in twrp reboot.
also flash Magisk-v21.4.zip so you can have root.
you may have to flash twrp also I am not sure, it's been awhile before I install crDroid. You can always flash twrp in fastboot mode if you have to.
Take Care.
Click to expand...
Click to collapse
Thank you again, and you're welcome for the bit on the Mobile Services Manager. My apologies for the lag in responding too; real life got in the way for a bit there. I'll look into your suggestion as I get a chance and will report back.
Graf_Eberstein said:
Thank you again, and you're welcome for the bit on the Mobile Services Manager. My apologies for the lag in responding too; real life got in the way for a bit there. I'll look into your suggestion as I get a chance and will report back.
Click to expand...
Click to collapse
Not a problem. Because I only have an H910 I didn't get all the bloatware on other lgv20 phones. But that Mobile Services Manager is a huge bloatware that installs more bloatware. So I thought I would try and find it and remove it in the latest version. You can update Auto_Debloat and it should get rid of that Mobile Services Manager for you. All you have to do is just flash the new version in twrp and reboot.