Database Info

How to replace one file when failing to boot

Hey guys
I screwed up my vold.fstab trying to get "_ExternalSD" back.
Unfortunately! I did not run a nandroid before I made the change.
Now, I can dirty flash my rom on top, or go back to a nandroid from a few days ago, but I'd really just like to recover and go on my merry way. And maybe learn something in the process.
Only thing is, I can't figure out how to access the phone other than the External SD card through CWM.
Can I mount the internal /system and access through USB? Is there some facility to copy a file from one point to another? Any other methods? I guess the phone has to be up to run ADB, right?
I don't know how to generate a flashable zip but I could extract the original version of the file from the original rom. I assume that its non trivial to create a flashable zip, but maybe someone can comment? It looks like there is signing and certificates involved..
thanks for any ideas

bluenote73 said:
Hey guys
I screwed up my vold.fstab trying to get "_ExternalSD" back.
Unfortunately! I did not run a nandroid before I made the change.
Now, I can dirty flash my rom on top, or go back to a nandroid from a few days ago, but I'd really just like to recover and go on my merry way. And maybe learn something in the process.
Only thing is, I can't figure out how to access the phone other than the External SD card through CWM.
Can I mount the internal /system and access through USB? Is there some facility to copy a file from one point to another? Any other methods? I guess the phone has to be up to run ADB, right?
I don't know how to generate a flashable zip but I could extract the original version of the file from the original rom. I assume that its non trivial to create a flashable zip, but maybe someone can comment? It looks like there is signing and certificates involved..
thanks for any ideas
Click to expand...
Click to collapse
this is why i hate it when people make those guides.
messing with the vold.fstab is dangerous (even though its only a few lines) if your trying to recover your data, give up. its not going to happen. (sorry)
when you edit the vold.fstab it messed up the partitions on your internal SD card and most likely did the equivalent of wiped your /system partition. (or another important one.) your actually lucky it did not completely brick your phone.
your post was a little vague, but if you can, just restore an older nandroid, or wipe everything and install another ROM. (you can try dirty flashing but i dont think itll work)
if you cannot access CWM, then follow the steps in This guide. it should get you back up on your feet. after you follow that guide flash a gingerbread ROM (any gingerbread rom will do fine) then you can reboot and flash any ROM you want. (it needs this to fix a quirk in that script)
Hope you get it fixed
EDIT: re read your post, if your feeling adventurous and want to give it a shot, boot into CWM and connect it via usb. you can now get into an ADB shell on your phone by typing 'adb shell' if you have adb all setup and working. (im working from memory here so dont quote me on any of this)
now, you should be able to access your /system folder from that shell. be very careful though, i dont have much experience right here, and if i remember correctly you might not be in the full root directory yet)
if you can get into it try replacing your vold.fstab with a stock one,
if you dont have a stock one lying around, make a nandroid of the current state of the rom, then flash another rom, pull the vold.fstab, then re-restore back to the broken one and restore it (id upload mine but my phone is OOC right now )
after that just reboot and hope it resolves itself, if not then just follow my advice above
and keep that guide i linked to handy, messing around in CWM has the ability to brick your phone, if it does, then just follow that guide.

Klathmon said:
this is why i hate it when people make those guides.
messing with the vold.fstab is dangerous (even though its only a few lines) if your trying to recover your data, give up. its not going to happen. (sorry)
when you edit the vold.fstab it messed up the partitions on your internal SD card and most likely did the equivalent of wiped your /system partition. (or another important one.) your actually lucky it did not completely brick your phone.
your post was a little vague, but if you can, just restore an older nandroid, or wipe everything and install another ROM.
if you cannot access CWM, then follow the steps in This guide. it should get you back up on your feet. after you follow that guide flash a gingerbread ROM (any gingerbread rom will do fine) then you can reboot and flash any ROM you want. (it needs this to fix a quirk in that script)
Hope you get it fixed
Click to expand...
Click to collapse
How bout adb and pushing the file back in? Or cant you access the phone via adb?
Sent from my LG-P970 using XDA

