Do we know if the Marshmallow update updates the bootloader?
Our current root method uses an exploited 5.1 system, so it will not work on 6.0. Someone will need to use a similar exploit on the 6.0 system if the exploit does indeed still work.
If the bootloader is not updated with 6.0, we will be able to go back to 5.1 simply by flashing the 5.1 system. If it is updated, we may have lost root for forever. I will stick with 5.1 for now and I will take the Marshmallow update this Sunday if there is no additional information.
Any way to update to MM if you are using a Verizon V10 on AT&T?
jabreu203 said:
Any way to update to MM if you are using a Verizon V10 on AT&T?
Click to expand...
Click to collapse
you can use the kdz but it's nowhere to be seen
I'm in the same boat with a T-Mobile sim. Waiting for a kdz to get onto Marshmallow.
If you tell me how I can do it.
Unfortunately I clicked update now. :/ I dont know too much but if you tell me how to discover this info I will definitely tell you if the boot loader is adjusted with the update.
jalthejew said:
Unfortunately I clicked update now. :/ I dont know too much but if you tell me how to discover this info I will definitely tell you if the boot loader is adjusted with the update.
Click to expand...
Click to collapse
You should be able to find the bootloader version in a benchmark app, then I could do the same
The bootloader does not actually need to be unlocked at all to root the device. All you need is the KDZ file and some experienced hacking to do it. That's how we got root for the V10 anyways.
i have a weird question to ask. i am using att sim card on a Verizon v10. can i flash a kdz att or even the unlocked version system on the Verizon variant ?
If I'm not mistaken the boot loader for the Verizon Lg G3 wasn't unlocked, they just had to work around that.
hann1balk1ng said:
If I'm not mistaken the boot loader for the Verizon Lg G3 wasn't unlocked, they just had to work around that.
Click to expand...
Click to collapse
I was about to say 'Yes they did, I had twrp and custom roms...' but then I powered it up and remembered they had to use the 'Bump Method' to install twrp alongside the default bootloader and recovery. If you powered on while holding volume down you'd get the default lg recovery, but then if you went to factory reset from there and clicked yes it brought up twrp. So yea, a pretty interesting work around there.
kjcsg said:
I was about to say 'Yes they did, I had twrp and custom roms...' but then I powered it up and remembered they had to use the 'Bump Method' to install twrp alongside the default bootloader and recovery. If you powered on while holding volume down you'd get the default lg recovery, but then if you went to factory reset from there and clicked yes it brought up twrp. So yea, a pretty interesting work around there.
Click to expand...
Click to collapse
@thecubed @IllegalArgument @autoprime @Shelnutt2 @Dees_Troy
Maybe these devs can help if they are still around and have access to a Verizon LG V10 with root and are willing to spend the time to try and help out this thread...
burnsky05 said:
@thecubed @IllegalArgument @autoprime @Shelnutt2 @Dees_Troy
Maybe these devs can help if they are still around and have access to a Verizon LG V10 with root and are willing to spend the time to try and help out this thread...
Click to expand...
Click to collapse
Lets hope so.....
burnsky05 said:
@thecubed @IllegalArgument @autoprime @Shelnutt2 @Dees_Troy
Maybe these devs can help if they are still around and have access to a Verizon LG V10 with root and are willing to spend the time to try and help out this thread...
Click to expand...
Click to collapse
They might not be so inclined. IIRC, they were rightly agitated when someone open-sourced their work, potentially making it easier for manufacturers to prevent in the future, despite them specifically advising against it.
kjcsg said:
I was about to say 'Yes they did, I had twrp and custom roms...' but then I powered it up and remembered they had to use the 'Bump Method' to install twrp alongside the default bootloader and recovery. If you powered on while holding volume down you'd get the default lg recovery, but then if you went to factory reset from there and clicked yes it brought up twrp. So yea, a pretty interesting work around there.
Click to expand...
Click to collapse
The bootloader was still locked, its just that the images were signed to make the boot loader think they were signed.
NetworkingPro said:
The bootloader was still locked, its just that the images were signed to make the boot loader think they were signed.
Click to expand...
Click to collapse
And the original recovery was was modified or somehow the bump script hijacked the factory reset process to divert to twrp. I wonder if the bump script can be modified with the correct paths and info such as pplus instead of vs985.
kjcsg said:
And the original recovery was was modified or somehow the bump script hijacked the factory reset process to divert to twrp. I wonder if the bump script can be modified with the correct paths and info such as pplus instead of vs985.
Click to expand...
Click to collapse
It really wasn't that complicated, honestly. All bump did was sign certain bytes like LG to make the bootloader think TWRP was a truly signed image. The same applied to kernels, or anything else that was bumped. When you flashed the newly bumped recovery image you were literally replacing the factory one.
NetworkingPro said:
It really wasn't that complicated, honestly. All bump did was sign certain bytes like LG to make the bootloader think TWRP was a truly signed image. The same applied to kernels, or anything else that was bumped. When you flashed the newly bumped recovery image you were literally replacing the factory one.
Click to expand...
Click to collapse
My only question then is why would they leave the original, the lg recovery, there when you would power on while holding volume down and have to go through the factory reset button to get to twrp instead of just overwriting the original with twrp completely? Not that it matters too much, I just wish I knew how to do it so I could get the vs990 bumped or somehow get twrp on it. But I think I'd need a good bit of exploit schooling to understand it all haha.
I hope we get at least recovery soon, but I've never understood why recoveries never have a text editor included! (and often not even shell access, much less SU shell access!)
Related
Hello Guys,
Just wanted to check there is any official method to reload LG D802 boot loader which will remove the signature "ROOTED" in recovery mode. This will help to retain the warranty in case of any hardware failures like speaker, cam etc. Just wanted to know if any method is available
Thanks
ravi.ameer said:
Hello Guys,
Just wanted to check there is any official method to reload LG D802 boot loader which will remove the signature "ROOTED" in recovery mode. This will help to retain the warranty in case of any hardware failures like speaker, cam etc. Just wanted to know if any method is available
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2432476&highlight=remove+root+status - Pretty sure this works for most variants besides maybe VZW to remove that and get you back to stock.
es0tericcha0s said:
http://forum.xda-developers.com/showthread.php?t=2432476&highlight=remove+root+status - Pretty sure this works for most variants besides maybe VZW to remove that and get you back to stock.
Click to expand...
Click to collapse
Hey, thanks for the great guide! But this doesn't reload the recovery loader. I tried this method and I'm easily able to revert to stock but the recovery loader is triggered as ROOTED and this will kill the warranty. (I'm not soo bothered about the warranty of the software but it matters about hardware. Who knows tomorrow)
Big thanks if we would find a solution for this.
Thanks.
I ran across a thread somewhere where it was mentioned that you have to reload it twice.
http://forum.xda-developers.com/showpost.php?p=48754417&postcount=9
Sounds like a plan.... first flash would be removing custom like removing root access....and second flash was like racking the device that the device is not rooted and reloading the boot loader itself and resetting the trigger...truly sounds like a plan.... I will try this method....
Sent from my LG-D802
Trying to root Nougat (Android 7)? Then read the comments at the bottom please...
I will first state I do NOT own a Moto G4, I own the G3 and the X Pure which are both 3rd Gen devices, but I was requested to write this tutorial by a few users here due to lots of failed root attempts using older "standard" methods that do not work on this device. I also do not like the "one click" root methods, because they can and do fail (KingoRoot will brick a Moto G3/4, regardless of what it's web page says), and when they do people have no idea how to fix it. The manual way is not difficult, and it teaches you how to work on, fix, and use your device on a level above that of the average smartphone user.
I will only cover rooting, the prerequisites are covered elsewhere in detail and I will link to reliable sources for the information. Specifics of the prerequisites are outside of the scope of this tutorial, but are open for discussion in this thread. Remember, I do not own this device although the methods used are the same as similar devices.
Prerequisites:
0) Be running Marshmallow (Android 6.x) stock ROM, at this time Nougat (Android 7.x) is not working via any method.
1) Device must have an unlocked bootloader. See Moto - Unlocking the Bootloader for more info.
NOTE: As of 7/18/2016, Amazon ad-subsidised Moto G 4th Gen devices cannot be bootloader unlocked, therefore they cannot be rooted. Sorry, Lollipop and newer Android security changes pretty much put an end to that.
2) You need to have TWRP installed or one-time booted via fastboot. CWM and other recoveries will NOT work at this time. See TWRP's Moto G 2016 page
3) You need a copy of the latest stable SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device. SR1-SuperSU-v2.78-SR1-20160915123031.zip is the lastest version verified to work with this method.
Note: Do NOT use any 2.77 version, it was a beta intended specifically for the SG Note 7 and will not work, it does not harm but fails to root.
4) Reboot and start TWRP recovery, and PERFORM A COMPLETE BACKUP IN TWRP (Nandroid)!!!
How to do it:
Now, the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...
In TWRP, go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press enter (there is no confirmation returned), then exit and press the Home key. Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).
Why do I have to do this???
For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.
Hope this is helpful to someone!
As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.
EDIT: Photos added showing what a proper command and flash should look like. Note that in picture 1 the exit command is not needed, you can just back out. In pictures 2 and 3 a proper flash of SuperSU is shown, note that system-less mode is specified and the boot image is patched, this is what should occur. It is normal for it to loop once or twice, but that is it, first boot could take 10 minutes plus.
Notes on Nougat/Android 7... At this time this method of rooting does not work properly on the official Nougat ROM for this device, it causes WiFi issues and interface problems (settings crashes, etc) and with no complete factory image there is no work fix other than to restore your Nandroid backup to pre-root status. If you wish to play with this method and try it, your on your own, I will try to assist but as I stated earlier I do not own this device. To my knowledge as of this posting, there is no working root on stock Android 7 on this device.
I can confirm this worked on my formerly-amazon XT1625 16GB G4. You will get an error about not being able to mount /data, but it proceeds and works anyway.
This is exactly what was missing! I rooted as normal with the latest SuperSU expecting it to just work like on other phones/tablets, but yeah. Before specifying systemless, it hung on boot. After following your instructions it booted right up. Thanks!
Also if you setup adaptable storage with your SDcard, so it works like internal storage, TWRP can't find any files on the SDcard. You will need to revert to non-adaptable storage for TWRP to find the supersu ZIP file.
And make sure you're using the latest SuperSU-- I accidentally tried a very old version which did not work!
Scared Noobie
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Appreciate this. I miss the old days where it was all simple. Everything was flashable. Never had to flash back to something or re flash.
cuvtixo said:
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Click to expand...
Click to collapse
It's about as common as bring bricked from performing a factory reset, because that is the only part that really does much... So extremely rare, but the possibility is always there. Remember to have patience, the resets and wipes can take what seems like forever.
The dangerous part is what you do after the bootloader is unlocked.
Sent from my MotoG3 using Tapatalk
cuvtixo said:
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Click to expand...
Click to collapse
Very rare...all you need is read, read, read and follow the instructions. Good luck
Very nice and just what I needed. Worked perfectly on my Amazon Moto G4 with ads. I got no errors or messages but booted fine-got caught in a boot loop once as the SuperSU file explains after it installs. Boots in less then a minute first time.
Marty
acejavelin said:
It's about as common as bring bricked from performing a factory reset, because that is the only part that really does much... So extremely rare, but the possibility is always there. Remember to have patience, the resets and wipes can take what seems like forever.
The dangerous part is what you do after the bootloader is unlocked.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Hey i wiped this up based on your post it should really help. it completely automates the process check it out if you want to and you can also ad it to the OP if you want to.
DOWNLOAD TOOL HERE Root-moto-g-4th-gen
Tomsgt said:
Hey i wiped this up based on your post it should really help. it completely automates the process check it out if you want to and you can also ad it to the OP if you want to.
DOWNLOAD TOOL HERE Root-moto-g-4th-gen
Click to expand...
Click to collapse
cheers mate
I signed up for xda just to give you props! I rooted my phone using instructions not from here and i was suck in a boot loop. your little command there fixed it! I freakin love you.. wish i could buy you dinner! Thanks a million
zipjay said:
I signed up for xda just to give you props! I rooted my phone using instructions not from here and i was suck in a boot loop. your little command there fixed it! I freakin love you.. wish i could buy you dinner! Thanks a million
Click to expand...
Click to collapse
Your welcome... Just give click thanks on the first post, but if you feel absolutely compelled to buy me dinner, there is the Donate button.
Sent from my MotoG3 using Tapatalk
I rooted my G4 in the normal way using supersu 2.46, and now boot hangs on the white Moto screen. (advice from another site)
I am waiting for a SD card to update to 2.76 with the systemless command.
Is there anything else I can do in the interim, I tried deleting the contents of /supersu from Twrp and that hasnt made any difference. I have also wiped data and caches.
thanks .. Mike
mikeruss said:
I rooted my G4 in the normal way using supersu 2.46, and now boot hangs on the white Moto screen. (advice from another site)
I am waiting for a SD card to update to 2.76 with the systemless command.
Is there anything else I can do in the interim, I tried deleting the contents of /supersu from Twrp and that hasnt made any difference. I have also wiped data and caches.
thanks .. Mike
Click to expand...
Click to collapse
Can't you just use MTP mode of TWRP to copy the latest SuperSU to internal storage then flash after creating the config file?
Sent from my MotoG3 using Tapatalk
thank you, worked fine.
would I be right in thinking I need the sdk23, arm, 64 bit version of xposed ?
mikeruss said:
thank you, worked fine.
would I be right in thinking I need the sdk23, arm, 64 bit version of xposed ?
Click to expand...
Click to collapse
I don't know... I don't own the G4 *yet* but possibly in the near future now that I know the Amazon version can have the ads striped out easily enough... I would do a nandorid and try it, if it fails, restore and use the 32-bit version.
Someone else may have a better answer for you.
acejavelin said:
I don't know... I don't own the G4 *yet* but possibly in the near future now that I know the Amazon version can have the ads striped out easily enough... I would do a nandorid and try it, if it fails, restore and use the 32-bit version.
Someone else may have a better answer for you.
Click to expand...
Click to collapse
32 bit
Sent from my Moto G (4) using Tapatalk
thanks, xposed works fine
Well, I was planning on joining all of you with your Moto G4's soon, or possibly the G4 Plus... but since the Amazon version can't be unlocked anymore I got cold feet, and today Best Buy was running a special on the Moto X Pure 32GB edition for $249 (My Best Buy Elite members only), I pulled the trigger on that one instead. No change in helping though, I didn't have the device to begin with so I will continue to assist with this thread as I can.
I know this isn't the correct forum but I've searched and haven't found anything and since this seems to be the closet device I was wondering if there is any development for this device yet or any rooting methods that may work
I looked as well. There does not seem to be any serious develop on the V530. I'm bootloader unlocked but no root or twrp that I could find.
Mike02z said:
I looked as well. There does not seem to be any serious develop on the V530. I'm bootloader unlocked but no root or twrp that I could find.
Click to expand...
Click to collapse
Thanks. I couldn't even get that far. Don't get me wrong it's a nice device but I'm sure a custom ROM would make it fly. Hopefully soon as more people get the device we'll see some development.
First thing first. Bootloader commands must be there.
If so, you just need TWRP
I'd also be very interested in rooting/custom rom for this device, as I moved to it from my Nexus 7 2013 that was very much showing it's age. It's almost painful being on a stock rom from a 3rd party at this point. I've searched through google and nobody seems to be taking much interest in this device. The same was true for the original xperia z tablet and it's got official lineageos support, so I remain hopeful.
love this thing
I would just love to root this beast. New to LG products, not new to rooting. Can anyone point me in the right direction on where to start?
Did you root t
widto08 said:
I would just love to root this beast. New to LG products, not new to rooting. Can anyone point me in the right direction on where to start?
Click to expand...
Click to collapse
Did you ever get this tablet rooted.. I. Can't find any information about this device online it's like it they never made it
Saint$1t said:
Did you ever get this tablet rooted.. I. Can't find any information about this device online it's like it they never made it
Click to expand...
Click to collapse
I am having problems even booting into bootloader on this thing. I was able to boot into recovery mode but can't get out of the "no commands".
adb reboot recovery
adb reboot bootloader -> just reboots it.
It might be possible to use dirtyc0w exploit to get root access on this tablet.(nvm it seems our android version is already patched for that. )
I too have been able to get the bootloader unlocked but unable to find a version of TWRP or find any rooting tool that supports this device. Still holding out hope but this doesn't seem to be a super popular device :/
Hey guys! I bricked my tab and i need a stock kdz or system, recovery and boot.imgs! Does anyone have or can pull these file for me thanks in advance!
Sent from my [device_name] using XDA-Developers Legacy app
I have rooted mine..if I had the stock system.img could you used that? This is what I did to obtain root..
Download the Lg download utility mode tool '''https://github.com/Lekensteyn/lglaf''
and the sources ''https://pycryptodome.readthedocs.io/en/latest/src/installation.html'
Then open cmd in the folder and execute: python lglaf.py --debug --rawshell --cr -c '!S sh' <--- there might be an error message or laf_acess_denied but its okay.
re-enter the command: python lglaf.py --debug --rawshell <--- this should open up an interactive shell..enter ls and see if it lists the files on the device then close the interactive shell
run python extract-partitions.py to get the stock boot.bin but change the file extension to .img
push the boot.img to the device, install magisk manager, patch the boot.img, pull img then flash with fastboot
Nice! We finally get root a couple days after a seemingly innocent fall off my bed wrecked my screen :crying:. Deciding on replacing it or getting a MediaPad M5.
tbh I've rooted this device since last month or so but I really didn't have time to make a tutorial
Is anyone able to pull there kdz? My tab is bricked and ive tried LG bridge and all others! Or the the imgs in need to go back to stock! Any help please! Thanks!
Sent from my [device_name] using XDA-Developers Legacy app
Vincent_vann said:
tbh I've rooted this device since last month or so but I really didn't have time to make a tutorial
Click to expand...
Click to collapse
I followed your comment and was able to root. May I use your process to make a tutorial? I will give you credit
---------- Post added at 05:42 PM ---------- Previous post was at 05:33 PM ----------
Thanks to Vincent_vann I have root. With this I can finally start building a custom TWRP for this tablet. I wish we had a forum for this device. I requested one last year but it still hasn't been made even though it was approved. If I get one built, and there isn't a dedicated forum, I'll post it in this thread.
Just built TWRP. I noticed some folks asking for stock recovery, boot, and system img files. I have recovery and boot img. Not sure where to post these though. Same with twrp. If someone has any reccomendations on how to go about this I'll gladly provide.
I have the Canadian variant (v533) and wouldn't mind giving TWRP a whirl on it. All specs are same so I think it'll work. Don't mind testing if you do get somewhere to post TWRP. Also good job on getting it compiled ?
Jambii1987 said:
I have the Canadian variant (v533) and wouldn't mind giving TWRP a whirl on it. All specs are same so I think it'll work. Don't mind testing if you do get somewhere to post TWRP. Also good job on getting it compiled ?
Click to expand...
Click to collapse
Thank you! Unfortunately with nougat file based encryption TWRP has issues with decrypting /data after the setup of the tablet. So it's working 50% which is annoying because you'll have to wipe data whenever you want to flash something. Not a big deal for roms, but very inconvenient for other zips. If you still want it let me know and I'll find a place. Else I'll be tackling the decryption issue this weekend.
xnukemx47 said:
Thank you! Unfortunately with nougat file based encryption TWRP has issues with decrypting /data after the setup of the tablet. So it's working 50% which is annoying because you'll have to wipe data whenever you want to flash something. Not a big deal for roms, but very inconvenient for other zips. If you still want it let me know and I'll find a place. Else I'll be tackling the decryption issue this weekend.
Click to expand...
Click to collapse
I think I'll wait until you try getting decryption working. I have a had many fights with that beast lol
Jambii1987 said:
I think I'll wait until you try getting decryption working. I have a had many fights with that beast lol
Click to expand...
Click to collapse
Have any good resources you can recommend?
Hi,
I tried to upgrade my US998 from Oreo to Pie using LGUP patched. The upgrade process went well until the phone restarted and have this error message:
"Your device has failed a routine safety check and will not boot..."
I did try using LG Bridge to fix = not working
I did try fastboot boot laf.img (using extracted laf from H93031a_00_OPEN_EU_OP_1105) not working.
Any other solution?
Thanks
This Post got recommended to me. I am a Samsung user so my answer will probably be very stupid.
If you have fastboot, why don't you flash a recovery and a custom rom? Ik stupid but it's the only thing that comes to my mind since i don't have a LG phone lol
JanBoyGamer23 said:
This Post got recommended to me. I am a Samsung user so my answer will probably be very stupid.
If you have fastboot, why don't you flash a recovery and a custom rom? Ik stupid but it's the only thing that comes to my mind since i don't have a LG phone lol
Click to expand...
Click to collapse
Installing TWRP or any recovery wont work for me. The bootloader still locked thou.
jaacoozee said:
Installing TWRP or any recovery wont work for me. The bootloader still locked thou.
Click to expand...
Click to collapse
Is that "Download mode" the same as the Samsung one? How do you NORMALLY access it?
JanBoyGamer23 said:
Is that "Download mode" the same as the Samsung one? How do you NORMALLY access it?
Click to expand...
Click to collapse
I'm not sure. Normally I access download mode using volume up and power button. The download mode was there for a sec and then the screen back to
"Your device has failed a routine safety check and will not boot..."
again.
Ah ok so now I understand.
But why don't you unlock your bootloader then if fastboot works? Do you know for sure that TWRP doesn't work?
I really want to help but I don't have a LG phone
JanBoyGamer23 said:
Ah ok so now I understand.
But why don't you unlock your bootloader then if fastboot works? Do you know for sure that TWRP doesn't work?
I really want to help but I don't have a LG phone
Click to expand...
Click to collapse
EDIT: The LG Bootloader unlocking page is "under construction". Guess you have to bring your phone to LG for them to fix this...
JanBoyGamer23 said:
EDIT: The LG Bootloader unlocking page is "under construction". Guess you have to bring your phone to LG for them to fix this...
Click to expand...
Click to collapse
Unfortunately my LG V30 is US region. The official bootloader site not support my phone. Thanks for your info anyway
I'm not sure why a Samsung user was recommended this post. And no offense to the Samsung user, but the process for unlocking, etc is VERY different for Samsung than it is for LG... so I recommend not worrying about that. Believe me, I know, because I'm researching switching to a Samsung in the future, and the process is very different!
That being said, the best resource here is the WTF thread with the post by ChazzMatt. That post has everything you need in one place.
jacoozie, the error you're getting indicates that you had a non-stock phone when you flashed the KDZ on an unlocked phone. For this reason, it's no surprise you got this error - the phone must be COMPLETELY STOCK for a stock KDZ flash. I'm guessing you had TWRP or something else installed, which is causing this problem. Once you unlock, you cannot just flash things willy nilly... and generally you don't flash with KDZ unless you're trying to change models (aka Frankenstein) or on the way to a custom ROM.
It sounds like you've done some unlocking rooting... if so, I recommend you start over with the WTF thread, read it VERY CAREFULLY and ENTIRELY and then reflash as instructed there. I'm guessing you may need to go back to KDZ Nougat and then work your way forward. If you have questions, ask in that thread... but you shouldn't have any questions as the thread is VERY complete (been updated all the time with very detailed information, so everything is in there).
schwinn8 said:
I'm not sure why a Samsung user was recommended this post. And no offense to the Samsung user, but the process for unlocking, etc is VERY different for Samsung than it is for LG... so I recommend not worrying about that. Believe me, I know, because I'm researching switching to a Samsung in the future, and the process is very different!
That being said, the best resource here is the WTF thread with the post by ChazzMatt. That post has everything you need in one place.
jacoozie, the error you're getting indicates that you had a non-stock phone when you flashed the KDZ on an unlocked phone. For this reason, it's no surprise you got this error - the phone must be COMPLETELY STOCK for a stock KDZ flash. I'm guessing you had TWRP or something else installed, which is causing this problem. Once you unlock, you cannot just flash things willy nilly... and generally you don't flash with KDZ unless you're trying to change models (aka Frankenstein) or on the way to a custom ROM.
It sounds like you've done some unlocking rooting... if so, I recommend you start over with the WTF thread, read it VERY CAREFULLY and ENTIRELY and then reflash as instructed there. I'm guessing you may need to go back to KDZ Nougat and then work your way forward. If you have questions, ask in that thread... but you shouldn't have any questions as the thread is VERY complete (been updated all the time with very detailed information, so everything is in there).
Click to expand...
Click to collapse
Thanks for the reply.
I didnt install TWRP or any recovery tools to my phone. My phone bootloader still locked thou.
I have read the WTF thread but the problem is I cant get into my Download mode.
Ok, what steps are you using to try to get into download mode? Presumably turning off the phone, then holding the volume up button and plugging in the USB cable (other end already connected to a Windows computer), correct? If that doesn't work, can you try other USB cables? Sometimes a bad cable could prevent the phone from going into download mode.
i updated to android 12, without any modifications prior, is it possible to root this phone still? or is there no root method for android 12 yet? i've been curious on rooting it for a little while now.
texas7412 said:
i updated to android 12, without any modifications prior, is it possible to root this phone still? or is there no root method for android 12 yet? i've been curious on rooting it for a little while now.
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/v60-bootloader-unlock-and-magisk-root.4358785/ Reports are saying it works fine.
surgemanx said:
https://forum.xda-developers.com/t/v60-bootloader-unlock-and-magisk-root.4358785/ Reports are saying it works fine.
Click to expand...
Click to collapse
Thank you! I hope it works fine for me.. i don't really want to kill my phone Lol i've had a lot of experience with rooting and unbricking phones, but i'm still a bit on edge especially with this one given its price compared to like $50 or less i've paid for others Haha
texas7412 said:
Thank you! I hope it works fine for me.. i don't really want to kill my phone Lol i've had a lot of experience with rooting and unbricking phones, but i'm still a bit on edge especially with this one given its price compared to like $50 or less i've paid for others Haha
Click to expand...
Click to collapse
We have the firehose for the V60!The possibilities are endless..lol..
surgemanx said:
We have the firehose for the V60!The possibilities are endless..lol..
Click to expand...
Click to collapse
i hate to say it.. but the tutorial isn't working for me in qfil it tells me "Please make sure you have selected the correct programmer in flat build page" i rebooted it into the 9008 mode 10-20 times now and it hasn't worked..
texas7412 said:
i hate to say it.. but the tutorial isn't working for me in qfil it tells me "Please make sure you have selected the correct programmer in flat build page" i rebooted it into the 9008 mode 10-20 times now and it hasn't worked..
Click to expand...
Click to collapse
Here,try this one.I just used it not even 10 minutes ago to make a full LUNS back up of a V60 I have laying on my desk.I'm actually using LUNS backups to crossflash other carrier V60's with AT&T software so the VoLTE works.
Edit:Oh,make sure you choose flat build.Then choose this firehose.
surgemanx said:
Here,try this one.I just used it not even 10 minutes ago to make a full LUNS back up of a V60 I have laying on my desk.I'm actually using LUNS backups to crossflash other carrier V60's with AT&T software so the VoLTE works.
Edit:Oh,make sure you choose flat build.Then choose this firehose.
Click to expand...
Click to collapse
this was certainly an interesting experience, i could unlock the bootloader, but doing it via the file thing provided it won't work, going to fastboot and doing fastboot oem unlock, then booting into a twrp recovery and flashing magisk v24.3, it bricked the OS and i had to fight to get it to boot, twrp broke and is locked it refuses to unlock, it gave me an odd looking recovery mode as if it was from android kitkat or something (thats the best i can describe it, it looked much different from the other recovery to wipe) and it said it couldn't boot android and it said to factory reset, so i did.. it downgraded me to android 11 and now its rooted but i can't update to android 12 now because of it being rooted? is there a way to update to 12 now?
texas7412 said:
this was certainly an interesting experience, i could unlock the bootloader, but doing it via the file thing provided it won't work, going to fastboot and doing fastboot oem unlock, then booting into a twrp recovery and flashing magisk v24.3, it bricked the OS and i had to fight to get it to boot, twrp broke and is locked it refuses to unlock, it gave me an odd looking recovery mode as if it was from android kitkat or something (thats the best i can describe it, it looked much different from the other recovery to wipe) and it said it couldn't boot android and it said to factory reset, so i did.. it downgraded me to android 11 and now its rooted but i can't update to android 12 now because of it being rooted? is there a way to update to 12 now?
Click to expand...
Click to collapse
Afraid not because OTA updates will look for rooted or bootloader unlocked devices and will normally give you a white screen error code.Nature of the beast I guess you could say.If you don't plan on doing a custom rom or trying to remove OEM software it's not really worth it honestly.
surgemanx said:
Afraid not because OTA updates will look for rooted or bootloader unlocked devices and will normally give you a white screen error code.Nature of the beast I guess you could say.If you don't plan on doing a custom rom or trying to remove OEM software it's not really worth it honestly.
Click to expand...
Click to collapse
Ahh okay. Thanks though! Do you know why it would have downgraded from 12 to 11 though? that doesn't really make any sense to me.. why did rooting downgrade without me installing an older system or anything like that?
texas7412 said:
Thank you! I hope it works fine for me.. i don't really want to kill my phone Lol i've had a lot of experience with rooting and unbricking phones, but i'm still a bit on edge especially with this one given its price compared to like $50 or less i've paid for others Haha
Click to expand...
Click to collapse
Think about it this way, a V60 with a broken screen is less than 100 bucks. If you brick it, you can fix it for far less than bricking any other phone in a similar class.
texas7412 said:
Ahh okay. Thanks though! Do you know why it would have downgraded from 12 to 11 though? that doesn't really make any sense to me.. why did rooting downgrade without me installing an older system or anything like that?
Click to expand...
Click to collapse
Now,that's an odd one.My thoughts would be because of the engineering bootloader that's written for unlocking purposes?Are you sure it was A12 to begin with?lol..
pflatlyne said:
Think about it this way, a V60 with a broken screen is less than 100 bucks. If you brick it, you can fix it for far less than bricking any other phone in a similar class.
Click to expand...
Click to collapse
And this is very true!The V60 was way ahead of it's time!It's a shame LG devices were never marketed properly and supported on a local retail level like they should have been.And even if you did brick them,worst thing would be peeling the back off and hitting the testpoint to bring it back to life.
surgemanx said:
Now,that's an odd one.My thoughts would be because of the engineering bootloader that's written for unlocking purposes?Are you sure it was A12 to begin with?lol..
Click to expand...
Click to collapse
Yes! I was so excited that i got 12 on it, the bootloader shows its android 12 though.. which is really confusing to me.. is there any chance there's an android 12 kdz for this phone floating around that i could try to root and flash? i'm kind of regretting it now, i can't get the fingerprint scanner working following the tutorial there.. i can't update to 12 again it just fails to download, my recovery mode is gone, i can't get back into the bootloader/fastboot mode only EDL mode but it won't recognize anything within windows, adb won't work nor fastboot, can i recover it still if i wish to go back to stock?
The good news is, it gets much better benchmark scores and is much much faster..
on geekbench, 1688 single core, 6203 multicore, it had a higher score but said it was invalid? that one was 4067 single core, 15601 multicore
antutu, it scored 695755 with just using kernel auditor and maxing out the cpu freq and setting gpu freq to 870mhz.
Edit: I just remembered, for where you mentioned the bootloader, i don't have the engineering one installed. i never got that far to even install it. just android debugging > oem unlock > fastboot > fastboot oem unlock
texas7412 said:
Yes! I was so excited that i got 12 on it, the bootloader shows its android 12 though.. which is really confusing to me.. is there any chance there's an android 12 kdz for this phone floating around that i could try to root and flash? i'm kind of regretting it now, i can't get the fingerprint scanner working following the tutorial there.. i can't update to 12 again it just fails to download, my recovery mode is gone, i can't get back into the bootloader/fastboot mode only EDL mode but it won't recognize anything within windows, adb won't work nor fastboot, can i recover it still if i wish to go back to stock?
The good news is, it gets much better benchmark scores and is much much faster..
on geekbench, 1688 single core, 6203 multicore, it had a higher score but said it was invalid? that one was 4067 single core, 15601 multicore
antutu, it scored 695755 with just using kernel auditor and maxing out the cpu freq and setting gpu freq to 870mhz.
Edit: I just remembered, for where you mentioned the bootloader, i don't have the engineering one installed. i never got that far to even install it. just android debugging > oem unlock > fastboot > fastboot oem unlock
Click to expand...
Click to collapse
That depends on what model of V60 you have?Most of the kdz files for Verizon or T-Mobile can be found at the link below.AT&T or Sprint no kdz's to be found except back up Qfil copies I have found.Take a look,and LGUP it if you find the firmware you want.Most will be A11 and you can just OTA back to A12 with no problem.
Models - LG-Firmwares.com
Free archive of LG firmwares. Comparison of features and reviews of all mobile devices. Quick download of updates for your device.
lg-firmwares.com
surgemanx said:
That depends on what model of V60 you have?Most of the kdz files for Verizon or T-Mobile can be found at the link below.AT&T or Sprint no kdz's to be found except back up Qfil copies I have found.Take a look,and LGUP it if you find the firmware you want.Most will be A11 and you can just OTA back to A12 with no problem.
Models - LG-Firmwares.com
Free archive of LG firmwares. Comparison of features and reviews of all mobile devices. Quick download of updates for your device.
lg-firmwares.com
Click to expand...
Click to collapse
okay good! Thank you! Is there any chance of a android 12 KDZ for the t-mobile variant? and if i flash back an original KDZ, will i have to wipe everything again? Thanks.
texas7412 said:
okay good! Thank you! Is there any chance of a android 12 KDZ for the t-mobile variant? and if i flash back an original KDZ, will i have to wipe everything again? Thanks.
Click to expand...
Click to collapse
If you refurb it with LGUP it will wipe it all.The T-Mobile model has A12,but no physical kdz as of yet.So,you'll have to OTA back to A12 once you set it all back up.
surgemanx said:
If you refurb it with LGUP it will wipe it all.The T-Mobile model has A12,but no physical kdz as of yet.So,you'll have to OTA back to A12 once you set it all back up.
Click to expand...
Click to collapse
do i have to refurb to go back to stock, or can i do it via the upgrade option? Sorry if i'm being bothersome lol
surgemanx said:
If you refurb it with LGUP it will wipe it all.The T-Mobile model has A12,but no physical kdz as of yet.So,you'll have to OTA back to A12 once you set it all back up.
Click to expand...
Click to collapse
HEY! SO I FLASHED THE STOCK BOOT A AND BOOT B AND THEN IT LET ME UPDATE TO 12!
i let the update do its thing, reflashed TWRP and then flashed the patched boot a and b, now i have a rooted android 12. WOOHOO!
texas7412 said:
HEY! SO I FLASHED THE STOCK BOOT A AND BOOT B AND THEN IT LET ME UPDATE TO 12!
i let the update do its thing, reflashed TWRP and then flashed the patched boot a and b, now i have a rooted android 12. WOOHOO!
Click to expand...
Click to collapse
Yes,that wil work until the next update.If it's modified when the next OTA hits,it will give you the update error.Basically,you just set it back stock and the update works.But,glad you have it worked out.