Has anyone tested the latest beta leaks for the Note 8 One UI N950USQU5DRL5, DRL6, or DRL7. Here is a LINK to Androidsage with instructions. I am tempted to install however I have a Gear S2 watch and Gear VR. If I read correctly DRL6 and 7 work with the gear wearable. Here is another LINK that I found that you should look at before installing the latest beta leaks.
madmangunradio said:
Has anyone tested the latest beta leaks for the Note 8 One UI N950USQU5DRL5, DRL6, or DRL7. Here is a LINK to Androidsage with instructions. I am tempted to install however I have a Gear S2 watch and Gear VR. If I read correctly DRL6 and 7 work with the gear wearable. Here is another LINK that I found that you should look at before installing the latest beta leaks.
Click to expand...
Click to collapse
A little search would have helped you out here.. https://forum.xda-developers.com/verizon-galaxy-note-8/help/update-to-pie-announced-t3881335
I've installed N950USQU5DRL7 and both my Gear S2 watch and my Gear VR are working without any problems. So far so good. I changed my theme back to default theme to set the night mode for dark ui and it's working. I'll update this thread if I find any problems.
Only thing I see missing on drl7 is super slow-mo
---------- Post added at 09:04 AM ---------- Previous post was at 09:03 AM ----------
Will we be able to get ota's if we manually flashed the drl7 update?
gabesir said:
Only thing I see missing on drl7 is super slow-mo
---------- Post added at 09:04 AM ---------- Previous post was at 09:03 AM ----------
Will we be able to get ota's if we manually flashed the drl7 update?
Click to expand...
Click to collapse
No.. Have to flash back to CRK1.
I wanted DRL7 after having done the DRL5 update...........so had to Odin back to CRK1.......................phone was in a bootloop for several hours before I was able to get into Recovery mode................so not looking forward to doing again to get the official Pie update, but will have to at some point.
anyone have a CRK1 spr file to DL please
.........with very detailed instructions would be helpful, don't want to get into a bootloop.
ycats said:
.........with very detailed instructions would be helpful, don't want to get into a bootloop.
Click to expand...
Click to collapse
did you flash CRK1? whats the issue?
ycats said:
I wanted DRL7 after having done the DRL5 update...........so had to Odin back to CRK1.......................phone was in a bootloop for several hours before I was able to get into Recovery mode................so not looking forward to doing again to get the official Pie update, but will have to at some point.
Click to expand...
Click to collapse
You just need to make sure you hold the buttons down securely so they don't come up a little bit and it's a lot harder to keep them held down with a case on the phone.. You need to hold all 3 buttons for up to 2 minutes sometimes and if you don't that's why you get stuck in a boot loop..
gabesir said:
did you flash CRK1? whats the issue?
Click to expand...
Click to collapse
I did the Odin back to CRK1 and after it "passed" and rebooted, got into a continuous bootloop for several hours.
---------- Post added at 02:40 PM ---------- Previous post was at 02:39 PM ----------
MrMike2182 said:
You just need to make sure you hold the buttons down securely so they don't come up a little bit and it's a lot harder to keep them held down with a case on the phone.. You need to hold all 3 buttons for up to 2 minutes sometimes and if you don't that's why you get stuck in a boot loop..
Click to expand...
Click to collapse
I had removed the case and held the three buttons for five minutes.
ycats said:
I did the Odin back to CRK1 and after it "passed" and rebooted, got into a continuous bootloop for several hours.
---------- Post added at 02:40 PM ---------- Previous post was at 02:39 PM ----------
I had removed the case and held the three buttons for five minutes.
Click to expand...
Click to collapse
I read that another user said they had to hold it for over 7 minutes?? That seems excessive but idk I've never had that problem yet.
ycats said:
I did the Odin back to CRK1 and after it "passed" and rebooted, got into a continuous bootloop for several hours.
---------- Post added at 02:40 PM ---------- Previous post was at 02:39 PM ----------
I had removed the case and held the three buttons for five minutes.
Click to expand...
Click to collapse
I just remembered something.. If it ever does that to you again open a command prompt or terminal and send the reboot recovery through ADB. I know you know how to use adb but to those of you who don't know just type "adb shell reboot recovery" without the quotes obviously and wait for the phone to do it.. It may work and it may not..
Well, might have to see if it does................I know CRK1 was the update for December, isn't there a newer one for Oreo for January?
Im aware that the one ui android pie update will be dropping soon but im interested in trying this method for testing it before the official release. My question is are you all using sprint carrier locked devices or unlocked devices?
Related
Q&A for [ROM][UPDATED] Asus ZenFone 4 stock WW 6.5.27 deodexed rom [20141009]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
rooting.......be watting
thanks you.
Anyone have music player bug? Playlist and queue dissapear after reboot,and album art caching so lagging
Greenify Cut wake up path also give me freeze and reboot (I think because of Xposed Framework) any solution for this?
Thanks
ww v6.5.30 available...update OTA has failed ,how can i update v6.5.30 for zenfone 4
failed update 6.5.30
hi, i just want to ask why it is always a fail when i update to 6.5.30, im using zenfone 4 kitkat 4.4.2 V6.5.27, it is also rooted. thanks...
Help !!
Me too :'( , i'm in 6.5.27 and after downloaded firmware 6.5.30 it's still error @@ !!
Update Ota
what happen if there is an OTA update from asus? is it safe to update it? thx
It's safe dude,bring new update and fixed some bugs on previous version
For all people who failed OTA Update,,check your /system which mean are you have doing something i.e. removing system apps,modifying build.prop or something else,,bring it back and reupgrade your version
Sent from my ASUS_T00I using Tapatalk
---------- Post added at 06:34 PM ---------- Previous post was at 06:33 PM ----------
Even after updating, Music Player issue still exist,but overall and performance increase after updating
Sent from my ASUS_T00I using Tapatalk
6.5.30 update failed
Arya_3RDNumber said:
It's safe dude,bring new update and fixed some bugs on previous version
For all people who failed OTA Update,,check your /system which mean are you have doing something i.e. removing system apps,modifying build.prop or something else,,bring it back and reupgrade your version
Sent from my ASUS_T00I using Tapatalk
---------- Post added at 06:34 PM ---------- Previous post was at 06:33 PM ----------
Even after updating, Music Player issue still exist,but overall and performance increase after updating
Sent from my ASUS_T00I using Tapatalk
Click to expand...
Click to collapse
hi..I already installed all of the system apps that I've deleted and unroot my phone...but I still have same error on the 6.5.30...maybe I'll just have to wait for the 6.5.30 file to flash it...
After flashing this system img, i am unable to on my wifi .. it just dosent get on ... please help me
matthewarenn said:
hi..I already installed all of the system apps that I've deleted and unroot my phone...but I still have same error on the 6.5.30...maybe I'll just have to wait for the 6.5.30 file to flash it...
Click to expand...
Click to collapse
When come to babydroid and indicated as upgrading/updating, try to push vol.up + vol.down hold it until 50% updating process or more. It will skip the error.
Rd Batam said:
When come to babydroid and indicated as upgrading/updating, try to push vol.up + vol.down hold it until 50% updating process or more. It will skip the error.
Click to expand...
Click to collapse
will tty that...hope it works...crossfingers..
---------- Post added at 09:53 PM ---------- Previous post was at 08:55 PM ----------
Rd Batam said:
When come to babydroid and indicated as upgrading/updating, try to push vol.up + vol.down hold it until 50% updating process or more. It will skip the error.
Click to expand...
Click to collapse
still error even i press the volume up and down...
matthewarenn said:
will tty that...hope it works...crossfingers..
---------- Post added at 09:53 PM ---------- Previous post was at 08:55 PM ----------
still error even i press the volume up and down...
Click to expand...
Click to collapse
WW_6.5.30 ROM zip has been uploaded by ASUS on http://dlcdnet.asus.com/pub/ASUS/ZenFone/A400CG/ASUS_T00I_WW_6_5_30_UpdateLauncher.zip
Extract it and get the UL_ASUS-xxxx-user.zip, move to SD card/storage root folder the restart the phone.
Notification update will show and follow the wizard.
Do the same trick as quoted before (press and Hold the vol.up+vol.down when the babbydroid show until updateing 50% or more).
I did this and succeed with result unroot system. Goodluck..http://cdn4.xda-developers.com/images/icons/icon12.gif
Rd Batam said:
WW_6.5.30 ROM zip has been uploaded by ASUS on http://dlcdnet.asus.com/pub/ASUS/ZenFone/A400CG/ASUS_T00I_WW_6_5_30_UpdateLauncher.zip
Extract it and get the UL_ASUS-xxxx-user.zip, move to SD card/storage root folder the restart the phone.
Notification update will show and follow the wizard.
Do the same trick as quoted before (press and Hold the vol.up+vol.down when the babbydroid show until updateing 50% or more).
I did this and succeed with result unroot system. Goodluck..http://cdn4.xda-developers.com/images/icons/icon12.gif
Click to expand...
Click to collapse
ill try this and praying that this works...crossing my toe fingers...thanks a lot...
Rd Batam said:
WW_6.5.30 ROM zip has been uploaded by ASUS on http://dlcdnet.asus.com/pub/ASUS/ZenFone/A400CG/ASUS_T00I_WW_6_5_30_UpdateLauncher.zip
Extract it and get the UL_ASUS-xxxx-user.zip, move to SD card/storage root folder the restart the phone.
Notification update will show and follow the wizard.
Do the same trick as quoted before (press and Hold the vol.up+vol.down when the babbydroid show until updateing 50% or more).
I did this and succeed with result unroot system. Goodluck..http://cdn4.xda-developers.com/images/icons/icon12.gif
Click to expand...
Click to collapse
hey..i already updated my phone...thanks a lot...your the man
[Request][ROM] Where can i download Stock ROM of Asus Zenfone 4
Can anyone provide me a direct link for downloading kitkat WW 6.5.30 or 6.5.27 stock rom for my asus Zenfone 4
Wi-Fi not working after flashing this ROM
I have downgraded my Asus Zenfone 4 running v6.5.30 using the latest version of this deodexed ROM.
While I was able to flash the ROM successfully onto my Zenfone 4, I was surprised to find out that the Wi-Fi isn't working anymore.
Wi-Fi version shows up as "Unknown" in the Settings > About > Hardware Information.
A screenshot showing the "Wi-Fi version" as unknown is in the attachment.
I tried going back to v6.5.30 by downloading the latest full ROM on Asus' website but the update keeps failing. I tried @Rd Batam's suggestion but unfortunately, it doesn't work.
Can somebody provide us a stock system.img of v6.5.30?
Thanks.
I've got the same issue as you
nandy2783 said:
After flashing this system img, i am unable to on my wifi .. it just dosent get on ... please help me
Click to expand...
Click to collapse
What was the version of your firmware before you flashed this ROM? Mine was running Stock v6.5.30 before flashing into this ROM.
Can somebody help us resolve this problem?
Thanks.
paul0289 said:
I have downgraded my Asus Zenfone 4 running v6.5.30 using the latest version of this deodexed ROM.
While I was able to flash the ROM successfully onto my Zenfone 4, I was surprised to find out that the Wi-Fi isn't working anymore.
Wi-Fi version shows up as "Unknown" in the Settings > About > Hardware Information.
A screenshot showing the "Wi-Fi version" as unknown is in the attachment.
I tried going back to v6.5.30 by downloading the latest full ROM on Asus' website but the update keeps failing. I tried @Rd Batam's suggestion but unfortunately, it doesn't work.
Can somebody provide us a stock system.img of v6.5.30?
Thanks.
Click to expand...
Click to collapse
Sir I have exactly the same issue.. tried with flashing v6.5.30 so many times.. it's keeps on failing.. my WiFi is not gonna work anymore...
tvsijin said:
Sir I have exactly the same issue.. tried with flashing v6.5.30 so many times.. it's keeps on failing.. my WiFi is not gonna work anymore...
Click to expand...
Click to collapse
Maybe I'll just try upgrading my little brother's Zenfone 4 running Jellybean into v6.5.30, make a system.img out of it and see if I can flash it via fastboot.
I am trying to check for updates but I am not seeing the recent update that is being pushed out yet, so I was wondering if someone managed to capture the OTA file
Here are the details:
Firmware Version: MSM8960PRO_BP_23255.138.89.00R
Kernel Version: 3.4.42-gb476356 hudsoncm @ ilclbld99 # 1 Tue Aug 25 07:43:11 CDT 2015
System Version: 222.27.5.ghost_row.Retail.en.US
Build Number: LPA23.12-15.5
Pulled this off my phone: https://mega.nz/#!a4Mz2BiQ!VSxGh6g2oLviQ5yO9bhlh9-MCVBTf3GE7vzYZ3ZYvw0
But I haven't been able to apply it, even after using fastboot to flash stock system partition. All the hashes fail comparison.
All my attempts at taking this have failed as well, I even reflashed stock 5.1 from Motorola and tried. Have you tried sideloading this?
crpeck said:
All my attempts at taking this have failed as well, I even reflashed stock 5.1 from Motorola and tried. Have you tried sideloading this?
Click to expand...
Click to collapse
Yes, I think it is a bad OTA. It failed at me as well.
Benoe said:
Yes, I think it is a bad OTA. It failed at me as well.
Click to expand...
Click to collapse
My phone won't even start now. I disabled and uninstalled xPosed and flashed the stock recovery, and restarted and it let me download and install the update. Then I check my phone and it won't start. I get the boot screen with the rotating globe, then just a black screen. Scouring the forums for a fix.
I've tried re-locking the bootloader but can't seem to get that to work now that I've moved to 5.1. The method I used previously just fails. It looked like unlocked bootloaders were failing on the update.
---------- Post added at 10:43 PM ---------- Previous post was at 10:42 PM ----------
adamkaye said:
My phone won't even start now. I disabled and uninstalled xPosed and flashed the stock recovery, and restarted and it let me download and install the update. Then I check my phone and it won't start. I get the boot screen with the rotating globe, then just a black screen. Scouring the forums for a fix.
Click to expand...
Click to collapse
I hate to say this, but, did you try powering it off & back on? Ever since 5.1 whenever I've reloaded the firmware the initial boot always locked up on me.
someone has succeded with the update here:
http://forum.xda-developers.com/moto-x/general/official-moto-x-stagefright-patched-libs-t3200734/page7
crpeck said:
I've tried re-locking the bootloader but can't seem to get that to work now that I've moved to 5.1. The method I used previously just fails. It looked like unlocked bootloaders were failing on the update.
---------- Post added at 10:43 PM ---------- Previous post was at 10:42 PM ----------
I hate to say this, but, did you try powering it off & back on? Ever since 5.1 whenever I've reloaded the firmware the initial boot always locked up on me.
Click to expand...
Click to collapse
I do have an unlocked bootloader on my XT1053 Dev Edition, so maybe you're right, unlocked BLs can't upgrade? Damn shame. I ended up having to format the system partition and completely sideload the stock 5.1 ROM from scratch. Such a pain. I'm holding off on upgrading for now. Either going to get a new phone soon anyway or start flashing ROMs. I never felt the need to flash anything fancy on here since stock Android + Moto's tweaks + some Xposed/GravityBox magic were perfect for me, but I may have to flash something that has Stagefright built in.
I should add, at this point, I'm just glad to have a working phone. I'm no magician with this stuff, and there was a point last night where I thought I had completely bricked my phone.
Check out the link in post #7 above - it worked for me.
I have a Nexus 6, Marshmallow (Build MMB29K). I rooted it using the NRT which installed SuperSU version v2.46. Apparently from the NRT dialogs, the last step of rooting is configuring SuperSU properly.
I get a message that I must update to the latest binaries; but every attempt fails.
I am new at this. Can someone please help?
m_albert69 said:
I have a Nexus 6, Marshmallow (Build MMB29K). I rooted it using the NRT which installed SuperSU version v2.46. Apparently from the NRT dialogs, the last step of rooting is configuring SuperSU properly.
I get a message that I must update to the latest binaries; but every attempt fails.
I am new at this. Can someone please help?
Click to expand...
Click to collapse
stop using toolkits, do it the freaking right way. its MUCH easier the right way. use google, search for the latest supersu, download it, flash it in twrp recovery, then reboot. btw, the toolkits version is VERY old. and you trust the toolkit?
---------- Post added at 09:38 PM ---------- Previous post was at 09:04 PM ----------
latest btw http://download.chainfire.eu/752/SuperSU/BETA-SuperSU-v2.65-20151226141550.zip
simms22 said:
stop using toolkits, do it the freaking right way. its MUCH easier the right way. use google, search for the latest supersu, download it, flash it in twrp recovery, then reboot. btw, the toolkits version is VERY old. and you trust the toolkit?
---------- Post added at 09:38 PM ---------- Previous post was at 09:04 PM ----------
latest btw ...
Click to expand...
Click to collapse
Thank you for the info. Your link fixed it. But please, go a bit easier on me. I'm new to all this.
simms22 said:
.....btw, the toolkits version is VERY old. and you trust the toolkit?
Click to expand...
Click to collapse
lies, all lies.
wug just updated it last week to work on froyo
---------- Post added at 09:06 PM ---------- Previous post was at 09:05 PM ----------
yea simms, take it ez on the noobs geez, not everyone knows it all like you
bweN diorD said:
lies, all lies.
wug just updated it last week to work on froyo
Click to expand...
Click to collapse
I THINK the problem was that TWRP asked if I wanted to install ITS version of SuperSU. I wasn't supposed to allow that; but I did.
EDIT: When I'm nervous, I tend not to read everything carefully.
m_albert69 said:
I THINK the problem was that TWRP asked if I wanted to install ITS version of SuperSU. I wasn't supposed to allow that; but I did.
Click to expand...
Click to collapse
yea, you dont want to do that ever.
bweN diorD said:
yea, you dont want to do that ever.
Click to expand...
Click to collapse
I'm sure that's what happened. I thought it was weird that I had to "swipe to install" twice.
m_albert69 said:
I'm sure that's what happened. I thought it was weird that I had to "swipe to install" twice.
Click to expand...
Click to collapse
another thing, im thinking you should have been using su zip 2.52 also, not 2.4whatever. i could be mistaken, but i always use 2.5*.
---------- Post added at 09:17 PM ---------- Previous post was at 09:13 PM ----------
m_albert69 said:
I'm sure that's what happened. I thought it was weird that I had to "swipe to install" twice.
Click to expand...
Click to collapse
i just noticed simms linked you to 2.65, i wouldnt recommend you use that unless you need it, its systemless and still working out the kinks.
Looking back on my NRT logs, it DID install 2.64. But as I said, during the TWRP recovery I nervously allowed it to do everything it asked of me. That included installing its own version of SuperSU, which must have immediately overwritten NRT's version.
m_albert69 said:
Looking back on my NRT logs, it DID install 2.64. But as I said, during the TWRP recovery I nervously allowed it to do everything it asked of me. That included installing its own version of SuperSU, which must have immediately overwritten NRT's version.
Click to expand...
Click to collapse
actually it more likely made some sort of conflict. 2.64 installs in the kernel, twrp put it in the system, but in all the years i have had a smart phone, i have never used twrps root once.
m_albert69 said:
Thank you for the info. Your link fixed it. But please, go a bit easier on me. I'm new to all this.
Click to expand...
Click to collapse
im sorry for sounding/being so rough on you.. really i am. but stuff like flashing supersu is part of the most very basic knowledge needed. and i mean very basic. i was just trying to get that point across. im normally an extremely nice person :angel:
---------- Post added at 11:04 PM ---------- Previous post was at 11:01 PM ----------
bweN diorD said:
actually it more likely made some sort of conflict. 2.64 installs in the kernel, twrp put it in the system, but in all the years i have had a smart phone, i have never used twrps root once.
Click to expand...
Click to collapse
twrps root, never. its always a very old version, so stay away :good:
Hi
i recently had this problem and overcome it by doing the following
open up settings > click on applications > Application Manager > scroll across to all > scroll down to Supersu and click it (should come up with application info) > click remove installed updates
once that is completed i rebooted (may not be need but better to be safe) the opened up supersu again, and installed the binary with the normal procedure and all updated ok
this was done on my Samsung Galaxy S6 Edge running 3.10.61-S6_UniBase_BOG8_v2, Android Version 5.1.1
i hope this helps someone
regards
Dennis
got the ota today on my phone. is it Marshmellow?
Got it earlier this week.
No, it is not Marshmallow. Marshmallow should be version 6.
Was this question rhetorical? The details are listed in the release notes.
There's some radio related firmware in there for anyone interested. Sometimes that's helpful for people with radio issues.
---------- Post added at 12:07 PM ---------- Previous post was at 12:04 PM ----------
It'd be nice if there was a method to upgrade modem firmware without needing the entire update.zip. That was certainly always a pro with Samsung devices. Odin was nice but Chainfire's Mobile Odin was noice.
Hello, looking for help.
My daughters Ze551kl had an ota update error resulting in a true cyclic bootloop from asus bootup screen to op system which reboots in about 1 second after flashing the op system background.
I cant unlock the bootlock. No operating system access.
I tried to restore with adb sideload and i get response on a pc and the phone that it installs ok, but the bootloop remains. I put 1531 on via adb and i did get the correct files from asus. I have done this several times. No change.
I can't flash because the bootloader is locked and i cant find an adb bootloader level unlock. Does this exist?
What do you folks recommend?
I cannot install twrp or do flashing of recovery. I can get to fastboot and the recovery options. I have cleared the cashes.
Thanks for any advice.
---------- Post added at 11:32 AM ---------- Previous post was at 11:16 AM ----------
Hello, almost forgot, do i need to unlock the bootloader?
If the abd transfer has worked and installed the new version, but the bootloop remains, what else can be done? Is this a partition or hardware problem that showed itself during the update process?
You may have bricked it. Personally, I'd send it to Asus, if it's still in warranty, and let them fixit.
How can I remove the October update on my phone or fix? I install and the phone does not turn on :crying::crying::crying:
https://c.mi.com/thread-2533551-1-0.html same here, fastboot continue worked for me
and reposted here too: https://c.mi.com/thread-2533525-1-0.html - becasue feedbacks they are responding to faster.
I had the same problem, i fixed it by just connecting the device to my laptop using the usb cable.Just restart it once to twice and it worked.
Now when it boots up it says that the update has failed, but when i again update the phone, it shuts down the phone at next login, but when i restart the device again the device was updated to october verson
laviniu_c said:
https://c.mi.com/thread-2533551-1-0.html same here, fastboot continue worked for me
and reposted here too: https://c.mi.com/thread-2533525-1-0.html - becasue feedbacks they are responding to faster.
Click to expand...
Click to collapse
Thanks for fast reply, you safe my ass :victory: the Mi a2 work
Did you guys have any mod installed? Because my phone is just running fine with October patch, updated right now without problems (full stock and locked device)
Labestiajaker said:
Thanks for fast reply, you safe my ass :victory: the Mi a2 work
Click to expand...
Click to collapse
no problem! glad it worked! did you use wifi to download or mobile data?
---------- Post added at 05:25 PM ---------- Previous post was at 05:24 PM ----------
N1ck474 said:
Did you guys have any mod installed? Because my phone is just running fine with October patch, updated right now without problems (full stock and locked device)
Click to expand...
Click to collapse
nope, no root, no changes, not unlocked BL, and not the first ota i did either.
laviniu_c said:
no problem! glad it worked! did you use wifi to download or mobile data?
---------- Post added at 05:25 PM ---------- Previous post was at 05:24 PM ----------
nope, no root, no changes, not unlocked BL, and not the first ota i did either.
Click to expand...
Click to collapse
Wow, that's weird, but it can't be Xiaomi fault, cause the OTA is ok and working fine
laviniu_c said:
no problem! glad it worked! did you use wifi to download or mobile data?
---------- Post added at 05:25 PM ---------- Previous post was at 05:24 PM ----------
nope, no root, no changes, not unlocked BL, and not the first ota i did either.
Click to expand...
Click to collapse
Wifi
N1ck474 said:
Wow, that's weird, but it can't be Xiaomi fault, cause the OTA is ok and working fine
Click to expand...
Click to collapse
i disagree. they are at fault. no ota should brick stock phones. ever. this has happend before on other phones too (mi 9se being the latest one i've seen). some users would update properly and some would just end up with nice and expensive paperweights. via ota. if i was a betting man, i would assume this is related to the version of the bootloader on the phone. and sometime they miss something on the ota update. causing certain versions of the bootloaders to reject the update. but i dont have any expertise here, im just an average joe with a phone that failed an OTA miserably. perhaps just restarting it a couple of times also is enough, but i resurrected mine with the fastboot continue i had found earlier.
laviniu_c said:
i disagree. they are at fault. no ota should brick phones. ever. this has happend before on other phones too (mi 9se being the latest one i've seen). some users would update properly and some would just end up with nice and expensive paperweights. via ota. if i was a betting man, i would assume this is related to the version of the bootloader on the phone. and sometime they miss something on the ota update. causing certain versions of the bootloaders to reject the update. but i dont have any expertise here, im just an average joe with a phone that failed an OTA miserably. perhaps just restarting it a couple of times also is enough, but i resurrected mine with the fastboot continue i had found earlier.
Click to expand...
Click to collapse
I can understand but, if my untouched phone just got an OTA and successfully installed it, the update should be ok, idk why some phones have this type of problem but it's not normal, maybe an old mod? A restored partition after a ROM install? Idk, but i can say that: the OTA is ok on my stock phone, the problem should be something else...
N1ck474 said:
I can understand but, if my untouched phone just got an OTA and successfully installed it, the update should be ok, idk why some phones have this type of problem but it's not normal, maybe an old mod? A restored partition after a ROM install? Idk, but i can say that: the OTA is ok on my stock phone, the problem should be something else...
Click to expand...
Click to collapse
My phone has never been cleaned and modified, September 2019 and other work, but this update brick my phone.
maybe an old mod? A restored partition after a ROM install? Idk, but i can say that: the OTA is ok on my stock phone, the problem should be something else...
nope... nothing new interesting/installed since the previous sept ota. never unlocked, never restored, never rooted it. it is/was plain stock...
Then retry the update, take a backup First, if the OTA brick the phone again ask for a complete refund
Same here, completely stock. Turned off after the Android One screen, restarted and booted again but with an Update Failed notification. Tried it a second time, same thing. First time I have issues with an OTA so far.
My phone is Global Version, I inform if the brick is in this model
N1ck474 said:
Then retry the update, take a backup First, if the OTA brick the phone again ask for a complete refund
Click to expand...
Click to collapse
it's funny, it just got out of warranty. 1y old this month
---------- Post added at 06:09 PM ---------- Previous post was at 06:09 PM ----------
global too
laviniu_c said:
it's funny, it just got out of warranty. 1y old this month
---------- Post added at 06:09 PM ---------- Previous post was at 06:09 PM ----------
global too
Click to expand...
Click to collapse
It doesn't have 2 years of warranty? Btw mine Is Global too, i think(?), it's from Germany
Those who "soft-bricked with OTA" : Just keep trying to reboot many times with external power on and pauses. Sooner or later phone is to reboot to now (after OTA) inactive slot (read about A/B structure if you do not know what i mean) with the previous bootable version (10.0.14.0 ? or any which was there before OTA), - as such behavior is specified in AndroidOne requirements.
N1ck474 said:
It doesn't have 2 years of warranty? Btw mine Is Global too, i think(?), it's from Germany
Click to expand...
Click to collapse
yep you're right 2 years indeed! gonna have fun with the seller )
yep they're all global, there was never a mi a2 for china ( that one is the mi 6x). there is a version for india but i doubt it was ever sold outside india since it has fewer lte bands.
N1ck474 said:
It doesn't have 2 years of warranty? Btw mine Is Global too, i think(?), it's from Germany
Click to expand...
Click to collapse
Mine is from Spain Amazon