Okay, the problem is -- I recently installed a theme on my internal storage, and no matter what I do, it doesn't want to uninstall. I tried going to start-settings-syystem-remove programs, but it didn't work. I tried running the cab file and letting it uninstall but it didn't work. So, i think the only other option is a hard reset. But, i want to back up everything on my internal storage. However, if i backup everything then restore, the theme will still be 'installed' correct? All i want from this is the theme uninstalled. I have the cab files of my other programs so i could easily load them up after the hard reset. I do want to keep my pictures and videos etc. Any ideas on how to accomplish this?
If you do a hard reset it will leave your internal storage intact, with no programs, or themes installed, you can then safely remove whatever folders/files it created on your internal storage when you installed it.
However you will need to reinstall each of you proggies as well that you need.
Maybe you could change the file extension, that could help if you want to delete the file.
I want to clear my internal storage with my hard reset, so if I save my backup file onto my internal storage, won't the backup file be deleted?
yes.....back things up on your pc if you are deleting both device and internal storage. PC backup is crucial anyway.
A hard reset won't clear your internal memory as well, you'll need to format that using the phone.
Well i want to format the internal storage so I have to go to start-settings-system-clear storage? But before that I probably should send everything to my PC so I can just send it to my phone after, correct?
Steps
1) send everything to your pc
2) after the transfer, begin to delete files from Internal using your PC
3) hard reset phone (will bring you back to manufactures specs with what ever rom you have)
Would i delete files from internal via my PC with ActiveSync? That doesn't seem to work for me half of the time.
To get the fastest response, when you connect the usb cable choose the Disk option, this will load the internal memory as a memory stick / flash drive in your My Computer, from there you can backup what you need and then format the drive. Putting it in Disk Mode is more or less same as ActiveSync but syncs direct with the internal memory chip so allows for faster file transfer
Steps one and two completed. Should I do a hard reset and press volume down instead of volume up? Or shouls i clear storage?
If you have backed up what you need, format the internal storage from either your PC or phone, then do the Hard Reset. Once done your back to square one, out of the box type with your phone.
I remember having a similar problem when I was trying to install a clock...
No matter how I tried to remove it, it just wouldnt remove completely. The name was no longer appearing in the "Remove Programs" list but there were still bits and pieces of the clock on my today screen...
Eventually, I just installed another clock over it and when I went to remove this new clock, it seems the uninstall process also removed the junk that was left over from my initial install... Everything was back to normal after that and I didnt need to do a hard-reset...
Maybe give that a go...
Did the clear storage, and walah the theme is gone. And opera now works. Thanks guys.
Glad you got it sorted mate, love how HTC make there devices so easy to manage, with some other phones if that had happened, you would be stuck.
Yet with the HTC I can flash ROM's as often as I like to try different ones, etc, almost change them as often as I reinstall my desktop and pc with all the beta testing I do. Nicely done HTC.
Really pulling my hair out over this issue. I installed the latest version of the GPE Lollipop 5.0.1 ROM that can be found in the Development section on my HK One M8, clean flash and everything with the .zip located at the root of my internal storage, and now when I boot up, I can't access any of my files. I have no pictures, no music, no download folder, etc. When I try to locate my files in ES File Explorer, nothing comes up, and when I plug my phone into my desktop, the only folder I have is "Ringtones". I've read a couple posts that suggest using TWRP to format the entire storage, but I have no external SD card to install a ROM from. Added to this, when I choose "Mount" in TWRP and plug into the desktop, nothing happens. USB OTG isn't even an option that I can select, it just sits there and never actually checks the checkbox. This never happened while I was using digitalhigh's GPE ROM (the one in the Verizon development section), and I'm just at a complete loss right now. Any assistance would be greatly appreciated, thanks.
Edit: Strangely enough, when I use TWRP'S file browser, even when choosing to flash a .zip file, I can see everything there, all my files right where I left them, all the folders still intact.
getinnocuous said:
Really pulling my hair out over this issue. I installed the latest version of the GPE Lollipop 5.0.1 ROM that can be found in the Development section on my HK One M8, clean flash and everything with the .zip located at the root of my internal storage, and now when I boot up, I can't access any of my files. I have no pictures, no music, no download folder, etc. When I try to locate my files in ES File Explorer, nothing comes up, and when I plug my phone into my desktop, the only folder I have is "Ringtones". I've read a couple posts that suggest using TWRP to format the entire storage, but I have no external SD card to install a ROM from. Added to this, when I choose "Mount" in TWRP and plug into the desktop, nothing happens. USB OTG isn't even an option that I can select, it just sits there and never actually checks the checkbox. This never happened while I was using digitalhigh's GPE ROM (the one in the Verizon development section), and I'm just at a complete loss right now. Any assistance would be greatly appreciated, thanks.
Edit: Strangely enough, when I use TWRP'S file browser, even when choosing to flash a .zip file, I can see everything there, all my files right where I left them, all the folders still intact.
Click to expand...
Click to collapse
I have the same exact issue right now. I happened just as you described it; flashing the 5.0.1 GPE ROM. I CAN get into the storage, however, when I mount my phone to my computer through TWRP. A BIG problem, however, is that I can't copy any files into the phone. I get a "File size limit exceeded" message.
I did some digging here and on other forums and it would SEEM that something happened during the ROM flash that completely changed the file system. Where it used to be FAT32 (I think), it now says "Generic Hierarchical." This particular file system apparently only has a file limit of 4 gigs. Anything above that and it won't accept it.
I'm currently trying to find a way to fix this but I've got nothing. I can't even flash a new ROM or anything because I'm locked out of my phone's storage.
getinnocuous said:
Really pulling my hair out over this issue. I installed the latest version of the GPE Lollipop 5.0.1 ROM that can be found in the Development section on my HK One M8, clean flash and everything with the .zip located at the root of my internal storage, and now when I boot up, I can't access any of my files. I have no pictures, no music, no download folder, etc. When I try to locate my files in ES File Explorer, nothing comes up, and when I plug my phone into my desktop, the only folder I have is "Ringtones". I've read a couple posts that suggest using TWRP to format the entire storage, but I have no external SD card to install a ROM from. Added to this, when I choose "Mount" in TWRP and plug into the desktop, nothing happens. USB OTG isn't even an option that I can select, it just sits there and never actually checks the checkbox. This never happened while I was using digitalhigh's GPE ROM (the one in the Verizon development section), and I'm just at a complete loss right now. Any assistance would be greatly appreciated, thanks.
Edit: Strangely enough, when I use TWRP'S file browser, even when choosing to flash a .zip file, I can see everything there, all my files right where I left them, all the folders still intact.
Click to expand...
Click to collapse
Sorry if I am replying too late, but I ended up in this same boat and this was the top result for what I was searching for on Google and the symptoms were exactly the same, I could see my files on TWRP but it seems like internal storage wasn't being mounted when booting into the rom. What I ended up doing was using TWRP's File Manager (under Advanced menu) to copy the contents of the internal storage to my external sd card. After that I did an advanced wipe and included internal storage (which seems to format it) and finally internal storage became available when booted into a rom again, and I didn't even have to sacrifice my files.
My Workaround/Fix
Although I don't own an HTC One, I encountered the same problem after flashing a ported ROM to a BLU Studio-G. So I'm sharing my Workaround/Fix: Reboot to recovery (TWRP in my case); Make a backup of the current ROM; Recovery will create another folder inside the original TWRP/Backup folder; After the backup completes, hit 'Restore' and make a note of the location of that folder; return to main menu and reboot.
I used Root Explorer but I imagine other competent File Managers can be used: Now move the other backup folders to the new location in the TWRP/Backup folder and that should solve the problem. All backup folders will again be available to be restored in Recovery. :good::victory: Hope this helps someone else before having to purchasing a wig
First of all, sorry for the bit of a text wall below, but if you could bare with me, I really need help and would greatly appreciate any comments that could be of help. Thank you.
So I was looking at a thread on how to do something so I changed two lines on build.prop. I made a back up of the original build.prop file. So my phone was able to start up but everything was invisible and couldn't do anything other than use my notification shade and respond to messages. I ended up turning on emergency mode then I turned it off right after and that fixed it. I guess I messed up when I copy and pasted the original build.prop and replaced it with the one that made my phone mess up in the first place. This messed it up my phone even more and now it's in a bootloop. I can only go into ODIN download mode and recovery. I tried clearing system cache but that didn't help at all. The first time my phone messed up it showed up as a drive on a few different computers that I used, but once the bootloop started it won't be recognized as a drive on any of the three computers I tried. It shows up as "Gadget Serial" when in download mode and when it's powered off it shows as SAMSUNG_Android. I have installed the Samsung phone drivers on two of the computers but that didn't help either.
When it shows up as SAMSUNG_Android it shows that MTP USB Device didn't install properly. I was thinking maybe that's what is causing the problem? I am using the original usb cable that came with the phone. Odin recognizes it so I could always restore it with a ROM, but I need to backup my photos (to my fault, I haven't done a backup in awhile) before I restore it to a fresh ROM. No android file explorers show it either, or a root explorer like Droid Explorer. I've also tried to connect it to a mac (third computer) but that doesn't show up either.
Some person suggested to me to restore with a ROM that saves data, but to no avail, I couldn't find one (anybody know of any?)
I was also reading about using the wipe data/factory reset, but I couldn't get a straight answer if it deletes or keeps the data in the SD Card section on the internal storage (does anybody know?)
So I feel like I might be screwed and may lose my photos and other data. If I could connect my phone to my computer properly, I might be able to edit build.prop again to fix the problem. If I can't connect it to my computer ever, is there any other way I could back up my photos or other data? I have a OTG cable if that helps at all.
Some additional info: I'm on a stock ROM, stock kernal, and rooted. And yes I had R/W on when editing build.prop.
So any ideas guys, I really need to get my phone up and running again.
Thanks in advanced.
Just reflash the stock ROM through ODIN.
EncryptedCurse said:
Just reflash the stock ROM through ODIN.
Click to expand...
Click to collapse
That won't delete my data (i.e. my photos and and other files on sd card portion)?
FrostyChill said:
That won't delete my data (i.e. my photos and and other files on sd card portion)?
Click to expand...
Click to collapse
i dont have an answer to that question, but whats more important - fixing ur phone or keeping ur now-unaccessable-anyway files?
i THINK replacing a rom does not delete ur data, but i highly recommend waiting for someone else to chime in as I am completely unsure and just going off what i think i've read before.
take this as a lesson, any time you are going to play with system files (be it in a phone or computer), backup anything you care about, and be prepared to lose what you dont.
Flashing rom doest wipe the data in the external sd card but it do wipe the internal storage i recommend flashing a rom after taking out your sd card
jassi150 said:
Flashing rom doest wipe the data in the external sd card but it do wipe the internal storage i recommend flashing a rom after taking out your sd card
Click to expand...
Click to collapse
considering this is the S6 forum, its safe to assume hes talking about an S6, which means its safe to assume he cant do that.
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.