Related
Hey guys!!
I've been asked quite a few times, how to install the newest ROM for the GNex, the easiest way...
I've just tried it a few minutes ago, so I can tell you, waht it did and how to do it
Step 1:
Well, first things first;
you need the drivers. You'll want to download them from: here
Now, you need to download following file: Samsung official ROM
Step 2:
After you have downloaded both files and have installed the drivers, extract the firmware to a location, you can remember
eg.: %userprofile%\Downloads
Put the phone in Odin mode. Via USB Jig or VOL. DWN. + PWR. BTTN.
Once in Odin mode, plug phone in to computer via USB cable, wait for the drivers to install and then open the program. It may take up to 30 secs. to recognize the phone. Then click start. The flash process will take up to 3 Mins and will relock the bootloader, should you have unlocked it.
Final:
now just set your phone up and wait about five minutes, for the update notification to pop up... Now, everything is done, your phone is completely back to stock and nobody can tell you've messed around with it ^^
Though my personal favourite way of doing this, is with my root helper, but never mind about that (Click here to take a peek )
I hope you had fun doing this, I also hope you check out the 3rd link and I very much hope, I could teach you a bit more about the GNex ^_^
I am trying to follow your instructions but they do not work. After starting the drivers install, windows says it's installing drivers and then nothing happens.
Don't use ODIN. Follow any of the stickies at the top of the section on setting up adb and fastboot then flashing a factory build from there.
What xobx said
Sent from my Galaxy Nexus using Tapatalk 2
I've used both Odin and fastboot-method and have never had any single issue with them. Both works fine. If you have time to create tar packages everytime new factory image shows I don't see a reason why I should discourage you from using this tool.
m.kochan10 said:
I've used both Odin and fastboot-method and have never had any single issue with them. Both works fine. If you have time to create tar packages everytime new factory image shows I don't see a reason why I should discourage you from using this tool.
Click to expand...
Click to collapse
Because its a Samsung rather than Android tool and this is a Nexus device.
063_XOBX said:
Because its a Samsung rather than Android tool and this is a Nexus device.
Click to expand...
Click to collapse
And an unsupported tool, at that.
Sent from my Nexus
063_XOBX said:
Because its a Samsung rather than Android tool and this is a Nexus device.
Click to expand...
Click to collapse
Of course but when you reboot your Nexus into Odin/download mode it's technically no longer google's unique developer phone but it becomes a regular Samsung handset (with no download counter though). GNex is equipped with Odin mode not without a reason. This means manufacturer left the door open to use Odin flash as an alternative method. Of course it's not officially recommended but as long as it works fine as a second method I've got nothing against it. The more important here is whether odin flash is a safe and effective method. According to my experience.... it is. I mean I wouldn't recommend it as a primary method, but It's always good to know you have options just in case...
I use fastboot when I am on MacOS (definitely more often) and Odin whenever I flash firmware using Windows.
---------- Post added at 06:37 PM ---------- Previous post was at 06:09 PM ----------
bk201doesntexist said:
And an unsupported tool, at that.
Sent from my Nexus
Click to expand...
Click to collapse
Excuse me, not trying to be sarcastic but unsupported by who?
.... seriously?
Not supported by anyone actually: Google, Samsung, not even the community.
Sent from my Nexus
bk201doesntexist said:
.... seriously?
Not supported by anyone actually: Google, Samsung, not even the community.
Sent from my Nexus
Click to expand...
Click to collapse
Oh that's what you meant. Sure. Well It's kinda obvious that u use it at your own risk just like rooting or flashing anything to your device. I think that everybody is aware of that including OP. No intention to sound ignorant or impolite but this lack of official support is irrelevant for me. If I brick my handset using Odin, cwm, RUU or fastboot it's only me to blame.
m.kochan10 said:
Oh that's what you meant. Sure. Well It's kinda obvious that u use it at your own risk just like rooting or flashing anything to your device. I think that everybody is aware of that including OP. No intention to sound ignorant or impolite but this lack of official support is irrelevant for me. If I brick my handset using Odin, cwm, RUU or fastboot it's only me to blame.
Click to expand...
Click to collapse
Doesn't mean you should recommend that somebody use what is, frankly, an inferior tool. Even a toolkit (I just threw up in my mouth a little) is better than ODIN.
Thing is, if I flash through Odin, I can't say I did, either to Google or Samsung. They will reply that the official tool to reset device to factory state is fastboot. There's not even a mention to download mode. Its a leaked tool, the only way I see Odin as an option is if fastboot isn't available. And even then, I would rather use either Heimdall (which i don't believe supports our device) or OMAPflash.
Sent from my Nexus
No no, as I posted earlier, the primary tool is of course fastboot. It's not like I recommend using Odin. I'm just not a big opponent cos I've never had any bad experiences using it and thus I don't understand this (forgive me expression) fear of using it. If anybody asks me I recommend fastboot at the first place. (It takes even more time to create tar.md5 package in cygwin than to flash every single .img via terminal to be honest) But sometimes people can only enter odin mode using usb jig. Then odin flash seems to be the one and only option.
---------- Post added at 10:15 PM ---------- Previous post was at 10:05 PM ----------
bk201doesntexist said:
Thing is, if I flash through Odin, I can't say I did, either to Google or Samsung. They will reply that the official tool to reset device to factory state is fastboot. There's not even a mention to download mode. Its a leaked tool, the only way I see Odin as an option is if fastboot isn't available. And even then, I would rather use either Heimdall (which i don't believe supports our device) or OMAPflash.
Sent from my Nexus
Click to expand...
Click to collapse
I am not really proud of myself but why would you care about google or samsung, like honestly ? None of them will ever recognize the difference if you send your brick to their service center anyway ...and Heimdall is even less stable than Odin.
BTW. Did any of you notice that Odin flash unlocks your bootloader?
hello guys
need yout help, tried searching google for sulotion but came up empty.
ive rooted the lg g4 h815(android 6.0-V20c-SEA) before via iroot pc but after factory reset its returned to be unrooted.
when i try to root again its keep failing because of debugging issue (the software keep telling me its not in debugging altough it is)
i think the problem is when i do usb debugging - connecting to pc the option is checked in the check box but it turns gray.whats the problem is? how can i fix it ?
thank you in advance
If you mean the USB debugging option is checked but gray when your phone is plugged in, that is normal, you cannot change that option when you're plugged in via usb.
I'm not familiar with iroot personally, I could take a look if you need though, but maybe revoke usb debugging authorizations through dev options then accept the pc's key fingerprint once again to "kickstart" iroot.
If you've rooted before through iroot on the same software version you're on now, it should work again without too much effort. Also maybe try switching to MTP (Media Sync) or PTP (Camera sync), or between the both until something happens.
That's all I can think of ATM, I'll probably go check out iroot right now, and think a little more and come back, but I wanted to give you a quick enough response. I wish you the best of luck though!
Edit: Forgot to mention that sometimes SuperSU may get uninstalled from factory reset, if the the G4 Factory Reset protocol deletes the system partition, and then reinstalls it, then this would explain why/if you lost root, I do not know if that's the protocol though. If iroot roots and injects SuperSU as the root manager, try reinstalling it possibly.. unless you are 100% positive you are somehow completely unrooted. (Use a root checker to check if you still got it)
I recommend wiping Data, Cache and Dalvik from TWRP next time, if that's not what you did this time. :good:
Williquah said:
If you mean the USB debugging option is checked but gray when your phone is plugged in, that is normal, you cannot change that option when you're plugged in via usb.
I'm not familiar with iroot personally, I could take a look if you need though, but maybe revoke usb debugging authorizations through dev options then accept the pc's key fingerprint once again to "kickstart" iroot.
If you've rooted before through iroot on the same software version you're on now, it should work again without too much effort. Also maybe try switching to MTP (Media Sync) or PTP (Camera sync), or between the both until something happens.
That's all I can think of ATM, I'll probably go check out iroot right now, and think a little more and come back, but I wanted to give you a quick enough response. I wish you the best of luck though!
Edit: Forgot to mention that sometimes SuperSU may get uninstalled from factory reset, although I've never heard of that, if iroot roots and injects SuperSU as the root manager, try reinstalling it possibly.. unless you are 100% positive you are somehow completely unrooted. (Use a root checker to check if you still got it)
Click to expand...
Click to collapse
thank you for the quick response...
I tried the revoking and debugging again - but nothing.
i will try the mtp ptp thing (when i get home after work)
and will love to hear from you if you have another solution but thank you so much
mikmikush said:
thank you for the quick response...
I tried the revoking and debugging again - but nothing.
i will try the mtp ptp thing (when i get home after work)
and will love to hear from you if you have another solution but thank you so much
Click to expand...
Click to collapse
No problem at all, I really do hope to fix this for you. Are you on the same software version as you were when you first rooted?/Which version is that?
Another thing I thought of, is your computer. Is it the same one that you used the first time? Do you have full admin access on it? Do you have all the LG drivers on it?
Do you have ADB/Fastboot fully installed on it? Obviously these are the first things you probably think about when you think about root, but I'm just making sure nothing is slipping by, you know?
Depending on what software version you're on, maybe we should try another root method if nothing works.
The last thing I'd say is to backup all your data/internal and flash the firmware you want to root on, but I really don't think we need to go that far.
P.S. I own a VS986 (VZW version of the G4) so I can only go to certain extents to reproduce/"debug" the problem you are having. Keep me updated!
Williquah said:
No problem at all, I really do hope to fix this for you. Are you on the same software version as you were when you first rooted?/Which version is that?
Another thing I thought of, is your computer. Is it the same one that you used the first time? Do you have full admin access on it? Do you have all the LG drivers on it?
Do you have ADB/Fastboot fully installed on it? Obviously these are the first things you probably think about when you think about root, but I'm just making sure nothing is slipping by, you know?
Depending on what software version you're on, maybe we should try another root method if nothing works.
The last thing I'd say is to backup all your data/internal and flash the firmware you want to root on, but I really don't think we need to go that far.
P.S. I own a VS986 (VZW version of the G4) so I can only go to certain extents to reproduce/"debug" the problem you are having. Keep me updated!
Click to expand...
Click to collapse
ok step by step
model number h815
I rooted it a year ago or so , but i dont remember which pc (mine or my perents) and or version (mom's phone now its papa's ).
I would love to install international rom but since i bricked my note 4 years ago(don't judge was 16 years old girl without pation and expirience ) and just succsedd installing a new rom with my mate 8 , im afraid and still searching a suitable rom.
the drivers installed and it says that ADB/Fastboot fully installed on it (i will duoble check it when i get home )
all the data is backed up from papa's galaxy s5 hench the factory restart (we all moved from one phone to another haha)
sorry for any lang mistakes and for the long response
About phone ????
mikmikush said:
ok step by step
model number h815
I rooted it a year ago or so , but i dont remember which pc (mine or my perents) and or version (mom's phone now its papa's ).
I would love to install international rom but since i bricked my note 4 years ago(don't judge was 16 years old girl without pation and expirience ) and just succsedd installing a new rom with my mate 8 , im afraid and still searching a suitable rom.
the drivers installed and it says that ADB/Fastboot fully installed on it (i will duoble check it when i get home )
all the data is backed up from papa's galaxy s5 hench the factory restart (we all moved from one phone to another haha)
sorry for any lang mistakes and for the long response
Click to expand...
Click to collapse
Sorry for forgetting the whole reason you're in this problem is because of a factory reset lol, of course you have your data backed up. And trust me, I understand about the brick, I really messed up my G3 2 years back. Thanks also for the device pictures, could you post a shot of "About Phone=>>Software Info". That would be great!
Funny thing I just did that same phone rotation thing very recently XD
Lol love rotation, here
mikmikush said:
Click to expand...
Click to collapse
Well, it seems that the factory reset must also have deleted the system partition, then reinstalled it with the most updated version.. which is not good for the current situation.
Notice Security Patch Level is "2016-01-01" and you're running Android M 6.0, means that the software you're on is very recent, if not the most recent. I did some looking around just now, but I couldn't turn up anything that achieved successful root on "V20c-SEA-XX", which is what you would need.
Technically you could try the stock firmware KDZ for your device, which should be 5.1.1, then flash it with like LGUP, but I seriously don't recommend that unless you find a thread that confirms a working downgrade from V20c-SEA, because if the qfuse does not match between firmware versions, you could easily end up with a hardbrick.
Here is the link to your stock firmware, in case you find that it is safe to downgrade from 20c-SEA to 10b-SEA:
http://storagecow.eu/index.php?dir=Xda/LG+G4/H815/
You could try this: http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS
I'm not sure it will work, but I can't imagine it'd harm you, since it's LG official.
You could also try to fill the checkbox "OEM Unlock", and then try to unlock the bootloader via fastboot. I am not sure if this could possibly cause harm if it does not work properly, so try this at your own risk.: http://oneplus.wonderhowto.com/how-...all-custom-recovery-root-oneplus-one-0156099/ (It's all the same commands even though it says for OnePlus One device. If you happen to unlock the bootloader using fastboot, do not go on to Step 2 on that page)
If nothing works, you could subscribe to this thread: http://forum.xda-developers.com/g4/help/rooting-h815-v20c-sea-xx-t3371107
Or these may be helpful at some point: https://www.reddit.com/r/lgg4/comments/4dk9xt/lg_g4_h815_sea_v10e_kdz/
http://forum.xda-developers.com/g4/general/finally-h815-v10c-sea-xx-t3211920
https://www.reddit.com/r/AndroidQue...rading_lg_g4_h815_sea_with_locked_bootloader/
https://www.reddit.com/r/lgg4/comments/4aa1pi/root_question_h815_v20cseaxx/
http://forum.xda-developers.com/sitesearch.php?q=H815 V20c-SEA
Here's the LGUP software if you ever need: http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
I know alot of the links and such you can do by yourself, and may not be super helpful yet, but it should give you the information you need. And if root is not achievable yet on your software version, be patient, even on Marshmallow devices are being rooted even with locked bootloaders.
I apologize for such a long wait time + post! I wish you good luck again! :good:
P.S. You should include your current software version in your OP (Android 6.0 - V20c-SEA) so people more knowledgeable than I may be able to help you even more.
Williquah said:
Well, it seems that the factory reset must also have deleted the system partition, then reinstalled it with the most updated version.. which is not good for the current situation.
Notice Security Patch Level is "2016-01-01" and you're running Android M 6.0, means that the software you're on is very recent, if not the most recent. I did some looking around just now, but I couldn't turn up anything that achieved successful root on "V20c-SEA-XX", which is what you would need.
Technically you could try the stock firmware KDZ for your device, which should be 5.1.1, then flash it with like LGUP, but I seriously don't recommend that unless you find a thread that confirms a working downgrade from V20c-SEA, because if the qfuse does not match between firmware versions, you could easily end up with a hardbrick.
Here is the link to your stock firmware, in case you find that it is safe to downgrade from 20c-SEA to 10b-SEA:
http://storagecow.eu/index.php?dir=Xda/LG+G4/H815/
You could try this: http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS
I'm not sure it will work, but I can't imagine it'd harm you, since it's LG official.
You could also try to fill the checkbox "OEM Unlock", and then try to unlock the bootloader via fastboot. I am not sure if this could possibly cause harm if it does not work properly, so try this at your own risk.: http://oneplus.wonderhowto.com/how-...all-custom-recovery-root-oneplus-one-0156099/ (It's all the same commands even though it says for OnePlus One device. If you happen to unlock the bootloader using fastboot, do not go on to Step 2 on that page)
If nothing works, you could subscribe to this thread: http://forum.xda-developers.com/g4/help/rooting-h815-v20c-sea-xx-t3371107
Or these may be helpful at some point: https://www.reddit.com/r/lgg4/comments/4dk9xt/lg_g4_h815_sea_v10e_kdz/
http://forum.xda-developers.com/g4/general/finally-h815-v10c-sea-xx-t3211920
https://www.reddit.com/r/AndroidQue...rading_lg_g4_h815_sea_with_locked_bootloader/
https://www.reddit.com/r/lgg4/comments/4aa1pi/root_question_h815_v20cseaxx/
http://forum.xda-developers.com/sitesearch.php?q=H815 V20c-SEA
Here's the LGUP software if you ever need: http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
I know alot of the links and such you can do by yourself, and may not be super helpful yet, but it should give you the information you need. And if root is not achievable yet on your software version, be patient, even on Marshmallow devices are being rooted even with locked bootloaders.
I apologize for such a long wait time + post! I wish you good luck again! :good:
P.S. You should include your current software version in your OP (Android 6.0 - V20c-SEA) so people more knowledgeable than I may be able to help you even more.
Click to expand...
Click to collapse
Thank you thank you! You are awesome.
I will follow the links later and reply ...
I will ???? thank you
@mikmikush You're welcome, my pleasure!
Williquah said:
@mikmikush You're welcome, my pleasure!
Click to expand...
Click to collapse
ok
i think i find the problem- the adb is not working
i followed to unlock bootloader of lg, { https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS }
and when do this step:
"Enter your phone’s unique Device ID. You can view the Device ID by connecting your phone to the PC using a USB cable and entering "adb reboot bootloader" in DOS command window of the folder you created in previous step (for example: C:\tools). Your phone will reboot into the fastboot mode. Enter "fastboot oem device-id" in DOS command window."
it says failed to start daemon - error cannot connect to daemon.....
and i cant trace lg id.
any sugestion?
mikmikush said:
ok
i think i find the problem- the adb is not working
i followed to unlock bootloader of lg, { https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS }
and when do this step:
"Enter your phone’s unique Device ID. You can view the Device ID by connecting your phone to the PC using a USB cable and entering "adb reboot bootloader" in DOS command window of the folder you created in previous step (for example: C:\tools). Your phone will reboot into the fastboot mode. Enter "fastboot oem device-id" in DOS command window."
it says failed to start daemon - error cannot connect to daemon.....
and i cant trace lg id.
any sugestion?
Click to expand...
Click to collapse
I have SEA device too, not being able to be unlocked via LG's official bootloader unlock tutorial
CrazyLegenD said:
I have SEA device too, not being able to be unlocked via LG's official bootloader unlock tutorial
Click to expand...
Click to collapse
its like my problem?
what did u do?
mikmikush said:
ok
i think i find the problem- the adb is not working
i followed to unlock bootloader of lg, { https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS }
and when do this step:
"Enter your phone’s unique Device ID. You can view the Device ID by connecting your phone to the PC using a USB cable and entering "adb reboot bootloader" in DOS command window of the folder you created in previous step (for example: C:\tools). Your phone will reboot into the fastboot mode. Enter "fastboot oem device-id" in DOS command window."
it says failed to start daemon - error cannot connect to daemon.....
and i cant trace lg id.
any sugestion?
Click to expand...
Click to collapse
Alright, so I guess it does have something to do with your adb. First off, check your Firewall, make sure you allow adb through and out your Firewall, also maybe temporarily disable your Antivirus whilst using adb, or allow a connection through it if you can. Try turning off USB Tethering through your G4. Try going to Task Manager and ending the adb process tree, it should then try to restart itself. Don't use a wireless adb connection.. if you were trying that, although I didn't think you were.
In "short" order,
1. I would firstly suggest allowing access through your firewall/antivirus, or really I would disable both for now just in case
2. Then try killing the adb process tree in Task Manager
3. Try the adb commands: "kill-server", "start-server"
4. Install any device driver you would possibly need
5. Reinstall adb and fastboot, maybe just install entire SDK-Tools package if you don't have it already
-- If adb is not recognizing your device, which is why you can't track your id, then you can simply enter "adb devices" and it will list your device whenever your error is fixed.
That's all I can think of ATM, I'll post this now but I'll still be thinking of other options. Let me know what happens. Fingers crossed.
(You are starting the command window in your adb directory right?)
---------- Post added at 07:39 AM ---------- Previous post was at 07:36 AM ----------
CrazyLegenD said:
I have SEA device too, not being able to be unlocked via LG's official bootloader unlock tutorial
Click to expand...
Click to collapse
H815 SEA?/Same software version and error?
Complete root guide for H815 EU http://forum.xda-developers.com/g4/general/howto-complete-guide-to-unlock-twrp-t3370003
htr5 said:
Complete root guide for H815 EU http://forum.xda-developers.com/g4/general/howto-complete-guide-to-unlock-twrp-t3370003
Click to expand...
Click to collapse
We're working on H815 SEA though.
Edit: Your guide is for EU v20d, she's on v20c on the SEA, do they use the same exact software? Is there a pending update for her?
Williquah said:
Alright, so I guess it does have something to do with your adb. First off, check your Firewall, make sure you allow adb through and out your Firewall, also maybe temporarily disable your Antivirus whilst using adb, or allow a connection through it if you can. Try turning off USB Tethering through your G4. Try going to Task Manager and ending the adb process tree, it should then try to restart itself. Don't use a wireless adb connection.. if you were trying that, although I didn't think you were.
In "short" order,
1. I would firstly suggest allowing access through your firewall/antivirus, or really I would disable both for now just in case
2. Then try killing the adb process tree in Task Manager
3. Try the adb commands: "kill-server", "start-server"
4. Install any device driver you would possibly need
5. Reinstall adb and fastboot, maybe just install entire SDK-Tools package if you don't have it already
-- If adb is not recognizing your device, which is why you can't track your id, then you can simply enter "adb devices" and it will list your device whenever your error is fixed.
That's all I can think of ATM, I'll post this now but I'll still be thinking of other options. Let me know what happens. Fingers crossed.
(You are starting the command window in your adb directory right?)
---------- Post added at 07:39 AM ---------- Previous post was at 07:36 AM ----------
H815 SEA?/Same software version and error?
Click to expand...
Click to collapse
Williquah said:
We're working on H815 SEA though.
Edit: Your guide is for EU v20d, she's on v20c on the SEA, do they use the same exact software? Is there a pending update for her?
Click to expand...
Click to collapse
i stopped the firewall and tried killing the adb process tree in Task Manager
done "kill-server", "start-server"
Install any device driver you would possibly need- i think i installed everything but im not sure though
done - Reinstall adb and fastboot, maybe just install entire SDK-Tools package
when i try adb devices - daemon fail
im frustrated
mikmikush said:
i stopped the firewall and tried killing the adb process tree in Task Manager
done "kill-server", "start-server"
Install any device driver you would possibly need- i think i installed everything but im not sure though
done - Reinstall adb and fastboot, maybe just install entire SDK-Tools package
when i try adb devices - daemon fail
im frustrated
Click to expand...
Click to collapse
Trust me, I understand your frustration, I'm going to make a guide for you in the next 6 hours or so.
Try a different computer if you can, I haven't had adb fail but many other tools sometimes work
on different computers for me. I've also heard "Dell PC Suite" should be uninstalled as it could cause adb hang ups,
if you have it. @htr5's guide might work for you if you have a software update available, I'm not sure though since it's not specifically for your device.
Regardless, I'm sure you will need to use adb soon, so we have to fix that.
I will try to make that guide asap, I obviously can only do so much, again, since I don't have your device, hopefully it will help though. I highly suggest trying on a fresh/different computer though.
Edit: Try USB 2.0 if you were using a 3.0 port (3.0 ports have the SS along with the usb "logo")
USB 2.0 is on the right:
"H815 SEA Root/General Guide"
@mikmikush
It does seem that you can treat your SEA device very similarly to the EU common version, in ways such as flashing KDZ's and rooting.
I cannot confirm this, but mentions in this thread: http://forum.xda-developers.com/g4/help/safe-root-h815-v10b-sea-variant-t3184152 make it seem like it should be okay.
Aoi_sora9x said:
I'm a SEA variant holder here.
It's fine, you can use the Low Effort Root method. You can also flash the EU open KDZ without any problem.
You lose VoLTE, but to me it doesn't matter so I don't really care.
I'm running the latest 10E ATM, and it's much much better than 10B, so flash away.
Click to expand...
Click to collapse
Yes, that post is for v10b, but it should also work for v20d/v20c. (Not the Low Effort Root method) - You will be working with EU software v20d.. while you are with SEA v20c,
so it's up to you if you want to try this, but it's the closest I can come right now. Thank @htr5 because I believe he has all of this in his guide, and I'll probably send you to his guide halfway through.
You may lose some features or brick your device by flashing firmware/software made for other devices. Trust your instinct!
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1. Install adb setup from here this includes necessary adb drivers, adb itself, and fastboot.
2. Install LG Mobile Driver
3. Download LGUP tool from here (This is for restoring your device to stock if you softbrick via KDZ)
Follow this thread if/when you need to.
4. Here contains a KDZ for EU v20C, which I'm 99.9% sure will match your current software, even though it says for EU.
5. Here contains every partition including the KDZ for 20d by @autoprime, which will be necessary if you decide to root from @htr5's guide (v20d Root Method)
6. Once again, try to unlock the bootloader officially through LG, if you are successful, you can follow @htr5's 20d Root Guide here
7. Be careful and let me know how it goes
@autoprime Mentions that there is "NO anti-rollback qfuse used in this update" (20d) so if you flash the 20d KDZ and it works, I believe you should then be able to downgrade successfully to an earlier firmware version - without worrying about qfuse - and root using a Lollipop (5.0/5.1) method if you can't get anywhere on Marshmallow (6.0). - This I'm not 100% positive about, again, but it is my thinking.
Please thank anyone I mentioned and anyone who's link I provided, they all deserve it!
just got my pixel xl today. unlocked the bootloader fine.
next step flash twrp. i fastboot boot twrp img. temp twrp , installed the zip.. i reboot to recovery. that where everything F up.. now i can not get into fastboot.. is there a way for me to get fastboot mode back ??
never mind just had to reboot the phone 3 times..
Hello. I think I am near you. I was on the latest stock 7.1.2 of may. Unlocked bootloader ok. Then boot the TWRP and flash the TWRP zip. After that I have bootloop all time. I can put the phone in bootloader but now my phone is not recognised by the computer. The first time I connected the phone he asked me what to do and I said transfers data. But now I cannot do anything.
How did you get in fastboot mode???
Any idea how to help me???
I really appreciate help!!
sytayeth said:
Hello. I think I am near you. I was on the latest stock 7.1.2 of may. Unlocked bootloader ok. Then boot the TWRP and flash the TWRP zip. After that I have bootloop all time. I can put the phone in bootloader but now my phone is not recognised by the computer. The first time I connected the phone he asked me what to do and I said transfers data. But now I cannot do anything.
How did you get in fastboot mode???
Any idea how to help me???
I really appreciate help!!
Click to expand...
Click to collapse
Hello,
You need to read this post: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
The thread contains a zip (verified boot signer v2 zip) that you must install right after you install the TWRP zip on latest May version...
This is weird your phone is not recognized while in bootloader.
Boot the bootloader and issue:
fastboot devices
Does it output your serial number in the command prompt?
Good luck...
5.1 said:
Hello,
You need to read this post: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
The thread contains a zip (verified boot signer v2 zip) that you must install right after you install the TWRP zip on latest May version...
This is weird your phone is not recognized while in bootloader.
Boot the bootloader and issue:
fastboot devices
Does it output your serial number in the command prompt?
Good luck...
Click to expand...
Click to collapse
Thank for your answer. The real problem was that in fastboot the phone is not recognised. There were no serial number. And I write in past because I could made it work.
I am very happy you worried about me. You have a new friend in Spain.
Thanks.
sytayeth said:
Thank for your answer. The real problem was that in fastboot the phone is not recognised. There were no serial number. And I write in past because I could made it work.
I am very happy you worried about me. You have a new friend in Spain.
Thanks.
Click to expand...
Click to collapse
Hey,
No problem. Glad you solved it by yourself anyway. What was the issue? Maybe others with the same problem could benefit from your experience?
Why your computer didn't recognized your phone while in bootloader?
Cheers...
5.1 said:
Hey,
No problem. Glad you solved it by yourself anyway. What was the issue? Maybe others with the same problem could benefit from your experience?
Why your computer didn't recognized your phone while in bootloader?
Cheers...
Click to expand...
Click to collapse
I really don't know the problem. I was just about to cry when I saw a post about skipsoft toolkit. And I thought why not to try. I installed that software in other pc, follow the instructions and now I am here again.
Yesssss!!!!
sytayeth said:
I really don't know the problem. I was just about to cry when I saw a post about skipsoft toolkit. And I thought why not to try. I installed that software in other pc, follow the instructions and now I am here again.
Yesssss!!!!
Click to expand...
Click to collapse
You shouldn't be modding you're device if you have to rely on a toolkit to save you. What if there wasn't a toolkit. You'd be SOL.
I highly recommend you learn how to use fastboot and adb, and do this stuff the right way. I'm not trying to be mean or anything. I just would hate to see you brick you're device. These pixel phones cost way too much to be screwing around with if you don't know what you're doing.
toknitup420 said:
You shouldn't be modding you're device if you have to rely on a toolkit to save you. What if there wasn't a toolkit. You'd be SOL.
I highly recommend you learn how to use fastboot and adb, and do this stuff the right way. I'm not trying to be mean or anything. I just would hate to see you brick you're device. These pixel phones cost way too much to be screwing around with if you don't know what you're doing.
Click to expand...
Click to collapse
Thanks. I am trying to learn. Not only fastboot or adb. English too. But sometimes I am a bit risky or only stupid.
By the way, recommend me a post or a place to learn.
sytayeth said:
Thanks. I am trying to learn. Not only fastboot or adb. English too. But sometimes I am a bit risky or only stupid.
By the way, recommend me a post or a place to learn.
Click to expand...
Click to collapse
Honestly the best way I found to learn adb and fastboot is YouTube. It's so much easier to watch how to do it. Thats how I learned. There's also @Heisenberg 6p guide. That can get you all setup for adb and fastboot too. It's very comprehensive.
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
toknitup420 said:
Honestly the best way I found to learn adb and fastboot is YouTube. It's so much easier to watch how to do it. Thats how I learned. There's also @Heisenberg 6p guide. That can get you all setup for adb and fastboot too. It's very comprehensive.
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thanks. I'll try.
Guys I need your help and I’m desperate to someone get me to the right dirrection.
I just got a pixel 2 xl, I unlock the bootloader and root with twrp. I try to install a lineage os rom with the gaps and it looks like everything when the well. I erase the cache and free I reboot it went back to the bootloader screen. From that point I have been spending all day trying to get back to factory or at least trying to install any other rom with out any luck. It someone can help me out I will be more than happy to send a Starbucks card or something. I just got the phone,
I forgot to mention that when I try to use the and side load it says something about the e drive, like if there es no drive on my phone
rectangularspace said:
Guys I need your help and I’m desperate to someone get me to the right dirrection.
I just got a pixel 2 xl, I unlock the bootloader and root with twrp. I try to install a lineage os rom with the gaps and it looks like everything when the well. I erase the cache and free I reboot it went back to the bootloader screen. From that point I have been spending all day trying to get back to factory or at least trying to install any other rom with out any luck. It someone can help me out I will be more than happy to send a Starbucks card or something. I just got the phone,
Click to expand...
Click to collapse
Do you know and understand how you use fastboot or the Deuces script to flash factory images to return you to stock OS?
Well not really. But I follow many instrucciones from differents post and nothing
rectangularspace said:
Well not really. But I follow many instrucciones from differents post and nothing
Click to expand...
Click to collapse
Read over this thread. Then let us know if you need help. https://forum.xda-developers.com/pi...de-reference-8x-oreo-to-t3826330/post77530335
Also, if you have twrp installed, you can flash the OTA zip that corresponds to your current OS version :good:
I do have twrp installed the problem is that I don’t have the zip on the phone to install the ota file.
Try with deceus Script (Just search for it) and select repair bootloop. It will download the factory Image and flash it on a and b partition then your phone will boot again. But your data will be lost :/
Ok., I will let you guys know thank you
Also, I forgot to mention that it looks like that I don’t have a OS installed ( twrp is telling me that every time i try to get out to the get out of the twrp menu. At this point i haven’t don’t anything mention in this post because I’m resetting my computer nd I’m installing right now the android sdk software.
You don't have to install the full Android SDK software for the job you're trying to do. You can download the latest Fastboot commands and ADB through Google, or even XDA(somewhere).
I've installed adb to my Windows commands, so once in recovery, when I need a file, I just "adb push file.zip /sdcard/".
No worries though. You'll be back up and running. ?
Edit: Also, if you still have data on your phone, you can check using the file explorer on TWRP. If you do, you can adb pull anything you want to keep.
@rectangularspace Link to the standalone platform tools HERE. This is all you need.
Guys. It's working now. I follow the instructions and when I execute the batch I notice that it was missing some files but it did worked, I was able to start over. One thing I notice is that play store was not updating the apps , I had to reboot a couple of times even force stop play store and it looks like is working. I was gonna ask, it's been a long time since I was in Android, if I decide to update to os 9 (pie) if I don't like it, can I downgrade to any previous OS?
rectangularspace said:
Guys. It's working now. I follow the instructions and when I execute the batch I notice that it was missing some files but it did worked, I was able to start over. One thing I notice is that play store was not updating the apps , I had to reboot a couple of times even force stop play store and it looks like is working. I was gonna ask, it's been a long time since I was in Android, if I decide to update to os 9 (pie) if I don't like it, can I downgrade to any previous OS?
Click to expand...
Click to collapse
Yes, but going down from 9 to 8 will cause/require a data wipe.
rectangularspace said:
Guys. It's working now. I follow the instructions and when I execute the batch I notice that it was missing some files but it did worked, I was able to start over. One thing I notice is that play store was not updating the apps , I had to reboot a couple of times even force stop play store and it looks like is working. I was gonna ask, it's been a long time since I was in Android, if I decide to update to os 9 (pie) if I don't like it, can I downgrade to any previous OS?
Click to expand...
Click to collapse
Why did you decide to install Oreo?? There will be no further security or functionality updates for 8.1. The next monthly update to Pie should be the first Monday of next month (October 1st) if you don't get a OTA nag before then.
I have the update available to install on my settings. But what I'm looking for is to start over on rooting my pixel 2 xl. But after last experience I'm a little conservative when it comes to mess with the phone. I'm reading right now the post where it says to do the critical unlock for the phone but I don't know witch bootloader version I have. Can you guys help me out
I have tmz10n version on my bootloader. It means that I need to do the critical unlock? By the way I did already unlock my bootloader and i Haven lock it again. And I think at some point when I was having trouble with my phone to put it back to run I did also the critical unlock process.
rectangularspace said:
I have tmz10n version on my bootloader. It means that I need to do the critical unlock? By the way I did already unlock my bootloader and i Haven lock it again. And I think at some point when I was having trouble with my phone to put it back to run I did also the critical unlock process.
Click to expand...
Click to collapse
You only need to do the unlock process one time, BUT there are two separate unlock commands which include unlock_critical. If in doubt you can use fastboot device-info or getvar to check the current status. Make sure you are using the latest version of the platform tools I linked to above. One word of caution... don't EVER re-lock your bootloader or you WILL run into problems. Even if you are returning the phone to Google for RMA you do not need to re-lock it.
My bad, after unlock my bootloader I haven't look back again. So it is unlock right now. Thank you for advised. For what I read the only way to unlock it it will be by running the command fastboot right? If I upgrade to pie using the upgrade available in my settings right now, it will not lock the bootloader right?
rectangularspace said:
My bad, after unlock my bootloader I haven't look back again. So it is unlock right now. Thank you for advised. For what I read the only way to unlock it it will be by running the command fastboot right? If I upgrade to pie using the upgrade available in my settings right now, it will not lock the bootloader right?
Click to expand...
Click to collapse
I meant the only way to lock the bootloader will be thru a fastboot command.
rectangularspace said:
I meant the only way to lock the bootloader will be thru a fastboot command.
Click to expand...
Click to collapse
Yes, once you have successfully unlocked the phone in fastboot using the two separate commands, you will never have to do it again, AND flashing anything will not re-lock the bootloader. Please read over Nathan's GUIDE HERE to confirm you have done this correctly (and completely). Once this is done you can flash OTA's , full Google images, custom roms, etc. Lastly, if you are properly unlocked you cannot brick your phone. No matter how bad it gets, you will always have a path to restore the phone to it's original state. Don't hesitate to take the OTA being offered on your phone. It will take you to 9.0 without losing data or locking anything. :good:
Hi guys,
Please help me out, is there any way I can recover from soft brick if I have a locked bootloader and usb debugging is turned off?
Can you get into fastboot and then factory recovery? If you can get there I believe you should be able to do a reset.
timothy009 said:
Hi guys,
Please help me out, is there any way I can recover from soft brick if I have a locked bootloader and usb debugging is turned off?
Click to expand...
Click to collapse
Try booting into recovery and then from your PC sideload the latest ota zip file.
Sent from my [device_name] using XDA-Developers Legacy app
Shouldn't it be necessary to have enabled USB debugging before?
timothy009 said:
Shouldn't it be necessary to have enabled USB debugging before?
Click to expand...
Click to collapse
No. Not while in recovery mode using the "update by adb" option.
This is the stock recovery we are talking about, right?
timothy009 said:
This is the stock recovery we are talking about, right?
Click to expand...
Click to collapse
Yes
Sent from my [device_name] using XDA-Developers Legacy app
Please help me. I have pixel 3 xl joining Q beta. When the setting is pressed, the device does not work. hang like picture. My device has not been unlocked when participating in the test.
spotmark said:
Can you get into fastboot and then factory recovery? If you can get there I believe you should be able to do a reset.
Click to expand...
Click to collapse
Currently the 3xl pixel is hanging so I can't unlock the bootloader pixel to flash the original rom.
nguyenmanh287 said:
Currently the 3xl pixel is hanging so I can't unlock the bootloader pixel to flash the original rom.
Click to expand...
Click to collapse
Google "rescue ota". You use a full OTA from the Google image page and from the stock recovery using the "apply update by adb" option to send the ota from your pc to the phone. Does not require an unlocked bootloader. Does require the latest adb/fastboot binaries on your pc. Directions are right there on Google's ota download page. Best of luck! :good:
v12xke said:
Google "rescue ota". You use a full OTA from the Google image page and from the stock recovery using the "apply update by adb" option to send the ota from your pc to the phone. Does not require an unlocked bootloader. Does require the latest adb/fastboot binaries on your pc. Directions are right there on Google's ota download page. Best of luck! :good:
Click to expand...
Click to collapse
Currently my 3xl pixels are dying. it has not been unlocked yet, so I cannot adb the original google rom
nguyenmanh287 said:
Currently my 3xl pixels are dying. it has not been unlocked yet, so I cannot adb the original google rom
Click to expand...
Click to collapse
I understand your first language is not English and I am trying to help you. Please try to parse/translate the information. You do NOT need an unlocked bootloader or USB debugging to use the ADB option in stock recovery mode using the full OTA image. In too many other threads you have never stated YES, I have a working stock recovery. If you have that, follow the instructions. Yes, you can flash a full OTA image in an attempt to rescue your P3XL even though your bootloader is locked. Otherwise please state you DO NOT have access to a stock recovery instead of cross posting to at least a half dozen threads "help me"! Too many posts from you and never enough information to help you.
Thank you very much. I will ask someone who speaks English to describe the whole situation so you know my PIXEL 3XL status.
---------- Post added at 02:35 AM ---------- Previous post was at 02:34 AM ----------
v12xke said:
I understand your first language is not English and I am trying to help you. Please try to parse/translate the information. You do NOT need an unlocked bootloader or USB debugging to use the ADB option in stock recovery mode using the full OTA image. In too many other threads you have never stated YES, I have a working stock recovery. If you have that, follow the instructions. Yes, you can flash a full OTA image in an attempt to rescue your P3XL even though your bootloader is locked. Otherwise please state you DO NOT have access to a stock recovery instead of cross posting to at least a half dozen threads "help me"! Too many posts from you and never enough information to help you.
Click to expand...
Click to collapse
Thank you very much. I will ask someone who speaks English to describe the whole situation so you know my PIXEL 3XL status.
v12xke said:
Google "rescue ota". You use a full OTA from the Google image page and from the stock recovery using the "apply update by adb" option to send the ota from your pc to the phone. Does not require an unlocked bootloader. Does require the latest adb/fastboot binaries on your pc. Directions are right there on Google's ota download page. Best of luck! :good:
Click to expand...
Click to collapse
Can you guide me specifically? did you tell facebook friends then i send pictures to you? help me?
This is my Facebook
https://www.facebook.com/NGUYENMANH287
nguyenmanh287 said:
Can you guide me specifically? did you tell facebook friends then i send pictures to you? help me?
This is my Facebook
https://www.facebook.com/NGUYENMANH287
Click to expand...
Click to collapse
The post you quoted, has the link to the OTA download page which contains the best instructions available. You can run that page through an online translator if necessary.
You have gotten the help you asked for. Now it's time for you to help yourself. You can take your device to someone more knowledgeable, who is in your area if you feel you can not follow the instructions on Google's page, but there is no further instruction that can be given here that will make this any easier for you.
v12xke said:
Google "rescue ota". You use a full OTA from the Google image page and from the stock recovery using the "apply update by adb" option to send the ota from your pc to the phone. Does not require an unlocked bootloader. Does require the latest adb/fastboot binaries on your pc. Directions are right there on Google's ota download page. Best of luck! :good:
Click to expand...
Click to collapse
v12xke said:
Google "rescue ota". You use a full OTA from the Google image page and from the stock recovery using the "apply update by adb" option to send the ota from your pc to the phone. Does not require an unlocked bootloader. Does require the latest adb/fastboot binaries on your pc. Directions are right there on Google's ota download page. Best of luck! :good:
Click to expand...
Click to collapse
I have the same issue described. My bootloop started with September Android 10 update. I already sideloaded October ota from Google website, and it updated without any problem. Still bootloop. I'm on a pixel 3xl 100% stock bootloader locked no root
movilserver said:
I have the same issue described. My bootloop started with September Android 10 update. I already sideloaded October ota from Google website, and it updated without any problem. Still bootloop. I'm on a pixel 3xl 100% stock bootloader locked no root
Click to expand...
Click to collapse
Not sure why you used the October image, but with a locked bootloader your only option is the rescue OTA. You could try a factory reset from recovery. If that doesn't (or did not) work, then try the December OTA image. Make sure you are using the correct image for your phone (there may be more than one choice). If this fails you should contact Google support, or if you bought it elsewhere, contact them for any warranty you might have.
Make sure to wipe cache
v12xke said:
Not sure why you used the October image, but with a locked bootloader your only option is the rescue OTA. You could try a factory reset from recovery. If that doesn't (or did not) work, then try the December OTA image. Make sure you are using the correct image for your phone (there may be more than one choice). If this fails you should contact Google support, or if you bought it elsewhere, contact them for any warranty you might have.
Click to expand...
Click to collapse
Already tried December. Same thing. I live in Cuba. No warranty or anything. The phone was a gift, and it worked with pie without any issues
---------- Post added at 07:43 PM ---------- Previous post was at 07:42 PM ----------
ktmom said:
Make sure to wipe cache
Click to expand...
Click to collapse
I don't have that option in recovery. Any way I've wiped data several times, I think that should wipe cache also
movilserver said:
Already tried December. Same thing. I live in Cuba. No warranty or anything. The phone was a gift, and it worked with pie without any issues
---------- Post added at 07:43 PM ---------- Previous post was at 07:42 PM ----------
I don't have that option in recovery. Any way I've wiped data several times, I think that should wipe cache also
Click to expand...
Click to collapse
If you have done a FDR from recovery, and sideloaded a couple of valid OTA's, sorry to say I think you're pretty much done. It's too bad the bootloader is locked, as you would have more tools to work with. What is your bootloader version? 10 or Pie? If still Pie you might get lucky sideloading the correct Pie OTA that exactly matches your bootloader, and get back into System. Once up and running you could look into unlocking it if that is an option. If not wait for a 10 update to come down vs. sideloading. Nothing to lose at this point. Hang in there.