Related
I know the obvious ans would be to use 4ext superwipe.
What I want is like re-writing those partitions with all memory locations set to zeroes. The 4ext full wipe only works like quick format in windows desktop.
Any ideas how to do it?
____________________
Solved. See post 17 for details.
pushpann said:
I know the obvious ans would be to use 4ext superwipe.
What I want is like re-writing those partitions with all memory locations set to zeroes. The 4ext full wipe only works like quick format in windows desktop.
Any ideas how to do it?
Click to expand...
Click to collapse
Had to search a bit, but found an article that explains how to do this. It links to 3 apps (havn't tested myself, just remember there's no going back), from the description the first one only works on SD card, the second one might (it does not mention which partitions it formats), and the last one seems to be removed.
I did not read the whole article, but I suggest you do that before doing anything.
Good luck.
pushpann said:
I know the obvious ans would be to use 4ext superwipe.
What I want is like re-writing those partitions with all memory locations set to zeroes. The 4ext full wipe only works like quick format in windows desktop.
Any ideas how to do it?
Click to expand...
Click to collapse
Hi,
A RUU will reset everything back to stock, and fix any partition issues.
Is that what you are after?
malybru said:
Hi,
A RUU will reset everything back to stock, and fix any partition issues.
Is that what you are after?
Click to expand...
Click to collapse
As he said, he wants it to be completely formatted, meaning no data can be recovered, which is like a hard full wipe - no way to restore.
RUU does format the data partition, but it only removes records of files, and the data itself is still available and possible to read (until new files will be written over it).
No! I dont want to get involved with RUU stuff.. I just want to completely wipe my phone.. Like complete formatting of the USB drives. All system and data partitions set to zeroes.
In simple words, if you do quick formating on pendrives, you can restore (some or all data before format, depends on what you've put on the drive after format ) using some Data Recovery tools.
What i believe is that recovery just wipes the memory addresses, without putting zeroes on all the memory locations. have been googling for this for almost a week, haven't got any clue yet!
pushpann said:
I know the obvious ans would be to use 4ext superwipe.
What I want is like re-writing those partitions with all memory locations set to zeroes. The 4ext full wipe only works like quick format in windows desktop.
Any ideas how to do it?
Click to expand...
Click to collapse
I would do it this way (this is something I came up with, and if it screws up anything, you are responsible) :
Write a script that reformat your nand rom and then dumps (creates) a huge file containing zeroes. Then reformat using 4ext and repartition.
I am curious, why exactly do you want to do this? The lack of results from Google would suggest that this is not something people would normally do.
JAM THAT THANKS BUTTON.
Happy to help.
I assume you're not going to use the phone after?
If you aren't going to use the phone after, one word. Sledgehammer.
If you are keeping the phone; create a file on the partition filled with rubbish (linux has a command for this). Make sure it fills the entire partition and then run mkfs.ext4 /dev/block/partition. Repeat a dozen times or create a script to do it for you.
It's easier than erasing the whole NAND disk and partitioning it. Mainly because you'll wipe the recovery partition and create an expensive paperweight. Which brings me back to sledgehammer.
Sent from my HTC
pushpann said:
No! I dont want to get involved with RUU stuff.. I just want to completely wipe my phone.. Like complete formatting of the USB drives. All system and data partitions set to zeroes.
In simple words, if you do quick formating on pendrives, you can restore (some or all data before format, depends on what you've put on the drive after format ) using some Data Recovery tools.
What i believe is that recovery just wipes the memory addresses, without putting zeroes on all the memory locations. have been googling for this for almost a week, haven't got any clue yet!
Click to expand...
Click to collapse
On my first commented I linked to an article which gives two ways to wipe your phone (set to zeroes and all). Here are the two apps:
https://play.google.com/store/apps/details?id=com.kovit.p.forevergone
https://play.google.com/store/apps/details?id=ch.ethz.infsyssec.sddroid
Try those to see if they format the Data partition.
Far_SighT said:
I would do it this way (this is something I came up with, and if it screws up anything, you are responsible) :
Write a script that reformat your nand rom and then dumps (creates) a huge file containing zeroes. Then reformat using 4ext and repartition.
I am curious, why exactly do you want to do this? The lack of results from Google would suggest that this is not something people would normally do.
JAM THAT THANKS BUTTON.
Happy to help.
Click to expand...
Click to collapse
Hmm.. My phone has become very laggy.. No matter what ROM flash, what firmware I flash.
DennisBold said:
I assume you're not going to use the phone after?
If you aren't going to use the phone after, one word. Sledgehammer.
If you are keeping the phone; create a file on the partition filled with rubbish (linux has a command for this). Make sure it fills the entire partition and then run mkfs.ext4 /dev/block/partition. Repeat a dozen times or create a script to do it for you.
It's easier than erasing the whole NAND disk and partitioning it. Mainly because you'll wipe the recovery partition and create an expensive paperweight. Which brings me back to sledgehammer.
Sent from my HTC
Click to expand...
Click to collapse
By hearing what you say, i kinda feel little scared to do these steps. Anyway thanks for the suggestion..
astar26 said:
On my first commented I linked to an article which gives two ways to wipe your phone (set to zeroes and all). Here are the two apps:
https://play.google.com/store/apps/details?id=com.kovit.p.forevergone
https://play.google.com/store/apps/details?id=ch.ethz.infsyssec.sddroid
Try those to see if they format the Data partition.
Click to expand...
Click to collapse
Those apps dont work.. By internal data they mean internal sdcard not system or data partition.
BTW just saw this app called lagfix. It says it will discard the unused blocks, but doesnot work on my phone.. Has anyone tried it? For me it's saying trim on system,data and cache not supported! DAMN
DennisBold said:
I assume you're not going to use the phone after?
If you aren't going to use the phone after, one word. Sledgehammer.
If you are keeping the phone; create a file on the partition filled with rubbish (linux has a command for this). Make sure it fills the entire partition and then run mkfs.ext4 /dev/block/partition. Repeat a dozen times or create a script to do it for you.
It's easier than erasing the whole NAND disk and partitioning it. Mainly because you'll wipe the recovery partition and create an expensive paperweight. Which brings me back to sledgehammer.
Sent from my HTC
Click to expand...
Click to collapse
Yeah, I had similar thoughts. I was going for repartition becasue then the whole of nandroid can be wiped in one go.
To clean the phone, sledgehammer / mowing the device with a car (or both, one after the other) are the best methods.
Here's one more idea. Create a pseudo nandroid backup with all of your nandroid partitions(/system /data /cache etc) filled with garbage/zeroes. Then restore that. And bam, the nandroid is hard formatted (after a quick format of course).
Like always, it's your phone. I am not responsible for anything that you do to it.
JAM THAT THANKS BUTTON.
Happy to Help.
pushpann said:
Hmm.. My phone has become very laggy.. No matter what ROM flash, what firmware I flash.
By hearing what you say, i kinda feel little scared to do these steps. Anyway thanks for the suggestion..
Those apps dont work.. By internal data they mean internal sdcard not system or data partition.
BTW just saw this app called lagfix. It says it will discard the unused blocks, but doesnot work on my phone.. Has anyone tried it? For me it's saying trim on system,data and cache not supported! DAMN
Click to expand...
Click to collapse
Tried it yesterday, it's meant for certain devices that did not use the TRIM command like they should (Many Nexus 7 tablets were slowed down by this issue), but it seems the Sensation does not need it (or at least our kernels do not support the command).
What seems as the only way to do so is to create many blank files and delete them (like many already said). you can create a large file and copy it a few times to the Data partition, which will fill it, and then delete it. using a normal file manager will work (or you can use "adb push" command to push the file a couple of times).
Far_SighT said:
Yeah, I had similar thoughts. I was going for repartition becasue then the whole of nandroid can be wiped in one go.
To clean the phone, sledgehammer / mowing the device with a car (or both, one after the other) are the best methods.
Here's one more idea. Create a pseudo nandroid backup with all of your nandroid partitions(/system /data /cache etc) filled with garbage/zeroes. Then restore that. And bam, the nandroid is hard formatted (after a quick format of course).
Like always, it's your phone. I am not responsible for anything that you do to it.
JAM THAT THANKS BUTTON.
Happy to Help.
Click to expand...
Click to collapse
You sure it does complete format while restoring nandroid? BTW i still am not sure how to fill system and data partitions with zeroes or garbage! Anyway thanks for the heads up
pushpann said:
You sure it does complete format while restoring nandroid? BTW i still am not sure how to fill system and data partitions with zeroes or garbage! Anyway thanks for the heads up
Click to expand...
Click to collapse
You shouldn't have to worry about formatting empty space. No one ever, except possibly computer forensics is going to want information from an empty phone. They have access to browsing history from Google, call records from your mobile provider and ban access details from your banks. They wouldn't need your phone. There are things that make it hard for the average person. Including mounting the NAND disk in a way that it can be opened like a normal disk drive, and then running the tools to restore data. If someone really wanted data it's possible but they will not go through all that for 500MB of bank details, porn or whatever people do with phones these days. If you're trying to hinder the police because you did something wrong, then you should just stop.
Theoretically it can be done through an android device but cross compiling tools to recover data is long and tedious to do. There is nothing so important that someone would spend hours creating tools for an Android device to restore data that may already be irrevocably gone. Not to mention the learning curve for new software. If you are worried, burn the device and buy something new. That is the general rule for sensitive data. Make sure it's gone before you move on.
It's safe to click "Format all partitions" and then erase your SD card and give your phone away.
If it helps, install Android on top. Choose something big. Most of your application data is stored on your SDCard FYI.
Lastly, if it's lag you are trying to fix. Go backwards with Android not forwards. JellyBean demands more than ICS and ICS demands more than GingerBread. Having the latest OS doesn't work for everyone. For example, Windows 8.1 doesn't work for me because there's no fastboot support without huge editing of system drivers. The same is true in Android. GingerBread stability may be more important than ICS or JB features, or JellyBean features may be more important. However don't expect lag free 4.2 or 4.3, our devices may work with it, but they were never intended to go above 4.1(Ville C2 updates stop there too I think) due to hardware limitations. Others may argue differently, but you should question the effort they're (including me) putting in with kernel and device tree upgrades. It's amazing work nonetheless but it basically shouldn't have to be done if the device were supported. Buy a new device if you want the latest and greatest. My Sensation has become a trophy for me to the amazing things you can do with one of HTCs first dual core phones. I don't expect it to work without some kinks and bugs or even fatal flaws but I still respect it for having running Sense 3.0 to 5.0 (yes I've tried it).
Sorry for the rant. I'm a little bit grumpy, but hope it helps explains why you can mostly erase and install a new version of android then throw the device away and be relatively safe.
There's probably going to be someone who reads all of this and thinks I'm crazy, to that guy or girl. Thanks for reading all of it!
Sent from my HTC
DennisBold said:
You shouldn't have to worry about formatting empty space. No one ever, except possibly computer forensics is going to want information from an empty phone. They have access to browsing history from Google, call records from your mobile provider and ban access details from your banks. They wouldn't need your phone. There are things that make it hard for the average person. Including mounting the NAND disk in a way that it can be opened like a normal disk drive, and then running the tools to restore data. If someone really wanted data it's possible but they will not go through all that for 500MB of bank details, porn or whatever people do with phones these days. If you're trying to hinder the police because you did something wrong, then you should just stop.
Theoretically it can be done through an android device but cross compiling tools to recover data is long and tedious to do. There is nothing so important that someone would spend hours creating tools for an Android device to restore data that may already be irrevocably gone. Not to mention the learning curve for new software. If you are worried, burn the device and buy something new. That is the general rule for sensitive data. Make sure it's gone before you move on.
It's safe to click "Format all partitions" and then erase your SD card and give your phone away.
If it helps, install Android on top. Choose something big. Most of your application data is stored on your SDCard FYI.
Lastly, if it's lag you are trying to fix. Go backwards with Android not forwards. JellyBean demands more than ICS and ICS demands more than GingerBread. Having the latest OS doesn't work for everyone. For example, Windows 8.1 doesn't work for me because there's no fastboot support without huge editing of system drivers. The same is true in Android. GingerBread stability may be more important than ICS or JB features, or JellyBean features may be more important. However don't expect lag free 4.2 or 4.3, our devices may work with it, but they were never intended to go above 4.1(Ville C2 updates stop there too I think) due to hardware limitations. Others may argue differently, but you should question the effort they're (including me) putting in with kernel and device tree upgrades. It's amazing work nonetheless but it basically shouldn't have to be done if the device were supported. Buy a new device if you want the latest and greatest. My Sensation has become a trophy for me to the amazing things you can do with one of HTCs first dual core phones. I don't expect it to work without some kinks and bugs or even fatal flaws but I still respect it for having running Sense 3.0 to 5.0 (yes I've tried it).
Sorry for the rant. I'm a little bit grumpy, but hope it helps explains why you can mostly erase and install a new version of android then throw the device away and be relatively safe.
There's probably going to be someone who reads all of this and thinks I'm crazy, to that guy or girl. Thanks for reading all of it!
Sent from my HTC
Click to expand...
Click to collapse
I dont wanna sell my phone and I know that my data isnt that valueable that anyone will try to read my data with hard efforts. My sensation used to perform awesome 2-3 months back, and now that I must have quick formatted my system and data partitions more than 1500 times, i think a full wipe may do some help for those nag n lag issues.
And about going back to GB? Man, Everyone feels GB is sad after using ICS/JB. If my phone doesnot stop lagging every second after I format these partitions, i think its time for a new phone!
Anyway thanks for such a detailed reply
pushpann said:
I dont wanna sell my phone and I know that my data isnt that valueable that anyone will try to read my data with hard efforts. My sensation used to perform awesome 2-3 months back, and now that I must have quick formatted my system and data partitions more than 1500 times, i think a full wipe may do some help for those nag n lag issues.
And about going back to GB? Man, Everyone feels GB is sad after using ICS/JB. If my phone doesnot stop lagging every second after I format these partitions, i think its time for a new phone!
Anyway thanks for such a detailed reply
Click to expand...
Click to collapse
The lag isn't from formatting. You can try ARHD ICS if you want. Or probably Sense 4+ with 4.1.2 but anything above that might not work out great.
Sent from my HTC
pushpann said:
I dont wanna sell my phone and I know that my data isnt that valueable that anyone will try to read my data with hard efforts. My sensation used to perform awesome 2-3 months back, and now that I must have quick formatted my system and data partitions more than 1500 times, i think a full wipe may do some help for those nag n lag issues.
And about going back to GB? Man, Everyone feels GB is sad after using ICS/JB. If my phone doesnot stop lagging every second after I format these partitions, i think its time for a new phone!
Anyway thanks for such a detailed reply
Click to expand...
Click to collapse
How old is your Sensation? I could well be that your nand is dying. In that case, repartition your phone and make /system and /data from parts seldom used (like /cache).
If you want data security, full encryption will keep noobs away.
Thanks for the replies guys!
Today i actually did the zeroing of the partitions with Nandroid method.. I download an app called dummy file creator and it created dummy files(files with zeroes all over it. after searching in internet it seemed legit method of fully zeroing out the memory locations) in data partition untill it ran out of memory. Then i copied those files to system partition too manually till it also became full(I had to do this manually because the app didnt support creating dummy files in system partition) and made nandroid of data and system separately then did almost a dozen time 4ext format and restoring the nandroid. Finally i formatted all the partitions and installed Codename Lungo ROM(CM10.1).
HELL YEAH! it feels FASTer. Not sure if its gonna last long.
pushpann said:
Thanks for the replies guys!
Today i actually did the zeroing of the partitions with Nandroid method.. I download an app called dummy file creator and it created dummy files(files with zeroes all over it. after searching in internet it seemed legit method of fully zeroing out the memory locations) in data partition untill it ran out of memory. Then i copied those files to system partition too manually till it also became full(I had to do this manually because the app didnt support creating dummy files in system partition) and made nandroid of data and system separately then did almost a dozen time 4ext format and restoring the nandroid. Finally i formatted all the partitions and installed Codename Lungo ROM(CM10.1).
HELL YEAH! it feels FASTer. Not sure if its gonna last long.
Click to expand...
Click to collapse
Just found something and wanted to add - for future reference - Android Tuner seems to be able to make the TRIM operation on all partitions on our sensation, in a much easier way.
pushpann said:
Thanks for the replies guys!
Today i actually did the zeroing of the partitions with Nandroid method.. I download an app called dummy file creator and it created dummy files(files with zeroes all over it. after searching in internet it seemed legit method of fully zeroing out the memory locations) in data partition untill it ran out of memory. Then i copied those files to system partition too manually till it also became full(I had to do this manually because the app didnt support creating dummy files in system partition) and made nandroid of data and system separately then did almost a dozen time 4ext format and restoring the nandroid. Finally i formatted all the partitions and installed Codename Lungo ROM(CM10.1).
HELL YEAH! it feels FASTer. Not sure if its gonna last long.
Click to expand...
Click to collapse
Can you guide me? i want to do that but i'm noob . how did you do that? pls help me
BSHD666 said:
Can you guide me? i want to do that but i'm noob . how did you do that? pls help me
Click to expand...
Click to collapse
hehe you found it:good:
Just wanted to check peoples thoughts on this. Had a 32GB Sandisk card corrupt (i think) on me the other day. Woke the phone and seen the SD card icon in the task bar as if it had just mounted the SD but it had unmounted it and said that there wasn't one inserted. Have yet to try it in a PC to see what (if any) files I can recover.
The previous night I had made a nandroid backup (Philz touch), there was something not quite right with the file sizes not showing on screen but it seemed to work the second time around. Can't recall if the card was formatted as FAT32 or exFAT, but if FAT32 could one of the nandroid files caused issues if it was over 4GB? Anyway going to see what I can possibly recover and if it can be reformatted again before possibly purchasing a 16GB Samsung card here: (http://www.7dayshop.com/samsung-plus-microsdhc-uhs-1-16gb-memory-card-class-10). Dont mind the smaller size if its more reliable.
gsmyth said:
Just wanted to check peoples thoughts on this. Had a 32GB Sandisk card corrupt (i think) on me the other day. Woke the phone and seen the SD card icon in the task bar as if it had just mounted the SD but it had unmounted it and said that there wasn't one inserted. Have yet to try it in a PC to see what (if any) files I can recover.
The previous night I had made a nandroid backup (Philz touch), there was something not quite right with the file sizes not showing on screen but it seemed to work the second time around. Can't recall if the card was formatted as FAT32 or exFAT, but if FAT32 could one of the nandroid files caused issues if it was over 4GB? Anyway going to see what I can possibly recover and if it can be reformatted again before possibly purchasing a 16GB Samsung card here: (http://www.7dayshop.com/samsung-plus-microsdhc-uhs-1-16gb-memory-card-class-10). Dont mind the smaller size if its more reliable.
Click to expand...
Click to collapse
I quite highly doubt a Samsung SD card will be more reliable. Don't know what's the fuss about SanDisk corrupted but I myself or anyone in my friend/colleague circle have yet to face a problem with SanDisk!
And the first thing you should do is format your card to exFAT, I really don't know how and why people uses FAT32
jujuburi said:
I quite highly doubt a Samsung SD card will be more reliable. Don't know what's the fuss about SanDisk corrupted but I myself or anyone in my friend/colleague circle have yet to face a problem with SanDisk!
And the first thing you should do is format your card to exFAT, I really don't know how and why people uses FAT32
Click to expand...
Click to collapse
This is the first problem I've had with it to be honest, had it or over a year and was using it in my HTC Sensation previously. I'm trying to remember if it was exFAT or FAT32, I remember a ROM (Google Edition S4 ROM) not being compatible with exFAT and checking mine out of curiosity, but just can't recall what it was and never flashed the ROM. I didn't reformat it coming from my Sensation so it hadn't changed in anyway.
Luckily all my photos were backed up to dropbox so nothing lost of too much importance. Need to get a microSD card reader to see if its completely borked or if files can be retrieved.
Someone will correct me if I'm wrong but I'm pretty sure that Nandriod breaks the files down smaller than 4GB if you're running on Fat32 so I doubt that'll be your problem. Mostly because the FAT32 architecture just won't accept a file that big unless the Linux kernel of Android ignores the limitations. I would HIGHLY recommend NOT restoring a nandroid backup if you think the sizes are off or if you're attempting to recover the data without and MD5 checksum. That's all sorts of bad juju.
As for Sandisk vs Samsung, I have both, I've never had a problem with either. My sammy card is in my TF201 and my Sandisk is in my I337 as it's a faster card from my benchmarks. But like I said, no problems with either.
As for data recovery, go check out Recuva, it's supposed to be pretty good especially for being free. Since I'm IT I have professional grade software for data recovery and don't have tons experience with Recuva. A couple tips about data recovery. Once you determine you want to recover data, DO NOT WRITE TO OR FORMAT THE CARD, that'll prove to make the entire process more difficult. it's going to take a good long time, at least an hour for the initial scan. Do all the work on the card from a computer and not through a connection to your phone. Anyway if you have any questions or possibly want some help shoot me a PM, I'm happy to impart my knowledge.
Theoriginalgiga said:
Someone will correct me if I'm wrong but I'm pretty sure that Nandriod breaks the files down smaller than 4GB if you're running on Fat32 so I doubt that'll be your problem. Mostly because the FAT32 architecture just won't accept a file that big unless the Linux kernel of Android ignores the limitations. I would HIGHLY recommend NOT restoring a nandroid backup if you think the sizes are off or if you're attempting to recover the data without and MD5 checksum. That's all sorts of bad juju.
As for Sandisk vs Samsung, I have both, I've never had a problem with either. My sammy card is in my TF201 and my Sandisk is in my I337 as it's a faster card from my benchmarks. But like I said, no problems with either.
As for data recovery, go check out Recuva, it's supposed to be pretty good especially for being free. Since I'm IT I have professional grade software for data recovery and don't have tons experience with Recuva. A couple tips about data recovery. Once you determine you want to recover data, DO NOT WRITE TO OR FORMAT THE CARD, that'll prove to make the entire process more difficult. it's going to take a good long time, at least an hour for the initial scan. Do all the work on the card from a computer and not through a connection to your phone. Anyway if you have any questions or possibly want some help shoot me a PM, I'm happy to impart my knowledge.
Click to expand...
Click to collapse
I thought it should break them down, it was just the /data partition that includes the apps and app cache, if it could be over 4GB stored as a .tar file would that still be broken down as such? Won't be attempting to restore the nandroid (if its even still recoverable) as I have flashed a pre-rooted stock odin firmware and its actually really smooth (maybe thats due to the sd card not being inserted). Although I seem to be having an issue flashing a custom ROM, as even after flashing the firmware via odin then trying to flash a ROM via Philz touch its still bootlooping (even with a wipe/factory reset and clean install format). Haven't attempted a different custom ROM but just havent had the time to test that out. Thinking I would have to download the original firmware files and start from scratch with rooting and adding a recovery to see if that solves it, but think I'm going to sit tight for the moment.
Thanks for the recommendation and the support, much appreciated.
gsmyth said:
I thought it should break them down, it was just the /data partition that includes the apps and app cache, if it could be over 4GB stored as a .tar file would that still be broken down as such? Won't be attempting to restore the nandroid (if its even still recoverable) as I have flashed a pre-rooted stock odin firmware and its actually really smooth (maybe thats due to the sd card not being inserted). Although I seem to be having an issue flashing a custom ROM, as even after flashing the firmware via odin then trying to flash a ROM via Philz touch its still bootlooping (even with a wipe/factory reset and clean install format). Haven't attempted a different custom ROM but just havent had the time to test that out. Thinking I would have to download the original firmware files and start from scratch with rooting and adding a recovery to see if that solves it, but think I'm going to sit tight for the moment.
Thanks for the recommendation and the support, much appreciated.
Click to expand...
Click to collapse
Well in general in windows when a FAT32 structure is asked to write a file larger than 4GB it'll flat out deny it (usually saying something like disk is full). If you're writing to a FAT32 structure using something that increments the file as it writes it, when it hits the 4GB file size limit, it'll usually say again disk is full and the file will go corrupt (which can lead to the file being undetectable). I do believe that Nandriod is smart enough to realize when it gets to that 4GB limit it'll break the tar into multiple files or else the linux OS would probably kick back an error. As for your ROM bootloops and things like that, I'd see about another ROM, maaaaybe it could just be that the ROM you flashed doesn't like your phone (I have an i717 that does that with a ROM). If that still doesn't solve it, like you said. Start at the beginning completely clean and just work through the entire process.
Theoriginalgiga said:
Well in general in windows when a FAT32 structure is asked to write a file larger than 4GB it'll flat out deny it (usually saying something like disk is full). If you're writing to a FAT32 structure using something that increments the file as it writes it, when it hits the 4GB file size limit, it'll usually say again disk is full and the file will go corrupt (which can lead to the file being undetectable). I do believe that Nandriod is smart enough to realize when it gets to that 4GB limit it'll break the tar into multiple files or else the linux OS would probably kick back an error. As for your ROM bootloops and things like that, I'd see about another ROM, maaaaybe it could just be that the ROM you flashed doesn't like your phone (I have an i717 that does that with a ROM). If that still doesn't solve it, like you said. Start at the beginning completely clean and just work through the entire process.
Click to expand...
Click to collapse
Cheers, I had re-downloaded the previous version of the ROM which I was on before hand and made sure to check the md5s but it still wouldn't boot which was annoying, but a full install from scratch may be the way to go. Never had bootloops before and was just worried after I had wiped and started a fresh and it still happened. I think the real lesson is to make sure to backup ANYTHING that is of value to you!
Luckily I had just happened to use the auto backup for photos to dropbox so got off lightly this time!
I have had the EXACT same issue 2 weeks ago.
I bought 2 x 32gig microSD cards (Sandisk)
1 for my phone and 1 for my digital camera.
Recently the 32gig one in my phone just DIED for no reason at all. Lost all my files, music, everything.
I contacted Sandisk, had it repalced. In the meanwhile i purchased a 64gig Samsung one.
I am yet to have an issue with the Samsung 64gig, but only time will tell.
On a plus note, Sandisk sent me a replacement 32gig card very quickly (infact too quick, i purchased the 64gig Samsung one on the idea that the Sandisk replacement was going to take months... in fact it only took 6 days...)
Cheers
How did you contact Sandisk, did you need to give a serial number or provide proof of purchase?
Sent from my Nexus 7 using xda app-developers app
jujuburi said:
And the first thing you should do is format your card to exFAT, I really don't know how and why people uses FAT32
Click to expand...
Click to collapse
I always use Fat32 on SD-cards. Why? It works on every Rom, with every kernel, every recovery, on every device, every camera, every computer, all the time.
When not in need of files greater than 4GB Fat32 simply is the way to go, compatibilty-wise.
gsmyth said:
How did you contact Sandisk, did you need to give a serial number or provide proof of purchase?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Tried the card in a reader connected to my laptop but nothing. I've emailed Sandisk support so will see what they say.
Sent from my GT-I9505 using xda app-developers app
Hello every one,
I have a complicated situation with deleted files (photos and videos) recovery,
Phone : Nexus 5
Android: M (6.0) BN: (MRA58N)
Root/unlock: Unrooted and Unlocked
Some one has deleted all the files in the camera folder in the gallery, i want to restore these deleted files. After hours of digging the internet, i found a lot of applications that doesn't work (almost all of it either require root or require USB Mass storage), and as you know we are only able to connect to the PC using MTP protocol.
Rooting the device requires unlocking it which will cause the whole phone to be wiped.
I have two questions:
1) Is there any (REAL) way to recover the deleted files (Images and videos) with the current circumstances (Unrooted, Unlocked, MTP Connection) ?
2) If the answer of question 1 is NO, if i unlocked (and for sure wiped) the phone then rooted it, can i still have the ability to recover these files, i mean how badly the wipping process will affect the internal phone storage?
I really appreciate your help in advance.
Best regards,
kldoon said:
Hello every one,
I have a complicated situation with deleted files (photos and videos) recovery,
Phone : Nexus 5
Android: M (6.0) BNMRA58N)
Root/unlock: Unrooted and Unlocked
Some one has deleted all the files in the camera folder in the gallery, i want to restore these deleted files. After hours of digging the internet, i found a lot of applications that doesn't work (almost all of it either require root or require USB Mass storage), and as you know we are able to connect to the PC using MTP protocol.
Rooting the device requires unlocking it which will cause the how phone to be wiped.
I have to questions:
1) Is there any (REAL) way to recover the deleted files (Images and videos) with the current circumstances (Unrooted, Unlocked, MTP Connection) ?
2) If the answer of question 1 is NO, if i unlocked (and for sure wiped) the phone then rooted it, can i still have the ability to recover these files, i mean how badly the wipping process will affect the internal phone storage?
I really appreciate your help in advance.
Best regards,
Click to expand...
Click to collapse
1 - no
2 - no
phones uses emmc nand cards, they are basicly ssds, no mechanical parts, instant access time, etc... . because of that,when a file is deleted, its actually deleted, not just "masked".
and if you unlock, you delete all userdata, apps,files,etc, no way of recovering. Altought on early n4s bootloader the wipe was glitched(you could restore your data), on the n5 it fully wipes
Tip: next time you could use google´s free auto backup(google photos)
opssemnik said:
1 - no
2 - no
phones uses emmc nand cards, they are basicly ssds, no mechanical parts, instant access time, etc... . because of that,when a file is deleted, its actually deleted, not just "masked".
and if you unlock, you delete all userdata, apps,files,etc, no way of recovering. Altought on early n4s bootloader the wipe was glitched(you could restore your data), on the n5 it fully wipes
Tip: next time you could use google´s free auto backup(google photos)
Click to expand...
Click to collapse
Its Unfortunate to hear that , i hoped there will be a small chance to recover the deleted data after wiping the phone and rooting it.
I Would like to hear if there is any other options.
Best thanks @opssemnik
Is the same true for HTC One M8?
opssemnik said:
1 - no
2 - no
phones uses emmc nand cards, they are basicly ssds, no mechanical parts, instant access time, etc... . because of that,when a file is deleted, its actually deleted, not just "masked".
and if you unlock, you delete all userdata, apps,files,etc, no way of recovering. Altought on early n4s bootloader the wipe was glitched(you could restore your data), on the n5 it fully wipes
Tip: next time you could use google´s free auto backup(google photos)
Click to expand...
Click to collapse
The original questioner had a Nexus.
Does your answer also apply to HTC One M8?
Thanks.
PhilBill said:
The original questioner had a Nexus.
Does your answer also apply to HTC One M8?
Thanks.
Click to expand...
Click to collapse
i don´t know about the bootloader unlock part wiping the data on the M8 (since those were never sold here in Brazil) however the rest still applies. on HDDs and other mechanical drives, the deletation process is just removing the file from the index on the drive, so it cant find anymore, thats due to mechanical drives having fragmentation, not instant access times and other things(such as lower read/write speeds, bad sectors, etc). since those dont apply to solid state devices, such as ssds or emmcs, every file operation is permanent
Hi guys,
I own a Nexus 5 16gb with purenexus 6.01 I'm buying another 32gb and to speed things up I would like to transfer the Nandroid backup of the first on thesecond.it can do? there would be stability problems?
i will use the 32gb as main phone and the 16gb for "home experiments" about rom, kernels and another...
thank you
It is possible to restotre it, but HELL DONT EVER RESTORE EFS!!!! it will mess up the imei and you will loose conectivity
aciupapa said:
It is possible to restotre it, but HELL DONT EVER RESTORE EFS!!!! it will mess up the imei and you will loose conectivity
Click to expand...
Click to collapse
of course, just boot, system and data (cache?).
I'm just afraid that in the boot.img is saved some serial number [phone, or a wifi mac address] that do not meet on the other device, can lead to malfunctions or brick
Luca TIR said:
of course, just boot, system and data (cache?).
I'm just afraid that in the boot.img is saved some serial number [phone, or a wifi mac address] that do not meet on the other device, can lead to malfunctions or brick
Click to expand...
Click to collapse
I have been restoring all of my partitions with twrp for a long time, no problems. TeamWin had informed users that restoring the EFS partition on a specific device (nexus 5x, 6, don't remember exactly) would brick the device. But restoring your 16gb backup to a 32gb device might have other problems such as not seeing your entire memory.
Judging by the fact that if you flash your 32gb nexus 5 with the google factory image then you have to manually "wipe data/factory reset" via recovery to get it to recognize 32gb (or else it says you have only 16, small heart attack there), then that means that the memory capacity is defined somewhere in the software (obviously). Also, the partitions would be of different sizes. You'd have no problem transferring backups between identical devices, though when you have a different memory storage, you need to reinstall everything.
Hardware information such as MAC adresses are not saved anywhere, they are retrieved at runtime. Consider that you can even change a MAC address on the fly and the device would have no problem with it as long as you turn it off and on again (ifconfig wlan0 down && ifconfig wlan0 up) (as far as the OS is concerned, because you can't truly change it, I think it's hardware defined). Same goes for IMEI etc. But the flash memory consists of many partitions that need to be of specific size. If you restore a partition with different size than it's original one, you might soft brick it.
In conclusion, no, don't transfer your backup. Unlock the device, flash recovery, flash zips, setup your device again...
chrisk44 said:
I have been restoring all of my partitions with twrp for a long time, no problems. TeamWin had informed users that restoring the EFS partition on a specific device (nexus 5x, 6, don't remember exactly) would brick the device. But restoring your 16gb backup to a 32gb device might have other problems such as not seeing your entire memory.
Judging by the fact that if you flash your 32gb nexus 5 with the google factory image then you have to manually "wipe data/factory reset" via recovery to get it to recognize 32gb (or else it says you have only 16, small heart attack there), then that means that the memory capacity is defined somewhere in the software (obviously). Also, the partitions would be of different sizes. You'd have no problem transferring backups between identical devices, though when you have a different memory storage, you need to reinstall everything.
Hardware information such as MAC adresses are not saved anywhere, they are retrieved at runtime. Consider that you can even change a MAC address on the fly and the device would have no problem with it as long as you turn it off and on again (ifconfig wlan0 down && ifconfig wlan0 up) (as far as the OS is concerned, because you can't truly change it, I think it's hardware defined). Same goes for IMEI etc. But the flash memory consists of many partitions that need to be of specific size. If you restore a partition with different size than it's original one, you might soft brick it.
In conclusion, no, don't transfer your backup. Unlock the device, flash recovery, flash zips, setup your device again...
Click to expand...
Click to collapse
clear, precise and convincing ... you're right .especially different partitioning and memory size did not convince me, you have confirmed to me. I try suffered some rom nougat when I get the device
p.s.:no small heart attack please, i'm an ambulance driver :laugh: (really)
many thanks
The emulated sdcard is not backed up by twrp anyway. I would just adb pull that partition and then push all the files back on the knew device. Data and system should be fine with twrp.
(apparently) it's working!!!
Today, I received the "twin"
just out of curiosity I tried to restore the backup on the 16gb and 32gb [purenexus 6.01] and all seems to work.but I have yet to test it.
Now I go to work tomorrow I put the sim card and use it normally to confirm that everything is ok.
p.s.:the data on the free / busy sd internal memory are righteous
Attention developers!!!
I have an idea of a concept where the A/B slots could be used to boot 2 different ROMs simultaneously one on Slot A and another on slot B using another data partition. Is it possible?
Feel free to discuss in this thread.
It would work, but we only have one data partiton. You have to split it (like on the mi a1 I think?)
I have found a good method for dual-booting, but some roms don't work and there is only 1 data partition.
I have lots of ideas ???
Can we not split the single data partition into two separate partitions for data?
shaunakdsilva said:
Can we not split the single data partition into two separate partitions for data?
Click to expand...
Click to collapse
Well then storage for each partition will decrease and it may be a issue for installing apps and other data am i right?
Aduser345 said:
Well then storage for each partition will decrease and it may be a issue for installing apps and other data am i right?
Click to expand...
Click to collapse
You can use one slot for daily driver rom with a bigger data partition size and use the other spot for experimental rom with a smaller data partition size. How many of us really use the entire 64gb or 128gb storage for data?
shaunakdsilva said:
You can use one slot for daily driver rom with a bigger data partition size and use the other spot for experimental rom with a smaller data partition size. How many of us really use the entire 64gb or 128gb storage for data?
Click to expand...
Click to collapse
Hmmm.....but what about that encrypted storage thing??
Won't it interefere with booting the rom?
And would our device be able to handle rom switching?
I mean im not that an expert but atleast what i hav heard about the boot.img being incompatible with both the roms is it possible to dual boot???? I really want a custom rom and oos pie in my device???
Aduser345 said:
Hmmm.....but what about that encrypted storage thing??
Won't it interefere with booting the rom?
And would our device be able to handle rom switching?
Click to expand...
Click to collapse
Only a developer would be able to answer those questions. As far as i know, anything is possible!
Anyway, we can use twrp as dual boot manager?
core7x said:
Anyway, we can use twrp as dual boot manager?
Click to expand...
Click to collapse
TWRP offers to switch the slot which is how i got the idea that probably we could have two ROMs installed and switch the slot from TWRP as and when required.
Aduser345 said:
Hmmm.....but what about that encrypted storage thing??
Won't it interefere with booting the rom?
And would our device be able to handle rom switching?
I mean im not that an expert but atleast what i hav heard about the boot.img being incompatible with both the roms is it possible to dual boot???? I really want a custom rom and oos pie in my device???
Click to expand...
Click to collapse
In order to make things simpler, decrypted data partition would be a pre requirement.
Encryption is not really useful for most people and a possible issue doing this kind of manipulation to actually make some sense out of (otherwise useless) A/B partition scheme
This idea would probably be slow and a lot of overhead (i.e. wasted battery) but you could theoretically create a writable disk image and then have the ROM dynamically mount that in the data location. No idea how it would work or if it would work.
Otherwise, you could always look into chroot or something like that. Just throwing ideas out, I have no development capability.
can i install pie on one slot and if for whatever reason do not like can i go back to the other slot? rooted as well? thank u!
Smartest op ever
maybe a possibility?
Ive used "DualBootpatcher" on many devices in the past. I don't know if it works on a/b devices like the op6.
Let me know if it does, and if it bricks your device.
Https://forum.xda-developers.com/cr...ualboot-dualbootpatcher-simpler-dual-t3297414
Looks like it works on the op5!:
https://forum.xda-developers.com/oneplus-5/development/patcher-dualboot-multiboot-oneplus-5-t3633150
And the 5t is officially supported!
Https://dbp.noobdev.io/supported_devices.html
Maybe somebody can reach out to the developer
Neil_Armstrong_ said:
Smartest op ever
Click to expand...
Click to collapse
I can't really figure if that is sarcasm... could you explain how it's so smart?
Yeah I'd love to dual boot my op6, I'm really missing it because I used it on my Nexus 5x and it was really useful, we should all reach out to the devs of multiboot or dual boot patcher or someone could port it, that'd be amazing
Anything is possible, the issue how much development would be required. My guess here is the answer is "so much that no one is going to bother."
There's nothing special about A/B. It's just duplicated partitions, a system for flagging which set is active, and using the arrangement for seamless updates. It's not designed for dual boot because both slots are intended to use the same data partition. So at the very least you'd need some function to split or otherwise change how the data partition is used. Given that much of this is baked into core Android, I suspect that hacking it for dual boot would be both unstable and a risk of brickage. Past tools for non-A/B phones are most certainly not going to work here.
https://www.google.com/amp/s/forum.xda-developers.com/pixel/help/dual-booting-t3507924/amp/