This morning, I saw a notification appear on my phone showing that the Feb-21 security patch is ready to be installed. The size is 41+MB. The description looks nothing unusual as this phone has been getting only security patches for quite some time. However, once it attempt to restart it went dead. I tried numerous times to power up the phone (pressing the power button) but it's not responding. Nothing happen. Does it mean my phone is bricked by the security patch update?
chiwawa10 said:
This morning, I saw a notification appear on my phone showing that the Feb-21 security patch is ready to be installed. The size is 41+MB. The description looks nothing unusual as this phone has been getting only security patches for quite some time. However, once it attempt to restart it went dead. I tried numerous times to power up the phone (pressing the power button) but it's not responding. Nothing happen. Does it mean my phone is bricked by the security patch update?
Click to expand...
Click to collapse
Can you access recovery mode?
chiwawa10 said:
Does it mean my phone is bricked by the security patch update?
Click to expand...
Click to collapse
First of all:
1. Did you had your bootloader unlocked ?
2. Were you rooted when taking the OTA update ?
Your description doesn't quite match the result.
A differential update (like security updates) shouldn't brick the bootloader and from your description the bootloader doesn't (well) load itself.
Worst case with a diff. update is that the bootloader will give you an error message and won't load the OS but the fact that you have a black screen indicates that the bootloader itself isn't able to operate.
I would try two things:
a) Try to access Recovery Mode : Vol Up + Power + Cable connected
b) Try to access Download Mode : Vol Down + Power + Cable connected
Those two will dictate which actions you can take moving forward based on which modes you can still access.
Also:
Does the phone indicate charging when you connect the USB cable ?
Does your PC detect it (shows up in Device Manager) when connected ?
if a) and b) fails but the PC still detects the phone you might be able to reflash using Qualcomm Flash Image Tool (QFLI), I'm pretty sure there was an Oreo firmware in QFIL format available somewhere on the web.
Edit: QFIL, NB0, recovery MR packages firmware available in this thread [OTA] [Fastboot] [QFIL] Nokia 7 Plus OTA and Fastboot Collection
Thanks for the reply. Finally I managed to boot the phone up by pressing volume up + power button. However, it does not boot into recovery mode. Instead it boots up in normal mode. Since then I did not try reboot or power down my phone. Glad that it's not bricked. And no, I do not have the bootloader unlocked. Though I'm tempted to do so if the updates stop coming. At least I can still breath some life into the phone by installing other flavor of android. Still clinging on to hope that HMD will allow us to officially unlock bootloader. Otherwise, this will be my last Nokia phone from HMD.
chiwawa10 said:
Thanks for the reply. Finally I managed to boot the phone up by pressing volume up + power button. However, it does not boot into recovery mode. Instead it boots up in normal mode. Since then I did not try reboot or power down my phone. Glad that it's not bricked. And no, I do not have the bootloader unlocked. Though I'm tempted to do so if the updates stop coming. At least I can still breath some life into the phone by installing other flavor of android. Still clinging on to hope that HMD will allow us to officially unlock bootloader. Otherwise, this will be my last Nokia phone from HMD.
Click to expand...
Click to collapse
This will be my last one too if nokia won't support the unlock
chiwawa10 said:
This morning, I saw a notification appear on my phone showing that the Feb-21 security patch is ready to be installed. The size is 41+MB. The description looks nothing unusual as this phone has been getting only security patches for quite some time. However, once it attempt to restart it went dead. I tried numerous times to power up the phone (pressing the power button) but it's not responding. Nothing happen. Does it mean my phone is bricked by the security patch update?
Click to expand...
Click to collapse
My phone got bricked after a regular update.no bl unlock or something else weird. I really won't forgive nokia for that.
Related
Hello everyone, I saw a few posts on this forum about other bricked phones, but my case is different (if its not then please link me the thread, Thanks).
Story: Today I decided that my unrooted phone wasn't enough for me, so I said: "Why not root?" . I have to add that I owned a LG Magna 3G before this Huawei P8 LIte 2017 and oh boi was the rooting procedure WAY HARDER(the huawei procedure)... I did well with my LG, but not so well with my Huawei. To be honest I was almost done but because I couldnt boot into TWRP, I decided to follow a guide I cant find cause I followed so many that my History is a mess (if anyone requests I will do some digging though). The guy suggested to someone that couldnt boot into TWRP (like me) that he should falsh TWRP>relock his OEM>Shutdown>Press a combination to go into recovery mode>???>Profit. I did just that but my device is now a 180 Euro brick.
Probelm: My device bootloops. Every time I shut it down (hold power key for 10sec), it reboots and gets stuck on the famous "Your device has been locked and can't be trusted. To learn more, BLAH BLAH BLAH. Your device is booting now...
I tried several key combinations, but whatever I do, when I hold my power key for 10sec, The huawei logo pops up for a second or two and then I get stuck on this screen again...
Sadly, I seem to have no connection between my PC and my device (adb can't find any connected device).
I also want to add that, after I was promted to relock my OEM, I removed the USB cable whoopsie.
What Im looking for:
A way to regain contact between my PC (adb) and my phone
A way to shutdown my device for now (and not forever... just for the night)
Someone to tell me that he had the same issue and took the following steps (Need clear answers and steps)
Anything else whatsoever
I don't think it's necessary to provide the files I used, since the reason my device is like this is because of my own stupidity:silly:
Thank you for your time.
You have to hold Power and Volume Up button pressed to boot into erecovery, not only power, check it.
grgzz said:
You have to hold Power and Volume Up button pressed to boot into erecovery, not only power, check it.
Click to expand...
Click to collapse
Sorry for replying after 2 hours, I didn't get a notification.
I tried:
1. Holding the buttons until I see the "your device is booting..." message
2.Holding the buttons until it vibrates
3.Holding the buttons until I see the Huawei logo
Thanks for your time anyway
You press Volume Up + Power simultaneously, when you see the Huawei logo you release Power and hold Volume Up only until it boots to erecovery.
grgzz said:
You press Volume Up + Power simultaneously, when you see the Huawei logo you release Power and hold Volume Up only until it boots to erecovery.
Click to expand...
Click to collapse
Tried this several times, no result.
Is there a more drastic solution to my stubborn phone?
Aneom7331 said:
Tried this several times, no result.
Is there a more drastic solution to my stubborn phone?
Click to expand...
Click to collapse
The most drastic solution is the DC Phoenix software, not for free, if i am right they ask 15€ for 72 hours.
Not going to bother with this one tho... if I am very desperate, I might try to "borrow" it, but Im gonna seek other solutions until then.
Thanks for your time
On the "your device has been unlocked" hold the Volume up button until you boot to eRecovery. From there connect to wifi and restore stock rom. Afaik, erecovery should boot on bootlooped device. Give it a try
If this doesnt work, plug in to pc, and hold volume up + power, on huawei logo leave power button and hold volume up until you get to erecovery
aciupapa said:
On the "your device has been unlocked" hold the Volume up button until you boot to eRecovery. From there connect to wifi and restore stock rom. Afaik, erecovery should boot on bootlooped device. Give it a try
If this doesnt work, plug in to pc, and hold volume up + power, on huawei logo leave power button and hold volume up until you get to erecovery
Click to expand...
Click to collapse
Hello, thanks for replying
My device is now good, only gapps are missing but I don't care too much. Here is what happened:
So, I left my phone unplugged from any power source during the night (meanwhile the screen couldn't turn off), although I swear I did this 20 times already, when I booted my device after I came back from my University, my phone booted into eRecovery... I downloaded the latest package and it seems to work just fine now, the only problem is that the gapps need to be flased via TWRP (that I don't think I have anymore, how ironic).
Thanks to all of you who cared about giving me a solution :victory: Have a fantastic day
If you want to have a complete working system, i suggest you to try to update using erecovery again. It should download full firmware with gapps etc
Aneom7331 said:
Hello, thanks for replying
My device is now good, only gapps are missing but I don't care too much. Here is what happened:
So, I left my phone unplugged from any power source during the night (meanwhile the screen couldn't turn off), although I swear I did this 20 times already, when I booted my device after I came back from my University, my phone booted into eRecovery... I downloaded the latest package and it seems to work just fine now, the only problem is that the gapps need to be flased via TWRP (that I don't think I have anymore, how ironic).
Thanks to all of you who cared about giving me a solution :victory: Have a fantastic day
Click to expand...
Click to collapse
aciupapa said:
If you want to have a complete working system, i suggest you to try to update using erecovery again. It should download full firmware with gapps etc
Click to expand...
Click to collapse
Well, that was what we told you to do at first time. Erecovery can bring it back to life easily. Now as you have already been told erecovery flashes the complete firmware, including gapps.
You can also try to update it through the settings menu, in the system update settings you press the three dots menu on the upper right corner and select download latest complete package.
grgzz said:
Well, that was what we told you to do at first time. Erecovery can bring it back to life easily. Now as you have already been told erecovery flashes the complete firmware, including gapps.
You can also try to update it through the settings menu, in the system update settings you press the three dots menu on the upper right corner and select download latest complete package.
Click to expand...
Click to collapse
I know you told me first but, the difference was that, my phone had to ran out of battery to do this. In the end of my last reply I said thanks to all of you who cared, including you, you cared the most actualy
Aneom7331 said:
I know you told me first but, the difference was that, my phone had to ran out of battery to do this. In the end of my last reply I said thanks to all of you who cared, including you, you cared the most actualy
Click to expand...
Click to collapse
Well, at least it works now.
Hi Everyone! Well, today is my time to ask for some help! :fingers-crossed:
I got my hands on a great looking Huawei P20 PRO, unfortunately the Phone is locked FRP... But as i had searched around, there was a method to bypass that by a simple bug they had on the "TALKBACK", like one week ago people was doing that bypass successfully , but this phone has a newer version of talk back, 7.1.x.x...
On the videos people have the previous 6.1.x.x version... That means i don't have the same "help" option as they have.
-After that i tried to get the phone into Fastboot mode, but i can't get the phone on that mode, i press volume down and hold for a while with the device turned off, then i plug the usb, and it just starts charging...
-I press Both vol up and vol down buttons with power at same time, it goes to a screen "EMUI" that says "SOFTWARE INSTALL FAILED! GET HELP FROM xxxx.EMUI COM/BLABLABLA) and says "Reboot system now"...i then press reboot now, and i does a regular reboot and starts up to select language etc, all good... BUT FRP locked...
- Then last night i tried to press VOLUME UP then plug the USB and it got into Erecovery mode, that gave me the option to download the latest version, wipe the current one, shutdown, or reboot... well i had nothing to lose and i did the first to download the latest version, after a 4gb download and install the phone is on the same situation, same version, same everything....
Makes me wonder if someone already done bad attempts before me.
Is there anyway to get the phone on Flashboot? Or bypass the FRP ?
Same
I have exactly the same
Any help????
Thebuckers1986 said:
I have exactly the same
Any help????
Click to expand...
Click to collapse
have you tried the wifi update? it didnt work with me... search for "Upgrade to Android Pie through eRecovery and the Wifi - Firmware Finder PC"
I just updated to January 2019 update, everything was fine until i pressed 'Restart now' after it finished updating. Now it froze at Androidone screen. I hold the power button, it vibrates and looks like it's starting up but instead it freezes again at Androidone screen. If I unplug my phone it seemingly shuts down after a while, but again if I try anything it's the same thing again and I remain stuck at the Androidone screen. Please help. Thanks, Vladan
Same issue. After the update..phone boots up to Androidone logo and shuts down. If the I press the power button, it vibrates and comes up to Androidone logo and screen goes blank again
I have same problem. for me it because I forgot to remove Magisk before update. I fix by flash December Rom and then update January pacth.
UnlimitedBB said:
Same issue. After the update..phone boots up to Androidone logo and shuts down. If the I press the power button, it vibrates and comes up to Androidone logo and screen goes blank again
Click to expand...
Click to collapse
So what to do??
vladankrle said:
So what to do??
Click to expand...
Click to collapse
I have no idea. I didn't try any methods until now.
vladankrle said:
I just updated to January 2019 update, everything was fine until i pressed 'Restart now' after it finished updating. Now it froze at Androidone screen. I hold the power button, it vibrates and looks like it's starting up but instead it freezes again at Androidone screen. If I unplug my phone it seemingly shuts down after a while, but again if I try anything it's the same thing again and I remain stuck at the Androidone screen. Please help. Thanks, Vladan
Click to expand...
Click to collapse
I have the same issue. I am able to use fastboot commands from my computer, but cannot (or do not know how to) sideload update .tgz file I downloaded from en.miui.com.
Also, I am unable to use adb commands and boot into recovery.
same issue with two mi a2. stuck on bootloader after update.
I can press and hold vol- + power to boot into fast boot.
Then press and hold vol+ + power to get it to boot back to the old partition for normal use.
There might be another update later on which would probably fix the issue?
I tried to update again and now I get the same issue ouch...
Mine went well but I did something wrong in Magisk and it stop booting.
In fastboot mode I've changed it from A to B and it loaded PIE with january update. So, try to change from A to B ou B to A and see if that fixes the problem.
Tried to boot this morning but no luck.
However... The phone came back to live this evening but God knows how.
Mmm... What is going on
Confirmed, unfortunately
Dammit, you guys!.. UNFORTUNATELY, this is confirmed!!
Brand new Mi A2 (Global Version), from the shop today and went through System updates - through, to Google January 2019 Security Update and the device will not boot; same problem as with everybody else here. Argh.
EDIT:
ken218 said:
However... The phone came back to live this evening but God knows how.
Click to expand...
Click to collapse
Yup, had just managed to start it: system was up. Went for a Factory Reset and now I'm back in the loop. Stuck again, just upon rebooting. This is going the be a serious issue.
Try to start it with holding both volume buttons down and power - then release after logo and, also -perhaps- volume down.
Click to expand...
Click to collapse
^^ At least, that's what I think I'd done, heh. Sorry, not 100% sure, all happened in -serious- panic! xF
EDIT: Ah, well, thank God (LOL). It looks like there isn't anything wrong with Google's "Security patch level: January 5, 2019" (Android 9)!
However, because this happened through normal operation - it seems that a LOT of people *are* going to have this problem...
How many know that you should Factory (Data) Reset after a (regular, OTA) update; and how many will be able to boot their device, out of the loop. Geez!
P.S. Btw., you owe me *beers! ;$
EDIT: Zomg., this thread is a duplicate, already @
Code:
https://forum.xda-developers.com/mi-a2/help/bootloop-recent-android-ota-update-t3892559
Had the same problem here with April's update - hanging on logo screen constantly. Issue resolved when I connected phone to pc. Then it entered into factory reboot mode and finally booted correctly.
ol3w said:
Had the same problem here with April's update - hanging on logo screen constantly. Issue resolved when I connected phone to pc. Then it entered into factory reboot mode and finally booted correctly.
Click to expand...
Click to collapse
You only connected it to the pc? @ol3w
ol3w said:
Had the same problem here with April's update - hanging on logo screen constantly. Issue resolved when I connected phone to pc. Then it entered into factory reboot mode and finally booted correctly.
Click to expand...
Click to collapse
Thanks! This worked for me!
ol3w said:
Had the same problem here with April's update - hanging on logo screen constantly. Issue resolved when I connected phone to pc. Then it entered into factory reboot mode and finally booted correctly.
Click to expand...
Click to collapse
I had similar issue with April 2019 update. But mine was switching off few seconds after the Android One logo screen. The phone can boot into fastboot mode though.
But instead of connecting to the PC like ol3w, I had mine connected to a charger to add some juice to the battery, thinking I will have to flash the firmware again. Few minutes later, I was promptted with a "The phone failed to boot previously, do you want to "Retry"/"Shutdown"" screen. (note: I can't really remember if the second option was "Shutdown" or something else). I selected "Retry" thinking it will fail again. But then, couple of minutes later, the phone booted correctly.
Xiaomi's security patch is getting quite... unreliable recently. Wondering if I should abandon ship when pixel 3a is out (if it doesnt cost premium money)
Same problem with boot after update 2019
Failed to boot
I had the same problem. My problem was solved by using USB cable. I connected USB cable to the PC and mobile and I pushed Power. Mobile booted correctly and I work from this time. Try it, I wish you good luck.
T
Hoping someone can offer some advice.
So a few days ago my Nokia 8 stopped saving pictures (it was doing this regularly after I flashed the latest (5150) build).
I rebooted the phone only it froze on the Nokia boot logo.
It wouldn't do a forced reboot via the power button, I had to just let the power drain completely to get it to do anything.
I am trying to now flash the latest qlz but I cant get the device in to Download Mode in order to flash.
If I connect it to power (plug or usb) and it gets enough power to turn on then this is what I get:
1. Power and vol+ button held down - boots to Nokia logo, freezes
2. Power and vol- button held down - stays on bootloader unlocked warning screen
3. No buttons held down - stays on bootloader unlocked warning screen
Can anyone advise?
Its almost as if my bootloader is corrupt.
If I try option (1) I do see the device listed via
Code:
adb devices
but its shown as
Code:
NBXXXXXXX unauthorized
and since I have no filesystem access to the device I cant push the key to authorise it.
Any advice humbly appreciated as I really need access to my phone now.
Thanks
Dan
dt_matthews said:
Hoping someone can offer some advice.
So a few days ago my Nokia 8 stopped saving pictures (it was doing this regularly after I flashed the latest (5150) build).
I rebooted the phone only it froze on the Nokia boot logo.
It wouldn't do a forced reboot via the power button, I had to just let the power drain completely to get it to do anything.
I am trying to now flash the latest qlz but I cant get the device in to Download Mode in order to flash.
If I connect it to power (plug or usb) and it gets enough power to turn on then this is what I get:
1. Power and vol+ button held down - boots to Nokia logo, freezes
2. Power and vol- button held down - stays on bootloader unlocked warning screen
3. No buttons held down - stays on bootloader unlocked warning screen
Can anyone advise?
Its almost as if my bootloader is corrupt.
If I try option (1) I do see the device listed via
Code:
adb devices
but its shown as
Code:
NBXXXXXXX unauthorized
and since I have no filesystem access to the device I cant push the key to authorise it.
Any advice humbly appreciated as I really need access to my phone now.
Thanks
Dan
Click to expand...
Click to collapse
The fastest way to fix it is taking to a care centre near you. or any Nokia certified store to reflash it for you. if it's out of warranty they will probably charge you ~$20
Hello,
I was on CrDoid 7.2. (Android 11) It was working normally.
I rebooted to recovery (TWRP 3.5), and flashed CrDroid 6.2 (Android 10).
And it bricked severely the phone. At startup, i get a message
"REV CHECK FAIL, DEVICE:9, BINARY:8 (DTB)"
I really think the situation is hopeless :
- impossible to reach download mode
- impossible reach recovery mode
- BixBy + Volume down + Power + plugging the cable doesn't work
- if the telephone stays plugged, i get a boot-loop (before the message "your bootloader is unlocked, please press power button to continue")
Any help is welcome but i really think i lost my phone. Quite painful. I'm not so rich.
I think the device tree of the ROM i flashed is mistaken.
I played i lost.
Jean
jean_michmich said:
Hello,
I was on CrDoid 7.2. (Android 11) It was working normally.
I rebooted to recovery (TWRP 3.5), and flashed CrDroid 6.2 (Android 10).
And it bricked severely the phone. At startup, i get a message
"REV CHECK FAIL, DEVICE:9, BINARY:8 (DTB)"
I really think the situation is hopeless :
- impossible to reach download mode
- impossible reach recovery mode
- BixBy + Volume down + Power + plugging the cable doesn't work
- if the telephone stays plugged, i get a boot-loop (before the message "your bootloader is unlocked, please press power button to continue")
Any help is welcome but i really think i lost my phone. Quite painful. I'm not so rich.
I think the device tree of the ROM i flashed is mistaken.
I played i lost.
Jean
Click to expand...
Click to collapse
Try the FRP Hijacker Tool. It has also happened to me that nothing worked anymore. The cell phone does not appear in the list, but still worked with the SC-01C and SoftBrick Fixer.
This also happened to me before, and I also couldn't get back to TWRP.
The error "REV CHECK FAIL, DEVICE:9, BINARY:8 (DTB)" means that the version of your device is at 9 and the binary you flashed is at 8. You can't simply downgrade Android versions on Samsung devices.
Are you sure you can't enter download mode? The key combination to enter download mode isn't what you said (" BixBy + Volume down + Power + plugging the cable doesn't work "). Try PLUGGING YOUR PHONE IN YOUR PC + VOLUME DOWN + BIXBY.
If you can access download mode, let me know so I can help you get your device unbricked.
Hello,
My mistake is that I downgraded from 11 to 10. You are probably right.
I think (but i'm not sure) that during downgrading, the sboot.bin is not anymore matching with the Device Tree and it generates a crash during flashing.
@WSC Productions : Huge thanks for the advice about the combo buttons.
@bininga59 : I'll give a try to your solution with the software FRP Hijacker Tool. But the phone is restarting itslef every 5 seconds..I wonder how a connection can be established.
Tonight will be a long night again
jean_michmich said:
Hello,
My mistake is that I downgraded from 11 to 10. You are probably right.
I think (but i'm not sure) that during downgrading, the sboot.bin is not anymore matching with the Device Tree and it generates a crash during flashing.
@WSC Productions : Huge thanks for the advice about the combo buttons.
@bininga59 : I'll give a try to your solution with the software FRP Hijacker Tool. But the phone is restarting itslef every 5 seconds..I wonder how a connection can be established.
Tonight will be a long night again
Click to expand...
Click to collapse
You can definitely go back from A11 to A10. It's the same bootloader (9). If it keeps restarting, then you should get into download mode too. Emergency off and then immediately quieter + Bixby immediately push the USB plug in.
jean_michmich said:
Hello,
My mistake is that I downgraded from 11 to 10. You are probably right.
I think (but i'm not sure) that during downgrading, the sboot.bin is not anymore matching with the Device Tree and it generates a crash during flashing.
@WSC Productions : Huge thanks for the advice about the combo buttons.
@bininga59 : I'll give a try to your solution with the software FRP Hijacker Tool. But the phone is restarting itslef every 5 seconds..I wonder how a connection can be established.
Tonight will be a long night again
Click to expand...
Click to collapse
No problemo. Try @bininga59 's advice, it'll probably work - he probably knows more than I do about Samsung ROMs tbh. If it doesn't though, let me know.
What i didn't know :
Doing Volume down + BixBy Button + plugging cable for simple electric supply
Is not the same as
Doing Volume down + BixBy Button + plugging cable linked to a computer
The cable you plug to the telephone while you are pressing volume down + BixBy must be linked to a computer.
I finally reached the Download Mode
Many thanks again