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?
Related
just bought this phone, G965FD model. do i really need to wait the 7 days or is their a way to bypass that for real works? i ws on bre6 and i downgraded to the ARC5 build thinking it would help but no dice..any true honest help and details for the correct instructions would be appreciated.
im at my last nerves with this thing. i know that reading is good but when youve spent the last 3 days at 8+ hours per day reading and not fully understanding it is frustrating. really needing root. thanks in advance
For the 7d if you are not rmm status prenormal you should be able to do the date hack. It was published on the xda news feed a bit ago but the gist of it is:
1) disable auto date/time and manually set date to like a month ago. At least 9 - 10 days
2) do the manual check for system update
3) change date back to auto or manually set to today.
4) reboot (may not be needed I forget but won't hurt)
5) check for system updates again.
They might have patched this but it's worth trying. You can see if youre rmm prenormal by booting download mode it will be in the text on the flashing screen.
Good luck!
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)?
I've possibly followed all types of instructions on the Internet to install TWRP on my S9+, but it hasn't worked for me.
My phone is a Samsung S9+, Android 10, G965F, star2lte, bought in Indonesia. "OEM Unlocking" is visible and ON (Bootloader already unlocked) in the Developer menu.
After turning off the phone and booting using Vol-down+Bixby+Power, and after pressing Vol-up, it goes into Download mode just fine. However, RMM is displayed as "Prenormal". I waited 168h (actually 172h) to make sure that wasn't the issue. I have done this more than once, after trying all types of install methods. Every time I wait 168h+, but it does not change the outcome, i.e., RMM is ALWAYS in Prenormal, even though "OEM Unlocking" is ON in the Developer menu.
Odin (v3.14) shows "Added!", "Auto Reboot" is disabled, the TWRP tar file is loaded into AP. When I press Start, the progress bar above ID:COM goes green until it hits the end and abruptly turns red while flashing "FAIL!". Then, a red line across the phone screen reads, "Only official released binaries are allowed to be flashed(RECOVERY)". That's it...
I tried the other methods described on the LineageOS website, i.e., `adb sideload filename.zip`, but the process when reaches 47% (as described in the article), it says "Total xfer: 1.00x", but the next reboot goes to the Samsung A10 OS.
Really looking for help with this...
Another thing. I opened an account with Chimera some time back, thinking that their tools could help me switch RMM, but it did not help, This is their answer:
Yes the problem could come from the RMM state of the device and from the FRP lock too. But in your case the FRP lock is OFF. Which is a good state. The RMM unlock can be done for the devices but only in ADB mode. Which is not workable for you currently. what you can try is to reflash the device with the stock firmware or with a combination file and then do the RMM unlock.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I've tried flashing the firware with the stock firmware from Samsung, but the result is the same, no matter which firware I use.
However, how to I try the "combination file"? Where can I find that? Any advice?
More info about the phone:
- Baseband version: G965FXXU9ETF2
- Knox version: 3.4.1
- PRODUCT NAME: SM-G965F
- CURRENT BINARY: Samsung Official
- RMM STATE: Prenormal
- FRP: OFF
- EOM: OFF
- Secure Download: Enabled
- CCIC: MAX77705 hw: 3 main: 30
- WARRANTY VOID: 0 (0x0000)
- RP SWREV: B:9 K:9 S:9
There are other params, but I'm not sure if it's useful here.
I've checked out the combination file, but it seems that I can't downgrade to A9 or A8 because of the RP protection. Should I use U9 to give it a try? (shooting in the dark, here...)
welcome to club... that's what the bounty is for
aIecxs said:
welcome to club... that's what the bounty is for
Click to expand...
Click to collapse
How to do that?
sorry i am native german speaker. there exist no solution, nothing you can do...
aIecxs said:
sorry i am native german speaker. there exist no solution, nothing you can do...
Click to expand...
Click to collapse
Thanks for the reply. Could you tell me why, even in German (I'll use Google Translate if necessary)?
aIecxs said:
sorry i am native german speaker. there exist no solution, nothing you can do...
Click to expand...
Click to collapse
Also, I talked to the reseller I bought the S9 from, and for a fee he's willing to exchange my S9 updated to Android 10 to a new S9 with stock Android 8.
Will I then be able to install TWRP+LineageOS 15 on Android 8? Then if so, will I subsequently be able to upgrade to Lineage 16 (A9), then 17 (A10) without encountering RMM=Prenormal and being stuck again?
ask reseller to unlock bootloader
aIecxs said:
ask reseller to unlock bootloader
Click to expand...
Click to collapse
Where I am, i.e., Indonesia – not in Jakarta, that's not an option, unfortunately...
I'm not familiar with this issue but check this.. It may work..
Leon said:
I'm not familiar with this issue but check this.. It may work..
Click to expand...
Click to collapse
Thanks for taking the time to send that video – much appreciated. I tried that before, but it didn't work either.
Sorry to hear that. I guess is more complicated than it seems.
OK, reposting my answer here: I don't think we'll ever succeed, from what I have been told by Chimera themselves. They said that sometime in June 2020, as part of their latest Android 10 update, Samsung locked entirely RMM, for good, and there's no way to disable it. From my knowledge on the subject (which is pretty limited), I don't think it is possible if your device is running Android 10 past June 2020. I'd love someone to confirm that, but no one has so far, and it's not because of lack ot trying...
What I did is I returned my Samsung S9 Plus to the reseller, handed him some money and got a brand new device with stock Android 8.0. I then did the 7-day wait so OEM could be enabled, which worked (finally!!!), then installed TWRP, then Lineage 15.1 (but I had to install VENDOR-27_ARI9.zip before that, because it wanted Android 8.1, and not 8.0) + Magisk + DM-Verify + GAPS (pico), then it booted on Lineage 15.1 like a charm. I still can't believe it's working...
I am now going to upgrade to LineageOS 16.0, then 17.1, then 18 if that's available. Let's cross fingers!
leobassin said:
OK, reposting my answer here: I don't think we'll ever succeed, from what I have been told by Chimera themselves. They said that sometime in June 2020, as part of their latest Android 10 update, Samsung locked entirely RMM, for good, and there's no way to disable it. From my knowledge on the subject (which is pretty limited), I don't think it is possible if your device is running Android 10 past June 2020. I'd love someone to confirm that, but no one has so far, and it's not because of lack ot trying...
What I did is I returned my Samsung S9 Plus to the reseller, handed him some money and got a brand new device with stock Android 8.0. I then did the 7-day wait so OEM could be enabled, which worked (finally!!!), then installed TWRP, then Lineage 15.1 (but I had to install VENDOR-27_ARI9.zip before that, because it wanted Android 8.1, and not 8.0) + Magisk + DM-Verify + GAPS (pico), then it booted on Lineage 15.1 like a charm. I still can't believe it's working...
I am now going to upgrade to LineageOS 16.0, then 17.1, then 18 if that's available. Let's cross fingers!
Click to expand...
Click to collapse
Just a quick update: It's now running Lineage OS 17.1 fine; I just love Lineage OS.
leobassin said:
Just a quick update: It's now running Lineage OS 17.1 fine; I just love Lineage OS.
Click to expand...
Click to collapse
How did you install custom rom's without having custom recovery?
the post you quoted says "[...] installed TWRP [...]" - looks pretty much like custom recovery to me
leobassin said:
OK, reposting my answer here: I don't think we'll ever succeed, from what I have been told by Chimera themselves. They said that sometime in June 2020, as part of their latest Android 10 update, Samsung locked entirely RMM, for good, and there's no way to disable it. From my knowledge on the subject (which is pretty limited), I don't think it is possible if your device is running Android 10 past June 2020. I'd love someone to confirm that, but no one has so far, and it's not because of lack ot trying...
What I did is I returned my Samsung S9 Plus to the reseller, handed him some money and got a brand new device with stock Android 8.0. I then did the 7-day wait so OEM could be enabled, which worked (finally!!!), then installed TWRP, then Lineage 15.1 (but I had to install VENDOR-27_ARI9.zip before that, because it wanted Android 8.1, and not 8.0) + Magisk + DM-Verify + GAPS (pico), then it booted on Lineage 15.1 like a charm. I still can't believe it's working...
I am now going to upgrade to LineageOS 16.0, then 17.1, then 18 if that's available. Let's cross fingers!
Click to expand...
Click to collapse
I don't understand your logic. So you returned an android 10 s9 plus to receive a s9 plus with a lower android 8 , then flashed a series of firmwares that took you to ...wait.......back to android 10 anyway??
IMO stock android 10 is much more stable and its arm64 platform is not exactly buggy .
Better to stick to stock in these newer phones until custom firmware is much more prominent.
I'm all for rooting modding , I have lots of android TV boxes, amazon devices running twrp magisk etcetera.
But I feel somethings should be left alone .
S9+ Exynos (unrooted , debloated , nova launcher , brave browser , YouTube Vanced)
Good enough for me
Just a thought
@Bertonumber1 you must have missed the point that indeed that was the only way left to overcome non-unlockable bootloader
aIecxs said:
@Bertonumber1 you must have missed the point that indeed that was the only way left to overcome non-unlockable bootloader
Click to expand...
Click to collapse
ok sorry , i get it mow , so i wont be able to flash a post june 2020 update s9 +
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.
Hello all...hoping to get some assistance with this thing. Long story short, debloated it due to horrid battery life and high heat. Everything was great until about a week ago when my settings app go renamed somehow. Tried fixing it but couldn't find the com.android.settings file with the correct signature for my phone (AT&T, US Model, unlocked, not rooted).
It's been working fine except no settings...so I backed up the usual stuff and had plans to do a factory reset this weekend. A few hours ago I picked it up and it went all wonky on me. Upon boot, it comes up to the lock screen and then the screen just starts turning on/off. I'm unable to bring up the passcode screen...but, am able to bring up the power menu by holding the power button. But, can't power down or get into safe mode that way. After about 5 seconds of doing this, it reboots. Rinse and repeat. Safe mode via buttons starts, but, does the same thing.
I am able to get into both recovery mode and download mode though. I can view logs/etc.
Normally, I'd just ***** and moan, then do the factory reset, However, I made one huge oversight when I backed up my data earlier this week and forgot to backup my notes. There's about a dozen of them, pages and pages long with all the medical details regarding my sons illness that I've been tracking for years. It's a nightmare dealing with different Dr's all the time so I've logged it all on the phone. Unfortunately, the best app I've found for it doesn't do cloud storage and keeps them saved as local txt files on the device.
Is there any hope I can somehow pull the files using recovery/download mode or utilize the logs to determine the errors and fix it enough to be able to get them? I'm fairly tech savvy and have ADB installed. I'm super ADD though and my head is just spinning trying to sort through all the possible posts regarding trying to do this...many being for older phones.
Absolute worst case, is there a legitimate service that would be able to do it?
Any help recovering my son's medical notes would be really really appreciated.
RiBBiTeDD said:
Hello all...hoping to get some assistance with this thing. Long story short, debloated it due to horrid battery life and high heat. Everything was great until about a week ago when my settings app go renamed somehow. Tried fixing it but couldn't find the com.android.settings file with the correct signature for my phone (AT&T, US Model, unlocked, not rooted).
It's been working fine except no settings...so I backed up the usual stuff and had plans to do a factory reset this weekend. A few hours ago I picked it up and it went all wonky on me. Upon boot, it comes up to the lock screen and then the screen just starts turning on/off. I'm unable to bring up the passcode screen...but, am able to bring up the power menu by holding the power button. But, can't power down or get into safe mode that way. After about 5 seconds of doing this, it reboots. Rinse and repeat. Safe mode via buttons starts, but, does the same thing.
I am able to get into both recovery mode and download mode though. I can view logs/etc.
Normally, I'd just ***** and moan, then do the factory reset, However, I made one huge oversight when I backed up my data earlier this week and forgot to backup my notes. There's about a dozen of them, pages and pages long with all the medical details regarding my sons illness that I've been tracking for years. It's a nightmare dealing with different Dr's all the time so I've logged it all on the phone. Unfortunately, the best app I've found for it doesn't do cloud storage and keeps them saved as local txt files on the device.
Is there any hope I can somehow pull the files using recovery/download mode or utilize the logs to determine the errors and fix it enough to be able to get them? I'm fairly tech savvy and have ADB installed. I'm super ADD though and my head is just spinning trying to sort through all the possible posts regarding trying to do this...many being for older phones.
Absolute worst case, is there a legitimate service that would be able to do it?
Any help recovering my son's medical notes would be really really appreciated.
Click to expand...
Click to collapse
Man, i'm so sorry to hear that :/
Sience you have access to recovery, did you try to wipe only cache partition and hit repair apps(also in recovery)?
I'm also using debloated device and i dont have any problems with it
nocio said:
Man, i'm so sorry to hear that :/
Sience you have access to recovery, did you try to wipe only cache partition and hit repair apps(also in recovery)?
I'm also using debloated device and i dont have any problems with it
Click to expand...
Click to collapse
Yeah...that's the first thing I tried after safe mode failed. :\
There's quite a few folks reporting similar issues since the last OTA update a couple weeks ago.
Usually I delay until I get a chance to restore then allow it...this one didn't even give me a chance. I was using my phone when it popped up. No option to remind me later. When I tried to exit it counted down from 10, rebooted and installed.
RiBBiTeDD said:
Yeah...that's the first thing I tried after safe mode failed. :\
There's quite a few folks reporting similar issues since the last OTA update a couple weeks ago.
Usually I delay until I get a chance to restore then allow it...this one didn't even give me a chance. I was using my phone when it popped up. No option to remind me later. When I tried to exit it counted down from 10, rebooted and installed.
Click to expand...
Click to collapse
I have one idea, it may seem unusual but it may work.
Try to remove sim card and than boot device
nocio said:
I have one idea, it may seem unusual but it may work.
Try to remove sim card and than boot device
Click to expand...
Click to collapse
Thanks for the idea. But, yeah, tried that to already...cleared cache and repaired apps afterwards too. Tried it with cable, tried a 2.0 cable too.
No dice.
The app repair works just fine and then it does the same thing when lock screen tries to appear.
RiBBiTeDD said:
Thanks for the idea. But, yeah, tried that to already...cleared cache and repaired apps afterwards too. Tried it with cable, tried a 2.0 cable too.
No dice.
The app repair works just fine and then it does the same thing when lock screen tries to appear.
Click to expand...
Click to collapse
Only thing that came to my mind is to download latest firmware for your device than flash it via odin
EDIT: but be carefull with that. Odin have box to untick factory reset but i didnt do that a loooooooooong time so i dont know if something is changed
nocio said:
Only thing that came to my mind is to download latest firmware for your device than flash it via odin
EDIT: but be carefull with that. Odin have box to untick factory reset but i didnt do that a loooooooooong time so i dont know if something is changed
Click to expand...
Click to collapse
Yeah, I figured that'd be my last shot at it... I've read the horror stories of tripping Knox even with factory firmware.
Was just really hoping there was some way to yank the stuff using recovery or download modes.
RiBBiTeDD said:
Yeah, I figured that'd be my last shot at it... I've read the horror stories of tripping Knox even with factory firmware.
Was just really hoping there was some way to yank the stuff using recovery or download modes.
Click to expand...
Click to collapse
I think that you can't trip Knox only when you flash official firmware over unlocked bootloader and custom ROM, but I'm not so sure.
Last time I did that is when I had Samsung Galaxy S2 and flashing official firmware over official firmware and that didn't trip the Knox counter
Does flashing genuine firmware trip knox?
Hi It's been a while since I bothered flashing firmware so I am not upto date with how things work now. My questions are I am currently on 02s version of firmware and would like to go samsungs version so I can take part in things like the one...
forum.xda-developers.com
Here you can see that flashing official firmware over official firmware(i'm guessing that you are not rooted) won't trip knox counter
nocio said:
Does flashing genuine firmware trip knox?
Hi It's been a while since I bothered flashing firmware so I am not upto date with how things work now. My questions are I am currently on 02s version of firmware and would like to go samsungs version so I can take part in things like the one...
forum.xda-developers.com
Here you can see that flashing official firmware over official firmware(i'm guessing that you are not rooted) won't trip knox counter
Click to expand...
Click to collapse
Awesome! Thank you!
I was able to get the files...for others in the same boat, here's a link to what worked for me:
Help finding correct firmware and installing for AT&T SM-G991U.
Hello all...I'm a fellow victim of the OTA updates screwing us debloaters currently stuck in a boot-loop. I'm trying to recover my the past several years text notes containing all the medical details for my son's illness. Details on that can be...
forum.xda-developers.com