Pink_bunny
Lurker
My current cellular carrier is AT&T (contract). The phone on my plan is a Samsung Galaxy S4. The original phone sizzled on the charger, frying the digitizer. The original phone was replaced via warranty and I still have both the new phone and the sizzled phone. The phone with the bad digitizer works, absent the black screen (it updates, connects to wifi, etc.). The problem is that for whatever reason, only Samsung knows, only some of my images, screenshots, and other data stored to the removable SD card on the original phone (even though I always had one in the old phone), and the others were stored to the internal 16GB onboard memory of the phone itself. When the poor thing first sizzled, I only had a swipe-up screen lock on and I had zero idea what an MHL adapter was or an OTG cable or I wouldn't need to post this ... but in my then profound ignorance, I called Advanced Tech Support at AT&T (huge error). Long story short, using Android Device Manager, the PIN was reset on the fried phone. Problem is that, even though it rings and/or changes from a 10 key input to alpha/numeric input, or even takes the messages I send through Google; the d#mn phone will not accept the correct PIN. (period)
I (now) know EVERY-SINGLE-POSSIBLE-WAY to get into a locked Android 4.4+ phone, even tried swapping screens to try to input the PIN -- I have done it all. (And I am very tech savvy -- with big screens, not these teeny screens lol). However, the information on this phone MUST be retrieved and I do not care how it happens, even if the warranty is voided in the process and I have to own both phones. The data is that important.
This is what I think I can do but I am not 100% sure, so alas: long-winded post here. I think that I need to remove the back housing from both phones (after SD, SIM, battery is out). I think I need to connect the screen cable from the fully functional phone to the broken phone. I think that I then need to have sdk running on my PC, with the correct path, etc. At this point, since usb debugging is NOT enabled on the broken phone, I think that I need to use the hardware method to boot the broken phone on the broken phone itself (now with visible screen to see menu and minus the OS required for the mhl adapter -- and PIN), using cwm to enable usb debugging from the boot menu. And from this point, I then use my PC to enter the correct code to the phone once it is recognized by sdk ... in order to bypass the PIN, etc.
Sorry so long. The part that I am most unsure of is how to enable usb debugging without the PIN on the broken phone. I also do not want to accidentally do a hard reset before I even have an image of the drive using sdk. The ONLY other thing I can think of is if it is possible to boot the mhl driver from the SD so the screen will work using HDMI, similar to choosing HDD boot order in dos on a PC but I really don't think that will work.
Yes, I know the code to accomplish this once usb debugging is enabled. I am not 100% sure about forum rules so if this needs to be answered off the board, that is fine. But yes, I own both phones.
Thank you in advance and kudos for completely reading the KitKat version of War and Peace
I (now) know EVERY-SINGLE-POSSIBLE-WAY to get into a locked Android 4.4+ phone, even tried swapping screens to try to input the PIN -- I have done it all. (And I am very tech savvy -- with big screens, not these teeny screens lol). However, the information on this phone MUST be retrieved and I do not care how it happens, even if the warranty is voided in the process and I have to own both phones. The data is that important.
This is what I think I can do but I am not 100% sure, so alas: long-winded post here. I think that I need to remove the back housing from both phones (after SD, SIM, battery is out). I think I need to connect the screen cable from the fully functional phone to the broken phone. I think that I then need to have sdk running on my PC, with the correct path, etc. At this point, since usb debugging is NOT enabled on the broken phone, I think that I need to use the hardware method to boot the broken phone on the broken phone itself (now with visible screen to see menu and minus the OS required for the mhl adapter -- and PIN), using cwm to enable usb debugging from the boot menu. And from this point, I then use my PC to enter the correct code to the phone once it is recognized by sdk ... in order to bypass the PIN, etc.
Sorry so long. The part that I am most unsure of is how to enable usb debugging without the PIN on the broken phone. I also do not want to accidentally do a hard reset before I even have an image of the drive using sdk. The ONLY other thing I can think of is if it is possible to boot the mhl driver from the SD so the screen will work using HDMI, similar to choosing HDD boot order in dos on a PC but I really don't think that will work.
Yes, I know the code to accomplish this once usb debugging is enabled. I am not 100% sure about forum rules so if this needs to be answered off the board, that is fine. But yes, I own both phones.
Thank you in advance and kudos for completely reading the KitKat version of War and Peace