Related
I have the dev edition of the moto x 2013. I've unlocked the bootloader successfully. I flashed the Recovery img with this command
Code:
mfastboot flash recovery openrecovery-twrp-2.8.3.0-ghost.img
and flashed the SuperSU.zip (UPDATE-SuperSU-v2.40) through the Recovery successfully. But when I checked to see if it was rooted with Root Checker Basic, it said the Device wasn't.
I'm sure that I've done all the steps right in this guide Guide on "Rooting Unlocked Bootloader". Please Help
PS: I'm new to all this rooting and stuff. Sorry if there is a post out there that covers this. I couldn't find any posts that say this guide didn't work.
Did you download SuperSU from the play store? ?
---------- Post added at 12:38 AM ---------- Previous post was at 12:35 AM ----------
Here is a video guide also... To see if you missed anything,
http://forum.xda-developers.com/showthread.php?t=2487635
Thanks for the video guide! I'll check into it later, as it is kind of late here...
No I did not install SuperSU from the play store. I got it from the link the guide provided me. and sorry I can't post a url since i'm new to this forum
You still at need to install SuperSU. You've flashed the binaries in recovery, but need the app if it isn't in your app drawer.
---------- Post added at 12:51 AM ---------- Previous post was at 12:51 AM ----------
If it is in your app drawer already, open it... See what it says.
Okay. I installed it, updated the binaries, and it flashed for me... It works now. I see why the app is needed. Thank you!!!!
Eh, Quick question, does it matter what android version i need to do a nandroid backup and is it easy?
Android version is irrelevant to make a backup. Yes it's easy... Just go to backup in your recovery, click.... Done. ?
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.
Hey guys so I have a problem.
Tried to upgrade to the Nougat EMUI 5 from EMUI 4.1 on my P9. It installed but it had no camera and no keyboard installed. So I tried to do a factory reset, I did but now I'm stuck in the set up wizard, and can't even complete it because no keyboard (google voice in its place) and if I try to skip step that need input and go to the end it just loops from the beginning.
Next step I took a stock rom of 4.1 and placed it in my external SD card in dload folder and tried to do a force upgrade but no help. It immediately shows 5% and it fails with no error just a red exclamation mark. So next I tried to use fastboot to flash it but get errors saying remote command not allowed (I have HiSuite installed, but the phone doesn't show when I run 'adb devices').
Factory reset fails, erecovery fails to download anything, can't system recover with hisuite as it fails. But when I try it, the fastboot screen on the phone say 'rescue mode entered' so it's being detected.
I'm at my wits end here on how to get it back. Screw latest android, just want to use the phone. Also does this break warranty? I didn't root it or anything but installing unsupported software could be considered warranty void?
Thank you for help in advance
Fybere said:
Hey guys so I have a problem.
Tried to upgrade to the Nougat EMUI 5 from EMUI 4.1 on my P9. It installed but it had no camera and no keyboard installed. So I tried to do a factory reset, I did but now I'm stuck in the set up wizard, and can't even complete it because no keyboard (google voice in its place) and if I try to skip step that need input and go to the end it just loops from the beginning.
Next step I took a stock rom of 4.1 and placed it in my external SD card in dload folder and tried to do a force upgrade but no help. It immediately shows 5% and it fails with no error just a red exclamation mark. So next I tried to use fastboot to flash it but get errors saying remote command not allowed (I have HiSuite installed, but the phone doesn't show when I run 'adb devices').
Factory reset fails, erecovery fails to download anything, can't system recover with hisuite as it fails. But when I try it, the fastboot screen on the phone say 'rescue mode entered' so it's being detected.
I'm at my wits end here on how to get it back. Screw latest android, just want to use the phone. Also does this break warranty? I didn't root it or anything but installing unsupported software could be considered warranty void?
Thank you for help in advance
Click to expand...
Click to collapse
I believe your warranty is still valid since you havent unlocked the bootloader. After upgrading to Nougat you should have downloaded the rollback package from huawei`s page, since you cannot simply go from Nougat back to Marshmallow ( you need to flash two files, first being "an intermediate package", and second one being marshmallow update.app file, both of which can be downloaded from huawei`s official site ). Try this and see if it helps
http://www.carbontesla.com/2016/11/downgrade-rollback-huawei-p9-nougat-to-marshmallow-europe/
Brontok said:
I believe your warranty is still valid since you havent unlocked the bootloader. After upgrading to Nougat you should have downloaded the rollback package from huawei`s page, since you cannot simply go from Nougat back to Marshmallow ( you need to flash two files, first being "an intermediate package", and second one being marshmallow update.app file, both of which can be downloaded from huawei`s official site ). Try this and see if it helps
Click to expand...
Click to collapse
Thanks for the reply, now I know for the future.
In the mean time I fixed it with DC phoenix tool. Although now I have a problem as it set it to C900 so lock screen doesnt update, themes and icons dont work. All issues i can live but would like to fix them. All I know is that I have to unlocka the bootloader, install TWRP, install the version I want with hw and dt folders, and reboot. But everyone on forums speak like you know how to do it and can't find a good guide on how to do it.
Fybere said:
Thanks for the reply, now I know for the future.
In the mean time I fixed it with DC phoenix tool. Although now I have a problem as it set it to C900 so lock screen doesnt update, themes and icons dont work. All issues i can live but would like to fix them. All I know is that I have to unlocka the bootloader, install TWRP, install the version I want with hw and dt folders, and reboot. But everyone on forums speak like you know how to do it and can't find a good guide on how to do it.
Click to expand...
Click to collapse
You`re welcome. DC Phoenix is good, but you have to pay in order to use it, right ? That`s my problem, I cant pay since all my money comes from my dad . In your case I would probably try to update via huawei updater and HiSuite. As far as I`ve seen, that method has been most reliable for the majority of users.
Fybere said:
Thanks for the reply, now I know for the future.
In the mean time I fixed it with DC phoenix tool. Although now I have a problem as it set it to C900 so lock screen doesnt update, themes and icons dont work. All issues i can live but would like to fix them. All I know is that I have to unlocka the bootloader, install TWRP, install the version I want with hw and dt folders, and reboot. But everyone on forums speak like you know how to do it and can't find a good guide on how to do it.
Click to expand...
Click to collapse
I dont know how much research you have done or what you have tried exactly but it sounds like you have made matters worse. I was in your situation before but was able to get past the setup wizard without a keyboard, after this I got ADB working and just installed a keyboard APK.
C900 means you have a cross flashed rom, this can cause all sorts of different issues and I believe when it comes to updates, C900 either gets no updates at all or be the very last in line to get updates. Also, being on C900 could void your warranty.
DC Phoenix worked for me, I found myself in the same position as you (no dload, reocvery, e-recovery only fastboot) and thought my phone was unrecoverable for good. Tried every method possible. in the end bit the bullet paid the fee for DC Phoenix had my phone running in 20 minutes.
Hopefully some smart cookies can develop some freeware that works the same way.
Z-Blade said:
I dont know how much research you have done or what you have tried exactly but it sounds like you have made matters worse. I was in your situation before but was able to get past the setup wizard without a keyboard, after this I got ADB working and just installed a keyboard APK.
C900 means you have a cross flashed rom, this can cause all sorts of different issues and I believe when it comes to updates, C900 either gets no updates at all or be the very last in line to get updates. Also, being on C900 could void your warranty.
Click to expand...
Click to collapse
I fixed it by using DC Phoenix to flash the B163 stock ROM but got the C900 firmware due to cross flashing. I fixed it by unlocking my bootloader, installing TWRP and rooting it. Then I just flashed the C432 OEMINFO, reboot and immidietaly got a notification that an available update is ready to be downloaded (B182). Downloaded it, installed no problem and now I'm on L09C432B182, which is what I wanted, minus all bloatware from my provider (Vodafone)
All done with SRK Tool (in the utilities menu it has for OEM fixing and even the themes not working by flashing the hw_init folders).
Overall, got it running and everything fixed
Fybere said:
I fixed it by using DC Phoenix to flash the B163 stock ROM but got the C900 firmware due to cross flashing. I fixed it by unlocking my bootloader, installing TWRP and rooting it. Then I just flashed the C432 OEMINFO, reboot and immidietaly got a notification that an available update is ready to be downloaded (B182). Downloaded it, installed no problem and now I'm on L09C432B182, which is what I wanted, minus all bloatware from my provider (Vodafone)
All done with SRK Tool (in the utilities menu it has for OEM fixing and even the themes not working by flashing the hw_init folders).
Overall, got it running and everything fixed
Click to expand...
Click to collapse
Awesome, good to hear. I highly recommend you upgrade to Nougat (but make sure your camera app and keyboard app is installed and working). You should be able to do this by using HiSuite and Updater 2.0.
In the same situation
Fybere said:
I fixed it by using DC Phoenix to flash the B163 stock ROM but got the C900 firmware due to cross flashing. I fixed it by unlocking my bootloader, installing TWRP and rooting it. Then I just flashed the C432 OEMINFO, reboot and immidietaly got a notification that an available update is ready to be downloaded (B182). Downloaded it, installed no problem and now I'm on L09C432B182, which is what I wanted, minus all bloatware from my provider (Vodafone)
All done with SRK Tool (in the utilities menu it has for OEM fixing and even the themes not working by flashing the hw_init folders).
Overall, got it running and everything fixed
Click to expand...
Click to collapse
Hi, can you tell me how to use this tool? because unfortunately I'm in the same situation.
mjcaballero said:
Hi, can you tell me how to use this tool? because unfortunately I'm in the same situation.
Click to expand...
Click to collapse
First of all, get your bootloader unlock code. To get it google how to get it (I cant post link as I don't have enough posts to have privileges). If you can't on the English, make a new account on the chinese emui page and use google translate in chrome to navigate. (if the padlock button doesnt give you a form to fill out, clear your cache and cookies or open in incognito mode)
Once you have the code, find the "SRK Tool Huawei Bootloader/ROOT/Recovery/Backup/Utility" thread on XDA and download the latest stable build, should be around 700mb. Also in the thread, the guy posted a video on how to do it.
Step 1: Unlock bootloader
Step 2: install TWRP Recovery
Step 3: Root
These 3 steps are in the video.
Once you successfully rooted, open the tool again and in the Utilities menu (7) there is an option to flash OEMInfo. Select that and choose the OEM info you want. I needed C432. It will use the superuser app to flash it, reboot and you should be on it.
If you are asking how to use DC-Phoenix, again they have both written as well as a video with instructions on how to do it. You don't need an unlocked bootloader as it will use an exploit to circumvent it. Do Method 1, if it doesn't work, do Method 2.
Good luck mate
Z-Blade said:
Awesome, good to hear. I highly recommend you upgrade to Nougat (but make sure your camera app and keyboard app is installed and working). You should be able to do this by using HiSuite and Updater 2.0.
Click to expand...
Click to collapse
I got into this mess in the first place by flashing the B361 and my camera and keyboard didnt work after upgrading it. But now that i know how to fix it, I might give it a shot. Is there a thread with features and testing of the Nougat emui 5 for P9? I saw a lot of threads of people rolling back due to battery issues and other stuff. Don't want to update if its not the best.
Thanks
Fybere said:
First of all, get your bootloader unlock code. To get it google how to get it (I cant post link as I don't have enough posts to have privileges). If you can't on the English, make a new account on the chinese emui page and use google translate in chrome to navigate. (if the padlock button doesnt give you a form to fill out, clear your cache and cookies or open in incognito mode)
Once you have the code, find the "SRK Tool Huawei Bootloader/ROOT/Recovery/Backup/Utility" thread on XDA and download the latest stable build, should be around 700mb. Also in the thread, the guy posted a video on how to do it.
Step 1: Unlock bootloader
Step 2: install TWRP Recovery
Step 3: Root
These 3 steps are in the video.
Once you successfully rooted, open the tool again and in the Utilities menu (7) there is an option to flash OEMInfo. Select that and choose the OEM info you want. I needed C432. It will use the superuser app to flash it, reboot and you should be on it.
If you are asking how to use DC-Phoenix, again they have both written as well as a video with instructions on how to do it. You don't need an unlocked bootloader as it will use an exploit to circumvent it. Do Method 1, if it doesn't work, do Method 2.
Good luck mate
I got into this mess in the first place by flashing the B361 and my camera and keyboard didnt work after upgrading it. But now that i know how to fix it, I might give it a shot. Is there a thread with features and testing of the Nougat emui 5 for P9? I saw a lot of threads of people rolling back due to battery issues and other stuff. Don't want to update if its not the best.
Click to expand...
Click to collapse
Thanks a lot for help, my phone is alive again, i use DC Phoenix to resurrect, and SRK for the update
i have problem to
..
---------- Post added at 12:33 PM ---------- Previous post was at 12:27 PM ----------
please i try to install twrp but not work
---------- Post added at 12:38 PM ---------- Previous post was at 12:33 PM ----------
mjcaballero said:
Thanks a lot for help, my phone is alive again, i use DC Phoenix to resurrect, and SRK for the update
Click to expand...
Click to collapse
what you chose i dont know i buy buy the DC PH..
HOW
---------- Post added at 02:38 PM ---------- Previous post was at 02:33 PM ----------
mjcaballero said:
Thanks a lot for help, my phone is alive again, i use DC Phoenix to resurrect, and SRK for the update
Click to expand...
Click to collapse
PLEASE
---------- Post added at 02:40 PM ---------- Previous post was at 02:38 PM ----------
i install tswp last but not work
---------- Post added at 02:44 PM ---------- Previous post was at 02:40 PM ----------
ppppplease
---------- Post added at 02:45 PM ---------- Previous post was at 02:44 PM ----------
oooooooo
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?
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