N00BY0815 said:
How bout adb and pushing the file back in? Or cant you access the phone via adb?
Sent from my LG-P970 using XDA
Click to expand...
Click to collapse
re read your post and updated my last post right after you posted
after dealing with noobies all day, i forget sometimes people want to try big things

Thanks guys. The info I was missing was there's no special trick to attaching adb while in CWM! Just plug in!
My phone is back up and running and partitions are fine as far as I can see after just booting up.

Hi there! I messed up with the vold.fstab filfe on my tablet – I replaced it with a downloaded file with the intention to transfer apps to my external SD card.
Now my tablet is only showing the startup logo and won’t continue loading. I can access recovery mode. Now I want to restore the original vold.fstab file.
My questions:
1. Using the Android SDK, the file explorer does not show any files, though my tablet is recognized.
2. Using adb push, it yields an error: permission denied, how to successfully push the original vold.fstab and replace the existing vold.fstab?
3. If I dump an image of my tablet and edit the dumped image, would this be easier compared to the steps above?
Thanks!

http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.

TwitchyEye said:
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
Click to expand...
Click to collapse
Thanks, I will try it later when I got home. My tablet is not found here. I have a Skyworth S71(3G) with RK3066 chipset.

BryanF said:
Thanks, I will try it later when I got home. My tablet is not found here. I have a Skyworth S71(3G) with RK3066 chipset.
Click to expand...
Click to collapse
You need to do an adb remount before you can push. Was it rooted before?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!

Mansa_noob, yes, my tablet is rooted. I followed some instructions about adb but had an error saying access denied, and also no files are displayed at file explorer. See my posts above. I also mounted it successfully. I will post some sreenshots later.
Please if you have some instructions, I am willing to try.
---------- Post added at 07:06 AM ---------- Previous post was at 07:02 AM ----------
TwitchyEye said:
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
Click to expand...
Click to collapse
Hi twitchyEye, it did not work. It attemps to install (using the install update from ext sd card) but then says installation aborted.
Any more suggestions? Thanks

What recovery are you using? I suck with adb so I got nothing on that front.

It was the stock recovery from my Tablet. I don't have it on hand right now, I will post later. The chipset is RK3066. My problem is my tablet has no official support on the internet (maybe becaue it's still new). Model is Skyworth S71(3G).

I see. Yeah this is over my head man. I thought for sure you were running a custom recovery and it was an easy answer. I'm actually struggling right now with adb myself with a similar issue something about permissions whenever I try to do anything to my phone. So I guess right now would be a perfect time for somebody to chime in with a smarter answer!

TwitchyEye said:
I see. Yeah this is over my head man. I thought for sure you were running a custom recovery and it was an easy answer. I'm actually struggling right now with adb myself with a similar issue something about permissions whenever I try to do anything to my phone. So I guess right now would be a perfect time for somebody to chime in with a smarter answer!
Click to expand...
Click to collapse
Are you doing adb remount and still getting permission denied?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!

mansa_noob said:
Are you doing adb remount and still getting permission denied?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
Yes, I did adb remount and still access denied

BryanF said:
Yes, I did adb remount and still access denied
Click to expand...
Click to collapse
This is strange. A properly rooted phone would adb remount to r/w system. Something is fishy. Is it rooted+
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!

mansa_noob said:
This is strange. A properly rooted phone would adb remount to r/w system. Something is fishy. Is it rooted+
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
I am sure it is rooted, because I downloaded an application from Google play to check it it is rooted or not. It is really rooted. I alvo confirmed this as I can now fully backup and restore my apps using Titanium backup before the tablet is messed up.

BryanF said:
I am sure it is rooted, because I downloaded an application from Google play to check it it is rooted or not. It is really rooted. I alvo confirmed this as I can now fully backup and restore my apps using Titanium backup before the tablet is messed up.
Click to expand...
Click to collapse
OK. Odd or not, it is what it is. Is it possible for you to load a custom recovery?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!

