I waited to write here, if the March 2020 patches solved the problem, but unfortunately it is not...
several nokia comunity users have the same problem and nokia is not responding about It.
having Nokia 8.1, I gave Nokia 7.1 to my girlfriend last year ... great smartphone, the Android 10 update work very well, but the February 2020 patch was a disaster!
Probably it didn't install well, and then the phone asked for a factory restart.
the problem is that the Factory reset did not come back to a pre-February patch state, but always brings it to the point of "restarting the phone to finish installing the February patch".
and immediately the restart is requested, which can be postponed, but not indefinitely, so after fifteen days the smartphone restarts by itself, and freezes again asking for a factory reset!
in an endless loop!
I think I have to do a system flash to bring the phone back to a previous stable state, right?
Can you help me on the procedure to follow?
I have never unlocked the bootloader and all the rest
thank you guys
My friend has the same issue.
well you have two solutions here
1) Pause your updates so your phone never installs them
2)Get your phone flashed with the stock firmware , and if you want get it unlocked.
I have spent about 2 months trying to fix the issue but in the end I got the phone flashed which fixed the problem.
The issue comes due to your phone not being able to verify the selected partitions for boot which is why it asks you to reset.
thanks for the answer!
the guarantee is still active,
I think I will send it to nokia assistance, as soon as next week I will be able to see my girlfriend (for the emergency covid19 I haven't seen her for 60 days, but next week there is the unlock down).
meanwhile I took for her a Nokia 4.2 to be used as a replacement.
I hope Nokia's lab assistance will flash the system quickly and better than what I could do
PCIHD said:
well you have two solutions here
1) Pause your updates so your phone never installs them
2)Get your phone flashed with the stock firmware , and if you want get it unlocked.
I have spent about 2 months trying to fix the issue but in the end I got the phone flashed which fixed the problem.
The issue comes due to your phone not being able to verify the selected partitions for boot which is why it asks you to reset.
Click to expand...
Click to collapse
Can you show me to a thread or video for option 2)?
Related
Hi,
I've got Nexus 9 Stock, unrooted and bootloader locked, I got an OTA update, downloaded and installed it, when it rebooted the boot animation repeated endlessly.
It doesn't do part 2 of the boot animation it just repeats part 1, the four colored dots dancing around in circles..(is this a bootloop?)
I tried booting into safe mode without any success.
I tried wiping the cache partition but it didn't seem to do anything, it just stayed on 'formatting cache' for ages..
I rebooted, still endless boot animation. I rebooted back into fastboot and then recovery, when recovery loaded it had an error message 'cant mount cache partition'..
I tried wiping the cache partition again but got the same result, it stayed on 'formatting cache' for ages..
I rebooted back into recovery mode and tried 'formatting data/factory reset' and again it didn't seem to do anything, it just stayed on 'formatting data' for ages..
When I rebooted back into recovery it went straight back to where it left off: 'formatting data' without displaying the menu, and it stayed there for ages..
I figured, at the very least, recovery is buggered. So I tried flashing twrp via fastboot but I soon learned I can't do that while the bootloader is locked and I can't unlock the bootloader without enabling it in developer options which i can't get to because of the endless boot animation.
Help please, what should I do?
Wiping cache takes much longer on the N9 than any other device I've owned. Seriously, give it 30 minutes to one hour to complete wiping cache; don't power it off while it's doing that.
Once you're done wiping cache and rebooting you'll probably still be on 5.0.1. Your options are to wait for Google to release a new OTA, call HTC for an RMA, or flash the factory image (it can be done without overwriting user data).
I'm having the same problem. Actually, a bunch of us on the Nexus 9 product forums are having the problem too.
https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!categories/nexus/nexus-9
Google seems to replacing some and referring other people to HTC. I spoke with HTC this morning and they're having me send it to them for repair.
It's probably a nand problem!!
I hope this isn't the beginning of a #nexus9bricked
Nexus 7 tabs have been having hand failures for months now. Just search twitter for #nexus7bricked
+1 to the update bricking their Nexus 9
Yep mine got bricked when I installed the OTA update on a stock locked Nexus 9 this evening. Factory reset didn't fix the issue and I can't flash 5.0.1 because of Google's asinine developer options in Lollipop.
You can't flash even a signed factory image without selecting a Developer Option allowing for ADB to unlock the boot loader. So if you can't boot into the OS, you can't use Recovery to flash an image. Every Android device I've ever owned has been near indestructible because you could always refresh from recovery. Not so in Lollipop anymore, even with a stock device, unless you have the foresight to preemptively select the Developer Option allowing the boot loader to be unlocked.
I called HTC and they knew my problem almost before I got on the call given the call volume they're getting. They said I had two options: wait for an impending Google update fixing the issue coming sometime this weekend/early next week or RMA it to the repair center. They expect the update this weekend, and if I RMA it, that will take 7-10 business days and the repair center will simply be waiting for this imminent update fix from Google.
The rep could not explain to me how Google is going to issue an update to fix a boot loop on a device that can't be flashed, so I'll believe it when I see it. Part of me thinks they've been totally sandbagged with calls on this tonight and know they can't possibly repair/replace this many devices in a timely manner.
ksutherland91 said:
Yep mine got bricked when I installed the OTA update on a stock locked Nexus 9 this evening. Factory reset didn't fix the issue and I can't flash 5.0.1 because of Google's asinine developer options in Lollipop.
You can't flash even a signed factory image without selecting a Developer Option allowing for ADB to unlock the boot loader. So if you can't boot into the OS, you can't use Recovery to flash an image. Every Android device I've ever owned has been near indestructible because you could always refresh from recovery. Not so in Lollipop anymore, even with a stock device, unless you have the foresight to preemptively select the Developer Option allowing the boot loader to be unlocked.
I called HTC and they knew my problem almost before I got on the call given the call volume they're getting. They said I had two options: wait for an impending Google update fixing the issue coming sometime this weekend/early next week or RMA it to the repair center. They expect the update this weekend, and if I RMA it, that will take 7-10 business days and the repair center will simply be waiting for this imminent update fix from Google.
The rep could not explain to me how Google is going to issue an update to fix a boot loop on a device that can't be flashed, so I'll believe it when I see it. Part of me thinks they've been totally sandbagged with calls on this tonight and know they can't possibly repair/replace this many devices in a timely manner.
Click to expand...
Click to collapse
I also believe they are pretty busy with this issue. After 4 calls over 12 hours, I finally have an RMA and have the privilege of sending them my device to get repaired. Now, I have to wait 2 days for them to send me the shipping labels (they are covering shipping) and then 7-10 days for the repair.
What a PITA for a "premium" device.
Yeah they suggested I call back tomorrow or Saturday for updates on when this Google fix is coming about. The Nexus support agent I chatted with at Google says he's unaware of any impending update to fix this issue.
Right now I'm afraid I'm going to call HTC in a day or two and find out I have to send it in, and then I'll start the whole process 2 days later than I could have.
HTC live chat: guy said, that they repair using fastboot only. Imho, service command for flash on locked bootloader is present and hidden under OEM section.
Phone shop couldn't reinstall firmware. I'll sent it back to HTC to fix.
Meanwhile, I solved my problems by buying a new tablet - Galaxy Tab S 10.5 !
Thanks for all the replies, best of luck to everyone else
Now I can get back to wasting time and energy playing clash of clans hehe.
Hey!
So I have been using an android phone from 3 years now and I have been stuck in an huge problem! And I need your help in order to solve this problem. Here is the problem so basically I have a Freetel nico (Japanese brand) which is about 3 to 4 years now running on top of stock kitkat rom or in other words the same rom when I unboxed it. After few months my screen cracked on the bottom near the capacitive touch keys. After the crack the home buttom stopped working! I was all okay with that and the next day my notification panel started glitching and stopped showing any notifications which was really annoying. Now I knew that there some serious problem, so I taught of resetting the phone so I went in the setting and tried factory reset. After few minutes it didn't go to system recovery but the phone just restarted itself. I tried it once again and got the same problem, next step I had was to hard reset it by going into the recovery. When I hold the button and let go it didn't take me to the recovery this time also. So in conclusion I came to know that there was no recovery inside the phone (I did erase the phone through recover about 2 times before this incident everything went well during that time). Moving on I rooted the phone and installed SuperSU and other softwares that could install recovery mode to the phone. I got the same result this time also, I also tried installing a different rom through the stock system update app same result.... After a year of all this work I taught it would be best just giving it to the company service center but I came to know that the company had no longer selling this device and there is no service available .
After all of that tries above I still continued to solve this problem I tried ADB resetting it through pc no luck here also! So if you guys could recommend me some apps or softwares I could try in order to reset my phone please do let me know in the comments. Or you could also ask any scripts that you want to know from the phone which could solve the problem I can do that also!
Thank you
Darshan
I have an LG G pad x 8.0 TMO V521 build number NRD90U updated to Nougat fully updated as of jan 1st 2018 with no modification, no root, no open bootloader basically got it from store kept up to date via lg bridge.
The problem in a failed attempt to downgrade I believe I flashed my recovery with it having some password I didn't realize was there it made it to 10% has password error and stops most of my recovery images are not recognized when looking for them from recover device menu the 1 that is wont go past 10% device only reads at 1%. After realizing it was at a point I could not do anything from I disconnected the battery to preserve what battery i had left hoping I didn't totally mess everything up. Hard reset sends to update screen and boot sends to upgrade screen but device wont accept any update That I've tried.I have searched what to me seems like all the current threads with no luck finding what I thought was useful info since most refer to devices with open boot loaders or twrp or other things installed on the device that I don't have. Willing to except that I may have missed the thread I actually needed though by it being for similar process that sounded wrong so if I did even a push in the right direction would be a world of help.
My question is can this be recovered and how or am I SOL and should just go smash it with a big hammer for the frustration its been.
This problem fixed itself the next time I attempted to fix it with lg bridge and the update recovery kept saying i wasnt connected to iternetand making me click retry every 2 percent for about 45 minutes but i eventually got there and it wouldnt even do that last time so yay thanks all who may have attemped to understand my problem even if you never got to a solution for me if any admin wish to delete this thread your welcome to or if anyone knows a better solution for future occurences still not a fan of the method I had work.
I've already waited for 7 days (168 hours). I didn't reboot the device while waiting for the 7 days. I'm using SM-G965F/DS version, which is Samsung Exynos and not Samsung Snapdragon.
But I was wondering when I've first received my device I did a software update and my security patch level become 1 March 2018. Do you think the newer update causes me to be unable to get OEM Unlock? I really have no idea what went wrong.
Pls help, Thank you!
been having the same trouble after rom update. i had left my phone on for almost 9 days straight and no luck. any one yet have a solution?
I would like to help you about this if u still having this problem
instrumentaly said:
I would like to help you about this if u still having this problem
Click to expand...
Click to collapse
I need help. I am on A8+ and didn't get OEM UNLOCK option after keeping my phone up for 170 hrs. Now I have flashed the HONG KONG ROM with AP BL CP CSC and what do you think? Will it show OEM UNLOCK after 7 days ? I have KSA Model Phone.
craidyn.rahman1 said:
been having the same trouble after rom update. i had left my phone on for almost 9 days straight and no luck. any one yet have a solution?
Click to expand...
Click to collapse
Same here. I have tried multiple ROMS, though I have only once completed waiting 7 days or 168 hrs non stop without rebooting, but OEM UNLOCK never appeared. Now I have flashed HONG KONG ROM and waiting for 7 days to complete.
But this time I have enable Nougat Easter Egg game which is CAT-SNACK game. I saw on multiple forums by multiple guys that they got OEM UNLOCKED by getting EASTER EGG Game enabled. So I am waiting for this trick as well. You try enabling Easter Egg game by tapping on Android 7.1.1 from SOFTWARE INFO TAB and then LONG PRESS and you will see a CAT icon in the bottom. This means you got Easter Egg game enabled. Check youtube for more info.
After first unlock, it may disappear even after 7 days. The important thing after 7 days is prenormal - you want it to be gone. Go into download and see if the locks are off before doing anything else. If so, focus on prenormal.
Same phone as OP, same problem. It's been 13 freaking days since I did the reset. Where the f*ck is OEM unlock??
kydar said:
Same phone as OP, same problem. It's been 13 freaking days since I did the reset. Where the f*ck is OEM unlock??
Click to expand...
Click to collapse
Go to recovery mode and see if locks are off. If so, and prenormal is gone, just flash TWRP and DON'T touch OEM anymore.
Sent from my [device_name] using XDA-Developers Legacy app
@gaww Locks are off but still prenormal. It's been 2 weeks today. I don't understand. I'm ready to throw this f-in phone against the wall.
kydar said:
@gaww Locks are off but still prenormal. It's been 2 weeks today. I don't understand. I'm ready to throw this f-in phone against the wall.
Click to expand...
Click to collapse
There have been a few times that has happened. Make sure you haven't done something like trying the date changing fix or reset it during that time.
You may have to factory reset it to clear it out, and of course that will start the 7 day clock again. You can start using it in stock mode - but do nothing that affects the date.
After 7 days again (sorry), start going into recovery mode ONLY to see if prenormal is gone. If not, only reboot. Keep checking - hopefully it will show up just after 7 more days.
Sent from my [device_name] using XDA-Developers Legacy app
There have been a few times that has happened. Make sure you haven't done something like trying the date changing fix or reset it during that time.
Click to expand...
Click to collapse
@gaww I may have tried the date/time hack after the first reset, I am not 100% sure. But I have another idea; tell me if this sounds like it's worth a try. I downloaded the original ROM version from sammobile, G965FXXU1ARC5. This is the version that was on the phone when I got it. The build date is 22 Mar 2018 and the Security Patch Level is 01 Mar 2018. This was (I believe) before Sammy fixed the date/time hack. So I was thinking I'd Odin that ROM back onto the phone, do the date/time hack to get OEM unlock immediately, then flash TWRP and go from there.
If for whatever reason the date/time hack doesn't work, I'll factory reset it again (since mucking with the date/time seems to mess up the 168 hour timer) and wait a week. Either way, I'm no worse off than I am now.
I will of course update this thread to let everyone know if it works or not. Wish me luck!
kydar said:
@gaww I may have tried the date/time hack after the first reset, I am not 100% sure. But I have another idea; tell me if this sounds like it's worth a try. I downloaded the original ROM version from sammobile, G965FXXU1ARC5. This is the version that was on the phone when I got it. The build date is 22 Mar 2018 and the Security Patch Level is 01 Mar 2018. This was (I believe) before Sammy fixed the date/time hack. So I was thinking I'd Odin that ROM back onto the phone, do the date/time hack to get OEM unlock immediately, then flash TWRP and go from there.
If for whatever reason the date/time hack doesn't work, I'll factory reset it again (since mucking with the date/time seems to mess up the 168 hour timer) and wait a week. Either way, I'm no worse off than I am now.
I will of course update this thread to let everyone know if it works or not. Wish me luck!
Click to expand...
Click to collapse
Good luck?
Sent from my [device_name] using XDA-Developers Legacy app
Well, that didn't work. I don't understand why. I followed all the instructions (unticked auto system update, auto software update, and auto time update; set time back 8 days, checked for OTA, rebooted, set time to today, checked for OTA, rebooted) but still no OEM unlock. The ROM that's currently installed predated Samsung getting wise to these tricks, so it SHOULD have worked. *shrug*
So I flashed the ROM again and am in jail for the next 7 days. Next time I'm in the market for a new phone, I'm going to have to give serious thought before I buy another Samsung. I don't appreciate them ****ing with me like this.
I found a way! yay
ok so, as "gaww" mentioned above; just go into Odin downloading mode and try to flash TWRP then phone show "Locked by FRP"
reboot and go to the phone setting > accounts > remove google and Samsung accounts!
enable USB debugging if you didn't
reboot
you will see OEM unlock backed!!!
hope its help
I am amazed by EFTSU in rooting my SM-N960N. Root is confirmed by adb shell, and su convert $ to # in shell. Exploration of /data/data/ for Sqlite db is quite enjoyable.
How can one construct SM-N960N_N960NKSU3FUE1_10_e06a4.8EFT which is 12.7MB, small in comparison with BL(4MB), AP, (4GB),CP(26MB), CSC(35MB)? Eftsu is related to AP through Magisk processed file described in "How to Root your Android ..." by Skanda Hazarika?
Hey, So yesterday I got the stupid idea to try out Android 13 QRP Beta 1.
I heard praise of Pixel-Flasher which helps out in Updating & maintaining root. Around 2 weeks ago I updated from Android 12 Stable to Android 13 Stable using ADB sideload & lost root, booting with magisk-patched img results in bootloop, So I ran the phone with my banking apps broken and without root for 2 weeks. I had enough and thought let's start fresh on QRP with proper root. So, I backed up all my data and prepared my Pixel 6 for formatting.
Finally, I tried my shot with Pixel-Flasher and read all instructions for usage, it was running pretty laggy on my M1 MBP. NOTE: I'm not Blaming the developer of Pixel-Flasher for anything, and I'm completely responsible for probably performing the wrong steps coming below.
I downloaded the factory zip for the latest Android 13 Sep Update [was running Aug], extracted and patched the boot.img using Pixel-Flasher and Magisk on my Pixel 6. Chose the option to WIPE Data and selected the patched-magisk.img and proceeded to flash. And I'm pretty sure this is where I screwed up by not selecting the stock img. The procedure went through and finally, my Phone flashed Phone is corrupted and will not boot, clicked the Power Button & it got stuck on the Google Logo. As it was stuck there I forced it to reboot and it went into fastboot d. I was sure I did something wrong so I powered it off and tried to boot into fastboot now... Black Screen no response, Connected charger... no response, Connected USB and held power + vol down for 60 secs... no response. The phone was at 95% so not battery dead by any chance.
This is where I diagnosed that I bricked the Motherboard. To add fire to the pot, I live in India & got this phone from my Uncle. No warranty in India.
Now I'm sitting here with regret and a 200g Paperweight. There is a Repair Shop called ShatterFix here in India that services Pixel 6 unofficially, and I'm considering sending in the phone for diagnosis. What I'm worried about is that the Motherboard replacement part itself costs close to ₹20,000 - ₹25,000 INR.
Any suggestions or help is welcome for a boy in misery. Had a great time with my Pixel 6 for 8 months, fell back to using my OnePlus 6T now.
Thanks, this is my first time posting a large essay thread like this. Sorry if it had useless info or if anything wasn't clear.
If you haven't tried https://flash.android.com/ then I'd suggest giving it a shot. You never know if it works..
I had the same issue on my 4a a while ago, nothing seemed to be working but then i used this, it detected the phone and flashed the latest version.
Aks said:
If you haven't tried https://flash.android.com/ then I'd suggest giving it a shot. You never know if it works..
I had the same issue on my 4a a while ago, nothing seemed to be working but then i used this, it detected the phone and flashed the latest version.
Click to expand...
Click to collapse
I did try that, as I can't even boot the phone into fastboot or ADB, the device is not detected
suhas2k said:
Hey, So yesterday I got the stupid idea to try out Android 13 QRP Beta 1.
I heard praise of Pixel-Flasher which helps out in Updating & maintaining root. Around 2 weeks ago I updated from Android 12 Stable to Android 13 Stable using ADB sideload & lost root, booting with magisk-patched img results in bootloop, So I ran the phone with my banking apps broken and without root for 2 weeks. I had enough and thought let's start fresh on QRP with proper root. So, I backed up all my data and prepared my Pixel 6 for formatting.
Finally, I tried my shot with Pixel-Flasher and read all instructions for usage, it was running pretty laggy on my M1 MBP. NOTE: I'm not Blaming the developer of Pixel-Flasher for anything, and I'm completely responsible for probably performing the wrong steps coming below.
I downloaded the factory zip for the latest Android 13 Sep Update [was running Aug], extracted and patched the boot.img using Pixel-Flasher and Magisk on my Pixel 6. Chose the option to WIPE Data and selected the patched-magisk.img and proceeded to flash. And I'm pretty sure this is where I screwed up by not selecting the stock img. The procedure went through and finally, my Phone flashed Phone is corrupted and will not boot, clicked the Power Button & it got stuck on the Google Logo. As it was stuck there I forced it to reboot and it went into fastboot d. I was sure I did something wrong so I powered it off and tried to boot into fastboot now... Black Screen no response, Connected charger... no response, Connected USB and held power + vol down for 60 secs... no response. The phone was at 95% so not battery dead by any chance.
This is where I diagnosed that I bricked the Motherboard. To add fire to the pot, I live in India & got this phone from my Uncle. No warranty in India.
Now I'm sitting here with regret and a 200g Paperweight. There is a Repair Shop called ShatterFix here in India that services Pixel 6 unofficially, and I'm considering sending in the phone for diagnosis. What I'm worried about is that the Motherboard replacement part itself costs close to ₹20,000 - ₹25,000 INR.
Any suggestions or help is welcome for a boy in misery. Had a great time with my Pixel 6 for 8 months, fell back to using my OnePlus 6T now.
Thanks, this is my first time posting a large essay thread like this. Sorry if it had useless info or if anything wasn't clear.
Click to expand...
Click to collapse
Sounds like you never flashed, at the minimum, the A13 bootloader, or the A13 image, to the other slot and when you ran into problems your phone reverted to the other slot which still had A12 on it, therefore causing you to brick your phone due to the new ARB (anti-rollback protection).
Not familiar with things in India, but I would at least try contracting Google and explaining that your phone died and you think it was because of the new anti-rollback protection they implemented in the A13 bootloader. From observations, they seem to be pretty good at either fixing or replacing devices that have run into this problem, maybe even without a warranty. Worth a shot...
suhas2k said:
I did try that, as I can't even boot the phone into fastboot or ADB, the device is not detected
Click to expand...
Click to collapse
Did you install the drivers from Google for ADB and fastboot?
Without these, the device can't be detected.
Cheers
tom1807 said:
Did you install the drivers from Google for ADB and fastboot?
Without these, the device can't be detected.
Cheers
Click to expand...
Click to collapse
Yes, for past 8 months I was updating with root using adb side load so yes, both fastboot & adb drivers are properly installed.
Lughnasadh said:
Sounds like you never flashed, at the minimum, the A13 bootloader, or the A13 image, to the other slot and when you ran into problems your phone reverted to the other slot which still had A12 on it, therefore causing you to brick your phone due to the new ARB (anti-rollback protection).
Not familiar with things in India, but I would at least try contracting Google and explaining that your phone died and you think it was because of the new anti-rollback protection they implemented in the A13 bootloader. From observations, they seem to be pretty good at either fixing or replacing devices that have run into this problem, maybe even without a warranty. Worth a shot...
Click to expand...
Click to collapse
Looks like you are right, it's ARB issue.
I did try contacting the B2X Service Centers in India and they only service now 6a but not the 6.