My phone was working fine on Thursday morning. Around noon I went to check my phone and it was off. I turned it on and it gets stuck at the initial Samsung boot screen. With the research and testing I have done so far the current state of the phone is...
- Any attempt at normal boot results in getting stuck at the initial Samsung boot screen.
- I am NOT able to enter recovery mode by any method I've tried so far.
- I AM able to enter download mode by holding volume down or both volume buttons while inserting the USB cable.
- The phone DOES charge via USB.
- Connecting to the computer gives a "USB Device Not Recognized" error.
- I have tried cleaning the USB port with alcohol pads as best I can and it had no effect.
- ADB does NOT see the devices (and I know ADB/Drivers/USB Debugging/etc is configured correctly because I develop with this device)
- The phone is NOT rooted nor have I changed ANYTHING within the past few weeks.
- The device IS carrier unlocked (not that this should matter at all).
- The phone does have Google Voice with Groove IP Lite installed (and I remember news that the GV API would change around this time, maybe it broke something?)
- ODIN 3 v1.85 can SOMETIMES see the phone at 0:[COM3] (I'm still trying to figure this out. I THINK it only works if I put battery in, boot to download mode by inserting USB, then after it boots to download I remove and re-insert USB to re-connect the device on the computer, but I'm not certain yet)
I was going to replace the device next month anyways so I don't really care about the device itself. What I am trying to figure out is whether there is any way to recover certain data such as memo notes or game/app data from the device? If I tried to install a new rom via ODIN will that wipe out my app data and notes and stuff or would the data persist like it would for a carrier-pushed update? Can I somehow pull this data off the device from within download mode before I try to flash the device? Am I going in the wrong direction and should be trying something entirely different to begin with? What do you guys suggest? Thanks.
I was waiting to see if anyone else would pitch in with useful information about recovering your data. However, since no one has, I can say that I am pretty sure that you will not be able to recover anything currently in any of the system partitions. (System, kernel, data, preload, etc.) Once you recover your phone, you will still almost certainly have the information that was on your internal sdcard (USB Memory.)
Using Odin3, you should open Odin on the desktop of your pc first, then use the method that works for you to get into download mode, and Odin should recognize your phone.
I understand that you are not too concerned about the device. I would point out that a working I777 that is in good working condition with a clean esn is worth probably $100.00 to $125.00 on Swappa. It would be in your best interest to recover the phone. (Or if that's too much trouble, you can always send it to me, lol.)
Since the phone can enter download mode and be recognized by the computer, it is almost certainly recoverable. The only possible reason that it would not be recoverable is if the problem is due to damaged emmc memory in some part of the system partitions. When you flash the stock firmware, or any firmware, you will lose any possible access to the data partition. You will most likely be required to enter recovery after the flash to perform a wipe data/factory reset before the phone will boot into the system. The data will not persist as it would for an over the air or kies update. But again, as I said in the other thread, you may retain the game data if it is saved to the sdcard. Memo notes are definitely stored in the data partition, so those are lost.
The only thing you can do within download mode is flash firmware, nothing else is possible. I don't know of any other direction you could be going than what we have discussed so far.
As I said before, someone with good developer skills and understanding may be able to help, but as far as I know, no one with that level of skill hangs out in this forum, or has any interest in the I777 any more.
creepyncrawly said:
I was waiting to see if anyone else would pitch in with useful information about recovering your data. However, since no one has, I can say that I am pretty sure that you will not be able to recover anything currently in any of the system partitions. (System, kernel, data, preload, etc.) Once you recover your phone, you will still almost certainly have the information that was on your internal sdcard (USB Memory.)
Using Odin3, you should open Odin on the desktop of your pc first, then use the method that works for you to get into download mode, and Odin should recognize your phone.
I understand that you are not too concerned about the device. I would point out that a working I777 that is in good working condition with a clean esn is worth probably $100.00 to $125.00 on Swappa. It would be in your best interest to recover the phone. (Or if that's too much trouble, you can always send it to me, lol.)
Since the phone can enter download mode and be recognized by the computer, it is almost certainly recoverable. The only possible reason that it would not be recoverable is if the problem is due to damaged emmc memory in some part of the system partitions. When you flash the stock firmware, or any firmware, you will lose any possible access to the data partition. You will most likely be required to enter recovery after the flash to perform a wipe data/factory reset before the phone will boot into the system. The data will not persist as it would for an over the air or kies update. But again, as I said in the other thread, you may retain the game data if it is saved to the sdcard. Memo notes are definitely stored in the data partition, so those are lost.
The only thing you can do within download mode is flash firmware, nothing else is possible. I don't know of any other direction you could be going than what we have discussed so far.
As I said before, someone with good developer skills and understanding may be able to help, but as far as I know, no one with that level of skill hangs out in this forum, or has any interest in the I777 any more.
Click to expand...
Click to collapse
Yeah. It was worth a shot but I think I am out of luck on this.
I tried using Odin 3 v1.85 and also Odin 3 v3.09 from 2 separate computers with several cables in order to flash the PDA/AP from 'I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar.md5' but without any luck. After 10-20 minutes Odin says 'fail' and there is never any change on the phone screen at any point in the process. I also tried the 'I777UCKH7 OCD No BL.exe' one-click link from your signature links with a similar result. The program starts with factoryfs.img but the progress bar never moves and after 10-20 minutes it fails. The phone never shows any change at any point in the entire process.
I might be doing something wrong (perhaps with Odin I MUST flash the bootloader/phone/csc as well?) but it's looking more and more like the phone has a memory issue or something like that. Do you have any other suggestions? I'm willing to try anything at this point just to get the phone running for a few weeks while I decide on the next phone (hmmmm, Nexus 5, OnePlusOne, G3 or...)
Regardless of all that, thanks for all your help so far!
Both of those packages are complete in themselves. On the UCMD8 you only need the one tar in the PDA slot.
To discover if there is nand read/write corruption try this:
Instructions to clear nand read/write corruption. Instructions are specific. Do in order, and don't skip.
Odin3 v1.85 is recommended.
1) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning
2) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
3) If that is successful you are done. If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
For the record, no one writes those kinds of instructions as well as you do - both you and 4-2ndtwin have been great examples of how to help people for many years.
Thank you both for showing the rest of us how to convey help in an eloquent manner.
I tried your instructions with both v1.85 and v3.09 and although there was a brief glimmer of hope it looks like my device really is locked up beyond any further use. Odin shows the 'KERNEL' flash and the progress bar fills up in a second or two but then it goes to '<ID:0/003> NAND Write Start!!
' and like every other attempt it either hangs here indefinitely or fails after 10-20 minutes.
The only other things I can think of is to do a repartitioning or to physically disassembly the phone to look for any trouble spots (maybe a little dust or corrosion is shorting something) but of course being realistic there is virtually no chance of these having an effect.
I don't frequent the boards enough to know the standards here but I can say thank you for all the help you have provided. It's more than anyone can ask for such an old (but still good!) device.
Maybe it will take a jtag repair to get it going again, or perhaps there is actual eMMC damage, which can also be repaired. Whatever the problem is, a good option at this point would be the folks at Mobile Tech Videos repair shop. They have an excellent reputation here in the forum, and can do all sorts of repair.
Related
folks,
With the recent number of AT$T note users having Odin troubles, I decided to post up a few of the "known" problems that jam up the device. They are Brick level issues, and I decided to share them with you in a new thread.
The information is likely already out there, but spread far, and over many threads, so this will offer you a one stop fix you "NEED" to have, in the event you are restoring the SGH-I717 device to a factory state, and you find yourself seeing the download mode "limp mode" screen.
( this screen makes you think that download mode is gone, and no longer functions, but it does)...
Many users have the desire to return to stock, and in doing so, have encountered Severe Odin issues. This particular one, has caught several users in the last month, myself as well, and can catch even the seasoned Odin user by surprise.
Follow the steps below, and you will be okay....(I hope.)
(First) : When flashing a stock Odin .tar back to the SGH-I717, you "MUST" first go into your recovery...(CWM/TWRP) and factory reset the device. This will remove the data remnants that are often staying on the device.
(this can cause an immediate force close when the device boots from a good flash restore, and can corrupt your new shiney restored rom on pre-boot)
(Second): When pushing the stock rom .tar through Odin, "DO NOT" uncheck the "reset" toggle in ODIN !!!
this bypasses a critical write step in the restore process, and forces the device into download "limp" mode. Basically asking you to emergency restore using kies.
This is because the recovery is still being written to the device, even though Odin confirms the write step as a "PASSED". and the boot must occur to finish the process.
(Third): and possibly the most important step:
"DO NOT" attempt to multi-push Odin files back to back, by turning off the reset toggle in Odin.
You "MUST" ALLOW THE DEVICE TO BOOT, between .tar flashes. Again, the reset is a feature that finalizes the writing of the files to the device, and must remain "ON"...
Now, I realize that many PC environments are different, and each device also. Not to mention user skill levels, and what is being accomplished. But with the number of folks having flash issues using Odin lately, I simply wanted you to be aware of a few things that "WILL" jam you up.
And I'm certain that a few of these "bricks", needing a JTAG repair, were not true bricks. Instead, the download mode was still there, but was asking for a Kies emergency restore in the "limp mode" screen instead.
The screen is much different, showing a picture of a device, with an "X" between it, and a computer icon. Basically telling you that your flash failed, even though Odin shows a "PASSED" in the dialogue box.
Edit:
In the event of the download mode "limp", you will see an error screen asking you to go into kies for an emergency restore.
The kies restore is not needed. As you can start Odin again, and push the rom.tar to the device from this screen. (but you "MUST" remove the cable, then open Odin and load the .tar, then plug in the device and wait for the "COM" connection to show.
If Odin fails to push the .tar, "Then" go to Kies, and emergency restore the device using the super secret code.
Standard disclaimers apply, and mileage may vary...so do your homework.
hope this helps a few of you out......g
Nicely done, good sir.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Thanks G!
Bam....and another add to the GNote Super Page
[Road & Ref Map]: Galaxy Note Super Everything Thread (I717)
Thank you Joe ....
I hope this helps a few folks ...and slows down some of these problems we've been having .....g
What to do if we cannot get into recovery just download mode.
prettedda said:
What to do if we cannot get into recovery just download mode.
Click to expand...
Click to collapse
Flash.. then boot to recovery and factory rs... then reflash
Sent from my GT-N7000 using Tapatalk 2
Agreed.....g
I'm trying to use Odin to root a stock AT&T Galaxy Note i717 with Gingerbread. I can't get Odin to work. It keeps failing. Any ideas?
I've searched for hours for different solutions and have tried them all. I'm on my last leg, and I can't wrap my head around what is going on.
I'm running an S2 with ShoStock3 rom. It's been rooted for over a year now without any major hiccups at all. Last night, it froze on me. Usually when it does this, I just force-restart by holding the power button down until it cycles. Phone usually boots right back up, and I'm all set. This time it just stayed on the boot screen. For eternity. I let it sit like that for more than 45 min, and it never budged. Turn it off from the booth screen, it'll boot right back up. I can go into download mode, but not recovery, and every little trick I've tried works.
I've tried flashing new kernels with ODIN. Tried various recoveries, like Philz and even went as far as the one touch factory ROM and using the regular method for getting the stock ROM. Nothing. Maybe I'm doing something wrong. Most people who have this problem only recently added a new ROM or modified something. I haven't touched the ROM, kernel, etc. for over a year before this happened.
ODIN never makes it far when trying to flash anything. It depends on what is being flashed. It never gets past nand read/write. It never gets past boot.bin. It never gets past factory.img. Etc. Etc. I don't know if maybe something isn't going through between computer and phone, and that's why I'm not having success or what in the world is going on. Every tutorial or help I found confidently stated that all you have to do is flash this kernel, go to recovery, clear cache, and you're all set. But I feel like I'm the odd man out.
I'm afraid that this won't see much attentions, as the S2 is far from new, but like I said I am on my last leg. I just don't understand how it stops working from cycling power. I also don't understand how every attempt doesn't even scratch the surface. Any and all help will be greatly appreciated
The most basic step is to verify you're using the correct button combo to get into recovery: power+both volume keys, then release after the second Samsung logo.
SteveMurphy said:
The most basic step is to verify you're using the correct button combo to get into recovery: power+both volume keys, then release after the second Samsung logo.
Click to expand...
Click to collapse
^^ while the device is NOT USB connected to a computer.
Actually, you're lucky. This device is so popular, even though is it getting old, that there are still a handful of knowledgeable people hanging around.
You need to get into recovery. As Steve and Cyril have said, try the correct button combination, and post back here to verify that you are using the correct combo and that it will not go into recovery.
If you do get into recovery, perform a wipe data/factory reset and see if that gets your phone to boot into the system.
If you are unable to get into the recovery with the correct combo, then you may have one of several possible issues. The first possibility to troubleshoot is nand read/write corruption. Do the following:
Instructions to clear nand read/write corruption. Instructions are specific; do them in order, and don't skip.
Odin3 v1.85 is recommended.
1) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
2) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning
3) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
I have done the correct button combination for recovery, I promise you that. It brings up Samsung logo first, cuts off, and brings it up a second time, but releasing does nothing. I've tried it several times with different delays as well.
creepyncrawly said:
Instructions to clear nand read/write corruption. Instructions are specific; do them in order, and don't skip.
Odin3 v1.85 is recommended.
1) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
2) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning
3) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
Click to expand...
Click to collapse
I've actually tried this. On step one, it hangs up on "NAND Write Start!!", just like everything else that tries to get flashed.
To clarify, I should be flashing the I777 UCKH7 sbl.tar file, correct?
Luckily for me I qualified for a free upgrade from ATT for an S4, but I don't want to give up on this phone just yet. Especially with all of the data I have yet to recover from it.
XxArxAngelxX said:
I have done the correct button combination for recovery, I promise you that. It brings up Samsung logo first, cuts off, and brings it up a second time, but releasing does nothing. I've tried it several times with different delays as well.
I've actually tried this. On step one, it hangs up on "NAND Write Start!!", just like everything else that tries to get flashed.
To clarify, I should be flashing the I777 UCKH7 sbl.tar file, correct?
Luckily for me I qualified for a free upgrade from ATT for an S4, but I don't want to give up on this phone just yet. Especially with all of the data I have yet to recover from it.
Click to expand...
Click to collapse
Yes, that is the correct secondary boot loader.
Next, you must assume that there is a connection problem between the phone and the computer. The micro usb port, the cable, the usb port on the computer and the computer itself are all possible weak links in the connection. So try different cables, different ports on the computer, escpecially one directly connected to the mother board, even try a different computer. You can not proceed until you can get the phone to receive a flash and pass. A few people have even reported that they finally were able to complete a flash just by trying repeatedly over and over until it finally passed.
creepyncrawly said:
Yes, that is the correct secondary boot loader.
Next, you must assume that there is a connection problem between the phone and the computer. The micro usb port, the cable, the usb port on the computer and the computer itself are all possible weak links in the connection. So try different cables, different ports on the computer, escpecially one directly connected to the mother board, even try a different computer. You can not proceed until you can get the phone to receive a flash and pass. A few people have even reported that they finally were able to complete a flash just by trying repeatedly over and over until it finally passed.
Click to expand...
Click to collapse
Tried using different computer. Brand new cord. Multiple times tried. Different ports. I dunno, it's doing the same thing. It stops whenever it gets to NAND Write Start.
EDIT: Tried something I saw in another thread. Used stock binary with pit file. Never finished, so aborted it. Now phone doesn't come on at all for any reason whatsoever. -.- Pretty sure I fried it
Hi All,
I've had my original VRUAMDK S4 running Cyanogen since the day I got it, I never took an update and have always had a custom recovery. However, the phone's compass sensor has been wacky and I really need to flash back to a Samsung ROM for a few minutes to fix the compass.
However, I've just tried to use one of the "VRUAMDK No-Wipe" ROMs and bricked my phone, odin died almost immediately with a "Failed". I've seen that perhaps the no-wipe ROM is not going to work with a phone that already has custom recovery.. Problem is, I can't find a "true" image to actually restore VRUAMDK load.
Does anyone have a "full" image of the original Samsung Verizon S4 VRUAMDK they could post, that I can flash in Odin?
Update, I found the "SCH-I545_MDK_562219_Stock_Restore.tar.md5" which I'm hoping is right. It definitely gets further than before, but now every Odin flash fails at persdata.img.ext4.
Screen shows "stat [224,1440]".
Thoughts?
This will wipe out your phone entirely. It will be as if you bought a brand new MDK phone from Verizon that nobody has ever used. Please keep that in mind. Everything you've ever had on this phone will be wiped away and you will have no pictures, text messages, videos, emails, notes, programs, etc.
I downloaded it and double-checked that it's exactly the same one that I have, by file hash. You'll have to unzip it at least twice, maybe three times. I use 7zip for all of that.
SCH-I545_MDK_562219_Stock_Restore.tar.md5.gz
SCH-I545_MDK_562219_Stock_Restore.exe
Remember, you'll have a completely wiped phone. This is beyond a "factory reset". This is the closest thing to Samsung building a phone in the factory and then installing the operating system...you'll have nothing of yours on it. Whenever I've done this, I've taken out my microSD card. I don't think it touches it, but I do it anyway out of paranoia.
https://www.androidfilehost.com/?fid=22979706399755579
Here are some quick and dirty instructions I wrote for myself:
Jon8RFC's notes said:
1) Run SCH-I545_MDK_562219_Stock_Restore.exe with the s4 in "download mode" (reboot while holding the 'volume down' button, then press 'volume up' when prompted to continue)
This takes 17 minutes from start until initial phone setup is ready
2) Boot into the phone, sign into a google account
3) Go into settings and enable developer mode, then enable USB debugging
4) Run the RUN_ME.bat file in the ALL-IN-ONE folder
Click to expand...
Click to collapse
Steps 3 and 4 are if you want to re-root and unlock the bootloader with Loki. You'll need this:
http://forum.xda-developers.com/showthread.php?t=2301720
If you use TWRP, I suggest replacing the openrecovery.img with a more recent one, like TWRP 2.8.4.0 (2.8.5.0 for the i545 is no good), and rename it openrecovery.img in the folder where all of the files unzip to, in the same folder as the RUN_ME.bat. I think the one it comes with is 2.6.0.2 or something, because the tool is very old. I've swapped in 2.8.4.0 without a hitch, and then you're able to do a NANDROID backup of your MDK install and future installs...you can't NANDROID restore a 2.6.0.2 backup with 2.8.4.0, unfortunately. So, do it the updated way from the start.
http://dl.twrp.me/jfltevzw/
I'm not sure of the exact process you're following--files, programs, buttons pushed, etc. The ODIN I posted is a pretty simple set it and forget it kind of thing. Make sure your phone has enough of a charge since it likely will drain faster than your computer's USB port can output. I don't know what happens if an ODIN fails in the middle due to a power failure or USB disconnect...maybe nothing at all, but maybe a hard brick. Don't risk it, and charge up!
As for the error, that's a new one to me that I've never seen. I'm no expert. I did a quick search and some people suggested that using non-Samsung USB cables were the culprit for this particular error. Strange as it may be, my dinky, thin Samsung cable can deliver full power from the charger and a shorter, thicker gauge monoprice cable cannot. So, it's worth a shot if you have it, or try another cable.
Jon8RFC said:
It will be as if you bought a brand new MDK phone from Verizon that nobody has ever used. Please keep that in mind.
Click to expand...
Click to collapse
These are really great notes. And yep, that was absolutely my intent - get back to the original MDK status.
It was a 2-part problem. First, apparently Odin only half-works when you run it inside VMWare. I had to switch to a native Windows machine. Second, the USB cable.
Invisiblek posted a commit to CM that has fixed the compass issue. It's so nice to see the compass properly work again!!
Hello. I'm new to the mdk bootloader and want to preserve it. I'd like to know that I could Odin back to stock mdk rom with unlocked BL if I ever screw it up. Is the stock tar link and info still relevant to me? Would I also need jftlevxz mdk pit files for the partition?
Thanks much.
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))
Hi,
I’d really appreciate it if someone can help me, as I’ve not been able to find my exact problem and solution anywhere in the last 5 days of trying to fix my Samsung Galaxy S3 SPH-L710 – Sprint.
Not sure what happened but I had just swapped out my battery and my problem began – I have 3 batteries that I charge and swap when needed… one of the reasons I’m still using the S3. Been wanting to get a new phone but just haven’t decided which one and kept putting if off. Anyway… After charging the battery I turned on the phone and it got stuck on the Samsung Galaxy S3 screen. Went online and read I should try a cache wipe. I did that and got a bunch of failed to mount lines and a few other failures. Mostly failed cache. Not sure if this had anything to do with it but I was running low on the internal free space and had to delete a few things to make more space and then it would fill up again etc… Internal size is 16gb.
Here’s what I tried:
Attempted the 4.4.2 ROM flash in Odin. – Got a PIT partition message and then tried again and got write Failures after NAND started. Tried a few more times and same thing but I don’t get the PIT error anymore… I tried different Odin versions, computers, and cables, and same results. I have the correct USB driver. I’m using the same version ROM that’s on my phone, but the build name on my phone is last (newest) update and I could only find the previous build of the same 4.4.2 version. Note – This phone was a swap by Sprint when my first S3 had a start button issue. This one is a refurbished… not sure if that changes anything.
I also tried a TWRP install via Odin and it Failed.
I tried to Root via Odin and it Failed.
I DID NOT do a factory reset because I don’t want to lose all my data.
MORE INFO:
Phone is not Rooted and never was.
Phone goes into download mode and also stock recovery mode without any problems.
I never set the developer option and I didn’t enable debugging. Not sure how, now that my phone is soft-bricked.
QUESTIONS:
I’d like to preserve all my data and settings and somehow back them up so that I can put them on a reset phone.
Is there any way to work around this soft-brick and grab all the info including the system info and settings, all my files, and pictures, etc??… Everything! … I’d like to get the phone working again and put it all back on it and be the same as it was. I have so much important stuff on the phone. I have been doing backups via Kies but haven’t done it for a few months and I don’t even want to lose even a few months of data, and the way my phone was set up. Is there anything I can do to basically get a mirror image of my phone? Assuming all the information is still intact but it just can’t mount properly.
Is the developer / debugging setting preventing me from being able to do what I tried? Is it because I’m not Rooted? Is there OEM Locking on my phone?
Should I try to install TWRP from the stock recovery via external SD card? And then Backup from there? Is that different than doing it from Odin or will that fail too?
Please help – I love my S3. No phone for 5 days and I feel so disconnected :crying:
Thank you!