mansa_noob said:
OK. Odd or not, it is what it is. Is it possible for you to load a custom recovery?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
I want to try, but the stock recovery is my last hold as I have no stock ROM. If I overwrite the stock ROM, I cannot reinstall it as I don't have a copy of it.

So why not flash cwm with nvflash and then make a backup of your current stock rom? I did exactly that.
Sent from my LG-P999 using xda premium

[Q] Flash CWM 5 over CWM 6

I currently have CWM 6 installed, but prefer the older version's backup method and file structure (don't like the Blob thing). Can I flash CWM 5 over 6? Thanks!

Youy could, but I dont recommend it. I dont have CWM installed so I cant tell you exactly how, but in the advanced options I am to understand there is an option to disabled the segmented backups, which would eliminate the blobs folder and each backup would then be in its own folder.

apacseven said:
Youy could, but I dont recommend it. I dont have CWM installed so I cant tell you exactly how, but in the advanced options I am to understand there is an option to disabled the segmented backups, which would eliminate the blobs folder and each backup would then be in its own folder.
Click to expand...
Click to collapse
Thanks for your response. I looked at the various menu options and couldn't find that option. Can you be more specific? Thanks!

STraver said:
Thanks for your response. I looked at the various menu options and couldn't find that option. Can you be more specific? Thanks!
Click to expand...
Click to collapse
The best I can do since I dont use CWM myself and dont really feel like installing it just to check (sorry) is quote the person that pointed out to me that it can be disabled. Hope this helps.
Legato Bluesummers said:
You guys realize you can stop making blob backups and go back to normal tar right? Under back up go to advanced settings or whatever its called and choose the other option. Now you won't make back ups in blobs,but now you do them the old way. One folder for the whole back up, about 1-2 GB in size. Blobs are just nice as the backup takes under 5 min. Doing it the old way takes a bit longer.
Click to expand...
Click to collapse
FWIW I use and prefer TWRP (team win recovery project). I switched to it because I was frustrated with the very problem you are having, and gave TWRP a shot and never looked back. I make backups quite frequently and I needed the option of deleting individual backups at will. You can install it with ez recovery. Give it a shot sometime.

apacseven said:
The best I can do since I dont use CWM myself and dont really feel like installing it just to check (sorry) is quote the person that pointed out to me that it can be disabled. Hope this helps.
FWIW I use and prefer TWRP (team win recovery project). I switched to it because I was frustrated with the very problem you are having, and gave TWRP a shot and never looked back. I make backups quite frequently and I needed the option of deleting individual backups at will. You can install it with ez recovery. Give it a shot sometime.
Click to expand...
Click to collapse
Okay thanks. I can't find the option they're talking about. Thanks for your help.

Iirc if you chose backup to external sd card wont it put each backup in its own dated dir inside the clockworkmod dir?
Sent from my CleanRom'd Galaxy SIII

x714x said:
Iirc if you chose backup to external sd card wont it put each backup in its own dated dir inside the clockworkmod dir?
Click to expand...
Click to collapse
Thats what it was doing when I stopped using it, but each folder was only 20mb. The rest of the data was going into the blobs folder.

how to tell if bootloader is unlocked after rooting...

followed this thread http://forum.xda-developers.com/showthread.php?t=2046439 yesterday to root my samsung galaxy s3 and unlock the bootloader, but i am unsure if it worked 100%. i know it is rooted because i dl'ed titanium backup and it works, but how do i tell if my bootloader is unlocked or not? did a search, couldn't find an answer, so i am asking here.

There's not really a concrete way to tell however if you reboot and the Samsung logo flashes by in a second then you're unlocked. Typically it sits for three to five seconds on this screen but once unlocked, this screen just flashes by.
Sent from my SCH-I535 using xda app-developers app

