Go to the Google site guys...build is up...looks like one to rule them all
Here is a link to the OTA https://developers.google.com/android/ota#sailfish
Or if you want the factory image
https://developers.google.com/android/images#sailfish
Interesting there aren't separate builds...
Do they post a changelog anywhere? Curious what changes are in store.
pjd2011 said:
Interesting there aren't separate builds...
Click to expand...
Click to collapse
More interesting... it looks like the 6P will have a separate build for Verizon this month...
Waiting for non verizon build like the one from November
This build NMF26O seems to have a newer baseband than the Canadian update (NPF26J). Hopefully LTE issues sorted for those who have it.
I haven't finished extracting it...is the bootloader the same or has it changed?
Doing everything from my phone while the wife does the Christmas shopping
bwthor20 said:
Do they post a changelog anywhere? Curious what changes are in store.
Click to expand...
Click to collapse
http://android-developers.blogspot.com/2016/12/welcoming-android-711-nougat.html?m=1
Sent from my Pixel using Tapatalk
do i need to flash every OTA or just the last one? currently on 7.1.0 (Europe, NDE63U, Nov 2016)
google is not really informative at this point
I'm getting the December OTA as I type this. I have a 32GB Pixel with locked bootloader, from the Google Store.
EDIT: Now I'm getting it on my N5x as well. I haven't seen an OTA roll out this swiftly before.
OTA just popped up... Verizon pixel 128gb
Do those of us on Verizon have to worry about thisessing up unlocked bootloader if it's already unlocked??
Also curious if this patched the bootloader exploit used
has anyone flashed the factory image or side loaded the OTA for a non-VZ device yet?
spunks3 said:
has anyone flashed the factory image or side loaded the OTA for a non-VZ device yet?
Click to expand...
Click to collapse
Flashed factory img, carrier tmobile purch from BB
jay661972 said:
Flashed factory img, carrier tmobile purch from BB
Click to expand...
Click to collapse
very nice, which commands did you use to flash?
I'm currently rooted with TWRP alpha2 and SuperSU SR5. I'd like to update without losing data.
My system is on Sot B so I'm thinking:
Code:
fastboot flash bootloader bootloader.img
fastboot reboot bootloader
fastboot flash radio radio.img
fastboot reboot bootloader
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_b system.img
fastboot flash vendor vendor.img
and then to get TWRP back:
fastboot boot twrp.img
- TWRP install twrp.zip
Reboot into recovery
- TWRP install supersu.zip
Does the above sound accurate?
spunks3 said:
very nice, which commands did you use to flash?
I'm currently rooted with TWRP alpha2 and SuperSU SR5. I'd like to update without losing data.
My system is on Sot B so I'm thinking:
and then to get TWRP back:
fastboot boot twrp.img
- TWRP install twrp.zip
Reboot into recovery
- TWRP install supersu.zip
Does the above sound accurate?
Click to expand...
Click to collapse
I use the flash-all file, i edit the file first to remove the -w so i can dont have to wipe the data
Cant answer the TWRP, not sure if it works with the new update
aholeinthewor1d said:
Do those of us on Verizon have to worry about thisessing up unlocked bootloader if it's already unlocked??
Also curious if this patched the bootloader exploit used
Click to expand...
Click to collapse
I just sideloaded the OTA onto my VZW Pixel with unlocked bootloader. My bootloader remains unlocked and I flashed twrp and SuperSU SR5. So far everything is working fine.
According to the dePixel8 website (http://theroot.ninja/depixel8.html) "dePixel8 is patched in Android 7.1.1 and newer, do not ask for future support or any kind of support."
So if you take this OTA from the phone (on an unlocked bootloader) you may well be locked out for good (unless someone finds another exploit).
stranula said:
I just sideloaded the OTA onto my VZW Pixel with unlocked bootloader. My bootloader remains unlocked and I flashed twrp and SuperSU SR5. So far everything is working fine.
According to the dePixel8 website (http://theroot.ninja/depixel8.html) "dePixel8 is patched in Android 7.1.1 and newer, do not ask for future support or any kind of support."
So if you take this OTA from the phone (on an unlocked bootloader) you may well be locked out for good (unless someone finds another exploit).
Click to expand...
Click to collapse
Thanks for the reply. I did some more reading and realized it's safe to install the OTA since I'm already unlocked. The update can't relock it. I already installed it via OTA and everything is ok
sorry, big time newb here. How do I flash the update if I have Verizon pixel with bootloader unlocked and with twrp installed? OTA doesn't work and I don't want to lose data....please help
Related
Like topic states, I would like the bootloader version of JSR78D.
Here's how to check:
turn device off
hold down power and volume down until fastboot screen appears
version should be in bottom left of screen
Preferably I would like to also request a nandroid and dump of the bootloader, but having just the bootloader version will do.
If you've already updated to JSS15J: I already know the bootloader version for that, I dont need it again.
Just to add to the original post, all N7 LTE devices ship with JSR78D out of the box and you will get an update to JSS15J after you boot it for the first time. You will need to get the bootloader information before performing that first OTA update. Thanks!
Sent from my Galaxy Note 8.0 using Tapatalk 4
Mine is FLO-03.14, I have the LTE version and already updated to the latest OTA update.
nex86 said:
Mine is FLO-03.14, I have the LTE version and already updated to the latest OTA update.
Click to expand...
Click to collapse
Thanks but we need the bootloader version from before it was updated. Thanks anyway.
Sent from my Nexus 7 using Tapatalk 4
Just a friendly bump...
My LTE (deb) was shipped with JSS15J in Germany. Bought it on release date 28.08.2013.
So I doubt that later produced hardware would be shipped with an older ROM version, you can grab this information.
scorpio16v said:
My LTE (deb) was shipped with JSS15J in Germany. Bought it on release date 28.08.2013.
So I doubt that later produced hardware would be shipped with an older ROM version, you can grab this information.
Click to expand...
Click to collapse
Just to confirm, my LTE Nexus 7 also came with JSS15J from Media Market in Germany.
.
.
Dave_S said:
Just to confirm, my LTE Nexus 7 also came with JSS15J from Media Market in Germany.
.
.
Click to expand...
Click to collapse
Getting my device on Monday (LTE) will check for you.
I, too, have bought my N7 in Germany, it came with JSS15J. I have received several updates for the Google Apps, but so far no OTA system update. So I'm still on JSS15J and, I guess, the original bootloader shipped with the device.
Bootloader version according to bootloader screen is FLO-03.14. For completeness: HW version is 'rev_e', Baseband version is 'DEB-G00_1.23.0_0720'
TheManii said:
Like topic states, I would like the bootloader version of JSR78D.
Here's how to check:
turn device off
hold down power and volume down until fastboot screen appears
version should be in bottom left of screen
Preferably I would like to also request a nandroid and dump of the bootloader, but having just the bootloader version will do.
If you've already updated to JSS15J: I already know the bootloader version for that, I dont need it again.
Click to expand...
Click to collapse
Postal service lost my package, so it won't be arriving today
Maybe they find it this week or maybe not, who knows
just unpack new LTE, boot loader FLO-03.05
how to backup the boot loader?
xdacinq said:
how to backup the boot loader?
Click to expand...
Click to collapse
If you have fastboot set up, you can unlock your bootloader with "fastboot oem unlock", reboot your device once, then boot into the latest TWRP recovery via "fastboot boot <IMG file name>". Once in TWRP select "Backup" and be sure "Boot" is selected on the backup screen.
dasmanul said:
If you have fastboot set up, you can unlock your bootloader with "fastboot oem unlock", reboot your device once, then boot into the latest TWRP recovery via "fastboot boot <IMG file name>". Once in TWRP select "Backup" and be sure "Boot" is selected on the backup screen.
Click to expand...
Click to collapse
But TWRP 2.6.1.0 is not available yet for N7 LTE. And 2.6.0.0 may result in multi touch issue. I will try Wug's Nexus Root Kit instead.
Will i be asked if i want to update via OTA or do i get them without influence by myself?
xdacinq said:
But TWRP 2.6.1.0 is not available yet for N7 LTE. And 2.6.0.0 may result in multi touch issue. I will try Wug's Nexus Root Kit instead.
Will i be asked if i want to update via OTA or do i get them without influence by myself?
Click to expand...
Click to collapse
You are not flashing TWRP with that command, you are booting an image just for 1 time, so it's temporary.
fasboot flash xxx xxx.img > flashes an image permanently
fasboot boot xxx xxx.img > boots with that image for once
jak3z said:
You are not flashing TWRP with that command, you are booting an image just for 1 time, so it's temporary.
fasboot flash xxx xxx.img > flashes an image permanently
fasboot boot xxx xxx.img > boots with that image for once
Click to expand...
Click to collapse
ok, understood.
@TheManii do you need the files from my version?
03.05 is the same as flo on JWR66N, because of that I already have a good copy of it.
If there's enough interest I could pack it into a custom recovery flashable update zip.
jak3z said:
You are not flashing TWRP with that command, you are booting an image just for 1 time, so it's temporary.
Click to expand...
Click to collapse
Careful, though! If I read this thread correctly, booting an image even just once can affect your touchscreen firmware. However, the same thread could also offer a remedy if you actually experience problems.
For the record: I have TWRP 2.6.0.0 flashed on my LTE model and haven't experienced any multitouch issues. I have, however, probably never tried to use more than 2 fingers at once.
So would you recommend to install the OTA?
xdacinq said:
So would you recommend to install the OTA?
Click to expand...
Click to collapse
In case you're asking me: I don't feel I have had the device long enough to give any recommendations. All I can say is that mine came with JSS15J out of the box and I haven't had any issues. I've unlocked my bootloader, rooted the device in order to install XPosed and XPrivacy and flashed TWRP 2.6.0.0. I haven't received any OTA updates yet.
dasmanul said:
Careful, though! If I read this thread correctly, booting an image even just once can affect your touchscreen firmware. However, the same thread could also offer a remedy if you actually experience problems.
For the record: I have TWRP 2.6.0.0 flashed on my LTE model and haven't experienced any multitouch issues. I have, however, probably never tried to use more than 2 fingers at once.
Click to expand...
Click to collapse
You read correctly.
This post has a more detailed explanation of what is going on:
http://forum.xda-developers.com/showthread.php?t=2428194
TWRP 2.6.0.0 = JSS15J touchscreen firmware
TWRP 2.6.1.0 = JSS15Q touchscreen firmware
This has nothing to do with whether you boot into it temporarily vs flashing it on your tablet. As long as you run ANY kernel (including the kernels bundled into TWRP/CWM/etc.) it will try to upgrade your firmware if the one in the kernel is newer, and then that is the firmware your tablet uses until a newer one comes along. Going back to your old kernel/ROM will NOT restore your older touchscreen firmware but there are solutions for that now.
So this may be a stupid question, but this is my first Nexus device. I will have a 6P delivered Thursday and plan to unlock, decrypt, and install TWRP. The guides so far reference using MDB08K, and the modified boot is only for this version currently. After I install TWRP, am I able to install the factory image for the latest MDB08M and just exclude flashing certain images? Or do I need to flash them all then wait for a new modified boot image for 08M and install TWRP over again?
geoff5093 said:
So this may be a stupid question, but this is my first Nexus device. I will have a 6P delivered Thursday and plan to unlock, decrypt, and install TWRP. The guides so far reference using MDB08K, and the modified boot is only for this version currently. After I install TWRP, am I able to install the factory image for the latest MDB08M and just exclude flashing certain images? Or do I need to flash them all then wait for a new modified boot image for 08M and install TWRP over again?
Click to expand...
Click to collapse
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess
MrDSL said:
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess
Click to expand...
Click to collapse
Its good to do this right away because when you unlock the bootloader, it wipes the phone. I haven't done this on mine yet because I'm curious about Android Pay and what impact that will have on it.
bitpushr said:
Its good to do this right away because when you unlock the bootloader, it wipes the phone. I haven't done this on mine yet because I'm curious about Android Pay and what impact that will have on it.
Click to expand...
Click to collapse
OH OH!!!! We have to behave, we have an Administrator with the same phone UGH!! Just kidding Hello @bitpushr
Somewheres around here someone is reporting pay working with unlock and root. If I recall correctly he removed root in su settings to add the card and then set back to root and it was working. Highly concerned individuals might want to verify that from multiple sources...
MrDSL said:
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess
Click to expand...
Click to collapse
But don't you need to use the corresponding modified boot image to root it? There currently isn't one for the latest factory image I believe.
geoff5093 said:
But don't you need to use the corresponding modified boot image to root it? There currently isn't one for the latest factory image I believe.
Click to expand...
Click to collapse
Chainfire has one and I believe there is one in the development forum.
MrDSL said:
Chainfire has one and I believe there is one in the development forum.
Click to expand...
Click to collapse
I was looking at his thread, but I only see one for the 08K image.
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
The one in the dev section also appears to only be for 08K: http://forum.xda-developers.com/nexus-6p/development/kernel-stock-decrypted-kernel-verity-t3235013
I just wanted to confirm that these need to be the same, so I'll wait for an update.
I thought Build MBD08K was the latest..
I know that I'm currently running cleanrom MBD08K with modified MBD08K boot.img
Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.
mysongranhills said:
Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.
Click to expand...
Click to collapse
Awesome!! ????
mysongranhills said:
Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.
Click to expand...
Click to collapse
I assume if we have MDB08K, rooted with TWRP and want to take the OTA to MDB08M, that we can use a similar procedure:
1. Flash stock boot.img and recovery.img from MDB08K factory image (temporarily disabling root and TWRP)
2. Download and install OTA
3. Reflash modified MDB08K boot.img from Chainfire
4. Reflash TWRP recovery
5. Install SuperSU 2.52 using TWRP
Has anyone tried this method?
rsmolen said:
I assume if we have MDB08K, rooted with TWRP and want to take the OTA to MDB08M, that we can use a similar procedure:
1. Flash stock boot.img and recovery.img from MDB08K factory image (temporarily disabling root and TWRP)
2. Download and install OTA
3. Reflash modified MDB08K boot.img from Chainfire
4. Reflash TWRP recovery
5. Install SuperSU 2.52 using TWRP
Has anyone tried this method?
Click to expand...
Click to collapse
No, but your logic is sound. I see no problems doing it that way. Why would you prefer the OTA updates over the latest factory images? I know for me part of the reason I did it the way I did was b/c I couldn't get phone to download/recognize that OTA update existed.
In case anyone else is still wondering, flashing the 08M factory image and then using the 08K modified boot works fine. I'm on the latest and rooted right now.
mysongranhills said:
No, but your logic is sound. I see no problems doing it that way. Why would you prefer the OTA updates over the latest factory images? I know for me part of the reason I did it the way I did was b/c I couldn't get phone to download/recognize that OTA update existed.
Click to expand...
Click to collapse
I just thought this would be slightly easier than flashing the system.img from the factory image. However, given the modified boot.img and systemless SuperSU, I guess only flashing the system.img (and radio.img if changed) from the new build would probably be easier at this point. However, if xPosed comes to Marshmallow and modifies system, that will be another step in the upgrade process, which presumably would not need to be done if you could take the OTA the way I proposed.
Was rooted on stock 7.0 and SuperSu, TWRP.
Flashed latest april factory image 7.1.2 using Flashfire which went Great. Rebooted to twrp recovery and flashed pixel mod, great.
Noticed I'm still on bootloader 3.62 and radio 3.72. ? So I guess flashfire doesn't update those.
I'm on Verizon.
Do I need to update to latest bl 3.67 and radio 3.81?
By what method? Fastboot, Flashfire, TWRP
Thanks much
Born<ICs said:
Was rooted on stock 7.0 and SuperSu, TWRP.
Flashed latest april factory image 7.1.2 using Flashfire which went Great. Rebooted to twrp recovery and flashed pixel mod, great.
Noticed I'm still on bootloader 3.62 and radio 3.72. ? So I guess flashfire doesn't update those.
I'm on Verizon.
Do I need to update to latest bl 3.67 and radio 3.81?
By what method? Fastboot, Flashfire, TWRP
Thanks much
Click to expand...
Click to collapse
Hello,
Reboot to bootloader,
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
Done... :good:
Cheers...
Figured fastboot works but..
Phone seems to function fine so...
Do I actually want/need to flash the latest BL & Radio?
Curious why flashfire skips over these and if it's possible to add these images separately in the flashfire sequence.
Thanks
Born<ICs said:
Figured fastboot works but..
Phone seems to function fine so...
Do I actually want/need to flash the latest BL & Radio?
Curious why flashfire skips over these and if it's possible to add these images separately in the flashfire sequence.
Thanks
Click to expand...
Click to collapse
Hello,
I keep my bootloader up to date. Because it's part of the system, maybe security flaws have been patched... If it was useless, they wouldn't release a new one.
The radio? Well, maybe it will improve your reception or maybe not. It could even be worse. Radio version doesn't matter. If you want, you can flash the new one and if you don't see an improvement, you can flash your current one back. It's up to you...
Check this: https://flashfire.chainfire.eu/settings/#flash_bootloaders
The part about flashing bootloader. Didn't see infos regarding radio though.
Cheers...
5.1 said:
Hello,
I keep my bootloader up to date. Because it's part of the system, maybe security flaws have been patched... If it was useless, they wouldn't release a new one.
The radio? Well, maybe it will improve your reception or maybe not. It could even be worse. Radio version doesn't matter. If you want, you can flash the new one and if you don't see an improvement, you can flash your current one back. It's up to you...
Check this: https://flashfire.chainfire.eu/settings/#flash_bootloaders
The part about flashing bootloader. Didn't see info's regarding radio though.
Cheers...
Click to expand...
Click to collapse
Oh, OK thanks for the link. Fastboot it is then.
There's actually someone on XDA who created a flashable zip that can be used to update the bootloader and radio through TWRP. Not being great at command lines on the computer I usually use that and have never had a problem.
OK thanks I found the post. Took a chance and downloaded the latest bootloader radio combo zip and flashed via twrp.
All good
I have looked through the entire internet and i cant find one for that specific one, not an EU on atleast
(reteu.en.Eu retgb)
and i don't wanna screw up my phone.
thanks
XxperexX said:
I have looked through the entire internet and i cant find one for that specific one, not an EU on atleast
(reteu.en.Eu retgb)
and i don't wanna screw up my phone.
thanks
Click to expand...
Click to collapse
We don't have it for any variant... Don't know if we ever will, never been leaked and the sources for them are questionable if we will ever get any more factory images at all.
What is the problem?
acejavelin said:
We don't have it for any variant... Don't know if we ever will, never been leaked and the sources for them are questionable if we will ever get any more factory images at all.
What is the problem?
Click to expand...
Click to collapse
I need to restore to stock recovery and relock the bootloader, but i heard i cant do that if i use an image older than mine
XxperexX said:
I need to restore to stock recovery and relock the bootloader, but i heard i cant do that if i use an image older than mine
Click to expand...
Click to collapse
Why do you want relock BL? It can help with... nothing.
You can flash the newest version RetEu 6.0.1 with oem_lock commands.
I suggest rather:
Flash the first 6.0.1 reteu 24...58 without locking
If everything will be ok:
Flash the last 6.0.1 24...58-5 with locking BL.
After it you should get one or two OTAs.
Remember: bootloop with locked BL - only authorized service can help.
dzidexx said:
Why do you want relock BL? It can help with... nothing.
You can flash the newest version RetEu 6.0.1 with oem_lock commands.
I suggest rather:
Flash the first 6.0.1 reteu 24...58 without locking
If everything will be ok:
Flash the last 6.0.1 24...58-5 with locking BL.
After it you should get one or two OTAs.
Remember: bootloop with locked BL - only authorized service can help.
Click to expand...
Click to collapse
Oh, probably wont do that then.
Another question, can i download the android 7 ota uodate when i get it still? With an unlocked bootloader saying "Offical" and twrp?
So far ota update is only for 24...58-13.
With twrp you can't install any ota update.
Unlocked BL doesn't matter for OTAs.
dzidexx said:
So far ota update is only for 24...58-13.
With twrp you can't install any ota update.
Unlocked BL doesn't matter for OTAs.
Click to expand...
Click to collapse
Exactly, i need to get rid off twrp, but i can only do that if i flash a stock recovery, which i cant
It might be worth trying this older firmware whose name suggests that it is reteu for UK and FR, and seeing if newer OTAs show up:
https://firmware.center/firmware/Mo..._MPH24.49-18_cid7_subsidy-DEFAULT_CFC.xml.zip
More available here, but none of them seem like they're for UK phones:
https://firmware.center/firmware/Motorola/Moto X Style/Stock/XT1572/
If your bootloader is unlocked and you're trying to lock it, you could try flashing it while keeping the bootloader unlocked, and then flash it again as part of the flashboot oem lock begin -> flashboot oem lock process. (From what I've seen, the device is fine flashing older firmware with an unlocked bootloader, but not with a locked one.)
Bit of a noob at this, but I was able to get the bootloader unlocked and install twrp recovery but after realizing that NMI81C is kinda old and being a sprint user and there OTA updatings being stupid slow I wanted to manually update to NMJ32F via adb sideload.
How do I do this? From what I read, you have to revert back to stock recovery via stock recovery.img but I cant seem to find any stock recovery.img online..
am I just stupid, a complete noob, or both?
Btw this is my first time trying this in years after switching from my note 4 to iphone, so this is basically all new to me lol
cygnets said:
Bit of a noob at this, but I was able to get the bootloader unlocked and install twrp recovery but after realizing that NMI81C is kinda old and being a sprint user and there OTA updatings being stupid slow I wanted to manually update to NMJ32F via adb sideload.
How do I do this? From what I read, you have to revert back to stock recovery via stock recovery.img but I cant seem to find any stock recovery.img online..
am I just stupid, a complete noob, or both?
Btw this is my first time trying this in years after switching from my note 4 to iphone, so this is basically all new to me lol
Click to expand...
Click to collapse
Yep, you need stock recovery to accept and sideload stock OTAs. They did release stock firmware images finally. I shouldn't assume the stock recovery is there, but I will say that it probably is.
cygnets said:
Bit of a noob at this, but I was able to get the bootloader unlocked and install twrp recovery but after realizing that NMI81C is kinda old and being a sprint user and there OTA updatings being stupid slow I wanted to manually update to NMJ32F via adb sideload.
How do I do this? From what I read, you have to revert back to stock recovery via stock recovery.img but I cant seem to find any stock recovery.img online..
am I just stupid, a complete noob, or both?
Btw this is my first time trying this in years after switching from my note 4 to iphone, so this is basically all new to me lol
Click to expand...
Click to collapse
You have the latest firmware for Sprint. The later is for all other carriers.
https://www.essential.com/developer/current-builds
DAE1964 said:
You have the latest firmware for Sprint. The later is for all other carriers.
Click to expand...
Click to collapse
Indeed, I read that even though this is the current firmware for sprint users, its only because sprints OTA updates are ridiculiously slow. So as others can update OTA (those not with Sprint) we cant, UNLESS we manually download the update and use adb sideload to update. Which is what im trying to do, but because I have twrp recovery already installed on build NMI81C, I need to revert back to stock firmware but can't find any stock firmware for NMI81C thus leaving me stuck on NMI81C with twrp.
Not only that, is root check is saying its not rooted.
Download the NMI81C firmware from https://www.essential.com/developer/current-builds and then you should be able to just flash the boot from that package by adding .img to the "boot" file and then flashing it via "fastboot flash boot boot.img". After that you should be able to boot into the stock recovery and then select apply update via adb. Just use the command "adb sideload ota.zip" to begin the update.
Just a closer, was able to revert back to stock firmware but on firmware NMJ20D and remove TWRP recovery. I just finished installing the NMJ32F firmware on my Sprint variant. No longer on NMI81C
now I can start looking into getting TWRP and such back on my phone, thank you guys
Barshalen said:
Download the NMI81C firmware from https://www.essential.com/developer/current-builds and then you should be able to just flash the boot from that package by adding .img to the "boot" file and then flashing it via "fastboot flash boot boot.img". After that you should be able to boot into the stock recovery and then select apply update via adb. Just use the command "adb sideload ota.zip" to begin the update.
Click to expand...
Click to collapse
damn I just got done doing all that without help, but thank you for that. I didnt have to download the NMI81C firmware tho, just went straight to NMJ20D and then updated to NMJ32F.
After sideloading latest firmware, does the bootloader still say Variant - Sprint? Is there a way to make the Variant openus since the hardware is the same?
timkennett said:
After sideloading latest firmware, does the bootloader still say Variant - Sprint? Is there a way to make the Variant openus since the hardware is the same?
Click to expand...
Click to collapse
Oh, do keep us informed if you find a way to modify the Variant. My phone doesn't list anything after Variant (no Sprint or OpenUS) even though I bought mine from Sprint. I sent a tech request to essential, waiting to hear back.