Related
I accustomed to storing their audio or video file like photos into a mini memory stick. However, how can we recover them once lost? What can I do ? Any software like Power Data Recovery?? 3Q for your advice.
Wait, what does this have to do with Win8? I'm confused (or maybe you are)...
Assuming "memory stick" (whatever the <REDACTED> that is) exposes itself as a standard block-storage device, you can probably use whatever recovery tools you're used to... no guarantee they'll work, though.
I've had a positive experience using MiniTool Power Data Recovery.
It worked wonders on a flash disk that apparently lost its data, but with this software I could recover most of them, although with very ugly file names.
There are 4 options which can be confusing but I've mostly used Digital Media Recovery and Undelete Recovery.
For non media files, the result wasn't so great but I recovered some files from an almost defective SD card.
cha91 said:
I've had a positive experience using MiniTool Power Data Recovery
Click to expand...
Click to collapse
Well, what can i say but thank you so much!
Had the same problem and all the pictures of my holiday were gone. :victory:
With kind regards, Basti
pHaZic said:
Well, what can i say but thank you so much!
Had the same problem and all the pictures of my holiday were gone. :victory:
With kind regards, Basti
Click to expand...
Click to collapse
You're welcome! I'm glad it helped.
I had the same problem a while ago so now I recommend this software
mining said:
I accustomed to storing their audio or video file like photos into a mini memory stick. However, how can we recover them once lost? What can I do ? Any software like Power Data Recovery?? 3Q for your advice.
Click to expand...
Click to collapse
yup, any recovery software will do, just defrag first before recovering for best result
Physiotherapist said:
yup, any recovery software will do, just defrag first before recovering for best result
Click to expand...
Click to collapse
Worst result dont you mean... Recovery software relies on the fact that when deleting a file it is simply removed from the file table but the data itself is still present. Defragging will move files around and will now believe where your file previously existed is now unallocated space and will happily over-write it. For recovery software to work at its best you need to ensure as few changes are made to the file system as physically possible.
SixSixSevenSeven is correct. Leaving aside the fact that defragging a flash storage device (like a memory stick, SD card, SSD, CompactFlash, etc.) is a terrible idea in general*, it will drastically reduce your chances of being able to recover any data at all. If you have already done a defrag, the odds are very good that your data is now unrecoverable.
* Win7 and up know not to actually defrag Flash-based storage, but what they do instead - called TRIM, and intended to optimize the storage - is almost as bad for purposes of data recovery. TRIM tells the "disk" that the physical memory cells which were storing the data of deleted files are no longer needed, which typically has the effect of zeroing the data.
Hi fellow xda-members,
I've already posted this in the One XL section, but I realized it is a more generic problem/more generic technical question.
Thats why I post this again to maybe reach the real experienced guys from xda whom maybe know an answer to my specific question.
Ive summarized the most important points to not double-post the question.
I recently wiped my One XL 32GB with the HBOOT Factory Reset,
didnt know that it wipes the internal storage aswell...
Needless to say that I work with the phone and the data is priceless...
I already piped the whole block device(mmcblk0) via netcat and dd,
opened it with a hex editor and found out the whole fat-partition is nulled.
From what I know and heard, the only way to really secure delete any storage device
is to overwrite the data several(Mostly heared 7 times) times to avoid unwanted recovery.
The Partition wasnt formatted and neither mounted yet, there should be no changes made from android since the wipe.
If you take that into account, there's a hope to recover the data.
Does someone have experience with jtag raw data recovery?
Is there any way to gather other/deeper data with jtag?
Thanks for all replys
criestr
Its possible that the external storage is on a second MMC device.
So recently my device stopped recognizing the SanDisk 64gb micro-SDXC I had formatted as internal storage. As far as I am aware when you format a SD this way the phone turns it into an encrypted volume and stores the key on internal storage, presumably somewhere the user cannot normally access it. The card itself is not dead, plugging it into my computer verifies this, but I cannot access it. I think some write operation failed and made it invisible to the phone. the phone did the same thing to a 128gb PNY card, but I reformatted it on PC, then reformatted it again on the phone and now the PNY is working fine. my question is, is there any way to extract the encryption key for my 64gb card(Root based tool or otherwise) from the card profile on my phone and decrypt it on a PC so I can reclaim my data? The phone still has a profile for the card, so presumably the key is still in internal storage somewhere. I had about 40gb of media on that card that I had not backed up (photos, videos, music and such). My ohone is not currently rooted but i wouldnt mind rooting it if someone has a root only solution.
I would wipe cache, then data then try another ROM.
sciencetor2 said:
So recently my device stopped recognizing the SanDisk 64gb micro-SDXC I had formatted as internal storage.
Click to expand...
Click to collapse
It is possible, though I have not done it before, I avoid adoptable storage for this reason. Do NOT wipe your ROM, or you will permanently lose your encryption key to your data that you have on the card.
If you put the SD card into a Linux PC that can recognize the partitions (Windows will not show it), you will see two partitions, android_meta and android_expand. To decrypt the big one, android_expand, you will need to recover your key from the phone.
To recover the encryption key, you will need either root access or a custom recovery like TWRP, to access '/data/misc/vold' to retrieve the encryption key (aes-cbc-essiv:sha256). Save the .key file to somewhere safe.
Then something like
dmsetup create crypt1 --table "0 `blockdev --getsize /dev/sdb2` crypt \
aes-cbc-essiv:sha256 00010203040506070809010a0b0c0d0e0f 0 /dev/sdb2 0"
mount -t ext4 /dev/mapper/crypt1 /mnt/1/
More info here - http://nelenkov.blogspot.com/2015/06/decrypting-android-m-adopted-storage.html
Once you have recovered your data, reformat the card and use it as portable storage
SenK9 said:
More info here -nelenkovDOTblogspotDOTcom/2015/06/decrypting-android-m-adopted-storageDOThtml
Once you have recovered your data, reformat the card and use it as portable storage
Click to expand...
Click to collapse
(url edited due to new user restrictions)
Thank you! this is exactly what I was looking for, but i couldn't find anything on google about anyone figuring out all the details (encryption key location, encryption method, usable tool for decryption)
now is there any way i can root, extract the key, then unroot so that i can RMA the phone? It seems to now render any sd i put into it unreadable by itself within about 5 minutes of formatting, regardless whether i format as internal or portable. not sure if this is hardware (reader malfunction) or some software is writing to the card incorrectly, but it is now doing it consistently.
sciencetor2 said:
(url edited due to new user restrictions)
Thank you! this is exactly what I was looking for, but i couldn't find anything on google about anyone figuring out all the details (encryption key location, encryption method, usable tool for decryption)
now is there any way i can root, extract the key, then unroot so that i can RMA the phone? It seems to now render any sd i put into it unreadable by itself within about 5 minutes of formatting, regardless whether i format as internal or portable. not sure if this is hardware (reader malfunction) or some software is writing to the card incorrectly, but it is now doing it consistently.
Click to expand...
Click to collapse
I do not believe it's possible to root or change the recovery without unlocking the bootloader, unless there's some other method I'm not aware of. Even MM systemless root method - http://forum.xda-developers.com/mot...t-moto-x-style-xt1572-br-marshmallow-t3259380, requires unlocking the bootloader, which of course then technically voids the warranty.
However, in this case, it might be worth contacting Moto to inform them of what's happened, it's definitely some kind of bug in the software which has caused this, and thus you are stuck in this catch-22 situation. They might make an exception or have some other solution. Let us know how you go.
SenK9 said:
... requires unlocking the bootloader, which of course then technically voids the warranty. ...and thus you are stuck in this catch-22 situation.
Click to expand...
Click to collapse
Even more of a catch 22 situation, because if i read that correctly, the process for unlocking the bootloader also requires wiping the phone (and thus, the encryption keys) (i miss geohot with his 1 click soft roots). I will wait a little while and see if I or anyone else reading this thread can find a way around that, but it seems ill have to contact Moto support either way, since my 16gb model is barely usable without an SD card.
This is another example of why taking control of your phone before something goes wrong is so important.
Did you try wiping cache yet?
lafester said:
This is another example of why taking control of your phone before something goes wrong is so important.
Did you try wiping cache yet?
Click to expand...
Click to collapse
I checked the recovery menu but there didn't seem to be an option for wiping cache on this device (recovery menu was a little different than I am used to, only had option for factory reset) Also, while wiping cache might conceivably prevent it from screwing up future cards, I don't know if it will fix this one, and i'm not sure if i wanna risk wiping anything without getting my hands on the encryption keys first. if it becomes apparent that i'm just not getting root without wiping, then I'll try playing around with recovery options to at least get back SD slot usage.
You can erase cache in fastboot. If you are locked there is no way to root without wiping data.
lafester said:
You can erase cache in fastboot. If you are locked there is no way to root without wiping data.
Click to expand...
Click to collapse
Isn't that what the setting "OEM Unlocking" under "Developer Options" is for? I thought I read that, if you enable this option before you unlock the bootloader, it allows you to unlock without the wipe/factory reset?
YITBOS said:
Isn't that what the setting "OEM Unlocking" under "Developer Options" is for? I thought I read that, if you enable this option before you unlock the bootloader, it allows you to unlock without the wipe/factory reset?
Click to expand...
Click to collapse
I hadn't heard that... Got a source?
YITBOS said:
Isn't that what the setting "OEM Unlocking" under "Developer Options" is for? I thought I read that, if you enable this option before you unlock the bootloader, it allows you to unlock without the wipe/factory reset?
Click to expand...
Click to collapse
No all that does is allow you to unlock (providing you have a key of course).
well it looks like nobody has found a non wiping solution to root my phone, so I'm going to have to give up on the data and see if I can get back SD functionality, or just RMA the phone. I think i will also publish a script that allows you to plug in your phone and the SD at the same time and allow you to decrypt an internal formatted card by pulling the keys and using them to mount the drive to help people who are in similar situations, but have root. Thanks anyway for the help.
Hi Everyone, I'm stuck in the same catch 22 situation. Device is not rooted or bootloader unlocked, so can't access the key, and trying to root/unlock bootloader will wipe the keys. Any updates, @sciencetor2??
Have you written to Motorola/google about this?
I'm still not ready to give up on the data... hundreds of vacation pictures, that couldn't get backed up.
I'm in the same boat any good news on this?
As long as the phone can see the card, you can change it to portable storage. However, if something goes wrong and phone can not see the card anymore, it's nearly impossible to access the volume without the retrieving the key from the phone, and you must root the phone in order to get the key, as I understand.
I have another similar problem, SD card becomes locked writing and disappears from phone, even I used it as portable storage. And the card can't be formatted at all. So I believe the phone somehow does something and change the state of SD card!
Did anyone find a solution yet. Stuck with same problem. Will loose very important data.
Same here.
I adopted my sdcard as internal storage in CM13.
It was constantly in bootloop, so I formatted the internal memory of the phone to install a new rom ...
But now I can not recover the data within the sd because I can not access it nor with the new rom (I can not even mount it from TWRP) nor from a linux PC (the filesystem is unknown).
Pretty much ... I did not know that the sdcard adopted were encrypted!
Any solution? :\
Hello everybody!
Is there any way to recover the deleted ".key" file?
so i havent gotten back on this thread in a while but i think i at least figured out the "why" on why the card was no longer being recognized. it seems to come down to read/write speed. my 64GB and 128GB cards that i was having the issue with were both U1 cards, which means their read/write is only sitting around 10Mbps, and both of those had issues being detected by the phone after a little bit of time in use. I replaced the card in the same phone a few months back with a high throughput U3 card, and it has been running smoothly ever since. this leads me to the hypothesis that if the card is not fast enough for the phone's taste, it will just ignore it (or timeout on reads, not sure which is actually happening) which is leading to the issues we are experiencing. unfortunately this doesnt lead us to a solution for recovering from the existing cards, but hopefully it will help avoid making the mistake of using a slow card in the future.
So I finally made the leap from Lollipop to Marshmallow. Everything has been going fine for the most part, but I've hit a huge snag: moving apps to SD.
I use Titanium Backup to keep a full backup of my phone on the external SD card. I depend on this backup for two purposes:
1) it makes updating the ROM (like this time) a lot easier. I do a factory reset, get the base Android going, re-install Titanium Backup from the Play Store, point it to my backups on the external SD card, and then I'm good to restore (either full app+data if that's safe, or I first re-install the app from the Play Store then just restore the app's data using TB).
2) It saves my butt in the event of a phone hardware failure, which has happen several times over my many years as an Android user. I just buy a replacement phone, move the SD card over, and restore my apps/data in a similar manner as in #1.
I have a Galaxy S5 with 16GB of internal storage, which is certainly not enough so I depend on my 64GB external SD card greatly. Between keeping all my large media on the external SD, as well as moving what large apps to SD as I can, this has been fine. I use Bliss ROM.
So make the jump from Android 5 -> 6, and finally get to the point where I need to move some of the apps I've restored to SD... but can't find the option. I do some research, and now am in a panic. From what I can tell, you can only move apps to SD if you use the SD as adopted/internal storage, which means it gets re-formatted, encrypted, and can only be used with that phone. This eliminates the possibility of #1 & #2 above. To continue performing #1 & #2, I need to use the SD as "portable storage" (the way it is now), which apparently leaves no way to move apps to SD.
I am in a pickle now, and feel stuck. I'm hoping I'm missing another option. Help?
sremick said:
So I finally made the leap from Lollipop to Marshmallow. Everything has been going fine for the most part, but I've hit a huge snag: moving apps to SD.
I use Titanium Backup to keep a full backup of my phone on the external SD card. I depend on this backup for two purposes:
1) it makes updating the ROM (like this time) a lot easier. I do a factory reset, get the base Android going, re-install Titanium Backup from the Play Store, point it to my backups on the external SD card, and then I'm good to restore (either full app+data if that's safe, or I first re-install the app from the Play Store then just restore the app's data using TB).
2) It saves my butt in the event of a phone hardware failure, which has happen several times over my many years as an Android user. I just buy a replacement phone, move the SD card over, and restore my apps/data in a similar manner as in #1.
I have a Galaxy S5 with 16GB of internal storage, which is certainly not enough so I depend on my 64GB external SD card greatly. Between keeping all my large media on the external SD, as well as moving what large apps to SD as I can, this has been fine. I use Bliss ROM.
So make the jump from Android 5 -> 6, and finally get to the point where I need to move some of the apps I've restored to SD... but can't find the option. I do some research, and now am in a panic. From what I can tell, you can only move apps to SD if you use the SD as adopted/internal storage, which means it gets re-formatted, encrypted, and can only be used with that phone. This eliminates the possibility of #1 & #2 above. To continue performing #1 & #2, I need to use the SD as "portable storage" (the way it is now), which apparently leaves no way to move apps to SD.
I am in a pickle now, and feel stuck. I'm hoping I'm missing another option. Help?
Click to expand...
Click to collapse
From what I've read there is a method for app2sd to work with mm. I never had success with it though, and downgraded to ll.
ldeveraux said:
From what I've read there is a method for app2sd to work with mm. I never had success with it though, and downgraded to ll.
Click to expand...
Click to collapse
A method other than formatting the card as internal/adopted storage? Did the method involve setting up multiple partitions?
While I could set up a FAT32 partition just for TB, then adopt the rest, my backups aren't the only thing I've needed to access after popping out the SD card. For example, just being able to load media that way is quick and sometimes a life-saver. I've also used that as a way to get zip files on that I could then flash via recovery. I'm also not clear if you can "mount" adopted storage as USB while in recovery so it's visible to the computer as a USB mass-storage device while the phone is connected via USB cable (as you have been able to do normally up to this point).
sremick said:
A method other than formatting the card as internal/adopted storage? Did the method involve setting up multiple partitions?
While I could set up a FAT32 partition just for TB, then adopt the rest, my backups aren't the only thing I've needed to access after popping out the SD card. For example, just being able to load media that way is quick and sometimes a life-saver. I've also used that as a way to get zip files on that I could then flash via recovery. I'm also not clear if you can "mount" adopted storage as USB while in recovery so it's visible to the computer as a USB mass-storage device while the phone is connected via USB cable (as you have been able to do normally up to this point).
Click to expand...
Click to collapse
I'm not the app developer, I have no clue how/if it works. It didn't for me, but did for many others. Go to that thread and read up!
ldeveraux said:
I'm not the app developer, I have no clue how/if it works. It didn't for me, but did for many others. Go to that thread and read up!
Click to expand...
Click to collapse
Which app/thread are you referring to? Or are you talking about Bliss ROM itself? I didn't post in that thread, as this issue seems generically Marshmallow-related, and not specific to Bliss.
sremick said:
Which app/thread are you referring to? Or are you talking about Bliss ROM itself? I didn't post in that thread, as this issue seems generically Marshmallow-related, and not specific to Bliss.
Click to expand...
Click to collapse
It's a marshmallow problem, not Rom specific. In xda's app section there are threads for both link2sd (not working) and app2sd (works for some). Check those, I think that's where I saw the info.
Ok it wasn't easy but I think I've gotten my head wrapped around Apps2SD and have it working. I tried the free version, backed up my 64GB external SD, partitioned it with a 16GB f2fs partition (for moving/linking apps) and the remainder exfat (for using the way I've traditionally used it). Restored everything back to the exfat partition and fixed where BeyondPod and Titanium Backup were pointing to. Did a few test links and it seemed to be working although fumbling my way through was confusing at first as I didn't find a clear "how to". Ended up buying the Pro version of Apps2SD once I felt good that this was a workable solution.
I still get an error on boot about my SD being corrupt but I just need to search on that, I'm sure there's a simple fix somewhere.
sremick said:
Ok it wasn't easy but I think I've gotten my head wrapped around Apps2SD and have it working. I tried the free version, backed up my 64GB external SD, partitioned it with a 16GB f2fs partition (for moving/linking apps) and the remainder exfat (for using the way I've traditionally used it). Restored everything back to the exfat partition and fixed where BeyondPod and Titanium Backup were pointing to. Did a few test links and it seemed to be working although fumbling my way through was confusing at first as I didn't find a clear "how to". Ended up buying the Pro version of Apps2SD once I felt good that this was a workable solution.
I still get an error on boot about my SD being corrupt but I just need to search on that, I'm sure there's a simple fix somewhere.
Click to expand...
Click to collapse
I think the consensus was to use NotifyClean (Xposed module) to eliminate that message at boot. :good: Everything still working for you otherwise? I was thinking of upgrading now, and think this might work too:
http://blog.sam.liddicott.com/2016/02/android-6-semi-adopted-storage.html
sremick said:
Ok it wasn't easy but I think I've gotten my head wrapped around Apps2SD and have it working. I tried the free version, backed up my 64GB external SD, partitioned it with a 16GB f2fs partition (for moving/linking apps) and the remainder exfat (for using the way I've traditionally used it). Restored everything back to the exfat partition and fixed where BeyondPod and Titanium Backup were pointing to. Did a few test links and it seemed to be working although fumbling my way through was confusing at first as I didn't find a clear "how to". Ended up buying the Pro version of Apps2SD once I felt good that this was a workable solution.
I still get an error on boot about my SD being corrupt but I just need to search on that, I'm sure there's a simple fix somewhere.
Click to expand...
Click to collapse
Is f2fs and exfat supported by stock MM in Apps2SD? Got it formatted with fat32 and ext4.
ldeveraux said:
I think the consensus was to use NotifyClean (Xposed module) to eliminate that message at boot
Click to expand...
Click to collapse
Ugh. I do not want to have to use Xposed.
Everything still working for you otherwise?
Click to expand...
Click to collapse
Well it was working just great... then I rebooted. Apparently some trouble getting the 2nd partition (fsfs, where the apps are being moved to) to mount at boot. Trying to sort it out in this thread:
http://forum.xda-developers.com/android/apps-games/apps2sd-partition-sd-card-link-apps-to-t3122919
andacro said:
Is f2fs and exfat supported by stock MM in Apps2SD?
Click to expand...
Click to collapse
No idea, I never run stock.
The problem is solved, the solution is as followed:
Problem
- The device is unable to mount every partition, this includes:
/efs
/persdata
/system
/data
/cache
Solution
Flash the stock firmware following this instruction to Repartition the device:
https://www.sammobile.com/forum/showthread.php?t=30800
The credit goes to member greenman of sammobile forum as the link above.
Thank you very much for everyone who took the time and effort to read the thread and answer my question. I appreciate it a lot.
HI there, i think you should try and grab an image for 935F from sammobile and restore with ODIN? This should restore the device into clean state. Not sure if you tried, ie to boot into download mode, and flash via odin?
**Edit, oops, i see you already tried Odin. Hope someone can assist you..
Edit. As far I have learned so far. Every root method etc will decrypt ur sd card. If you format it will be encrypted again. Because the files get reinstalled with the config. Wich can hurt allot. As I stated before try to get the first backup from efs and ur bootloader twrp makes. After make a new one and make sure they are on ur pc. I think u will need 2 freshly flash stock rom with repartition. Since it will relocate the sd card and reformats it. But im not truely sure. If I were you wait for some senior members to confirm.
I had this issue before kinda same as yours. No os etc. But I always make backups of efs and bootloader and everything else every change I make.
So I bassicly made a fresh flash. Downloaded latest stock firmware from sammobile and converted the 4 files into 1 huge file wich I putted in ap. And putted the normal once in bl and csc etc. Then Putted in hidden image for the repartion and checked reset efs.
The flash took 15 minuts and the bootup about 30 with 3 reboots.
But pls dont try this yourself. I Program whit icepicket multi flashdevice as daily job and write the coding for eepromx chips. Thats the heart of most prints with hidden coding. And controls all hardware. This method worked out for me. But like I said I rather should wait for someone to confirm this.
removed
chaopac said:
Thank you all for your answers. I appreciate your help.
Prognosis:
I agree. also think I need a repartition of some sort. Some googling of this issue shows some people use PIT files, or other files to repartition the device.
What I think happened was, since I was using the SD as adoptable storage, it has files that makes it looks like internal storage.
When I reflash the ROM and got it running, the OS and system files were correctly link (or rather installed) in the "real" internal storage. That was how I got my device to run fine.
However, when I use the app "Aparted" to format my SD, it could have mistakenly format my "real" internal storage, thinking it was my SD, since it has similar files structure (or the partition name was messed up somehow) , and this breaks the link of the system to the files, making the system think the files are non-existent.
OR, it could have formatted my real SD, but at this point in time, the system were mistakenly recognizing the SD as its internal storage, thus, showing the internal storage to be non-existent.
Now, the system are non-recognizable by any tools, either by Recovery or by system, saying they are always 0 MB in size, including all partition, system, data, efs, cache.
Assessment:
What I worry about most is since my research, some people said efs is unique to each device, and they are very specific that it is not possible to recreate. So if I lose that partition means I lose the whole thing.
To top it off, I don't even make any back up of the system. Not even the files on my adaptable storage SD.
When I was trying to reflash ROM to rescue my device I have already formatted it with my PC.
:crying:
I don't really know what else I could do. My last hope probably is the Samsung Store. I can only hope this problem is only in software, and it could be fixed. At this point I probably need to pay to get it revived.
Click to expand...
Click to collapse
Well I didnt lose efs yet using odin with re partition and efs reset. And if you already need to pay. Yes efs is an unique file.
removed
chaopac said:
Thank you all for your answers. I appreciate your help.
Prognosis:
I agree. also think I need a repartition of some sort. Some googling of this issue shows some people use PIT files, or other files to repartition the device.
What I think happened was, since I was using the SD as adoptable storage, it has files that makes it looks like internal storage.
When I reflash the ROM and got it running, the OS and system files were correctly link (or rather installed) in the "real" internal storage. That was how I got my device to run fine.
However, when I use the app "Aparted" to format my SD, it could have mistakenly format my "real" internal storage, thinking it was my SD, since it has similar files structure (or the partition name was messed up somehow) , and this breaks the link of the system to the files, making the system think the files are non-existent.
OR, it could have formatted my real SD, but at this point in time, the system were mistakenly recognizing the SD as its internal storage, thus, showing the internal storage to be non-existent.
Now, the system are non-recognizable by any tools, either by Recovery or by system, saying they are always 0 MB in size, including all partition, system, data, efs, cache.
Assessment:
What I worry about most is since my research, some people said efs is unique to each device, and they are very specific that it is not possible to recreate. So if I lose that partition means I lose the whole thing.
To top it off, I don't even make any back up of the system. Not even the files on my adaptable storage SD.
When I was trying to reflash ROM to rescue my device I have already formatted it with my PC.
:crying:
I don't really know what else I could do. My last hope probably is the Samsung Store. I can only hope this problem is only in software, and it could be fixed. At this point I probably need to pay to get it revived.
Click to expand...
Click to collapse
chaopac said:
After some more reading, I think my last resort is to perform a "Full Firmware" flash, with options such as NAND erase, PIT file flash and EFS clear.
However, I am not entirely sure what they will do, and if in my device situation they will help fix the issue or make it worse. Information I've found so far on the net are quite vague.
So I guess I will wait until someone who is familiar with this so called "Flash Full Firmware" process to point me in the right direction to move forward. Until then, I will keep searching.
Thank you for your input. I appreciate your time.
Click to expand...
Click to collapse
Edit I have typed this and readed it back. There are allot of grammar corrections to make. But I had a shift of 9 hours and due a traffic jam I also had to drive 4 hours. Also im dutch and my keyboard trys to correct stuf to Dutch. Hope you will understand what I wrote. Im just to tired now to correct it haha.
Repartion is ussualy used when you change from a multi csc to a single csc with the open pit file from the csc file. It hold how your mobile provider app instaltion etc etc.
Efs clear will bassicly wipe the cache of that part. It hold the previous versions of your mobile provider allowed things and system apl version. Also the history of previous settings. When you set up the mobile first time with a sim and add your google account there is an option restore previous backup and seetings of accounts amd system app versions of last reset. Wich always be turned on after factory reset. If you tick clear efs in odin it will wipe that. The unique codes in the efs part are not wipeable easily. Only when you really start messing arround with fully system root acces.
When a print is flashed the mainbord it is done with a flash device. In this case the one I have is used by big corporations. Every print has an hardcode. With unique codes.
To acces these or flash a new one you need sich device. Then u also need the right method. From 5 pins to uart usb in this case. Them u need the right port nuber and flash time etc etc etc. Also corporations use those special devices since we can connect different cables mini usb rs245 and so on. Wich give use another layer of protection for people who try to steal our hard code.
To ecplain lets say I made a print and the flash will be on a mini usb. Lets say the cable has 3 wires to the mini usb amd the mino usb has 5 connectors we can connect to. This gives us the oppertunity to lets say we put wire 1 and 2 on connector 3 and wire 3 on connector 1. We have allot of options. Since we can also program eich wire will transfer the data. We even can put resistors on them as a safery check.
That is one of the reasons why its damn hard to read the coding and unlock a new bootloader or efs file to root stuf. It takes allot of time to get it done. And im not sure if great programmers like chainfire do it this way. But it takes them allot of effort and time to deliver us the great rooted software.
The issue is resolved. The solution is updated at the post #1.
Thank you for everyone who read the thread and participated in.