considering we all use the same unlocked aboot.img, it's pretty easy to concretely verify that you're bootloader is unlocked.
but im too stupid to write a script, and no one wants to do it because it's a bit longer than timing the samsung boot logo (which when you compare time-invested to information given, is pretty reliable)
basically involves comparing the md5 of the aboot.img of your phone to the known unlocked aboot.img (will try to find the terminal/adb shell commandsi posted before)
found it:
The unlocked md5 is: 0ba9ad45fc15cf3d62af7dd363686b3f
So if you pull a copy of your current aboot partition and save it to your sd card.
Run the following in ADB shell or terminal. Make sure you run it as superuser:
dd if=/dev/block/mmcblk0p5 of=/storage/sdcard0/aboot.img
That command will save an aboot.img to your internal sd. Check it's md5 and see if it matches.
Can run in adb:
md5 /storage/sdcard0/aboot.img
or
use any of the many md5 checking apps out there

SlimSnoopOS said:
There's not really a concrete way to tell however if you reboot and the Samsung logo flashes by in a second then you're unlocked. Typically it sits for three to five seconds on this screen but once unlocked, this screen just flashes by.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
ok, cool, thanks! so it looks like the root took, but the bootloader didn't unlock. the samsung logo took 3 seconds to pass by. so what do i need to do now to unlock it? should i repeat the steps from what i did yesterday?

corbn89 said:
considering we all use the same unlocked aboot.img, it's pretty easy to concretely verify that you're bootloader is unlocked.
but im too stupid to write a script, and no one wants to do it because it's a bit longer than timing the samsung boot logo (which when you compare time-invested to information given, is pretty reliable)
basically involves comparing the md5 of the aboot.img of your phone to the known unlocked aboot.img (will try to find the terminal/adb shell commandsi posted before)
found it:
The unlocked md5 is: 0ba9ad45fc15cf3d62af7dd363686b3f
So if you pull a copy of your current aboot partition and save it to your sd card.
Run the following in ADB shell or terminal. Make sure you run it as superuser:
dd if=/dev/block/mmcblk0p5 of=/storage/sdcard0/aboot.img
That command will save an aboot.img to your internal sd. Check it's md5 and see if it matches.
Can run in adb:
md5 /storage/sdcard0/aboot.img
or
use any of the many md5 checking apps out there
Click to expand...
Click to collapse
I'm gonna bookmark this cuz this is a really good explanation. I don't ever suggest dd methods (nor memorize them) cuz I know a single typo could brick the device.
a.demarco said:
ok, cool, thanks! so it looks like the root took, but the bootloader didn't unlock. the samsung logo took 3 seconds to pass by. so what do i need to do now to unlock it? should i repeat the steps from what i did yesterday?
Click to expand...
Click to collapse
Just sideload EZ Unlock v1.2 and press the unlock button. You'll hear an audio confirmation and boom, unlocked.

ok, so now i am confused. i have the correct supersu+bootloader on the sd card, and the supersu app on the phone, but the samsung logo still takes a while to disappear.
edit: nevermind, got it working, samsung logo now just flashes by. thanks again for all your help!

SlimSnoopOS said:
I'm gonna bookmark this cuz this is a really good explanation. I don't ever suggest dd methods (nor memorize them) cuz I know a single typo could brick the device.
Just sideload EZ Unlock v1.2 and press the unlock button. You'll hear an audio confirmation and boom, unlocked.
Click to expand...
Click to collapse
Yep, it's pretty straightforward. I tested my unlocked bootloader with this. Haven't had a chance to tested while locked though (will have to wait till my next odin to stock).
But yeah, as long as no one switches the "if" and the "of" it should be safe (aka accidentally pasting something into the normally inaccessible partition rather than copying out to the sd)
---------- Post added at 10:32 AM ---------- Previous post was at 10:29 AM ----------
a.demarco said:
ok, so now i am confused. i have the correct supersu+bootloader on the sd card, and the supersu app on the phone, but the samsung logo still takes a while to disappear.
Click to expand...
Click to collapse
sometime that image doesn't take for whatever reason. just use the app slimsnoop os linked to, should do the trick

