Easily Switch Between JB/KK/LP Bootloader
!! d800 ONLY !!
Make sure you flash the right model!
With the advent of BUMP, we can now use the KK bootloader. A lot of projects preserved the old JB bootloader, since that was needed due to loki. This is the easy way to update your JB bootloader to the new KK bootloader.
Inspired by @dorimanx who did this for the d802. I followed suit and made this for the d800.
What this is:
As it simply says, it upgrades (or downgrades) the bootloader. This includes several other small partitions, in addition to aboot and sbl1.
Sources:
10d & 20c - Extracted from TOT file
20y & 30f - I started with 20d, then did FOTA to 20y and extracted the partitions. Then I did FOTA to 30f and again extracted the partitions.
What this is NOT:
This does not touch your boot, recovery, or modem/radio partitions. You must make sure those are compatible BEFORE flashing this.
WARNING: You can easily brick your phone if you mess this up! This is for d800 ONLY!!! Also, you must have BUMPed boot and recovery images already on your phone to use KK bootloader or you will get fastboot error (or it just won't boot). JB supports BUMP images and LOKI images. KK only supports BUMP.
Lollipop Information:
Special LOLLIPOP WARNING: At this time, the Lollipop BL is not exploitable. Therefore, if you flash Stock LP BL, you will probably brick, or at a minimum, you will lose access to recovery.
To use a BUMPED lollipop ROM, you should install the Lollipop Bump bootstack on my site. It is all of the 30f Lollipop partitions, with a 20y aboot (so bump will work).
Download:
Did you read the warning above? If not, DO NOT DOWNLOAD.
Did you read it twice? If not, DO NOT DOWNLOAD.
Do you understand everything it says? If not, DO NOT DOWNLOAD.
Do you know how to recover if you mess your phone up? If not, DO NOT DOWNLOAD.
I do not want any posts saying "HALP I MESSED THIS UP."
Which bootloader am I currently on?
The only sure way to know is to flash one, or know which one you flashed last.
You can get an idea of your bl when you use the button combo to enter recovery (VolDwn+Pwr, release and repress when LG logo comes up, hold until menu comes up) the screen looks different. On JB the phone asks you to repeatedly press power for factory reset. On KK the phone has you use the volume rocker to pick different menu options.
Download:
https://www.gregtwallace.com/lg-g2/d800_d801-bootloaders/
Again, thanks to @dorimanx.
Shameless plug for donations:
Venmo Preferred (No Fee)
Zelle, send to [email protected]
Backup (Charges Fee)
Paypal
Update 2015.07.29
-Version 1.1 does NOT flash misc partition.
+Misc contains things like MAC addresses and doesn't need to be flashed.
Update 2015.05.12
I have added the 20y KK bootloader, which appears to be different than the originally posted 20c. Both are now posted.
Additionally, I added the LP 30f bootloader. WARNING: This bootloader is not (yet?) exploitable! Flashing it will likely brick your device, or at the very least it will break your recovery. You have been warned!
Reserved2
Reserved2
Cool thing! And nice work! I was just looking around to learn more stuff about bootloaders ..did dorimanx made a thread for d802?
Your awesome version of TWRP is bumped, dorimanxs kernel is bumped too thats all i need to switch on kk bootloader
raulx222 said:
Cool thing! And nice work! I was just looking around to learn more stuff about bootloaders ..did dorimanx made a thread for d802?
Your awesome version of TWRP is bumped, dorimanxs kernel is bumped too thats all i need to switch on kk bootloader
Click to expand...
Click to collapse
No he didn't, but he posted the d802 version under his kernel thread, which is linked in my signature.
Great initiative, @blastagator!
Now... On to the actual bootloader... stuff.
EDIT : Nevermind. Just noticed that this is for the D800 only... and I have a D802, lol.
You, sir, are a badass. Thank you for this
Sent from my LG-D800 using XDA Free mobile app
Formhault said:
Great initiative, @blastagator!
Now... On to the actual bootloader... stuff.
EDIT : Nevermind. Just noticed that this is for the D800 only... and I have a D802, lol.
Click to expand...
Click to collapse
As stated in the OP, dorimanx made exactly the same zip for the d802 to update the bootloader and the other necessary partitions.
You'll just need a bumped recovery + bumped kernel.
Just in case you would like to upgrade to KK bootloader
I'm just waiting for render to release bumped R26 and the first thing I'll do is update the bootloader
Could someone please be kind enough to make one for vs980? I tried making one myself by picking the same exact files off of vs980 kdz but it didn't work.
Voltaine said:
I'm just waiting for render to release bumped R26 and the first thing I'll do is update the bootloader
Click to expand...
Click to collapse
Me too, I guess :silly:
idoluvizsick said:
Could someone please be kind enough to make one for vs980? I tried making one myself by picking the same exact files off of vs980 kdz but it didn't work.
Click to expand...
Click to collapse
I used this: http://forum.xda-developers.com/showthread.php?t=2600575
Extract the partitions out of the stock tot, then just use a simple flash script. Again, if you don't know what you're doing - it is VERY easy to mess up and DIFFICULT to recover from.
Noticing this says bumped boot and recovery required in the op. Was wondering even if I'm on stock everything, boot included, do I still need to be bumped. I would say yes on the recovery due to the nature of how autorec worked. But what about boot, since it is bone stock? Thanks for the info. Thanks for your work on this phone.
Yikes I tried this with 12/5 AICP 5.0 drgravy d800, Render5, and blastagators bumped TWRP 2.8.2.0.
Installed the KK-20C bootloader, the device spent a long time on on the LG logo with a few vibrates, then it blackscreened. While blackscreened plugging into PC started charging and gave me access to Internal Storage. Tried a power off and back on again with same result.
Luckily, manually going into TWRP and flashing the JB-10D bootloader got things back to normal.
EDIT: Just dawned on me that I had the dr87 Working Rotation JB Baseband installed. Perhaps I should have tried with the KK Baseband?
buffal0b1ll said:
Yikes I tried this with 12/5 AICP 5.0 drgravy d800, Render5, and blastagators bumped TWRP 2.8.2.0.
Installed the KK-20C bootloader, the device spent a long time on on the LG logo with a few vibrates, then it blackscreened. While blackscreened plugging into PC started charging and gave me access to Internal Storage. Tried a power off and back on again with same result.
Luckily, manually going into TWRP and flashing the JB-10D bootloader got things back to normal.
EDIT: Just dawned on me that I had the dr87 Working Rotation JB Baseband installed. Perhaps I should have tried with the KK Baseband?
Click to expand...
Click to collapse
I don't think it works with JB based kernels.
sr20ryda said:
I don't think it works with JB based kernels.
Click to expand...
Click to collapse
I used Render 5 which is a L Kernel. Is this JB based?
buffal0b1ll said:
I used Render 5 which is a L Kernel. Is this JB based?
Click to expand...
Click to collapse
Yes. All the LP builds have JB based kernels AFAIK.
sr20ryda said:
Yes.
Click to expand...
Click to collapse
Is there a bumped kernel that d800 can use on L with KK bootloader then?
I don't believe so.
It works only with dorimanx on stock based rom, no cm aosp aicp et
_____________________________Write less read more and be smart
siggey said:
It works only with dorimanx on stock based rom, no cm aosp aicp et
_____________________________Write less read more and be smart
Click to expand...
Click to collapse
After reading ALOT of info heres where i am. I think our good guy render is trying to get his kernel working bumped for KK bootloader and lollipop builds.. heres where i got sad.
It seems recently there is ALOT of dev arguements on the nature of opensource bump so much so that the the orginators have actually closed down and stopped development on the project. lets not go any further with that disucssion, there are other threads for that if you care to read.
So basically i dont have a build environment right now to try to bump any kernels using the instructions and I'm not sure what to think right now considering what i HAVE read. I actually stay away from posting alot of things on XDA that i do on my own, because of this very nature i have seen pop up to many times to count. So to summerize:
Dont have a build environment where i am right now to try...even when i get home im not sure how i will feel since i do respect the codefire guys but understand why someone would have done what they did. If i am successful getting someone elses work say renders kernel, to finally boot ill let him know but im sure render will figure it before i even do that :highfive:
Related
Ok so seeing as the Lollipop is rolling out today for the 2012 N7 and moto x, and I just read a post that it's being batch pushed to our great N5.
I am wondering if I should flash stock 4.4.4 and hit the check now button intill it comes or if I should wait for a custom build of Lollipop.
If I do go stock for the time being, can someone point me to a flashable stock image... And when 5 hits my phone i will up load an image for you guys...
Any way what would you do?
Form your own opinion
Well Where can I find a flashable stock image of 4.4.4
1. Google has already explained how OTA works. It starts at 1 percent of all devices and gradually climbs. If you don't get it the first batch on OTA, clicking Check now doesn't do a single thing, you don't lose your place in line or get another chance. It's a one time thing.
2. Because of #1 ... I'd wait for the factory image and flash that after backing up all your data.
technically, source is not up for the n5, and neither is the android 5.0 stock image for the n5. and @dicecuber is right, its up to you to decide, not us. me.. i flashed a aosp build with the older n5 binaries.
If you want stock use a toolkit. Better yet use google.
kitila said:
If you want stock use a toolkit. Better yet use google.
Click to expand...
Click to collapse
never ever tell someone who has no idea what they are doing to use a root toolkit. that is the absolutely worse piece of advice.
Going off of what the OP is saying, does anyone think that the image will be able to be dirty flashed over the latest Developer Preview?
Ramocity said:
Going off of what the OP is saying, does anyone think that the image will be able to be dirty flashed over the latest Developer Preview?
Click to expand...
Click to collapse
some ppl that tried, had issue. but i dirty flashed aosp lollipop over kitkat without issue.
Dump of Stock Partitions
Lollipop d800-30f
Since we don't have a d80030f KDZ or TOT yet, I decided I would try to do the next best thing. I did a back to factory 20c -> 20y -> 30f upgrade progression. Then I did a factory reset, followed by one click root. Then I dumped all of the partitions that are normally part of the KDZ.
The zip includes Stock 30f images of:
aboot
dbi
laf
misc (removed, not needed - specific to each phone)
persist
rpm
sbl1
tz
I have the modem partition, which will get its own zip and its own post. (http://forum.xda-developers.com/att-g2/development/modems-att-stock-modems-t3106221)
I also dumped system, but it is huge. Please don't download it if you're not a ROM maker (it'll make Google mad at me): https://drive.google.com/folderview...NEb0dUVlpQenhrOHZsaGYyQ3ZiOGV0LWM&usp=sharing
Download:
https://www.gregtwallace.com/lg-g2/d800_d801-bootloaders/
-Bootloader stack is under the bootloader section.
Shameless plug for donations:
Venmo Preferred (No Fee)
Zelle, send to [email protected]
Backup (Charges Fee)
Paypal
-Empty-
Good. If you post are system, there all I needed to go to the lp?
qweewq22 said:
Good. If you post are system, there all I needed to go to the lp?
Click to expand...
Click to collapse
I'm not posting it for that. Use OTA if you want stock lollipop.
blastagator said:
I'm not posting it for that. Use OTA if you want stock lollipop.
Click to expand...
Click to collapse
can u give me the stock d800 framework-res.apk? i flashed a wrong one and i have a bootloop
Abrilabr said:
can u give me the stock d800 framework-res.apk? i flashed a wrong one and i have a bootloop
Click to expand...
Click to collapse
Here ya go.
Flashable zip of the whole ROM will be soon (probably work on it tonight).
@blastgator, what will be the difference between your flashable zip and the stock OTA, other than the fact that it's a zip? Also, do you find it preferable to use stock LP on our device vs BlissPop or other 5.1.1 ROMs? I spend a lot of time and computing power building nightlies, want to know if it's pointless. I don't think so, but now that we have LP, I needed to ask you. PMing you!
berryman13 said:
@blastgator, what will be the difference between your flashable zip and the stock OTA, other than the fact that it's a zip? Also, do you find it preferable to use stock LP on our device vs BlissPop or other 5.1.1 ROMs? I spend a lot of time and computing power building nightlies, want to know if it's pointless. I don't think so, but now that we have LP, I needed to ask you. PMing you!
Click to expand...
Click to collapse
I still run KK. I am just doing some of this stuff to get ready for the upcoming move. I was going to start looking into ROM creation, based on stock ROM (since we don't really have any at this point).
Therefore, I don't really know the answer to your question - "is it worth it?"
And yes, the zip is just what I recovered after doing the FOTA. Much easier grabbing these instead of having to flash 20c and then force 2x FOTAs.
berryman13 said:
@blastgator, what will be the difference between your flashable zip and the stock OTA, other than the fact that it's a zip? Also, do you find it preferable to use stock LP on our device vs BlissPop or other 5.1.1 ROMs? I spend a lot of time and computing power building nightlies, want to know if it's pointless. I don't think so, but now that we have LP, I needed to ask you. PMing you!
Click to expand...
Click to collapse
blastagator said:
I still run KK. I am just doing some of this stuff to get ready for the upcoming move. I was going to start looking into ROM creation, based on stock ROM (since we don't really have any at this point).
Therefore, I don't really know the answer to your question - "is it worth it?"
And yes, the zip is just what I recovered after doing the FOTA. Much easier grabbing these instead of having to flash 20c and then force 2x FOTAs.
Click to expand...
Click to collapse
that's exactly what i was going to say, i don't use blisspop, i don't like custom roms, i prefer stock experience and i cant upgrade since im not on AT&T network, and what he is doing is exactly what i (and many others alike) need, a flashable zip of the Lollipop update
Gemc666 said:
that's exactly what i was going to say, i don't use blisspop, i don't like custom roms, i prefer stock experience and i cant upgrade since im not on AT&T network, and what he is doing is exactly what i (and many others alike) need, a flashable zip of the Lollipop update
Click to expand...
Click to collapse
I slapped a zip together earlier for the stock ROM - it wasn't cooperative and made me mad so I gave up for the evening. Kept getting error:
E: Failed to sysMapFile
It was >2GB so that might have been part of the problem.
Gemc666 said:
that's exactly what i was going to say, i don't use blisspop, i don't like custom roms, i prefer stock experience and i cant upgrade since im not on AT&T network, and what he is doing is exactly what i (and many others alike) need, a flashable zip of the Lollipop update
Click to expand...
Click to collapse
Exactly what I'm looking/waiting for as well. 100% stock Lollipop rom in a flashable zip format. Well, a debloated version would be better but I'll debloat myself if need be. Our Devs are amazing, I'll hang tight and wait for it
Awesome, thank you so much! There hasn't been much movement for a stock LP ROM for the D800, so I'm glad you're doing it!
<Deleted> Test build info was here.
blastagator said:
If any brave testers dare:
http://blastagator.ddns.net/testing.php - beta1
It might not work! Please make sure you know how to recover!!!
I would not post something I would not try on my phone.
HOWEVER, I have NOT tried this on my phone because I had some family issues come up and I can't be "off the grid" so to speak to test things in recovery.
This flashes 20y bootstack, 30f modem, 30f system, and 30f bumped boot.img. Nothing else /should/ be modified. Root may or may not work. It appears installed, but you may need to run "One-Click-Root" or some similar thing after install.
Also, I modified nothing other than root and doing a bump. FOTA will still be functional as well as any other nasties that could cause issues down the line. This is STOCK!
If anyone tries, please report back, for everyone's sake.
Click to expand...
Click to collapse
Downloading, i'll report back later thank you very much
Question can i flash that from 20k? or do i need to be on something specific?
<Deleted> - Old test build info.
I downloaded the beta earlier but ran out of time today to do the install. Before I get brave and attempt it tonight or tomorrow, has anyone done it already and if so what were the results? Thanks.
ItsDon said:
I downloaded the beta earlier but ran out of time today to do the install. Before I get brave and attempt it tonight or tomorrow, has anyone done it already and if so what were the results? Thanks.
Click to expand...
Click to collapse
Didn't work. I had a bad update-binary in there. Once I fixed that I kept playing mix and match because of fastboot error. Still no luck, and needed my phone back. I'll tinker more later.
Tried full 20y bootstack. Tried just aboot and laf 20y, rest as LP. Tried each of this with bumped and unbumped stock LP boot.img.
Bumping gave me a padding error, guessing it might be partially related to that. Unsure.
Thanks for the update, saved me a few headaches I'll hang in there until you get a version that boots. Thanks for doing this!
ItsDon said:
Thanks for the update, saved me a few headaches I'll hang in there until you get a version that boots. Thanks for doing this!
Click to expand...
Click to collapse
I won't be messing with it for awhile. I have to work all weekend. 12 straight days of work, woohoo!
Thank you @blastagator for all your help. No rush. To know someone is looking into it will hopefully spark some interest in the d800 community! Once again - your contributions around here have been invaluable.
Do you have a US996, and want to be able to start modding/theming the ROM? FINE! HERE! Lol...
Please know, this is 100% stock, including kernel. Also, I do not own a US996 (but I do own the H918). This ROM has already been tested (thanks @monsieurtalbot !)
No changes on the ROM. SuperSU gets flashed alongside the ROM. Oh, and setenforce=0 is set via init.qcom.post-boot
Before proceeding. It is absolutely necessary for you to be on a stable TWRP build (currently, RC8, 3.0.2-0, and 3.0.2-1). Also, you must have already have had decrypted your ENTIRE phone. If your phone bootloops into TWRP, you probably didn't decrypt, and/or didn't flash no-verity properly, or it could also be that you are on an old TWRP build. . You have been warned.
This is for the Factory Unlocked US Cellular. Untested on the other US996.
Here we have the base NRD90M ROM from LG. The only difference from this, and what came on your phone is, that it is not ODEXd anywhere. DeODEXing basically bundles all parts of an APK together which saves space, allows for modification of the APK (like for System UI and stuff), and ever so slightly increases performance (by the littlest amount possible). This is ONLY for the US996.
Also, no need to wipe, as /system is fully removed (your apps and settings will stay since that is in /data). Since we only have 1 base from LG, ROMs don't need to be wiped, even if coming from ODEX.
Major thanks to @Chainfire for creating SuperSU
Major thanks to @jcadduono for the root exploit, AND for the TWRP image(s), AND for inspiring me to learn to do it. Also, he supplied the stock System.img, boot.img, and sources for a custom kernel!/RealMVP
SUPER happy to say I am using this currently and it is flawless. Fantastic base for our custom unlocked US996 community.
No more systemless root. This is a full root and I was finally able to delete the stupid boot sounds.
Thx for letting me be the test dummy.
Just so everyone knows I dirty flashed in TWRP from stock and I have had 0 issues. I am a heavy power user.
Everything is working as it should be.
Since it's not specified in the OP - let me make sure that everyone understands that this is for the USA Factory Unlocked US996 ONLY.
Super excited for some custom roms. =)
---------- Post added at 10:53 PM ---------- Previous post was at 10:39 PM ----------
Moving this conversation over from the H918 thread...
I would love to see the FM working on our US996 . . .
BUT - I've had no luck flashing the available zips so far that are for the H918.
FM Service crashes - I figure the chip is there - just needs to likely be enabled on the kernel end.
SO - if you are truly looking into making us a kernel, let's put that on a likely very long todo list. lmao <3
monsieurtalbot said:
Since it's not specified in the OP - let me make sure that everyone understands that this is for the USA Factory Unlocked US996 ONLY.
Click to expand...
Click to collapse
I mean, they would have to be to have TWRP
And it does say US996 in title, as well as in OP
Tilde88 said:
I mean, they would have to be to have TWRP
And it does say US996 in title, as well as in OP
Click to expand...
Click to collapse
There's another US996 for US Cellular - as we all know - so as things get released possibly for that model (which holds the same model number for whatever reason) and this thread ages - it might not be a terrible idea to exclusively specify so some poor soul down the road doesn't flash this to the wrong device... :highfive:
monsieurtalbot said:
I would love to see the FM working on our US996 . . .
BUT - I've had no luck flashing the available zips so far that are for the H918.
FM Service crashes - I figure the chip is there - just needs to likely be enabled on the kernel end.
SO - if you are truly looking into making us a kernel, let's put that on a likely very long todo list. lmao <3
Click to expand...
Click to collapse
Shouldn't be too hard to enable in the kernel. And if it isn't in the source, it could added i guess
Tilde88 said:
Shouldn't be too hard to enable in the kernel. And if it isn't in the source, it could added i guess
Click to expand...
Click to collapse
Any chance you could post the md5 sum for the ROM to check that we got a good download? I want to ensure a good file before flashing a new system.
AlkaliV2 said:
Any chance you could post the md5 sum for the ROM to check that we got a good download? I want to ensure a good file before flashing a new system.
Click to expand...
Click to collapse
It would have to be later tonight, getting ready for work now. You can just double click the zip on your pc. If it opens without an error, you are good to go.
Would you happen to have a stock ODEXed rom for US996 to post as you did for the H918?
Also, are you planning to build anything off the US996 stock deODEXed rom or is it for safety net purposes?
I was thinking about diving into the v20 world to do some dev work, though am I reading this right? Each ROM has to be based off of the system.img for each model number? That makes it hard to decide which device model to buy
--->
Mentalmuso said:
I was thinking about diving into the v20 world to do some dev work, though am I reading this right? Each ROM has to be based off of the system.img for each model number? That makes it hard to decide which device model to buy
--->
Click to expand...
Click to collapse
I honestly am not sure, but I did this just to be safe. As it turns out, FM is not included in the US996 ROM or kernel. I don't know of any other discrepancies, but that was enough for me.
IMO the H918 is the way to go, and just Unlock it from Tmobile. But that's just my opinion.
papashex said:
Would you happen to have a stock ODEXed rom for US996 to post as you did for the H918?
Also, are you planning to build anything off the US996 stock deODEXed rom or is it for safety net purposes?
Click to expand...
Click to collapse
I suppose I could upload a stock ODEXd, but, I don't see the point. :cyclops:
You're right, no point. It's early in the game, hopefully there will be a .tot or .kdz (lg equivalent of ruu) for the eventual 7.1 update.
Thanks for your efforts to date.
Can this ROM be flashed on a sprint 997 that was unlocked and rooted using the dirty Santa method?
The reason I'm asking is because that process seems to change my phone to an unlocked 996 and I want to start fresh with a stock ROM.
Well this is weird. I went to install this and TWRP is telling me I have the wrong device. It is telling me i have a 918 when I know for a fact its a 996....
bryancotton84 said:
Well this is weird. I went to install this and TWRP is telling me I have the wrong device. It is telling me i have a 918 when I know for a fact its a 996....
Click to expand...
Click to collapse
It detects your model from build.prop I believe.
Can you change your model in your build.prop and retry?
Would anyone be willing on trying out a custom kernel? FM might be working. Plus other things and stuff .
I don't have a US996, so I can't test it. So be sure to have a stock boot.img and your stock /system/lib/modules folder. If this fails, you can simply flash your stock boot.img right within twrp, and then push the modules folder into /system/lib/modules. Or you can reflash the ROM.
i was able to dirty flash this straight onto my stock VS995 with the konverge kernel flashed as well and the only problem i have is the static boot but that's easily fixed
Get Ur Noob On said:
i was able to dirty flash this straight onto my stock VS995 with the konverge kernel flashed as well and the only problem i have is the static boot but that's easily fixed
Click to expand...
Click to collapse
What is static boot?
Anyone willing to test the custom kernel, be sure to read what I wrote in the post above. You can find it here
Tilde88 said:
What is static boot?
Anyone willing to test the custom kernel, be sure to read what I wrote in the post above. You can find it here
Click to expand...
Click to collapse
basically until the phone actually boots into the os it looks like a messed up tv showing only static colors and you cant see anything, what you do is you wait until it boots into the os and shut the screen off then hold your finger over the front camera and it fixes it and everything is normal.
Tilde88 said:
I suppose I could upload a stock ODEXd, but, I don't see the point. :cyclops:
Click to expand...
Click to collapse
Any chance you could do it, If it's not too much trouble? I'd like to install it on my F800L, if I can, and I seem to be having issues with the current deodex'd version.
If I'm honest, I have no idea if it will make any difference whatsoever, and the issue could be something completely unrelated (ihavenoideawhatimdoing), but I'd just like to try it, anyway. I got an odex'd H918 working, so It has me wondering if it makes any difference?
This guide is to help out the people who are rooted to know exactly what to do if you get an OTA notification so that there are no errors.
This guide will only work for the Systemless rooting. Guide here
The basic things for achieving OTA after rooting can be found here
Basic things to keep in mind if:
1. Still on soak - Follow this guide and come back to marshmallow and then you should be able to take the OTA.
2. If you are on Stock and rooted - Make a nandroid backup and then the next step is pretty simple, go to SuperSU app and click on the option Full Unroot and click on yes and then again yes and wait for the Phone to reboot. Once it starts back wait for the optimization of the Apps and then download the OTA and then install it. Make sure it is the Stock recovery through which you flash the OTA.
It should go through Smoothly. I have done it twice. Since Nougat doesn't support any known root method yet, so keeping a titanium backup before unrooting is preferred so that as soon as it supports root u can restore all of it back.
Happy updating!
I personally won't install N until we have a rooting method. Because there is no "coming back" if root doesn't materialize.
SoNic67 said:
I personally won't install N until we have a rooting method. Because there is no "coming back" if root doesn't materialize.
Click to expand...
Click to collapse
That's true! But it'll be just a matter of time before we get it!
SoNic67 said:
I personally won't install N until we have a rooting method. Because there is no "coming back" if root doesn't materialize.
Click to expand...
Click to collapse
I have downgraded using my tutorial. And i told you that the firmware that i posted is official...
http://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961
TechBurner said:
I have downgraded using my tutorial. And i told you that the firmware that i posted is official...
http://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961
Click to expand...
Click to collapse
I don't know but XT1643, doesn't come out of the box MPJ24.139-13.1.... it comes out with 23.1 i guess...
That guide did work perfectly!
abhi212b said:
I don't know but XT1643, doesn't come out of the box MPJ24.139-13.1.... it comes out with 23.1 i guess...
That guide did work perfectly!
Click to expand...
Click to collapse
I know that works perfectly right now, the only reason i made the tutorial on how to downgrade is because we had the same scenario for Moto g 1st gen. People got used to downgrading using the normal method, what they didnt realize was that the bootloader and gpt were not being flashed and they showed failed when you did that for the official firmware. But after a month tons of Moto g 1st gens got hard bricked because of that. Anyone who tried to downgrade from modified stock or custom rom based on Lollipop (At that time) Got their phone hard bricked. It's the same for Nougat also and is same for All cross android versions after Kitkat.
With every new update they release a new partition table and a new bootloader . The new bootloader doesnt allow you to flash the previous bootloaders over it and same for partition but for some varients of the phone the warning is not there and the older bootloader is flashed resulting in a hard brick. This is also true for Custom roms based on the official firmware (which will come) and devices in which a custom kernel has been flashed.
I am not saying trust me, i am just saying be careful .
^ That's what I meant when I said "no coming back". You are stuck with a N bootloader and a MM firmware. Might work fine, might not.
Quick question
I have a XT1643
On stock rooted rom with elemental kernel.
Got an update notification yesterday.
I flashed the stock boot.img I found on the forum but the wifi is not working after flashing that.
what do I need to do in order to get it working and get the update?
Thanks
SoNic67 said:
^ That's what I meant when I said "no coming back". You are stuck with a N bootloader and a MM firmware. Might work fine, might not.
Click to expand...
Click to collapse
I agree with you on this. I am stuck with an N Bootloader and and MM firmware.
I can upgrade to an N ROM but I get FP issues (cosmetic, but still not desirable)
I cannot take an official OTA anymore because even if I downgrade to stock, I still have an N Bootloader which prevents me from taking OTA.
Unless we get a stock N rom, I guess we are stuck with this setup.
Sent from my Moto G (4) using Tapatalk
SoNic67 said:
^ That's what I meant when I said "no coming back". You are stuck with a N bootloader and a MM firmware. Might work fine, might not.
Click to expand...
Click to collapse
It will i guess because then again u can take an OTA to N ...
tandon.ayush said:
Quick question
I have a XT1643
On stock rooted rom with elemental kernel.
Got an update notification yesterday.
I flashed the stock boot.img I found on the forum but the wifi is not working after flashing that.
what do I need to do in order to get it working and get the update?
Thanks
Click to expand...
Click to collapse
Everything needs to be on stock! Stock boot, recovery, logo, kernel etc. then it works ! any modifications will lead to an error!
Moto E4 XT1766
Partition Index & Bootloader Updater
Build No. NCQ26.69-64
TWRP Flashable Installer
WARNING: DO NOT use this updater.zip if your device has been updated to any firmware version newer than NCQ26.69-64. Downgrading can hard brick your device. If your device has been upgraded to a newer build, or if you aren't sure, proceed to this thread: https://forum.xda-developers.com/moto-e4/how-to/firmware-restoring-moto-e4-xt1766-t3820749, which is the latest firmware -- NCQS26.69-64-5.
DISCLAIMER: Although I have thoroughly tested this update installer, I am not responsible for any adverse effects incurred from using it. Because this installer does flash bootloader and other sensitive partitions on your device, charging your device to at least 50% is recommended prior to proceeding.
PURPOSE:
This installer updates your partition index and bootloader components to Build No. NCQ26.69-64. If you are not running the stock Android OS, or have never updated your device to Build No. NCQ26.69-64, this installer will update your partition index (gpt.bin) and bootloader components to the most current firmware version. For custom ROM users, this alleviates the task of reverting to an unmodified stock Android OS, installing OTAs, and then reinstalling your daily driver custom ROM -- all to simply update your bootloader and partition index. Specifically, this installer updates the following partitions:
/rpm - primary bootloader
/sbl1 - secondary bootloader
/aboot - application bootloader
/tz - trust zone (bootloader component)
/devcfg - device configuration (component)
/keymaster - bootloader component
/cmnlib - bootloader component
/cmnlib64 - bootloader component
/prov - bootloader component
INSTRUCTIONS:
Download the updater zip from the below link and save it to internal or external storage. Boot into TWRP, install the zip, and reboot. Your partition index and bootloader are now up to date. Note: this update can be installed on a stock or custom ROM.
DOWNLOAD LINK:
https://drive.google.com/file/d/18eFi6E1YnNB68OwmEJeH0FGmAVsE89Jo/view?usp=drivesdk
Very cool, thanks brother
Sent from my XT1766 using Tapatalk
@MotoJunkie01 it worked fine, but I got this error. Anything to worry about?
Thanks for this bro.
@madbat99, nothing to worry about. It's a pseudo-error due to a conflict in the update-binary. I'll iron it out just because it messes with my OCD. :good:
MotoJunkie01 said:
@madbat99, nothing to worry about. It's a pseudo-error due to a conflict in the update-binary. I'll iron it out just because it messes with my OCD. :good:
Click to expand...
Click to collapse
I figured. Just thought I'd ask. Thanks again
madbat99 said:
@MotoJunkie01 it worked fine, but I got this error. Anything to worry about?
Thanks for this bro.
Click to expand...
Click to collapse
How did you screenshot in the recovery?
frederickrl said:
How did you screenshot in the recovery?
Click to expand...
Click to collapse
Same way as in the os. Power + volume down
madbat99 said:
Same way as in the os. Power + volume down
Click to expand...
Click to collapse
I thought it may be, twrp is so advanced thx!
Hard bricked
I need help my phone is hard bricked just showing on PC as an unknown usb device..
I have flashed wrong firmware my device sperry xt1766..
Please help
My phone xt1766 is bricked by flashing wring firmware on pc showinh qhs usb dload and unable to power on...
please help
hassanshaikhhyd said:
My phone xt1766 is bricked by flashing wring firmware on pc showinh qhs usb dload and unable to power on...
please help
Click to expand...
Click to collapse
Your phone is most likely in edl not sure what solution would be at this time
skullkid383 said:
Your phone is most likely in edl not sure what solution would be at this time
Click to expand...
Click to collapse
is there change of its solution in future
hassanshaikhhyd said:
is there change of its solution in future
Click to expand...
Click to collapse
I might be getting second more e4 when I get paid as a test subject cause my friend had same problem so I want to find a solution for this if and when I do I'll me u know
Bricked
Same prob, flashed it on twrp and everything looked good until it shut off completely and never powered back on.
Tried hard reset. won't even go into recovery/
I just forresst gumped my xt1765 too, i just noticed this update was for xt1766, not xt1765. Been trying out RR, AICP and Lineage with minor bugs, then thought this update might correct minor bugs since not build as specified here. Anyways, flashed favorite after trying all custom roms for few weeks at a time and decided that LineageOS was my favorite with least bugs/issues but after flashing LineageOS it felt just right. Like finding your favorite fitting lost pair of jeans or hooking up with an ex again....just felt right...anyways, short story and heartbreak after I flashed this zip, my beloved moto gen E4, my nickname, get it Jenny no. 4? Our last kiss was the reboot system kiss and caress....and just like that, she was gone forever...no power, no recovery, no nothing at all... and just now the small print cognizant epiphany opened my dreamy happily perpetually sleeping eyes. the perfect device, fast as i wanted, tweaked like i liked and she never complained or got mad or talked back well she did when i needed googlies answered...this zip was for the sperry xt1766...now my moto genE4 is gone forever....
Ive been flashing for years all kinds of different devices and never have I had this type of problem..there was always the fallback flashing back to stock if bootlooped or soft bricked. Flash, boom, fixed, start over. Never have I encountered the no power no charge no nothing one last kiss goodbye, EVER. Well, life lesson learned. I just needed to get that off my chest. I feel a little better now guys, thanks for listening.
cuervo233 said:
I just forresst gumped my xt1765 too, i just noticed this update was for xt1766, not xt1765. Been trying out RR, AICP and Lineage with minor bugs, then thought this update might correct minor bugs since not build as specified here. Anyways, flashed favorite after trying all custom roms for few weeks at a time and decided that LineageOS was my favorite with least bugs/issues but after flashing LineageOS it felt just right. Like finding your favorite fitting lost pair of jeans or hooking up with an ex again....just felt right...anyways, short story and heartbreak after I flashed this zip, my beloved moto gen E4, my nickname, get it Jenny no. 4? Our last kiss was the reboot system kiss and caress....and just like that, she was gone forever...no power, no recovery, no nothing at all... and just now the small print cognizant epiphany opened my dreamy happily perpetually sleeping eyes. the perfect device, fast as i wanted, tweaked like i liked and she never complained or got mad or talked back well she did when i needed googlies answered...this zip was for the sperry xt1766...now my moto genE4 is gone forever....
Ive been flashing for years all kinds of different devices and never have I had this type of problem..there was always the fallback flashing back to stock if bootlooped or soft bricked. Flash, boom, fixed, start over. Never have I encountered the no power no charge no nothing one last kiss goodbye, EVER. Well, life lesson learned. I just needed to get that off my chest. I feel a little better now guys, thanks for listening.
Click to expand...
Click to collapse
The old dreaded hard brick. Lights out time. Been there done that. Have you read this method to restore your device using a microSD card? https://forum.xda-developers.com/moto-e4/how-to/untested-moto-e4-xt1765-metropcs-t3843657
This guide for the xt1766 gives overview to the method as well. https://forum.xda-developers.com/moto-e4/how-to/e4-sprint-xt1766-unbrick-easy-sdcard-t3833408/page2
Basically, download the unbrick image for your xt1765 from the 1st link I posted above. Then, see the second link on the xt1766 for instructions on attempting the unbrick.
I had 1766 that broke so I put the back of it in another Moto e4 plus....just wondering if I have any options...
Amphetmine Gene said:
I had 1766 that broke so I put the back of it in another Moto e4 plus....just wondering if I have any options...
Click to expand...
Click to collapse
Wait...seen this before. Bad form pooping the same post in multiple threads.
https://forum.xda-developers.com/mo...droid-7-1-1-rom-moto-e4-t3885821/post79275927
Davey126 said:
Wait...seen this before. Bad form pooping the same post in multiple threads.
https://forum.xda-developers.com/mo...droid-7-1-1-rom-moto-e4-t3885821/post79275927
Click to expand...
Click to collapse
Thanks man, yea only 2nd time I've ever posted anything...but good to no
No permission to downloader
HI.
I need this file.
Google not permission to downloader