Related
AMAZON VARIANT NOW SUPPORTED!
NO PC REQUIRED AT ALL FOR THIS TUTORIAL!
READ ME: I am not responsible for bricked/damaged devices from following this procedure. It should be safe, if done right on the supported models. This does not void your warranty, but it is soak test firmware, meaning that it is beta software, and might have bugs/issues. I haven't noticed any myself, however.
Alright, I am aware that there are already videos describing how to install Nougat, but this is a (fairly) easy to follow text tutorial.
Step 1: Make sure your running the latest Marshmallow.
Before you can install the Nougat update, you have to make sure that you are running the latest Marshmallow firmware for your device. If your phone is running the MPJ24.139-63 firmware, you are good to go. Anything lower, and you will have to update your firmware, either manually, or through the OTA checker.
HAVE A NEWER FIRMWARE? (OR AMAZON VARIANT)
I had a link to a Reddit user's guide to do this, but they have apparently deleted their account, so I'll link this guide from XDA: http://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961
UPDATE: Download this file and flash it in recovery the same way that you install Nougat, to update to the latest Marshmallow firmware, if you are on anything lower than MPJ24.139-63: https://docs.google.com/uc?export=download&confirm=mkUs&id=0BzpjDRtfDv8PdER0cml3VzRHZTA
Step 2: Download the Nougat OTA File.
Follow this link to download the Nougat OTA file: http://downloadmirror.co/Uq5/Blur_Version.24.31.64.athene.retail.en.US.zip
Step 3: Boot into Recovery.
You have to boot into recovery to sideload this OTA file. First, power off the device completely. When it is completely powered down, hold the Volume Down button, and then the power button, not letting go of either button, until an Android appears, with a bunch of text. You are now in Fastboot Mode. Press the Volume Down button until you see Recovery Mode, then hit the power button.
Step 4: Install.
Once you are in Recovery, you may see an Android logo again, with the text "No Command" below it. What you need to do here is hold the power button, and whilst holding the power button, press Volume Up, to access the menu. It is easy from here. You need to select the option to install update from SD Card, using the Volume buttons for navigation, and Power to select. From there, you find where you downloaded the BLUR_VERSION.24.31.64.ATHENE.RETAIL.EN.US.ZIP file, and select it. It will start installing the official Nougat OTA. Give it some time, upwards of 15 minutes to install. Once it has complete, simply select the Reboot system now option, and if all went well, you should see the "Android is upgrading" screen, and now you are running official Nougat soak test on your G4.
NOTES - The install may hang on the "Patching system image after verification." message. Give it around 5-10 minutes, it will eventually pass that stage.
I can't guarantee that this method will work on all G4 variants. I can confirm it works on a UK Retail XT1622, however.
This may make it harder to install the stable official Nougat when that releases worldwide, I am not sure yet if it affects the upgrade path to the stable firmware.
KNOWN ISSUES
I actually have not found any issues with this firmware yet, it appears VERY stable for a soak test build. If you have come across any, or need help, comment below.
COMPATIBLE MODELS
These models have said to have had success with this update.
XT1643 - Moto G4 Plus Dual-SIM (India)
XT1640 - Moto G4 Plus Dual-SIM (Brazil)
XT1642 - Moto G4 Plus
XT1622 - Moto G4
XT1626 - Moto G4 (India)
DOWNGRADE TO MM FOR OFFICIAL NOUGAT OTA WITHOUT BOOTLOADER UNLOCK
Follow this guide from the Moto G4 Plus XDA section to downgrade your G4 to Marshmallow to install the official Nougat OTA:
https://forum.xda-developers.com/moto-g4-plus/how-to/install-official-firmware-soak-test-t3531296
Welp, can't apply the MPJ24.139-63 update on XT1621 lol
Does it work on the xt1625 non amazon, MPJ24.139-64 ?
traceable ? (sorry not good at this title thing)
Hey thanks for sharing this.
I just wanted to ask whether or not Motorola/their repair service will be able to tell if I applied this update (meaning if I roll back to older firmwear without unlocked bootloader), since I sent my Moto G4 in for a repair but apparently since it came back yesterday the issues came back.
So I just want to make sure whether I can try this without them blaming it on me "flashing unfinished software" once I'll send it back for a repair/replacement
Thanks in advance
Yoloswaggerboy69 said:
Hey thanks for sharing this.
I just wanted to ask whether or not Motorola/their repair service will be able to tell if I applied this update (meaning if I roll back to older firmwear without unlocked bootloader), since I sent my Moto G4 in for a repair but apparently since it came back yesterday the issues came back.
So I just want to make sure whether I can try this without them blaming it on me "flashing unfinished software" once I'll send it back for a repair/replacement
Thanks in advance
Click to expand...
Click to collapse
They dont seem to care, they just reflash and send it back.
Rempala said:
They dont seem to care, they just reflash and send it back.
Click to expand...
Click to collapse
Thanks a bunch
Cyberneticx said:
Does it work on the xt1625 non amazon, MPJ24.139-64 ?
Click to expand...
Click to collapse
It does not. It checks your current firmware version and that one is too NEW. I have the same. I got this: http://i.imgur.com/ggmBiMZ.jpg
Cyberneticx said:
Does it work on the xt1625 non amazon, MPJ24.139-64 ?
Click to expand...
Click to collapse
mattgoldey said:
It does not. It checks your current firmware version and that one is too NEW. I have the same. I got this: http://i.imgur.com/ggmBiMZ.jpg
Click to expand...
Click to collapse
I have added a way to downgrade your firmware to install the update.
LoopingCreeper said:
I have added a way to downgrade your firmware to install the update.
Click to expand...
Click to collapse
Do I have to root the phone to downgrade?
I went to the link and I think it was a different version.
I bought mine on the motorola store and it's a custom phone. It came as xt1625 but there is no amazon nor anyother thing on it
Cyberneticx said:
Do I have to root the phone to downgrade?
I went to the link and I think it was a different version.
I bought mine on the motorola store and it's a custom phone. It came as xt1625 but there is no amazon nor anyother thing on it
Click to expand...
Click to collapse
You don't have to root or unlock your bootloader or anything like that. I believe that G4 and G4+ ROMs are interchangeable.
LoopingCreeper said:
I have added a way to downgrade your firmware to install the update.
Click to expand...
Click to collapse
That reddit post is deleted and the person that posted it deleted their account. Not sure I'd be comfortable downgrading now.
Can anyone confirm XT1621? Would it be safe to bet that it'll work if XT1622 is working?
Thank You, i have MOTO G4 with Nougat,
no need to downgrade the bootloder because i was on MPJ24.139-63, this worked with XT1622 - Moto G4 bought from Romania.
"Patching system image after verification" was like 15 minutes and when i choose reboot the led in the bottom of phone was flashing,(strange, i was reading about this led on xda) i hope will function in Nougat .
this does not work in any way shape or form with the XT1625 retail or amazon variants.
If I were upgrading from stock marshmallow to stock nougat and not performing a factory reset I would completely understand why i need to be on the latest version. However, I'm coming from a cm based ROM and will have to do a factory reset anyways. The firmware file includes the most up to date bootloader, soooo why do I need to flash -63 before flashing -64? Is there something I'm missing here or am I correct?
(I'm on Retus XT1625, non Amazon prime variant with an unlocked bootloader)
Travisholt92 said:
If I were upgrading from stock marshmallow to stock nougat and not performing a factory reset I would completely understand why i need to be on the latest version. However, I'm coming from a cm based ROM and will have to do a factory reset anyways. The firmware file includes the most up to date bootloader, soooo why do I need to flash -63 before flashing -64? Is there something I'm missing here or am I correct?
(I'm on Retus XT1625, non Amazon prime variant with an unlocked bootloader)
Click to expand...
Click to collapse
short answer to your question: the nougat ROM looks for a -63 boot image, and also verifies against baseband versions.
it doesn't matter though, because the Nougat ROM linked herein will not work on a XT1625. i have spent hours trying to make it happen.
trevorcobb said:
it doesn't matter though, because the Nougat ROM linked herein will not work on a XT1625. i have spent hours trying to make it happen.
Click to expand...
Click to collapse
What error are you getting when you try and flash it? I tried, but my firmware version was newer than the expected version, so it refused to flash.
I tried this on a locked bootloader with XT1625 amazon prime phone.
I am getting the error This package expects the value "athene" for "ro.product.name" or "athene" for "ro.product.name" on the OEM partition; But the actual value are "athene_amz""athene_amz"
It'll probably work on the non-Amazon version, then.
I have Adoptable Storage and the ZIPs don't show up in the SD card. Is it safe to swap to another card temporary to do the update?
Hello guys this guide is for who want to root phone without disabling ota updates.
(BOOTLOODER SHOULD BE UNLOCK)
BIG THANKS FOR MAKING PATCHED BOOT IMg @Jan.Pul
IAM NOT RESPONSIBLE FOR ANY CAUSE OF YOUR DEVICE DO IT ON OWN RISK)
1)Download patched boot.img from link below
2)copy that patched boot.img to your adb folder
3) adb debugging should be on and oem unlock should be on for unlock bootlooder
4)turn off your device and go into fastboot mode by pressing holding volume down and power key
5) check whether fastboot detect your device or not by typing this command on (cmd) FASTBOOT DEVICES
6) if fastboot shows that your device is connected your good to go
7) you need to boot into patched boot.img for this type a command FASTBOOT BOOT patched_boot.img your device will boot automatically
8) download magisk manager apk from google and. Open ur magisk manager and install ad direct method and reboot
If you get bootloop dont worry just press your power key for 5sec it will boot automatically
PATCH BOOT IMG : https://drive.google.com/file/d/1cU6qOMiHlGdSAbRtMVgTlHummcGksnt6/view?usp=drivesdk
Guessing this is for the Indian/Chinese version and the bnd-l24 is still sitting on the shelf? And rooting without making a backup isn't usually the smartest thing to do but we all know that.
Is there a source this came from by any chance?
Yes..But Why?
maximran said:
maximran said:
this guide is for who want to root phone without disabling ota updates.
(IAM NOT RESPONSIBLE FOR AMY CAUSE OF YOUR DEVICE DO IT ON OWN RISK)
Click to expand...
Click to collapse
str8stryk3r said:
rooting without making a backup isn't usually the smartest thing to do but we all know that.
Is there a source this came from by any chance?
Click to expand...
Click to collapse
I Eh... Would Love To See This Happen..
I'm... still at a loss to understand why so many people want to root the 7x... Now?
There is an adaway substitute available... ( Search it if you care to ) no root needed.
You can adjust DPI...
You have Themes....
You can remove apps from user view... ( Search it if you care to )
And.... removing unwanted apps WILL NOT free up more RAM.. RAM Management will just fill the allotted space with something else...
You need to make a backup ??? Eh.... Your Stock Software WILL NOT FAIL Unless you are in there messing with it or, are installing illegal apps that are cancering your unit.
Battery Management apps like Greenify? really? how many of you even have to use the Power Saving options already installed in the 7x? I'm getting a day and a half easy.. without using any of the Power Saving options.. YMMV of course.
Oreo is 3 to 4 weeks away.
There still, is No Stock Image Available from Honor to turn to should your Rooting efforts fail you.
So, What possible benefits are you getting by Rooting Nougat Now..
It's YOUR device.. and I wish you the best of luck should you find a reason that you feel justifies the need to root right now..
I'm going to Root my 7x as well... once a Stock Image is available from Honor and, EMUI / OREO 8.0 , The Updated Security Patch and Facial Unlock / AR options are delivered.. That will hold me for the 6 - 7 months I'll own the 7x.
I am just so curious why so many would gamble with Root.. with no clear cut method of being able to recover from a catastrophe.... and no real benefit at this time.
Click to expand...
Click to collapse
RaiderWill said:
maximran said:
I Eh... Would Love To See This Happen..
I'm... still at a loss to understand why so many people want to root the 7x... Now?
There is an adaway substitute available... ( Search it if you care to ) no root needed.
You can adjust DPI...
You have Themes....
You can remove apps from user view... ( Search it if you care to )
And.... removing unwanted apps WILL NOT free up more RAM.. RAM Management will just fill the allotted space with something else...
You need to make a backup ??? Eh.... Your Stock Software WILL NOT FAIL Unless you are in there messing with it or, are installing illegal apps that are cancering your unit.
Battery Management apps like Greenify? really? how many of you even have to use the Power Saving options already installed in the 7x? I'm getting a day and a half easy.. without using any of the Power Saving options.. YMMV of course.
Oreo is 3 to 4 weeks away.
There still, is No Stock Image Available from Honor to turn to should your Rooting efforts fail you.
So, What possible benefits are you getting by Rooting Nougat Now..
It's YOUR device.. and I wish you the best of luck should you find a reason that you feel justifies the need to root right now..
I'm going to Root my 7x as well... once a Stock Image is available from Honor and, EMUI / OREO 8.0 , The Updated Security Patch and Facial Unlock / AR options are delivered.. That will hold me for the 6 - 7 months I'll own the 7x.
I am just so curious why so many would gamble with Root.. with no clear cut method of being able to recover from a catastrophe.... and no real benefit at this time.
Click to expand...
Click to collapse
Oh I agree with ya. I'm not fooling with mine until a definitive stable method comes out after oreo. I might even hold off until we start getting some custom rooms and kernels. I've unlocked my bootloader and that's about the extent of my Honor 7x modding for the time being.
Click to expand...
Click to collapse
A Question Sir..
str8stryk3r said:
RaiderWill said:
Oh I agree with ya. I'm not fooling with mine until a definitive stable method comes out after oreo. I might even hold off until we start getting some custom rooms and kernels. I've unlocked my bootloader and that's about the extent of my Honor 7x modding for the time being.
Click to expand...
Click to collapse
Have You Tried "Re-Locking" Your Bootloader.. And Then Doing A Factory Reset?
Just asking because.. I thought.. (And I Could Be 100% WRONG) I read somewhere that, relocking using the command line causes the 7x to brick..
Click to expand...
Click to collapse
RaiderWill said:
str8stryk3r said:
Have You Tried "Re-Locking" Your Bootloader.. And Then Doing A Factory Reset?
Just asking because.. I thought.. (And I Could Be 100% WRONG) I read somewhere that, relocking using the command line causes the 7x to brick..
Click to expand...
Click to collapse
No I unlocked the bootloader so I wouldn't have to in the future. Why, bootloader unlocking China cause me to not be able to do ota updates? I was under the impression that only rooting and installing twrp would cause issues with ota but I could've read wrong
Click to expand...
Click to collapse
@maximran, root with Magisk "KEEPFORCEENCRYPT=true"; but if I change to "false", should work too?
str8stryk3r said:
RaiderWill said:
No I unlocked the bootloader so I wouldn't have to in the future. Why, bootloader unlocking China cause me to not be able to do ota updates? I was under the impression that only rooting and installing twrp would cause issues with ota but I could've read wrong
Click to expand...
Click to collapse
True, even I have unlocked my bootloader but I still received OTA.
Click to expand...
Click to collapse
kilroystyx said:
@maximran, root with Magisk "KEEPFORCEENCRYPT=true"; but if I change to "false", should work too?
Click to expand...
Click to collapse
It will not work
Interesting!
str8stryk3r said:
RaiderWill said:
No I unlocked the bootloader so I wouldn't have to in the future. Why, bootloader unlocking China cause me to not be able to do ota updates? I was under the impression that only rooting and installing twrp would cause issues with ota but I could've read wrong
Click to expand...
Click to collapse
Asder.mko said:
str8stryk3r said:
True, even I have unlocked my bootloader but I still received OTA.
Click to expand...
Click to collapse
Really ?
Please.. let me know once the update arrives.
I've NEVER seen a Signed O.T.A. software update package walk through the front door of a device with an Unsecured Bootloader.
Aren't you guys getting the "Exclamation Warning" screen when you first boot up letting you know your device is officially "Unsecure" ?
I'm not rooting Nougat.. just curious.. you normally get an "Update Failed!" message.. Thanks!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
RaiderWill said:
str8stryk3r said:
Asder.mko said:
Really ?
Please.. let me know once the update arrives.
I've NEVER seen a Signed O.T.A. software update package walk through the front door of a device with an Unsecured Bootloader.
Aren't you guys getting the "Exclamation Warning" screen when you first boot up letting you know your device is officially "Unsecure" ?
I'm not rooting Nougat.. just curious.. you normally get an "Update Failed!" message.. Thanks!
Click to expand...
Click to collapse
Well, I got the OTA in December itself but since I had rooted and installed twrp recovery, I wasn't able to install the update.
Yes, we get that " your device is not secure... Blah blah blah..."
Click to expand...
Click to collapse
Click to expand...
Click to collapse
RaiderWill said:
str8stryk3r said:
Asder.mko said:
Really ?
Please.. let me know once the update arrives.
I've NEVER seen a Signed O.T.A. software update package walk through the front door of a device with an Unsecured Bootloader.
Aren't you guys getting the "Exclamation Warning" screen when you first boot up letting you know your device is officially "Unsecure" ?
I'm not rooting Nougat.. just curious.. you normally get an "Update Failed!" message.. Thanks!
Click to expand...
Click to collapse
Before I went ahead an unlocked my bootloader I checked as many sources as I could about if whether or not I'd still be able ota update and the vast majority of the things I read states that what causes the update to fail is not having stock rom and not having stock recovery. The bootloader being unlocked doesn't modify those or any system files so everything should be fine. Unless Huawei changed things specifically for our Honor 7x then there shouldn't be any problems with ota updates. I guess I'll find out when the L24 people start saying they got updates and I don't receive it or can't install it
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Well, that's quite right. I don't know whether Huawei/Honor implemented THAT thing, but yeah reverting back to stock conditions wand applying OTA wouldn't be an issue!
( P.S - I'm stuck here too as I have OTA update since December but haven't reverted to stock to install it. I don't yet know properly about manual installation! )
(I haven't received my 7x yet and I haven't had any recent experience with Huawei OTA updates and I am not advocating that anyone should alter their phones in any way which would void their warranties... )
However, I was surprised to hear in this forum that Huawei has made things more restrictive since the Mate2. Given that you can still obtain bootloader unlock codes (and the only reason AFAIK is to allow you to flash a new recovery) and that Huawei has publicly committed to open-source and has given 7x's to developers, it seems contrary to a "lockdown" philosophy. Rather, it would appear as they are still encouraging 3rd party development to prolong product lifespan in order to attract cheapskates like me who still use a 4-year old phone.
Things may have changed but In order to get OTA updates, here were some of the issues on the Mate2 :
Some people had a difficult time obtaining the bootloader unlock codes. Either you can get a code or you couldn't. Without an unlocked bootloader, you can't flash a different recovery.
You "can't" flash TWRP. That's not entirely true. You needed to restore the appropriate version of Huawei recovery before each OTA, because update.zip can only be interpreted by the appropriate recovery. (Think format differences between CWM and TWRP.)
You were able to root and still obtain OTA. (Albeit, there was only one OTA. The rest had to be downloaded to SD and flashed. But that was okay back then 'cause no one outside of China really knew about Huawei.) The updates weren't checking whether you had modified the existing software or not. Once you've voided your warranty, Huawei didn't care if you then decide to then make your phone more vulnerable or accidentally brick it. The problem was that the update could fail if you remove a piece of bloatware that Huawei decided to update. (The folders would be missing for example. And the update would not recover gracefully.)
But a big THANKS to previous posters which reminded me to backup everything (basically as soon as I receive my 7x).
Oh....if you are flashing a custom recovery, you should also backup the "stock" recovery after each OTA update. Sometimes the recovery is also updated. (That's what I meant by "appropriate" version.)
iammudd said:
(I haven't received my 7x yet and I haven't had any recent experience with Huawei OTA updates and I am not advocating that anyone should alter their phones in any way which would void their warranties... )
However, I was surprised to hear in this forum that Huawei has made things more restrictive since the Mate2. Given that you can still obtain bootloader unlock codes (and the only reason AFAIK is to allow you to flash a new recovery) and that Huawei has publicly committed to open-source and has given 7x's to developers, it seems contrary to a "lockdown" philosophy. Rather, it would appear as they are still encouraging 3rd party development to prolong product lifespan in order to attract cheapskates like me who still use a 4-year old phone.
Things may have changed but In order to get OTA updates, here were some of the issues on the Mate2 :
Some people had a difficult time obtaining the bootloader unlock codes. Either you can get a code or you couldn't. Without an unlocked bootloader, you can't flash a different recovery.
You "can't" flash TWRP. That's not entirely true. You needed to restore the appropriate version of Huawei recovery before each OTA, because update.zip can only be interpreted by the appropriate recovery. (Think format differences between CWM and TWRP.)
You were able to root and still obtain OTA. (Albeit, there was only one OTA. The rest had to be downloaded to SD and flashed. But that was okay back then 'cause no one outside of China really knew about Huawei.) The updates weren't checking whether you had modified the existing software or not. Once you've voided your warranty, Huawei didn't care if you then decide to then make your phone more vulnerable or accidentally brick it. The problem was that the update could fail if you remove a piece of bloatware that Huawei decided to update. (The folders would be missing for example. And the update would not recover gracefully.)
But a big THANKS to previous posters which reminded me to backup everything (basically as soon as I receive my 7x).
Oh....if you are flashing a custom recovery, you should also backup the "stock" recovery after each OTA update. Sometimes the recovery is also updated. (That's what I meant by "appropriate" version.)
Click to expand...
Click to collapse
My thoughts exactly. Why would they provide they website to unlock the bootloader if that kept ota updates from going through. The only thing that's really holding back the development of this device is Huawei hasn't released the full stock firmware package yet. I have the L24 version so it's exciting seeing L21/A10 making some progress because it's only a matter of time until things start to kick off all around.
str8stryk3r said:
My thoughts exactly. Why would they provide they website to unlock the bootloader if that kept ota updates from going through. The only thing that's really holding back the development of this device is Huawei hasn't released the full stock firmware package yet. I have the L24 version so it's exciting seeing L21/A10 making some progress because it's only a matter of time until things start to kick off all around.
Click to expand...
Click to collapse
No need for full fw broh need vendor partitions, device tree, kernel sources
maximran said:
No need for full fw broh need vendor partitions, device tree, kernel sources
Click to expand...
Click to collapse
Lmao, and that's why I'm not a developer. I just know having the stock image files is important so that when something gets screwed up got have something to fall back on.
Bringing Up The Rear...
Asder.mko said:
Yes, we get that " your device is not secure... Blah blah blah..."
Click to expand...
Click to collapse
That Answers My Question As To Wether Or Not You Do See The Unsecure Msg..
Anyway.. Great Discussion.
Fact or Fiction... who will get the updates via O.T.A. ? The Non-Rooted, The Rooted.. or Both.
Even with Project Treble... will this device ever take off with Developer support ?
Will Huawei / Honor release a stock image of Nougat and Oreo ? ( Eh, Honor.. it's been 60 days since Kernel source was released.. and you know people are Rooting away.. why have you not released the stock Nougat image for the 7x?) and don't use working on EMUI & OREO as an excuse.. that's simply not good enough.. :angel:
I'm going to enjoy laying back... and watching how this unfolds.
Re-Reading my own words, as to what is the motivation for everyone Rooting Nougat now.. and what is anyone getting out of doing it.. because so much of what you would normally do with Admin Access is already incorperated into the 7x.. is there really a need to even Root whats coming without something like a Stable Linage / Franco Kernel combo ROM available vs a 100% stable Factory Fresh EMUI / Oreo 8.0 setup.
For me, it will be a fun to see what key Developers, ROM's and support in general.. the 7x actually gets.. and at what point they release firmware for restoration purposes.
You Just Never Know.
RaiderWill said:
That Answers My Question As To Wether Or Not You Do See The Unsecure Msg..
Anyway.. Great Discussion.
Fact or Fiction... who will get the updates via O.T.A. ? The Non-Rooted, The Rooted.. or Both.
Even with Project Treble... will this device ever take off with Developer support ?
Will Huawei / Honor release a stock image of Nougat and Oreo ? ( Eh, Honor.. it's been 60 days since Kernel source was released.. and you know people are Rooting away.. why have you not released the stock Nougat image for the 7x?) and don't use working on EMUI & OREO as an excuse.. that's simply not good enough.. :angel:
I'm going to enjoy laying back... and watching how this unfolds.
Re-Reading my own words, as to what is the motivation for everyone Rooting Nougat now.. and what is anyone getting out of doing it.. because so much of what you would normally do with Admin Access is already incorperated into the 7x.. is there really a need to even Root whats coming without something like a Stable Linage / Franco Kernel combo ROM available vs a 100% stable Factory Fresh EMUI / Oreo 8.0 setup.
For me, it will be a fun to see what key Developers, ROM's and support in general.. the 7x actually gets.. and at what point they release firmware for restoration purposes.
You Just Never Know.
Click to expand...
Click to collapse
People like to root and mod their own devices for their own reasons but you're right, a lot of the reasons I modded past devices was because the roms almost always ran better than stock but the 7x imho runs great. Used to be kernels for better battery life and such. I like custom roms because I like to be able to do certain things that stock roms limited as far as customizing goes. A lot of people hate bloat and end up deleting every file on the phone that isn't necessary or to their liking to make the rom as minimal as possible.
But as of now I'm happy with the phone and don't feel the urge to need to root and and a custom recovery. The roms that eventually come would have to offer something worthwhile to flash. But hell, that's subject to change given how I'm feeling that day lol. There's a new AOSP based rom in another thread that sounds promising
RaiderWill said:
Will Huawei / Honor release a stock image of Nougat and Oreo ? ...
Re-Reading my own words, as to what is the motivation for everyone Rooting Nougat now.. and what is anyone getting out of doing it.. because so much of what you would normally do with Admin Access is already incorperated into the 7x..
Click to expand...
Click to collapse
I assume that you already know this ... but I should mention it for others that you can run TWRP (if there is a version for one's phone) without flashing it. (I don't have my 7x yet, so I prob really shouldn't be trying to give detailed instructions anyways.) From there, you can make backups of the stock image, stock recovery, etc. (So thx again to this forum for reminding me that I should backup all stock images as soon as I receive my 7x so that MY fingerprints are not all over the backups.)
As to rooting, there ARE at least 2 things that Huawei hasn't provided without root:
Yes, I can make app backups (and/or use the Huawei "easy transfer"... not sure what app that is at the moment) but I'd assume that I won't be able to transfer it to a non-Huawei device. That's why I continue to use Titanium Backup.
USB Mass Storage Enabling (and by extension Selinux Passive mode). I want fast transfer to my desktop, etc.... and I want a drive-letter (yes, there are Win programs which only work with drive letters). Without UMS, I haven't found a way to do that.
FOR MOTO G7 PLUS ONLY!!!
Hello, everyone.
I created a .bat file "executable " For those who want to flash the stock rom on your Moto G7 Plus.
Just put it in the stock Rom folder along with the fastboot files and run the file.
For those who want the file, just download it by the following link or download the file that is on the thread.
http://www.mediafire.com/file/q836uaerr17pn0f/Flash_ROM_G7%252B.zip/file
Could you share where to get the Stock ROM fein?
---------- Post added at 11:13 PM ---------- Previous post was at 10:25 PM ----------
Tried the same sequence with a Stock ROM last week, but didn't achieve to get back to original ROM. I always get the prompt in the initial boot, that a different OS is installed than the original. This has the consequence that I cannot upgrade wit OTA anymore. And there is an upgrade already available (Jan security patch)
moto g7 G7........
any one have a flash rom.bat stock rom for moto g7.......
Which stock rom did you flash on your Moto g7 plus?
Where can I find the stock rom?
Nes.
NesNol said:
Where can I find the stock rom?
Nes.
Click to expand...
Click to collapse
Didn't you just find it yesterday on the telegram group?
What was the problem that you asked again here today?
Latest Stock ROM RETAIL at that link is the one we have all been using.
You'll need to download it to a computer, unzip it in a folder with the fastboot/ADB files, then fastboot flash it with phone attached in bootloader mode.
NesNol said:
Where can I find the stock rom?
Nes.
Click to expand...
Click to collapse
You have a model of the XT1965-3 smartphone and region of the software is reteu? Then this your last firmware.
"Your device has loaded a different operating system."
baikal0912 said:
You have a model of the XT1965-3 smartphone and region of the software is reteu? Then this your … .
Click to expand...
Click to collapse
Thank you very much!
I guess that the software channel was reteu.
A second moto g7 phone I bought - and is unmodified - says "software channel: reteu".
The information on the package of my phone says XT1965-3.
I flashed this image already, the result is a 'working' system except for the message at the start "Your device has loaded a different operating system." .
NesNol said:
Thank you very much!
I guess that the software channel was reteu.
A second moto g7 phone I bought - and is unmodified - says "software channel: reteu".
The information on the package of my phone says XT1965-3.
I flashed this image already, the result is a 'working' system except for the message at the start "Your device has loaded a different operating system." .
Click to expand...
Click to collapse
This will get rid of that message we all got too:
[Bootlogo] Modded Bootlogo from unlocked bootloader
The new RETEU stock version was just updated in last few days, before that not available and you could have used the RETAIL channel that I mentioned above, it worked fine for several users on RETEU channel.
Dahenjo said:
This will get rid of that message we all got too:
The new RETEU stock version was just updated in last few days, before that not available and you could have used the RETAIL channel that I mentioned above, it worked fine for several users on RETEU channel.
Click to expand...
Click to collapse
Get rid of the message?
Does that also mean that OTAs will work? That banking apps will not complain about the integrity of the system?
Thanks!
NesNol said:
Get rid of the message?
Click to expand...
Click to collapse
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
After unlocking bootloader there is some message like this on starting device, keep in mind we all got these too and everything is fine but we like to cover it up with a different bootlogo, just looks better that is its only purpose. This message is because you also upgraded the firmware, meaning it's not really a different OS but only a different version of your correct OS.
Does that also mean that OTAs will work? That banking apps will not complain about the integrity of the system?
Click to expand...
Click to collapse
For G7 Plus we are not getting the OTAs properly after unlocking or rooting, I was originally rooted on PPW29.98-28 and repeatedly got the notifications of upgrading to 29.98-66-2 but it kept failing, the only way to stop it was freezing the Moto Update Process using Titanium Backup. So my only remaining option to upgrade was to fastboot flash the full firmware, as you just did, it wipes your data but gets you to the same place.
With future updates we may be able to capture them and then a dev can make them into a TWRP flashable zip with no wiping of internal data. We had that on G5 Plus which was a nice thing and they are still doing that. But until that might happen the best we can do is the same for now - when your channel has an update just get it from lolinet (these are all official stock firmwares there) and fastboot flash after backing up your data.
Usually it is more from the rooting (if you did that too) that may mess up your banking or other apps, but in Magisk there are settings that may work on that, you'll just have to try and see but there are mixed results. My choice is to not use banking apps on my devices anyway even if not unlocked or rooted, I just do it from home on a computer that I won't forget and leave out in public somewhere. :crying:
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
…
…
Click to expand...
Click to collapse
Hi,
thank you very much for your elaborate answer!
I will come back on it soon.
Nes
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
After unlocking bootloader there is some message like this on starting device, keep in mind we all got these too and everything is fine but we like to cover it up with a different bootlogo, just looks better that is its only purpose. This message is because you also upgraded the firmware, meaning it's not really a different OS but only a different version of your correct OS.
For G7 Plus we are not getting the OTAs properly after unlocking or rooting, I was originally rooted on PPW29.98-28 and repeatedly got the notifications of upgrading to 29.98-66-2 but it kept failing, the only way to stop it was freezing the Moto Update Process using Titanium Backup. So my only remaining option to upgrade was to fastboot flash the full firmware, as you just did, it wipes your data but gets you to the same place.
With future updates we may be able to capture them and then a dev can make them into a TWRP flashable zip with no wiping of internal data. We had that on G5 Plus which was a nice thing and they are still doing that. But until that might happen the best we can do is the same for now - when your channel has an update just get it from lolinet (these are all official stock firmwares there) and fastboot flash after backing up your data.
Usually it is more from the rooting (if you did that too) that may mess up your banking or other apps, but in Magisk there are settings that may work on that, you'll just have to try and see but there are mixed results. My choice is to not use banking apps on my devices anyway even if not unlocked or rooted, I just do it from home on a computer that I won't forget and leave out in public somewhere. :crying:
Click to expand...
Click to collapse
So you expect that in future my phone will be OK again? And receive OTAs while having Magisk installed.
I tried indeed to Magisk my phone, as I did with my old OnePlus One.
Which leads to TWRP, but then I discovered that the recovery has disappeared on this Moto!?
Then I was lost, and read about A/B and treble(?).
Concerning the banking applications: Even if I handle the banking transactions on my Mac, I still need the banking app on my phone for authentication.
Which is also true for accessing my medical data (GP, hospitals, etc), insurance companies, taxes, etc.
Last question: Is there a full description of how to magisk my phone?
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
…
…
…
…
Click to expand...
Click to collapse
I have replied to this messages twice.
None has arrived?!
Nes
---------- Post added at 01:34 PM ---------- Previous post was at 01:33 PM ----------
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
…
…
…
…
Click to expand...
Click to collapse
I have replied to this message twice.
None has arrived?!
Nes
NesNol said:
So you expect that in future my phone will be OK again? And receive OTAs while having Magisk installed.
I tried indeed to Magisk my phone, as I did with my old OnePlus One.
Which leads to TWRP, but then I discovered that the recovery has disappeared on this Moto!?
Then I was lost, and read about A/B and treble(?).
Concerning the banking applications: Even if I handle the banking transactions on my Mac, I still need the banking app on my phone for authentication.
Which is also true for accessing my medical data (GP, hospitals, etc), insurance companies, taxes, etc.
Last question: Is there a full description of how to magisk my phone?
Click to expand...
Click to collapse
Sorry not to reply yet, I sometimes have other things going on besides my phone. Also I thought I gave you a good answer on the situation, based on what I know as just another user (not a dev, not with Moto).
Yes, there have been changes since your last phone, it was the same for me. So it's good to find out as much as possible before deciding to unlock & root again, because the results may not be like before. We used to unlock and flash TWRP directly but we can't do that now or maybe brick the phone. It is always the risk when choosing not to remain fully stock/locked/etc as when you bought it, and with that is a responsibility to do the research first and not just expect other users to tell you every step.
So I don't know if things will change, but for now we can't get OTAs anymore after unlocking. For me I didn't mind and I am willing to upgrade manually if that let's me work with the device the way I like with root & using custom ROMs etc. I didn't plan to ever go back to how I bought it and don't need banking apps or other types that rooting might mess up. For others that may not be the case so they must learn the situation then decide for themselves.
As for installing Magisk, now we have TWRP working enough to just put the Magisk zip on your SD card and install it in TWRP. Before we had a functional TWRP we had another method by installing Magisk Manager and using it to patch the boot.img then fastboot flash that, but it's not needed anymore since TWRP, just do it the old way now.
Flashing the roms from lolinet, in my case ( RETEU[/URL) is a complete reset of the phone, I assume.
To flash, these steps should be right:
Copying the firmware to sdcard.
Boot in TWRP
Flashing the lolinet firmware.
Delete Dalvik Cache.
Should TWRP and Magisk be reinstalled immedeately after this procedure? Or renew the developer mode, reinstall twrp and magisk?
Woif said:
Flashing the roms from lolinet, in my case RETEU is a complete reset of the phone, I assume.
To flash, these steps should be right:
Copying the firmware to sdcard.
Boot in TWRP
Flashing the lolinet firmware.
Delete Dalvik Cache.
Should TWRP and Magisk be reinstalled immedeately after this procedure? Or renew the developer mode, reinstall twrp and magisk?
Click to expand...
Click to collapse
It won't work to flash full firmware in TWRP, so far the only way is using fastboot with phone connected to a computer in bootloader (unlocked) mode. Unzip firmware into your fastboot/ADB folder and also the batch file available in this thread, then run the batch file.
Yes this will reset/wipe your phone (except for SD) so backup your data first, and it will be like when you first bought it. You can reinstall TWRP and then Magisk, but boot to system first and set things up including enabling USB debugging setting in developer options again.
I am going to try and update now as the notifications are much too annoying.
Moto G7 Plus - lake Stock rom / firmware download here
NesNol said:
Where can I find the stock rom?
Nes.
Click to expand...
Click to collapse
Moto G7 Plus - lake
Download the Moto G7 Plus - lake stock firmware according to the Country/region/retail/carrier for example US Retail > T-Mobile, Verizon or Amazon, and everything is flashed through fastboot mode
XT1965-2 > https://boycracked.com/2019/02/11/official-motorola-moto-g7-plus-xt1965-2-stock-rom/
XT1965-3 > https://boycracked.com/2019/02/11/official-motorola-moto-g7-plus-xt1965-3-stock-rom/
XT1965-4 > https://boycracked.com/2019/02/11/official-motorola-moto-g7-plus-xt1965-4-stock-rom/
XT1965-6 > https://boycracked.com/2019/07/26/official-motorola-moto-g7-plus-xt1965-6-lake_retcn-stock-rom/
XT1965-9 > https://boycracked.com/2019/07/26/official-motorola-moto-g7-plus-xt1965-9-lake-stock-rom/
XT1965-T > https://boycracked.com/2019/07/26/o...-g7-plus-xt1965-t-lake-us-t-mobile-stock-rom/
Remove the line
'fastboot erase userdata'
from the flashROM.bat file and it won't factory reset. It will act like an upgrade.
Sent from my Moto Z (2) using XDA Labs
vickbuitenzorg said:
Moto G7 Plus - lake
Download the Moto G7 Plus - lake stock firmware according to the Country/region/retail/carrier for example US Retail > T-Mobile, Verizon or Amazon, and everything is flashed through fastboot mode
Click to expand...
Click to collapse
Can I use a different retail code than current stock? My phone is XT1965-2, PPW29.98-28, RETLA. The system reminders are all in Spanish. Could I update to PPW29.98-66, EEGB (UK English) without a problem?
Also, if this is possible, could I update by removing the 'fastboot erase userdata' line from the BAT file, or, due to the language change, would I need to leave that line and do a factory reset?
Hi,
I tried to upgrade my US998 from Oreo to Pie using LGUP patched. The upgrade process went well until the phone restarted and have this error message:
"Your device has failed a routine safety check and will not boot..."
I did try using LG Bridge to fix = not working
I did try fastboot boot laf.img (using extracted laf from H93031a_00_OPEN_EU_OP_1105) not working.
Any other solution?
Thanks
This Post got recommended to me. I am a Samsung user so my answer will probably be very stupid.
If you have fastboot, why don't you flash a recovery and a custom rom? Ik stupid but it's the only thing that comes to my mind since i don't have a LG phone lol
JanBoyGamer23 said:
This Post got recommended to me. I am a Samsung user so my answer will probably be very stupid.
If you have fastboot, why don't you flash a recovery and a custom rom? Ik stupid but it's the only thing that comes to my mind since i don't have a LG phone lol
Click to expand...
Click to collapse
Installing TWRP or any recovery wont work for me. The bootloader still locked thou.
jaacoozee said:
Installing TWRP or any recovery wont work for me. The bootloader still locked thou.
Click to expand...
Click to collapse
Is that "Download mode" the same as the Samsung one? How do you NORMALLY access it?
JanBoyGamer23 said:
Is that "Download mode" the same as the Samsung one? How do you NORMALLY access it?
Click to expand...
Click to collapse
I'm not sure. Normally I access download mode using volume up and power button. The download mode was there for a sec and then the screen back to
"Your device has failed a routine safety check and will not boot..."
again.
Ah ok so now I understand.
But why don't you unlock your bootloader then if fastboot works? Do you know for sure that TWRP doesn't work?
I really want to help but I don't have a LG phone
JanBoyGamer23 said:
Ah ok so now I understand.
But why don't you unlock your bootloader then if fastboot works? Do you know for sure that TWRP doesn't work?
I really want to help but I don't have a LG phone
Click to expand...
Click to collapse
EDIT: The LG Bootloader unlocking page is "under construction". Guess you have to bring your phone to LG for them to fix this...
JanBoyGamer23 said:
EDIT: The LG Bootloader unlocking page is "under construction". Guess you have to bring your phone to LG for them to fix this...
Click to expand...
Click to collapse
Unfortunately my LG V30 is US region. The official bootloader site not support my phone. Thanks for your info anyway
I'm not sure why a Samsung user was recommended this post. And no offense to the Samsung user, but the process for unlocking, etc is VERY different for Samsung than it is for LG... so I recommend not worrying about that. Believe me, I know, because I'm researching switching to a Samsung in the future, and the process is very different!
That being said, the best resource here is the WTF thread with the post by ChazzMatt. That post has everything you need in one place.
jacoozie, the error you're getting indicates that you had a non-stock phone when you flashed the KDZ on an unlocked phone. For this reason, it's no surprise you got this error - the phone must be COMPLETELY STOCK for a stock KDZ flash. I'm guessing you had TWRP or something else installed, which is causing this problem. Once you unlock, you cannot just flash things willy nilly... and generally you don't flash with KDZ unless you're trying to change models (aka Frankenstein) or on the way to a custom ROM.
It sounds like you've done some unlocking rooting... if so, I recommend you start over with the WTF thread, read it VERY CAREFULLY and ENTIRELY and then reflash as instructed there. I'm guessing you may need to go back to KDZ Nougat and then work your way forward. If you have questions, ask in that thread... but you shouldn't have any questions as the thread is VERY complete (been updated all the time with very detailed information, so everything is in there).
schwinn8 said:
I'm not sure why a Samsung user was recommended this post. And no offense to the Samsung user, but the process for unlocking, etc is VERY different for Samsung than it is for LG... so I recommend not worrying about that. Believe me, I know, because I'm researching switching to a Samsung in the future, and the process is very different!
That being said, the best resource here is the WTF thread with the post by ChazzMatt. That post has everything you need in one place.
jacoozie, the error you're getting indicates that you had a non-stock phone when you flashed the KDZ on an unlocked phone. For this reason, it's no surprise you got this error - the phone must be COMPLETELY STOCK for a stock KDZ flash. I'm guessing you had TWRP or something else installed, which is causing this problem. Once you unlock, you cannot just flash things willy nilly... and generally you don't flash with KDZ unless you're trying to change models (aka Frankenstein) or on the way to a custom ROM.
It sounds like you've done some unlocking rooting... if so, I recommend you start over with the WTF thread, read it VERY CAREFULLY and ENTIRELY and then reflash as instructed there. I'm guessing you may need to go back to KDZ Nougat and then work your way forward. If you have questions, ask in that thread... but you shouldn't have any questions as the thread is VERY complete (been updated all the time with very detailed information, so everything is in there).
Click to expand...
Click to collapse
Thanks for the reply.
I didnt install TWRP or any recovery tools to my phone. My phone bootloader still locked thou.
I have read the WTF thread but the problem is I cant get into my Download mode.
Ok, what steps are you using to try to get into download mode? Presumably turning off the phone, then holding the volume up button and plugging in the USB cable (other end already connected to a Windows computer), correct? If that doesn't work, can you try other USB cables? Sometimes a bad cable could prevent the phone from going into download mode.
i updated to android 12, without any modifications prior, is it possible to root this phone still? or is there no root method for android 12 yet? i've been curious on rooting it for a little while now.
texas7412 said:
i updated to android 12, without any modifications prior, is it possible to root this phone still? or is there no root method for android 12 yet? i've been curious on rooting it for a little while now.
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/v60-bootloader-unlock-and-magisk-root.4358785/ Reports are saying it works fine.
surgemanx said:
https://forum.xda-developers.com/t/v60-bootloader-unlock-and-magisk-root.4358785/ Reports are saying it works fine.
Click to expand...
Click to collapse
Thank you! I hope it works fine for me.. i don't really want to kill my phone Lol i've had a lot of experience with rooting and unbricking phones, but i'm still a bit on edge especially with this one given its price compared to like $50 or less i've paid for others Haha
texas7412 said:
Thank you! I hope it works fine for me.. i don't really want to kill my phone Lol i've had a lot of experience with rooting and unbricking phones, but i'm still a bit on edge especially with this one given its price compared to like $50 or less i've paid for others Haha
Click to expand...
Click to collapse
We have the firehose for the V60!The possibilities are endless..lol..
surgemanx said:
We have the firehose for the V60!The possibilities are endless..lol..
Click to expand...
Click to collapse
i hate to say it.. but the tutorial isn't working for me in qfil it tells me "Please make sure you have selected the correct programmer in flat build page" i rebooted it into the 9008 mode 10-20 times now and it hasn't worked..
texas7412 said:
i hate to say it.. but the tutorial isn't working for me in qfil it tells me "Please make sure you have selected the correct programmer in flat build page" i rebooted it into the 9008 mode 10-20 times now and it hasn't worked..
Click to expand...
Click to collapse
Here,try this one.I just used it not even 10 minutes ago to make a full LUNS back up of a V60 I have laying on my desk.I'm actually using LUNS backups to crossflash other carrier V60's with AT&T software so the VoLTE works.
Edit:Oh,make sure you choose flat build.Then choose this firehose.
surgemanx said:
Here,try this one.I just used it not even 10 minutes ago to make a full LUNS back up of a V60 I have laying on my desk.I'm actually using LUNS backups to crossflash other carrier V60's with AT&T software so the VoLTE works.
Edit:Oh,make sure you choose flat build.Then choose this firehose.
Click to expand...
Click to collapse
this was certainly an interesting experience, i could unlock the bootloader, but doing it via the file thing provided it won't work, going to fastboot and doing fastboot oem unlock, then booting into a twrp recovery and flashing magisk v24.3, it bricked the OS and i had to fight to get it to boot, twrp broke and is locked it refuses to unlock, it gave me an odd looking recovery mode as if it was from android kitkat or something (thats the best i can describe it, it looked much different from the other recovery to wipe) and it said it couldn't boot android and it said to factory reset, so i did.. it downgraded me to android 11 and now its rooted but i can't update to android 12 now because of it being rooted? is there a way to update to 12 now?
texas7412 said:
this was certainly an interesting experience, i could unlock the bootloader, but doing it via the file thing provided it won't work, going to fastboot and doing fastboot oem unlock, then booting into a twrp recovery and flashing magisk v24.3, it bricked the OS and i had to fight to get it to boot, twrp broke and is locked it refuses to unlock, it gave me an odd looking recovery mode as if it was from android kitkat or something (thats the best i can describe it, it looked much different from the other recovery to wipe) and it said it couldn't boot android and it said to factory reset, so i did.. it downgraded me to android 11 and now its rooted but i can't update to android 12 now because of it being rooted? is there a way to update to 12 now?
Click to expand...
Click to collapse
Afraid not because OTA updates will look for rooted or bootloader unlocked devices and will normally give you a white screen error code.Nature of the beast I guess you could say.If you don't plan on doing a custom rom or trying to remove OEM software it's not really worth it honestly.
surgemanx said:
Afraid not because OTA updates will look for rooted or bootloader unlocked devices and will normally give you a white screen error code.Nature of the beast I guess you could say.If you don't plan on doing a custom rom or trying to remove OEM software it's not really worth it honestly.
Click to expand...
Click to collapse
Ahh okay. Thanks though! Do you know why it would have downgraded from 12 to 11 though? that doesn't really make any sense to me.. why did rooting downgrade without me installing an older system or anything like that?
texas7412 said:
Thank you! I hope it works fine for me.. i don't really want to kill my phone Lol i've had a lot of experience with rooting and unbricking phones, but i'm still a bit on edge especially with this one given its price compared to like $50 or less i've paid for others Haha
Click to expand...
Click to collapse
Think about it this way, a V60 with a broken screen is less than 100 bucks. If you brick it, you can fix it for far less than bricking any other phone in a similar class.
texas7412 said:
Ahh okay. Thanks though! Do you know why it would have downgraded from 12 to 11 though? that doesn't really make any sense to me.. why did rooting downgrade without me installing an older system or anything like that?
Click to expand...
Click to collapse
Now,that's an odd one.My thoughts would be because of the engineering bootloader that's written for unlocking purposes?Are you sure it was A12 to begin with?lol..
pflatlyne said:
Think about it this way, a V60 with a broken screen is less than 100 bucks. If you brick it, you can fix it for far less than bricking any other phone in a similar class.
Click to expand...
Click to collapse
And this is very true!The V60 was way ahead of it's time!It's a shame LG devices were never marketed properly and supported on a local retail level like they should have been.And even if you did brick them,worst thing would be peeling the back off and hitting the testpoint to bring it back to life.
surgemanx said:
Now,that's an odd one.My thoughts would be because of the engineering bootloader that's written for unlocking purposes?Are you sure it was A12 to begin with?lol..
Click to expand...
Click to collapse
Yes! I was so excited that i got 12 on it, the bootloader shows its android 12 though.. which is really confusing to me.. is there any chance there's an android 12 kdz for this phone floating around that i could try to root and flash? i'm kind of regretting it now, i can't get the fingerprint scanner working following the tutorial there.. i can't update to 12 again it just fails to download, my recovery mode is gone, i can't get back into the bootloader/fastboot mode only EDL mode but it won't recognize anything within windows, adb won't work nor fastboot, can i recover it still if i wish to go back to stock?
The good news is, it gets much better benchmark scores and is much much faster..
on geekbench, 1688 single core, 6203 multicore, it had a higher score but said it was invalid? that one was 4067 single core, 15601 multicore
antutu, it scored 695755 with just using kernel auditor and maxing out the cpu freq and setting gpu freq to 870mhz.
Edit: I just remembered, for where you mentioned the bootloader, i don't have the engineering one installed. i never got that far to even install it. just android debugging > oem unlock > fastboot > fastboot oem unlock
texas7412 said:
Yes! I was so excited that i got 12 on it, the bootloader shows its android 12 though.. which is really confusing to me.. is there any chance there's an android 12 kdz for this phone floating around that i could try to root and flash? i'm kind of regretting it now, i can't get the fingerprint scanner working following the tutorial there.. i can't update to 12 again it just fails to download, my recovery mode is gone, i can't get back into the bootloader/fastboot mode only EDL mode but it won't recognize anything within windows, adb won't work nor fastboot, can i recover it still if i wish to go back to stock?
The good news is, it gets much better benchmark scores and is much much faster..
on geekbench, 1688 single core, 6203 multicore, it had a higher score but said it was invalid? that one was 4067 single core, 15601 multicore
antutu, it scored 695755 with just using kernel auditor and maxing out the cpu freq and setting gpu freq to 870mhz.
Edit: I just remembered, for where you mentioned the bootloader, i don't have the engineering one installed. i never got that far to even install it. just android debugging > oem unlock > fastboot > fastboot oem unlock
Click to expand...
Click to collapse
That depends on what model of V60 you have?Most of the kdz files for Verizon or T-Mobile can be found at the link below.AT&T or Sprint no kdz's to be found except back up Qfil copies I have found.Take a look,and LGUP it if you find the firmware you want.Most will be A11 and you can just OTA back to A12 with no problem.
Models - LG-Firmwares.com
Free archive of LG firmwares. Comparison of features and reviews of all mobile devices. Quick download of updates for your device.
lg-firmwares.com
surgemanx said:
That depends on what model of V60 you have?Most of the kdz files for Verizon or T-Mobile can be found at the link below.AT&T or Sprint no kdz's to be found except back up Qfil copies I have found.Take a look,and LGUP it if you find the firmware you want.Most will be A11 and you can just OTA back to A12 with no problem.
Models - LG-Firmwares.com
Free archive of LG firmwares. Comparison of features and reviews of all mobile devices. Quick download of updates for your device.
lg-firmwares.com
Click to expand...
Click to collapse
okay good! Thank you! Is there any chance of a android 12 KDZ for the t-mobile variant? and if i flash back an original KDZ, will i have to wipe everything again? Thanks.
texas7412 said:
okay good! Thank you! Is there any chance of a android 12 KDZ for the t-mobile variant? and if i flash back an original KDZ, will i have to wipe everything again? Thanks.
Click to expand...
Click to collapse
If you refurb it with LGUP it will wipe it all.The T-Mobile model has A12,but no physical kdz as of yet.So,you'll have to OTA back to A12 once you set it all back up.
surgemanx said:
If you refurb it with LGUP it will wipe it all.The T-Mobile model has A12,but no physical kdz as of yet.So,you'll have to OTA back to A12 once you set it all back up.
Click to expand...
Click to collapse
do i have to refurb to go back to stock, or can i do it via the upgrade option? Sorry if i'm being bothersome lol
surgemanx said:
If you refurb it with LGUP it will wipe it all.The T-Mobile model has A12,but no physical kdz as of yet.So,you'll have to OTA back to A12 once you set it all back up.
Click to expand...
Click to collapse
HEY! SO I FLASHED THE STOCK BOOT A AND BOOT B AND THEN IT LET ME UPDATE TO 12!
i let the update do its thing, reflashed TWRP and then flashed the patched boot a and b, now i have a rooted android 12. WOOHOO!
texas7412 said:
HEY! SO I FLASHED THE STOCK BOOT A AND BOOT B AND THEN IT LET ME UPDATE TO 12!
i let the update do its thing, reflashed TWRP and then flashed the patched boot a and b, now i have a rooted android 12. WOOHOO!
Click to expand...
Click to collapse
Yes,that wil work until the next update.If it's modified when the next OTA hits,it will give you the update error.Basically,you just set it back stock and the update works.But,glad you have it worked out.