a.demarco said:
ok, so now i am confused. i have the correct supersu+bootloader on the sd card, and the supersu app on the phone, but the samsung logo still takes a while to disappear.
edit: nevermind, got it working, samsung logo now just flashes by. thanks again for all your help!
Click to expand...
Click to collapse
Great! Just so you know, you can uninstall EZ Unlock (if you installed it that is) and never use it again. You will not need it again unless you do the following which which will re-lock your bootloader:
1) take a Verizon OTA
2) Odin flash a stock image
Make sure to do a nandroid and happy flashing!

SlimSnoopOS said:
Great! Just so you know, you can uninstall EZ Unlock (if you installed it that is) and never use it again. You will not need it again unless you do the following which which will re-lock your bootloader:
1) take a Verizon OTA
2) Odin flash a stock image
Make sure to do a nandroid and happy flashing!
Click to expand...
Click to collapse
still learning all about this, i will have to search what a nandroid is. i am doing a backup currently using titanium backup (free version right now), and it seems to be working well.
i want to flash either the cm 10.1 or jellybeans v.15 i think, just gotta read more about them.

a.demarco said:
still learning all about this, i will have to search what a nandroid is. i am doing a backup currently using titanium backup (free version right now), and it seems to be working well.
i want to flash either the cm 10.1 or jellybeans v.15 i think, just gotta read more about them.
Click to expand...
Click to collapse
Ahh, you'll see a lot of terms thrown around like that haha here's a glossary of common terms taken from DroidStyle's guide in the dev section.
Basically a nandroid is a complete system or rom backup akin to a computer backup. You perform a nandroid in custom recovery (CWM or TWRP) however its labeled as "Backup" in both recoveries. "Nandroid" is just the common name for it. The reason you perform a nandroid is to have a safe point to restore your phone to if you flash a rom, kernel, or mod and your phone begins to misbehave. Before flashing your first rom, it's highly recommended that you perform a nandroid in your custom recovery and even save a copy on a computer so you always have that in two places. It may take about 1.5-2 GB's of space per backup so I wouldn't keep too many on your phone at a time.

SlimSnoopOS said:
Ahh, you'll see a lot of terms thrown around like that haha here's a glossary of common terms taken from DroidStyle's guide in the dev section.
Basically a nandroid is a complete system or rom backup akin to a computer backup. You perform a nandroid in custom recovery (CWM or TWRP) however its labeled as "Backup" in both recoveries. "Nandroid" is just the common name for it. The reason you perform a nandroid is to have a safe point to restore your phone to if you flash a rom, kernel, or mod and your phone begins to misbehave. Before flashing your first rom, it's highly recommended that you perform a nandroid in your custom recovery and even save a copy on a computer so you always have that in two places. It may take about 1.5-2 GB's of space per backup so I wouldn't keep too many on your phone at a time.
Click to expand...
Click to collapse
good to know... should i bother with titanium backup at all? or just boot into cwm and do a nandroid from there?

a.demarco said:
good to know... should i bother with titanium backup at all? or just boot into cwm and do a nandroid from there?
Click to expand...
Click to collapse
Perform both actually. Backup apps with TB so when you flash a rom you can restore apps at once if you actually like the rom. I typically restore a few apps when trying new roms then if I like the rom, I'll restore more apps. Backup with CWM so that in case you dislike the rom you flash, you can completely restore to your previous rom. They serve two similar functions yet distinctly different as well.

SlimSnoopOS said:
Perform both actually. Backup apps with TB so when you flash a rom you can restore apps at once if you actually like the rom. I typically restore a few apps when trying new roms then if I like the rom, I'll restore more apps. Backup with CWM so that in case you dislike the rom you flash, you can completely restore to your previous rom. They serve two similar functions yet distinctly different as well.
Click to expand...
Click to collapse
awesome, thank you for the help. doing the nandroid backup right now through cwm, backing it up to the external sd card so i can then save it to the computer.
so i should only use the tb to back up the apps? oops, i backed everything up on it, was wondering why it took so damn long!

