Related
NEXUS 7 3G-"nakasig" - Jelly Bean/KitKat Discussions, Problems and Solutions
Hi Nexus 7 "Nakasig" users,
I would like to consider this thread as your one place to chat or anything else related to Jelly Bean on the NEXUS 7 - 3G
I need everyone help to keep this thread somewhat sane, report any trolling or flaming and don't respond to it.
Keep all your posts in this thread polite and make sure you follow The Forum Rules.
I request you to stop posting:
- 'Thanks this helped'
- 'Yeah Me too'
-'+1'
These kind of posts are useless instead use the thanks button to show your appreciation
Click to expand...
Click to collapse
For all your JB needs, go to:
==>[Index] All for NEXUS 7 - "Nakasig" - (GSM/HSPA+)
==>[GUIDE] Unlock and Root a Nexus 7 3G “Nakasig- Tilapia”
==> [GUIDE][BOOTLOADER][4.3] TILAPIA JWR66V - 4.23 Flash Image Instructions - UPDATE
==>[GUIDE]If you need some help for install SDK and ADB drivers in Win 7, you can use this guide which is really good and comprehensive for all of us
It will be better for you to find one thread where we can concentrate all discussions, problems and solutions for the Nexus 7 3G
It 's a tool which is very good if you want to buy a Google Nexus Devices :good:
Google Nexus Devices World Availability Checker
Top man!
Any one got a working recovery and supersu/superuser that works with 4.2?
Since I've heard people losing 3G and stuff when they rooted, and I kinda don't want to have to set my stuff up again
WarningHPB said:
Top man!
Any one got a working recovery and supersu/superuser that works with 4.2?
Since I've heard people losing 3G and stuff when they rooted, and I kinda don't want to have to set my stuff up again
Click to expand...
Click to collapse
You've probably heard that from idiots who don't know what they are doing.
The latest version of TWRP works perfectly fine with 4.2 (3G and not). I'm using it on my 3G without any issues.
And the previous 'su' binaries and apk's should be fine. Neither of them should cause any problems with the 3G functionality as they have nothing to do with it. I installed custom recovery and rooted mine the day I got it. Everything is perfect.
Also, absolute worst case scenario, if you do screw something up, it's easy to revert without losing all of your data.
Hmm...I don't consider myself an idiot but did nothing more sinister than root and flash CWM and lost cellular data functionality completely at random two days later (unknown baseband). Had about 6 Android devices before this going back to HTC Hero, flashed all sorts, and never seen anything like it. Eventually had to flash factory image to get it back. Not especially helpful as inexplicable and not reproduced but worth saying nonetheless.
dave_uk said:
Hmm...I don't consider myself an idiot but did nothing more sinister than root and flash CWM and lost cellular data functionality completely at random two days later (unknown baseband). Had about 6 Android devices before this going back to HTC Hero, flashed all sorts, and never seen anything like it. Eventually had to flash factory image to get it back. Not especially helpful as inexplicable and not reproduced but worth saying nonetheless.
Click to expand...
Click to collapse
FYI, there seems to be a sporadic bug in JB on my GNex where on certain reboots it says Unknown Baseband and IMEI in the About menu, and then on the next reboot it's fine. I am wondering if that same bug is cropping up on the N7, and it's just coincidentally happening on some people's devices after rooting, but it goes away later. On my GNex this issue is particularly noticeable if I gave the phone a full reboot from inside software (e.g. using the app Easy Reboot). Whereas a power off / power on does not as frequently run into this issue.
I'm looking forward to getting mine Ordered today and it shipped today! I'm going to give my 16gb (bought in Aug for $249 so no price mod for me ) to either my GF or my daughter. lol
Sorry for the OT post.. I'm just excited. It will be nice to not have to tether my N7 to my phone. I just switched to the shared data plan on AT&T so it will only cost me $10 to add the N7 to my plan
Just fired up my 3g and will root it tomorrow, is there anything really different in rooting this thing vs the 16gb, anything I should watch out for?
kitsunisan said:
Just fired up my 3g and will root it tomorrow, is there anything really different in rooting this thing vs the 16gb, anything I should watch out for?
Click to expand...
Click to collapse
No, they are identical from a rooting perspective. However, they do run slightly different versions of the image, so if you wind up flashing stock, use the right one.
so first my success, i have managed to get root and a TWRP recovery.
now my question in menus im seeing horizontal lines that move with the landscape. so as the phone rotates the screen, the lines also rotate. maybe its just the background design but it seems really awkward to me that they would intend from these lighter brighter lines to be there
if someone would do me a HUGE favor and get me a stock JVP15S recovery? i flashed over mine with CWM before i could back it up and now i have a 34mg OTA update i cant take because of the custom recovery image
death 90 said:
if someone would do me a HUGE favor and get me a stock JVP15S recovery? i flashed over mine with CWM before i could back it up and now i have a 34mg OTA update i cant take because of the custom recovery image
Click to expand...
Click to collapse
I'm not sure that you will find someone who can give you this file, cause it contains all personal data and apps.
death 90 said:
if someone would do me a HUGE favor and get me a stock JVP15S recovery? i flashed over mine with CWM before i could back it up and now i have a 34mg OTA update i cant take because of the custom recovery image
Click to expand...
Click to collapse
I don't have my N7 yet, but on most Androids the stock recovery images do not vary much or at all between minor upgrades, so any stock recovery should be fine. Try the recovery.img inside the JOP40C image straight from Google. https://developers.google.com/android/nexus/images#nakasigjop40c
Worst case if the update still won't take, flash both system and boot from the stock image too (this will unroot you but so would the OTA, and you can fix that later), and then you'll be stock enough for OTAs to work the next time it prompts.
philos64 said:
I'm not sure that you will find someone who can give you this file, cause it contains all personal data and apps.
Click to expand...
Click to collapse
The recovery partition does not contain any personal data or apps. Everything personal is in /data.
philos64 said:
I'm not sure that you will find someone who can give you this file, cause it contains all personal data and apps.
Click to expand...
Click to collapse
im pretty sure the "recovery" partition doesn't contain any of those things. i don't want a stock rom, i need stock a recovery. twrp allows you to back up certain partitions such as boot, cache, and recovery
cmstlist said:
I don't have my N7 yet, but on most Androids the stock recovery images do not vary much or at all between minor upgrades, so any stock recovery should be fine. Try the recovery.img inside the JOP40C image straight from Google. https://developers.google.com/android/nexus/images#nakasigjop40c
Worst case if the update still won't take, flash both system and boot from the stock image too (this will unroot you but so would the OTA, and you can fix that later), and then you'll be stock enough for OTAs to work the next time it prompts.
The recovery partition does not contain any personal data or apps. Everything personal is in /data.
Click to expand...
Click to collapse
i just downloaded that ill try flashing it now i downloaded the "Google Nexus 7 Toolkit" and while it didn't work for me, it did provide a JRo03d stock recovery which i flashed with fastboot and that recovery did not work. when you nexus 7 arrives i believe it would be possible to recover the stock recovery using "fastboot boot twrp-recovery", ALTHOUGH im not sure when you would execute the "backup recovery" if it would read the phones actual partition or the image you uploaded and booted on
cmstlist said:
The recovery partition does not contain any personal data or apps. Everything personal is in /data.
Click to expand...
Click to collapse
Sorry for my quick answer, I haven't seen the "recovery.img". that's file system.zip or tar which contains apps and data for restore
And if you want the Factory image, go to the thread : [Index] All for NEXUS 7 - "nakasig" - (GSM/HSPA+) , it is on, ready for download
ya i grabbed it thanks. what i don't understand is what the 34mg update is for? any ideas? i uploaded two shots, one settings page showing the build mine shipped with and the other is just the update screen i got showing size. Im about to flash the stock ROM from google now. we'll see how goes
the 34mg update was "signed-nakasig-JOP40C-from-JVP15S". i was able to flash the recovery from the stock ROM JOP40C and use that to patch through android and avoid flashing usuing TWRP
death 90 said:
im pretty sure the "recovery" partition doesn't contain any of those things. i don't want a stock rom, i need stock a recovery. twrp allows you to back up certain partitions such as boot, cache, and recovery
i just downloaded that ill try flashing it now i downloaded the "Google Nexus 7 Toolkit" and while it didn't work for me, it did provide a JRo03d stock recovery which i flashed with fastboot and that recovery did not work. when you nexus 7 arrives i believe it would be possible to recover the stock recovery using "fastboot boot twrp-recovery", ALTHOUGH im not sure when you would execute the "backup recovery" if it would read the phones actual partition or the image you uploaded and booted on
Click to expand...
Click to collapse
Honestly don't try toolkits. Just don't, because you don't know what commands or files they are really flashing, and especially because they were written for the wi-fi version. The stock recovery from the wi-fi version is not guaranteed to be compatible with the 3G version.
philos64 said:
Sorry for my quick answer, I haven't seen the "recovery.img". that's file system.zip or tar which contains apps and data for restore
And if you want the Factory image, go to the thread : [Index] All for NEXUS 7 - "nakasig" - (GSM/HSPA+) , it is on, ready for download
Click to expand...
Click to collapse
System.img is also devoid of personal information because to the standard end user it is write-protected. All the personal stuff is in the data partition.
death 90 said:
the 34mg update was "signed-nakasig-JOP40C-from-JVP15S". i was able to flash the recovery from the stock ROM JOP40C and use that to patch through android and avoid flashing usuing TWRP
Click to expand...
Click to collapse
Glad it worked out for you. I had a feeling it was just going to give you JOP40C anyway.
So, I have been trying to root my 3G tablet (JOP40C), but have no luck. I installed TWRP and unlocked just fine using the Google Nexus 7 ToolKit 3.2. When I use the toolkit to root it seems like it is doing everything fine, reboots, and I do not see any errors during the process. However, when I access Titanium backup, or Root Checker it cannot gain root access. I have tried all the options in the toolkit and nothing is working. Can anyone give me some pointers? Thanks!
spongers said:
So, I have been trying to root my 3G tablet (JOP40C), but have no luck. I installed TWRP and unlocked just fine using the Google Nexus 7 ToolKit 3.2. When I use the toolkit to root it seems like it is doing everything fine, reboots, and I do not see any errors during the process. However, when I access Titanium backup, or Root Checker it cannot gain root access. I have tried all the options in the toolkit and nothing is working. Can anyone give me some pointers? Thanks!
Click to expand...
Click to collapse
Yes - Don't use a toolkit!
Since you already have a custom recovery, put the attached file on your sdcard and install it using TWRP. Then you should be good to go.
Hi,
I have the non-Taiwan Butterfly S. I unlocked it via HTC Dev, and installed Clockwork Recovery.
This week, the 4.2 update was released for Singapore. It seems to have been in two parts, one which was a minor upgrade (235MB), and after that was applied, I got the option of the larger, 4.3, 700MB, OTA.
Applying the OTA seems to have left me, at boot time, with a blank screen (there is some backlight visible, after the HTC splash). I read tonight that OTA should not be used with custom recoveries, so I have (using fastboot) been able to flash the stock recovery.
I can now go into Fastboot, HBoot, and even Recovery. But I think I may no longer have an actual "system".
How can I flash either a custom ROM, or investigate the situation?
And also, after I see the Recovery screen (the battery icon), what can I do there?
Thanks,
ghane0 said:
Hi,
I have the non-Taiwan Butterfly S. I unlocked it via HTC Dev, and installed Clockwork Recovery.
This week, the 4.2 update was released for Singapore. It seems to have been in two parts, one which was a minor upgrade (235MB), and after that was applied, I got the option of the larger, 4.3, 700MB, OTA.
Applying the OTA seems to have left me, at boot time, with a blank screen (there is some backlight visible, after the HTC splash). I read tonight that OTA should not be used with custom recoveries, so I have (using fastboot) been able to flash the stock recovery.
I can now go into Fastboot, HBoot, and even Recovery. But I think I may no longer have an actual "system".
How can I flash either a custom ROM, or investigate the situation?
And also, after I see the Recovery screen (the battery icon), what can I do there?
Thanks,
Click to expand...
Click to collapse
What I would do is get TWRP Recovery (Just a matter of personal preference you can get clockwormod too) do a full wipe, clear the cache, dalvik cache and install a custom ROM hope I helped somehow
Do you still have the OTA zipfile on your device? It should be possible to force the stock recovery to install it, I just don't know how exactly. If you manage to achieve that, it should fix any corrupted files or inconsistent state, unless something went completely wrong.
Also, did the CWM recovery actually succeed to install the smaller OTA? I find that somewhat weird, but then again, I haven't tried to install OTAs using CWM, only TWRP and that did fail early.
If it was a 901S, I'd suggest installing the stock ROM from scratch, but since your phone is 901E (as far as I understand) and my stock ZIPs are for 901S, that's not guaranteed to work. Still, you might try to do that, but make sure to make a backup of the current state first, just in case it only gets worse. If it does work, it's probably going to be the easiest way out.
Another option would be to get someone else with the 901E to post a backup of their /system, I could turn that into a ZIP, which would solve your problem.
koniiiik said:
Do you still have the OTA zipfile on your device? It should be possible to force the stock recovery to install it, I just don't know how exactly. If you manage to achieve that, it should fix any corrupted files or inconsistent state, unless something went completely wrong.
Also, did the CWM recovery actually succeed to install the smaller OTA? I find that somewhat weird, but then again, I haven't tried to install OTAs using CWM, only TWRP and that did fail early.
If it was a 901S, I'd suggest installing the stock ROM from scratch, but since your phone is 901E (as far as I understand) and my stock ZIPs are for 901S, that's not guaranteed to work. Still, you might try to do that, but make sure to make a backup of the current state first, just in case it only gets worse. If it does work, it's probably going to be the easiest way out.
Another option would be to get someone else with the 901E to post a backup of their /system, I could turn that into a ZIP, which would solve your problem.
Click to expand...
Click to collapse
It is a 901s he said non Taiwan
Sent from my HTC Butterfly s using XDA Premium 4 mobile app
seyidaga said:
What I would do is get TWRP Recovery (Just a matter of personal preference you can get clockwormod too) do a full wipe, clear the cache, dalvik cache and install a custom ROM hope I helped somehow
Click to expand...
Click to collapse
I have downloaded the Maximus ROM. I am open to doing this, but I cannot figure out how to use the stock recovery (there seem to be no controls).
koniiiik said:
Do you still have the OTA zipfile on your device? It should be possible to force the stock recovery to install it, I just don't know how exactly. If you manage to achieve that, it should fix any corrupted files or inconsistent state, unless something went completely wrong.
Click to expand...
Click to collapse
I think so, too, but at this stage, I am willing to go clean-slate and restart with a stock, factory, look.
koniiiik said:
If it was a 901S, I'd suggest installing the stock ROM from scratch
Click to expand...
Click to collapse
I have downloaded the stock zip from your website. How do i flash that in stock recovery?
I have access to fastboot from my laptop, I can see the device.
Thanks,
daorderdillon said:
It is a 901s he said non Taiwan
Click to expand...
Click to collapse
Oh, okay, I think I'm getting lost in which area has which version of the phone. Never mind then and thanks for the correction.
ghane0 said:
I think so, too, but at this stage, I am willing to go clean-slate and restart with a stock, factory, look.
I have downloaded the stock zip from your website. How do i flash that in stock recovery?
I have access to fastboot from my laptop, I can see the device.
Thanks,
Click to expand...
Click to collapse
Well, to install custom ROMs, you'll have to use either TWRP or CWM, I don't know about a way to do that using stock recovery.
Ok, I did this:
Installed CWM Recovery
Flashed the Stock zip from koniiiik's archive
Rebooted successfully. Lots and lots of force closes, Everything from android.core to ...
Used Rom Manager to restore a backup made a month ago
Rebooted. All OK now
Flashed Stock Recovery (again, thanks koniiiik)
Booted. Checked OTA. Got a small update (1.x)
Applied. Rebooted, Checked OTA again
Got the 4.3 package. Applied.
All is well
Between Step #3 and #4, I got my entire backlog of SMS delivered, which I lost in the next step. But that is a small price to pay.
Thanks to all of you helped,
ghane0 said:
Used Rom Manager to restore a backup made a month ago
Click to expand...
Click to collapse
Would you mind uploading somewhere the /system part of that backup? I'd be interested in comparing it to the builds I have at hand.
Backup of /system, nearly stock
I say nearly stock, because it was taken after HTC Unlock, Clockwork Recovery was installed, and root flashed
koniiiik said:
Would you mind uploading somewhere the /system part of that backup? I'd be interested in comparing it to the builds I have at hand.
Click to expand...
Click to collapse
I have three files in the directory:
system.ext4.tar (0B)
system.ext4.tar.a (954MB)
system.ext4.tar.b (500MB)
Is the split to avoid files greater than 1GB?
Will upload starting a few hours. Dropbox will do?
ghane0 said:
I say nearly stock, because it was taken after HTC Unlock, Clockwork Recovery was installed, and root flashed
Click to expand...
Click to collapse
Don't worry about that, of these three, only root affects /system and it should be not too difficult to revert.
ghane0 said:
Is the split to avoid files greater than 1GB?
Click to expand...
Click to collapse
Most likely – FAT filesystems, depending on inode size and other factors, only support file sizes up to a certain limit. Sometimes it's 2 GB, sometimes 4 GB, sometimes probably as little as 1 GB.
ghane0 said:
Will upload starting a few hours. Dropbox will do?
Click to expand...
Click to collapse
That would be most helpful. Thanks.
Dropbox is back up, I have sent you a link.
Thanks
Hey All,
I only recently picked up an XT-1060 (2013 Moto X, Dev Ed) that I plan to set up on my Verizon account. I have some experience with both the Nexus 7 (2012) and HTC's Android variants, and, for those platforms, there are technical advantages to booting to a non-stock recovery image directly from fastboot *without flashing that recovery image to the device*. I did a search of all the Moto X forums for such an alternative, and a cursory look didn't give me anything that jumped off the page regarding whether or not this was even possible.
Which brings me to my question: Assuming that I've already taken care of unlocking the bootloader, can I boot to a non-stock recovery on my new unlocked Moto X without flashing that recovery?
Many thanks!
cheers,
john
What do you mean by flashing?
You can fastboot twrp.img,which is a custom recovery.
Unfortunately, booting a custom recovery isn't possible on the Moto X. Why? I have no idea.
Just think of it as an extra later of security against an inadvertent OTA installation.
Thanks to you both for your kind replies.
nhizzat said:
Unfortunately, booting a custom recovery isn't possible on the Moto X. Why? I have no idea.
Just think of it as an extra later of security against an inadvertent OTA installation.
Click to expand...
Click to collapse
This is a bit of a disappointment. It means that I've got to strip out and save the stock recovery somewhere, then re-flash it to enable OTAs. I tend to stay on the "current-stock-plus-rooted" track. The only reason I need a custom recovery is (1) To root the device, and (2) To do nandroid backups from time to time (and possibly restores).
On devices that allow it, this means that I only need to boot the custom one occasionally, with the side benefit of being able to accept OTAs without problems. At least that's been the case for me so far.
Nicolae-Daniel said:
What do you mean by flashing?
You can fastboot twrp.img,which is a custom recovery.
Click to expand...
Click to collapse
This line doesn't make any sense to me. My typical scenarios are: If I'm trying to boot twrm, say, I'd issue: "fastboot boot twrp.img"; and, if I want to flash it, I'd use "fastboot flash recovery twrp.img". Day to day, the only thing I do with recovery is wipe the system cache, and I can do that with the stock recovery. *Sigh*
Regardless, thanks again you two...
cheers,
john
That's the approach I've always taken with my Nexus 7. All the functionality of flashing a custom recovery with one less variable to worry about.
jrredho said:
Thanks to you both for your kind replies.
This is a bit of a disappointment. It means that I've got to strip out and save the stock recovery somewhere, then re-flash it to enable OTAs. I tend to stay on the "current-stock-plus-rooted" track. The only reason I need a custom recovery is (1) To root the device, and (2) To do nandroid backups from time to time (and possibly restores).
On devices that allow it, this means that I only need to boot the custom one occasionally, with the side benefit of being able to accept OTAs without problems. At least that's been the case for me so far.
This line doesn't make any sense to me. My typical scenarios are: If I'm trying to boot twrm, say, I'd issue: "fastboot boot twrp.img"; and, if I want to flash it, I'd use "fastboot flash recovery twrp.img". Day to day, the only thing I do with recovery is wipe the system cache, and I can do that with the stock recovery. *Sigh*
Regardless, thanks again you two...
cheers,
john
Click to expand...
Click to collapse
I'm guessing you will have to play with stock and custom recoveries for that.
jrredho said:
It means that I've got to strip out and save the stock recovery somewhere, then re-flash it to enable OTAs.
Click to expand...
Click to collapse
You always can take recovery.img from your official firmware zip archive and flash it anytime.
UPD: And i hope you know, that OTA will fail if you modify or remove pre-installed apps using root.
k3nny2k said:
You always can take recovery.img from your official firmware zip archive and flash it anytime.
Click to expand...
Click to collapse
Yes, and this is exactly what I'm trying to avoid!
k3nny2k said:
UPD: And i hope you know, that OTA will fail if you modify or remove pre-installed apps using root.
Click to expand...
Click to collapse
I do know that, yes. My plan is to leave the device largely stock. I just need nandroid backups, a handful of root-requiring apps, and tethering. These are the only reasons that I root. I also do not need moment-to-moment access to a custom recovery.
Anyway, thanks for keeping me on my toes!
cheers,
john
(originally posted in the flashfire threads, but it was suggested I post here)
My apologies if this has already been covered (I could not find an answer in searching)
I appreciate that it can be dangerous to use flashfire to flash the bootloader partition and that one should use fastboot. My question is:
If I download a FW package and the bootloader has changed, what happens if I flash to the kernel, system, cache, vendor etc... and do not flash to bootloader and radio? Will the flash fail; will the phone soft brick; will nothing happen and I can go merrily along?
The question derives from this: If the phone can become unusable with a mismatched bootload and radio to the rest of the images, it would require to unpack the package and check for a version prior to flashing other partitions (so I assume). If I go that far, would it not be easier to not use flashfire and simply manually flash the required files when updates are available?
Thanks
N6, unlocked and rooted (previously always updating latest patches and rerooting myself (using TWRP), but wishing to try flashire)
RLBL said:
(originally posted in the flashfire threads, but it was suggested I post here)
My apologies if this has already been covered (I could not find an answer in searching)
I appreciate that it can be dangerous to use flashfire to flash the bootloader partition and that one should use fastboot. My question is:
If I download a FW package and the bootloader has changed, what happens if I flash to the kernel, system, cache, vendor etc... and do not flash to bootloader and radio? Will the flash fail; will the phone soft brick; will nothing happen and I can go merrily along?
The question derives from this: If the phone can become unusable with a mismatched bootload and radio to the rest of the images, it would require to unpack the package and check for a version prior to flashing other partitions (so I assume). If I go that far, would it not be easier to not use flashfire and simply manually flash the required files when updates are available?
Thanks
N6, unlocked and rooted (previously always updating latest patches and rerooting myself (using TWRP), but wishing to try flashire)
Click to expand...
Click to collapse
it is really rare that a bootloader flash is required, and a radio update is never required. if you dont flash them, then you just dont flash them, thats all.
I'd add that going to a major update you'll want to pay close attention. The bootloader probably will need updating. e.g. lollipop to MM, the bootloader had to be updated.
The radio is optional and often with trial and error, you'll find a particular one that for your hardware, in your area, you get the best signal. There is a thread with N6 flashable radios here: http://forum.xda-developers.com/showthread.php?t=3066052.
Had you posted that you had an N6 in your original post, I'd have helped you, because that's what I use
ktmom said:
I'd add that going to a major update you'll want to pay close attention. The bootloader probably will need updating. e.g. lollipop to MM, the bootloader had to be updated.
The radio is optional and often with trial and error, you'll find a particular one that for your hardware, in your area, you get the best signal. There is a thread with N6 flashable radios.
Had you posted that you had an N6 in your original post, I'd have helped you, because that's what I use
Click to expand...
Click to collapse
both mm a lollipop, i never updated my bootloader. i did update it after mm though.
ktmom said:
I'd add that going to a major update you'll want to pay close attention. The bootloader probably will need updating. e.g. lollipop to MM, the bootloader had to be updated.
The radio is optional and often with trial and error, you'll find a particular one that for your hardware, in your area, you get the best signal. There is a thread with N6 flashable radios here: http://forum.xda-developers.com/showthread.php?t=3066052.
Had you posted that you had an N6 in your original post, I'd have helped you, because that's what I use
Click to expand...
Click to collapse
Oh That looks interesting. My Cellular signal sucks even though I am supposedly close to some towers. I am going to try using flashfire with these (hope I don't brick myself lol)
So I assume that when N comes out officially and I need to change bootloaders, I would do so via fasboot, then afterwards I can the the updates via fashfire.
RLBL said:
Oh That looks interesting. My Cellular signal sucks even though I am supposedly close to some towers. I am going to try using flashfire with these (hope I don't brick myself lol)
So I assume that when N comes out officially and I need to change bootloaders, I would do so via fasboot, then afterwards I can the the updates via fashfire.
Click to expand...
Click to collapse
all the radios, and bootloaders, are available in flashable zip for here on xda as well. to flash via twrp recovery
simms22 said:
all the radios, and bootloaders, are available in flashable zip for here on xda as well. to flash via twrp recovery
Click to expand...
Click to collapse
Cool... But I only used TWRP to flash the SU binaries to root. Now that I am rooted, I figured I could simply go back to stock recovery* and use flashfire going forward.
* I figured that because I had no other use for for a custom recovery presently, I may as well stay completely stock and rooted. Furthermore, from my understanding (which can be wrong) I no longer need a custom recovery to flash/install anything, as flashfire can do it all. Of course that brings one to ask "why am I rooted if I am staying stock?". I root my device so I can simulate a power button press without cancelling smart lock operations (either through tasker shell keyevent, gravity screen, or nova prime swipe gesture). I like not having to use the buttons on my phone
Why get rid of custom recovery? Just leave it and keep a backup on hand, then when there is an issue with basically anything you can just restore your backup instead of freaking out and running here using caps and exclamation marks asking how to fix.
scryan said:
Why get rid of custom recovery? Just leave it and keep a backup on hand, then when there is an issue with basically anything you can just restore your backup instead of freaking out and running here using caps and exclamation marks asking how to fix.
Click to expand...
Click to collapse
1 - why use a custom recovery if I do not need to (serious question, not being confrontational - see below)
2 - I totally know how to flash to whatever I want without using any toolkits (and ofc using a custom recovery)
3 - Why would one assume that one panics? (just because I have a low post count and admittedly an Android noob - N6 1st phone - does not mean I am an idiot)
4 - Considering I am not using custom ROMs and staying stock, I would think the likelihood of things going wrong is low (could be totally wrong there lol but I have done everything myself manually since the get go (never even taken an OTA for my upgrades), and never had 1 issue as of yet. This post was a general question in nature. It was not posted because I needed something to be fixed)
If I do not need it, why have it: I am experimenting to see if I can use FF completely stock (and rooted). Please provide some rationale as to why I should keep a custom recovery so I can evaluate (you may be 100% right). The point is: from my understanding one can use FF without a custom recovery so why not try... so far, so good.
On backups: be aware (not that you should care, but you did comment)... I have nothing on my phone that requires backing up at that... I can completely wipe the phone and it only takes time to do a google restore and I am back to where I am (been there, done that. Annoying for time though lol but I have no data on the phone safe from tasker profiles which are on my google drive and easily restored).
And what happens when you flash a bootloader and something screws up? You can't fix it from the stock recovery menu, now can you. So what not have something useful on the recovery partition for that 1 and 1000 chance something goes wrong.... Just my opinion, being I've been flashing phones since the first Android device was released on T-Mobile. The g1 (still have and still flash Roms
Sent from my Nexus 6 using XDA Free mobile app
RLBL said:
1 - why use a custom recovery if I do not need to (serious question, not being confrontational - see below)
2 - I totally know how to flash to whatever I want without using any toolkits (and ofc using a custom recovery)
3 - Why would one assume that one panics? (just because I have a low post count and admittedly an Android noob - N6 1st phone - does not mean I am an idiot)
4 - Considering I am not using custom ROMs and staying stock, I would think the likelihood of things going wrong is low (could be totally wrong there lol but I have done everything myself manually since the get go (never even taken an OTA for my upgrades), and never had 1 issue as of yet. This post was a general question in nature. It was not posted because I needed something to be fixed)
If I do not need it, why have it: I am experimenting to see if I can use FF completely stock (and rooted). Please provide some rationale as to why I should keep a custom recovery so I can evaluate (you may be 100% right). The point is: from my understanding one can use FF without a custom recovery so why not try... so far, so good.
On backups: be aware (not that you should care, but you did comment)... I have nothing on my phone that requires backing up at that... I can completely wipe the phone and it only takes time to do a google restore and I am back to where I am (been there, done that. Annoying for time though lol but I have no data on the phone safe from tasker profiles which are on my google drive and easily restored).
Click to expand...
Click to collapse
1. the only one important thing about having twrp installed.. backups and restores. before dlashing or changing anything, i akways create a backup in twrp. if something doesnt work out, you can always restore your backup, as ive done many many times. its a quicky fix it.
31ken31 said:
And what happens when you flash a bootloader and something screws up? You can't fix it from the stock recovery menu, now can you. So what not have something useful on the recovery partition for that 1 and 1000 chance something goes wrong.... Just my opinion, being I've been flashing phones since the first Android device was released on T-Mobile. The g1 (still have and still flash Roms
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I think that was the whole point of my post was it not? What happens if you DON'T flash a bootloader while using FF (but in the case where it did change)? And like I said, in the 1/1000 chance that something does go wrong and I did not have a backup: Flash the complete package via adb? Like I said, I have nothing to backup, thus nothing to recover. Not saying I shouldn't, just saying I don't. I only used TWRP to gain root access, nothing more (no custom ROMs, kernels, optimizations, anything on my phone...not even local app data saves - I am one of those old farts who uses their phone as a PDA with phone capabilities and that is it. All "data" is cloud based for calendar info etc.)
It was a relatively simple (general) question around some experimentation I am doing to see if it would work if one was completely stock (safe from root); did not think it would turn in an philosophical argument on whether or not one should use a stock recovery (which I have been using a custom up until yesterday, but was thinking about putting it back on this evening anyways, just because)
Anyways, got my answer... thx
simms22 said:
1. the only one important thing about having twrp installed.. backups and restores. before dlashing or changing anything, i akways create a backup in twrp. if something doesnt work out, you can always restore your backup, as ive done many many times. its a quicky fix it.
Click to expand...
Click to collapse
Thanks!... Obviously when I do venture into more with the phone I will do that. Currently it is a work and personal device so the only thing I do is flash Google stock builds instead of waiting for OTAs. Not saying I should not have a backup, but I don't. Only once after the 1st flash I re-locked the bootloader (as per instructions). What I waste of time; but it did show me that in a non-efficient disaster recovery, I can get everything back to where I was.
A restore would have been efficient, but I have found that I really have nothing to back up.. yet.
I guess a (off-topic) question I have for you is: What and Why did things not work out? In my case where I am only flashing stock loads (not waiting for OTAs), what could one anticipate going wrong that a re-flash could not recover from, but a restore could? Example a write corruption of a partition and the only thing I can do is boot into recovery as my PC cannot see the phone via adb? Can something like that happen?
Backing up system is what saves your a**
Sent from my Nexus 6 using XDA Free mobile app
31ken31 said:
Backing up system is what saves your a**
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
cool... but... what if you are stock? Save my ass from what? Will a (re)flash of stock binaries not suffice?
Look I appreciate I am sounding argumentative, but I am curious to understand what can happen and why. I can understand the "need" to do it if customizing a device etc... but I am very curious as to why if you are stock:
example:
A stock user unlocks his bootloader so they can flash files straight from google be it OTAs or the complete package. It is not listed anywhere to have a custom recovery in their instructions which would lead one to believe it is not required if flashing said files... I assume something could go wrong of course and the most efficient way is to do a restore from backup... but I also assume one could simply re-flash and start over.
I am not devaluating the merits of a custom recovery; I was just curious if one could use (easily) flash fire without one - and one can. The purpose of the question was two-fold:
- because I was flashing stock, then reflashing twrp to get root I found the process longer than it needed to be so I thought I could use flashfire and have it do it for me.
- then I realized that flashing re-roots as well so I did not need to flash the custom recovery to obtain root. I thought "hey what if I accidentally checked "recovery" and accidentally went back to stock. No harm done as I can move on and still be rooted.
Not sure my butt needs saving to ask. You may be doing something that having backups is a good and safe idea... what if you are not? No harm in still using a custom of course, but it was just a question (I ask such questions so I know in advance why something happened and what to do so I do not come running to forums in all caps as someone else said lol)
off topic: If one has nothing to backup, what is there to restore?
RLBL said:
cool... but... what if you are stock? Save my ass from what? Will a (re)flash of stock binaries not suffice?
Look I appreciate I am sounding argumentative, but I am curious to understand what can happen and why. I can understand the "need" to do it if customizing a device etc... but I am very curious as to why if you are stock:
example:
A stock user unlocks his bootloader so they can flash files straight from google be it OTAs or the complete package. It is not listed anywhere to have a custom recovery in their instructions which would lead one to believe it is not required if flashing said files... I assume something could go wrong of course and the most efficient way is to do a restore from backup... but I also assume one could simply re-flash and start over.
I am not devaluating the merits of a custom recovery; I was just curious if one could use (easily) flash fire without one - and one can. The purpose of the question was two-fold:
- because I was flashing stock, then reflashing twrp to get root I found the process longer than it needed to be so I thought I could use flashfire and have it do it for me.
- then I realized that flashing re-roots as well so I did not need to flash the custom recovery to obtain root. I thought "hey what if I accidentally checked "recovery" and accidentally went back to stock. No harm done as I can move on and still be rooted.
Not sure my butt needs saving to ask. You may be doing something that having backups is a good and safe idea... what if you are not? No harm in still using a custom of course, but it was just a question (I ask such questions so I know in advance why something happened and what to do so I do not come running to forums in all caps as someone else said lol)
off topic: If one has nothing to backup, what is there to restore?
Click to expand...
Click to collapse
its all a matter of choice, period.
flashing stock, you dont need to do anything. flashing different mods, custom roms, gapps, or supersu, you need to use twrp recovery. you can even flash twrp to be permenant or flash twrp for a one time use. if you are flashing custom roms/mods regularly, its convieniant to have twrp, if your not it doesnt matter. but the one thing twrp is great for is backing up, in case. and you dont need many back ups, just one recent backup. so you can back up, then get rid of twrp until needed again. anyways, its all a personal choice, and thats all it is. for me, flashing twrp then leaving it makes sense, since ill never ever do anything stock. for you, you have your own needs and wants.
simms22 said:
its all a matter of choice, period.
flashing stock, you dont need to do anything. flashing different mods, custom roms, gapps, or supersu, you need to use twrp recovery. you can even flash twrp to be permenant or flash twrp for a one time use. if you are flashing custom roms/mods regularly, its convieniant to have twrp, if your not it doesnt matter. but the one thing twrp is great for is backing up, in case. and you dont need many back ups, just one recent backup. so you can back up, then get rid of twrp until needed again. anyways, its all a personal choice, and thats all it is. for me, flashing twrp then leaving it makes sense, since ill never ever do anything stock. for you, you have your own needs and wants.
Click to expand...
Click to collapse
Thank you for answering the question.
I figure when this phone (or whichever phone) is not my daily driver and no longer linked to sensitive stuff I will start venturing into the domain of custom ROMs and Kernels.
RLBL said:
Thank you for answering the question.
I figure when this phone (or whichever phone) is not my daily driver and no longer linked to sensitive stuff I will start venturing into the domain of custom ROMs and Kernels.
Click to expand...
Click to collapse
custom recoveries just make things easier for you, overall, to do stuff. but kernels, that could be the bomb. but you will need to learn about how to use governors/schedulers to make any kind of headways. for example, i use a completely different governor/scheduler(ondemand/deadline) than any other nexus kernel, and i feel that my way makes my phone much better/faster than any other setup. and thats whats important to me
Update: test passed (I knew it would)
With a stock recovery, I was able to use flashfire and upgrade to the latest update and re-root.
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)