I got bootloop so I flash aug rom with miflash,and I update it to descember,after I update to latest december update (nougat),I don't get oreo update again even I try to factory reset,clear data frame work,etc,any solution?
aditsubrata said:
I got bootloop so I flash aug rom with miflash,and I update it to descember,after I update to latest december update (nougat),I don't get oreo update again even I try to factory reset,clear data frame work,etc,any solution?
Click to expand...
Click to collapse
you must wait until several hours or days again
Sent from my Mi A1 using Tapatalk
aditsubrata said:
I got bootloop so I flash aug rom with miflash,and I update it to descember,after I update to latest december update (nougat),I don't get oreo update again even I try to factory reset,clear data frame work,etc,any solution?
Click to expand...
Click to collapse
If u can't wait u can flash a pre rooted stable oreo
Related
Just a PSA, if you update to build NMJ51B you will not be able to sideload the Oreo beta 1 update. It will error saying your current build has a newer date and downgrade is not allowed.
eman5oh said:
Just a PSA, if you update to build NMJ51B you will not be able to sideload the Oreo beta 1 update. It will error saying your current build has a newer date and downgrade is not allowed.
Click to expand...
Click to collapse
Confirmed
I should add that unlocking the bootloader will not help, I had to downgrade to NMI81C first to flash the Oreo beta 1.
Can you factory flash NMJ51B when on the Oreo Beta? I keep running into issues when trying to flash.. wondering if that's why.
After running flashall.bat, it will hang up on the first step (flash nvdef.img target didn't report max-download-size)
Same. Just going to wait for beta 2 next week.
Just return back to a previous version from stock using the system dumps in the other thread. I can confirm this will allow you to install the update.
DiamondDave98 said:
Same. Just going to wait for beta 2 next week.
Click to expand...
Click to collapse
The wait is over...newly released beta 2 is up!
can i side load oreo on NM164C build?
ali.sbi said:
can i side load oreo on NM164C build?
Click to expand...
Click to collapse
Where did you get that build from?
Caltinpla said:
Where did you get that build from?
Click to expand...
Click to collapse
it's completely stock that i just got my ph-1. can i update to oreo with ADB over this build?the system updates shows me a new build but when i want to update it says that can't download,any suggestions?
ali.sbi said:
it's completely stock that i just got my ph-1. can i update to oreo with ADB over this build?the system updates shows me a new build but when i want to update it says that can't download,any suggestions?
Click to expand...
Click to collapse
Yes, you can.
If you feel comfortable with ADB flashing then you can flash the latest Oreo beta 2 over N without problems. Just follow the instructions, download links, and steps directly form Essential website.
Did anyone get this new update? I wonder what's this about. It's just around 63 MB.
FYI I've previously updated to the latest December 1 2017 patch 2 weeks ago.
skroder said:
Did anyone get this new update? I wonder what's this about. It's just around 63 MB.
FYI I've previously updated to the latest December 1 2017 patch 2 weeks ago.
Click to expand...
Click to collapse
Yep. Another small update.
Build number: N2G47H.7.12.19
Displax said:
Yep. Another small update.
Build number: N2G47H.7.12.19
Click to expand...
Click to collapse
No glaring bugs so far?
Installed. And again, no changelog. Only God knows what they've done
Enviado do meu Mi A1 através de Tapatalk
amithiel said:
Installed. And again, no changelog. Only God knows what they've done
Enviado do meu Mi A1 através de Tapatalk
Click to expand...
Click to collapse
Same here. New update with 0 info
Still with 1 December security patch level.
Any changes in the kernel ?
Yash67 said:
Any changes in the kernel ?
Click to expand...
Click to collapse
Recieved this update, cant figure out what it changed? May be getting ready for O?
Guys i recieved the updated but is stuck información step 2 (installing), what should i do??
They updated the kernel, the previous one was from December 1st, now it's December 19th.
Bluexmorningx said:
Guys i recieved the updated but is stuck información step 2 (installing), what should i do??
Click to expand...
Click to collapse
Just wait, it took time on mine but completed eventually.
Got mine as well, was rooted with Magisk. Restored boot image, then installed the update, and rebooted. Then installed Magisk again. This was the easiest time I have ever had with the root/magisk/ota.
Micka84 said:
They updated the kernel, the previous one was from December 1st, now it's December 19th.
Click to expand...
Click to collapse
mine is 7 december
goofball2k said:
Got mine as well, was rooted with Magisk. Restored boot image, then installed the update, and rebooted. Then installed Magisk again. This was the easiest time I have ever had with the root/magisk/ota.
Click to expand...
Click to collapse
Can u tell me how u restored boot image?
goofball2k said:
Got mine as well, was rooted with Magisk. Restored boot image, then installed the update, and rebooted. Then installed Magisk again. This was the easiest time I have ever had with the root/magisk/ota.
Click to expand...
Click to collapse
Can you please describe what you have done? Would also be interesting for me. I tried to restore stock boot image via Magisk Unistaller (Magisk-uninstaller-20171222.zip) in booted (not installed) TWRP. And also directly with fastboot from fastboot ROM image with
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Both attemps ended with a bootlop. After i installed Magisk via TWRP again, the bootloop was gone and system booted as before (but i cannot install the update via updater then). Thanks!
Can anyone on N check if a /dsp partition is mounted?
If it is, it confirms that this update is a preparatory one for O.
ur0 said:
Can anyone on N check if a /dsp partition is mounted?
If it is, it confirms that this update is a preparatory one for O.
Click to expand...
Click to collapse
Today Update
I updated directly from October to December (not the new patch, the first December one) without problems using the OTA updater & I'm rooted with Magisk.
First I unlocked the bootloader, temp booted TWRP using fastboot boot and flashed Magisk 14.5 using that. This way recovery is not modified & I can still root - did not allow system modifications in TWRP. No data was wiped and it worked fine.
For updating I used the instructions here (restore stock boot > step 1 OTA > Install Magisk to 2nd slot in app > step 2 OTA > Done. kept root and did OTA successfully.
Hope this helps people stuck with OTAs, it worked for me.
Micka84 said:
They updated the kernel, the previous one was from December 1st, now it's December 19th.
Click to expand...
Click to collapse
Same Here.
Hello I have been unable to update to the January, my pixel shows "Couldn't update - installation problem"
I have installed the Stock Pixel 2 Kernel + SafetyNet Patch from here
I am thinking it might be causing the issue?
Where would I get the stock kernel for 8.1.0 December 5th security patch level?
rweddy1 said:
Hello I have been unable to update to the January, my pixel shows "Couldn't update - installation problem"
I have installed the Stock Pixel 2 Kernel + SafetyNet Patch from here
I am thinking it might be causing the issue?
Where would I get the stock kernel for 8.1.0 December 5th security patch level?
Click to expand...
Click to collapse
Seriously? You didn't even want to read twrp topic
joloxx9joloxx9 said:
Seriously? You didn't even want to read twrp topic
Click to expand...
Click to collapse
Got it thanks
rweddy1 said:
Got it thanks
Click to expand...
Click to collapse
whered u find it
From google factory images here, the boot image is the stock kernel, if you flash this then you are back to stock.
Cheers,
Hye, I wanna try stock ROM of FRD-L09C432 as this ROM has the latest security update and patches (B402), now i'm on stock ROM FRD-L09C636 (still on B389,no update via OTA). My question is, can i just flash the FRD-L09C432 update using dload mode or there is another ways? My phone boot-loader is locked and not rooted. TIA
Hi. I did try the dlod method on my honor 8 (FRD-L09C432) and it worked fine. No problems at all. I am now on B399 and december security patch.
BlChaT said:
Hi. I did try the dlod method on my honor 8 (FRD-L09C432) and it worked fine. No problems at all. I am now on B399 and december security patch.
Click to expand...
Click to collapse
But my phone is on FRD-L09C636, can it still work?
Hey here I will share OTA for our NB1 to flash with stock recovery and sdcard method.
If I'm right it will work.
Pls try and report.
Download zip file,
Copy to external sdcard
Reboot to recovery,
Choose update from SD and press power button.
I will start with June security patch.
https://drive.google.com/file/d/1G0qg1b0ZbWjvWi3_WnimY3oy0xexRyXh/view?usp=drivesdk
Powered by View 10
Will work with sideload too, right?
hi
2WildFirE will this update patch can use and support for Nokia 8 TA-1004 Dual sim, i'm from malaysia region...
Unluckily it errors when installing on an unlocked phone....I unrooted it fully, rebooted to recovery and it errors always. Should I relock the bootloader to install OTAs?
No, you do not need to block the boot loader. You need to flash the previous full update 4.88B. And then upgrade to OTA.
I am already on 4.88B (rooted with magisk). No modification has been made on /system partition. I uninstalled magisk and rebooted: in theory that should be enough but in practice it does not work....
Topogigi said:
I am already on 4.88B (rooted with magisk). No modification has been made on /system partition. I uninstalled magisk and rebooted: in theory that should be enough but in practice it does not work....
Click to expand...
Click to collapse
It won't if this is block-based OTA as Magisk modifies boot partition (with Android kernel and in A/B case recovery too). Quote from Android official documentation: "block OTA handles the entire partition as one file and computes a single binary patch".
Sure, but I uninstalled magisk thus restoring original boot partition before trying to apply OTA...
dark ghost1988 said:
2WildFirE will this update patch can use and support for Nokia 8 TA-1004 Dual sim, i'm from malaysia region...
Click to expand...
Click to collapse
Thanks for reporting [emoji1360]
Powered by View 10
support
does this firmware are support for Nokia 8 TA-1004 dual sim...??
End of the story: I reflashed the full 4.88B OTA update and immediately after the new june patch: it always gives an error. Tried to install the june patch by OTA, and it errors in the same way. I have the doubt that the new patch is allowed to check the bootloader and if it founds it unlocked, an error arises. Anyone confirming that?
Topogigi said:
End of the story: I reflashed the full 4.88B OTA update and immediately after the new june patch: it always gives an error. Tried to install the june patch by OTA, and it errors in the same way. I have the doubt that the new patch is allowed to check the bootloader and if it founds it unlocked, an error arises. Anyone confirming that?
Click to expand...
Click to collapse
Ok, I assume that noone had problems in updating to the june security patches with an unlocked bootloader, so there must be a problem with my device......
Ok I managed to update to june security patches with this file......Had to reflash both slots (A/B) with the full june camera update (4.88B), then I updated through recovery and it worked. Glad to tell that the system is fully tested and working.
No news about July security patch?
Topogigi said:
End of the story: I reflashed the full 4.88B OTA update and immediately after the new june patch: it always gives an error. Tried to install the june patch by OTA, and it errors in the same way. I have the doubt that the new patch is allowed to check the bootloader and if it founds it unlocked, an error arises. Anyone confirming that?
Click to expand...
Click to collapse
confirmed ..
thats what happened to me
after i unlocked my bootloader ,rooted mgdisk
after July's OTA
i cant fastboot to june stock firmware
i even tried to sideload the june OTA and it said
that i cant downgrade from July to june
Topogigi said:
Ok I managed to update to june security patches with this file......Had to reflash both slots (A/B) with the full june camera update (4.88B), then I updated through recovery and it worked. Glad to tell that the system is fully tested and working.
Click to expand...
Click to collapse
Thanks Topogigi
How did you do it ?
im kinda stuck here
im considering OST LA ?
Any Ideas ??:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
why666me said:
Any Ideas ??:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
have you tried switching slots? it sure wont solve the issue stated but it may restore the usability of your expensive brick :laugh:
Code:
If you are currently on slot A, type this: fastboot --set-active=_b
Or on slot B type this: fastboot --set-active=_a
No Switch with locked bootloader ?
Nothing work on fastboot with locked bootloader....
issue solved using OST LA 6.0.4