Hi,
Would anybody be willing to upload the stock recovery from the At&t Razer Phone 2 please.
I would really appreciate it. I'm trying to work on some more for this phone.
Thank you
I know another att variant guy captured the newest pie zip URL and I downloaded it. The recovery lives in the boot.img right?
Were AT&T the ones that sent you the THX model? Or did you buy it straight from Razer?
I'll find that URL and past it here. I've extracted the previous Oreo update from the att build prior to moving to the global version. I had to capture the URL from a log, then downloaded it, then extracted it then I had to use python to fully extract pieces of the payload. Which included the boot.img.
Not a developer but I think I can help here.
Here's the URL for pie July security for att:
https://android.googleapis.com/pack.../2965f0fadb65852413dba10a4fed1029ecce838f.zip
This will help you extract the payload.bin in the zip:
https://shorturl.at/ABEMW
jonchance_84 said:
I know another att variant guy captured the newest pie zip URL and I downloaded it. The recovery lives in the boot.img right?
Were AT&T the ones that sent you the THX model? Or did you buy it straight from Razer?
I'll find that URL and past it here. I've extracted the previous Oreo update from the att build prior to moving to the global version. I had to capture the URL from a log, then downloaded it, then extracted it then I had to use python to fully extract pieces of the payload. Which included the boot.img.
Not a developer but I think I can help here.
Here's the URL for pie July security for att:
https://android.googleapis.com/pack.../2965f0fadb65852413dba10a4fed1029ecce838f.zip
This will help you extract the payload.bin in the zip:
https://shorturl.at/ABEMW
Click to expand...
Click to collapse
I received it from Razer for development/testing. Yes the recovery is in the boot.img. My computer is down right now do to kid damage lol. Got to repair it. I've downloaded the payload.bin but I need help extracting it.
Thank you
kountry83 said:
I received it from Razer for development/testing. Yes the recovery is in the boot.img. My computer is down right now do to kid damage lol. Got to repair it. I've downloaded the payload.bin but I need help extracting it.
Thank you
Click to expand...
Click to collapse
I'll pull out my old dumpy laptop. Good one is at work. I'll see if I can extract the boot.img.
---------- Post added at 07:27 PM ---------- Previous post was at 06:44 PM ----------
Try that.
https://mega.nz/#!d0MSGIIQ!imc6jZyK0wyJrzFvDt9WhgSqwLZTdV9oexaYBP9gfeQ
Hey bud,
Thank you for the extracted image. I really appreciate it. I fixed my laptop this morning and extracted the whole payload.bin with python. I'm currently doing research on the partitions. I'm also trying to figure out why the arter97 r10 kernel won't boot with at&t latest update. Just hangs at boot. It installs nicely with global. Again thank you very much for your time and effort.
Kountry
kountry83 said:
Hey bud,
Thank you for the extracted image. I really appreciate it. I fixed my laptop this morning and extracted the whole payload.bin with python. I'm currently doing research on the partitions. I'm also trying to figure out why the arter97 r10 kernel won't boot with at&t latest update. Just hangs at boot. It installs nicely with global. Again thank you very much for your time and effort.
Kountry
Click to expand...
Click to collapse
R10 works just fine on my device updated to AT&T's latest.
JDBarlow said:
R10 works just fine on my device updated to AT&T's latest.
Click to expand...
Click to collapse
Hmm I wonder what I'm doing wrong. I followed the exact steps I did on the global firmware. Is their something I'm missing. Mine just sits at boot animation. What's your steps if you don't mind me asking bud.
Thank you
kountry83 said:
Hmm I wonder what I'm doing wrong. I followed the exact steps I did on the global firmware. Is their something I'm missing. Mine just sits at boot animation. What's your steps if you don't mind me asking bud.
Thank you
Click to expand...
Click to collapse
Not at all. Of course I unlocked both bootloader and critical.
Then I've extracted the AT&T Oreo file on Razers website into my adb folder and run the flash all .bat file. After first boot I allow it to update to latest Pie update. Are you on AT&T?? I'm the one that posted the captured OTA link.
@JDBarlow Yes I'm on latest At&T. I've had it working a few days ago but switched to global for a minute to do a vendor/system comparison. Now I can't get it to work again. Thank you for the it's captured link bud. I've done the same thing you did but my phone came development unlocked with different recovery setup. I backed up all of my development firmware.
kountry83 said:
@JDBarlow Yes I'm on latest At&T. I've had it working a few days ago but switched to global for a minute to do a vendor/system comparison. Now I can't get it to work again. Thank you for the it's captured link bud. I've done the same thing you did but my phone came development unlocked with different recovery setup. I backed up all of my development firmware.
Click to expand...
Click to collapse
@kountry83 I know bro I'm patiently waiting on someone (dev) to step up and take this device on..I love it man has so much potential if we had more development :good:
Nice to see someone taking a swing at it. So tired of people trash talking this phone, when it's capable of so much. I'm not a dev but seems to me that this phone would be easy to tinker with since Razer pretty much begs you to. Welp I guess JD and I will be here to test anything or help any way we can. I've really only seen him and one other dude using this phone on att. Openly that is. I ended up on global cause I hated waiting on att to release pie update.
JD, how's your cell connection quality? I can literally stare at my signal and it drops out completely from 3 bars or so. Maybe I could flash the modem.img to see if the basebands are different? I might just flash the Oreo att firmware them let it update, then flash arter kernel, then flash magisk zip within arter twrp to get root.
jonchance_84 said:
Nice to see someone taking a swing at it. So tired of people trash talking this phone, when it's capable of so much. I'm not a dev but seems to me that this phone would be easy to tinker with since Razer pretty much begs you to. Welp I guess JD and I will be here to test anything or help any way we can. I've really only seen him and one other dude using this phone on att. Openly that is. I ended up on global cause I hated waiting on att to release pie update.
JD, how's your cell connection quality? I can literally stare at my signal and it drops out completely from 3 bars or so. Maybe I could flash the modem.img to see if the basebands are different? I might just flash the Oreo att firmware them let it update, then flash arter kernel, then flash magisk zip within arter twrp to get root.
Click to expand...
Click to collapse
@jonchance_84 Honestly I've gotten such great reception in my area I haven't even diagnosed that. I can pay more attention to it and see what happens. We actually get the 5G Evo in our area..
The flashing sequence you stated above is the exact order I've done mine twice now and everything works very well!!
Edit: I don't get the 5Ge on the Razer 2.. didn't want you to think that ?
JDBarlow said:
@jonchance_84 Honestly I've gotten such great reception in my area I haven't even diagnosed that. I can pay more attention to it and see what happens. We actually get the 5G Evo in our area..
The flashing sequence you stated above is the exact order I've done mine twice now and everything works very well!!
Click to expand...
Click to collapse
I'm not even a mile from i-20 in East Texas. This is all I get on lte, but the weird thing is that never settles in.
@jonchance_84 I live in East Texas too! I got a little land, log cabin, man cave, and guest house that use to be a bed and breakfast lol. Love this country living. I'm on T-Mobile.
kountry83 said:
@jonchance_84 I live in East Texas too! I got a little land, log cabin, man cave, and guest house that use to be a bed and breakfast lol. Love this country living. I'm on T-Mobile.
Click to expand...
Click to collapse
Nice! Other than the heat right now, love it here. I work in IT for an oil and gas company. Starting to tinker more with Android as a hobby. Last phone was a Nexus 6. Always been able to flash, follow directions with no problem, but the dev side seems a bit tricky.
@JDBarlow
I just did the same thing you did with the at&t update and booted up to setup. Then booted to bootloader then flashed arter boot.img to both a and b. Tried to boot back to setup and hangs on boot animation. Don't get why I'm having a hard time getting this to boot off this kernel. Ugh
kountry83 said:
@JDBarlow
I just did the same thing you did with the at&t update and booted up to setup. Then booted to bootloader then flashed arter boot.img to both a and b. Tried to boot back to setup and hangs on boot animation. Don't get why I'm having a hard time getting this to boot off this kernel. Ugh
Click to expand...
Click to collapse
Any errors when flashing arter boot.img via fastboot?
jonchance_84 said:
Nice! Other than the heat right now, love it here. I work in IT for an oil and gas company. Starting to tinker more with Android as a hobby. Last phone was a Nexus 6. Always been able to flash, follow directions with no problem, but the dev side seems a bit tricky.
Click to expand...
Click to collapse
kountry83 said:
@JDBarlow
I just did the same thing you did with the at&t update and booted up to setup. Then booted to bootloader then flashed arter boot.img to both a and b. Tried to boot back to setup and hangs on boot animation. Don't get why I'm having a hard time getting this to boot off this kernel. Ugh
Click to expand...
Click to collapse
@kountry83 @jonchance_84
That's just freaking crazy lol I'm in East Texas too
Instead of flashing the kernel to both slots try ONLY <fastboot flash boot arter97.img> then reboot before installing magisk
Edit: the last time did this flashing sequence I actually booted to recovery right after installing arter97 installed magisk then booted to system
@jonchance_84 no errors. @JDBarlow just tried that also. Don't know what's going on here. I think it might be a little different hardware and software wise.
JDBarlow said:
@[email protected]_84
That's just freaking crazy lol I'm in East Texas too
Instead of flashing the kernel to both slots try ONLY <fastboot flash boot arter97.img> then reboot before installing magisk
Click to expand...
Click to collapse
Maybe he isn't setup with the a/b scheme?
Edit: Maybe the arter kernel isn't compatible with some hardware that's different? Causing kernel panic which results in bootloop? It's gotta be something simple though. Otherwise the att firmware wouldn't even boot at all.
Related
hey everyone just picked up a prototype N6 from a buddy and having serious issues rooting this verion. i have rooted my other N6 with no issues but this build (shamu-userdebug l lrw80j 1454210 dev-keys) just wont seem to work if anyone can point me in the right direction that would be great ty. this version included a power button on the back of the phone which was nice and why it caught my eye.
What have you tried and where does it fail?
Root is usually unlock bootloader, flash recovery, flash supersu from recovery.
The problem you may have if the hardware is different is that the kernel would then be different, meaning there wont be a version of TWRP with a bootable kernel for your device. So just like you cannot run TWRP for a HTC on the Nexus 6, that could be the same case.
oh ok i see what you mean. everytime it gets to the try to temp load twrp it never seems to boot up im using the toolkit .and now it seems that i can't even boot into the system anymore just into fast boot but i can still use the flash boot flash options in root tool kit and i think you are so right about the kernel but just dont know which one to use i tried restoring /baseband /boot/system with a orignal factory 6.0 but individually but not working . is there a different method you think i can try? ty for your help.
sunnybwoy1 said:
oh ok i see what you mean. everytime it gets to the try to temp load twrp it never seems to boot up im using the toolkit .and now it seems that i can't even boot into the system anymore just fast boot. is there a different method you think i can try? ty for your help
Click to expand...
Click to collapse
If you're going to root, recovery is important.
There are apps that can root once booted into android, but you're playing with fire, especially if there hardware is different - as that means you will not have a factory image to flash either. These things are best kept untouched.
Great and I just messed up this systems IMG. cause I'm just stuck at the fastboot now I hope there is away around this. I had a feeling I shouldn't have gotten this version but wanted to be different now it just cost me smfh. Here are the pics of the phone and info
Here are some pics of the phone and build number
sunnybwoy1 said:
Here are some pics of the phone and build number
Click to expand...
Click to collapse
I cant think of a way around it. You could try flashing a stock system.img via fastboot but I cant say I'm hopeful and likely will make things worse. Without custom recovery, it is unlikely that you can repair it.
You can of course try and factory reset it. Who knows, may make it boot?
Yea flashing the system. IMG in fastboot made it worst well I used the new android m system so maybe that's why. Not looking good I hope I can get some answers soon or if maybe someone can mod a system. IMG I can use with this hardware .
sunnybwoy1 said:
Yea flashing the system. IMG in fastboot made it worst well I used the new android m system so maybe that's why. Not looking good I hope I can get some answers soon or if maybe someone can mod a system. IMG I can use with this hardware .
Click to expand...
Click to collapse
I don't think you'll get help here.
to me, it doesnt look like a n6, it looks like a moto x pro..
simms22 said:
to me, it doesnt look like a n6, it looks like a moto x pro..
Click to expand...
Click to collapse
It does, but it definitely does have an engineering bootloader and says shamu XT1103, so it's another one of "those"
danarama said:
It does, but it definitely does have an engineering bootloader and says shamu XT1103, so it's another one of "those"
Click to expand...
Click to collapse
yup. i bet it was the moto x pro, but in development still. they probably used all the shamu software on it at first. im curious whether it would take the moto x pro software.
I'm going to try to flash a stock N6 ROM to see if it will load.
Is this prototype the one with fingerprints sensor on the back?
It has a power button on the back.
sunnybwoy1 said:
Great and I just messed up this systems IMG. cause I'm just stuck at the fastboot now I hope there is away around this. I had a feeling I shouldn't have gotten this version but wanted to be different now it just cost me smfh. Here are the pics of the phone and info
Click to expand...
Click to collapse
PM Me if you decide to "part" with it.
To put a long story short, messed up my phone by incorrectly rooting, and wish to load up stock firmware so I can hopefully use my phone again. Anyone possibly root their devices and have a firmware backup? If anyone has the firmware for the XT1921-3 T-Mobile variant please come forward.
j256 said:
To put a long story short, messed up my phone by incorrectly rooting, and wish to load up stock firmware so I can hopefully use my phone again. Anyone possibly root their devices and have a firmware backup? If anyone has the firmware for the XT1921-3 T-Mobile variant please come forward.
Click to expand...
Click to collapse
I just want to one-up this. I'm in need of an XT1921-3 boot partition image to fix an issue with my phone.
I tracked this down,thank Rootjunky! HE was doing a vid on recovering motorola devices,and linked to this user and i skipped you to the tmo firmware https://androidfilehost.com/?fid=5862345805528062419
Hopefully it's the right one,i'm used to Samsung naming
timjames474 said:
I tracked this down,thank Rootjunky! HE was doing a vid on recovering motorola devices,and linked to this user and i skipped you to the tmo firmware https://androidfilehost.com/?fid=5862345805528062419
Hopefully it's the right one,i'm used to Samsung naming
Click to expand...
Click to collapse
Thank you! I'll check it out. I also have a couple boot and system twrp backups that a couple of people have donated. I'll be going through them this weekend and will probably post them in a separate tmo thread
weakNPCdotCom said:
Thank you! I'll check it out. I also have a couple boot and system twrp backups that a couple of people have donated. I'll be going through them this weekend and will probably post them in a separate tmo thread
Click to expand...
Click to collapse
Glad i could (try) to point you in the right direction!
timjames474 said:
I tracked this down,thank Rootjunky! HE was doing a vid on recovering motorola devices,and linked to this user and i skipped you to the tmo firmware https://androidfilehost.com/?fid=5862345805528062419
Hopefully it's the right one,i'm used to Samsung naming
Click to expand...
Click to collapse
I have to thank you again. After getting my stock restored I was able to confirm the build number on this. It looks like a newer revision but its the same minor build number. I'll be testing it today. THANK YOU
weakNPCdotCom said:
I have to thank you again. After getting my stock restored I was able to confirm the build number on this. It looks like a newer revision but its the same minor build number. I'll be testing it today. THANK YOU
Click to expand...
Click to collapse
So,how'd testing go for you? Just popped by to check in. Hope your phone is still going well!
timjames474 said:
So,how'd testing go for you? Just popped by to check in. Hope your phone is still going well!
Click to expand...
Click to collapse
Perfect. Got the phone back to factory with everything working
weakNPCdotCom said:
Perfect. Got the phone back to factory with everything working
Click to expand...
Click to collapse
Hey there, I'm in this boat now and I was hoping you could tell me how you used the stock firmware to restore the phone? I'm pretty new to this and I was trying to root it and now I'm stuck in a boot loop.
chronometrist said:
Hey there, I'm in this boat now and I was hoping you could tell me how you used the stock firmware to restore the phone? I'm pretty new to this and I was trying to root it and now I'm stuck in a boot loop.
Click to expand...
Click to collapse
If you already have the 1921-3 zip, just follow the instructions in the restoration thread
T-Mobile G6 H872 20D Stock Collection
Based on OEM 20d KDZ. Extracted and Repacked.
DISCLAIMER
Proceed at your own risk. I am not responsible for any damage to your device.
20d Firmware is ARB01
Flashing LAF WILL REMOVE TWRP from your laf partition and restore stock DL Mode
SysBoot ROMs will only work with 20a or 20d bootloaders
FILE BREAKDOWN
The following Zips DO NOT include stock LAF or Recovery
You must flash the provided LAF separately if you wish to go back to stock DL mode.
Bootloader: 20d Stock Bootloader ONLY
SysBoot: 20d Boot and System ONLY (Modem, Bootloader not included). These zips are adb sideload compatible.
FullStock: Full 20d Firmware Installation
StockLAF: Individual LAF image for returning to stock DL mode
TWRPLAF: Individual LAF image for replacing stock DL mode with TWRP
Magisk: You know. You must flash this after flashing any of the above packages if you want to stay rooted.
INSTRUCTIONS
Make a FULL TWRP Backup using 3.2.3. Link to thread is below.
If you are already on my 11g/h or 20a SysBoot ROMs with root and you are able to mount System in TWRP, you should not need to Format Data.
If you are asked for a passcode in TWRP or are unable to mount System, Boot to TWRP and do a Format Data to remove encryption from your device.
Reboot back to Recovery after Formatting in order for TWRP to mount System.
Advanced Wipe - System, Data, Cache and Dalvik
Flash your chosen Zip using TWRP
You must have TWRP on recovery to flash LAF images.
It is recommended that Sysboot Images be flashed AFTER Bootloader or FullStock
If you Flashed SysBoot with Patched Kernel and Root, you are good to go. Otherwise, flash Magisk to maintain root access.
Wipe Cache/Dalvik
Reboot to system.
Your phone may reboot once or twice during the initial boot to system. This is normal.
Your phone may hang a while on the boot logo. This is also normal. If hang persists for too long, hold vol-down+power until phone powers off to reboot.
DOWNLOADS
Stable v1.0
Project Files have been moved to SourceForge
TWRP 3.2.3 for H872 by @Eliminator74 - Thank you for all the work you have done for the G6!
Magisk + Magisk Manager
Bootloader - md5:d4035f43f0dcf47d818a234077f9e7f1
SysBoot ROM - md5:778994866d440676aea146ac289e3852
SysBoot w/Patched Kernel + Magisk Root - md5:f1398a45581b7ab8a90d48a9c6bed81f
FullStock ROM - md5:ff9d7a22a70abd0caf83377308778fe4
StockLAF - md5:785a64b6b4a25d01df0d25a09c0f6f73
TWRPLAF - md5:f8ea4e93dc417d2d31f5cb8b77530bfa
Please let me know if you run into any problems with them. Thanks!
Other H872 Projects
H872 11G Stock Collection
H872 11H Stock Collection
H872 20A SysBoot ROMs (Stock and Rooted)
Announcement
I have officially moved to the V30 and no longer own the G6.
I will still be active in this community, but since I don't have the device any longer I will not be able to test any packages or issues that might arise.
All of my current projects have been tested. If anybody runs into problems, you can still let me know and I'll do my best to support my stock packages.
Thanks guys!
-weakNPCdotCom
XDA:DevDB Information
[STOCK] h87220d, ROM for the T-Mobile LG G6
Contributors
weakNPCdotCom
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.2.3
Based On: 20d KDZ
Version Information
Status: Beta
Current Stable Version: 1.0
Stable Release Date: 2018-10-18
Created 2018-10-18
Last Updated 2018-10-19
@Ken C FYI the 20a and 20d SysBoots are not deodexed, so it might be worth trying 20d to see if your Hotspot works.
weakNPCdotCom said:
@Ken C FYI the 20a and 20d SysBoots are not deodexed, so it might be worth trying 20d to see if your Hotspot works.
Click to expand...
Click to collapse
Hotspot works but no fp sensor flashed 20d bootloader and Sysboot-mroot with a quick wipe (default wipe; cache data and dalvik) I mentioned it in the other thread. Was wondering if I should've flashed the full stock while I was at it.
Everything else works fine so far.
Sent from my LG-H872 using Tapatalk
Ken C said:
Hotspot works but no fp sensor flashed 20d bootloader and Sysboot-mroot with a quick wipe (default wipe; cache data and dalvik) I mentioned it in the other thread. Was wondering if I should've flashed the full stock while I was at it.
Everything else works fine so far.
Sent from my LG-H872 using Tapatalk
Click to expand...
Click to collapse
Yeah I'm not sure why that would happen. Sorry about that man. I would try wiping system and cache without wiping data then flash FullStock followed by rooted sysboot. maybe some of the modem related images are causing the problem
weakNPCdotCom said:
Yeah I'm not sure why that would happen. Sorry about that man. I would try wiping system and cache without wiping data then flash FullStock followed by rooted sysboot. maybe some of the modem related images are causing the problem
Click to expand...
Click to collapse
Lol... Dude I noticed today that you and I have conversations spanning different threads.
I wiped everything, flashed full stock and the mroot zip and all seems good so far.
Sent from my LG-H872 using Tapatalk
Ken C said:
Lol... Dude I noticed today that you and I have conversations spanning different threads.
I wiped everything, flashed full stock and the mroot zip and all seems good so far.
Sent from my LG-H872 using Tapatalk
Click to expand...
Click to collapse
sweet. should have debloated 20d sysboot posted later tonight
Lol I know I'm being stupid but can someone explain it to me more simply so I don't brick my lg please and thank you
weakNPCdotCom said:
sweet. should have debloated 20d sysboot posted later tonight
Click to expand...
Click to collapse
Not to put you on the spot man. Actually think it's kinda funny but take a look since you seem to be able to, and see if there's a 20e build out. I'm thinking security patch since they always say enhancement. But I was wondering, just wondering, if it's only a security thing would there be someway to get those updates without having to go through all this everytime? I'm not niave to not think there couldn't be something else in these updates I'm just curious what your thoughts on that may be.
Probably better off safe than sorry but noticed that build number last night somewhere. Europe probably so not here yet.
Sent from my LG-H872 using Tapatalk
---------- Post added at 06:41 AM ---------- Previous post was at 06:36 AM ----------
aquinoer said:
Lol I know I'm being stupid but can someone explain it to me more simply so I don't brick my lg please and thank you
Click to expand...
Click to collapse
I don't have time now but I saw your posts from yesterday. I'll look when I get a chance to see what your on about if somebody else doesn't answer your question. If it's a root thing your technically in the wrong thread for that. But I'll see in an hour or so if I can possibly point you in the right direction. What model number are you running? H870, h872,etc. If memory serves me correctly most everything in here should be post root.
Didn't want you thinking you were being left out to dry
Sent from my LG-H872 using Tapatalk
Ken C said:
Not to put you on the spot man. Actually think it's kinda funny but take a look since you seem to be able to, and see if there's a 20e build out. I'm thinking security patch since they always say enhancement. But I was wondering, just wondering, if it's only a security thing would there be someway to get those updates without having to go through all this everytime? I'm not niave to not think there couldn't be something else in these updates I'm just curious what your thoughts on that may be.
Probably better off safe than sorry but noticed that build number last night somewhere. Europe probably so not here yet.
Sent from my LG-H872 using Tapatalk
---------- Post added at 06:41 AM ---------- Previous post was at 06:36 AM ----------
I don't have time now but I saw your posts from yesterday. I'll look when I get a chance to see what your on about if somebody else doesn't answer your question. If it's a root thing your technically in the wrong thread for that. But I'll see in an hour or so if I can possibly point you in the right direction. What model number are you running? H870, h872,etc. If memory serves me correctly most everything in here should be post root.
Didn't want you thinking you were being left out to dry
Click to expand...
Click to collapse
I have h872 I just want to get security patch and have root lol
I'm going to assume that you've already looked into the root thread for the device.
If you have fwul on a thumb drive and know how to boot to it from your pc you really should be good to go. Just to make your life easier put twrp and magisk on your external SD card before you do anything.
Perform the laf switch in lgup.
Go through step 1 in fwul, but when you come to step 2 you'll be better off flashing it manually.
Rooting will put twrp on your laf partition and allow you to access it from there (using the method you used to get into download mode) to flash twrp to recovery and magisk to keep root. Op has these files set to not have to worry about some of this stuff but, first time through I'd want to do it by the book.
Theoretically if you have TWRP on recovery you should be able to flash one of his prerooted roms making the whole mess easier but I've not discussed that option with him. So don't try it unless you're adventurous.
This is from the op and takes place after you do step 1 through fwul (which seems to be all you really need that for)
https://forum.xda-developers.com/showthread.php?p=77811927
Biggest piece of advice I could give you would be to do a dry run of fwul and see what you get. That way you can work out any hang ups before you commit. And get a feel for how it operates.
The dangerous part is where you change the laf on the phone through the patched lgup program and have to do that cord pull deal. It seems to be good at the 10% mark. But to be safe once you get it set to go have the phone in one hand and cord in other. As soon as it goes from laf to the next partition
AS SOON AS YOU SEE IT CHANGE, PULL THE CORD!!!
Then boot into fwul and perform follow step one. Don't worry if unpacking seems to take forever, it jumped to 31% for me and felt like it got hung up. Be patient, like really patient and it'll eventually run through. Then finish out the commands that put twrp on laf.
You could if you want to do the reading, look through anything with my name attached. I had a hell of a time getting things right. Also just in case I missed something.
I'm still waking up but this should be what you need. I screwed it up a bunch of times and was probably lucky with no brick but like I said before it seems the laf switch is the dangerous part. I've been able to recover from everything else.
The link I posted is really specific and may help you more than me telling you from memory. So I'd read that after making sure you got the first part worked out procedure Wise from the root thread itself. (make sure you understand what you need to do for that part) Sometimes it's worth it to read through a whole thread to see the screw ups everybody else made plus there's a video some guy posted that shows it being done. Not to mention I could've missed something by accident.
Also just in case if you've got another sim card device hanging around I'd put the card in that and use it until you get this worked out correctly. Just so in the worst case you've got a working phone to use.
And honestly if anything I posted makes you uncomfortable hold off until you are. Things can be fixed but why stress if you don't need to?
@weakNPCdotCom
Did I miss anything?
Sent from my LG-H872 using Tapatalk
aquinoer said:
I have h872 I just want to get security patch and have root lol
Click to expand...
Click to collapse
I've actually been wondering about the security patch deal myself.
It would be cool if we could do the monthly patch without people being nice and making things easier than they could be. It's not like it's not appreciated But it would be nice to just flash an update if it's only security related and go on with our lives.
Do you think there's any chance in hell this device would see P? The chip would be what 3 gens behind by then?
I just don't see it since it took this long to see O. I mean I've pushed phones further than they say you can with help from this site. But officially I don't see it happening so it's up to people creating roms that have a chance to keep a device longer than that 2 yr cycle. And that hasn't happened yet on this device. I blame that on the year it took to work out root
I did notice the other day that my spare moto X pure can run an 8.0 rom. It needs a new screen and It's running stock now but it's way easier to work on than this thing.
I wonder, with all the different partitions involved now a days if there wasn't some way. On the lines of how we achieved root in the first place. I know there's all the integration within the system and all that but I can dream right?
Can't sleep and that had me thinking
@weakNPCdotCom
Do you have anything you could send me so I can work this stuff out when you move along? I totally appreciate your help and think it's cool that your decent like this, but it doesn't make sense to depend on you like some (myself included) do if your moving on. Ain't gone lie and say if there wasn't something interesting on that newer phone that we could use I wouldn't be interested. But I can't switch phones that often and I'd like to be able to pull this stuff off myself to, if nothing, else keep it updated. There's just not the development that this model could pull off being done and i really don't see it happening. Love aex but I've mentioned why I run stock (gag gag) like I've been.
PM me if your willing, no stress just figured I'd ask. Page of links would be useful. I think I have an idea what your doing but I'm not sure how to achieve it.
Sent from my LG-H872 using Tapatalk
Ken C said:
I've actually been wondering about the security patch deal myself.
It would be cool if we could do the monthly patch without people being nice and making things easier than they could be. It's not like it's not appreciated But it would be nice to just flash an update if it's only security related and go on with our lives.
Do you think there's any chance in hell this device would see P? The chip would be what 3 gens behind by then?
I just don't see it since it took this long to see O. I mean I've pushed phones further than they say you can with help from this site. But officially I don't see it happening so it's up to people creating roms that have a chance to keep a device longer than that 2 yr cycle. And that hasn't happened yet on this device. I blame that on the year it took to work out root
I did notice the other day that my spare moto X pure can run an 8.0 rom. It needs a new screen and It's running stock now but it's way easier to work on than this thing.
I wonder, with all the different partitions involved now a days if there wasn't some way. On the lines of how we achieved root in the first place. I know there's all the integration within the system and all that but I can dream right?
Can't sleep and that had me thinking
@weakNPCdotCom
Do you have anything you could send me so I can work this stuff out when you move along? I totally appreciate your help and think it's cool that your decent like this, but it doesn't make sense to depend on you like some (myself included) do if your moving on. Ain't gone lie and say if there wasn't something interesting on that newer phone that we could use I wouldn't be interested. But I can't switch phones that often and I'd like to be able to pull this stuff off myself to, if nothing, else keep it updated. There's just not the development that this model could pull off being done and i really don't see it happening. Love aex but I've mentioned why I run stock (gag gag) like I've been.
PM me if your willing, no stress just figured I'd ask. Page of links would be useful. I think I have an idea what your doing but I'm not sure how to achieve it.
Sent from my LG-H872 using Tapatalk
Click to expand...
Click to collapse
Sorry for the delay in response. So, unfortunately when I tried debloating 20d I ran into a problem with the Calendar app crashing every 30 seconds. I spent hours trying to figure out which app I was removing that was causing that and I couldnt identify the problem. But I plan on revisiting the problem this coming weekend.
I have no problem sharing what I use to repack these.. I'll pm you the details in case you might want to give it a try.
weakNPCdotCom said:
Sorry for the delay in response. So, unfortunately when I tried debloating 20d I ran into a problem with the Calendar app crashing every 30 seconds. I spent hours trying to figure out which app I was removing that was causing that and I couldnt identify the problem. But I plan on revisiting the problem this coming weekend.
I have no problem sharing what I use to repack these.. I'll pm you the details in case you might want to give it a try.
Click to expand...
Click to collapse
Thanks man,
Something I've noticed on the 20d build. The "my places" app has been repeatedly closing. Not crashing and freezing it stops it. But when it would close it would close out settings at the same time.
Not sure if it was me or not. I been tweaking whatever I can. More curious if you'd seen it before yourself.
Saw you pm'ed me so I'll look at that. Feel like I live in a Morton's Salt label at the moment.
Sent from my LG-H872 using Tapatalk
LG G6 H872 - Software version H87220e
Can I install this on my phone I have LG G6 "LG-H872" - Software version H87220e - Kernel 3.18.71
or it has to be 20e?
can the lg g6 h872 be downgraded from h87220e to one with a bootloader for the available twrp for the T-Mobile lg g6?
Whew, so many options
I'm on rooted 20a now, TWRP on recovery and laf -- I want to go back to full stock/factory, INCLUDING laf and lafbak (returning the phone).
Does your FULLSTOCK zip do this, or do I have to flash laf after, or...?
TIA!
usmras said:
Can I install this on my phone I have LG G6 "LG-H872" - Software version H87220e - Kernel 3.18.71
or it has to be 20e?
Click to expand...
Click to collapse
macg13702 said:
can the lg g6 h872 be downgraded from h87220e to one with a bootloader for the available twrp for the T-Mobile lg g6?
Click to expand...
Click to collapse
Versions 11g - 20e are ARB01 and interchangeable. If you are rooted and/or already have TWRP on your phone then yes, you can flash the FullStock zip to downgrade. Otherwise, you will need to follow @runningnak3d 's root procedure which will require the KDZ for whatever version you want to end up on.
BUT.. I will put a 20e collection out for you guys asap.
RashaMatt said:
Whew, so many options
I'm on rooted 20a now, TWRP on recovery and laf -- I want to go back to full stock/factory, INCLUDING laf and lafbak (returning the phone).
Does your FULLSTOCK zip do this, or do I have to flash laf after, or...?
TIA!
Click to expand...
Click to collapse
FullStock does NOT replace your LAF or Recovery partitions. You can go back to stock LAF by flashing the StockLAF zip. However, I do not have any zips for recovery at the moment. I excluded these intentionally so people wouldnt lose all the hard work of rooting.
I dont have a 20d KDZ on hand, but I do have 20a. I can make a 20a recovery zip and add it to my 20a thread. Once it is available, you can put it on your phone's storage and flash it to recovery using TWRP already on your recovery partition (yes, even if TWRP is on recovery it can flash the recovery partition).
I can also include a stock recovery zip in the 20e package Ill be making.
weakNPCdotCom said:
FullStock does NOT replace your LAF or Recovery partitions. You can go back to stock LAF by flashing the StockLAF zip. However, I do not have any zips for recovery at the moment. I excluded these intentionally so people wouldnt lose all the hard work of rooting.
I dont have a 20d KDZ on hand, but I do have 20a. I can make a 20a recovery zip and add it to my 20a thread. Once it is available, you can put it on your phone's storage and flash it to recovery using TWRP already on your recovery partition (yes, even if TWRP is on recovery it can flash the recovery partition).
I can also include a stock recovery zip in the 20e package Ill be making.
Click to expand...
Click to collapse
If I just want to restore everything to factory stock, might it be just as easy to restore just laf from your ZIP, then use LGUP to flash the 20a kdz?
Thanks for all your hard work!
RashaMatt said:
If I just want to restore everything to factory stock, might it be just as easy to restore just laf from your ZIP, then use LGUP to flash the 20a kdz?
Thanks for all your hard work!
Click to expand...
Click to collapse
No problem m8! And yeah, if you want to download the KDZ I would use the patched LGUP that is linked in the H872 root thread
weakNPCdotCom said:
And yeah, if you want to download the KDZ I would use the flashed LGUP that is linked in the H872 root thread
Click to expand...
Click to collapse
Meaning this? LG-H872_Oreo-20a_Bootloader_B1.zip (W/LAF)
Hey there, I decided to try out the beta but I'm looking to revert to stock Oreo so I can get Pie through OTA. However I have no clue how to do it, I've read a couple threads referencing this but I can't seem to piece together what needs to be done.
Would someone be so kind to post step by step instructions on what I need to do? I'm pretty techy so just basic instructions would be a great help. Thanks and have a great day!
Spectrah said:
Hey there, I decided to try out the beta but I'm looking to revert to stock Oreo so I can get Pie through OTA. However I have no clue how to do it, I've read a couple threads referencing this but I can't seem to piece together what needs to be done.
Would someone be so kind to post step by step instructions on what I need to do? I'm pretty techy so just basic instructions would be a great help. Thanks and have a great day!
Click to expand...
Click to collapse
Download CRK1 with the SamFirm tool
Flash it with patched ODIN 3.13.1
Spectrah said:
Hey there, I decided to try out the beta but I'm looking to revert to stock Oreo so I can get Pie through OTA. However I have no clue how to do it, I've read a couple threads referencing this but I can't seem to piece together what needs to be done.
Would someone be so kind to post step by step instructions on what I need to do? I'm pretty techy so just basic instructions would be a great help. Thanks and have a great day!
Click to expand...
Click to collapse
Download this firmware crk1 from here https://androidfilehost.com/?fid=11410963190603879881 extract the files and you'll see inside of the extracted folder more files that have .md5 on the end of them right click on the files and click rename and just delete the .md5 part only and leave it so it still has the .tar on the end then use the REGULAR NEWEST version of Odin NOT the patched one and then load the files in their respective places AP to AP, BL to BL etc. etc. Then just flash it to the phone while the phone is in download mode and after the successful flash boot into recovery mode and select factory reset so everything is the way it's supposed to be.... Finished!
I really appreciate the help! I'm a bit confused because Mr. Orange is saying use patched ODIN but MrMike is saying not patched version. I'm not sure which version to use then.
Spectrah said:
I really appreciate the help! I'm a bit confused because Mr. Orange is saying use patched ODIN but MrMike is saying not patched version. I'm not sure which version to use then.
Click to expand...
Click to collapse
The patched one may not work and you'll be forced to start over.. The newest version of odin is for the newer bootloader versions and the patched one isn't updated for the newer bootloader versions but you can try it if you want if it doesn't work then start over.
MrMike2182 said:
The patched one may not work and you'll be forced to start over.. The newest version of odin is for the newer bootloader versions and the patched one isn't updated for the newer bootloader versions but you can try it if you want if it doesn't work then start over.
Click to expand...
Click to collapse
Hmm, is there any advantage to using the parched version? It sounds like there's an official version that will get me the desired results from what you're saying.
Spectrah said:
Hmm, is there any advantage to using the parched version? It sounds like there's an official version that will get me the desired results from what you're saying.
Click to expand...
Click to collapse
The patched version is usually used to switch from N950U to N950U1 or the other way.. I would just use the official version if I were you because I ALREADY flashed from 5DRL7 back to N950USQS5CRK1 and it's working perfectly.. But if you want to mess with the patched version you can but like I said if it doesn't work then you have to start over.
MrMike2182 said:
The patched version is usually used to switch from N950U to N950U1 or the other way.. I would just use the official version if I were you because I ALREADY flashed from 5DRL7 back to N950USQS5CRK1 and it's working perfectly.. But if you want to mess with the patched version you can but like I said if it doesn't work then you have to start over.
Click to expand...
Click to collapse
I'm gonna use the patched version, thanks so much for all of your help!
Spectrah said:
I'm gonna use the patched version, thanks so much for all of your help!
Click to expand...
Click to collapse
Must be something wrong with you obviously.. You go and ask for help and then the person who gives you the most details on how to do it and you'd rather listen to someone who gave you a one line answer. LMAO. Actually this is probably my own fault because I should have known better that when someone asks for step by step instructions basically asking someone to hold their hand through the process that they're a problem..
I used the patched version and it works perfectly on the N950U.
Mr. Orange 645 said:
I used the patched version and it works perfectly on the N950U.
Click to expand...
Click to collapse
Well others in the other thread complained that it didn't work but that's why I said it may or may not work I didn't outright say it doesn't work.
MrMike2182 said:
Well others in the other thread complained that it didn't work but that's why I said it may or may not work I didn't outright say it doesn't work.
Click to expand...
Click to collapse
I never said you did. Is there a particular reason you're being so confrontational and taking things so personal? You just bit the OP's head off and called him "a problem," because he didn't take your advice exactly. I didn't even mention you, quote, or refer to you. I was just sharing my experience, yet you jump on and defend yourself. Try to realax a little and have fun.
Mr. Orange 645 said:
I never said you did. Is there a particular reason you're being so confrontational and taking things so personal? You just bit the OP's head off and called him "a problem," because he didn't take your advice exactly. I didn't even mention you, quote, or refer to you. I was just sharing my experience, yet you jump on and defend yourself. Try to realax a little and have fun.
Click to expand...
Click to collapse
That's because too many folks on here want someone to hold their hand through the entire process instead of actually spending the time to learn how to do it on their own and then when you go spend your time to give them the best answers so they don't waste their time running into possible problems that others have stated that they did and then person just decides to go do the opposite then it's like what did you even ask for help for then? I agree that I was a bit of a jerk but that's from constantly dealing with that on here.
MrMike2182 said:
Must be something wrong with you obviously.. You go and ask for help and then the person who gives you the most details on how to do it and you'd rather listen to someone who gave you a one line answer. LMAO. Actually this is probably my own fault because I should have known better that when someone asks for step by step instructions basically asking someone to hold their hand through the process that they're a problem..
Click to expand...
Click to collapse
Unfortunately that was a typo and I meant the non patched version. Obviously you went above and beyond in making sure I was prepared and I really appreciate that. Sorry about the confusion.
THIS GUIDE IS NOW OBSOLETE
Links will be added once the new guide using the firehose comes out - No more bricking!
Thanks to everyone who contributed to the firehose!
I just cut and pasted the whole guide into a txt file, which is linked below in case there's ever any purpose of looking at it again.
https://drive.google.com/file/d/1wTRMvweLlsF-3WU9CYlz7X3ZIRE3vtCs/view?usp=sharing
Isn’t Mr. Zhu the author of twrp?
You might want to wait until I get to my computer again as I realized there are a few minor edits that could be helpful. It's not letting me edit it successfully on my phone
Malossi94 said:
Isn’t Mr. Zhu the author of twrp?
Click to expand...
Click to collapse
Yeah but apparently he stopped development, but le Minh sent the Korean fix after that so I'm not entirely sure lmao
antintin said:
Yeah but apparently he stopped development, but le Minh sent the Korean fix after that so I'm not entirely sure lmao
Click to expand...
Click to collapse
Mr. Zhu repaired kor twrp, and my kor skt G8 participated in the repair development:silly:
Malossi94 said:
Mr. Zhu repaired kor twrp, and my kor skt G8 participated in the repair development:silly:
Click to expand...
Click to collapse
Nice! I'll edit as soon as I get on my computer
Hi have followed the guide and got stuck at step 7. I get only the LG V50Thinq powered by android screen and nothing more. It just stays like for the past 30 minutes. I have rebooted several times but the same. i cannot access (or do not know) download mode.
Any help!
So, if your on a korean version that wil be a q version of android vulnerable. Therefore at step 6, you will need a pie kdz to flash those 4 xbl files. Do not make my mistake, you will get bricked ))
Marmalux said:
So, if your on a korean version that wil be a q version of android vulnerable. Therefore at step 6, you will need a pie kdz to flash those 4 xbl files. Do not make my mistake, you will get bricked ))
Click to expand...
Click to collapse
Sorry I'm afraid I don't understand. That's step 4, and you don't need to flash the whole kdz. Only the partitions the guide says to.
antintin said:
Sorry I'm afraid I don't understand. That's step 4, and you don't need to flash the whole kdz. Only the partitions the guide says to.
Click to expand...
Click to collapse
I think he's referring to how its a bit confusing how it says you should use android pie but also implies that you should use latest pre-march firmware, which for korean variant is actually android Q not pie so its little confusing which you should use, i could be wrong though, thanks alot for this guide though!
9RR said:
I think he's referring to how its a bit confusing how it says you should use android pie but also implies that you should use latest pre-march firmware, which for korean variant is actually android Q not pie so its little confusing which you should use, i could be wrong though, thanks alot for this guide though!
Click to expand...
Click to collapse
If someone can't deal with the level of instruction I provided here, I would very much advise against attempting it as it is inherently very risky. Probably not what anyone wants to here, but it is what it is
This is great news. Has anyone Tested using a LOS GSI or AOSP GSI? I am on verizon and have found with another phone that all GSIs on android version 9 and 10 have "No Sim Card" errors and you can not make calls or send texts (strangely you can receive both). This error wasn't seen with other network versions of the phone (palm phone). I am a little hesitant to go through this process to find out if data doesn't work on LOS 17 or AOSP 10. If anyone on verizon tries this out, please report back on how well the GSIs work, or if you find a specific ROM that works on Verizon.
CaptainElwood said:
This is great news. Has anyone Tested using a LOS GSI or AOSP GSI? I am on verizon and have found with another phone that all GSIs on android version 9 and 10 have "No Sim Card" errors and you can not make calls or send texts (strangely you can receive both). This error wasn't seen with other network versions of the phone (palm phone). I am a little hesitant to go through this process to find out if data doesn't work on LOS 17 or AOSP 10. If anyone on verizon tries this out, please report back on how well the GSIs work, or if you find a specific ROM that works on Verizon.
Click to expand...
Click to collapse
I've used a lot of gsis like bless and caos (use those instead of aosp definitely). I haven't had any data issues
antintin said:
I've used a lot of gsis like bless and caos (use those instead of aosp definitely). I haven't had any data issues
Click to expand...
Click to collapse
But I have a sprint model. I'm pretty sure Verizon people have tried it with no issues already though
antintin said:
If someone can't deal with the level of instruction I provided here, I would very much advise against attempting it as it is inherently very risky. Probably not what anyone wants to here, but it is what it is
Click to expand...
Click to collapse
Hi, thank you very much for this tutorial.
It was my mistake and got a permanent brick. It is true that the vulnerable firmware for kor is android Q and i have achieved root after downgrading to a older Q version. My problem was at step 4 because i used the q kdz and i did not download a separate pie kdz for that step.
Now i hope no one else will make my mistake since i really do not see how to get DL mode active or to switch slots without the USB. Only thing i got is the image that precedes the DL mode and the IMEI display. And since the USB is basically dead i think firehose (even if i had it) would not recover my phone.
I have flashed and unlock many phones and this is my first unrecoverable brick. My first LG though and probably the last.
Marmalux said:
Hi, thank you very much for this tutorial.
It was my mistake and got a permanent brick. It is true that the vulnerable firmware for kor is android Q and i have achieved root after downgrading to a older Q version. My problem was at step 4 because i used the q kdz and i did not download a separate pie kdz for that step.
Now i hope no one else will make my mistake since i really do not see how to get DL mode active or to switch slots without the USB. Only thing i got is the image that precedes the DL mode and the IMEI display. And since the USB is basically dead i think firehose (even if i had it) would not recover my phone.
I have flashed and unlock many phones and this is my first unrecoverable brick. My first LG though and probably the last.
Click to expand...
Click to collapse
I'm very sorry to hear that, but the firehose could almost definitely help you unbrick. I tried to clarify more that it has to be a pie kdz now, because before I just wrote "load your pie kdz" and you probably missed that. There should still be a warranty though, so you could try to use that if you'd like. It might say that yours expired on the website, but you can just click past it.
antintin said:
Spoiler
I'm very sorry to hear that, but the firehose could almost definitely help you unbrick. I tried to clarify more that it has to be a pie kdz now, because before I just wrote "load your pie kdz" and you probably missed that. There should still be a warranty though, so you could try to use that if you'd like. It might say that yours expired on the website, but you can just click past it.
Click to expand...
Click to collapse
Thank you antintin for your reply. You bring me some hope. The warranty will not apply because it is stated clearly that any attempt to BL unlock will void it (I got it from a shop in Spain via Ebay).
But the firehose on the other hand.... When do you think it will be available? And how will i ba able to get it?
Thank you very much!
Marmalux said:
Thank you antintin for your reply. You bring me some hope. The warranty will not apply because it is stated clearly that any attempt to BL unlock will void it (I got it from a shop in Spain via Ebay).
But the firehose on the other hand.... When do you think it will be available? And how will i ba able to get it?
Thank you very much!
Click to expand...
Click to collapse
Other people who bricked while different bl unlock methods were tested sent it in for warranty with no issues. The firehose will be available in November at the earliest probably. Proof of purchase from eBay should be enough, but I don't if there's any lg repair centers in Spain that support phones.
antintin said:
Other people who bricked while different bl unlock methods were tested sent it in for warranty with no issues. The firehose will be available in November at the earliest probably. Proof of purchase from eBay should be enough, but I don't if there's any lg repair centers in Spain that support phones.
Click to expand...
Click to collapse
In Spain there are several. But i`m in Ireland, and here is none ))
Successfully rooted korean variant, thanks for the guide! I was wondering if its okay now to update to newest firmware via LGUP upgrade mode? (I really want the system wide accent color customization in newest firmware, among other things) I assume it should be but i really don't wanna have to redo all this so id rather just ask, thanks in advance!