[Q] Need to backup Galaxy SII, but broken, locked screen - Galaxy S II Q&A, Help & Troubleshooting

Hello all.
As you might have guessed from the title, I recently broke my Galaxy SII's screen and I need to get all my precious info off it for my new S4 Active. Problem is, the screen is kept locked and with a broken screen I obviously can't unlock it in the normal manner. Fortunately the phone still works.
Unfortunately, my phone is unrooted and USB debugging is turned off (I think, I'm running on that assumption) so that doesn't help matters.
After some tinkering and learning (thanks to the sticky on recovery mode ) I have booted into recovery mode and have the Android SDK installed so while I can look at some things on the phone, not everything seems to be available.
Essentially, how can I get my data off my phone? It looks like I have to root the phone or something like that, but wouldn't that delete all my data (and thus defeat the purpose)?
Nothing like a broken screen to get you into learning Android development, and of course all responses are hugely appreciated

ArnoldJR28 said:
Hello all.
As you might have guessed from the title, I recently broke my Galaxy SII's screen and I need to get all my precious info off it for my new S4 Active. Problem is, the screen is kept locked and with a broken screen I obviously can't unlock it in the normal manner. Fortunately the phone still works.
Unfortunately, my phone is unrooted and USB debugging is turned off (I think, I'm running on that assumption) so that doesn't help matters.
After some tinkering and learning (thanks to the sticky on recovery mode ) I have booted into recovery mode and have the Android SDK installed so while I can look at some things on the phone, not everything seems to be available.
Essentially, how can I get my data off my phone? It looks like I have to root the phone or something like that, but wouldn't that delete all my data (and thus defeat the purpose)?
Nothing like a broken screen to get you into learning Android development, and of course all responses are hugely appreciated
Click to expand...
Click to collapse
It will depend on what data you're trying to get off the phone. My guess is photos/videos/music? If it's anything else, please specify.
You're on the right track, I'm pretty sure you'll need to root. But no, that won't delete any data My tip would be to root using Odin & Siyah kernel, as it's PC-based, if you were on JB 4.1.2 you'll need Siyah v6 (beta 4 or 5). The Odin link in my signature has a link which is an introduction to Odin flashing which you should find helpful. PC rooting with Odin (vs using Philz kernel) avoids using the busted screen for the rooting operation. Once you've flashed Siyah, you'll have root and a new custom recovery.
My next move would be to flash Dorimanx kernel, because it has an 'auto-mount' feature from recovery. Essentially that means the computer will recognise your internal SD (and external SD if you have one) as soon as you plug it in to your computer in recovery mode. To flash Dorimanx, you have a couple options. The easiest would be to download Dorimanx v8.43, and put it on a microSD card. Put that card in your phone, and from Siyah recovery, navigate to that file and flash it.
From there, reboot to your new recovery and plug into your computer. If all goes well then you can literally just copy your entire internal SD card to your computer and sift through for what you need
Hope that helps :highfive: Quote my post if you reply, else I won't notice it. I don't get time to go on Q&A much for now.
EDIT: Actually, an alternative would be not to flash Dorimanx on top of Siyah. From Siyah recovery, you could go: mounts & storage> mount USB storage and then plug into PC. Your PC should recognise it from there to copy all data from internal SD. If not, then flash Dorimanx for the auto mount feature.

hey.
my advice to you is to try using a "micro usb to hdmi" in most cases the touch works wile the screen does not.
its very common and cheep, i also suffered from the same problem, and i borrowed one from a friend, and thats what saved my data loss.
usually the phone interacts automatically with the usb-hdmi thing so you dont need to "click" on anything to make it work.
the touch tho is pretty tricky.. and you will learn it pretty fast!
hope one of your friends got one of these.. if not just buy one.. its a nice thing anyway.
hope i helped.

Hopper8 said:
It will depend on what data you're trying to get off the phone. My guess is photos/videos/music? If it's anything else, please specify.
You're on the right track, I'm pretty sure you'll need to root. But no, that won't delete any data My tip would be to root using Odin & Siyah kernel, as it's PC-based, if you were on JB 4.1.2 you'll need Siyah v6 (beta 4 or 5). The Odin link in my signature has a link which is an introduction to Odin flashing which you should find helpful. PC rooting with Odin (vs using Philz kernel) avoids using the busted screen for the rooting operation. Once you've flashed Siyah, you'll have root and a new custom recovery.
My next move would be to flash Dorimanx kernel, because it has an 'auto-mount' feature from recovery. Essentially that means the computer will recognise your internal SD (and external SD if you have one) as soon as you plug it in to your computer in recovery mode. To flash Dorimanx, you have a couple options. The easiest would be to download Dorimanx v8.43, and put it on a microSD card. Put that card in your phone, and from Siyah recovery, navigate to that file and flash it.
From there, reboot to your new recovery and plug into your computer. If all goes well then you can literally just copy your entire internal SD card to your computer and sift through for what you need
Hope that helps :highfive: Quote my post if you reply, else I won't notice it. I don't get time to go on Q&A much for now.
EDIT: Actually, an alternative would be not to flash Dorimanx on top of Siyah. From Siyah recovery, you could go: mounts & storage> mount USB storage and then plug into PC. Your PC should recognise it from there to copy all data from internal SD. If not, then flash Dorimanx for the auto mount feature.
Click to expand...
Click to collapse
I would like to get anything that's worth getting from the phone, so most important is the contacts and then photos/videos/app data.
It seems the link to download Odin is dead

Odin can be easily found with a Google search (or an XDA search). You're going to have to show at least a little bit of initiative if you want this done.
Edit - Also, you haven't specified which S2 variant you have. If you have any of the US variants, don't proceed with the above advice.
ArnoldJR28 said:
I would like to get anything that's worth getting from the phone, so most important is the contacts and then photos/videos/app data.
It seems the link to download Odin is dead
Click to expand...
Click to collapse

MistahBungle said:
Odin can be easily found with a Google search (or an XDA search). You're going to have to show at least a little bit of initiative if you want this done.
Edit - Also, you haven't specified which S2 variant you have. If you have any of the US variants, don't proceed with the above advice.
Click to expand...
Click to collapse
Just thought I'd make people aware of the dead link.
Phone variant is the I9100T (in Australia here).

Hopper's advice applies then.

ArnoldJR28 said:
I would like to get anything that's worth getting from the phone, so most important is the contacts and then photos/videos/app data.
It seems the link to download Odin is dead
Click to expand...
Click to collapse
I have no idea what you mean by the Odin link is dead. All links and attachments in my guide are up to date and working. I know, I just checked.
MistahBungle said:
Odin can be easily found with a Google search (or an XDA search). You're going to have to show at least a little bit of initiative if you want this done.
Edit - Also, you haven't specified which S2 variant you have. If you have any of the US variants, don't proceed with the above advice.
Click to expand...
Click to collapse
Good point, thanks. Had skimmed over the variant issue

Hopper8 said:
I have no idea what you mean by the Odin link is dead. All links and attachments in my guide are up to date and working. I know, I just checked.
Good point, thanks. Had skimmed over the variant issue
Click to expand...
Click to collapse
Not to worry, it was 404'ing for me, but I just went and googled it like Mistah said.
Flashing and pulling files from recovery mode worked like a charm so much appreciated, Hopper

ArnoldJR28 said:
Not to worry, it was 404'ing for me, but I just went and googled it like Mistah said.
Flashing and pulling files from recovery mode worked like a charm so much appreciated, Hopper
Click to expand...
Click to collapse
Good to hear it worked, and that you've got your data back :good: Now you know to keep regular backups of all the things you value, so get in that habit

Hopper8 said:
Good to hear it worked, and that you've got your data back :good: Now you know to keep regular backups of all the things you value, so get in that habit
Click to expand...
Click to collapse
Sorry to pester you but it seems I'm only halfway to the finish line. It looks like I only got some of my files and not others as when I "ls" folders in the shell like data, they're empty so I don't seem to have full access. Being Superuser doesn't let me see anything either.
Disregard, turns out all I had to do to see the contents of the /data folder was to mount it. The things you learn

Related

[Q] Force Close Loop. How can I fix this?

I haven't downloaded anything recently, I literally just picked up my phone after I woke up and I got a message saying "the application tasks provider has stopped working unexpectedly" and it gives me the option to force close. When I close it, a similar message pops up for email, messaging, social hub, tw launcher, facebook and it keeps going on and on without giving me a chance to use the phone. Do you guys know what I can do? I would be extremely grateful if you could help me out.

			
				
Bwahahahaa ;-) Gold.
Yes i've tried that. I've take the battery pack, memory card and sim card out, then replaced them but the loop keeps occuring. It's gotta be more of a software issue and that's why I need your help.
You haven't told us anything whatsoever about your setup/rom/kernel/etc. We're not mind readers
Try a factory reset in the first instance.
If you're running anything other than stock firmware, go back to stock firmware.
i recomendeed to change your rom..
i think that is a crush from your system, mate..
About 4 months ago I had exactly the same problem.
Is there Debugging-Mode enabled in you're phone?
Is you're phone rooted?
Try to take out only the SIM Card and then connect it to you're PC. Then turn the S2 on and try to backup all you're data.
If you're phone is rooted, try to boot up in CWM Recovery Mode and go to "advanced" and then "Fix Permissions". It shuold solve you're problem.
If you're phone isn't rooted, then you have to flash a stock or custom ROM.
MistahBungle said:
You haven't told us anything whatsoever about your setup/rom/kernel/etc. We're not mind readers
Try a factory reset in the first instance.
If you're running anything other than stock firmware, go back to stock firmware.
Click to expand...
Click to collapse
Sorry about that man, but I have no idea what my setup/rom/kernel is, don't even know what most of that means. The thing is I can't even go to the settings on my phone to check because the popups won't allow me to.
okries said:
i recomendeed to change your rom..
i think that is a crush from your system, mate..
Click to expand...
Click to collapse
I am an absolute and toal amateur, any advice at all of how to to that?
Dr.MacHack said:
About 4 months ago I had exactly the same problem.
Is there Debugging-Mode enabled in you're phone?
Is you're phone rooted?
Try to take out only the SIM Card and then connect it to you're PC. Then turn the S2 on and try to backup all you're data.
If you're phone is rooted, try to boot up in CWM Recovery Mode and go to "advanced" and then "Fix Permissions". It shuold solve you're problem.
If you're phone isn't rooted, then you have to flash a stock or custom ROM.
Click to expand...
Click to collapse
I know about technology but not like this. I have no idea what debugging mode/rooted or cwm recovery is. Any chance of explaining it to me in really, REALLY easy terms?
Sorry about my lack of knowledge guys, but I wholeheartedly appreciate you taking the time out to give me a hand.
1. Try wiping all data (fixed when i had the problem)
1. U need a kernel with CWM recovery (recommend siyah kernel)
2. Install with odin look on these forums for odin dont remember link
3. go to recovery (vol up+home button+power) and wipe data/cache (wipes everything apps, passwords, etc)
4. Try now if works click the thanks button
klawz said:
I know about technology but not like this. I have no idea what debugging mode/rooted or cwm recovery is. Any chance of explaining it to me in really, REALLY easy terms?
Click to expand...
Click to collapse
No problem man
Okay...when you have root permissions on youre phone you can write in system files and do other administrative work.
You can root youre phone by flashing a rooted kernel. The kernel is something like the heart of youre Android OS. You have to know some facts about youre S2, to root it successfully.
You have to know which Kernel version is installed at the moment. This information you can find in Settings -> About Phone -> Kernel Version (or something like that...my S2 is in German ). But when youre phone is bricked or youre system is damaged, its really hard or impossible to find out the kernel version. I think you won't be able to root it successfully :-(
So the only one possibillity to rescue youre S2 is, to flash a new firmware.

[Q] Destroyed memory partitioning. What do? [YP-G70]

Here's what happened:
-Had Eryigit GB​-Installed PA w/ mevordel's kernel 4.0​Rebooted recovery​Started weird bootloop=would go back into recovery and act like its installing something, then reboot, ad infinitum​
I tried reflashing Eryigits rom from odin,
then repartitioning. Somehow it was able to boot into Eryigit's ROM once, but the capacitative buttons didnt work and I couldnt reboot into anything except for download mode or a normal samsung logo bootloop.
I tried a few more things in Odin (not blindly, mind you) and still no go.. I can get it into recovery only if I flash a bootloader in Odin and auto-reboot it, otherwise it just goes back to the bootloop.
I believe I have the same problem as in this thread
I'm trying to adb into my device, but am having trouble detecting it. It'll connect in Odin fine, but not in adb, whether in download mode or just hanging at the samsung logo.
What can I do to fix this without adb working? I'm hoping for an odin fix for it, but through the mountains of threads I've been reading I don't believe there to be.
According to the thread above ^ it needs to be repartitioned manually... I read all the threads linked to and tried adb & heimdall but no luck after like 3+ weeks ):
Can anybody give me a better explanation of whats going on or throw me some troubleshooting advice?
<3 <3 <3
bmxer4130 said:
Here's what happened:
-Had Eryigit GB​-Installed PA w/ mevordel's kernel 4.0​Rebooted recovery​Started weird bootloop=would go back into recovery and act like its installing something, then reboot, ad infinitum​
I tried reflashing Eryigits rom from odin,
then repartitioning. Somehow it was able to boot into Eryigit's ROM once, but the capacitative buttons didnt work and I couldnt reboot into anything except for download mode or a normal samsung logo bootloop.
I tried a few more things in Odin (not blindly, mind you) and still no go.. I can get it into recovery only if I flash a bootloader in Odin and auto-reboot it, otherwise it just goes back to the bootloop.
I believe I have the same problem as in this thread
I'm trying to adb into my device, but am having trouble detecting it. It'll connect in Odin fine, but not in adb, whether in download mode or just hanging at the samsung logo.
What can I do to fix this without adb working? I'm hoping for an odin fix for it, but through the mountains of threads I've been reading I don't believe there to be.
According to the thread above ^ it needs to be repartitioned manually... I read all the threads linked to and tried adb & heimdall but no luck after like 3+ weeks ):
Can anybody give me a better explanation of whats going on or throw me some troubleshooting advice?
<3 <3 <3
Click to expand...
Click to collapse
If you are sure of what you state, solution is from post 39 at the following adress
http://forum.xda-developers.com/showthread.php?t=1676606&page=4
But check if you have a true "memory partitioning issue" best is said when wiping cache you get many advices about what is wrong (normaly in red letters!)
good luck and welcome to our club!
lolo9393 said:
If you are sure of what you state, solution is from post 39 at the following adress
http://forum.xda-developers.com/showthread.php?t=1676606&page=4
But check if you have a true "memory partitioning issue" best is said when wiping cache you get many advices about what is wrong (normaly in red letters!)
good luck and welcome to our club!
Click to expand...
Click to collapse
Hey thanks. I already read through all that stuff ^ and am not having much luck. Is there some way I can IM you or something? PM me if so. You seem very knowledgeable about this matter
bmxer4130 said:
Hey thanks. I already read through all that stuff ^ and am not having much luck. Is there some way I can IM you or something? PM me if so. You seem very knowledgeable about this matter
Click to expand...
Click to collapse
Normally we can solve this within a thread that can help any other getting the same issue.
i am still very involved because end 2011 I got in trouble (I was expecting to have much better performance by flashing a Gnote kernel !!!!) and stayed for months reading at XDA for a save. (also good english training then)
your Pb:
did you check by wiping if you are in this situation? You should get advice that (partition from n 14 and upper can't be read) if so follow the tracks from the relevant post and tell me what goes wrong with you.
I fixed it! you will do it the same!
PS:To enter Adb you should flash FIRST a kernel (with ODIN) rj14 for int'll version or entropy for US model
lolo9393 said:
Normally we can solve this within a thread that can help any other getting the same issue.
i am still very involved because end 2011 I got in trouble (I was expecting to have much better performance by flashing a Gnote kernel !!!!) and stayed for months reading at XDA for a save. (also good english training then)
your Pb:
did you check by wiping if you are in this situation? You should get advice that (partition from n 14 and upper can't be read) if so follow the tracks from the relevant post and tell me what goes wrong with you.
I fixed it! you will do it the same!
PS:To enter Adb you should flash FIRST a kernel (with ODIN) rj14 for int'll version or entropy for US model
Click to expand...
Click to collapse
Ok so I got into recovery with entropy's kernel and wiped everything,
When I try to mount usb storage it says:
E: Unable to write to ums lunfile (No such file or directory)
Click to expand...
Click to collapse
So yeah, its the internal memory.. now if i could just get adb shell to work right
okay now I'm just trying to adb shell into it from win7 x64 and fedora 18 linux with no luck. in win7 it shows up in adb devices, but i cant connect to it, right now im thinking its because of the java sdk and problems with the fact that its a 64 bit comp. in fedora adb devices says ???????????? offline usb:2-2...
bmxer4130 said:
okay now I'm just trying to adb shell into it from win7 x64 and fedora 18 linux with no luck. in win7 it shows up in adb devices, but i cant connect to it, right now im thinking its because of the java sdk and problems with the fact that its a 64 bit comp. in fedora adb devices says ???????????? offline usb:2-2...
Click to expand...
Click to collapse
So, you were able to flash entropy's kernel (said you have a US device?) Now you can go to recovery mode and enter adb call for;" adb devices" and your will and must show up. No need to mount anything. I 've never, under win7, tryied this. so no comment.
Would you mind to give me what is said after you do a single wipe because we have to be sure your problem is really a memory partition wreck.
lolo9393 said:
So, you were able to flash entropy's kernel (said you have a US device?) Now you can go to recovery mode and enter adb call for;" adb devices" and your will and must show up. No need to mount anything. I 've never, under win7, tryied this. so no comment.
Would you mind to give me what is said after you do a single wipe because we have to be sure your problem is really a memory partition wreck.
Click to expand...
Click to collapse
Ok, I was able to adb shell and rebuild the partition table, and it was indeed messed up, and I can mount usb storage, but I still can't get it to boot into any rom, and it refuses to boot into cwm recovery unless its just rebooted from odin. in recovery in the log it has an error about libc.so, idk if that has anything to do with it though. I'm beginning to think the problem may have to do with my usb cable. I accidentally switched the stock one with a Galaxy SII one, which should be fine, but maybe not.
bmxer4130 said:
Ok so I got into recovery with entropy's kernel and wiped everything,
When I try to mount usb storage it says:
So yeah, its the internal memory.. now if i could just get adb shell to work right
Click to expand...
Click to collapse
The "mount USB storage" option is for mounting the SD card on your computer. That error is because you don't have an external SD card inserted.
Mevordel said:
The "mount USB storage" option is for mounting the SD card on your computer. That error is because you don't have an external SD card inserted.
Click to expand...
Click to collapse
hehehe, I kinda realized that after posting. Derp.
But I think it may have to do with /data & maybe other folders/files being R/O (read only..) instead of R/W, as per this thread so I am now convinced I need the bootchain for the galaxy player, but this is just a sneaking suspicion, I need to do some more digging before making a fool of myself again
bmxer4130 said:
hehehe, I kinda realized that after posting. Derp.
But I think it may have to do with /data & maybe other folders/files being R/O (read only..) instead of R/W, as per this thread so I am now convinced I need the bootchain for the galaxy player, but this is just a sneaking suspicion, I need to do some more digging before making a fool of myself again
Click to expand...
Click to collapse
Ok you have all the needed stuff and now you are trained and skilled enough. You will succeed.
Why not you to try flashing Mevordel's GB Chip 1.5 rom that is in my view the best for your device, it is light simple and fast and no need for more for what we expect from this excellent but outdated product.
lolo9393 said:
Ok you have all the needed stuff and now you are trained and skilled enough. You will succeed.
Why not you to try flashing Mevordel's GB Chip 1.5 rom that is in my view the best for your device, it is light simple and fast and no need for more for what we expect from this excellent but outdated product.
Click to expand...
Click to collapse
Yes, I tried flashing it in cwm, along with eryigit (both with entropys kernel flashed over them) and PA venturi, but it refuses to boot properly. If it is the bootchain, how can I get a dump of a working one?
And I was able to dump a lot of stuff from [adb pull */*] and can access logs and dmesg, but havent inspected them fully. Is there an easy way to read the boot log and/or setup a custom log to run preboot? I figure that wouldnt be necessary since the linux kernel does a fine job of logging itself.
And yes I think I am skilled enough now, just was confused how to get to the adb shell, but I'm fairly well versed in linux, so the shell is relatively comfortable for me.
But if I'm able to figure it out I'm going to make a How To thread including what I've found and what you've found and posted to make it easier for nooblets in the future, maybe even make a simple shell script to repartition the US 8gb model.
I fixed it
how?
Jistropy said:
how?
Click to expand...
Click to collapse
Mainly luck hehe. But actually from the mentioned threads ^^^^^ and this nifty trick, but use caution as I have no clue how well this works for other devices, if it all. And a large part of the problem was that my battery was dead because it wasn't charging correctly when plugged into my computer; and it kept dying in Odin.
Do you have a similar problem?? I can probably help..

Samsung Galaxy Note II stuck at bootscreen [OS flashing?]

Well. It's my worst fear. Launched the DPI changer app, attempted to change my DPI (to a valid amount) and nothing happened, no big deal. My wireless connections stopped working and my shop stopped working. I downloaded a different DPI changer, everything was working except Google Play. I attempted everything then decided to tell it to "change" my DPI to default. Went to reboot then bam.
I get the following:
The standard splash with the Verizon 4GLite then it goes on to loop at the Samsung splash for a bit then loops from the beginning (4GLite).
I've tried getting into "recovery" mode but it won't go, I do not know why. (Vol up + home + power). Need help please, thanks.
(Noob alert, if you mention anything that I might need, if you could please supply a DL link to minimize any more mess ups I might make)
EDIT: I got into recovery mode I forgot you were able to remove the battery (I was panicking, I apologize) I am also rooted with 4.2
EDIT2: I've attempted a factory reset, nothing new happened.
EDIT3: I need to reflash an OS. I'm really freaking out. It says I don't have a bootloader (OS).
Bottom line: This problem kinda... multiplied itself most likely based on my own stupidity. I'm keeping it at the "Team Win Recovery Project v2.5.0.0" recovery menu because I don't even want to boot into anything. Awaiting instructions.
Solkrieg said:
Well. It's my worst fear. Launched the DPI changer app, attempted to change my DPI (to a valid amount) and nothing happened, no big deal. My wireless connections stopped working and my shop stopped working. I downloaded a different DPI changer, everything was working except Google Play. I attempted everything then decided to tell it to "change" my DPI to default. Went to reboot then bam.
I get the following:
The standard splash with the Verizon 4GLite then it goes on to loop at the Samsung splash for a bit then loops from the beginning (4GLite).
I've tried getting into "recovery" mode but it won't go, I do not know why. (Vol up + home + power). Need help please, thanks.
(Noob alert, if you mention anything that I might need, if you could please supply a DL link to minimize any more mess ups I might make)
EDIT: I got into recovery mode I forgot you were able to remove the battery (I was panicking, I apologize) I am also rooted with 4.2
EDIT2: I've attempted a factory reset, nothing new happened.
EDIT3: I need to reflash an OS. I'm really freaking out. It says I don't have a bootloader (OS).
Bottom line: This problem kinda... multiplied itself most likely based on my own stupidity. I'm keeping it at the "Team Win Recovery Project v2.5.0.0" recovery menu because I don't even want to boot into anything. Awaiting instructions.
Click to expand...
Click to collapse
I saw you posted this in the att forums but I think I can help. Just download any ROM and flash it. Twrp has a failsafe now that will basically prevent you from bricking your phone if no os is detected. Do you have an external memory card? If you do transfer a ROM to your card, put it in your device, and flash it. Your not bricked.....your just soft bricked. Or you can always go back to stock. I'm sure your device thread has instructions on how to Odin back to stock. Hope this helps
Sent from my SGH-I317 using xda premium
roughneckboren said:
I saw you posted this in the att forums but I think I can help. Just download any ROM and flash it. Twrp has a failsafe now that will basically prevent you from bricking your phone if no os is detected. Do you have an external memory card? If you do transfer a ROM to your card, put it in your device, and flash it. Your not bricked.....your just soft bricked. Or you can always go back to stock. I'm sure your device thread has instructions on how to Odin back to stock. Hope this helps
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
So if I wanted to flash stock, I just need to put the stock rom on my ESD put it into my phone and flash it from the recovery menu? Is there more to it than that? Or do I need to do that all externally with "Odin"? Where would I obtain the stock rom? And thank you for your response.
Solkrieg said:
So if I wanted to flash stock, I just need to put the stock rom on my ESD put it into my phone and flash it from the recovery menu? Is there more to it than that? Or do I need to do that all externally with "Odin"? Where would I obtain the stock rom? And thank you for your response.
Click to expand...
Click to collapse
I'm talking a touchwiz ROM one of your developers has made. You can find it in your forums. It sounds like you don't have much experience with this stuff. Did you make a nandroid backup at all?
Sent from my SGH-I317 using xda premium
roughneckboren said:
I'm talking a touchwiz ROM one of your developers has made. You can find it in your forums. It sounds like you don't have much experience with this stuff. Did you make a nandroid backup at all?
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
Sadly, no. I didn't. You are correct, I am very new to this sort of thing, I've rooted other devices before (simple one click only, I'm good with computers, but not smart phones) but nothing has blown up this bad before. I've placed this rom (http://forum.xda-developers.com/showthread.php?t=2261478) on my ESD however, when I put my ESD back in, it reads it as blank. I'm assuming I need to relaunch recover mode to refresh its directories. However I'm very scared to do that because I have no OS anymore.
Solkrieg said:
Sadly, no. I didn't. You are correct, I am very new to this sort of thing, I've rooted other devices before (simple one click only, I'm good with computers, but not smart phones) but nothing has blown up this bad before. I've placed this rom (http://forum.xda-developers.com/showthread.php?t=2261478) on my ESD however, when I put my ESD back in, it reads it as blank. I'm assuming I need to relaunch recover mode to refresh its directories. However I'm very scared to do that because I have no OS anymore.
Click to expand...
Click to collapse
Just navigate in your recovery back to your internal SD then back to your external. If that does not work then go to the reboot menu in TWRP and and hit recovery. It will restart your recovery only and should refresh what is sees on your external card. If that does not work go to mount and make sure external SD is ticked in the settings, if not then tick it, Reboot recovery again. If still that doesnt work then go to Advanced, file manager, and navigate to your external SD (if you can) and find the file you downloaded, pick the zip file and move it to your internal SD. Then flash it. Regardless of any of these steps if you can find the .zip file flash it. Then reboot. Hope that helps you. You should be able to reboot to recovery any time you need to regardless of no OS. Please keep your phone charging during this whole process. If this works then make a nandroid backup in Twrp.
---------- Post added at 03:43 AM ---------- Previous post was at 03:40 AM ----------
roughneckboren said:
Just navigate in your recovery back to your internal SD then back to your external. If that does not work then go to the reboot menu in TWRP and and hit recovery. It will restart your recovery only and should refresh what is sees on your external card. If that does not work go to mount and make sure external SD is ticked in the settings, if not then tick it, Reboot recovery again. If still that doesnt work then go to Advanced, file manager, and navigate to your external SD (if you can) and find the file you downloaded, pick the zip file and move it to your internal SD. Then flash it. Regardless of any of these steps if you can find the .zip file flash it. Then reboot. Hope that helps you. You should be able to reboot to recovery any time you need to regardless of no OS. Please keep your phone charging during this whole process. If this works then make a nandroid backup in Twrp.
Click to expand...
Click to collapse
Edit- If none of this works then you'll probably have to adb sideload your phone to transfer the rom to your internal SD card. Otherwise you can ODIN back to 100% stock which involves a huge download and you'll have to reroot your phone. If you don't know how to ODIN to stock then get on youtube and there are plenty of videos to help you along. The basis for the note 2 (att, verizon, sprint,....) should all be the same just a different file to download.
roughneckboren said:
Just navigate in your recovery back to your internal SD then back to your external. If that does not work then go to the reboot menu in TWRP and and hit recovery. It will restart your recovery only and should refresh what is sees on your external card. If that does not work go to mount and make sure external SD is ticked in the settings, if not then tick it, Reboot recovery again. If still that doesnt work then go to Advanced, file manager, and navigate to your external SD (if you can) and find the file you downloaded, pick the zip file and move it to your internal SD. Then flash it. Regardless of any of these steps if you can find the .zip file flash it. Then reboot. Hope that helps you. You should be able to reboot to recovery any time you need to regardless of no OS. Please keep your phone charging during this whole process. If this works then make a nandroid backup in Twrp.
---------- Post added at 03:43 AM ---------- Previous post was at 03:40 AM ----------
Edit- If none of this works then you'll probably have to adb sideload your phone to transfer the rom to your internal SD card. Otherwise you can ODIN back to 100% stock which involves a huge download and you'll have to reroot your phone. If you don't know how to ODIN to stock then get on youtube and there are plenty of videos to help you along. The basis for the note 2 (att, verizon, sprint,....) should all be the same just a different file to download.
Click to expand...
Click to collapse
I rebooted into recovery. I only hesitated because it warned me I didn't have an OS. That worked, I saw the ROM and am now flashing it. I will edit and let you know if all works.
EDIT: It worked, thank you so much for your time and effort! I'm sure it's a pain dealing with noobies, I hope this helps people in the future since it's very friendly to beginners. I hope to not come back to this thread and say something isn't working properly.
Solkrieg said:
I rebooted into recovery. I only hesitated because it warned me I didn't have an OS. That worked, I saw the ROM and am now flashing it. I will edit and let you know if all works.
Click to expand...
Click to collapse
Please do.
ROOTBOXED!
roughneckboren said:
Please do.
ROOTBOXED!
Click to expand...
Click to collapse
It worked, thank you so much for your time and effort! I'm sure it's a pain dealing with noobies, I hope this helps people in the future since it's very friendly to beginners. I hope to not come back to this thread and say something isn't working properly.
Solkrieg said:
It worked, thank you so much for your time and effort! I'm sure it's a pain dealing with noobies, I hope this helps people in the future since it's very friendly to beginners. I hope to not come back to this thread and say something isn't working properly.
Click to expand...
Click to collapse
No problem man. Not everyone here is a butthole. Its not a pain because I was there once too. Just make sure you run a backup in twrp. You can name it too! Just practice and read around. Watch YouTube videos (I learn by visual)
And I keep my backups on PC in case a memory card goes bad. If you wipe system in recovery make sure you flash a ROM because system is obviously your OS and twrp prevents it from booting and bricking your device. Good choice on the recovery. :thumbup:
If it will at least boot to something there's always hope. be sure to hit the thanks button. It always helps. Glad to have gotten you up and running. If you need more help just pm me.
ROOTBOXED!

Trouble with ADB installation and rooting

Hi, I've spent literally 5 hours today just trying to figure out what flashing is, rooting is, and how to install ADB/SDK drivers, but still no idea what flashing and rooting are (trying to unlock my phone). I've looked at so many guides, but I came across this one that seemed to work for me to install ADB/SDK tool http://forum.xda-developers.com/show....php?t=2199526. What I'm trying to do is basically root my phone which is a samsung galaxy s2 GT-i9100 4.1.2, I have no idea what Ice cream sandwich or that jelly bean thing is, this is pretty much my first smartphone, i've never really needed a phone. Now I'm trying to root with this guide here http://forum.xda-developers.com/show....php?t=1994544 since I have no SD card, but here's the thing, even when I go to recovery mode, and then apply update from ADB, I then open up the ADB cmd and type adb devices, nothing comes up, I don't understand why my phone won't show up? I still try the sideload command but it says cannot read CWM-SuperSU-v0.97.zip. So what I'm trying to say is, I am a complete noob at what everyone here is specialized in lol, so can anyone explain it to me?
Also, yes I have read the newbies Q&A threads and the other introduction threads, but I mean, this is the help section, so I should be able to get help right?
First of buy an sd card "there cheap" then put philz kernel on it and then update that zip in recovery. "Root done and cwm installed " search philz thread for right kernel. Look for what you have installed. You say its 4.1.2 that's jellybean. Now look in settings,about phone and look for something like lsw or lss and such and flash kernel that fits your details. If not sure post your details. main thing is to read lots and lots and lots about what mite go wrong. All well thinking yay I can root but what happens if it gos wrong? Study lots about what your going to do. Reading is easy fixing is not.
andrewwright said:
First of buy an sd card "there cheap" then put philz kernel on it and then update that zip in recovery. "Root done and cwm installed " search philz thread for right kernel. Look for what you have installed. You say its 4.1.2 that's jellybean. Now look in settings,about phone and look for something like lsw or lss and such and flash kernel that fits your details. If not sure post your details. main thing is to read lots and lots and lots about what mite go wrong. All well thinking yay I can root but what happens if it gos wrong? Study lots about what your going to do. Reading is easy fixing is not.
Click to expand...
Click to collapse
Thanks for the reply, but I understand that doing this come's with a lot of risks, I've already encountered a problem lol (everytime I turn on phone color is inverted). Right now I don't have an sd card available that's why I'm trying the ADB solution. I'll post my details since I'm not sure what step to take from here.
What I've done:
Installed ADB
On phone, checked USB debugging
(I've also tried using exynosabuse, but that didn't work)
What's wrong:
From what I think, I havent applied ADB updates (I think thats what they are) to my phone, because I connect my phone to my pc and it does not show up in devices manager with a yellow exclamation mark. So this doesn't let ADB detect my phone which isn't letting me apply the CWM-SuperSU-v0.97.zip. in stock recovery.
My details:
Kernel version 3.0.31-889555
[email protected] #3
SMP PREEMPT
Build number JZO54k.I9100XWLSM
Baseband version I9100BVLS4
Edit: I just found out that when I place my phone in download mode, and then connect it to the pc, I check device manager and I finally get the yellow exclamation mark. Now I'm really not sure what step to take, do I update the device with a yellow exclamation mark? If so with what drivers? I also know about odin now, but I need to be able to have odin recognize my phone, and then know which kernel is right for me.
SwifterZ said:
Hi, I've spent literally 5 hours today just trying to figure out what flashing is, rooting is, and how to install ADB/SDK drivers, but still no idea what flashing and rooting are (trying to unlock my phone). I've looked at so many guides, but I came across this one that seemed to work for me to install ADB/SDK tool http://forum.xda-developers.com/show....php?t=2199526. What I'm trying to do is basically root my phone which is a samsung galaxy s2 GT-i9100 4.1.2, I have no idea what Ice cream sandwich or that jelly bean thing is, this is pretty much my first smartphone, i've never really needed a phone. Now I'm trying to root with this guide here http://forum.xda-developers.com/show....php?t=1994544 since I have no SD card, but here's the thing, even when I go to recovery mode, and then apply update from ADB, I then open up the ADB cmd and type adb devices, nothing comes up, I don't understand why my phone won't show up? I still try the sideload command but it says cannot read CWM-SuperSU-v0.97.zip. So what I'm trying to say is, I am a complete noob at what everyone here is specialized in lol, so can anyone explain it to me?
Also, yes I have read the newbies Q&A threads and the other introduction threads, but I mean, this is the help section, so I should be able to get help right?
Click to expand...
Click to collapse
i have this pbm too
What you have done is a lot risk involved get an SD card. Check with app on play store cuz I think you have rooted it. Dose it boot to recovery now? Did you install cwm recovery? Do as I said and all will be good. Flash lsw philz kernel. What is it you want to do with your phone? Flash custom ROM??
andrewwright said:
What you have done is a lot risk involved get an SD card. Check with app on play store cuz I think you have rooted it. Dose it boot to recovery now? Did you install cwm recovery? Do as I said and all will be good. Flash lsw philz kernel. What is it you want to do with your phone? Flash custom ROM??
Click to expand...
Click to collapse
I checked with the GalaxSim Unlock app and my phone isn't rooted, and from what I think I have done, I haven't rooted at all. From the beginning it already was able to boot to recovery, by recovery you mean holding vol up + menu + power. I do not remember installing cwm recovery at any point. All I want to do with my phone is root it, so that I can unlock it.
You can use Odin?. Flash philz tar kernel lsw. Why hadn't you read how to do this? Its so simple to do I don't get it.
andrewwright said:
You can use Odin?. Flash philz tar kernel lsw. Why hadn't you read how to do this? Its so simple to do I don't get it.
Click to expand...
Click to collapse
I already said! When I open up Odin, it does not detect my phone! I don't know why.
An observation; you've made this process so much more difficult for yourself than you need to. Trying to use ADB to do what you're attempting to do is like killing a solitary microbe with Tsar Bomba (Google it).
Buy an SD card like I said. There like £2 for a 2gb card now!! Done helping now cuz your not helping your self. Seriously buy an SD card and you rooted in max ten mins. Risk is pretty much nil.
andrewwright said:
Buy an SD card like I said. There like £2 for a 2gb card now!! Done helping now cuz your not helping your self. Seriously buy an SD card and you rooted in max ten mins. Risk is pretty much nil.
Click to expand...
Click to collapse
Alright, lol thanks man i'll get one. Quick question though, my phone is automatically making the color inverted when i turn it on after a couple of seconds, i'm not pressing the home button 4 times or anything, it just automatically does it. Anyway i can fix this? or will it fix itself when i root the phone since i'll be changing the kernel? Also what kernel do I get?
Philz kernel lsw . inverted colours I have no clue about what's going on there but rooting it won't fix that. Check in settings. What have you changed/installed?
andrewwright said:
Philz kernel lsw . inverted colours I have no clue about what's going on there but rooting it won't fix that. Check in settings. What have you changed/installed?
Click to expand...
Click to collapse
All I installed since I started this is GalaxSim Unlock, ExynosAbuse, checked USB debugging, went into stock recovery but didn't do anything so turned off phone, went into download mode but didn't do anything so turned off phone. That's pretty much it. Will resetting my phone fix this? I really don't need anything on the phone, I can just reset it, but i'll do it if you say its safe.
Your not on 4.0.4 so yes its safe to factory reset.
andrewwright said:
Your not on 4.0.4 so yes its safe to factory reset.
Click to expand...
Click to collapse
Alright awesome thank you so much for your help.
Andrew, you said to get the lsw philz kernel, so I searched it up in the forums, and found this:
<< 03.06.2013 - PhilZ-cwm6 v5.06.1 with CWM 6.0.3.2 based recovery >>
DVLSH (i9100T) - XWLSS - XWLST - XWLSW - DXLSD - XXLSQ (i9100P) - ZSLSJ (fixed for bootloop)
http://d-h.st/users/philz_touch/?fld_id=16062#files
Should I download that? That was the only download that has LSW in the name in the list of kernels.
Yes lsw. Get signed zip put on ext SD or tar for Odin.if you have SD now put philz on ext SD card "a must" go to recovery and just update it. Reboot and your rooted. If boot loop factory reset then reboot. If your going with Odin get tar and flash away.
MistahBungle said:
Trying to use ADB to do what you're attempting to do is like killing a solitary microbe with Tsar Bomba (Google it).
Click to expand...
Click to collapse
:laugh: Good comparison! (I actually googled it.)
immortalneo said:
:laugh: Good comparison! (I actually googled it.)
Click to expand...
Click to collapse
You know I never even see that post till now Lol. Is a good way of putting it haha
BTW how you doing immortalneo? Did you get what you wanted from all that studying or you waiting for results? Hope you do well:thumbup::thumbup:
andrewwright said:
You know I never even see that post till now Lol. Is a good way of putting it haha
BTW how you doing immortalneo? Did you get what you wanted from all that studying or you waiting for results? Hope you do well:thumbup::thumbup:
Click to expand...
Click to collapse
Am doing great! Results have come, and I've got admission in a good college for my post graduation in Oral Medicine & Radiology!! :good:
Good to see you guys again!

Samsung S3 memory full

My work colleague is an idiot - Despite warnings from his S3 that phone memory was low he continued taking videos and pictures and he has no sd card in the phone. Now the phone boots up but the pattern unlock screen is unresponsive. I offered to try to help him as he said "The last 2 years photos of my life are on there" so clearly a factory reset will lose them all so that's not an option.
So I installed Kies, thinking I'll just grab them to my PC for him - but alas no. MTP USB driver installation fails every time and yes I've googled my socks off, tried all the regedit fixes, even tried installing Win 7 32 bit on a spare hard drive.
I've checked that the ribbon connector for the screen is attached, tried linux boot disks that don't see the phone and now I'm all out of ideas. Any help would be vastly appreciated :fingers-crossed:
Hello,
Welcome to XDA.
Most of the time the screen being locked wont let PC interact with the device. There are many different models of S3, give me your model number and I'll guide you to where you can find answers.
You may can flash a custom recovery or a temporary recovery(not sure because I don't know what is available for the model you're working with and what isn't), if you can get one of those recoveries then you may can use the factory reset in recovery(it wont wipe his photos) or adb to get the phone working.
Remember to create an XDA account so you can post and reply in the forums.
Droidriven said:
Hello,
Welcome to XDA.
Most of the time the screen being locked wont let PC interact with the device. There are many different models of S3, give me your model number and I'll guide you to where you can find answers.
Click to expand...
Click to collapse
Hi there and many thanks for the welcome. The model number is GT-19300 :fingers-crossed:
Azarameus said:
Hi there and many thanks for the welcome. The model number is GT-19300 :fingers-crossed:
Click to expand...
Click to collapse
Your issue is unusual because of how it got that way, I'm not certain exactly which subforum or thread you need but I will link you to the GT I9300 Main Forum linked below:
http://forum.xda-developers.com/galaxy-s3
You can check through the subforums there for anything you think applies, the Q&A and the 2 development subforums are most likely where you will find help, this thread will be moved to the GT I9300 Q&A forum linked below:
http://forum.xda-developers.com/galaxy-s3/help
If you get replies you can check them and respond there, you might want to find some off topic threads to post in until you have at least 10 posts so that you can post in the development forums there if you need to, there is a 10 post minimum before you can post there. Good luck.
Droidriven said:
Your issue is unusual because of how it got that way, I'm not certain exactly which subforum or thread you need but I will link you to the GT I9300 Main Forum linked below:
http://forum.xda-developers.com/galaxy-s3
You can check through the subforums there for anything you think applies, the Q&A and the 2 development subforums are most likely where you will find help, this thread will be moved to the GT I9300 Q&A forum linked below:
http://forum.xda-developers.com/galaxy-s3/help
If you get replies you can check them and respond there, you might want to find some off topic threads to post in until you have at least 10 posts so that you can post in the development forums there if you need to, there is a 10 post minimum before you can post there. Good luck.
Click to expand...
Click to collapse
Ok thanks again. I can get it into Recovery mode but all I've tried so far is clearing the cache, as I don't want to do anything that might lose his pictures.
Azarameus said:
Ok thanks again. I can get it into Recovery mode but all I've tried so far is clearing the cache, as I don't want to do anything that might lose his pictures.
Click to expand...
Click to collapse
If it is stock recovery then I believe if you can get to download mode then you can flash a custom recovery and flash the superSU zip to root the device then factory reset/wipe data, wipe cache and wipe dalvik cache, this will clear the lockscreen but won't erase his pictures, music, etc., it may let him back into his phone, he will just have to be careful because the device will be rooted and he could make things worse if he doesn't know what he's doing. If that works and he gets back in his phone but isn't comfortable with the risk of having a rooted device without understanding its usage then the device can be un rooted by going into the superSU settings and choosing the unroot and uninstall option. He'd still have custom recovery though. You might even be able to just flash the recovery to do the wipes and not have to root, I'm not sure about that though because I've never used recovery without root so I can't speak from personal experience.
I've never owned the i9300 so I'm not sure if you can do that or not safely from the state you are in so you may want to verify in this forum before you try it, but I don't see an issue with you doing it, its commonly used to root the S3 variants and doesn't wipe any important data or factory reset the device
Sent from my SCH-I535 using Tapatalk
Droidriven said:
If it is stock recovery then I believe if you can get to download mode then you can flash a custom recovery and flash the superSU zip to root the device then factory reset/wipe data, wipe cache and wipe dalvik cache, this will clear the lockscreen but won't erase his pictures, music, etc., it may let him back into his phone, he will just have to be careful because the device will be rooted and he could make things worse if he doesn't know what he's doing. If that works and he gets back in his phone but isn't comfortable with the risk of having a rooted device without understanding its usage then the device can be un rooted by going into the superSU settings and choosing the unroot and uninstall option. He'd still have custom recovery though. You might even be able to just flash the recovery to do the wipes and not have to root, I'm not sure about that though because I've never used recovery without root so I can't speak from personal experience.
I've never owned the i9300 so I'm not sure if you can do that or not safely from the state you are in so you may want to verify in this forum before you try it, but I don't see an issue with you doing it, its commonly used to root the S3 variants and doesn't wipe any important data or factory reset the device
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Whew, most of that went right over my head lol. An idiot's guide please? Bearing in mind that my PC can't currently connect to the phone I'm guessing that I need to put the custom recovery file (where to find one?) on an SD card via a PC card reader and try it from there in download mode? I think he'll be delighted just to get his pictures and videos back even if the phone never works again, so it being rooted won't be an issue.
Azarameus said:
Whew, most of that went right over my head lol. An idiot's guide please? Bearing in mind that my PC can't currently connect to the phone I'm guessing that I need to put the custom recovery file (where to find one?) on an SD card via a PC card reader and try it from there in download mode? I think he'll be delighted just to get his pictures and videos back even if the phone never works again, so it being rooted won't be an issue.
Click to expand...
Click to collapse
No, to get to download mode you need to have the phone off, then press and hold the volume down+home+power button, when you see the caution screen you press up, if you can get to this mode you may can flash a TWRP recovery through Odin from PC to phone.
But first, before we get to Odin, do you or he know what android version he had before this happened, Kit Kat? Lollipop? I need to see if there are locked bootloaders on your device builds and which ones they are and which are safe to flash TWRP, if the i9300 is like some of the other Samsung devices with certain locked bootloaders that can't be unlocked or downgraded then flashing TWRP could and probably would brick the device. I need some info so I can check for you.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
No, to get to download mode you need to have the phone off, then press and hold the volume down+home+power button, when you see the caution screen you press up, if you can get to this mode you may can flash a TWRP recovery through Odin from PC to phone.
But first, before we get to Odin, do you or he know what android version he had before this happened, Kit Kat? Lollipop? I need to see if there are locked bootloaders on your device builds and which ones they are and which are safe to flash TWRP, if the i9300 is like some of the other Samsung devices with certain locked bootloaders that can't be unlocked or downgraded then flashing TWRP could and probably would brick the device. I need some info so I can check for you.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I honestly have no idea which android build it is running on, as I can't get into the settings page or anything else and I very much doubt if my friend knows as he is pretty much clueless on such things, hence the problem. All I know is that its a few years old and when it starts up there is a three.co.uk white screen icon before it gets to the unresponsive lockscreen. I am also almost as clueless with android devices (I'm only a PC guy) - so far my only experience has been to set up kodi with addons for TV viewing which is why I came here to ask you expert guys
Methinks I won't try to get into download mode just yet in case it makes things worse
All your help is much appreciated, thank you!
Azarameus said:
I honestly have no idea which android build it is running on, as I can't get into the settings page or anything else and I very much doubt if my friend knows as he is pretty much clueless on such things, hence the problem. All I know is that its a few years old and when it starts up there is a three.co.uk white screen icon before it gets to the unresponsive lockscreen. I am also almost as clueless with android devices (I'm only a PC guy) - so far my only experience has been to set up kodi with addons for TV viewing which is why I came here to ask you expert guys
Methinks I won't try to get into download mode just yet in case it makes things worse
All your help is much appreciated, thank you!
Click to expand...
Click to collapse
The device was never updated, it never had stock upgrades? If not then I can narrow down what was on it, when was the device bought?
If you can boot to download mode and if it is recognized in Odin then you've got a chance, at the moment your PC isn't recognizing the phone but if it successfully connects to Odin then you've got a chance, otherwise I'm not sure what success you'll have.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
The device was never updated, it never had stock upgrades? If not then I can narrow down what was on it, when was the device bought?
If you can boot to download mode and if it is recognized in Odin then you've got a chance, at the moment your PC isn't recognizing the phone but if it successfully connects to Odin then you've got a chance, otherwise I'm not sure what success you'll have.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I would put a spare miniSD card in, flash TWRP recovery in odin, access the storage from there and copy the files to the SD card. Easy as pie.
The international version of the S3 (GT-i9300) already has an unlocked bootloader. So no problem there.
Important to note is that if the device is not rooted the TWRP recovery won't "stick" when the device is allowed to reboot automatically after the odin flash. So in odin you have to UNTICK(!) the reboot option and after flash reboot directly to recovery via holding Vol UP + Home + Power for about 7 sec.
Droidriven said:
The device was never updated, it never had stock upgrades? If not then I can narrow down what was on it, when was the device bought?
If you can boot to download mode and if it is recognized in Odin then you've got a chance, at the moment your PC isn't recognizing the phone but if it successfully connects to Odin then you've got a chance, otherwise I'm not sure what success you'll have.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I showed him this thread at work earlier and although he growled somewhat at being called an idiot in my OP, he had to agree he was lol. It turns out he bought his partner the same phone around the same time so I checked and it has Automatic upgrades ticked and is on build 4.3 so we can hopefully assume the problematic one is on the same version. When I mentioned the possibility of bricking to him he became unsure as to whether I should proceed with flashing. If he was to send the phone to Samsung themselves would they be able to retrieve his data safely, albeit with some cost and waiting?
Thanks again for your input
Hawaiihemd said:
I would put a spare miniSD card in, flash TWRP recovery in odin, access the storage from there and copy the files to the SD card. Easy as pie.
The international version of the S3 (GT-i9300) already has an unlocked bootloader. So no problem there.
Important to note is that if the device is not rooted the TWRP recovery won't "stick" when the device is allowed to reboot automatically after the odin flash. So in odin you have to UNTICK(!) the reboot option and after flash reboot directly to recovery via holding Vol UP + Home + Power for about 7 sec.
Click to expand...
Click to collapse
That sounds good - all he wants is his files back safely. It certainly isn't rooted. So once that is done and I'm back in recovery mode how do I get out of there, just reboot it from there?
Thanks for the help, it is much appreciated
Azarameus said:
That sounds good - all he wants is his files back safely. It certainly isn't rooted. So once that is done and I'm back in recovery mode how do I get out of there, just reboot it from there?
Thanks for the help, it is much appreciated
Click to expand...
Click to collapse
Yes, after you copied the files via the "File Manager" in TWRP you simply choose "reboot system". Rebooting to system will automatically restore the original recovery you are used to. Or you can choose to shutdown in TWRP, remove the SDcard "safely" first and then reboot.
Even more: After you copied all the photos/videos from internal storage (which should be under /storage/sdcard0/DCIM/camera) to SDcard you could simply delete a few of those.
If them taking up too much space is the problem for the lockscreen not working, deleting a few would of course free up some space again, which would then most likely make the lockscreen work again.
But let me make one thing clear: Flashing anything always brings with it the slight(!) possibility something could go wrong, because you are writing to the EMMC of the phone. BUT I can't imagine a samsung staff member doing anything different. He/she would also need to gain access somehow...
After all it's your choice but hundreds of people (including me) have used odin and twrp on different devices for years now without any problem whatsoever. :good:
--- Edit ---
Ah one more thing. I would definitely make a full backup (System/Data, EFS and bootloader) while I'm at it! You just choose "backup" in twrp, then the "MicroSD card" under "storage" and go from there. Pretty self explanatory. Never hurts to have a backup!
Hawaiihemd said:
Yes, after you copied the files via the "File Manager" in TWRP you simply choose "reboot system". Rebooting to system will automatically restore the original recovery you are used to. Or you can choose to shutdown in TWRP, remove the SDcard "safely" first and then reboot.
Even more: After you copied all the photos/videos from internal storage (which should be under /storage/sdcard0/DCIM/camera) to SDcard you could simply delete a few of those.
If them taking up too much space is the problem for the lockscreen not working, deleting a few would of course free up some space again, which would then most likely make the lockscreen work again.
But let me make one thing clear: Flashing anything always brings with it the slight(!) possibility something could go wrong, because you are writing to the EMMC of the phone. BUT I can't imagine a samsung staff member doing anything different. He/she would also need to gain access somehow...
After all it's your choice but hundreds of people (including me) have used odin and twrp on different devices for years now without any problem whatsoever. :good:
--- Edit ---
Ah one more thing. I would definitely make a full backup (System/Data, EFS and bootloader) while I'm at it! You just choose "backup" in twrp, then the "MicroSD card" under "storage" and go from there. Pretty self explanatory. Never hurts to have a backup!
Click to expand...
Click to collapse
Ok thanks again. I am going to attempt this tonight, will update on any progress
Azarameus said:
Ok thanks again. I am going to attempt this tonight, will update on any progress
Click to expand...
Click to collapse
Well, that worked! My idiot friend is happy now. Thanks a million for the help - you guys ROCK!
Azarameus said:
Well, that worked! My idiot friend is happy now. Thanks a million for the help - you guys ROCK!
Click to expand...
Click to collapse
Nice! And were you able to get the lockscreen working again?
Hawaiihemd said:
Nice! And were you able to get the lockscreen working again?
Click to expand...
Click to collapse
Yes indeed, all is working now as it should. The village idiot actually danced off to his car when I returned his phone - he has strict orders from me to move all his stuff to the SD card and make regular backups to his PC!
Thanks again - would never have done it without you guys

Categories

Resources