I'm trying to go back to stock after an AT&T OTA update bricked my wifes phone.
It just boots over and over over again. I followed the instructions to get into recovery mode, which it then asks for a password, I figured it was the pin code to get into the device. Problem is, after I enter the pin, it just starts doing its boot loop thing, over and over.
I can get the phone into download mode, and looking at ODIN, it appears it will take roms, but it will go back to the boot loop, and again recovery mode will ask for a password, which when giving the password it goes to boot loop mode again.
If I give it the wrong password it too many times it tells me its going to wipe the data.
I have been searching the forums all last night and part of the day at work today and I can't seem to find anyone who has had the same problem as me... either that, I'm having trouble articulating the correct syntax in the search menu to locate the problem.
I probably should have just took it into AT&T the next morning, but since they were closed I couldn't resist fiddling with it....
any ideas?
There was one other person who had that problem. I think his final solution was to go through the wrong password until the phone wiped and then he could use it. Found the thread for you here.
There might be another solution if that doesn't work.
creepyncrawly said:
There was one other person who had that problem. I think his final solution was to go through the wrong password until the phone wiped and then he could use it. Found the thread for you here.
There might be another solution if that doesn't work.
Click to expand...
Click to collapse
the gentlemen in the thread you posted had a device that was at least booting.
My device cannot even get that far.... I tried putting the incorrect code in to the recovery password field and it just goes back to reboot loop.
Thank you for the reply though.
I hope AT&T will take it back.
They probably will.
You might be able to completely reset the phone using the stock firmware package from sammobile.com (not the one available in our forums). It flashes everything, so the phone will be just like from the factory. See this post if you want to try it.
But that is somewhat risky, though should work. I have not tested the flash, of course. If it was my phone, I would probably try to exchange it under warranty.
being the daredevil I am, I went to that site and downloaded it and fired up odin... it comes back with an error on line 1874 such and such., then gives a fail flag.
I don't think they will let me return it. Because I think I already flashed a non-standard rom last night just trouble shooting this problem.
But thanks for the replies, maybe someone else will see this thread and have an idea.
I have seen many posts reporting returning a phone that was not stock, or still had the counter incremented, or one that would not boot. These users have stated that the person accepting the return did not even check the phone.
Of course, this is only anecdotal evidence, but it would be worth your time to try, especially if it is a store.
creepyncrawly said:
I have seen many posts reporting returning a phone that was not stock, or still had the counter incremented, or one that would not boot. These users have stated that the person accepting the return did not even check the phone.
Of course, this is only anecdotal evidence, but it would be worth your time to try, especially if it is a store.
Click to expand...
Click to collapse
+1, in my many exchanges and returns, not once has an employee powered the device on.
I'm kind of surprised stock recovery doesn't have a way to do a full wipe without a password...
Simba501 said:
+1, in my many exchanges and returns, not once has an employee powered the device on.
Click to expand...
Click to collapse
I'm going to try tonight after work.
yesterday I went to the local AT&T store and they claimed they couldn't help me because they don't handle warranty's and gave me directions to a store 20 miles away.
I don't know if he was just being a typical jerk or what, but I'll guess I'll find out tonight.
Well I do have one idea - it's possible in theory (but I've never successfully done it) to wipe /data in Odin/Heimdall.
(Last time I tried it, it bombed and I had to reformat - but that might get you out of this mess to have corrupted /data that requires a reformat.)
More later.
Related
Hey guys
1) Restarted my phone today using CM10.1 from a very recent nightly (within the past week).
2) On restart, phone froze and got kernel panic.
3) Restarted into CWM and tried to do a restore to an earlier backup I had made.
4) Half-way through the restore, I got ANOTHER kernel panic (never had that before)...
5) Only things I could do with the phone after that was enter download mode...nothing else...couldn't enter recovery mode anymore.
6) Went into download mode and flashed this CWM-Recovery (http://forum.xda-developers.com/showthread.php?t=1118693) and followed the instructions to the letter.
7) Odin 3.07 hung on NAND Write Start
8) Tried using Odin 1.3, and it seemed to flash correctly. It says completed no errors.
Phone will now not even start and is completely unresponsive...pressing any combination of buttons will not start the phone, and the phone is not recognized in Odin anymore...did I just hard brick it? Any other ideas?
Thanks,
Elliott
Service centre. Although if you can have someone who does JTAG's have a look at it to determine whether it can be JTAG'd without you giving them any money up front (I.E you only pay them if it can be JTAG'd), try that first.
Thanks that's what I thought.
Also, try a jig if you can get one. In all likelihood won't work, but stranger things have happened & you have nothing to lose.
Yeah thanks that's what I plan on doing. Any idea what I did wrong, though? I don't want it to happen again if I get it working with a jig.
Impossible to say. Not sure why you flashed that nondescript kernel/recovery in that situation tho given it probably wouldn't have worked even if the flash had been successful (You would probably have ended up with bootloop given recovery was obviously 'broken'). I would have flashed stock with Odin (And that's certainly what I tell people in your situation on here to do because it normally works).
But flashing recovery rather than a stock rom probably didn't break your phone, put it that way, so you didn't do anything 'wrong' per se. Just remember if you get into a similar situation again, go back to stock via Odin & start again (re-root your phone/restore a backup, flash your custom rom/kernel again, etc).
If the jig works (and don't get your hopes up or anything, we're talking a 1 in 10,000 chance, and that's probably being generous), flash stock with Odin (you wont have much choice).
Well...brought it to a JTAG specialist today and he couldn't fix it either...says it's very rare and he's had 5 out of 80 S2's like this happen without being able to fix them...
Bummer. Motherboard replacement in that case. If the phone's under warranty, take it to a service centre & say as little as possible. You might blag it for a warranty fix. No warranty ? You can still have a new motherboard put in by a service centre (more expensive option usually), or you can source a 2nd hand MB from a 'donor' phone (one with a broken screen that's otherwise OK, etc) & either swap it in yourself or pay a local mobile repair shop to do it (usually cheaper option).
@ OP By following what you flashed I noticed the date, we're talking about a 2 years old thread, a lot have changed since.
Not sure that was what bricked your device but I get that panic mode.
The other thing that it comes to mind is nand corruption, which has been quite common these days with people running custom.
I'm with bungle there, the best recovery package is going back to stock and start fresh.
I, on the other hand, wouldn't accept the situation you are on, I would spend a whole week trying to get that phone to boot again, whether a second opinion on a jtag, a new jig, another battery or any other thread on here at xda.
If the device gets hot near the rear camera and it won't even charge nor get warm around that area dismiss what I just said and proceed with the mobo replacement bungle suggested.
And of course, if you did something else to your device and didn't share it please, come clean so others don't freak out by reading this.
Sent from...this is not even my S2
Hey
Nothing else was done to the device...just what I stated exactly.
I caved today and bought a BNIB S3 because I couldn't go without a phone anymore...
Thanks for the help, guys
Elliott
Hello, This is my first Post on XDA so please help me to familiarize myself with rules and procedures and I apologize if I break any in any way.
Okay, So My phone (SM-G900T) is about 5 months old. I bought it in August, Without insurance (Terrible Idea), and now it is having problems. In the amount of time I've had it, I rooted it in mid to late September and used only an app called Xmod for a game. I then started using greenify, solid explorer and eventually used Xposed installer to try a few Xposed modules. Specifically I used, the YouTube adaway, Rich Pandora notification and that's about it. I also later installed Samsung Tools to backup my IMEI and important partitions.
A few days ago my phone randomly rebooted in the middle of a YouTube video so I let it reboot, but it rebooted again, and again, and again. I pulled the battery and turned it back on but the same problem persisted. I couldn't do anything to fix it so I just decided to factory reset the device through the stock recovery. Also, I did not install any custom roms or anything either. The factory reset did nothing. Now when I was in setup, everything force closed, froze and rebooted, repeatedly. So I found the original firmware that my phone came with and flashed it to my phone through Odin because I literally had no hope of what to do anymore. The problem lessened so I didn't install all my apps and overload the device as it would reboot when the RAM would get pretty full or too many things were running simultaneously in the background or foreground. The problem got a little worse so I factory reset one more time and it lessened again but now it came back and factory Resetting isn't lessening the problem. Now it just force closes a bunch of stuff and freezes and reboots into a bootloop midway through initial setup. I am desperate at this point right now and I need help from you guys. I don't have warranty because I rooted and I made the Extremely stupid decision of not getting insurance. So please can anyone help me out? I will be eternally grateful if you can help me turn this $609 brick into a phone again.
I will try to check this thread daily, but I go to school and I may not respond immediately, so please understand.
ahmed12534 said:
Hello, This is my first Post on XDA so please help me to familiarize myself with rules and procedures and I apologize if I break any in any way.
Okay, So My phone (SM-G900T) is about 5 months old. I bought it in August, Without insurance (Terrible Idea), and now it is having problems. In the amount of time I've had it, I rooted it in mid to late September and used only an app called Xmod for a game. I then started using greenify, solid explorer and eventually used Xposed installer to try a few Xposed modules. Specifically I used, the YouTube adaway, Rich Pandora notification and that's about it. I also later installed Samsung Tools to backup my IMEI and important partitions.
A few days ago my phone randomly rebooted in the middle of a YouTube video so I let it reboot, but it rebooted again, and again, and again. I pulled the battery and turned it back on but the same problem persisted. I couldn't do anything to fix it so I just decided to factory reset the device through the stock recovery. Also, I did not install any custom roms or anything either. The factory reset did nothing. Now when I was in setup, everything force closed, froze and rebooted, repeatedly. So I found the original firmware that my phone came with and flashed it to my phone through Odin because I literally had no hope of what to do anymore. The problem lessened so I didn't install all my apps and overload the device as it would reboot when the RAM would get pretty full or too many things were running simultaneously in the background or foreground. The problem got a little worse so I factory reset one more time and it lessened again but now it came back and factory Resetting isn't lessening the problem. Now it just force closes a bunch of stuff and freezes and reboots into a bootloop midway through initial setup. I am desperate at this point right now and I need help from you guys. I don't have warranty because I rooted and I made the Extremely stupid decision of not getting insurance. So please can anyone help me out? I will be eternally grateful if you can help me turn this $609 brick into a phone again.
I will try to check this thread daily, but I go to school and I may not respond immediately, so please understand.
Click to expand...
Click to collapse
Do you have SD card installed? If you do try taking it out and leave out or replace with another SdCard. Then flash the original stock firmware as you said you did before through (odin!) Then if that dont work try kias3 and use the emergency firmware recovery tool. Before you do any of this make sure you factory reset through stock recovery if possible.
Sent from my SM-G900T?
---------- Post added at 03:17 PM ---------- Previous post was at 03:07 PM ----------
Have you tried this tool? I had the same issue with my phone and reinstalled firmware and stock recovery through this tool and it stopped. If none of these tips work id say your phone may be borked or have faulty hardware. Take a look here as welll. Hope you can get your phone back to normal. I can understand what you're going through, like i said i had same issue with mine and mine has seems to be fine as of now. http://forum.xda-developers.com/showthread.php?t=2721146 . GOOD LUCK
Sent from my SM-G900T ?
beachbum40 said:
Do you have SD card installed? If you do try taking it out and leave out or replace with another SdCard. Then flash the original stock firmware as you said you did before through (odin!) Then if that dont work try kias3 and use the emergency firmware recovery tool. Before you do any of this make sure you factory reset through stock recovery if possible.
Sent from my SM-G900T?
---------- Post added at 03:17 PM ---------- Previous post was at 03:07 PM ----------
Have you tried this tool? I had the same issue with my phone and reinstalled firmware and stock recovery through this tool and it stopped. If none of these tips work id say your phone may be borked or have faulty hardware. Take a look here as welll. Hope you can get your phone back to normal. I can understand what you're going through, like i said i had same issue with mine and mine has seems to be fine as of now. http://forum.xda-developers.com/showthread.php?t=2721146 . GOOD LUCK
Sent from my SM-G900T ?
Click to expand...
Click to collapse
Okay, so I'm resetting it back to stock firmware through Odin as we speak. And yes, I had an SD card and have already taken it out and left it out and reset but still the problem has persisted, I will definitely try the solution you just mentioned, here I go. And thank you for replying...
Edit:
Hold on, which do you want me to try first? kias3(can you please link it if possible) with emergency firmware recovery tool? OR the Unified Android Toolkit?
Also... I don't exactly know how to use the toolkit, can you verify the steps to take to use the toolkit properly if I should use this solution? I'm sorry but I'm not very advanced at Android development, just intermediately experienced I suppose...
ahmed12534 said:
Okay, so I'm resetting it back to stock firmware through Odin as we speak. And yes, I had an SD card and have already taken it out and left it out and reset but still the problem has persisted, I will definitely try the solution you just mentioned, here I go. And thank you for replying...
Edit:
Hold on, which do you want me to try first? kias3(can you please link it if possible) with emergency firmware recovery tool? OR the Unified Android Toolkit?
Also... I don't exactly know how to use the toolkit, can you verify the steps to take to use the toolkit properly if I should use this solution? I'm sorry but I'm not very advanced at Android development, just intermediately experienced I suppose...
Click to expand...
Click to collapse
Try kies first that dont work try toolkit. Just Google how to use the toolkit it's pretty self explanatory but I don't think you'll need to use the tool kit anyways. http://www.sammobile.com/kies/
HOW TO USE RECOVERY TOOL IN KIES
http://forum.xda-developers.com/showthread.php?t=2261153&page=4
beachbum40 said:
Try kies first that dont work try toolkit. Just Google how to use the toolkit it's pretty self explanatory but I don't think you'll need to use the tool kit anyways. http://www.sammobile.com/kies/
HOW TO USE RECOVERY TOOL IN KIES
http://forum.xda-developers.com/showthread.php?t=2261153&page=4
Click to expand...
Click to collapse
okay, I tried resetting it using Kies3 but the device was not recognized so I had to find a different way because the guide on how to use Kies advised using Odin if Kies didn't recognize your phone. I don't have a code either, So I tried reflashing the stock firmware through Odin and it started up, froze and went into what I presume to be a bootloop as it is stuck on the T-Mobile splash screen with the notification light pulsing continuously. Did I also mention where my phone says Knox warranty void 0x1 there is another statement that says "Counter: 4" or something like that, while I am in download mode, does this have any significance? but yeah, other that Kies and Odin, I'm not sure if the android toolkit will help, because it's basically doing that same thing as I am with Odin, just more automated... Or am I wrong?
but as far as I know, that toolkit is literally the last option I have left, I guess I'll be trying that out tomorrow, with option 10 I believe where it says "10. Download, Extract + Flash Stock Firmware via Odin" but I'm not sure what ADB mode means... I can't really boot up the device so I don't know if that applies
Also, on a side note, how much do you think this will cost if I were to send the phone to Samsung and pay for repairs out of pocket, and do you think they could even repair it at all?
You know what... Do you think if I somehow installed CM12 on the device that the problem would fix itself? Because to me it seems like it's the Samsung software itself that is causing all this trouble along with a few Google apps. Now how would I root it and flash CM12 if it won't boot up fully...
Not sure if this would brick my phone either, let me know if it would if I tried to root through Odin and try to install CM12 through CWM recovery or something
Just throwing ideas, hoping this thread doesn't die before my problem is solved
Also, does geeksquad repair Samsung phones one time for a low fee if you've voided warranty?? If so then this could possibly be my final solution.
Also Never EVER buying a Samsung device again, they just aren't what they used to be back in the day, the other OEMs have caught up and left Samsung and their revenue in the dust...
ahmed12534 said:
Also Never EVER buying a Samsung device again, they just aren't what they used to be back in the day, the other OEMs have caught up and left Samsung and their revenue in the dust...
Click to expand...
Click to collapse
I disagree with this completely. Very few other handsets can hold a candle to the S5 or the Note 4. I don't know of anybody that has the problems you are describing with their phones without a hardware issue of some type or bad app. The Samsung software runs perfectly on millions of devices without the issues you're having. Therefore it's probably a bad app you've gotten a hold of, or you have a bad phone. CM12 will only introduce more issues and probably won't solve anything.
A stripped down custom rom might be a good bet because you can then start adding your apps back to find out where the issue is, or if it still has the same issues then it almost guarantees that there is some kind of a hardware issue.
So i'm helping a buddy out that was having an issue with several Note 2's that were purchased from a company that restricted their employees access to a lot of things on the phone. My friend handed a couple off to me. The first one was not passcode locked and it was a breeze (Basically just enabled USB Debugging). It is up and running. The other ones are passcode locked and when you try to go into wipe the data/factory reset from recovery it says "MDM does not allow factory reset". The Note 2 I'm having issues with in particular has a locked bootloader on KitKat 4.4.2 through Verizon.
I've spent almost literally every waking moment trying to find a way around this issue. I may have compounded it though. I discovered ODIN, flashed the stock firmware in the hopes that it would clear the phone. It did not (password was still in place). I then decided to flash the stock firmware with the .Pit file for an SCH-I605 and made sure re-partition was checked as well as erase nand. After the process completed successfully and the phone rebooted it will no longer boot beyond the Verizon screen. I still have access to recovery and download mode but in recovery its throwing out a bunch of command lines such as E:failed to mount /data etc. I've tried to reflash the stock firmware with and without the .pit file to no avail.
In the mean time I've tried to unlock the bootloader, attempted auto root, and install custom recoveries to see if I could some how get around the MDM issue. I've also attempted to install or flash from ADB and its still the same deal.
Anyway I'm tired, kind of exhausted, and not really sure what avenues I have left. That's where I'm hoping some of you guys come in. If you have any questions for me let me know and I'll try to shed some more light on it for you. Data DOES NOT matter to me so if you can think of anyway I can get this thing completely wiped out it so I can start from scratch it would be greatly appreciated, Thanks.
Is it just one phone with this problem or several? The mounting issues are becoming more common around here, and seem to be internal memory failure.
http://forum.xda-developers.com/note-2-verizon/help/stuck-boot-file-exists-t3286946
Droid_Nut said:
Is it just one phone with this problem or several? The mounting issues are becoming more common around here, and seem to be internal memory failure.
http://forum.xda-developers.com/note-2-verizon/help/stuck-boot-file-exists-t3286946
Click to expand...
Click to collapse
Well tonight I'll be getting my hands on a couple other test SCH-i605 phones that are in the same situation (Password locked and no ability to wipe from recovery) and I'll put them through the paces to see if I wind up with the same issue and get back with you on it.
The basic issue with this phone is just after trying that repartition with the pit file it doesn't want to boot beyond the verizon logo anymore and thats when it started throwing those errors in recovery. It could be a coincidence I guess.
I've been messing with Heimdall today to see if I could get a custom recovery flashed that way but the phone fails protocol initialization. The only thing I can get to flash to this phone is 4.4.2 and the i605 pit file through ODIN. Nothing else will budge.
I guess the question I really need answered, is there another way to wipe data/factory reset without the option in the stock Samsung recovery and no access beyond the lock screen?
What I have to work with is ODIN mode and whatever is in recovery that is not wipe data/factory reset.
So I did get my hands on a couple other phones with passcode locks that have the MDM lockout within the stock recovery that still fails to flash anything in Odin except the stock 4.4.2 firmware. So I can eliminate the idea its hardware. I have 4 phones here 3 of which have the same issue and the 4th I was lucky enough to not have a passcode. Quick fix to get MDM removed that way.
Again any ideas that are slightly more outside the box would be appreciated. Thanks.
Edit: If this helps the phone that is working that I manage to clean all of that stuff off of also throws the same error in ODIN with or without USB debugging so it leads me to believe there is something I'm actually missing... Time to go read more.
Well, sound like it is more than coincidence. Maybe you should contact Samsung and see if they can help?
Yeah I might do that. I'd just hope they have a one size fits all solution because I have about 600 to 1000 phones to tackle... Hahaha.
The conundrum here is that for the MDM company to release the lock on the phone I have to be able to get beyond the lock screen for the phone to process the request. To get beyond the lock screen I need the psswords that the previous company allowed their employees to put on the phones that for some odd reason they didn't have remove.
Anyway if I get this figured out i'll let you guys know how I got it. Thanks for the suggestion.
((deleted))
Long story short, stock phone just randomly blew up and I'm trying to re-install its stock Android OS. Phone has never been rooted before, it just started to reboot on its own and now I'm in a position where I can only access download mode.
I'm in Odin, with what I believe is the correct firmware for my device (SM-N950U1) and I just keep getting a "Secure Check Fail: system" when trying to flash. it via Odin. The Odin log says "FAIL! (auth) right after trying to write system.img.ext4 for a few minutes. The "Secure Check Fail: system" is the printout on the phone screen itself.
Any clues?
Bump! Anyone?
playbacktri said:
Bump! Anyone?
Click to expand...
Click to collapse
I see that you have not received an answer. That is upsetting. I am also struggling with this exact same issue on a g955u1. Have not found a solution. Did you end up solving your problem? If so, what did you have to do?
ap7x942 said:
I see that you have not received an answer. That is upsetting. I am also struggling with this exact same issue on a g955u1. Have not found a solution. Did you end up solving your problem? If so, what did you have to do?
Click to expand...
Click to collapse
Nope, I have not solved the problem. I've scoured the internet and other people asking the problem all have not had any answers either. My assumption is that the actual internal memory of the phone is corrupted and won't let me write past a certain point, or on certain sectors, or something and its not actually fixable via software. I think everyone else just stops at this point and its never resolved because there is no resolution hah.
Good luck, let me know if you ever figure it out...
playbacktri said:
Nope, I have not solved the problem. I've scoured the internet and other people asking the problem all have not had any answers either. My assumption is that the actual internal memory of the phone is corrupted and won't let me write past a certain point, or on certain sectors, or something and its not actually fixable via software. I think everyone else just stops at this point and its never resolved because there is no resolution hah.
Good luck, let me know if you ever figure it out...
Click to expand...
Click to collapse
This phone I am working on is for a customer of mine. Thankfully, they have given me an open ended time frame. I have been working on this for about a week trying to figure out whats going on.
The memory corruption thing you were talking about resonates with me, because prior to my customer bringing this in, they had attempted a couple factory resets trying to resolve the original issue which was all the system apps crashing. The phone would reboot like someone killed all the processes. Pretty much from the moment it reached the home screen, and it was not power related. The problem persisted after their factory resets within recovery mode. And then I hit the phone with Odin and ended up with a partial flash. Soft bricking the phone.
You saying that kinda reinforces what I was already thinking, that it might be a hardware issue. Im not sure.
5 minutes ago I was able to get odin to successfully flash BL, CP, and CSC. It even brought me back to the Samsung logo for a minute but hung there. That's the most success I have had with this thing. Ive flashed numerous firmwares and every single one of them fails on system.img.ext4. After it reboots, it boots directly into this altered version of download mode with an emergency recovery error.
I have flashed dozens of phones before without issue. This is the first time I have ever experienced this one. You could be right but I refuse to accept defeat in this case lol so im gonna keep trying and ill report back if I have success.
ap7x942 said:
This phone I am working on is for a customer of mine. Thankfully, they have given me an open ended time frame. I have been working on this for about a week trying to figure out whats going on.
The memory corruption thing you were talking about resonates with me, because prior to my customer bringing this in, they had attempted a couple factory resets trying to resolve the original issue which was all the system apps crashing. The phone would reboot like someone killed all the processes. Pretty much from the moment it reached the home screen, and it was not power related. The problem persisted after their factory resets within recovery mode. And then I hit the phone with Odin and ended up with a partial flash. Soft bricking the phone.
You saying that kinda reinforces what I was already thinking, that it might be a hardware issue. Im not sure.
5 minutes ago I was able to get odin to successfully flash BL, CP, and CSC. It even brought me back to the Samsung logo for a minute but hung there. That's the most success I have had with this thing. Ive flashed numerous firmwares and every single one of them fails on system.img.ext4. After it reboots, it boots directly into this altered version of download mode with an emergency recovery error.
I have flashed dozens of phones before without issue. This is the first time I have ever experienced this one. You could be right but I refuse to accept defeat in this case lol so im gonna keep trying and ill report back if I have success.
Click to expand...
Click to collapse
Man, that sounds very very familiar to mine. I don't know if you found my other threads where I was asking for help, but I woke up with a phone that wouldn't turn on. Finally found the key button combo to get it to soft reboot, then it would turn on and just crash in the middle of using it after anywhere from 30 seconds to 5 minutes. If i started to use the phone heavily it would just shut off instantly and reboot back up on its own.
After clearing the boot cache, then doing a factory reset, it finally just stopped turning on at all (just samsung boot logo loop)
So I hit it with odin, unsuccessfully for 2-3 days, and then out of nowhere it just finally took a successful flash. However, it still just bootlooped, so I did a factory reset again and it put it back to being toast.
Since then, not a single successful complete flash from odin. I too can do the BL, CSC and CP files but I can't flash the AP file as it is writing the most data and finally fails about 3-4 minutes into to writing the system image file.
Again...good luck, ha!
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