Related
I need some help XDA. I don't know if you'll help or not, but I'm law enforcement and I need to access a locked Droid X. None of the forensic solutions available support bypassing the lock code and I don't have access to the Gmail password for this phone.
What I was looking for is a way to flash the phone with a rooted recovery image that would not overwrite the user data on the phone, so that I could recover the contents of the phone. I've looked at several different options including adb/custom recovery images but it looks like I need to access the USB debugging mode to root the phone.
Can this be done and if so how. Is someone out there willing to help me with building a custom recovery image that doesn't overwrite or dump the user data?
maybe im oversimplifying this but have you tried just plugging it in to the computer? my x will automatically connect as a usb drive and allow me to access the files on the sd card, obviously this wont help if you are wanting call logs or txt messages unless they backed them up to the sd card, just a suggestion before custom recovery
xsurferx, I have tried that and the only thing I get is the phone will charge. In device manager the phone is recognized as a Motorola MB810 USB device.
There is no way to access the device available through Windows Explorer.
My bet is that the person who took the time to ensure that privacy is more important than convience ( deny data connect from usb, wipe sdcard, and strong enough password/encryption) has looked further into other routes aswell. But I don't know of any kind of flashable that would both preserve data and reset the lock screen. The phone is probably one of the best suited to not devulging its information. It would probably be easier to get a court order for the cell records. But I wish you luck.
Dispatched at the Speed of Light from my XOOM
If you're trying to access the SD card, take it out and use a SD card reader on a computer and should be able to fix permissions that way? Maybe....
Sent from my DROIDX using XDA App
Thanks chbennet, I've already retrieved the cell phone records from the provider (via Search Warrant) and examined the victim's phone in this case. But as always I'd also like to have all of the evidence including the suspect's phone contents. I already have the SD card contents.
There has to be a way similar to the iPhone to restore the system data to default while keeping the user data (call logs, SMS, Images, video, browser history, etc.) in tact.
The iPhone does this by creating a system partition and a user partition. Is this the same in Android phones? Or is it one partition and directories?
I'd still like to see if there is someone that could build a ROM flash that would disable the passcode.
If it is rooted, there was probably a nandroid backup on the card. If there was, this might help.
http://androidforums.com/evo-4g-all-things-root/319602-read-copy-contents-nandroid-backups.html
Dispatched at the Speed of Light from my XOOM
so my lovely G2 had a personality split.. sorta. as you can see from the attached image its done for. however, the bottom part (with the battery) still may work, even though its without the screen. when i plug it into my computer though, nothing happens. but nothing happened when i plugged it in when it was not broken either, its only when i set it to the USB storage device is when the PC recognized it.
i really would like to get a bunch of **** off this phone if possible. i had a lot of stuff on the SD card (including a bunch of apps that were installed/moved on the card), but all my texts and such are on the phone.
is there a way to get that stuff of the phone, through some debugging software maybe? also, the apps that are on the sd card, how would i put them on the whatever new phone i get? they're not with the .apk extension.
thanks guys for any help
Hey sell me it or something I want that front part so bad.
Sent from my Energized Amaze 4G
Or My Sexy Nexus 7
Yes girls know about XDA
you can thank a girl on here
how did u do that? take a look at the instruction how to change the display maybe you get forward with it
xbleem said:
how did u do that? take a look at the instruction how to change the display maybe you get forward with it
Click to expand...
Click to collapse
i was thinking of swapping the display, but don't want to risk buying one and then it not working anyway due to the damage elsewhere on the phone. i think i'll just buy another g2. love the ergonomics of it. got a galaxy s3 as a replacement and can't stand it. way too huge for me and the design is awful.
Anything on the sd card you can grab with a USB reader and a PC.
All your other goodies will be in your /data directory. If you have a recent CWM backup, you can grab the data off of there. It will be data.img and probably in a yaffs or ext3/4 format.
Otherwise, you could try booting into recovery or fastboot to see if you can get adb access, in which case, you can pull the data manually.
If it doesn't boot because there is no screen, you could try replacing/reattaching the ribbon cable to get it to boot long enough to pull data.
Lastly, I thought there was limited jtag info for the G2, so that might be a last ditch effort.
gee one said:
Anything on the sd card you can grab with a USB reader and a PC.
All your other goodies will be in your /data directory. If you have a recent CWM backup, you can grab the data off of there. It will be data.img and probably in a yaffs or ext3/4 format.
Otherwise, you could try booting into recovery or fastboot to see if you can get adb access, in which case, you can pull the data manually.
If it doesn't boot because there is no screen, you could try replacing/reattaching the ribbon cable to get it to boot long enough to pull data.
Lastly, I thought there was limited jtag info for the G2, so that might be a last ditch effort.
Click to expand...
Click to collapse
thank you. i will fiddle with that this weekend.
what is the jtag info you're referring to?
It's a protocol from communicating wiht the chips directly- it's usually used to unbrick android devices, but I don't recall too much info for the g2, other than someone posted a pict of some of the jtag ports.
If you have a recent cwm backup, that will probably be the easiest way to recover. As a matter of fact, I did that just now. I upgraded to jellybean, but in a moment of noobness, I wiped data before backing up the two files that have to be backed up manually (mileage.db and wpa_supplicant.conf). A little command line hacking and everything is right in the world.
gee one said:
Anything on the sd card you can grab with a USB reader and a PC.
All your other goodies will be in your /data directory. If you have a recent CWM backup, you can grab the data off of there. It will be data.img and probably in a yaffs or ext3/4 format.
Otherwise, you could try booting into recovery or fastboot to see if you can get adb access, in which case, you can pull the data manually.
If it doesn't boot because there is no screen, you could try replacing/reattaching the ribbon cable to get it to boot long enough to pull data.
Lastly, I thought there was limited jtag info for the G2, so that might be a last ditch effort.
Click to expand...
Click to collapse
If you have a friend with another G2, you could probably mimic button presses in order to do a nandroid backup (then extract the /data image).
Failing that, I'm sure someone on here could give you the exact button press count to do what you need to.
the thing is guys, i'm not very good with adb. i found a few videos online on how to do a screen portion swap along with the rails. and i'm going to bid on a G2 on ebay. i'll swap the screen and rails from the one i buy to my G2. see if that works, then probably just sell the unused portion of the other G2. i will hook up my G2 to adb though tomorrow. i have to install it when i get home. anyone know the link to the adb download?
what kind of OS do you have? It's much easier in linux, if you know linux.
There might be a link to a binary, but this will get you going with adb.
https://developer.android.com/sdk/index.html
You don't need to update everything - just the SDK platform tools.
So how bad is it? What type of data are you trying to save? Most of it will probably be on the SD card. Do you have a clockwork mod backup?
-
I have not done this before and have not tested this method, do this at your own risk!!!
We've made it to the XDA Portal! (link below)
http://www.xda-developers.com/android/fix-your-soft-bricked-galaxy-s-iii-samsungs-way/
Hi,
A few months ago I hard bricked my Galaxy S II into an unfixable situation the only fix being replacing the motherboard. More info: HERE
While looking for a fix I encountered this thread: HERE
This thread contained a leaked confidential file from Samsung on how to fix a Bricked Galaxy S III. It wasn't relevant to me then because I didn't have a S3, but now as an owner of a S3 I find this may be very useful and may save lots of money if & when needed.
Brief Description of the fix:
Copying the Bootloader file to an external SD Card, using a normal GT-I9300.
Inserting the external SD card into the bricked phone, and copying the bootloader file to the defective PBA.
After downloading the bootloader file to the defective phone, entering download mode with the phone, and downloading a Full S/W.(PIT, PDA, CSC, PHONE files)
Description of the files attached to this post:
(12-38)_GT-I9300_BRICKED.pdf.zip - This ZIP file Contains a PDF file that is the manual for the fix.
GT-I9300_Boot_Recovery.tar - This TAR file is the Bootloader that is copied to the external SD card.
Odin3v3.07.rar - The program specified in the manual that copies the bootloader onto the external SD card.
GT_I9300_unbrick_sdcard_head.zip - The BIN file used in Rebellos's method below.
Requirements:
Odin3 v3.07.exe and Odin3.ini
GT-I9300_Boot_Recovery.tar
(12-38)_GT-I9300_BRICKED.pdf.zip
External SD Card (Memory size should be 2GB or bigger.)
One normal I9300 phone(normally booted on)
*Resistor has to be shorted very carefully, avoiding touching any other parts at all cost. If you short too many things together - possibility of frying some component of your I9300 rises drastically.
No one has yet to report trying this fix and it being successful, but I am confident that if preformed according to the instructions this fix has the potential of fixing almost any bricked GS3.
One Little Problem:
Scenario: I bricked my phone and I want to fix it as mentioned in this thread. So I go ahead and look at the requirements:
I download it from the attachments.
I download it from the attachments.
I download it from the attachments.
I don't have one so I go buy one from a store for a little amount of money.
[*]Ummmm... I have one but it can't boot... Damn! I don't have any friends that own one.... Damn! What should I do?!
Buy a new one so I can use it to fix the old one :silly:
Take my bricked phone to a store and pay at least 60$ for a fix.
Follow the instructions below.
Highly Recommended: (Not Tested Yet, People who do this - please report in the thread)
Because of the 'One Little Problem' there are a few things you can do ahead of time so if you brick your phone you will be prepared:
If you don't own an extra one, buy a 2GB external SD card.
Follow steps 1-12 in the manual using your own phone.
Take the external SD card out of your phone and put it away in a safe place to be used if needed.
Or follow Rebellos's (Elite Recognized Developer) way:
Here's an experimental image: (Or attached to this post)
https://dl.dropbox.com/u/32145655/GT_I9300_unbrick_sdcard_head.zip
1) Insert SD card (Everything from it will be wiped!)
2) Bootup some linux machine (it can be rooted android phone aswell as its also linux machine )
3) Unpack archive
4) Perform dd if=GT_I9300_unbrick_sdcard_head.bin of=/dev/<path to SD card device>
On most of phones its /dev/block/mmcblk1 (MAKE SURE YOU DONT OVERWRITE YOUR INTERNAL PHONE MEMORY, ITS USUALLY "/dev/block/mmcblk0")
On PCs it depends, its sometimes /dev/sdb
More info about dding sd card:
http://mikelev.in/2010/09/cloning-an-sd-card-on-linux/
You're all ready and set, try to boot it up on dead I9300 and tell me how did it go! (Follow step 14 of Samsung's guide)
Also, I don't think Anyway JIG is necessary. Probably you only need to connect it to PC so it gets powered and you can use download mode.
Click to expand...
Click to collapse
Notice:
This method of fixing your bricked device is only meant to be used if all else fails: Full S/W package with Odin (PIT, BOOTLOADER, PDA, PHONE, CSC) Or USB Jig.
I have not done this before and have not tested this method, do this at your own risk!!!
-
-
Significant & Useful Posts
Significant & Useful Posts
mikep99 said:
Just been through actions 1-12 with no problems.
However, I can't see anything on internal/external sdcard that looks like a copy of the bootloader.
I'm assuming it's written to a part of the sdcard just like the 'goldcard' on the HTC Desire, which can't be seen without a hex editor.
This would then get picked up when using a jig?
Can anyone confirm this?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Rebellos said:
Here's an experimental image:
https://dl.dropbox.com/u/32145655/GT_I9300_unbrick_sdcard_head.zip
1) Insert SD card (Everything from it will be wiped!)
2) Bootup some linux machine (it can be rooted android phone aswell as its also linux machine )
3) Unpack archive
4) Perform dd if=GT_I9300_unbrick_sdcard_head.bin of=/dev/<path to SD card device>
On most of phones its /dev/block/mmcblk1 (MAKE SURE YOU DONT OVERWRITE YOUR INTERNAL PHONE MEMORY, ITS USUALLY "/dev/block/mmcblk0")
On PCs it depends, its sometimes /dev/sdb
More info about dding sd card:
http://mikelev.in/2010/09/cloning-an-sd-card-on-linux/
You're all ready and set, try to boot it up on dead I9300 and tell me how did it go! (Follow step 14 of Samsung's guide)
Also, I don't think Anyway JIG is necessary. Probably you only need to connect it to PC so it gets powered and you can use download mode.
Click to expand...
Click to collapse
Odia said:
You did not need to flash the bootloader to your phone first, its only in the instructions in case the bootloader in the good GS3 does not support SDCARD write protocol.
I can confirm that using an SDCARD image to create the tweezer-tag SDCARD does work.
NOTE: Its also possible to write the entire OS to SDCARD, not just the bootloaders.
Click to expand...
Click to collapse
Rebellos said:
Flashing new bootloader is relatively safe (as far as reflashing bootloader can be safe)
It's just same set of bootloaders but with enhanced ODIN protocol - support of writing into T-Flash. As Odia said - recently produced I9300 models might have this feature in bootloader already.
No repartition should be used for these, new bootloader should overwrite old bootloader in working I9300, and during second flash present PIT will be used.
Click to expand...
Click to collapse
Rebellos said:
It can be said I added few steps after step 11 and before step 12 of Samsung guide.
Note: System must be rooted.
11.1) Bootup phone and connect it to PC
11.2) Invoke "adb root"
11.3) Invoke "adb shell dd if=/dev/block/mmcblk1 of=/storage/sdcard0/recovery_sd_head.bin bs=1024 count=4096"
11.4) Invoke "adb pull /storage/sdcard0/recovery_sd_head.bin"
You will endup with dump of first 4 megabytes of sd card. Should be enough to contain all necessary data to re-create bootable sd card from it.
Actually boot partition is ~880KB big so I guess dump of ~900KB should be enough. But better to have abit more and be more sure it'll work.
Click to expand...
Click to collapse
Rebellos said:
I've disassembled my I9300 yesterday and did some live tests on it.
Unfortunately I was unable to trigger EXT-SD boot, it's pretty hard to short only single resistor without shorting anything else and hanging the board or blowing something up. I'll retry it someday later when I get better tools. Maybe I triggered ext-sd boot but it didn't end up in any special screen because my device was fully alive.
Some tech background I worked out on that solution
Some good news:
If this is possible for SGS3, it's highly plausible that this such method of unbricking can be used for Exynos SGS2 models. This of course needs preparing another magic-SD card.
Click to expand...
Click to collapse
Net.silb said:
We've made it to the XDA Portal! (link below)
http://www.xda-developers.com/android/fix-your-soft-bricked-galaxy-s-iii-samsungs-way/
Click to expand...
Click to collapse
Reserved...
Thanks for this
Sent from my GT-I9300 using xda premium
b-eock said:
Thanks for this
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
My pleasure!
Thanks man
Seems... complicated
I wonder if sharing the "Bootloader SD Image" is an option, would be great to have someone brave enough to upload it for the community to avoid messing with the bootloader of a healthy BORROWED i9300.
Thanks for sharing !
Just been through actions 1-12 with no problems.
However, I can't see anything on internal/external sdcard that looks like a copy of the bootloader.
I'm assuming it's written to a part of the sdcard just like the 'goldcard' on the HTC Desire, which can't be seen without a hex editor.
This would then get picked up when using a jig?
Can anyone confirm this?
Sent from my GT-I9300 using xda app-developers app
Thanks for the share man! Will do some digging and look into this as well when I get time!
Excellent... I've always been worried about bricking my device. I've had my S3 for 2 months and it's the first phone I've rooted, so bricking was always a serious concern for me.
If this is proven to work... thank god!
Hi guys,
Step 15 in the (12-38)_GT-I9300_BRICKED.pdf Is not 100% clear to me and I would love if someone can explain what exactly needs to be done at that step.
"15) Connect the PBA with Anyway JIG and power supply, with the POWER OFF. ※ Use 11pin cable to supply power to the PBA."
Moderators please make this sticky!
Report the thread guys,it'll be useful to have this around in case something bad happens!
If you can use any GS3 to restore the get sharing those files
Sent from my GT-I9300 using xda premium
Net.silb said:
Hi guys,
Step 15 in the (12-38)_GT-I9300_BRICKED.pdf Is not 100% clear to me and I would love if someone can explain what exactly needs to be done at that step.
"15) Connect the PBA with Anyway JIG and power supply, with the POWER OFF. ※ Use 11pin cable to supply power to the PBA."
Click to expand...
Click to collapse
I guess the anyway jig is the jig that they use to put phones into download mode? I got one for my s2 but I'm not sure if it's the same thing.
Sent from my GT-I9300 using Tapatalk 2
This can only be done if you have the Samsung Anyway jig and no one on XDA has their hands on that yet. Or schematics of the board. We need an inside guy to leak that or even give us one.
Sent from my GT-I9300 using xda premium
b-eock said:
This can only be done if you have the Samsung Anyway jig and no one on XDA has their hands on that yet. Or schematics of the board. We need an inside guy to leak that or even give us one.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Yes, maybe only a Samsung Anyway Jig can be used as the phone needs to be booted into "SD Card Mode".
But there is always the possibility that a normal Jig can be used, and the power supply can come from the battery and that shorting "R313 resistance" will force the phone into "SD Card Mode".
We can only know for sure once someone has tried it.
Edit:
Info on the Anyway Jig: http://forum.xda-developers.com/showthread.php?t=1629359
I am not here to argue, if we find a way to make the S3 unbrickable without the unbrickable mod. Then Awesome!!! Maybe this weekend we can talk about how things can be done. Until then I have football practice 6 outta the 7 days a week.
And I have that thread bookmarked bro
b-eock said:
I am not here to argue, if we find a way to make the S3 unbrickable without the unbrickable mod. Then Awesome!!! Maybe this weekend we can talk about how things can be done. Until then I have football practice 6 outta the 7 days a week.
And I have that thread bookmarked bro
Click to expand...
Click to collapse
Never intended to sound provocative, just trying to brainstorm ideas on how we can make this thing work!
Look here at post #14: http://forum.gsmhosting.com/vbb/f200/gt-i9300-boot-repair-freee-1497416/
The guy got into SD card mode and got this:
SDCARD MODE
COPY BINARY FROM SDCARD
COPY BINARY TO EMMC
SDCARD DOWNLOAD FAILED
If we can contact this guy and see exactly what happened maybe we can learn more about how to do this.
In short, i deleted my photos by accident, and deeply desire to recover them.
Data Recovery programs wont work on my Google Nexus 4, for a combination of reasons. Namely, because it is not a usb mass storage device, it is internal memory, and because the phone has not ever been rooted. If it is possible to recover the photos without rooting the phone, this would be favorable. But i doubt this is possible.
Is there a way to root my phone without causing a "factory wipe/reset"? Perhaps by avoiding unlocking the bootloader?I am not even 100% sure if this can be achieved on 4.4.2. as of now. I am continuing to investigate, but if anyone has the know-how, please let me know.
this forum here, suggests something that might work, but at the end of the forum, it suggests that 4.4.2 is still impossible to root without wiping.
-There are methods of scanning the phone after it has been rooted, but i can't find the right kind of rooting i need.
-There are methods of copying the phone's hard drive -bit-by-bit- to my PC in .RAW format, and then converting this into something that can be mounted like a real drive, which could be scanned and from which photos could be recovered., but this method requires a rooted phone as well
-there is a possibility of trying to mount the phone on a linux OS, and then scan it possibly. but i don't know if this is impossible.
i am reading the basics in the meantime.
LG Google Nexus 4, 4.4.2
Build:KOT49H
kernel:
3.4.0-perf-g2cae413
[email protected] #1
wed Nov20 14:54:28 PST 2013
Desktop PC: Windows 7 Professional 64bit, service pack 1.
Laptop: mac...
you can read more about things i have tried and my other concerns, in greater detail below.
LOTS OF METHODS, LITTLE CLARITY
I just came back from visiting some dear friends in china and purchased an upgraded version of dropbox. Before I uploaded my photos, I accidentally deleted my entire album.
What is the safest and surest attempt for recovery?
1. i need to avoid installing anything on my phone as much as possible - (lest it overwrite the empty areas where the "deleted" photos reside.)
2. i need to keep my phone off as much as humanly possible (lest it overwrite the empty areas where the "deleted" photos reside.)
3. almost without saying - id like to avoid bricking my phone, (lest it destroy my "deleted" photos)
SOFTWARE RECOVERY SECTION
All known software recovery programs won't find any data on my phone because either they are made for scanning mountable drives, USB mass storage devices, or some simply cannot scan the device unless i root my phone (although I am not sure if rooting is directly correlated with successful scanning, or if rooting the phone simply allows me to carry on with other necessary steps prior to "successful scanning"- like allowing me to installing apps that allow me to mount the internal memory as a scannable drive). Enabling USB Debugging, or enabling/disabling MTP is not the same as enabling USB mass storage mode. Seeing the Nexus 4 as "portable Device" under my computer does not mean it is a mounted drive that i can scan with a recover program. No matter what, nothing seems to work with the Google Nexus 4 as it is now.
***I first tried installing the driver's through the ANDROID SDK, by unzipping the contents from the downloaded zip file and by double clicking the .exe file. Double-clicking the .exe file resulted in a cmd dos-style window popping up and immediately disappearing. Perhaps i needed to put the extracted folder on "C:\"?
REGARDLES....later, I have used WugFresh Nexus Root Toolkit v1.8.2 for ensuring proper driver installation for my phone. I have only used this software to install drivers. It walks you through bad-driver uninstallation/clean up, it retrieves the latest drivers, installs them, and then tests their workability for you and lets you know if the drivers were successfully installed.
I have not used Wug's toolkit to root or hack my phone... yet....
Below is a list of software I have used on my Windows machine and my mac. These simply will not work with the phone as it is right now.
Remo
TenorShare
Bycloud android data recovery
Android Data Recovery
Dr. Fone
Recuva
- i havent tried disk digger. but it requires a rooted phone.
SO simple methods will simply not work? Please correct me if I am wrong.
BIT BY BIT CLONE METHOD
This seems to be the most tedious (but thorough) method for actually preparing something that can be truly scanned for photo-recovery. This method seems to create a bit-by-bit copy of the phone to my computer, which can be converted and mounted and then scanned.
However, it requires rooting. Not to mention, it recommends non-destructive rooting. Which leads me to the next section ...
ROOTING section (and its problems)
In the fruitless sections listed above, it always seems to lead towards rooting as a requirement. Most people say you should root your phone when you first get it, because, i suppose rooting is "synonymous" with a wipe/reset. I believe this reset happens as a result of the bootloader being unlocked. According to MY limited understanding, this unlocking process essentially causes a "factory reset" which wipes the phone, and then catastrophically overwrites the precious space where the deleted photos currently reside. this is unacceptable. I imagine, this "reset" is for security reasons.
Most people seem to suggest that you make a back up before you root. This isn't helpful for my situation because we are talking about retrieving deleted data. I cannot make a back-up of deleted data.
Is it really possible to root without wiping the Google Nexus 4?
Is it even profitable to consider rooting a viable option? I don't imagine myself enjoying a rooted phone as much as others on this forum. I would hate to be creating a black hole for malicious software to breed. i am only concerned with data retrieval for this one time in my life. Is rooting the only viable option? If i root, won't that make the previously mentioned software-scanning section (e.g., Dr. fone), more viable than the BIT-BY-BIT section tedious and pointless by comparison?
All in all, I think it most likely that i will need to root my phone and do the bit by bit copy. If a rooting-first-step is the final conclusion, then I am looking for clear and careful advice for my specific phone on how to root it without jeopardizing the deleted photos (e.g., avoiding a "factory reset" from unlocking the bootloader, or perhaps avoiding unlocking the bootloader altogether) and how to hopefully carry on from there. I don't even know if avoiding "unlocking the bootloader" will virtually guarantee a non-destructive root method
Rooting gets crazy because it leads to necessary installations of SuperUser, busybox, kernels, roms, etc... There are so many unfamiliar vague terms for a beginner like me and it is taking tons of time to break through. I am uninterested in keeping my phone rooted, or maintaining a lifestyle with a rooted phone. if we can move expeditiously from point A to B and then back, (get in, get the photos, and get out,) that would be the most awesome plan.
LINUX METHOD?
is there another way to get to the deleted photos?.
I do not know if 'mounting' the phone is akin to 'mounting' a scannable drive. http://www.youtube.com/watch?v=fw2MKGIgyF4
maybe this is another wild goose chase?
IN SUMMARY
1. It would be helpful if there was a root-free photo-recovery software solution that actually works (this is unlikely to be in existence) with an unrooted nexus 4
2. It would be helpful if it is possible to root without destroying my chances of recovering my deleted photos, with the goal of allowing recovery software access (deeper access) to my phone, i.e. disk digger or if necessary... a bit-by-bit copy to my PC.
3. it would be interesting if the nexus 4 can be magically mounted and scanned on the linux operating system
4. It would be MOST HELPFUL if there was a clear consensus on what direction to take, because there is a lot of misinformation out there. One wrong step and i could end up shooting myself in the foot twice (if i inadvertently reset my phone), or three times (if i brick my phone).
5. can the phone be put back to normal (i.e. unroot) after rooting? or does this require that i make a full backup of the phone in its current state? ( i tried using WUGS toolkit to backup my media, but it wont do it unless i unlock the bootloader... back to that problem again )
I'm sorry for sounding like an idiot. I have been at this for a more than a few hours. I sincerely appreciate any help and consideration towards this specific situation in advance, and the hope that this forum has already offered me.
Impossible to root 4.4.2 without unlocking the boot loader and wiping the device.
DrFredPhD said:
Impossible to root 4.4.2 without unlocking the boot loader and wiping the device.
Click to expand...
Click to collapse
Same problem.... There isn't a solution yet? :crying:
fabrollo said:
Same problem.... There isn't a solution yet? :crying:
Click to expand...
Click to collapse
Nope, you have to unlock the bootloader and that wipes the device
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
jd1639 said:
Nope, you have to unlock the bootloader and that wipes the device
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Click to expand...
Click to collapse
And after i should try to recover all the wiped files with diskdigger for example? Maybe the datas that we was searching will be found?
Thanks... if i must try this way to solve my problem i will bite the bullet...
fabrollo said:
And after i should try to recover all the wiped files with diskdigger for example? Maybe the datas that we was searching will be found?
Thanks... if i must try this way to solve my problem i will bite the bullet...
Click to expand...
Click to collapse
The chances of recovering anything is very small
Sent from my Nexus 5 using XDA Free mobile app
Hello
i have the Gold Galaxy S5 & a 64GB SDCard from Samsung.
The phone and SDCard are encrypted and have worked fine for a long while.
One day I tried accessing the files stored in the SDCard by connecting my S5 via USB 2 to my laptop (Ubuntu 15.10); and It failed to mount since.
I have created an image of the SDCard using 'dd' in Linux.
Therefore, I would rule out a hardware failure.
Furthermore, only once this card was mounted on this phone and I had a glimpse of my pictures, again it failed to copy anything out via USB.
Currently, when I put the SDCard into the phone it shows notifications saying:
... Preparing SD Card
... SD Card safe to remove
As I still have the phone encrypted - and I presume the encryption key are present.
Is there some way that I can copy the encryption key out of the phone? Use those to read the image of the SDCard?
The partition table of this SDCard does not appear to be correct - is it encrypted as well? Is this expected?
It is really annoying to have this happening when I was copying the data out of the phone as a backup ...
It would be really great to have my data back.
Your suggestion on how to solve this problem will be most welcome.
bumping ....
Thx
Since the moment that you damaged the encryption key protecting the card, the data over this card does not belong to you any more.
Kiriakos-GR said:
Since the moment that you damaged the encryption key protecting the card, the data over this card does not belong to you any more.
Click to expand...
Click to collapse
sorry
how did I 'damage' the encryption key?
I tried reading the SDCard in the same phone.
I have older backups of the phone that included the SDCard - would that help?
Thanks,
You better ask further questions in a forum specialized to Ubuntu 15.10
Kiriakos-GR said:
You better ask further questions in a forum specialized to Ubuntu 15.10
Click to expand...
Click to collapse
Doesn't sound like a problem on ubuntu's side unless it wrote some header or something when it tried to read.
Sent from my SAMSUNG-SM-G900A using Tapatalk
The card was mounted in the Phone - Ubuntu accessing it through the USB3
And it just stopped working - just like that!
But, could actually understand that it was something like that.
Would it be possible to reuse an old image (done with dd) of this USB to try and resurrect these files?
for info:
- where are the keys kept?
- surely the phone has some.
Cheers
nkdbr said:
for info:
- where are the keys kept?
- surely the phone has some.
Cheers
Click to expand...
Click to collapse
If I was aware of that? I would require 1000$ payment so to share it.
Message to all:
1) As long Samsung provides software tools only compatible with Microsoft Windows and Android, this translates that other OS platforms them are not supported.
2) Any attempt hacking phone encryption this is illegal.
3) One desperate owner who lost access to SD-card, he should physically visit Samsung service center, demonstrate proof of ownership for phone and card, and ask their help.
Kiriakos-GR said:
If I was aware of that? I would require 1000$ payment so to share it.
Message to all:
1) As long Samsung provides software tools only compatible with Microsoft Windows and Android, this translates that other OS platforms them are not supported.
2) Any attempt hacking phone encryption this is illegal.
3) One desperate owner who lost access to SD-card, he should physically visit Samsung service center, demonstrate proof of ownership for phone and card, and ask their help.
Click to expand...
Click to collapse
Android=Linux in a very basic sense. Even then, it's not 'not supported', furthermore as I said earlier, itse extremely unlikely plugging the phone in would break it regardless of the OS.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Rakuu said:
Android=Linux in a very basic sense.
Click to expand...
Click to collapse
I do agree and I did my homework about Android in old tablet about a year ago.
Rakuu said:
furthermore as I said earlier, itse extremely unlikely plugging the phone in would break it regardless of the OS.
Click to expand...
Click to collapse
When you use any OS this working with command line, this translates that if you are a terrible commander? you army this to be also drowned in the river because of you.
This is what it did happened here too.