Related
Hi,
Complete noob here ( have educated myself fairly though)
My Nexus 5 (lollipop) has gone into boot loop (circle) from yesterday. I have not had a chance to go into settings to enable the usb debug. Also when I press volume down + power and try to go into recovery mode there is a yellow exclamation.
I unlocked the bootloader with fastboot oem unlock. Then I tried to fastboot reboot. After this it again when to the circle thingy. And if i go into the bootloader, it still says the lock state is locked.
Please let me know or point to resources on how to get it back. I'm presuming it can be recovered.
Prior to this my phone was restarting continuously which was due to the power button problem. I fixed it at a local repair shop, but this looks like something to do with os.
djconnexion said:
Hi,
Complete noob here ( have educated myself fairly though)
My Nexus 5 (lollipop) has gone into boot loop (circle) from yesterday. I have not had a chance to go into settings to enable the usb debug. Also when I press volume down + power and try to go into recovery mode there is a yellow exclamation.
I unlocked the bootloader with fastboot oem unlock. Then I tried to fastboot reboot. After this it again when to the circle thingy. And if i go into the bootloader, it still says the lock state is locked.
Please let me know or point to resources on how to get it back. I'm presuming it can be recovered.
Prior to this my phone was restarting continuously which was due to the power button problem. I fixed it at a local repair shop, but this looks like something to do with os.
Click to expand...
Click to collapse
99.9% of the time, if you reboot the bootloader and it has relocked or re-unlocked itself after you run the lock/unlock command, it means that the NAND memory is fried and you'll need a new motherboard. Send it for warranty repair / replacement.
rootSU said:
99.9% of the time, if you reboot the bootloader and it has relocked or re-unlocked itself after you run the lock/unlock command, it means that the NAND memory is fried and you'll need a new motherboard. Send it for warranty repair / replacement.
Click to expand...
Click to collapse
Thanks, its out of warranty. So have to buy myself a new phone now, instead of going for a new motherboard.
What about the 00.1%?
djconnexion said:
Thanks, its out of warranty. So have to buy myself a new phone now, instead of going for a new motherboard.
What about the 00.1%?
Click to expand...
Click to collapse
Do you not live in Europe?
The other 0.01%, actually I have never seen anyone in this group. I have only ever seen 99.9%, but perhaps it is actually 100%
The other ( and it's probably around 50% ) Don't have the patience to wait for the wipe to complete and restart it before hand!
Niflheimer said:
The other ( and it's probably around 50% ) Don't have the patience to wait for the wipe to complete and restart it before hand!
Click to expand...
Click to collapse
That would be a different issue.
rootSU said:
99.9% of the time, if you reboot the bootloader and it has relocked or re-unlocked itself after you run the lock/unlock command, it means that the NAND memory is fried and you'll need a new motherboard. Send it for warranty repair / replacement.
Click to expand...
Click to collapse
Question: What fires the NAND? I have been unlocking and relocking my BL multiple times and I haven't faced the issue. Is it just a stroke of bad luck or while unlocking the BL will skipping any step cause it?
gamer.11 said:
Question: What fires the NAND? I have been unlocking and relocking my BL multiple times and I haven't faced the issue. Is it just a stroke of bad luck or while unlocking the BL will skipping any step cause it?
Click to expand...
Click to collapse
Many things can damage it, not just one specific reason.
gamer.11 said:
Question: What fires the NAND? I have been unlocking and relocking my BL multiple times and I haven't faced the issue. Is it just a stroke of bad luck or while unlocking the BL will skipping any step cause it?
Click to expand...
Click to collapse
Bad luck. As @Lethargy says could be anything.
I've been going over a few dozen NAND failure reports and so far I have nothing. It's not a particular batch , it's not a clear set of steps that brick it. All that I glanced is that tool-kits users seem to have a higher incidence of it - but the number of report is too small to be statistically relevant.
General wear could be a cause - but even so , the write counts shouldn't be so high to cause it - from what I could find nexus 5 NAND is rated at 48 TB of writes.
Niflheimer said:
I've been going over a few dozen NAND failure reports and so far I have nothing. It's not a particular batch , it's not a clear set of steps that brick it. All that I glanced is that tool-kits users seem to have a higher incidence of it - but the number of report is too small to be statistically relevant.
General wear could be a cause - but even so , the write counts shouldn't be so high to cause it - from what I could find nexus 5 NAND is rated at 48 TB of writes.
Click to expand...
Click to collapse
Wear could cause it if there were a bug in the wear-levelling code for the NAND firmware. Its unlikely but the galaxy s3 had that. I think we'd see many more instances though
We'd do indeed - especially for those of us who flash a different rom every day.
I'm curious , did anyone try flashing a image with the lg tool ? it might force a block recount since it bypasses a good part of the firmware.
Edit: I remember the old s3 kernel bug - though that was a fringe case that affected everyone with that particular chip and kernel. In our case it's too random for that.
Has anyone taking the time to try and figure out who manufactures the nand? I researched it a few years ago for another device and at that time there where only about 3 real suppliers. Everyone else just put there own stamp on it. It was Samsung, SansDisk and some other company I can't remember off the top of my head. I don't really think the nand failures we are seeing are outside of the norm but cheap nand could be more prone to corruption than better nand. You get what you pay for or so they say.
Hi all,
Hoping a kind tech wiz will be able to help me out here, having had a Z3 for a couple of weeks I dropped it- back down - from a couple of feet and the front glass completely shattered leaving the screen unresponsive.
Having received a quote in the region of £200 I figure I may as well sell it for spares and buy a new device. However, for peace of mind, I'd like to wipe the phone completely before selling it on. Is this possible to do without being able to use the screen?
Thanks
Dan
There are several ways you can factory reset your phone with broken screen. The first one that comes to mind is with PC Companion repair option. Make sure your battery level is above 80%.
Follow this tutorial and you're all set.
https://www.youtube.com/watch?v=CFUEQV6ob_4
fijasko said:
There are several ways you can factory reset your phone with broken screen. The first one that comes to mind is with PC Companion repair option. Make sure your battery level is above 80%.
Follow this tutorial and you're all set.
Click to expand...
Click to collapse
I've tried this but I can't get very far because my phone had a pin lock on before it broke and the companion app doesn't work if the screen is locked. I know what the pin is but obviously can't input it, any other ideas that could help?
Two V10's on Marshmallow. Both will randomly display the 48 hrs unlock message and make me use my unlock pattern instead of fingerprint to unlock my phone. It can be 5 seconds after I last used the phone, or several hours. It just happens randomly on both phones.
Anyone else, or any ideas?
Idk reset phone
Sent from my LG-H900 using XDA-Developers mobile app
dvtmg704 said:
Idk reset phone
Sent from my LG-H900 using XDA-Developers mobile app
Click to expand...
Click to collapse
Resetting phone will most likely not do anything. It probaly has something to do with the system partition, which if he is on Marshmallow, is untouchable
plastic_green_head said:
Two V10's on Marshmallow. Both will randomly display the 48 hrs unlock message and make me use my unlock pattern instead of fingerprint to unlock my phone. It can be 5 seconds after I last used the phone, or several hours. It just happens randomly on both phones.
Anyone else, or any ideas?
Click to expand...
Click to collapse
Its a security step. If you havent used your backup secure lock method (pin,password,pattern) in 48 hours, it promtps you to do so just to be certain you are the legit owner. Because alot of fingerprint sensors are NOT 100% accurate. Aswell there are ways to spoof a FPS, not bypass, i mean spoof,aka trick. I wont list how though. So dont worry, its a for your protection, and its a good step. Iphones were unlocked by cat paws. So if someone takes your phone and spoofs the fingerprint, they will only have access for 48 hours before they need your pin, password, or pattern, that only you know.
Shadow Assassin said:
Its a security step. If you havent used your backup secure lock method (pin,password,pattern) in 48 hours, it promtps you to do so just to be certain you are the legit owner. Because alot of fingerprint sensors are NOT 100% accurate. Aswell there are ways to spoof a FPS, not bypass, i mean spoof,aka trick. I wont list how though. So dont worry, its a for your protection, and its a good step. Iphones were unlocked by cat paws. So if someone takes your phone and spoofs the fingerprint, they will only have access for 48 hours before they need your pin, password, or pattern, that only you know.
Click to expand...
Click to collapse
Very late to reply, lol. But that reply didn't help. I already stated that it would ask me for it completely at random... even if it's been under 48 hrs since the last time I have used the backup secure unlock method. I could use it 5 seconds ago, and it could ask me again in another 5 seconds. I will repeat. It asks me for it randomly, even if it's been under 48 hrs since the last time I had to enter it.
I saw a user complaining about it somewhere on XDA forums. It seems like an early symptom of your phone dying. According to him, the phone randomly asked for unlock pin instead of fingerprint and would show something like "finger print unavailable for 48 hours". It was because his phone would reboot randomly when it was not in use. Try keeping an eye on your phone to check if it randomly shuts down and boots up? If so, back up your data and get ready for it to die.
plastic_green_head said:
Very late to reply, lol. But that reply didn't help. I already stated that it would ask me for it completely at random... even if it's been under 48 hrs since the last time I have used the backup secure unlock method. I could use it 5 seconds ago, and it could ask me again in another 5 seconds. I will repeat. It asks me for it randomly, even if it's been under 48 hrs since the last time I had to enter it.
Click to expand...
Click to collapse
I see my mistake. I will say I noticed this on my v10 a long time ago but then it stopped. Im at a loss as to whats going on or how to fix it. Sorry
Every time I unlock my screen, whether it's with the fingerprint or pattern, the screen will flicker for half a second. Super annoying because it's a bright white flash.
It's not face unlock assistive lighting, as I've ensured that is turned off.
I've also tried every display setting possible, toggling things like vision comfort, comfort tone, refresh rates, display calibrations, changing wallpaper, and so on.
Really hoping this isn't a hardware issue because I'm also noticing my touches don't register all the time, unless I'm pressing the screen slightly harder. Not sure if it's my screen protector but I am left a bit concerned.
Any ideas? I've Googled this a bit and I've noticed others have the same issue but on OnePlus 6 devices for the most part, not the 9 series. If anyone has run into this before and knows a fix, I'd love to hear it, thanks!
That's how the fingerprint works. It increases the screen brightness to the max usually. It's the flaw of using that kind of fingerprint rather than sonic like Samsung. Believe it takes a picture of your fingerprint and compares vs ultrasonic gets a 3D image, the difference is in speed too, optical is faster, but ultrasonic technically more secure and does not rely on lightning conditions. I personally prefer the hardware on the back kind over both.
zymphad said:
That's how the fingerprint works. It increases the screen brightness to the max usually. It's the flaw of using that kind of fingerprint rather than sonic like Samsung. I personally prefer the hardware on the back kind.
Click to expand...
Click to collapse
I don't remember it being this prominent on my previous OnePlus devices, though. My 8 Pro did not flicker as aggressively as this one does. It's enough for me to clearly notice it, even in brighter areas; this is why I've been left with a bit more concern than usual.
Not to mention this occurs even if I use my pattern to unlock.
Not sure. Mine does the same but doesn't bother me in the least bit. If it happened at other times other than unlock would be different story.
zymphad said:
Not sure. Mine does the same but doesn't bother me in the least bit. If it happened at other times other than unlock would be different story.
Click to expand...
Click to collapse
Any chance you could try and make a video of it happening on your device? I just want to see if it's the same thing as mine. That way, I'll have a better idea of this being a defect or normal behaviour.
I know, it's kind a big ask so no rush! If you ever have time. I can do the same if anyone needs to see what I am talking about exactly.
Update:
I've noticed the issue occurs only if the lock screen is showing. If ambient display is on and the fingerprint icon shows at the bottom then the device will unlock without flickering. The fact that it's happening only when the screen is on at the lock screen, is what's making me feel like maybe it's not a hardware problem. Very odd issue...
Another update,
After doing more Googling I came to the conclusion that it's a hardware issue over software. I tried to factory reset and the issue was still present.
I couldn't update the software on the phone though. It kept telling me that there was an installation problem. I'm guessing that's because I had previously used a rooted EU boot img and a factory reset through the phone settings isn't enough to get rid of that. I'm hoping the repair center won't fault me for sending the device back with an unlocked bootloader. Doesn't seem like OnePlus would do that anyway, given how open they are with the modding community.
Once I receive the replacement of test to see if the issue was still there and will update this thread.
rickysidhu_ said:
Another update,
After doing more Googling I came to the conclusion that it's a hardware issue over software. I tried to factory reset and the issue was still present.
I couldn't update the software on the phone though. It kept telling me that there was an installation problem. I'm guessing that's because I had previously used a rooted EU boot img and a factory reset through the phone settings isn't enough to get rid of that. I'm hoping the repair center won't fault me for sending the device back with an unlocked bootloader. Doesn't seem like OnePlus would do that anyway, given how open they are with the modding community.
Once I receive the replacement of test to see if the issue was still there and will update this thread.
Click to expand...
Click to collapse
One time I sent them bricked device and they still accepted the return. Returning unlocked bootloader phone shouldn't be a problem.
What made you think it was hardware since I see other people have the same thing. Hell I had it too. I don't seem to have that problem after updating to latest firmware. Seems to be software to me.
Hope it gets fixed. I saw a thread for it on OnePlus community forum, so hopefully OnePlus knows.
rickysidhu_ said:
I'm hoping the repair center won't fault me for sending the device back with an unlocked bootloader. Doesn't seem like OnePlus would do that anyway, given how open they are with the modding community.
Click to expand...
Click to collapse
When I sent the phone away for trade in there was no mention of rooting or bootloader unlock. Just wipe it.of your info and data.
zymphad said:
What made you think it was hardware since I see other people have the same thing. Hell I had it too. I don't seem to have that problem after updating to latest firmware. Seems to be software to me.
Hope it gets fixed. I saw a thread for it on OnePlus community forum, so hopefully OnePlus knows.
Click to expand...
Click to collapse
Thinking it's hardware because my 8 Pro doesn't literally cause a white flash of the entire screen, it would just up the brightness which is normal.
And I was also noticing my touches only registered on more firm presses. Made me think it could have been a bad display panel.
Didn't want to take any chances especially while inside the 15 day return/replacement window.
rickysidhu_ said:
Thinking it's hardware because my 8 Pro doesn't literally cause a white flash of the entire screen, it would just up the brightness which is normal.
And I was also noticing my touches only registered on more firm presses. Made me think it could have been a bad display panel.
Didn't want to take any chances especially while inside the 15 day return/replacement window.
Click to expand...
Click to collapse
Yeah good plan.
It absolutely does NOT do that on mine. Only the fingerprint area gets bright, not the entire screen.
NotTheGiant said:
It absolutely does NOT do that on mine. Only the fingerprint area gets bright, not the entire screen.
Click to expand...
Click to collapse
+1 on the 9Pro
According to the OnePlus support section of the site, the progress shows as "Inspected". I assume the next step is shipping out a replacement. Hopefully it's soon, will post an update on the new unit.
Thanks for letting me know you guys aren't experiencing the issue, makes me feel good about my decision of sending it back. Almost didn't do it because I didn't want to come back to this Pixel 5 after being spoiled by that 9's screen size lol.
Got the replacement today, after some testing it seems like this unit has no issues! There is a clear difference between this one and my original. There was a blinding white flash even when using my pattern to unlock. Same thing when double tapping the lock screen to put the device to sleep.
This has no white flashes so definitely seems like a hardware issue. Finally, I can start enjoying this thing!
rickysidhu_ said:
Got the replacement today, after some testing it seems like this unit has no issues! There is a clear difference between this one and my original. There was a blinding white flash even when using my pattern to unlock. Same thing when double tapping the lock screen to put the device to sleep.
This has no white flashes so definitely seems like a hardware issue. Finally, I can start enjoying this thing!
Click to expand...
Click to collapse
Awesome, glad you got a good one! They didn't make you wait too long...
rickysidhu_ said:
Got the replacement today, after some testing it seems like this unit has no issues! There is a clear difference between this one and my original. There was a blinding white flash even when using my pattern to unlock. Same thing when double tapping the lock screen to put the device to sleep.
This has no white flashes so definitely seems like a hardware issue. Finally, I can start enjoying this thing!
Click to expand...
Click to collapse
How bro it can be a hardware issue.. it's only happens on low brightness when you unlock the phone right?I am also facing the same issue but it is not there where I unboxed the phone and used it for 1day after receiving update to os 11.2.7.7only this problem starts to me..so how can it be a hardware issue
Bodhidharman said:
How bro it can be a hardware issue.. it's only happens on low brightness when you unlock the phone right?I am also facing the same issue but it is not there where I unboxed the phone and used it for 1day after receiving update to os 11.2.7.7only this problem starts to me..so how can it be a hardware issue
Click to expand...
Click to collapse
No it happened on any brightness. It was just more noticeable in low brightness and reading through the same issue on OP forums, others were confirming it is hardware related as a complete factory reset isn't able to resolve the issue. If it was software related, a complete restore would have/should have fixed it. Your issue might be different from what I was experiencing.
Hello all,
First post here and hoping someone can help me!!
I got a Samsung S22 ultra back during launch this year (Feb or March time?) and it's an awesome phone but unfortunately, over the last few months it's begun randomly restarting/rebooting itself on it's own accord (I remember checking and I have no settings ON to make it do this). It was mildly annoying and to be honest, I just persevered and didn't do a factory reset back then which I probably should have in hindsight...
Fast forward to this week. I am out walking the dog and my battery drops to 5% and the screen darkens in an attempt to conserve battery. I think in this time I have somehow maxed out my screen unlock attempts to the point that it now says 'Try again in 24 hours' which I thought would be fine if it wasn't for the fact that every time my phone randomly restarts itself, it also restarts the 24 hour lock period.
Essentially, I am indefinitely locked out of my phone and unfortunately remote unlock is off. Why oh why I do not know but I am kicking myself.
Basically, is there ANYWAY or METHOD that anyone can help me with that would enable my phone to stay powered on for the full 24 hours? the solution seems easy enough to me, allow the countdown to reach 0 and I will be able to unlock my phone again with fingerprint/pin. I have downloaded something called 'Droidkit' from Imobie and they have a feature called system fix. Could that be installed safely to my phone and perhaps correct or update any firmware/software isssues that is causing the reset? Or is the Samsung Knox security too secure?
I am absolutely desperate as I have got no back up arranged and stand to lose nearly 2/ 3 years of photos and videos of sentimental value (wedding, honeymoon, relatives, memories etc) and it's incredibly distressing to think my only option is factory reset when if my phone COULD JUST STAY POWERED ON FOR 24 HOURS AND ALLOW ME TO UNLOCK IT.
Please help, thank you in advance.
If you really need that data... use a data recovery specialist. That phone, if survives the data retrieval attempt, needs to go in for repair.
You can try keeping it on the charger to see if that prevents a reboot. Even with an SD card I redundantly backup its critical data, you should too.
blackhawk said:
If you really need that data... use a data recovery specialist. That phone, if survives the data retrieval attempt, needs to go in for repair.
You can try keeping it on the charger to see if that prevents a reboot. Even with an SD card I redundantly backup its critical data, you should too.
Click to expand...
Click to collapse
Sadly, keeping it plugged in to the charger doesn't keep it on power for 24 hours - it tends to restart randomly every so often still
Well I went to an official Samsung store today in the UK - I was told that for them to fix it would involve wiping/factory resetting the phone. Losing everything (which I am not yet prepared to do).
Would rebooting to bootloader be any good? I am not good with this stuff!
Thanks
Why you just don't switch phone off, and leave it like that for 24 hours?
Phone doesn't need to be turned on.
vinoboxer said:
Sadly, keeping it plugged in to the charger doesn't keep it on power for 24 hours - it tends to restart randomly every so often still
Well I went to an official Samsung store today in the UK - I was told that for them to fix it would involve wiping/factory resetting the phone. Losing everything (which I am not yet prepared to do).
Would rebooting to bootloader be any good? I am not good with this stuff!
Thanks
Click to expand...
Click to collapse
Try chilling it down to 50F, see if that helps.
Never attempt to charge an Li near or below freezing though. Bag it before you chill it.
The screen lock complicates everything. Files are encrypted so you need those encryption keys to access data. Way beyond the level I could troubleshoot. A data recovery specialist is your best shot. They may need to remove the chipset to access the files. Fees are around $800.
You can keep trying, get it into safe mode if possible. I never use a screen lock as you are the one most likely to be locked out, sometimes through no fault of your own. Having lost a 30yo database that's not recreatable myself, you have my empathy. Sometimes all you can do is learn from your mistakes... and not repeat them.
vinoboxer said:
Hello all,
First post here and hoping someone can help me!!
I got a Samsung S22 ultra back during launch this year (Feb or March time?) and it's an awesome phone but unfortunately, over the last few months it's begun randomly restarting/rebooting itself on it's own accord (I remember checking and I have no settings ON to make it do this). It was mildly annoying and to be honest, I just persevered and didn't do a factory reset back then which I probably should have in hindsight...
Fast forward to this week. I am out walking the dog and my battery drops to 5% and the screen darkens in an attempt to conserve battery. I think in this time I have somehow maxed out my screen unlock attempts to the point that it now says 'Try again in 24 hours' which I thought would be fine if it wasn't for the fact that every time my phone randomly restarts itself, it also restarts the 24 hour lock period.
Essentially, I am indefinitely locked out of my phone and unfortunately remote unlock is off. Why oh why I do not know but I am kicking myself.
Basically, is there ANYWAY or METHOD that anyone can help me with that would enable my phone to stay powered on for the full 24 hours? the solution seems easy enough to me, allow the countdown to reach 0 and I will be able to unlock my phone again with fingerprint/pin. I have downloaded something called 'Droidkit' from Imobie and they have a feature called system fix. Could that be installed safely to my phone and perhaps correct or update any firmware/software isssues that is causing the reset? Or is the Samsung Knox security too secure?
I am absolutely desperate as I have got no back up arranged and stand to lose nearly 2/ 3 years of photos and videos of sentimental value (wedding, honeymoon, relatives, memories etc) and it's incredibly distressing to think my only option is factory reset when if my phone COULD JUST STAY POWERED ON FOR 24 HOURS AND ALLOW ME TO UNLOCK IT.
Please help, thank you in advance.
Click to expand...
Click to collapse
you could send it to a unofficial repair store and let them check the phone, they might change the battery and check for any hardware issue or at least keep the phone on for you to be able open and backup everything from your phone.
you might lose the warranty by doing so.
i wish you the best.
All I see is you got too confident. If you have had fixed the randomly reboots when you started experiencing it this problem you have now would be easily fixed in 24 hours. Anyways, if I were in your shoes, I would try to flash the current complete firmware through Odin but flashing the HOME_CSC binary as CSC, since that one is supposed to don't wipe your data. That's what I would do (without high hopes) before doing a factory reset if that's my only option.
Try to unlock with Google's Find my phone app.
Hi, trying to boot into safe mode could potentially prevent the random reboots ONLY IF the culprit is an app.... It's worth trying anyway...
Why not factory reset in bootloader. It will trigger FRP lock but as long as you know your unlock code/password it will work fine. You'll lose your data but you'll be back in the phone
draskome said:
Why you just don't switch phone off, and leave it like that for 24 hours?
Phone doesn't need to be turned on.
Click to expand...
Click to collapse
I'm with draskome....
I don't have a S22 and my last Galaxy S was an S5 so I doubt I know anything...but where does it say it has to be on for 24 hours straight? All the other posts on this thread seem to take that condition as a given, so maybe it's just something a non-S22 user wouldn't know.... I would think that turning it off for at least 24 hours, and then turning on & loading up the phone, the phone's internal check would find 24 hours have passed and remove the "lock" on it; and that would only need a nanosecond to confirm...
If not, what a complete oversight by Samsung! That is completely stupid requirement that it must be on for 24 hours; I would see no intrinsic value in it needing to be on for that long before removing the lock.... maybe someone can explain....
simplepinoi177 said:
I'm with draskome....
I don't have a S22 and my last Galaxy S was an S5 so I doubt I know anything...but where does it say it has to be on for 24 hours straight? All the other posts on this thread seem to take that condition as a given, so maybe it's just something a non-S22 user wouldn't know.... I would think that turning it off for at least 24 hours, and then turning on & loading up the phone, the phone's internal check would find 24 hours have passed and remove the "lock" on it; and that would only need a nanosecond to confirm...
If not, what a complete oversight by Samsung! That is completely stupid requirement that it must be on for 24 hours; I would see no intrinsic value in it needing to be on for that long before removing the lock.... maybe someone can explain....
Click to expand...
Click to collapse
I think you're correct but maybe the OP's firmware or hardware is fubar and not following the protocol.
Got locked out of a bios like that, a hardware failure. Had I never set a password no lockout would have occured.
blackhawk said:
I think you're correct but maybe the OP's firmware or hardware is fubar and not following the protocol.
Got locked out of a bios like that, a hardware failure. Had I never set a password no lockout would have occured.
Click to expand...
Click to collapse
Hmmm...I wonder...
I find it unlikely that if OP is able to keep his phone turned on (but locked out) for some time -- just not for the 24 hours straight as the phone will randomly restart -- and the phone's hardware is that "fubar" so badly that it can keep on for at least minutes (if not hours) but not be able to track or release after finding out 24 hours has passed. I might believe the "fubar" failure is that severe if the phone would crash when loading up or immediately restart when starting up -- but then OP would say "bootloop" and not merely that it "randomly restarts" -- but it seems stable enough for at least a little while....
If what you say is true in the end, then the OP probably has no hope because even stopping the random restarts might not resolve the countdown properly because the "hardware [is]....not following the protocol" regardless....
simplepinoi177 said:
Hmmm...I wonder...
I find it unlikely that if OP is able to keep his phone turned on (but locked out) for some time -- just not for the 24 hours straight as the phone will randomly restart -- and the phone's hardware is that "fubar" so badly that it can keep on for at least minutes (if not hours) but not be able to track or release after finding out 24 hours has passed. I might believe the "fubar" failure is that severe if the phone would crash when loading up or immediately restart when starting up -- but then OP would say "bootloop" and not merely that it "randomly restarts" -- but it seems stable enough for at least a little while....
If what you say is true in the end, then the OP probably has no hope because even stopping the random restarts might not resolve the countdown properly because the "hardware [is]....not following the protocol" regardless....
Click to expand...
Click to collapse
Don't know. Maybe if they play with it a bit... but if the lock screen pass code has been corrupted... fubar.
Always redundantly backup critical data regularly, if you have a SD card slot use it. Having a data drive many times saves the data if the phone dies. Don't encrypt it...
reflash the firmware (use home csc), boot into safe mode