Hello XDA,
It's been awhile since I've made a post, but I'm very unsure about what I'm trying to do.
I have a T-Mobile HTC One S, about 4 years old, that has a damaged display, but I am trying to do a backup to pull out photos and whatnot that I had on the phone before I broke it.
My question is, is there a way for me to do a backup of the whole Android OS and whatever file there is on the phone to emulate it on my Windows PC?
Now for what I've done so far with a bit of back story. The phone broke about 4 years ago when I dropped it and damaged the display and I never got around to fixing it or trying to do a blind backup through the recovery until a few days ago.
I had a friend replace the screen and the phone booted up, except it was soft bricked and was stuck at the splash screen. I was able to get into the recovery and tried to mount the phone to my computer, but it wouldn't let me and I've forgotten what the error message was.
My problem now, is that I've dropped the phone again and the display is broken yet again, but I was curious if I could extract every single file out of the phone and use an emulator so that I can try and get back into it.
Thank you
Edit: I forgot to mention that the phone is rooted. I don't remember what ROM I used, but the phone does have clockwork mod recovery. My big thing is wanting to know what commands to use to create a backup from adb and what directories to point it at.
This would only be possible with a custom recovery. If you don't have one (and I would assume you don't since you did not mention it already), then there's nothing you can do to recover data as the method to install the custom recovery involves 1) being able to see the display to do some things 2) wipes the phone.
It's using a very old version of clockword mod for recovery. I did forget to mention that the phone is rooted though, and I'll make sure to add this tidbit into the original post.
You might be able to use a tool like this http://forum.xda-developers.com/showthread.php?t=2339530 then.
Related
I installed Chainfire3D (after hearing good things about it) and then realized the problems it causes, so i deleted the app and then its CF3D drivers from system/lib which didnt work properly anyways. Upon restart device doesnt boot anymore :crying: (welI maybe its on cause the battery generates heat, but its black screen) I also couldnt get titanium backup to work in the past just in case something like this happens cause it was constantly stuck on yahoo finance when backing up.
My main issue is I had alot of things (worth a couple days) installed on my phone, and dont want to lose all of it. Bad thing i didnt realize there is Nanadroid backup (cause its my first android phone) which works unlike titanium quickly and efficiently, but backing things up now after black screen is pointless no? i can acess CWM recovery, but dont want to factory reset yet.
So any way to inject those stupid CF3D drivers via ADB? Or maybe backup everything but that certain system/lib folder?
Edit: i ran into this:
On CF-Root just boot into recovery, ADB shell to it, and type "rootsh" (instead of "su") to have root shell access... if anything goes wrong, just "mount /system" and "/system/lib/cf3d_uninstall.sh" to remove the CF3D driver and restore the old one. Not very likely it will happen, but a good fallback option in case of issues (no need to reflash firmware or restore backup)
Click to expand...
Click to collapse
, unfortunately cf3d_uninstall.sh was one of the files i deleted, but maybe if someone who has Chainfire3D installed on S3 LTE can share that file, i can then inject it and restore the old drivers?
Seems mine suffered a similar fate.
a friend suggested SPB 3D loaded it. It sucked and caused lock-ups and delays. I uninstalled and the phone seemed to be fine after.
I plugged the phone in to charge overnight and about an hour later when going to bed the screen was stuck on the boot-up screen.
has not gone past this since.
Wanted to get the firmware restored and after trying to find a suitable stock one I took it to my SP for repair they tried to flash it but it fails every time, they said the motherboard is toast.
It will boot to flash mode so it can be uploaded but it doesn't work. Odin says no partitions.
Tried Heimdall it detects the phone but it tells me the image is corrupt and I also have no idea how to repair the partition that seems to be lost.
white 16GB Tmoble GS3
Actually my current issue is similar, it boots up says galaxy S3 then black screen. I can connect to odin, i can boot into clockwork, and i can flash roms, ODIN says everything is successful after i flash but when it boots it still goes to a black screen. this happened after i flashed a rom(that worked) and flashing a kernel that also previously worked....after that its been stuck....i can flash whatever with success but i cannot seem to get it past that Galaxy S3 screen....
I flashed the new FreeGS3 rom, and the TGST STOCK ICS Alpha37 kernel i cleared caches and wiped davliks not too sure where to go from here.....Do i need factory tmoble GS3 PIT file?
Redsalamander said:
Seems mine suffered a similar fate.
a friend suggested SPB 3D loaded it. It sucked and caused lock-ups and delays. I uninstalled and the phone seemed to be fine after.
I plugged the phone in to charge overnight and about an hour later when going to bed the screen was stuck on the boot-up screen.
has not gone past this since.
Wanted to get the firmware restored and after trying to find a suitable stock one I took it to my SP for repair they tried to flash it but it fails every time, they said the motherboard is toast.
It will boot to flash mode so it can be uploaded but it doesn't work. Odin says no partitions.
Tried Heimdall it detects the phone but it tells me the image is corrupt and I also have no idea how to repair the partition that seems to be lost.
Click to expand...
Click to collapse
Not to offend anyone the Dev app said he wasn't going to support it for the galaxy s3
Sent from my SCH-I535 using xda premium
Turns out mine was a faulty mainboard after dragging their feet to repair it including a delay due to them wanting to verify warantee with proof of purchase samsung finaly agreed to swap it out for a new one.
Redsalamander said:
Turns out mine was a faulty mainboard after dragging their feet to repair it including a delay due to them wanting to verify warantee with proof of purchase samsung finaly agreed to swap it out for a new one.
Click to expand...
Click to collapse
Well thing is on my end...i didn't flash whatever the OP had flashed. What i DID do though is flash a rom and a kernel on the same cwm event. when it rebooted...it just does this....
i have a backup file....its on my laptop though....with only using odin or cwm how can i push that file onto my phone? My CWM doesnt have USB mount else id just do that.....?
I've been searching the forums, and google for a while and can't seem to find a solution that works at all for me. First off, a little history. I am a n00b, and I very stupidly rooted my phone last night, without a recovery.... Actually I don't think just rooting was a big deal, it was me changing the vm heap properties that was really stupid. Why did I change it when the phone was working fine you might ask? Because I quickly gleaned over a forum post about adjusting the heap size to make your phone blazing fast, so, like any other idiot would, I did what the thread suggested, and instead of blazing fast speeds I got a boot screen logo....... forever... Talk about a huge mistake on my part....
Here's the problem,
Phone is stuck on the bootscreen, I can boot into system recovery (stock).
Android System Recovery has a message on the bottom of the screen that says "E: Cannot load volume /misc!"
I have wiped the cache partition, and did factory reset according to the manufactures website.
I cannot get ADB of Fastboot to see the device, even with drivers installed.
I do have a back up of build.prop that is unscathed, but I have no idea how to flash it, or "push" it or whatever.
I do not have CWM installed, and it appears that usb debugging is disabled.
My phone is a Kyocera Hydro. I'm using Windows 7 64bit.
I know I should never have done this, it was idiotic, and easily the dumbest thing I've done in a while. I'm hoping someone out there can help me fix this. Is it possible to put the backup of build.prop on the SD card and have it overwrite the corrupted one? Is there any hope at all?
I guess it can't be done then? I had hoped that as long as the bootscreen could come on that there was hope. Hopefully someone out there knows how to push the backup build.prop back onto the phone.
Well right now you're pretty screwed. There's no way to restore it without a custom recovery. You have 2 options -
1) Wait for someone to make a custom recovery for your phone.
2) Try to claim warranty and get it restored/exchanged at the service center. Say it just randomly rebooted and got stuck at the boot screen.
Sent from my Desire HD using xda premium
Aravoth said:
I guess it can't be done then? I had hoped that as long as the bootscreen could come on that there was hope. Hopefully someone out there knows how to push the backup build.prop back onto the phone.
Click to expand...
Click to collapse
Where did you get the phone Boost, Amazon Wal-Mart?
Sent from my KFTT using xda app-developers app
So long story short I have this thunderbolt that is not working any longer. All of this happened over a year ago so I am vague on what I did to get the phone in its currently ruined state. It was rooted with the stock image and after trying to put a CM rom on it that didn't work I mistakenly booted into the phones recovery instead of clock work.
I now get a security warning and it is now s-on. If i do a recovery or factory reset it just boots back into the bootloader. Attached is an image of what is current on the screen when I power it on. I can't get ADB working on this pc but my spare rig has it working in OSX. ADB does not display the device. I have a way to get files onto the sd card but I am still kinda new to all of this stuff and just looking for some help. So where do I proceed from here?
I am going out of my mind.
So the phone just literally booted into my rooted rom. So now the question is, how do I get rid of the security warning and get s-off permanently?
At my end.
After a long day of trying to fix this thing and crawling all over the internet reading different posts I officially don't have a damn clue as to how to fix this. I am pretty sure the bootloader is corrupted and seeing as the phone is so old now it's really hard to find working links to downloads for this device.
Hi,
A month ago i suffered a really bad flash and bricked my i9300. I had no efs backup, i knew very little about the importance of the efs-folder.
After trying every possible solution xda and the www have to offer i finaly gave up. Furious with myself. The last thing i did in pure desperation was to copy the efs-folder straight over to my PC and then deleted the efs-folder on the phone, and hoped that the phone would magicly put all the pieces on the right place again. That was not the case.
This is how the problem looks now: When i start the phone it just says SAMSUNG with the swirly bluish flame (or whatever) spinning around it. Then it reboots. Then i go into stock recovery it says "e:failed to mount /efs". I then flashed CWM (dont remember what version, but i belive it was the latest version) and tried mounting efs from there. - Same error - Failed to mount.
But now i have a new i9300 and was thinking to myself, could i use the efs.img-backup from this new phone to my old one? I assume, i would be breaking the law by cloning the imei. But after i've got the proper structure back to the efs-folder i could maybe switch the containing files with my files from the old phone?
Is this mad?
I would really appreciate any kind of help on this matter, or a solution to mount efs? Keep in mind though, that the phone doesn't boot into TW. All i got is Download mode and recovery.
I
DrunkWithAGun said:
Hi,
A month ago i suffered a really bad flash and bricked my i9300. I had no efs backup, i knew very little about the importance of the efs-folder.
After trying every possible solution xda and the www have to offer i finaly gave up. Furious with myself. The last thing i did in pure desperation was to copy the efs-folder straight over to my PC and then deleted the efs-folder on the phone, and hoped that the phone would magicly put all the pieces on the right place again. That was not the case.
This is how the problem looks now: When i start the phone it just says SAMSUNG with the swirly bluish flame (or whatever) spinning around it. Then it reboots. Then i go into stock recovery it says "e:failed to mount /efs". I then flashed CWM (dont remember what version, but i belive it was the latest version) and tried mounting efs from there. - Same error - Failed to mount.
But now i have a new i9300 and was thinking to myself, could i use the efs.img-backup from this new phone to my old one? I assume, i would be breaking the law by cloning the imei. But after i've got the proper structure back to the efs-folder i could maybe switch the containing files with my files from the old phone?
Is this mad?
I would really appreciate any kind of help on this matter, or a solution to mount efs? Keep in mind though, that the phone doesn't boot into TW. All i got is Download mode and recovery.
Click to expand...
Click to collapse
That new efs folder you're talking about still contains the IMEI number specific for that device. Any act pushing or copying that efs folder to your old phone is illegal.
However since you can still boot to Download mode on your old phone you can try flashing a new stock firmware via Odin and see if it boots properly. If it fails then better wait for a more expert answer since I haven't experience your issue on mine yet (and I hope i won't).
DrunkWithAGun said:
Hi,
A month ago i suffered a really bad flash and bricked my i9300. I had no efs backup, i knew very little about the importance of the efs-folder.
After trying every possible solution xda and the www have to offer i finaly gave up. Furious with myself. The last thing i did in pure desperation was to copy the efs-folder straight over to my PC and then deleted the efs-folder on the phone, and hoped that the phone would magicly put all the pieces on the right place again. That was not the case.
This is how the problem looks now: When i start the phone it just says SAMSUNG with the swirly bluish flame (or whatever) spinning around it. Then it reboots. Then i go into stock recovery it says "e:failed to mount /efs". I then flashed CWM (dont remember what version, but i belive it was the latest version) and tried mounting efs from there. - Same error - Failed to mount.
But now i have a new i9300 and was thinking to myself, could i use the efs.img-backup from this new phone to my old one? I assume, i would be breaking the law by cloning the imei. But after i've got the proper structure back to the efs-folder i could maybe switch the containing files with my files from the old phone?
Is this mad?
I would really appreciate any kind of help on this matter, or a solution to mount efs? Keep in mind though, that the phone doesn't boot into TW. All i got is Download mode and recovery.
I
Click to expand...
Click to collapse
I don't understand why you would want to do that? You have purchased a new phone, which has a new IMEI. Putting the old IMEI on there is a) pointless and b) not possible (I think).
Unless you have purchased a stolen phone?
But now i have a new i9300 and was thinking to myself, could i use the efs.img-backup from this new phone to my old one?
As said no
Suggest you ask in the IMEI?EFS thread instaed of starting yet another ,
None of the phones are stolen, but if i could get the old one working again i could either sell it for more than just a faulty phone or give it to my wife, anything. It's just an annoying paperweight.
My intentions was just to get phone in a better state then it is in now, meaning putting an original efs-structure from my new phone on it. And if it that way could jumpstart it so i could atleast get TW running, and from there switch out the new contents in the folder with the contents from the old phone i put on my pc.
And i am sorry for starting yet another efs-thread :\
Mod Edit
duplicate thread
Thread Closed
malybru
Forum Moderator
I bricked my phone, so I interested how and can I fix this.
What I actually done with it?
It was long time ago, but I think that I remember correctly.
I tried to install custom ROM,
I upload new rom, and before I try is this compatible
I deleted existing ROM and Recovery, so my phone stay without ROM and Recovery.
Now it just go in start screen and stay on it.
I remember that I tried to fix this from my PC
I managed to connect phone with pc, and I managed to aces from command line, but I didn't managed to do nothing.
I remember that I have some issue wit uploading file into phone because If I correctly remember I didn't have permissions to write on this partition or something like that.
Is there any chances to fix phone without recovery and rom on it?