Despite some saying that the M1D36H update was the last one already, today I got another update on my watch: M1D64K
As always, here's a download to the OTA package and already pre-built IMG files!
OTA ZIP DOWNLOAD LINKS:
DropBox
Google Drive
OneDrive
IMG READY-TO-FLASH DOWNLOAD LINKS:
DropBox (boot, recovery, system)
Google Drive (boot, recovery, system)
OneDrive (boot, recovery, system)
---------------
HOW TO INSTALL:
Download all the IMG files from above (system, boot and recovery)
Boot your watch into fastboot mode by rebooting and then constantly swiping from the left upper to the lower right corner when the LG logo comes on
Open a CMD window in the same directory (open folder, hold SHIFT and Right-Click > "Open command window here")
Use the following commands to flash all 3 files
Code:
fastboot flash system system_STOCK_6.0.1_M1D64K.img
Code:
fastboot flash boot boot_STOCK_6.0.1_M1D64K.img
Code:
fastboot flash recovery recovery_STOCK_6.0.1_M1D64K.img
Use "fastboot reboot" or the onscreen menu to reboot your watch back into Android Wear and enjoy your up-to-date watch!
---------------
Anyways, I hope this helped a bit!
!!!ATTENTION TO ALL INVISIBLEK KERNEL USERS!!!
It seems that the watch does NOT want to boot anymore after flashing the Invisiblek kernel which is sad, so you're stuck with the stock kernel for however long it takes for him to update it.
Received the update today and everything seems fine so far. Any idea what the update brings to the table? I don't notice anything new.
lattosimbaste said:
Received the update today and everything seems fine so far. Any idea what the update brings to the table? I don't notice anything new.
Click to expand...
Click to collapse
November security patch?
Seems likely, no real differences noted 12 hours on.
Should we thank LG or Google for this?
Is there a way to remove the update nag?
I received the December 1st security update just now.
M1D64S
Nick N said:
I received the December 1st security update just now.
M1D64S
Click to expand...
Click to collapse
I have another Smartwatch now but I'll try to grab the update and make some images of it again. Not sure when or even if tho.
You guys are missing the new update that came today, M1D64S
@ EpicLPer
here it is the new update link!
https://android.googleapis.com/pack.../8fcd79e93dc661a711856fd5476dfd4e05aca787.zip
Don't forget about today's update M1D65B
brostar14 said:
Don't forget about today's update M1D65B
Click to expand...
Click to collapse
hope to get the IMG soon, the update notification drives me crazy.
Related
Has Anyone Got it yet? some nexus 4 and nexus 7 users are getting it right now in the usa it seems
http://www.androidpolice.com/2013/02/11/breaking-android-4-2-2-update-rolling-out-to-gsm-galaxy-nexus-nexus-7-nexus-10/
come on developers drop it to ROMs !!
anyone receive it
please help to find the ota link
step
http://forum.xda-developers.com/showpost.php?p=21025378&postcount=27
Popped up on my daughter's stock, unrooted N7 about 5 minutes ago. I assume because I'm running a custom ROM with a custom recovery OTAs will be blocked on my N10 (that's how it was on my OG Droid and LTE GNexus).
I might have been excited about this a few months ago but now it's just meh.. I'll just wait for Rascarlo to update RasBean... My tablet is rock solid stable right now.. I'm in no rush to beta test another one of Googles messes.
Nexus 10 4.2.2 OTA URL
Hi all,
You can download 4.2.2 OTA from below link. Have a fun!! :fingers-crossed:
MD5:ed637878ccba20ba9d44e62685ac67e9
http://android.clients.google.com/p...igned-mantaray-JDQ39-from-JOP40D.eaef1443.zip
saltxyz said:
Hi all,
You can download 4.2.2 OTA from below link. Have a fun!! :fingers-crossed:
MD5:ed637878ccba20ba9d44e62685ac67e9
http://android.clients.google.com/p...igned-mantaray-JDQ39-from-JOP40D.eaef1443.zip
Click to expand...
Click to collapse
awesome thanks ! now how to update ?
nightfox11 said:
awesome thanks ! now how to update ?
Click to expand...
Click to collapse
adb sideload UPDATE-NAME.zip from Recovery with Android SDK
Not showing up for me in Canada yet.
Sent from my GT-I9300 using xda premium
espionage724 said:
adb sideload UPDATE-NAME.zip from Recovery with Android SDK
Click to expand...
Click to collapse
And with stock rom and stock recovery? Update from zip?
lKBZl said:
And with stock rom and stock recovery? Update from zip?
Click to expand...
Click to collapse
you should have adb in stock recovery aswell. just boot to stock recovery, make sure that you've configured the drivers and use the above command to install the update via adb
I've never tried that procedure though, but I guess it should work
I'm rooted but with stock recovery. Can I just use OTA root-keeper to temp-unroot, install update and then re-root?
antonusklesk said:
I'm rooted but with stock recovery. Can I just use OTA root-keeper to temp-unroot, install update and then re-root?
Click to expand...
Click to collapse
Yes, but don't temp unroot, backup the root and then use backup to root again.
Cheers, looking forward to getting home and having a play.....even if it is only minor fixes.
And thus starts a barrage of soft brick help threads because toolkits make simple tasks stupidly more complicated then they need to be.
onemandivision said:
you should have adb in stock recovery aswell. just boot to stock recovery, make sure that you've configured the drivers and use the above command to install the update via adb
I've never tried that procedure though, but I guess it should work
Click to expand...
Click to collapse
Can this get me into a soft brick and the comment over this one says?
lKBZl said:
Can this get me into a soft brick and the comment over this one says?
Click to expand...
Click to collapse
Yup.
So, is there a changelog?
lKBZl said:
Can this get me into a soft brick and the comment over this one says?
Click to expand...
Click to collapse
heres what i did:
1) download the latest stock factory image from google: https://developers.google.com/android/nexus/images#mantaray (JOP40C)
2) download the ota update JP40C->JOP40D http://android.clients.google.com/p...gned-mantaray-JOP40D-from-JOP40C.07ac4f5d.zip
3) download the ota update JOP40D->JDQ39 http://android.clients.google.com/p...igned-mantaray-JDQ39-from-JOP40D.eaef1443.zip
4) download the latest team win recovery .img file: http://techerrata.com/browse/twrp2/manta
5) reboot into bootloader mode
6) unzip the stock firmware from step 1)
7) open command line window, cd to folder where image-mantaray-jop40c.zip is, type fastboot update image-mantaray-jop40c.zip (add option -w if you want to clear userdata aswell, this will wipe your sdcard)
8) wait for reboot and get back into bootloader
9) open command line window, cd to folder where the team win recovery image file is, type fastboot flash recovery openrecovery-twrp-2.4.1.0-manta.img (filename can be different depending on the version you downloaded)
10) reboot into bootloader, select reboot recovery, open command line window, cd to where ota updates are, type adb push *filename* /sdcard for each ota update (replace *filename* by actual filename)
11) select install in team win recovery, install update from step 2) first, then update from step 3)
reboot.
you might lose all your data including your files stored on your tablet. this is probably the must reliable way to update because everything is set back to stock and then updated. so no customization whatsoever should interfere
heres the result:
Ignore the post by onemandivision previous steps are easier
Welcome everyone!
This thread has been created for extreme newbies/noobs and for their benefit. Not only noobs, but everyone is free to post questions and also give answers to those questions. Any type of question is allowed as long as it is related about the device. No off-topic discussions are allowed!
Hit Thanks if I Helped You!
Regards,
PoseidonKing
Hello,
I've installed a custom recovery, SuperSU and the xposed framework on my Wileyfox Swift 2 Plus and yesterday I've received an OTA update with wich I was (as expected) unable to update my phone. (it just rebooted to TWRP and did nothing) On their website I was only able to find an older build. I think what I have to do is install the stock recovery(to install the update then switch back to a custom one), but I don't know where to get it from.
boa05 said:
Hello,
I've installed a custom recovery, SuperSU and the xposed framework on my Wileyfox Swift 2 Plus and yesterday I've received an OTA update with wich I was (as expected) unable to update my phone. (it just rebooted to TWRP and did nothing) On their website I was only able to find an older build. I think what I have to do is install the stock recovery(to install the update then switch back to a custom one), but I don't know where to get it from.
Click to expand...
Click to collapse
Here you go. https://drive.google.com/file/d/0B1k2IwBoVgfFVVF1UEY3cUVVY28/view?usp=sharing
I grabbed this from cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87 - flash it via Fastboot preferably.
linuxct said:
Here you go. https://drive.google.com/file/d/0B1k2IwBoVgfFVVF1UEY3cUVVY28/view?usp=sharing
I grabbed this from cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87 - flash it via Fastboot preferably.
Click to expand...
Click to collapse
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
You mean, a Cid face? LOL
You can revert by flashing the system.img via fastboot from the very same zip I mentioned before. You can get it here: http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
E: footer is wrong
E: Signatur verification failed
Installation aborted.
Click to expand...
Click to collapse
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
zerospaced said:
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
I haven't checked myself but linuxct seems to say its an img file. You need to flash img files with fastboot. Have you tried unziping the .zip file and seeing if there are img files (e.g system.img, recovery.img)
If you don't know how to use fastboot here is a good tutorial: https://forum.xda-developers.com/showthread.php?t=2277112
Hope this helps.
zerospaced said:
I flashed TWRP so I can install SuperSU for root access
Click to expand...
Click to collapse
You can enable that inside Developer options > Root access. There's no need to either alter your system nor unlock your bootloader if your only concern is root privileges.
zerospaced said:
... but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
Cyanogen is no more, Wileyfox's switching to an AOSP-based ROM through the following OTAs, which will be Android 7.0 Nougat and will start rolling on february. You've more info here: https://forum.xda-developers.com/swift-2/how-to/official-wileyfox-statement-regarding-t3528844
linuxct said:
You can enable that inside Developer options > Root access. There's no need to either alter your system nor unlock your bootloader if your only concern is root privileges.
Click to expand...
Click to collapse
No, I think that is only there in CyanogenMod (the community based custom rom) not in the Cyanogen OS (the proprietary OS for businesses). As far as I know no OEM can release an android phone with Gapps and root. We have an option there called "OEM unlock" which will allow you to unlock your bootloader (from a computer) but nothing else that would grant root out of box.
zerospaced said:
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
Just flashing back to the stock recovery does not remove SuperSU. Due to your error I'm assuming you have a non-systemless root. In order to remove SuperSU you must flash http://downloadmirror.co/Uot/UPDATE-unSU.zip (with TWRP), and if that doesn't work I would recommend flashing back to full stock cyngn from: https://cyngn.com/support.
Cheers!
linuxct said:
You mean, a Cid face? LOL
You can revert by flashing the system.img via fastboot from the very same zip I mentioned before. You can get it here: http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
Click to expand...
Click to collapse
Thank you very much, flashing the system.img with
Code:
fastboot flash system system.img
fixed the issue and I was able to update my system to the latest version and since it only changed the system partition, no data (files from internal/external storage) nor apps (not even their data) were deleted. After the update I had to flash TWRP, SuperSU and Xposed again.
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
boa05 said:
Thank you very much, flashing the system.img with
Code:
fastboot flash system system.img
fixed the issue and I was able to update my system to the latest version and since it only changed the system partition, no data (files from internal/external storage) nor apps (not even their data) were deleted. After the update I had to flash TWRP, SuperSU and Xposed again.
Click to expand...
Click to collapse
Thank you, but unfortunately I've read this hint after trying the unsu method described here:
https://forum.xda-developers.com/showpost.php?p=63615067
I've installed the unsu-zip package and flashed the original boot.img via TWRP. It did not help, but since I did this I have another warning message when booting: "The dm-verity is not started in enforcing mode."
In the end I managed to get the update by installing the original zip package again and after this the OTA update worked.
What still remains is the new "dm-verity error message" right after booting....
Does anyone know if there is anywhere I can find the files to manually update to the new AOSP based ROM. Or has Wileyfox not released it?
(Or has anyone captured the PTA link?)
There is currently no new AOSP ROM. I've received only Cyanogen OS update (probably the last one?). According the Wileyfox statement on facebook, the new ROM (Nougat) will be released in the february...
rivierakid said:
There is currently no new AOSP ROM. I've received only Cyanogen OS update (probably the last one?). According the Wileyfox statement on facebook, the new ROM (Nougat) will be released in the february...
Click to expand...
Click to collapse
Nah they are releasing an update first to transition to their new rom.
"We have been ruthlessly testing this and planning a distribution for this update, with a rollout to be released beginning today with immediate effect." -Wileyfox Facebook
Click to expand...
Click to collapse
Then later (between February and end of Q1) they will release nougat. Its an easy mistake to make as they aren't too clear about it.
Thanks anyway.
It is unclear what kind of ROM will they release. According the statement it should be bloatware free OS
AOSP, Lineage OS, something else?
I really like cyanogenmod, so I hope there will be Lineage OS ROM in the future...
The new update
Hi, I'm not in the least technologically minded so please don't take the mick when I ask, will the new update delete the cyanogen os? Or is that something I will have to do? If so, what is safe to delete without damaging my phone?
Wow, that was a couple more questions then I had thought!
Thanks all.
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
MCPoppa said:
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
Click to expand...
Click to collapse
I don't think it'd be a good idea to mess with the bootloader for now. Also, I uninstalled SuperSU from the app. If you have xposed I suggest you uninstall that too (At least that's what I did). Sorry I can't help more I 'm still a little newby myself.
rivierakid said:
It is unclear what kind of ROM will they release. According the statement it should be bloatware free OS
AOSP, Lineage OS, something else?
I really like cyanogenmod, so I hope there will be Lineage OS ROM in the future...
Click to expand...
Click to collapse
Sadly, an OEM cannot rely on community-driven software, so it surely won't be CyanogenMod/Lineage. But, that doesn't mean that in the future we wouldn't be able to enjoy it thanks to custom ROM development
Jahane said:
Hi, I'm not in the least technologically minded so please don't take the mick when I ask, will the new update delete the cyanogen os? Or is that something I will have to do? If so, what is safe to delete without damaging my phone?
Wow, that was a couple more questions then I had thought!
Thanks all.
Click to expand...
Click to collapse
Welcome to the community!
This depends on what you understand about 'new update'. If the new update you're talking about is the currently rolling OTA, the one that's getting prompted on every phone right now, no, that won't delete CyanogenOS yet, but prepare the device to upgrade to a CyanogenOS-free Android 7.0 ROM, which will happen in a month or so. You won't have to do anything but let the phone update each and every single time it requests it. Cyanogen itself is not something you can remove as a user, unless you install what's called a custom ROM (this means, a different ROM software than the one provided by Wileyfox), so, you don't need to worry about it but keeping your device up-to-date as soon as it prompts you with an update ^_^
MCPoppa said:
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
Click to expand...
Click to collapse
Try relocking like you said, but before, flash everything included in the latest CyanogenOS fasboot image zip (from here). To flash all of them at once, execute each and every of the following commands:
Code:
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash modem NON-HLOS.bin
fastboot flash dsp adspso.bin
fastboot flash devcfg devcfg.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash splash splash.img
fastboot flash tz tz.mbn
Once done, relock your bootloader by doing:
Code:
fastboot oem lock
Please note, this probably doesn't fully lock your bootloader, as some propietary DRM keys might've been lost during the unlock process...
Good luck and please, keep us posted!
Dumped via non-flashed (only live booted) TWRP so I can dump the original recovery too.
Can be flashed in fastboot mode!
To flash these images reboot your watch, swipe from the top left to the bottom right corner when you see the LG logo and connect it to your PC.
Then in a command line enter:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Neat All-In-One Backup Document: DropBox Paper
Downloads: (Folder (dl.epiclper.com) - Folder (OneDrive))
ALL-IN-ONE zip (system.img, boot.img, recovery.img): Dropbox (252MB) - OneDrive Backup
recovery.img: Dropbox (22 528KB) - OneDrive Backup
boot.img: Dropbox (22 528KB) - OneDrive Backup
MD5 Hashes:
dory_601_M1DN65N_170506.zip: 9E938F49AAE17C6ED09AD7AFFDCFACEC
recovery.img: 62C1CBE5F2C16DD0FC387C772A800368
boot.img: 5430070B5C5E2D204B6C35F7C749B6D2
If you need more partitions tell me below, I've only included these ones so far because I know they won't contain any personal or device specific information and should be flashable on other devices too. However I've dumped every single one existing on the LG G Watch
Thanks i used it to restore from bootloop Android wear 2
So that's the latest original firmware right?
Yes, this is the stock ROM from LG.
MihaiSG said:
Yes, this is the stock ROM from LG.
Click to expand...
Click to collapse
Do you need to relock the bootloader after you flash it?
Not really. If you want your warranty back relock it.
dumb question : is it possible to have the bootloader, too ? just in case
StrangeSavage said:
dumb question : is it possible to have the bootloader, too ? just in case
Click to expand...
Click to collapse
You can find latest bootloader in my factory images thread, it hasn't been updated since
Xmaster24 said:
You can find latest bootloader in my factory images thread, it hasn't been updated since
Click to expand...
Click to collapse
thank you very much ! got DORYZ11c from there. looked at my G Watch and it has DORYZ12c now. I guess it arrived with some update sometime then.
anyway, as I'm not rooted I can't dump it (right now). maybe will root just for that
StrangeSavage said:
thank you very much ! got DORYZ11c from there. looked at my G Watch and it has DORYZ12c now. I guess it arrived with some update sometime then.
anyway, as I'm not rooted I can't dump it (right now). maybe will root just for that
Click to expand...
Click to collapse
you can tell if an OTA has a bootloader update if it contains a bootloader.img inside, the last update to have that was MEC23G so there is no need to dump the bootloader
i got bootloop and nothing can't fix my watch.please help me
Hi,
For those who didn't receive the OTA by now and are on stock, non-rooted, here's the link : (rename to update.zip, update it via settings/update or update via recovery (update or adb sideload) etc.....)
Don't know if it'll work when on stock N-B06 (can't test it because i'm on custom ROM ). Otherwise downgrade to B05 again and upgrade to B08.
EDIT : For those where update.zip not show up (which is a common issue, don't panic, you can wait for the FULL update later on...) try :
1. rename to update.up or fota_B08_B12_ssl.up or A2017GV1.2.0B08.zip
2. try to update over recovery. Inthere try to adb sideload or update via SD
2a : ADB sideload : boot phone into recovery, setup ADB, put zip in ADB folder (you know...or drag it later on in terminal...), open terminal in ADB folder (shift+rightclick open terminal here), type adb devices (there has to be your "device-number" and recovery),on phone apply ADB update, then type command : adb sideload nameofyourzip.zip and enter. Done !
3. don't forget to try either on intSD or extSD
4. wipe cache in recovery and try again...
AFH link : https://androidfilehost.com/?fid=962021903579488106
updated in DownloadCenter : https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
don't just HIT&RUN....there's a :good: button for some reason
Hi,
my Device is on stock B05 and non-rooted. I've downloaded it. renamed und put it in to root of the internal Memory - still no Update found...
Same for me. I've tried place update.zip in internal storage and sd card but update not found.
Adb sideload works
I renamed the file to update.zip and put it on a microSD Card. Then installed over recovery. It worked. I was on original B05 before.
@jopomopo,
please tell the community how you did with sideload ADB. Thanks
dodo34 said:
I renamed the file to update.zip and put it on a microSD Card. Then installed over recovery. It worked. I was on original B05 before.
@jopomopo,
please tell the community how you did with sideload ADB. Thanks
Click to expand...
Click to collapse
I did that to but as always installation failed. What i did is to boot into recovery and choose there adb sideload. On your computer you send valid file with adb sideload update zip to the phone. Of course you have to have valid adb files installed on computer and know your way how to use power shell.
Can someone extract the modem of this rom and upload it here?
That would be really nice.
some new features spotted ?
Angelo_0 said:
some new features spotted ?
Click to expand...
Click to collapse
No new features. However, I have the impression that the fingerprint scanner is quicker. Anyone else?
For me it doesn't work via system update but it works perfectly via ADB sideload. I do not saw any major changes. October security. And IMO feels a little bit faster in every point (figerprint + animation + loading of apps).
no full rom?
how to enable VoLTE ?
MrMD69 said:
For me it doesn't work via system update but it works perfectly via ADB sideload. I do not saw any major changes. October security. And IMO feels a little bit faster in every point (figerprint + animation + loading of apps).
Click to expand...
Click to collapse
Same for me.
I needed to sideload the OTA (not an OTA anymore :silly.
And nothing relevant too in rom. It's enough for me anyway : security patch is already good to have.
Enjoy!
MrMD69 said:
For me it doesn't work via system update but it works perfectly via ADB sideload. I do not saw any major changes. October security. And IMO feels a little bit faster in every point (figerprint + animation + loading of apps).
Click to expand...
Click to collapse
Updated through ota (from b05). Indeed, things seem a bit faster. Most noticable for me is the fingerprint sensor.
Too early to confirm, but battery seems better than B05.
i think screen dpi a bit lower .so thats good
and ram performance noticable better
Hi
I am actually on B06, if I make a downgrade to B05 I loose all my data?
no .
Is there any TWRP version of this update available?
Upgraded to B08. Method:downgraded to B05 and then updated from recovery. Till now all is ok
Anyone got aboot from B05 (emmc_appsboot.mbn)? I am rooted stock. I restored untouched system and stock recovery but I get an aboot error on flash. I flashed aboot downgrade to B01 back in April to get fastboot back : https://forum.xda-developers.com/showpost.php?p=71847111&postcount=39
Hi everybody
I've got a problem...
Downloaded latest OTA update from "xiaomi.eu", agreed to install, the phone then rebooted in to fastboot mode and does nothing else.
Rebooted the phone with adb command "fastboot continue" and this went well...it rebooted the system.
Now every time i restart the phone it reboots in to fastboot mode and i have to "fastboot continue" again.
I am also not able to enter recovery because the phone always enters fastboot mode.
Reinstalled recovery (Twrp-3.4.2B_toco_by.alex.msk1407.img) via ADB succesfully, but when i "fastboot reboot recovery" it reboots back into fastboot.
I'm also not able to boot into EDL mode.
Any solution?
Thanks
"MI NOTE LITE 8GB/128GB" running "MIUI by xiaomi.eu 12.1.1 | Stable 12.1.1.0(RFNMIXM)
Hi, I 'm in the same case, same model, same version.
I investigated and I can provide more details to help the community to look where to get a match to lightning our lanterns.
I downloaded the last OTA from built-in updater then the device was trapped in fastboot loop.
Unable to reboot/boot with adb/fastboot commands, but able to flash, I tried with différents recoveries,whose the last TWRP (testing version) let us discover the "super partition" (need fastbootd implantation to see it) This is the new OTA update partitioning.
We have to set up the proper flags via adb to perform successfully the update , or cancel the update process to retrieve original partitioning (non-updating state).
The commons way to restore recovery/fastboot might don't work, because system/vendor partitions are hidden inside "super partition" so might result of unknown/doesn't exist partition.
I am still seeking (Android dev super partitioning) and I'll be back when I'll discovered more...
EDIT : Doublon ? Another thread is open
https://forum.xda-developers.com/t/...astboot-after-updating-to-android-11.4223957/
EDIT: many users had a similar issue.
Will try with any another GSI rom, downloading...
opposatto said:
Hi, I 'm in the same case, same model, same version, I investigated and I can provide more details to help the community which lantern to pickup.
I downloaded the last OTA from built-in updater then the device was trapped in fastboot loop.
Unable to reboot/boot with adb/fastboot commands, but able to flash, I tried with différents recoveries,whose the last TWRP (testing version) let us discover the "super partition" (need fastbootd implantation to see it) This is the new OTA update partitioning.
We have to set up the proper flags via adb to perform successfully the update , or cancel the update process to retrieve original partitioning (non-updating state).
The commons way to restore recovery/fastboot might don't work, because system/vendor partitions are hidden inside "super partition" so might result of unknown/doesn't exist partition.
I am still seeking (Android dev super partitioning) and I'll be back when I'll discovered more...
EDIT : Doublon ? Another thread is open
https://forum.xda-developers.com/t/...astboot-after-updating-to-android-11.4223957/
Click to expand...
Click to collapse
Thank you. I'll be for updates
salsaecoentros said:
Thank you. I'll be for updates
Click to expand...
Click to collapse
Looking around https://source.android.com/devices/tech/ota/dynamic_partitions/implement
opposatto said:
Looking around https://source.android.com/devices/tech/ota/dynamic_partitions/implement
Click to expand...
Click to collapse
EDIT : so here is the idea, not tried yet:
https://source.android.com/devices/tech/ota/dynamic_partitions/implement
Alex msk's twrp is not compatible with android 11. Use orangefox or pitchblack recovery.
Btw i would recommend not upgrading to android 11 at the moment. It has a lot of bugs.
ApexPrime said:
Alex msk's twrp is not compatible with android 11. Use orangefox or pitchblack recovery.
Click to expand...
Click to collapse
So that's the problem....didn't think about that.
Thanks...i Will try one of them and them get back to you.
Thanks
salsaecoentros said:
So that's the problem....didn't think about that.
Thanks...i Will try one of them and them get back to you.
Thanks
Click to expand...
Click to collapse
Hi...
Sorry for the late Replay.
So i did like you said and installed new twrp and...what do you know...ir worked like a charme. No more issues.
Thank you do much.