a.demarco said:
awesome, thank you for the help. doing the nandroid backup right now through cwm, backing it up to the external sd card so i can then save it to the computer.
so i should only use the tb to back up the apps? oops, i backed everything up on it, was wondering why it took so damn long!
Click to expand...
Click to collapse
No problem! Yea, TB is useful for a lot once you have a grasp of the basic functions. Only backup user apps and do not backup/restore system apps. Depending on the number of apps and their storage size, backup time varies. You can always delete the previous TB backup files cuz its stored in the Titanium Backup folder of your internal or external sdcard. Doesn't hurt to copy that to a computer every once in awhile too.

corbn89 said:
considering we all use the same unlocked aboot.img, it's pretty easy to concretely verify that you're bootloader is unlocked.
but im too stupid to write a script, and no one wants to do it because it's a bit longer than timing the samsung boot logo (which when you compare time-invested to information given, is pretty reliable)
basically involves comparing the md5 of the aboot.img of your phone to the known unlocked aboot.img (will try to find the terminal/adb shell commandsi posted before)
found it:
The unlocked md5 is: 0ba9ad45fc15cf3d62af7dd363686b3f
So if you pull a copy of your current aboot partition and save it to your sd card.
Run the following in ADB shell or terminal. Make sure you run it as superuser:
dd if=/dev/block/mmcblk0p5 of=/storage/sdcard0/aboot.img
That command will save an aboot.img to your internal sd. Check it's md5 and see if it matches.
Can run in adb:
md5 /storage/sdcard0/aboot.img
or
use any of the many md5 checking apps out there
Click to expand...
Click to collapse
So when I start up terminal emulator, next to where it says "[email protected]:/ $" I type in su right? Then hit enter? Then on the following line I type: "dd if=/dev/block/mmcblk0p5 of=/storage/sdcard0/aboot.img"
After I type this a copy of aboot.img will be saved to my external memory card and from there I can match it up with the unlocked md5 and if it matches this garuntees that my bootloader is unlocked. Is this correct?
I'm a noob, please forgive me.

jricks said:
So when I start up terminal emulator, next to where it says "[email protected]:/ $" I type in su right? Then hit enter? Then on the following line I type: "dd if=/dev/block/mmcblk0p5 of=/storage/sdcard0/aboot.img"
Click to expand...
Click to collapse
Correct.
After I type this a copy of aboot.img will be saved to my external memory card and from there I can match it up with the unlocked md5 and if it matches this garuntees that my bootloader is unlocked. Is this correct?
I'm a noob, please forgive me.
Click to expand...
Click to collapse
It will save to your internal sdcard. sdcard0 = internal storage, sdcard1 = external sdcard.
Sent from my SCH-I535 using xda app-developers app

Much appreciated my friend.
Sent from my SCH-I535 using xda app-developers app

Let us know what your results are and which method you used to unlock.
I confirmed it on my phone that used the ez unlock app but multiple trials by others would be beneficial. Thanks

SlimSnoopOS said:
Correct.
It will save to your internal sdcard. sdcard0 = internal storage, sdcard1 = external sdcard.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I did everything mentioned above and it saved to my internal card however im unable to view it. What program do i to install to view it.
Sent from my SCH-I535 using xda app-developers app

You don't need to view it. You just need to run the file through a md5 checksum app or check the md5 with terminal or adb using the command I posted earlier

[Q] Bootloop, Need Help!

Hi everyone,
Long story short, my device wont boot. Ive got TWRP. I have the backup on my computer, but when i plug my phone in, i cant move the backup to my TWRP Backup directory because there is no way of getting to the internal storage. Im a noob with adb and i have no clue how to use it so can someone help with that. Thanks! :crying:

