I'm sorry for posting such a newbie thread but I'm rather stuck at the moment. I rooted my device earlier this week without much hassle. I was pretty excited and tried to get to customizing right away and ended up somewhat screwing up my device. I've tried following just about every solution that google will give me for Nandroid restore but I still can't achieve restoration.
Maybe someone can tell me what I'm doing wrong. I have been trying this method:
Phone in recovery mode
-in command prompt-
cd c:\(directory)
adb devices - it will show "000000000000 recovery"
adb shell - gives me "#"
cd /sdcard - I've tried with and without this step
nandroid-mobile.sh --restore - At this point it asks me about G1 keyboard or just continue, so I hit enter and get
error: unable to mount /sdcard, aborting
I've also tried to mount /sdcard after the adb shell step
and it returns:
mounting /dev/block/mmcblk0p1 on /sdcard failed: No such file or directory
but typing ls at the same point lists all the files on that level, including sdcard.
could it be my SD card is corrupt? I'm very confused, I really hope someone can help. Any replies or PMs would be very very appreciated. Thanks in advance!
1. hold the volume button down and press the end call button
2. press home button once the white/green screen comes up to go to recovery
3. scroll down and choose backup/restore
4. choose your backup file and restore
You don't need to do all of that other stuff unless your nandroid backup file is not working and gives you errors..............and usually if it gives you errors, its because the nandroid file was renamed in which case you just need to change it back to its proper name.
I had the same exact thing happen. Somehow the sd card is corrupted (just a guess on my part). Here is what I did:
Copy the entire contents of your sd card to a folder on your PC (this is so you don't lose anything on your sd card).
Reboot into recovery and re-partition your sd card making sure you upgrade the ext partition to ext3.
Do a complete wipe (Caution this will reset your phone, I am not responsible for any data you may lose).
reflash your nandroid backup and if that doesn't work reflash the rom zip file of the rom you were using.
Hopefully you have a nandroid backup or at least titanium backup for the apps you had installed (will make your life easier).
Copy the contents from the folder you created in the first step back to your SD card.
These steps fixed my problem. It MIGHT fix yours.
I hope this helps.
Peter
n01un0 said:
2. press home button once the white/green screen comes up to go to recovery
Click to expand...
Click to collapse
???
once the phone is powered down, all i do is hold home while pressing the end key.. takes me right to the recovery screen...
im not trying to be mean an not help but...PLEASE POST IN THE RIGHT SECTION and you might get more help!
ive never seen that problem from experience so im really no help. your best bet is post this thread in the Q&A section. I would bet tho by whats its saying like above that your SD CARD is corrupt somehow. just reformat(but make sure to backup the sd card), then try again.
n01un0 said:
1. hold the volume button down and press the end call button
2. press home button once the white/green screen comes up to go to recovery
3. scroll down and choose backup/restore
4. choose your backup file and restore
You don't need to do all of that other stuff unless your nandroid backup file is not working and gives you errors..............and usually if it gives you errors, its because the nandroid file was renamed in which case you just need to change it back to its proper name.
Click to expand...
Click to collapse
When I do it that way, it tells me to run nandroid backup via ADB..
prios914 said:
I had the same exact thing happen. Somehow the sd card is corrupted (just a guess on my part). Here is what I did:
Copy the entire contents of your sd card to a folder on your PC (this is so you don't lose anything on your sd card).
Reboot into recovery and re-partition your sd card making sure you upgrade the ext partition to ext3.
Do a complete wipe (Caution this will reset your phone, I am not responsible for any data you may lose).
reflash your nandroid backup and if that doesn't work reflash the rom zip file of the rom you were using.
Hopefully you have a nandroid backup or at least titanium backup for the apps you had installed (will make your life easier).
Copy the contents from the folder you created in the first step back to your SD card.
These steps fixed my problem. It MIGHT fix yours.
I hope this helps.
Peter
Click to expand...
Click to collapse
Thank you, I will get started on it today and let you know how it goes.
Also, sorry for posting in the wrong section. I thought it related to development but I will be sure to post anything like this in Q&A from now on.
-Jake
**Edit**
Thank you, Peter! I backed everything up and repartitioned the card, upgraded to ext3 like you said. After that I rebooted into recovery and tried nand restore from my device and it started up right away. Didn't have to wipe my device and everything is back to normal! Thanks so much!!
-Jake
Good to hear u got everything worked out bud.
Sent from my HERO200 using XDA App
okay that solved my hour and a half long struggle. thanks peter.
Hello, need some help here!
I unlocked the bootloader without backing up any of my files... I know I'm stupid... I was too carried away by the 4.4.2 improvements to think properly...
I tried this recovery method from this thread:
http://forum.xda-developers.com/showthread.php?t=1994705&nocache=1
and another similar one
But in both cases I am stucked at the first step: adb saying device is offline in cygwin.
Adb in the android sdk works fine. I'm on 4.4.2 ota from stock 4.2.2 (rogers), managed to flash twrp and got root.
I've tried revoking usb authorization but no go.
Is there any mighty guru who can help me out? Is there some way of mounting the internal storage in windows so that i can image the whole internal storage?
Any help greatly appreciate! Don't want to lose precious photos of my family...
cilix said:
Hello, need some help here!
I unlocked the bootloader without backing up any of my files... I know I'm stupid... I was too carried away by the 4.4.2 improvements to think properly...
I tried this recovery method from this thread:
http://forum.xda-developers.com/showthread.php?t=1994705&nocache=1
and another similar one
But in both cases I am stucked at the first step: adb saying device is offline in cygwin.
Adb in the android sdk works fine. I'm on 4.4.2 ota from stock 4.2.2 (rogers), managed to flash twrp and got root.
I've tried revoking usb authorization but no go.
Is there any mighty guru who can help me out? Is there some way of mounting the internal storage in windows so that i can image the whole internal storage?
Any help greatly appreciate! Don't want to lose precious photos of my family...
Click to expand...
Click to collapse
i have no idea what you are trying to do or what you have done.
so far this is what i have understood
you have unlocked your bootloader and install TWRP and SuperSU
so you have root access
now you are wanting to back you device up.
if this is what you are trying to do then just boot to TWRP and click on backup and make a nandroid back and move on.
with a nandroid back up if you ever install anything that stops your device from booting or cause FC all you do is boot back into TWRP and click restore and click on your nandroid back up and it will restore your phone just like it was when you created the backup.
Sorry for bad focus in writing, it was 5am+ and I was very desperate...
I had unlocked the bootloader without first doing a backup, thus the unlocking process wiped my data.
I had it unlocked so that I could flash twrp and root, which I then succeeded in doing so.
Now, I hope to recover the wiped data. As Moto X only has internal storage, I can't mount it as a drive in windows and do recovery that way.
The thread I found had a particular method of imaging the whole internal storage so that recovery could be done by loading the image in windows.
But by using that method, I can't get adb (of cygwin) to connect to my phone properly. It lists the phone but says device is offline.
Does anyone know how I can get adb (cygwin) to connect to my phone properly?
Or is there another method of recovering wiped data in internal storage?
Thanks for any help!
cilix said:
Sorry for bad focus in writing, it was 5am+ and I was very desperate...
I had unlocked the bootloader without first doing a backup, thus the unlocking process wiped my data.
I had it unlocked so that I could flash twrp and root, which I then succeeded in doing so.
Now, I hope to recover the wiped data. As Moto X only has internal storage, I can't mount it as a drive in windows and do recovery that way.
The thread I found had a particular method of imaging the whole internal storage so that recovery could be done by loading the image in windows.
But by using that method, I can't get adb (of cygwin) to connect to my phone properly. It lists the phone but says device is offline.
Does anyone know how I can get adb (cygwin) to connect to my phone properly?
Or is there another method of recovering wiped data in internal storage?
Thanks for any help!
Click to expand...
Click to collapse
ok i understand what you are trying to do but your not understanding how the moto x storage system works
there is 2 storage locations on are phone. Internal and emulated external(virtual SD card)
so when you do a factory reset or go into TWRP and click Wipe it wipes the internal storage only leaving the SD card files there
but the virtual sd card only contains your Pics/Downloads/and Some App Data but it dose not have your actual phone data like installed apps and setting so forth. so when you wipe your data there is no way to recovery your system you have to start over. the only thing left is going to be downloads some app data pics and other things you moved to your phone via your PC.
What i would do is rebuild your phone the way you want it and then do a nandroid backup via TWRP and then you wont have to deal with this issue again i normally make a new nandroid backup every week and delete the old one and then i make another backup via Titanium Backup.
Thanks dray_jr, for your detailed explanation.
I just found out the adb version in cygwin is outdated. I'll try to update it and see if it could work.
I don't want to give up hope yet
Dear community,
About a year after i really wanted to root my htc one mini 2, i decided I wanted to factory reset my phone.
So after this year I forgot everything i knew, and managed to wipe the whole OS...
I would really appreciate any hints that might help me to fix my phone again.
Info on where i'm standing with the problem:
1. I tried to find my stock ROM on this site and couldn't because under "firmware" i can only find 2.18.161.2, though mine is 2.18.166.1 - does this matter? It's the vodafone one, and they even have a nandroid backup for my version, but not the stock firmware.
2. I have TWRP installed, and the site tells me i need to have my bootloader locked to flash stock roms. I have no problem relocking or unlocking it, but in the relocked state, i can not access TWRP recovery and use the sideload feature to flash the rom. The phone always goes back to the bootloader screen and the title says " **security warning** ".
3. i would really like to get my phone back as close to it's stock state as possible.
I am kind of afraid of flashing the available stock firmware, as I don't know how to proceed from there without TWRP.
I read a lot about this topic, but i'm kind of loosing it right now...
Can some kind soul lend me their wisdom and help me out?
Would be much appreciated
mfG Montor
Hi,
You can either get put back everything to stock, as in flash stock recovery, relock the bootloader, get the available version from their site but the version number should be higher than the one already installed, however with S-Off you can flash any version.
Or
Leave everything as it is and perform a Nandroid restore.
What file are you getting from the website, is it RUU file, ROM, is it exe or zip ?, RUU will be beneficial to put back to complete stock with proper conditions met ?
WITH CUSTOM RECOVERY YOU CANNOT FLASH STOCK ROM.
TryllZ said:
Hi,
You can either get put back everything to stock, as in flash stock recovery, relock the bootloader, get the available version from their site but the version number should be higher than the one already installed, however with S-Off you can flash any version.
Or
Leave everything as it is and perform a Nandroid restore.
What file are you getting from the website, is it RUU file, ROM, is it exe or zip ?, RUU will be beneficial to put back to complete stock with proper conditions met ?
WITH CUSTOM RECOVERY YOU CANNOT FLASH STOCK ROM.
Click to expand...
Click to collapse
I would actually really like to put everything back to stock, because the reason for the root is somewhat gone now.
As already mentioned, I sadly can not find the stock recovery that i need.
I need the Vodafone x.xx.166.x format, and the closest i get would be the Vodafone x.xx.161.x format of the stock recovery.
What happens if i try to flash the available one? Do I brick my phone once again, or does it say something like "recovery version not matching device version" ?
Also, if by any chance the flash is successfull and the stock recovery x.xx.161.x is on my phone, how can i flash the stock firmware without TWRP?
Though I really like the idea of a more or less complete stock phone, I could totally go with the nandroid backup too.
The problem is, I already downloaded the files but as my OS is gone and i didn't turn on usb-debugging, i can not move a single file onto my device. (I assume that's the issue, because my adb push file /sdcard/TWRP/Backups didn't quite work...
Edit: Because you asked, I don't actually know what would be the best solution right now, but the only file fitting my device version is the nandroid backup, but there are RUUs for x.xx.161.x - which, as already mentioned, is the closest i can get to x.xx.166.x
Montor said:
I would actually really like to put everything back to stock, because the reason for the root is somewhat gone now.
As already mentioned, I sadly can not find the stock recovery that i need.
I need the Vodafone x.xx.166.x format, and the closest i get would be the Vodafone x.xx.161.x format of the stock recovery.
What happens if i try to flash the available one? Do I brick my phone once again, or does it say something like "recovery version not matching device version" ?
Also, if by any chance the flash is successfull and the stock recovery x.xx.161.x is on my phone, how can i flash the stock firmware without TWRP?
Though I really like the idea of a more or less complete stock phone, I could totally go with the nandroid backup too.
The problem is, I already downloaded the files but as my OS is gone and i didn't turn on usb-debugging, i can not move a single file onto my device. (I assume that's the issue, because my adb push file /sdcard/TWRP/Backups didn't quite work...
Edit: Because you asked, I don't actually know what would be the best solution right now, but the only file fitting my device version is the nandroid backup, but there are RUUs for x.xx.161.x - which, as already mentioned, is the closest i can get to x.xx.166.x
Click to expand...
Click to collapse
Here's how you can do it without developer option enabled.
- Make sure device is 100% charged, if you don't know how much charge exists, leave the device on charge for about 1-2 hours.
- Find an MMC of 4GB (Hoping your MMC slot is working)
- You will need Serial Number of your device for Nandroid restore, you can get it from the device box with IMEI stickers.
For RUU (zip file)
- Download the available RUU and rename it to 0P8BIMG.zip (I'm assuming its the same a normal HTC One Mini 2)
- Copy the file into the root of the MMC
- Insert MMC into device
- Boot up device and enter boot loader
- As the device enters bootloader it will automatically start flashing, if all conditions are met.
NB: I frankly can't remember if this will work with TWRP installed.
For Nandroid restore.
- THIS STEP NEEDS BE DONE FROM A PC, Extract all files from the Nandroid restore zip, connect the MMC to the PC.
- In the root folder of the MMC create a TWRP folder and inside it create a folder named BACKUPS and inside this create a folder named YOUR DEVICE SERIAL NUMBER (I haven't tested it with a different named folder so I don't know) inside this folder create a folder with the OS version number of your device and inside this folder place all extracted files.
- Put the MMC into the device.
- Enter TWRP and choose restore
- Locate the folder created in the earlier step, the TWRP Backup folder with files extracted in it.
- Let TWRP restore.
- As far as my knowledge goes it should work fine.
I will advise that you do a restore from Nandroid, because you have TWRP working this is the easiest method, to get the phone up and running then you can decide to go for RUU by enabling developer options and more.
I'm using a Nnadroid restore more than 6 months now, no problem whatsoever.
Good Luck
TryllZ said:
Here's how you can do it without developer option enabled.
- Make sure device is 100% charged, if you don't know how much charge exists, leave the device on charge for about 1-2 hours.
- Find an MMC of 4GB (Hoping your MMC slot is working)
- You will need Serial Number of your device for Nandroid restore, you can get it from the device box with IMEI stickers.
For Nandroid restore.
- THIS STEP NEEDS BE DONE FROM A PC, Extract all files from the Nandroid restore zip, connect the MMC to the PC.
- In the root folder of the MMC create a TWRP folder and inside it create a folder named BACKUPS and inside this create a folder named YOUR DEVICE SERIAL NUMBER (I haven't tested it with a different named folder so I don't know) inside this folder create a folder with the OS version number of your device and inside this folder place all extracted files.
- Put the MMC into the device.
- Enter TWRP and choose restore
- Locate the folder created in the earlier step, the TWRP Backup folder with files extracted in it.
- Let TWRP restore.
- As far as my knowledge goes it should work fine.
I will advise that you do a restore from Nandroid, because you have TWRP working this is the easiest method, to get the phone up and running then you can decide to go for RUU by enabling developer options and more.
I'm using a Nnadroid restore more than 6 months now, no problem whatsoever.
Good Luck
Click to expand...
Click to collapse
That is exactly where I'm stuck with my nandroid backup.
I just can't seem to find a way to push the folder with all the files onto my sd-card.
I tried with "adb push \myfolder /sdcard/TWRP/Backups/myphonesnumberthingy", but it gives me "Device not found" error.
The device is connected, and with "fastboot devices" it shows in the list.
Did I miss something important here?
All the drivers are installed, and I shouldn't be able to lock and unlock the bootloader if the device wasn't properly connected right?
Edit: Nevermind, it seems I can't read. I will try to put my sd-card out of my phone and connect it to my pc somehow
Montor said:
That is exactly where I'm stuck with my nandroid backup.
I just can't seem to find a way to push the folder with all the files onto my sd-card.
I tried with "adb push \myfolder /sdcard/TWRP/Backups/myphonesnumberthingy", but it gives me "Device not found" error.
The device is connected, and with "fastboot devices" it shows in the list.
Did I miss something important here?
All the drivers are installed, and I shouldn't be able to lock and unlock the bootloader if the device wasn't properly connected right?
Edit: Nevermind, it seems I can't read. I will try to put my sd-card out of my phone and connect it to my pc somehow
Click to expand...
Click to collapse
Use an MMC reader for working your MMC with a PC.
Your device connecting to your PC in the bootloader does not mean your commands will work, ADB works with device switched on, in bootloader its fastboot and NOT ADB.
TryllZ said:
Use an MMC reader for working your MMC with a PC.
Your device connecting to your PC in the bootloader does not mean your commands will work, ADB works with device switched on, in bootloader its fastboot and NOT ADB.
Click to expand...
Click to collapse
So i have an adapter for connecting the MMC to my PC.
I plug it in, and it shows me THIS.
Inside my recovery, if I use the file manager, I can't seem to access/find a single set of directories that looks like the one above...
Montor said:
So i have an adapter for connecting the MMC to my PC.
I plug it in, and it shows me THIS.
Inside my recovery, if I use the file manager, I can't seem to access/find a single set of directories that looks like the one above...
Click to expand...
Click to collapse
Have you extracted files from the Nandroid Backup zip and placed them into TWRP>Backups>Phone Serial Number>OS Version Number folder
Now, in TWRP choose Restore from the main screen, and locate the folder where your files are placed.
When in Restore, make sure you choose Storage: Micro SDCard at the top below Time, Battery and CPU.
TryllZ said:
Have you extracted files from the Nandroid Backup zip and placed them into TWRP>Backups>Phone Serial Number>OS Version Number folder
Now, in TWRP choose Restore from the main screen, and locate the folder where your files are placed.
When in Restore, make sure you choose Storage: Micro SDCard at the top below Time, Battery and CPU.
Click to expand...
Click to collapse
Yes i did extract the files in the zip, and placed them in TWRP/BACKUPS/serial/osversion.
But there is no way to locate it or access it.
When i open the file manager in TWRP, i see directories like "boot, cache, data, dev, devlog" etc, and also sdcard and external_sd.
External_sd is empty, and opening sdcard gives me only the directory created by my own nandroid backup, with the path /sdcard/TWRP/BACKUPS/HT533WR02324/2016-07-17--08-52-32.
Edit: Okay now we are getting closer to solving this.
I tried to change TWRP backup from internal storage to micro sdCard - but it shows (0MB) beside it.
Choosing it either way, does nothing. The checkbox internal storage stays checked.
I'm going to restart my phone and see if something changes...
Edit2: Did nothing, unfortunately.
If i remove the card, the box can't be checked.
If i insert it again and tap on it, it stays highlighted for about 4 seconds and then internal storage is still checked :/
Montor said:
Yes i did extract the files in the zip, and placed them in TWRP/BACKUPS/serial/osversion.
But there is no way to locate it or access it.
When i open the file manager in TWRP, i see directories like "boot, cache, data, dev, devlog" etc, and also sdcard and external_sd.
External_sd is empty, and opening sdcard gives me only the directory created by my own nandroid backup, with the path /sdcard/TWRP/BACKUPS/HT533WR02324/2016-07-17--08-52-32.
Edit: Okay now we are getting closer to solving this.
I tried to change TWRP backup from internal storage to micro sdCard - but it shows (0MB) beside it.
Choosing it either way, does nothing. The checkbox internal storage stays checked.
I'm going to restart my phone and see if something changes...
Edit2: Did nothing, unfortunately.
If i remove the card, the box can't be checked.
If i insert it again and tap on it, it stays highlighted for about 4 seconds and then internal storage is still checked :/
Click to expand...
Click to collapse
Firstly it shouldn't show you 0MB for SDCard, anyway, place the extracted Nandroid files in the /sdcard/TWRP/BACKUPS/HT533WR02324/2016-07-17--08-52-32 folder and then try again, if this folder is accessible then it should work.
MB: YOUR CONSTANT USE OF THE TERM FILE MANAGER IN TWRP IS GIVING ME AN IMPRESSION THAT YOU ARE ACCESSING THE FILE MANAGER IN TWRP WHERE AS YOU HAD TO PRESS THE RESTORE BUTTON FROM THE MAIN SCREEN, THE FILE MANAGER BUTTON IS DIFFERENT ALTOGETHER IN TWRP.
TryllZ said:
Firstly it shouldn't show you 0MB for SDCard, anyway, place the extracted Nandroid files in the /sdcard/TWRP/BACKUPS/HT533WR02324/2016-07-17--08-52-32 folder and then try again, if this folder is accessible then it should work.
MB: YOUR CONSTANT USE OF THE TERM FILE MANAGER IN TWRP IS GIVING ME AN IMPRESSION THAT YOU ARE ACCESSING THE FILE MANAGER IN TWRP WHERE AS YOU HAD TO PRESS THE RESTORE BUTTON FROM THE MAIN SCREEN, THE FILE MANAGER BUTTON IS DIFFERENT ALTOGETHER IN TWRP.
Click to expand...
Click to collapse
Oh it appears I didn't mention this.
The folder i CAN see, is inside the internal storage under "/sdcard/TWRP/BACKUPS/HT533WR02324/2016-07-17--08-52-32" - and I can't access the internal storage, i would have pushed the files if that was possible.
No no, I use the backup function to locate my nandroid backup files.
But with the backup function, I couldn't change directories and look for files so I used the file manager to do that.
The file manager doesn't allow me to change to sd card either way, so that doesn't work.
Edit:
The sd-card i have inside my phone right now is 64gb big - is it possible that this is too big to be recognized?
I also have a 32gb one, would that make a difference?
Montor said:
Oh it appears I didn't mention this.
The folder i CAN see, is inside the internal storage under "/sdcard/TWRP/BACKUPS/HT533WR02324/2016-07-17--08-52-32" - and I can't access the internal storage, i would have pushed the files if that was possible.
No no, I use the backup function to locate my nandroid backup files.
But with the backup function, I couldn't change directories and look for files so I used the file manager to do that.
The file manager doesn't allow me to change to sd card either way, so that doesn't work.
Edit:
The sd-card i have inside my phone right now is 64gb big - is it possible that this is too big to be recognized?
I also have a 32gb one, would that make a difference?
Click to expand...
Click to collapse
As per spec, this device supports 64GB too but I myself use a 32GB one, so yes you can try that and again you will need to access TWRP restore through the RESTORE button in TWRP main screen and NOT BACKUP button.
What you can do is copy the /sdcard/TWRP/BACKUPS/HT533WR02324/2016-07-17--08-52-32 folder into you SDCard TWRP folder and place the extracted files in this folder and try a restore.
TryllZ said:
As per spec, this device supports 64GB too but I myself use a 32GB one, so yes you can try that and again you will need to access TWRP restore through the RESTORE button in TWRP main screen and NOT BACKUP button.
What you can do is copy the /sdcard/TWRP/BACKUPS/HT533WR02324/2016-07-17--08-52-32 folder into you SDCard TWRP folder and place the extracted files in this folder and try a restore.
Click to expand...
Click to collapse
Okay it seems my 32gb one is broken, it's showing up but not as a mass storage.
Well if I could access the sd card with twrp at all, that would really help me - but I can't.
Backup botton and restore button behave the same when choosing the Micro SDcard (0MB).
And with the file manager, accessing the sd card gives me an empty directory...
Edit: Googling this problem tells me I need to format my card, as TWRP doesn't recognize it.
I read FAT32 somewhere, I read exFAT somewhere, what format does TWRP work with?
Montor said:
Okay it seems my 32gb one is broken, it's showing up but not as a mass storage.
Well if I could access the sd card with twrp at all, that would really help me - but I can't.
Backup botton and restore button behave the same when choosing the Micro SDcard (0MB).
And with the file manager, accessing the sd card gives me an empty directory...
Edit: Googling this problem tells me I need to format my card, as TWRP doesn't recognize it.
I read FAT32 somewhere, I read exFAT somewhere, what format does TWRP work with?
Click to expand...
Click to collapse
First can I know if you can see any file/folder in SD when accessing it through Restore in TWRP ?
Format it as exFat, hopefully it should work..
You mentioned its not showing as Mass Storage, what is it showing up as ?
TryllZ said:
First can I know if you can see any file/folder in SD when accessing it through Restore in TWRP ?
Format it as exFat, hopefully it should work..
Click to expand...
Click to collapse
First, through restore I can't navigate to other folders at all.
All I can do there, is tapping on Internal storage and choosing micro SDcard - which doesn't work.
It's like TWRP knows there is a sd card in my phone, but somehow can't access it.
That's why I assume it's due to it's formatting.
Switching folders/directories is only possible with the file manager with the advanced button - but this only shows me two things.
1. External_sd --> shows me an empty directory
2. sdcard --> shows me the folder where TWRP created the backup folder when I did the backup myself. (I assume that's the internal storage because under the restore button, this is the only thing that i shows up)
I read somewhere, that exFAT is only recognized by TWRP if you have a newer version of the recovery installed.
I don't know exactly but the version i'm using is definitely on of the first versions that came out.
Also, I checked my SD-card on my laptop, and apparently it allready is exFAT.
Edit: I was talking about the 32gb card not showing up.
I don't think it really matters, but my description wasn't very accurate.
The SD-card (32gb) is shown as the SD-card like it should, but the PC doesn't show any kind of used/free space bar underneath it.
Also, opening it gives a message like "There is no card connected"
Montor said:
First, through restore I can't navigate to other folders at all.
All I can do there, is tapping on Internal storage and choosing micro SDcard - which doesn't work.
It's like TWRP knows there is a sd card in my phone, but somehow can't access it.
That's why I assume it's due to it's formatting.
Switching folders/directories is only possible with the file manager with the advanced button - but this only shows me two things.
1. External_sd --> shows me an empty directory
2. sdcard --> shows me the folder where TWRP created the backup folder when I did the backup myself. (I assume that's the internal storage because under the restore button, this is the only thing that i shows up)
I read somewhere, that exFAT is only recognized by TWRP if you have a newer version of the recovery installed.
I don't know exactly but the version i'm using is definitely on of the first versions that came out.
Also, I checked my SD-card on my laptop, and apparently it allready is exFAT.
Edit: I was talking about the 32gb card not showing up.
I don't think it really matters, but my description wasn't very accurate.
The SD-card (32gb) is shown as the SD-card like it should, but the PC doesn't show any kind of used/free space bar underneath it.
Also, opening it gives a message like "There is no card connected"
Click to expand...
Click to collapse
The SDCard not showing free space bars is windows could possibly mean SDCard error.
FAT, FAT32 and exFAT work for Android so yes if you format it in any of these it ought to work. exFAT format is most commonly used in mobile devices in terms of SDCard.
Card disconnecting in Windows, I am guessing your card is having I/O issues, what this means is that if you try and format it and the MMC disconnects during the format process there is a chance it will be permanently damaged.
What you can do is just use Quick Format, this will not check for any errors, however if there is any sector errors in the MMC, flasing through TWRP could cause unexpected problems if that sector is accessed.
Advisably get a working 4GB SDcard to avoid any hiccups.
TryllZ said:
The SDCard not showing free space bars is windows could possibly mean SDCard error.
FAT, FAT32 and exFAT work for Android so yes if you format it in any of these it ought to work. exFAT format is most commonly used in mobile devices in terms of SDCard.
Card disconnecting in Windows, I am guessing your card is having I/O issues, what this means is that if you try and format it and the MMC disconnects during the format process there is a chance it will be permanently damaged.
What you can do is just use Quick Format, this will not check for any errors, however if there is any sector errors in the MMC, flasing through TWRP could cause unexpected problems if that sector is accessed.
Advisably get a working 4GB SDcard to avoid any hiccups.
Click to expand...
Click to collapse
I have the 64gb one i was always using, and the not working 32gb one.
Both are exFat.
I just wanted to know if it might work formatting the 64gb one
Edit: Concerning formatting, this is the thread I was referring to.
Montor said:
I have the 64gb one i was always using, and the not working 32gb one.
Both are exFat.
I just wanted to know if it might work formatting the 64gb one
Edit: Concerning formatting, this is the thread I was referring to.
Click to expand...
Click to collapse
The device supports 64GB and so does TWRP, now concerning your SDCard, yes it would work (as long as its hardware-error free)..
I'm using TWRP version 2.8.5.0 and my SDCard is exFAT and works fine with TWRP..could be that older versions of TWRP might not support exFAT but I personally can't confirm that as which is the older version that you are using.
TryllZ said:
The device supports 64GB and so does TWRP, now concerning your SDCard, yes it would work (as long as its hardware-error free)..
I'm using TWRP version 2.8.5.0 and my SDCard is exFAT and works fine with TWRP..could be that older versions of TWRP might not support exFAT but I personally can't confirm that as which is the older version that you are using.
Click to expand...
Click to collapse
Update!
I realized, it's probably really the 64gb sd card, that's the issue here.
I took the 4gb one out of my fathers phone - bam.
TWRP recognized it immediately and restore is in progress!!!
Will keep updating!
Edit: IT F*ING WORKED!
Thank you SO much for your help!!!
Is there any way I can give you somethign in return?
Montor said:
Update!
I realized, it's probably really the 64gb sd card, that's the issue here.
I took the 4gb one out of my fathers phone - bam.
TWRP recognized it immediately and restore is in progress!!!
Will keep updating!
Edit: IT F*ING WORKED!
Thank you SO much for your help!!!
Is there any way I can give you somethign in return?
Click to expand...
Click to collapse
Great...:good::good::good:
Frankly I never imagined it could be the 64GB, I was purely under the assumption TWRP would accept 64GB MMC, anyway I lacked that information but now I know.
Nope, its working now is more than enough for me.
My Note4's power switch failed (again). This will be the 5th one I've had in 2 years.
Despite the poor hardware quality and reliability, I like the phone and want to keep it for a while longer.
So I got a refurbished replacement, which I wanted to "clone" using TWRP's nandroid backup.
Before starting, I verified the new phone had exactly the same version (5.1.1, N910TUVU2DOK2), and it did.
Then I installed TWRP (twrp-3.0.2-0-trltetmo.img.tar) on the new phone with Odin, and booted into TWRP recovery, and installed UPDATE-SuperSU-v2.76-20160630161323.zip for systemless root, so the new phone was identical (although I suspect the nandroid restore would overwrite that anyway?)
On my original phone I booted to TWRP (luckily TiBack has boot to recovery since the power switch is bad). and backed up everything (except cache - used default options selected) to the ExtSD card.
Then I powered down, and moved the ExtSD card and SIM from the old phone to the new phone.
Important trick: To get TWRP restore to even recognize the backup is there, I had to rename the /TWRP/BACKUPS/xxxxxxxx code to new phones 8 digit ID (can be found with ADB devices)
On the new phone, I boot to TWRP, and Restore Data and System. I did not restore Boot, Modem, or Recovery.
I restarted the new phone, and it took a bit longer than normal but booted to my exact setup. It looked promising at first. It connected to LTE, and Wi-Fi, made a call, etc. Apps and settings appeared to be loaded and ran. ExtSD card with existing photos was visible to Camera and Gallery.
But then I started getting errors about the SDcard not being available. Next I discovered apps couldn't find their databases. I connected by USB and looked at the internal storage and compared it to my backups.
On the old phone the directory /storage/emulated/legacy/Android/data contains over 250 folders such as com.android.chrome.
On the new phone, after restoring, /storage/emulated/legacy/Android/data contains about 50 folders.
So my process of restoring Data and System did not actually restore all the data. What did I miss?
Update - I've continued to research this. I read this article, this article on partitions, and this article, and other posts on this forum about TWRP and Nandroid. I still don't see anything wrong with the procedure I followed. All the internal data should be backed up into the Data partition.
Further update: I found this article: What is EXCLUDED from a TWRP backup?
It's quite unexpected that a backup that is an "image" of a partition would exclude anything, but putting that aside, it is not obvious what is excluded.
The article says "Creating a backup of the user data partition will NOT include /data/media (your internal storage)!"
But where that "internal storage" is located in the filesystem?
As I browse from the root of the file system over FTP, the root / directory contains directories like .system, etc, proc, mnt, bin, and others that are common to unix/linux. One of those is /storage, which contains /storage/emulated/0. At that level I see what I would consider the "internal storage" These directories also appear as a folder named "Phone" when the phone is connected to a computer by USB. Folders like Alarm, Download, Movies, Pictures, Playlists are found here. There is a folder called data, but it does not contain a folder called media as referenced in the exclusion statement above.
/storage also contains /storage/extSdCard, which has the contents seen in the folder shared as Card over USB.
At the root of the file system there is another folder called data, but it is not accessible, either from on the phone with a root-level file explorer, or remotely by FTP.
In conclusion, my experience shows that all Internal Storage ( /storage/emulated/0) is indeed excluded from the Nandroid backup. It is still unclear why the note refers to internal storage as /data/media, though. That particular location does not seem to exist, at least on this phone with Android 5.1.1
/storage contains the mount points that the file systems for the internal storage, SD card, and any OTG storage attached to the phone.
Here's the working procedure for "cloning" a phone: copying an image of a phone to another identical phone.
1) Make a Nandriod Backup of the source phone (one way is with TWRP recovery backup function), store to MicroSD
2) Remove the MicroSD card, and mount it on a computer. Locate the folder /TWRP/BACKUPS/xxxxxxxx, where xxxxxxxx is the ID of the source phone, which can be seen using "ADB devices" when the phone is connected by USB. Find the ID of the new phone, and rename the folder to that ID. Otherwise, TWRP restore will not see the backup.
3) insert the MicroSD card and SIM from the source phone into the destination phone. Boot to recovery. Perform TWRP restore from the set with the current date. Reboot to Android. At this point the destination phone should boot normally, although it seems to be slower the first time.
4) Connect the source phone and the destination phone to a computer by USB, Synchronize the Internal data (mounted as MTP device) from the source to the destination phone. (TWRP Backup does not include the Internal data partition). It would probably be better to do this from recovery, I tried to do that, but was unable to cause the Internal partition to mount over USB while in TWRP recovery. So I let both phones boot to Android and synced that way. Reboot destination phone again to make sure apps find the new data on Internal. Power off source phone if desired.
Additional items that had to be done to restore the previous state:
Systemless root did not survive. I had to boot back to recovery and reinstall UPDATE-SuperSU-v2.76-20160630161323.zip. You could probably do that in recovery right after the restore, but I cannot confirm since I didn't do it that way.
Wi-Fi passwords were not retained. I had to re-enter.
All Bluetooth devices have to be re-paired, since the new phone has a different MAC address.
If you use an IP address reservation, it has to be updated with the new Wi-Fi MAC address.
Re-set Smart Lock if you use it
Re-activate any software that is registered to a specific phone rather than your Google account.