OK, so let me first apologise for being new to this and completely dumb. I am currently using an iphone and looking to move over to a SGN. I am pretty competent with computers, phones etc, and jailbreaking iPhone. I have messed with Linux in my spare time, so I am not afraid of detailed technical work. I have also done dozens of hours of research on how to hack android phones. The basic issue I have is that I haven’t found a single guide that explains it all clearly in one place, and also exploits are getting patched and being outdated (Zergrush for example)
I am reasonably comfortable with the threads on how to root, install CWM, and the different ROM’s explain how to install them, or at least there are multiple ways to attempt these things. It is a bit confusing because there is different advice on using or not using Odin, Mobile Odin, Kies etc, and their effect on the binary counter.
I have a few questions though, and I thought posting here might get some responses:
1). I would like to change the partition size for apps stored on the internal SD card. I have watched lots of youtube videos on this, and people suggest it can be done with ROM, CWM, Odin, and also directly on a PC with partition magic. What I don’t get is the partition structure within the phone. If this is done won’t it wipe the space where CWM and the recovery console is stored and brick the phone? Could someone explain what the partition structure is, and the best way to manage partition sizes. I believe that the SGN come with 1.8gig size for apps, and the rest for storage of music, pictures etc. I would rather have a much bigger size for apps internally, and keep music and pictures on the external SD card. I have seen the use of apps like Link2SD, Move2SD etc, but I want to sort out the partition sizes first.
2). Could someone also please explain what occasion might cause you to upgrade the Kernal. My assumption would be that everyone would want to be running the latest kernel, but it seems that people are running different kernals. Is this because they are closely tied with the ROM/firmware, and they are upgraded when the custom ROM is installed, so some suit different ROMS?
3). I would welcome any link to a page that explains all of the topics in order and really clearly e.g How to Root, then install CWM, then partition. Whether to use Odin, Mobile Odin, Kies etc.
You advice would be appreciated.
chriswilson_m3 said:
OK, so let me first apologise for being new to this and completely dumb. I am currently using an iphone and looking to move over to a SGN. I am pretty competent with computers, phones etc, and jailbreaking iPhone. I have messed with Linux in my spare time, so I am not afraid of detailed technical work. I have also done dozens of hours of research on how to hack android phones. The basic issue I have is that I haven’t found a single guide that explains it all clearly in one place, and also exploits are getting patched and being outdated (Zergrush for example)
I am reasonably comfortable with the threads on how to root, install CWM, and the different ROM’s explain how to install them, or at least there are multiple ways to attempt these things. It is a bit confusing because there is different advice on using or not using Odin, Mobile Odin, Kies etc, and their effect on the binary counter.
I have a few questions though, and I thought posting here might get some responses:
1). I would like to change the partition size for apps stored on the internal SD card. I have watched lots of youtube videos on this, and people suggest it can be done with ROM, CWM, Odin, and also directly on a PC with partition magic. What I don’t get is the partition structure within the phone. If this is done won’t it wipe the space where CWM and the recovery console is stored and brick the phone? Could someone explain what the partition structure is, and the best way to manage partition sizes. I believe that the SGN come with 1.8gig size for apps, and the rest for storage of music, pictures etc. I would rather have a much bigger size for apps internally, and keep music and pictures on the external SD card. I have seen the use of apps like Link2SD, Move2SD etc, but I want to sort out the partition sizes first.
2). Could someone also please explain what occasion might cause you to upgrade the Kernal. My assumption would be that everyone would want to be running the latest kernel, but it seems that people are running different kernals. Is this because they are closely tied with the ROM/firmware, and they are upgraded when the custom ROM is installed, so some suit different ROMS?
3). I would welcome any link to a page that explains all of the topics in order and really clearly e.g How to Root, then install CWM, then partition. Whether to use Odin, Mobile Odin, Kies etc.
You advice would be appreciated.
Click to expand...
Click to collapse
The time it took you to write this thread is almost the same as searching on xda for finding most of your answers
1. Partition is set with pit file, which is available with ROM, when you flash ROM with Odin, there you may see the option to re-partition, though you dont have choice to select the size manually on odin, you have to select the .pit (partition index table)file, which design the partition. As I know it comes default, some one make it manually i dont know. BUT listen carefully it is not without risk to brick phone, and thats why pit file in normal case you can't see in ROM package.
2. Most of near ROM kernel are alike. e.g. I M on LA4, safely using kernel KL7. ROM package it self contains kernel, so when you update it, it gets updated too. BUT in case of getting CWM you may need to select near kernel when exact kernel not available. More when you flash your ROM with CWM, you will given option to keep old kernel (to keep Root intact)
3. most of question regarding ROM , Installation , Rooting you will find on links on my signature.
Thanks Dr Ketan for your detailed response. I have actually read and bookmarked many of your threads as there are very informative and detailed.
I understand your response about the ROM and the Kernal, and also the PIT file setting the size of the partitions.
I guess then if you want to change the partition size of the internal memory, then that is something that is not normally done. It seems that most people partition the external SD card, and use link2SD to utilise the space as part of the extended memory. Would you say that is the best approach?
I can say it is safest way.
why do you feel the need to try to repartition?
1gb rom size is sufficent for any rom
2gb internal data is more than sufficient unless you like to install 100's of apps
Related
Hey all, I've been browsing around the forums trying to find answers but I must not be fully comprehending what's being explained.
I recently got a HTC HD2 (Person sent wrong phone on eBay - Purchased a HTC Desire after 4 weeks receive HD2 can't be without a phone for another month or 2). After playing around with Windows Mobile OS I have decided that I don't enjoy the experience of using the phone and have decided to try and flash Android to the device (thus why I am here).
I'm about to update the ROM to the latest official ROM from the HTC website (to update the Radio to get ready for flashing) however my problem lies after this.
I currently have a 2GB MicroSD card. "A breif guide to installing and maintaining Android" recommends a 4GB MicroSD card where others say I may use a 512MB MicroSD card. Thus leading to my confusion in flashing my device.
If anyone could point me in the right direction with the size of the sdcard I need and a "fool-proof" guide to flashing, or even a guide written for the average Joe to understand I would appreciate it.
Kind regards.
Well firstly, it doesnt matter what size of card you have aslong as it can hold the android files and your data.img (internal storage file).
Second, You can not currenly "flash" any android to your phone, You only have the ability to reboot your phone into android OS and this would be ran from your sd card, Your phone in no way will be altered or flashed with any rom.
I will not attempt to tell you how to accomplish this as its a ridiculous question to ask as its obviously a faq and has been asked too many times and answered too many times..
Read, guides, read build topics, learn!
TheATHEiST said:
Well firstly, it doesnt matter what size of card you have aslong as it can hold the android files and your data.img (internal storage file).
Second, You can not currenly "flash" any android to your phone, You only have the ability to reboot your phone into android OS and this would be ran from your sd card, Your phone in no way will be altered or flashed with any rom.
I will not attempt to tell you how to accomplish this as its a ridiculous question to ask as its obviously a faq and has been asked too many times and answered too many times..
Read, guides, read build topics, learn!
Click to expand...
Click to collapse
Thank you for the quick response. I've been reading all I can here, however, it seems that everything is going over my head (such as things like SPL and Radio Versions). I'm not looking for a free ride with doing this, I'm just trying to find some assistance in a way I can understand.
Mods, please close this thread. I have solved my problem.
Kind regards.
Just installed the Desire HD NAND rom and i've only got 20 megs left, even after moving as many apps to the SD. I can't download anything else anymore.
I tried downloading Google Maps, Kindle etc but it fails and gives an insufficient storage error.
Is there any way we can use the SD to increase the internal storage so the phone doesn't keep giving these errors?
Thanks.
I made a post in the NAND vs RAM thread about gaining root access and then installing DarkTremor's a2sd.
This is possibly a viable option, but really I don't know if it's do-able.
I haven't downloaded and picked apart any of the NAND ROMs to see how they're put together yet.
But as just a guess, I would imagine it would work, you'd just need to create an ext2 partition on your sd card, and then find a way to install DT's a2sd. The only form I've seen it in is as an update.zip, and I don't think these ROMs will support clockwork-type recovery, or maybe any recovery for that matter. It may be possible for a2sd to be cooked right into future ROMs though.
I'd download a ROM and check it out, but it'd probably be more efficient to just ask somebody who's already cooking them what they think of it
So I looked at all the other "starting Fresh" threads, and they don't answer the question I have.
I have been using virtuous sense and unity roms for a while now, but lately it seems as though the phones can't handle the amount of ram they need.
So i tried enabling swap (it's done properly and working, apparently), and it seems like it's not really helping much if at all. perhaps even making things slower.
My question is... if I want to start from say.... just a basic Desire Z, with root, s-off, eng hboot... etc.
How would I go about removing everything and getting back to a fresh DZ without any stray files from various roms, scripts like swap, etc...?
Can I just back up the sd card, partition the sd card back to one single partition, and slide the sd card back in there and it will act as if i have just the last installed rom on the phone, and nothing else?
EDIT: I'm noticing 4EXT Recovery can do a superwipe on all partitions.. how would I then connect to the phone and copy a new zip file there so that I can flash it on the cleanly wiped phone?
I'm guessing ADB Shell?
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Unrooting_and_Returning_to_Stock
Way back when, I followed that guide to get my phone back to complete stock before I started flashing again. As for the SD card, I took off the media files that I wanted and just formatted the card using the phone.
In between ROMs, SuperwipeG2+ is what I use to completely clear the phone, without killing root.
Thanks EfemaN.
I don't want to unroot. I want to retain the ability to do everything I do now... I just want it to be as if I'm doing this for the first time again.
So I'm just going to recap what I intend to do. Can you or someone else tell me if this is all that's required?
1) download rom of choice
2) back up SD card
3) format/repartition SD card
4) upload rom zip from step 1 to SD card
5) run SuperwipeG2+ to remove everything off the phone but retain eng. hboot, root, and s-off
6) select flash rom from zip in recovery, and use zip from step 4
7) enjoy?
please let me know if I have it right. I can't stand these reboots and random shutoffs now from my current rom- but I'm not sure if it's because of previous installs that I've not cleared properly... I just want to make sure its not my previous software having any conflicts. For peace of mind I want to start from a fresh phone with root/soff/hboot.
Step 2 should be backup apps with titanium, and step 3 should be nandroid backup just in case, step 7 should be restore backed up apps and data (but not system data), and step 8 PROFIT!
When you superwipe (if you don't use 4EXT Recovery) you'll want to use this version:
http://www.multiupload.com/U7JPZHUG1E
Otherwise your partitions will be converted to ext 3. I highly recommend the 4EXT Recovery though... it's brilliant.
Ditamae said:
When you superwipe (if you don't use 4EXT Recovery) you'll want to use this version:
http://www.multiupload.com/U7JPZHUG1E
Otherwise your partitions will be converted to ext 3. I highly recommend the 4EXT Recovery though... it's brilliant.
Click to expand...
Click to collapse
Yeah, that superwipe version will convert him to EXT4 automatically plus efs and wipe all partitions. Definatly what he needs. Good work as always! Its nice to have a handfull of helpful people around this subforum. Its refreshing from what xda used to be. A bunch of bitter geeks who just flame every question. Heck, I was scared to ask anything for a year, lol!
sino8r said:
Yeah, that superwipe version will convert him to EXT4 automatically plus efs and wipe all partitions. Definatly what he needs. Good work as always! Its nice to have a handfull of helpful people around this subforum. Its refreshing from what xda used to be. A bunch of bitter geeks who just flame every question. Heck, I was scared to ask anything for a year, lol!
Click to expand...
Click to collapse
Thanks sino8r. I know what you mean about posting on XDA... I spent a few months doing nothing but reading before I actually posted a question. But in the end I'm better off for it. I just want people to love their Visions as much as I do.
I am a flash addict and I am sure most of you are. I can't stand a smooth running phone that works flawlessly. If it does, then I must do something to it to destroy it's stability. Well, it's not easy to brick HD2 unless you are a real dummy or like to live very dangerously lolll....even that can be fixed...but it was more difficult for me to find a way to unlock my SD card back to normal after WP7 installation. Some suggested in this forum that some of the cameras and nokia phones will do the trick...I was frustrated when I screwed up my 16GB sd card and could not find that camera or phone...as it won't make sense to buy them to restore a $15 card.....so I gave up on that card until today....I decided to play with WP mango again with the same sd card...resulted in locking it again...my challenge was to succeed unlocking it this time.....followed the same old procedures with no success...I tried and exhausted all options again!!! Then I decided to pop my sd card on my second hd2 which is running android with 4ext recovery installed and try to format it or something....and it worked!!!!! Just repartitioned the card and reformatted and it automatically unlocked it during the process....No step by step by step by step installation of software or reading pages or running codes.....nothing else was needed!
Life is meant to be simple after all
Anyone who is having the same issue with sd card after Windows Phone 7 or 7.5 installation just repartition and reformat your card via 4ext recovery and it will work...nothing else needed :} Good Luck!
All credits to 4ext recovery developer....and the developer must be proud to find this info.
Here is Step by Step process-
If you are running Android NAND and have 4ext recovery installed....then
1. Turn off your device
2. Take out the SD card(if there is any in it) and insert the one you want to unlock/fix
3. Turn on your device HOLD red power button until you get to aMAGLDR v1.13 menu
4. Go to option 8. AD Recovery hit green button for it load
5. Now you should have 4ext recovery(mine is version 2.2.7) menu
6. Scroll down to Advanced
7. Choose> Partition SD Card
8. Choose whatever size you want to first one, second one to be and the rest goes to fat. If you want all in one partition, just choose '0' for the first two and '0' as swap.
9. Follow on screen instruction you may see.....and it will delete all previous partition and create new one
8. NOW go back to main 4ext recovery menu....and format you SD card...AND there it it! Your SD card it back to normal...enjoy
NOTE: I use 4ext recovery that you flash via usb flasher thru magldr NOT the one from market. You can find the flashable one in here. I will try to find the link and post it. BUT it is not and will not be my work!
Here is a link I found....but this NOT what I used. I used this recovery that I found in one ROM link I have tried in the past which I can't think of but I have been using the same recovery since then because it is the BEST with the option of EXT4 file system....the one I have you can directly flash it like any other recovery you normally would to partition NAND to flash NAND Android roms. Nand partition size has nothing to do with sd recovery steps.
http://forum.xda-developers.com/showthread.php?t=1297587
Since I did not use the above option....I won't be much of help. But from my understanding you can use this option to update your current recovery to 4ext recovery and then follow my steps. The app from the market would require to update your current recovery as well to be able to use my method to restore your SD card after WP7 installation Good Luck! Although it is a very simple process to undertake, I am not responsible if you damage your phone or the sd card even more!!!
If someone who has the usb flashable version of 4ext recovery(for HD2) could attach it or provide link that would be great for everyone. Mine is installed in the phone and I don't seem to have that file....too many files I download everyday and must delete them all at some point
If you've found a solution to a problem...please go ahead and include a link or something so people can find the tool you used without having to spend time searching through threads and forums, instead of just writing that you found a solution.
please provide more detail. I downloaded free app from Android "Play Store" market but cannot see where to partition card.
Please provide more detail. i.e. is it free or paid version.
which menu to use etc
I will post detailed step by step soon
SEE Post#1
Sent from my HTC HD2 using xda premium
Whatdoyaknow said:
please provide more detail. I downloaded free app from Android "Play Store" market but cannot see where to partition card.
Please provide more detail. i.e. is it free or paid version.
which menu to use etc
Click to expand...
Click to collapse
I did not install that way(read post) but I think you have to update your recovery to 4ext after you install that app. And after that you can easily try my steps. It will work
NYSEAN1 said:
I did not install that way(read post) but I think you have to update your recovery to 4ext after you install that app. And after that you can easily try my steps. It will work
Click to expand...
Click to collapse
Ok thanks for all your efforts.
It seems to m that you can install 4ext from "android market", load it then choose the first menu option "Online install..." and download the additional 4ext recovery file from there.
But I'm still having problems getting it to load at boot up
Update: No joy. I have Clockworkmod recovery on mine. Installed 4ext but overwrote boot stuff and would not load 4ex. So I need help how to replace Clockworkmod with 4ext or whatever I need to do (I have more expertise in WP7 than Android)
For the HD2 the 4EXT Recovery was originally ported by Dansta34 and i have also seen a variant on Coredroid which looks like it's the same. The Sensation 4EXT from Madmaxx will not work on the HD2.
The HD2 4EXT Recovery can be taken from either Dan's thread (TBD ROM) or from Coredroid, whereas i recommend taking it from Dan as he also took the workload of porting it to the HD2 as far as i know. So he should deserve the Download stats and the credits
I've also got it mirrored in my Signature. Feel free to take it from there. I've got both the CoreDroid and the TBD variant, yet the only difference i can see is the background image. Not sure though.
Once you downloaded that Recovery you can put your HD2 into USB Flasher Mode in Magloader and then flash the Recovery via the included DAF.exe, then proceed with the Steps the OP recommends. Notice: if you flash it for the sole purpose of unlocking your SD-Card, setting the partition sizes in flash.cfg is irrelevant. Just leave them as they are since the Recovery and the partitions will be deleted and set up different from the WP7 flash afterwards.
Since the Threadstarter has contacted me for a link to the files (?? Why is that) i'd like to point out that this Recovery is not a hidden gem but a normal Download for at least two Android ROM's and can be taken in exchange for a THANKS.
I recommened NYSEAN1 to reproduce and verify his findings, as i find it rather strange that noone else has noticed this "function" of the Recovery before. There is quite a large number of people who mess with both android and wp7 and noone has ever noticed that the HD2 can, by means of the 4EXT Recovery, unlock DRM encrypted SD-Cards? Very odd.
Well, if it does actually work, the better it is for us. So, we have to say THANKS to NYSEAN1 for finding out this wonderful trick that saves us from finding an old Nokia phone.
I'd still recommend to post this Info on the SD-Card unlocking threads as this seems the most independent and hassle-free solution to me. But please only after this procedure has been verified by more than just one person to be working as expected.
Thanks
Thank you very much.
I have sloved it.
Sneakyghost said:
The HD2 4EXT Recovery can be taken from either Dan's thread (TBD ROM) or from Coredroid, whereas i recommend taking it from Dan as he also took the workload of porting it to the HD2 as far as i know. So he should deserve the Download stats and the credits.
Click to expand...
Click to collapse
Many thanks Sneakyghost, this will save others the problems that I have had.
Would you mind providing a link Dan's thread or advise as to which to download from your great site – it seems to have a few Xt4 files. Not being an expert, I’m not sure which to use.
Sneakyghost said:
For the HD2 the 4EXT Recovery was originally ported by Dansta34 and i have also seen a variant on Coredroid which looks like it's the same. The Sensation 4EXT from Madmaxx will not work on the HD2.
The HD2 4EXT Recovery can be taken from either Dan's thread (TBD ROM) or from Coredroid, whereas i recommend taking it from Dan as he also took the workload of porting it to the HD2 as far as i know. So he should deserve the Download stats and the credits
I've also got it mirrored in my Signature. Feel free to take it from there. I've got both the CoreDroid and the TBD variant, yet the only difference i can see is the background image. Not sure though.
Once you downloaded that Recovery you can put your HD2 into USB Flasher Mode in Magloader and then flash the Recovery via the included DAF.exe, then proceed with the Steps the OP recommends. Notice: if you flash it for the sole purpose of unlocking your SD-Card, setting the partition sizes in flash.cfg is irrelevant. Just leave them as they are since the Recovery and the partitions will be deleted and set up different from the WP7 flash afterwards.
Since the Threadstarter has contacted me for a link to the files (?? Why is that) i'd like to point out that this Recovery is not a hidden gem but a normal Download for at least two Android ROM's and can be taken in exchange for a THANKS.
I recommened NYSEAN1 to reproduce and verify his findings, as i find it rather strange that noone else has noticed this "function" of the Recovery before. There is quite a large number of people who mess with both android and wp7 and noone has ever noticed that the HD2 can, by means of the 4EXT Recovery, unlock DRM encrypted SD-Cards? Very odd.
Well, if it does actually work, the better it is for us. So, we have to say THANKS to NYSEAN1 for finding out this wonderful trick that saves us from finding an old Nokia phone.
I'd still recommend to post this Info on the SD-Card unlocking threads as this seems the most independent and hassle-free solution to me. But please only after this procedure has been verified by more than just one person to be working as expected.
Click to expand...
Click to collapse
Thanks Sneaky.....I was not sure where I found it and who created it. But I remember seeing your name around it....thanks again! I hope this really works for others.
Whatdoyaknow said:
Many thanks Sneakyghost, this will save others the problems that I have had.
Would you mind providing a link Dan's thread or advise as to which to download from your great site – it seems to have a few Xt4 files. Not being an expert, I’m not sure which to use.
Click to expand...
Click to collapse
I used TMobile version....but it doesn't matter anyway..nand partition or size does not really have anything to do with it...any size is fine...just pick any 4ext recovery and flash it through usb flasher...all we are looking for is the 4ext recovery menu to re-partition and format the card.
Please report back it worked for you...very eager to know
linxuehui said:
Thank you very much.
I have sloved it.
Click to expand...
Click to collapse
Did it work for you????? Please report back!
NYSEAN1 said:
I used TMobile version....but it doesn't matter anyway..nand partition or size does not really have anything to do with it...any size is fine...just pick any 4ext recovery and flash it through usb flasher...all we are looking for is the 4ext recovery menu to re-partition and format the card.
Please report back it worked for you...very eager to know
Click to expand...
Click to collapse
Sorry, but it's not that simple. I have had to start all over and rebuild the O/S as loading the wrong 4ext on messed it up - would no boot past "go go go". Hence we need to know precisely which 4ext to load.
Whilst your instructions are great and will be/are a big help, we must calrify this to ensure the project is a success for others.
So one last vital piece of information needed, if you can help clarify.
Many thanks for your help
BTW. Are we talking about a completely bricked SD-Card or one that just need some fixing. i.e. has a small fat partition?
Whatdoyaknow said:
Sorry, but it's not that simple. I have had to start all over and rebuild the O/S as loading the wrong 4ext on messed it up - would no boot past "go go go". Hence we need to know precisely which 4ext to load.
Whilst your instructions are great and will be/are a big help, we must calrify this to ensure the project is a success for others.
So one last vital piece of information needed, if you can help clarify.
Many thanks for your help
BTW. Are we talking about a completely bricked SD-Card or one that just need some fixing. i.e. has a small fat partition?
Click to expand...
Click to collapse
If you flash any recovery your WP7 will be gone. No matter what partition size you set. Sorry. That's exactly why it doesn't matter which 4EXT you take.
Regarding your second question: I was suspecting that Nysean1 only fixed a card with a small FAT partition. But he recons that he also fixed the DRM encrypted card from e.g. a Yuki or xboxmod ROM.
Sent from my multi talented HD2
Sneakyghost said:
If you flash any recovery your WP7 will be gone. No matter what partition size you set. Sorry. That's exactly why it doesn't matter which 4EXT you take.
Regarding your second question: I was suspecting that Nysean1 only fixed a card with a small FAT partition. But he recons that he also fixed the DRM encrypted card from e.g. a Yuki or xboxmod ROM.
Click to expand...
Click to collapse
Yes I realize that things will be wiped. But I grabbed 4EXT from the Market which jammed at GoGoGo. So best we warn folk about that.
I downloaded and installed EXT4_CoreDroid_10_180_10 from your site thanks very much - seems all OK. Have Android NAND back running again
I have now tried it on a fully bricked SD Card, but no luck at all for me. Tried about 10 times will different options. So it seems it is not an unlock for a fully bricked card (unless I've done something wrong - you say any of the Ext4 from your site should work the same)
Tried it on a card with a small FAT partition, and that's worked, but I can do that using partition program on my PC, so no added value from my perspective
(unless Nysean1 can throw some more light on this)
Whatdoyaknow said:
Yes I realize that things will be wiped. But I grabbed 4EXT from the Market which jammed at GoGoGo. So best we warn folk about that.
I downloaded and installed EXT4_CoreDroid_10_180_10 from your site thanks very much - seems all OK. Have Android NAND back running again
I have now tried it on a fully bricked SD Card, but no luck at all for me. Tried about 10 times will different options. So it seems it is not an unlock for a fully bricked card (unless I've done something wrong - you say any of the Ext4 from your site should work the same)
Tried it on a card with a small FAT partition, and that's worked, but I can do that using partition program on my PC, so no added value from my perspective
(unless Nysean1 can throw some more light on this)
Click to expand...
Click to collapse
Sorry it did not work for you. I am not hundred percent sure what kinda lock my card had. I wanted to run WP7 and android...so I installed WP7....did not quite partition the card for android as per the instructions.....this is the second time I failed to do that....WP7 without the option of android sd is lame....anyways therefore I wanted my card back...could not format it in anyways...via my camera...was not even recognized by my computer and mini tool....send usb unlock code....all failed for me....this happened to my last card also...i was never able to revive it...and did not work out any method I could find in xda and outside....but this time and with this diff. card 4ext was able to partition and format it back to normal. I can't even find that one anymore to try my new finding as I am aslo skeptic to try and take another chance with my current card as I use it everday....that I know for sure had Yuki rom installed when it first came out ...I am still searching for that card...and if I do find it I will certainly give feed back.
However....those who have installed ext4 will certainly appreciate it...since it is (I think) the best recovery you can have for you android...only thing is that some roms don't support ext4...so be aware of that.
Thanks for your explanation NYSEAN1
Thus your title/heading is fully correct - to unlock from Yuki rom.
I guess I got excited thinking that meant unlock a "bricked" SD card, which has been bricked through an error installing a WP7 rom such as Yuki rom. The two issues are different. However, you have not claimed the later case, but the first, and that is fair enough.
I have always hoped that an Android system might resurrect a fully bricked card- I still hope, but not their yet.
Thanks again
Edit 1: BTW thanks for putting me on to ext4. I do like it!!!
Edit 2:
Seems like the only way for a bricked card is for a Nokia device (or similar), which I don't have. See
http://forum.xda-developers.com/showthread.php?t=1242071
NYSEAN1 said:
Sorry it did not work for you. I am not hundred percent sure what kinda lock my card had. I wanted to run WP7 and android...so I installed WP7....did not quite partition the card for android as per the instructions.....this is the second time I failed to do that....WP7 without the option of android sd is lame....anyways therefore I wanted my card back...could not format it in anyways...via my camera...was not even recognized by my computer and mini tool....send usb unlock code....all failed for me....this happened to my last card also...i was never able to revive it...and did not work out any method I could find in xda and outside....but this time and with this diff. card 4ext was able to partition and format it back to normal. I can't even find that one anymore to try my new finding as I am aslo skeptic to try and take another chance with my current card as I use it everday....that I know for sure had Yuki rom installed when it first came out ...I am still searching for that card...and if I do find it I will certainly give feed back.
However....those who have installed ext4 will certainly appreciate it...since it is (I think) the best recovery you can have for you android...only thing is that some roms don't support ext4...so be aware of that.
Click to expand...
Click to collapse
If you couldn't reset the card by sending unlock cab, it simply means you did not suffer from the WP7 DRM encryption. That means your method is up until now nothing more than a faint hope. Someone has to really verify.
My theory:
It is from my perspective and experience much more likely that the file system, boot record or both had been damaged in a random way. since every partitioning tool pursues a different way of doing it's job, some might fail at your particular issue and some might get the job done. This time, it worked out for you with the 4EXT while all others failed.
Tools to try before giving up:
- windows format
- SD formatter from SD-association
- mini Tool
- EASEUS Partition Master
- Acronis
- 4EXT
To overcome the WP7 DRM encryption you would need a tool that forcefully ignores some SD-specific parameters and commands, which where originally invented to lock down these cards. As with all these systems, they only work if both content provider and content reader agree to stick you the specifications. If one doesn't, the encryption doesn't work. So far, only a certain edition of Nokias symbian does ignore the encryption command. BUT: I was hoping that also the 4EXT would maybe ignore it...
Sent from my multi talented HD2
Cotulla has indicated that the next version of MAGDLR for LEO will include the ability to unlock SD cards that have been locked by WP7.
Thanks a lot mt8 had a 8 gb card and when i installed android on nand the card was preety much dead 0 Kb space and formated using various formating tools but no luck and saw this thread and gave it a shot and i have my card with 8 gb in it. i am using cwm 3.0
Sent from my HTC HD2 using xda premium
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.