adb shell
mount /data
exit
adb push c:\users\provickers\desktop\backupfile /data/media/0/whereverTWRPbackupsGO
Sent from my Nexus 5 using Tapatalk

http://forum.xda-developers.com/showthread.php?t=2513701
[TUTORIAL] How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5
sent from my HAMMERHEAD

CRIME INC. said:
http://forum.xda-developers.com/showthread.php?t=2513701
[TUTORIAL] How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5
sent from my HAMMERHEAD
Click to expand...
Click to collapse
Not really an option...

rootSU said:
adb shell
mount /data
exit
adb push c:\users\provickers\desktop\backupfile /data/media/0/whereverTWRPbackupsGO
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
that means nothing to me. can you write that in super duper nooby language please

Just read the adb stickie in q&a then
Sent from my Nexus 5 using Tapatalk

rootSU said:
Just read the adb stickie in q&a then
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I do adb shell
then mount /data
and it says: mounting /dev/block/mmcblk0p28 on /data failed: device or resource busy
Im currently in the home screen of TWRP

Maybe its already mounted by twrp in the mounts menu. If it is, skip that step. If not, mount in that menu
Sent from my Nexus 5 using Tapatalk

rootSU said:
Maybe its already mounted by twrp in the mounts menu. If it is, skip that step. If not, mount in that menu
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
alright thanks alot, hopefully it works!

rootSU said:
Maybe its already mounted by twrp in the mounts menu. If it is, skip that step. If not, mount in that menu
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Can u tell me where the twrp backups directory is? Coz obviously i cant get into my phone

I don't use twrp myself so im not sure where it is. If you use the ls command..... (thats LS in lowercase)
Eg....
ls /data/media/0
That will list all the directories on sdcard. I assume there will be a folder called twrp there. Within there not sure. But you can use ls to keep drilling down.
ls /data/media/0/twrp
I think there's a backup folder with dated folsers within it.
Take a twrp backup now and see....
Sent from my Nexus 5 using Tapatalk

Yes, the path's correct... TWRP makes a backup in /data/media/0/TWRP/3282387328 (random string)...
So, you will need to push the backup folder to /data/media/0/TWRP/... Now it will show up in the restore option.

vin4yak said:
Yes, the path's correct... TWRP makes a backup in /data/media/0/TWRP/3282387328 (random string)...
So, you will need to push the backup folder to /data/media/0/TWRP/... Now it will show up in the restore option.
Click to expand...
Click to collapse
Presuming he has the content of the random string folder, but not the folder itself, can he create a random string folder manually? Or must he take a backup and use that folder?
Sent from my Nexus 5 using Tapatalk

rootSU said:
Presuming he has the content of the random string folder, but not the folder itself, can he create a random string folder manually? Or must he take a backup and use that folder?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Like you, I've stuck with Philz for a long long time now.. Can't say for sure about twrp. I guess there's no harm in trying to make a folder and check.
However, sometimes while doing that, I faced a md5 mismatch error in twrp. But that's on a HTC One X.. No idea whether twrp has changed this since then.

rootSU said:
I don't use twrp myself so im not sure where it is. If you use the ls command..... (thats LS in lowercase)
Eg....
ls /data/media/0
That will list all the directories on sdcard. I assume there will be a folder called twrp there. Within there not sure. But you can use ls to keep drilling down.
ls /data/media/0/twrp
I think there's a backup folder with dated folsers within it.
Take a twrp backup now and see....
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I get "Permissions Denied". This is probably why nothing is working! What can i do?

ProVickers said:
Can u tell me where the twrp backups directory is? Coz obviously i cant get into my phone
Click to expand...
Click to collapse
/sdcard/TWRP/BACKUPS/your device serial number
Find the serial number in settings, about phone, status
Sent from my Nexus 5

Can't get to settings without booting phone.
OP can we keep this to one thread please? Its going to get confusing
Sent from my Nexus 5 using Tapatalk

i dont know why people dont do this, maybe they are worried of the little bit of space it takes in their storage, but i ALWAYS, since feb of 2009, keep a copy of my current rom and kernel in my storage. if i ever mess up doing anything, i always have my rom/kernel to flash again. no relying on computers(as im rarely around them). also, i always have one nandroid backup in my storage, just in case. it might not always be the most recent, but its there just in case.

@ProVickers
I'm not 100% sure of this but adb in TWRP doesn't work everywhere... You need to go to Advanced-Sideload.. then swipe right and then fire the adb push command..
rootSU said:
Can't get to settings without booting phone.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
He can get the serial number from the bootloader, right?

simms22 said:
i dont know why people dont do this, maybe they are worried of the little bit of space it takes in their storage, but i ALWAYS, since feb of 2009, keep a copy of my current rom and kernel in my storage. if i ever mess up doing anything, i always have my rom/kernel to flash again. no relying on computers(as im rarely around them). also, i always have one nandroid backup in my storage, just in case. it might not always be the most recent, but its there just in case.
Click to expand...
Click to collapse
Agreed.
Although i always have my rom, kernel and titanium backup. My nandoids move to my NAS as i don't have the space. However, I never modify anything that may require a restore when I'm away from home
Sent from my Nexus 5 using Tapatalk

Recover deleted files with mac

Hello,
yes this has probably been a problem to many people, but I couldn't find a solution for my case.
I flashed a ROM and forgot to backup my files before, so now my whole photos and files I need are gone.
I am looking for a solution to restore deleted photos on my nexus 5. I obviously can't use generic recovery methods because, well, I don't have a sd card to pull out and plug into my computer.
is there a app / method to recover deleted files directly on the nexus (over adb?)?
Paid solutions are welcome too!

Check this thread, has a topic on OTG, which happens to allow mounting as usb storage. Might do the trick.

Hmm the OTG part is about mounting devices on the nexus. I want it the other way around, mount it on my mac and run recovery software on it.
Any ideas on that?

Can't be done.
Only options are whats in my signature. Section 5.4
Sent from my Nexus 5 using Tapatalk

Aqua3 said:
Hello,
yes this has probably been a problem to many people, but I couldn't find a solution for my case.
I flashed a ROM and forgot to backup my files before, so now my whole photos and files I need are gone.
I am looking for a solution to restore deleted photos on my nexus 5. I obviously can't use generic recovery methods because, well, I don't have a sd card to pull out and plug into my computer.
is there a app / method to recover deleted files directly on the nexus (over adb?)?
Paid solutions are welcome too!
Click to expand...
Click to collapse
you can give this a try and it works great with nexus5 does job well http://www.android-data-recovery.org/android-data-recovery
u need a paid version ,it restores your contact ,messages,pic and files fine just put it on deep scan and let it do the rest later restore

rootSU said:
Can't be done.
Only options are whats in my signature. Section 5.4
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes, I am currently trying a option cross linked in that guide.
I'm taking a raw image of my data partition to my mac and will try to restore data there.
Steps taken from here - http://forum.xda-developers.com/gal...de-internal-memory-data-recovery-yes-t1994705. Although for windows, but finding the needed tools for mac is not that big of a task.
Will report if I have any success on this

Aqua3 said:
Yes, I am currently trying a option cross linked in that guide.
I'm taking a raw image of my data partition to my mac and will try to restore data there.
Steps taken from here - http://forum.xda-developers.com/gal...de-internal-memory-data-recovery-yes-t1994705. Although for windows, but finding the needed tools for mac is not that big of a task.
Will report if I have any success on this
Click to expand...
Click to collapse
Yep, we always love to hear a success story. Thanks!

This Data Recovery enables you to recover lost photos, videos, documents and more other files from your nexus 5, you can have a try.
t.co/IRVeusio2J

You've mentioned, " I don't have a sd card to pull out and plug into my computer", actually, you could apply to some app that could identify your device directly.
Here is an Android Data Recovery Mac that may help. You can also google other apps if you need.