During the research in order to build the TWRP recovery for this device I have noticed a very interesting fact. Although the phone is sold as a device with 8 GB internal memory, the memory chip used inside seems to be two times bigger. There is an unused (non-formatted) partition "mmcblk0p38" labeled as userdatabak and its size is 7816 MB. There is no data there, it is a completely blank partition. It will be interesting if the mmcblk0p37 (userdata) partition can be resized in order the reported internal memory of the device to be increased. I intend to experiment with this soon and will post an update here if I have some success. If anyone is interested and is willing to share ideas regarding the resizing I will be glad to see them.
does parted print show the partitions?
The 6039k (dual sim version) already has 16gb of rom and 1,5 of ram, maybe the parts used in the mono sim one are the same but just turned down, still strange for the manufacturer to cripple the phone on porpuse, more memory means an even better phone for the price and more sales...
Demetris said:
does parted print show the partitions?
Click to expand...
Click to collapse
No it doesn't. The partition table contains a protective MBR sector, and unfortunately parted cannot handle this layout. I'm playing with a raw image of the entire phone memory and successfully resized the partitions in it. But I used gdisk and resize2fs ... gdisk however is not available in the recovery mode on the phone. In this thread @meghd00t has a static build of gdisk which should do the trick. I will try to use it later directly on the device.
SUCCESS!!!
I did it ! The static build of gdisk works perfectly (big thanks @meghd00t). Here are screenshots before the repartitioning and afterwards. I will post a guide how can be done later today.
petrov.0 said:
I did it ! The static build of gdisk works perfectly (big thanks @meghd00t). Here are screenshots before the repartitioning and afterwards. I will post a guide how can be done later today.
Click to expand...
Click to collapse
So the phone is being sold as a 8gb somewhere? If no negative repercussions then great find! I thought the 4.7 had 16gb as well.
famewolf said:
So the phone is being sold as a 8gb somewhere?
Click to expand...
Click to collapse
Yes, the version with one sim card is with 8GB internal memory even according to gsmarena and is sold like this
famewolf said:
If no negative repercussions then great find! I thought the 4.7 had 16gb as well.
Click to expand...
Click to collapse
What you mean with negative repercussions ?
petrov.0 said:
I did it ! The static build of gdisk works perfectly (big thanks @meghd00t). Here are screenshots before the repartitioning and afterwards. I will post a guide how can be done later today.
Click to expand...
Click to collapse
Good job Sir!! This is what makes XDA such an amazing place to be!! This should be put on the main XDA portal!!
Nope stop or Alcatel will change the nands on new batches
Demetris said:
Nope stop or Alcatel will change the nands on new batches
Click to expand...
Click to collapse
Too late . The guide is already in the development section.
petrov.0 said:
Yes, the version with one sim card is with 8GB internal memory even according to gsmarena and is sold like this
What you mean with negative repercussions ?
Click to expand...
Click to collapse
I wondered at the possibility the chip actually was used for something such as a system backup. I also considered the possibility they sold it as an 8gb because areas in the 2nd partition did not pass quality standards and could possibly result in data loss over time. Cpu makers used to sell quad cores that failed tests as dual cores with the other two cores "locked"....and of course folks figured out how to unlock them but the system would crash from time to time.
Maybe the 6045i has 32GB??? Jajaja
famewolf said:
I wondered at the possibility the chip actually was used for something such as a system backup.
Click to expand...
Click to collapse
Initially I thought about this too. It is possible. But how can we know this? And why you will leave a completely blank partition there ? Belive me there is nothing else than zeroes in it.
famewolf said:
I also considered the possibility they sold it as an 8gb because areas in the 2nd partition did not pass quality standards and could possibly result in data loss over time.
Click to expand...
Click to collapse
Not likely. The memory chip probably will not leave the factory with size bigger than the offered from the actual manufacturer of the device (the phone in this case). If there are bad blocks they will not be seen by the software and will not be available to the user at all. But this is only a speculation based on my limited knowledge on the NAND chips (and little googling about the NAND technology). For now my device works with internal memory twice bigger than the initial one and only the time will show how durable the memory chip is.
And hey this is xda-developers. Why we participate here if not to play with our devices ?
techware7 said:
Maybe the 6045i has 32GB??? Jajaja
Click to expand...
Click to collapse
Sorry...no userdatabak partition on the 6045.
Thanks for sharing that. Im very interested in expanding my storage but how would that work with any further update such as OTA or even rooting? Would we have to undo the partition, would the update force us to re partition afterwards, or does this thing have no influence whatsoever to all of this? Sorry if the question seems stupid
Sent from my 6039Y using Tapatalk
Rorshan said:
Thanks for sharing that. Im very interested in expanding my storage but how would that work with any further update such as OTA or even rooting? Would we have to undo the partition, would the update force us to re partition afterwards, or does this thing have no influence whatsoever to all of this? Sorry if the question seems stupid
Sent from my 6039Y using Tapatalk
Click to expand...
Click to collapse
Rooting has no relation to the expansion of the device internal memory. Regarding the OTA ... who knows. Do you have an official update? I do not. In the upgrade for the 6045 the checks were only for the system files and the recovery partition. But prior an official update we can't know how the same will work. Personally I don't think that the owner of a modified device should use the OTA prior to check what will happen after it.
petrov.0 said:
Rooting has no relation to the expansion of the device internal memory. Regarding the OTA ... who knows. Do you have an official update? I do not. In the upgrade for the 6045 the checks were only for the system files and the recovery partition. But prior an official update we can't know how the same will work. Personally I don't think that the owner of a modified device should use the OTA prior to check what will happen after it.
Click to expand...
Click to collapse
Okay. But then is there any way to undo these changes in order to get OTA updates? Would restoring from a system image or any other form of backup affect the partition and get it back to its original state? Or should we definitely not try to expand the memory if we want updates?
Rorshan said:
Okay. But then is there any way to undo these changes in order to get OTA updates?
Click to expand...
Click to collapse
The resizing of the partition does not require root access (except from the recovery during the resizing), so you will be able to check for OTA updates (from the phone) and to receive them (when such are available), if your device is not rooted. As I said earlier however, because we still don't have an official update, we don't know what will be the checks in it and also what modifications will be included.
Rorshan said:
Would restoring from a system image or any other form of backup affect the partition and get it back to its original state?
Click to expand...
Click to collapse
No, the size of the partition will remain the same. To restore its initial size you will have to use gdisk again (in order to change the GPT layout), or if you have a backup of the entire memory chip (mmcblk0) prior the repartitioning, to flash it back to the device.
Thank you for this great find. I can confirm partition #38 (7.3Gb) exists on my 6039Y -2AVDRO7. Still, I'll wait for feedback if future OTAs work ok with the extended partition space.
@petrov.0 did you try to write and read from the extended memory blocks after the new allocation? I mean, is there any chance that the partition was only simulated and data might get corrupted?
@ anyone can post the partition table from a 16Gb DualSIM 6039Y, out of curiosity? thanks
rioachim said:
Thank you for this great find. I can confirm partition #38 (7.3Gb) exists on my 6039Y -2AVDRO7. Still, I'll wait for feedback if future OTAs work ok with the extended partition space.
@petrov.0 did you try to write and read from the extended memory blocks after the new allocation? I mean, is there any chance that the partition was only simulated and data might get corrupted?
Click to expand...
Click to collapse
Yes I did. I filled all the space with raw partiton images and then checked their md5susms.
Related
hello, posting this feedback/question here as i do not have privileges to post on the actual thread itself.. http://forum.xda-developers.com/showthread.php?t=1434860
i used v1.6 w/o any issues outside the known limitations/bugs. 200/10 w/ 40ad2sdx-a2Recovery.zip @ 4Gb.
i only recently upgraded to v2.0 (i am aware there is v2.1 out, but the issues i list arent addressed in the changelog; plus i havent had time to flash the new version). 300/45 w/ 40ad2sdx-a2Recovery.zip @ 4Gb.
1. every other/random reboot causes the phone process to stop.
2. most (large) apps can not be downloaded fully from google play; the media process stops. trying to clear/stop download managers etc. do not help.
3. videos of the same bitrate/size play slower in mx player as compared to v1.6.
could any of the above issues because i used a larger system partition? i know the cache partition isnt used by the OS. df shows that i have a 250M /system and 115M /sd-ext (with 103M used after clean boot). is this always set at the same size?
if this is actually causing the problem (at least for points 1 & 2); does the remaining size after the system partition get split between data and sd-ext? if so is there any way to increase the sd-ext partition and leave the data partition small as ill be mounting it from sd card anyway?
also, does CWR actually delete the dalvik-cache if using a mounted /data directory from the sd card and not from the nand?
after reading the 40ad2sdx init script that is installed. it renames the nand data partition to sd-ext and mounts the extra partition on the sd card as the new data dir. inside the sd-ext dir it copies back from the new data dir; android system apps and leaves the rest.
i see that this rom makes mention of not needing the cache partition or swap as it uses /dev/block/mtdblock5. which would otherwise be the nand data dir or sd-ext if using 40ad2sdx.
im guessing its either because of an swap as file on this partition or apps that live in and use /dev/block/mtdblock5 for temp writing - is what causes processes to stop (ie. as a result of no more virtual memory or temp write space in the directory where they are launched).
i have since upgraded to v2.1 and reverted back to using a 165mb system partition and 5mb cache partition. which leaves a 240mb /dev/block/mtdblock5.
after using 40ad2sdx, the android apps (?and also swap as file?) take up 108mb; leaving 131mb (im guessing) for temp write space; eg. downloading apps from play.
so far i have no more issues regarding points 1 & 2.
can anyone clear up how the process for swap works with this rom? if it was mostly swap to blame, would have mounting a swap partition have solved the problem in the first place? how exactly does this rom use cache/swap on /dev/block/mtdblock5? is there some general method for some/all apps to offload cache data on android and its an actual growing cache directory and not and actual swap as file? when upgrading to v2.1 i created a swap partition anyway, would there be any benefit if i was to swapon this?
re: point 3.
this has not changed. videos of same bitrate still play slower. i also forgot to mention that apps like (guitar) solo lie, real drums and piano perfect also play slower (and are more or less now unplayable, unlike v1.6 where they played fine). i was assume this has something to do with the HWA, has this caused some problem with audio processing?
Did you flash v2.1 with fresh install? (Task29 etc.)
Check my installation here (I have no issues).
Could you tell us a parameters of your memory card? We also have seen that one HD2 can behave different than another
NexusHD2 is not using SWAP partition, so creating it has no point. Maybe you should use a smaller partition size if you have enough space. I used 512MB and i still have 200MB free after install all my apps. Rest of files storing on FAT32.
Oh, and try to format your card with SDFormatter (google it) - 1024Kb allocation size, then partition in CWM.
pavlo_js said:
Did you flash v2.1 with fresh install? (Task29 etc.)
Check my installation here (I have no issues).
Click to expand...
Click to collapse
i am only having issues with point 3. ie. app solo performs slowly as compared to using v1.6 of this rom. and videos of (high) same bitrate now play slower. have you tested a high bitrate video that played on v1.6 and compared it to how it plays on v2.0 or v2.1 since HWA? or noticed sound processing delays when using apps like solo?
also you flash the adreno drivers. why? arent they included in the rom? if you did still with no issues, what was your method?
pavlo_js said:
Could you tell us a parameters of your memory card? We also have seen that one HD2 can behave different than another
Click to expand...
Click to collapse
its 16gb, i dont know what class it is. it came with the phone. i got this phone from a friend unopened a few months ago. but please remember, the problems i report in point 3. did not exist using the same card when using v1.6 rom.
pavlo_js said:
NexusHD2 is not using SWAP partition, so creating it has no point.
Click to expand...
Click to collapse
its been a while since i compiled a kernel, but if it is a flag that needs to be switched in the build, i cant see it taking up that much extra space in the image. is there any reason why there is no support for swap? again i still do not understand the manner in how this rom uses /dev/block/mtdblock5 swap/cache or if there is any benefit to using a swap partition that will ultimately reside on the sd card anyway (which is why im guessing there is swap as file within /dev/block/mtdblock5) but i have seen other roms mention support for swap.
pavlo_js said:
Maybe you should use a smaller partition size if you have enough space. I used 512MB and i still have 200MB free after install all my apps. Rest of files storing on FAT32.
Oh, and try to format your card with SDFormatter (google it) - 1024Kb allocation size, then partition in CWM.
Click to expand...
Click to collapse
you used a 512MB system partition? i guess you have the 1gig t-mobile. i have the 9193 telstra half gig phone; as i said recently, i am now using the minimal 165mb system partition; or do you mean some other partition, and why smaller?
anserinae said:
have you tested a high bitrate video that played on v1.6 and compared it to how it plays on v2.0 or v2.1 since HWA? or noticed sound processing delays when using apps like solo?
Click to expand...
Click to collapse
Unfortunately I have no comparison with v1.6 because I`m using NexusHD2 ICS since v2.0. I didn`t notice any delays in playback.
anserinae said:
also you flash the adreno drivers. why? arent they included in the rom?
Click to expand...
Click to collapse
From what I know, drivers were released several days later than the ROM
anserinae said:
but please remember, the problems i report in point 3. did not exist using the same card when using v1.6 rom.
Click to expand...
Click to collapse
So that is strange. It must be something deeper.
anserinae said:
you used a 512MB system partition? i guess you have the 1gig t-mobile.
Click to expand...
Click to collapse
I`m sorry. It's just a misunderstanding. I have HD2 EU. I meant 512MB EXT4 partition on SD Card. But now I don`t know if this has anything to do with your problem...
Maybe someone else will find a solution for your problem. I will try to think more about it.
pavlo_js said:
Unfortunately I have no comparison with v1.6 because I`m using NexusHD2 ICS since v2.0. I didn`t notice any delays in playback.
Click to expand...
Click to collapse
well the only way to compare high bite rate videos is to install the older rom. not that i think thats worth the effort. have you tried the (guitar) Solo app? and noticed that it lags behind after a few strums?
pavlo_js said:
From what I know, drivers were released several days later than the ROM
Click to expand...
Click to collapse
how did you do this?
pavlo_js said:
Maybe someone else will find a solution for your problem. I will try to think more about it.
Click to expand...
Click to collapse
well i guess i dont think i have any major problems. problems 1 & 2 are solved. no longer being able to use the musical apps because of sound processing issues is annoying but not the end of the world; i have seen a few posts in the official thread about sound issues, nothing as specific with any real case example like ive posted here however.
maybe if i get the chance to try the adreno drivers and flash the new kernel i can report back. i just havent made time nor jumped into doing so because they dont make mention of addressing any sound issues. *fingers crossed*
most of the videos i have play fine, i kept a few high bitrate videos on the card for testing purposes between rom versions which is why i mentioned it. i only started at rom v1.5. since moving to v2.0 some that used to play fine obviously no longer do so.
thanks alot for your feedback and help anyway mate
I have a Nook Simple Touch and I just bought it yesterday. I accidentally formatted its internal memory and now it keeps asking me to restart and restart. What should I do?
welcome in my sad world :crying:
Formatting internal memory does not cause trouble . connect nook with usb cable to computer . after appearance of "Nook" drive , reformat it . likely your problem is solved ...
Re
hshsh said:
Formatting internal memory does not cause trouble .
Click to expand...
Click to collapse
Well, it depends on what you mean for internal memory. I erased all the 8 partitions, and I can't recover anything, I tried every way of the forum but nothing works for me.
FerdiBen said:
Well, it depends on what you mean for internal memory. I erased all the 8 partitions, and I can't recover anything, I tried every way of the forum but nothing works for me.
Click to expand...
Click to collapse
FerdiBen, did you find a solution?
No way...
troelsfr said:
FerdiBen, did you find a solution?
Click to expand...
Click to collapse
Unfortunatelly no, still not working.
FerdiBen said:
Unfortunatelly no, still not working.
Click to expand...
Click to collapse
Do you have the ST or STG? I messed up the system on my STG and is now running the software of ST. Since I cannot find any factory image of the STG, I just order another Nook. My plan is to backup the rom and factory partitions and make a image from the new Nook, apply it to the old and overwrite the rom + factory partitions.
If you have the STG, I can send you a full STG image once I have it (the new nook should arrive in a week or so). From this you should be able to recover the partition tables and the software (I guess, I am pretty new to this). Your only problem will then be that you are missing the original rom and factory images.
Let me know if this would be useful for you.
Thanks!
troelsfr said:
Do you have the ST or STG? I messed up the system on my STG and is now running the software of ST. Since I cannot find any factory image of the STG, I just order another Nook. My plan is to backup the rom and factory partitions and make a image from the new Nook, apply it to the old and overwrite the rom + factory partitions.
If you have the STG, I can send you a full STG image once I have it (the new nook should arrive in a week or so). From this you should be able to recover the partition tables and the software (I guess, I am pretty new to this). Your only problem will then be that you are missing the original rom and factory images.
Let me know if this would be useful for you.
Click to expand...
Click to collapse
I have the ST but if your Nook actually works with ST factory image you could backup that one, I really will appreciate that!
FerdiBen said:
I have the ST but if your Nook actually works with ST factory image you could backup that one, I really will appreciate that!
Click to expand...
Click to collapse
Sure (see PM). I seem to recall that there is a UK version of the Nook (I might be wrong). Note that mine is a US version.
Perfect!
troelsfr said:
Sure (see PM). I seem to recall that there is a UK version of the Nook (I might be wrong). Note that mine is a US version.
Click to expand...
Click to collapse
Great! Mine is US too!
Hey Guys,
I asked @kokotas to help me figure out a way to make a Patch to extend the Internal Memory as for me, due to the size of the high-end Applications and Games, is too limited 16GB, 11,70GB available only, on our Z1.
So my first Idea was to sacrifice 16Gb Internal Memory and use 64GB External SD Memory formatted in EXT4 where all the Data will be stored.
To do so we have to understand few thing and how is the structure of the Z1 Kernel is made and try to extract "ramdisk.cpio" where we can edit "init.rc" and change the line "/data mount"
As for the kernel "Autopsy" we used @krabappel2548 kernel build, I hope he is fine with that.
From what we know, the recovery is injected in the boot.img and this makes things more complicated.
Are all kernels built in this way? Even the stock ones?
Also, is there a specific rule in the way of naming the included ramdisks?
I attached a picture to make things more clear.
Any help will be appreciate.
eclyptos said:
Hey Guys,
I asked @kokotas to help me figure out a way to make a Patch to extend the Internal Memory as for me, due to the size of the high-end Applications and Games, is too limited 16GB, 11,70GB available only, on our Z1.
So my first Idea was to sacrifice 16Gb Internal Memory and use 64GB External SD Memory formatted in EXT4 where all the Data will be stored.
To do so we have to understand few thing and how is the structure of the Z1 Kernel is made and try to extract "ramdisk.cpio" where we can edit "init.rc" and change the line "/data mount"
As for the kernel "Autopsy" we used @krabappel2548 kernel build, I hope he is fine with that.
From what we know, the recovery is injected in the boot.img and this makes things more complicated.
Are all kernels built in this way? Even the stock ones?
Also, is there a specific rule in the way of naming the included ramdisks?
I attached a picture to make things more clear.
Any help will be appreciate.
Click to expand...
Click to collapse
1. Sony doesn't have a recovery partition in their phones hence developers add the recovery in the ramdisk. Also stock sony kernels doesn't have a recovery included by default only bootloader/flashmode.
2. You can't adjust the 16gb internal partition without diving deeply into the bootloader. The NAND partition profiles are hardcoded in the bootloader so modifying even just a little bit of info in the partition of the NAND would brick your device. The only way I could possibly suggest to try is hijacking the fstab and ramdisk to unmount the internal storage and mount the external storage on init. But if your issue is only about disk space I suggest you leave the internal storage and just symlink the obb folder instead of hijacking the whole internal storage. And BTW the disk IO of the internal storage is worlds apart compared to your microsd card no matter what class it is so it would be very unefficient if you use your microSD card as internal. IMHO reading the dalvik-cache 1 by 1 on startup would be pretty slow! Same goes for reading the byte code of an app once you open it.
Riyal said:
1. Sony doesn't have a recovery partition in their phones hence developers add the recovery in the ramdisk. Also stock sony kernels doesn't have a recovery included by default only bootloader/flashmode.
Click to expand...
Click to collapse
We know that. If there will be a Partition for recovery it will be much more easy and safe. That why we also used a Kernel with recovery implemented.
Riyal said:
2. You can't adjust the 16gb internal partition without diving deeply into the bootloader. The NAND partition profiles are hardcoded in the bootloader so modifying even just a little bit of info in the partition of the NAND would brick your device.
Click to expand...
Click to collapse
We trying and this is the risk of everybody who flashing a Custom Kernel.
Riyal said:
The only way I could possibly suggest to try is hijacking the fstab and ramdisk to unmount the internal storage and mount the external storage on init. But if your issue is only about disk space I suggest you leave the internal storage and just symlink the obb folder instead of hijacking the whole internal storage.
Click to expand...
Click to collapse
Maybe not the whole internal storage but implement the external SD with the internal?
Riyal said:
And BTW the disk IO of the internal storage is worlds apart compared to your microsd card no matter what class it is so it would be very unefficient if you use your microSD card as internal. IMHO reading the dalvik-cache 1 by 1 on startup would be pretty slow! Same goes for reading the byte code of an app once you open it.
Click to expand...
Click to collapse
I know the difference between Internal and External Storage. Yes the internal bandwidth is higher but like I said is worth the sacrifice, or try. Best solution will be System and Apk on Internal and link the SD to use there all Data. This is more efficient that a third Apps like Link2sd or kind of. BTW, I don't think it will be so slow but we have to try. The idea have to be made to improve what next.
So we need more Ideas, do you have any?
We know that. If there will be a Partition for recovery it will be much more easy and safe. That why we also used a Kernel with recovery implemented.
We trying and this is the risk of everybody who flashing a Custom Kernel.
A: This isn't about risk this is a fact. Once you successfully manage to alter the partition table of the built in NAND you're sure to get a hard brick from doing this.
Maybe not the whole internal storage but implement the external SD with the internal?
A: Implementing internal storage with external to support it is possible but limited. Like I said you could symlink the obb and Android folder to the external storage. That way you can allocate some of the storage space to data, dalvik etc. and the data files to the external SD which uses the most resources.
Hmm, changing the partition table has been successfully done on the xperia T
http://forum.xda-developers.com/showthread.php?t=2147997
I am not an expert here, but is this what you are talking about,
What benefit would this give a user?
Sent from my C6903 using xda app-developers app
gregbradley said:
I am not an expert here,
Click to expand...
Click to collapse
Me either, @kokotas is the Master here and all thanks should go to him for help me with this, actually the picture is of his work.
gregbradley said:
Hmm, changing the partition table has been successfully done on the xperia T
http://forum.xda-developers.com/showthread.php?t=2147997
Click to expand...
Click to collapse
We do not try to repartitioning the Sony Z1 internal memory to get a recovery bootable from different partition, which still a very good idea to develop for Z1. We try to mount the External SD instead of the Internal to expand the storage for the Z1, and here we need a patch. If kind of patch like that will really work, with some help, anyone just will format the SD in EXT4 and use what like he like, 32/64GB.
So we will be glad even to involve more "Programmers" to help us make it true.
So any way to let this work?
Jay794 said:
What benefit would this give a user?
Click to expand...
Click to collapse
Expand storage. You will be able to format a 64GB, micro SD in 2 Partitions and use 32GB by the System and 32GB like a normal SD, for example, and it will be managed by the system and not by Apps. So instead of 11,70GB you will have 30GB in System.
Surely this will just make accessing the SD card data really slow? Even with a class 10 running games off the SD card would be laggy as hell
Sent from my C6903 using xda app-developers app
Jay794 said:
Surely this will just make accessing the SD card data really slow? Even with a class 10 running games off the SD card would be laggy as hell
Click to expand...
Click to collapse
Thank you for your Opinion. Is not your problem.
Expert Request Please..
Can someone who know more than me just have a look on the attachment and answer few question, unanswered form post 1.
..for Z1
1) Are all kernels built in this way? Even the stock ones?
2) Also, is there a specific rule in the way of naming the included ramdisks?
3) Do all kernels use the sbin folder?
4) Is ramdisk.cpio the default name used in all kernels
Hey, I support the idea, I just don't see how useful it will be
Sent from my C6903 using xda app-developers app
gregbradley said:
Hmm, changing the partition table has been successfully done on the xperia T
http://forum.xda-developers.com/showthread.php?t=2147997
I am not an expert here, but is this what you are talking about,
Click to expand...
Click to collapse
Yes it is possible but not easy... I'm pretty sure the dev that made that had a hard time before he successfully got it. Also I'm pretty sure he has a JTAG box so in case his phone got hard bricked he can easily fix it again. Also IMHO that was already patched by sony on the latest s1boot so I'm sure it's alot harder than before.
Riyal said:
Yes it is possible but not easy... I'm pretty sure the dev that made that had a hard time before he successfully got it. Also I'm pretty sure he has a JTAG box so in case his phone got hard bricked he can easily fix it again. Also IMHO that was already patched by sony on the latest s1boot so I'm sure it's alot harder than before.
Click to expand...
Click to collapse
Yes, he did brick his Xperia T a few times, and the LK kernel was never really taken up because of the risks.
But it does show that it was possible to change the partition table.
As for on the xperia Z1, I don't know
gregbradley said:
Yes, he did brick his Xperia T a few times
Click to expand...
Click to collapse
I can do that.
Only problem with having the SD used all the time for system files is the risk of corruption and or a failed card.
Saying that I had it on the S3 and it worked brilliantly, was a relatively simple script which required init'd support from a custom kernel.
In all fairness, after using folder mount the worries i've had with my internal memory have gone, i'm always over 10GB of space with several really big games installed which would easily take over the whole internal memory.
dladz said:
Only problem with having the SD used all the time for system files is the risk of corruption and or a failed card.
Click to expand...
Click to collapse
Here you sound like Google.
dladz said:
Saying that I had it on the S3 and it worked brilliantly, was a relatively simple script which required init'd support from a custom kernel.
Click to expand...
Click to collapse
I had it on HD2 as well and never had any issues and I had full control of my device, this is what also we looking at, no restrictions and no storage limit on a high-end device. I will be glad to see 64GB recognized as my System Storage instead using Apps on Apps like the Mount Folder.
I play Most Wanted, of curse a bit slow, on mine HD2 so if we get this work we will have 40mb/s in writing and reading, instead of 70mb/s in internal, due to the limitation of the slot. I think even with a kind of transfare like that you will never see any slow down of the performance on your device.
Some Smart One will say now to me "Why then you don't go back to HTC". That's the point! Imagine have Z1 with such a Development and full control of you device.
At last it's a choice of the user if he want apply that patch or not, but I think if this will be possible many will be happy, but like I can see, we don't have much support due to the risk and any Developer will not take this in consideration, or maybe will, but apparently not now.
eclyptos said:
Here you sound like Google.
I had it on HD2 as well and never had any issues and I had full control of my device, this is what also we looking at, no restrictions and no storage limit on a high-end device. I will be glad to see 64GB recognized as my System Storage instead using Apps on Apps like the Mount Folder.
I play Most Wanted, of curse a bit slow, on mine HD2 so if we get this work we will have 40mb/s in writing and reading, instead of 70mb/s in internal, due to the limitation of the slot. I think even with a kind of transfare like that you will never see any slow down of the performance on your device.
Some Smart One will say now to me "Why then you don't go back to HTC". That's the point! Imagine have Z1 with such a Development and full control of you device.
At last it's a choice of the user if he want apply that patch or not, but I think if this will be possible many will be happy, but like I can see, we don't have much support due to the risk and any Developer will not take this in consideration, or maybe will, but apparently not now.
Click to expand...
Click to collapse
I actually probably will be going back to HTC after this phone. Doubt it'll be the M8, although i do like it, the camera is sup par though and i've come accustomed to a decent picture.
dladz said:
I actually probably will be going back to HTC after this phone. Doubt it'll be the M8, although i do like it, the camera is sup par though and i've come accustomed to a decent picture.
Click to expand...
Click to collapse
I know, I try to don't give up on it too but to much to deal with. The camera is good but I was disappointed anyway. So I was thinking about 64GB HTC One, or wait for the next release and I will finally be fine. For the moment I try to deal with Z1, I hope somewhere we will have 64GB system storage , this maybe will change my mind, everything is possible.
eclyptos said:
I know, I try to don't give up on it too but to much to deal with. The camera is good but I was disappointed anyway. So I was thinking about 64GB HTC One, or wait for the next release and I will finally be fine. For the moment I try to deal with Z1, I hope somewhere we will have 64GB system storage , this maybe will change my mind, everything is possible.
Click to expand...
Click to collapse
Have you used folder mount before? It really is a great app and i've not needed the larger internal storage since using it.
It has been over 2 weeks now with this problem. Both cards are SanDisk 64GB Micro SD Cards...
I've tried accessing the micro SD card in different operating system and yet can't format it...
Used linux, Windows 7 and different mobile phones with different operating systems... All failed!
I am so sick of it need some urgent help to fix these... I can't send them back because i am in Kabul Afghanistan so am stuck with only option is to try fix it..
I can access the files saved on it which means Read ONLY but can't Write. Tried deleting and work! so not sure what is going on...
i tried lots of software on windows to delete the partition or format it in low level or just normal format but all useless
Can someone help out in this regard? I hope to get some proper help...
Cheers
The title most definitely does not say it all. If you have any realistic expectation of useful assistance, you need to give a detailed description of your issue, what you have done to try and resolve it or narrow down the possible causes. And in particular, verbatim error messages, your phone model and firmware version.
You imply that you are seeing some filesystem error message. But it's hard to even know what the ostensible error due to the lack of information in your original post. It's difficult to believe that it couldn't be fixed with a system reset and wiping the cache and /or NAND. In rare cases you might have partition corruption or a hardware fault. But we can't do anything unless you provide specific details.
.
fffft said:
The title most definitely does not say it all. If you have any realistic expectation of useful assistance, you need to give a detailed description of your issue, what you have done to try and resolve it or narrow down the possible causes. And in particular, verbatim error messages, your phone model and firmware version.
You imply that you are seeing some filesystem error message. But it's hard to even know what the ostensible error due to the lack of information in your original post. It's difficult to believe that it couldn't be fixed with a system reset and wiping the cache and /or NAND. In rare cases you might have partition corruption or a hardware fault. But we can't do anything unless you provide specific details.
.
Click to expand...
Click to collapse
hm... Not sure whether you have had such problem in past or not as i mentioned it is Dirty Bit problem so i am not sure what else are you after? the problem is the damn SD cards now they are original SanDisk 64GB sdhc X cards i am not sure whether the cache or anything else could be faulty as i have wiped it all... maybe i have missed something but i can't think of anything.
The rom that i am currently using is [ROM][G900F] X-Note TMT v.5.0 NG2 *Floating-True-Multidpi-Touchwiz* [4.4.2]. The previous ROM was AllianceROM_V5_S5_NG2_Final.
I would like to clear that the problem persist in windows and other phones too. I can't format sd cards with android nor with low level formatting or diskpart! so the problem remains the same!
Anyways.. i hope to get some proper help.
supermaster said:
hm... Not sure whether you have had such problem in past or not as i mentioned it is Dirty Bit problem so i am not sure what else are you after? the problem is the damn SD cards now they are original SanDisk 64GB sdhc X cards i am not sure whether the cache or anything else could be faulty as i have wiped it all... maybe i have missed something but i can't think of anything.
The rom that i am currently using is [ROM][G900F] X-Note TMT v.5.0 NG2 *Floating-True-Multidpi-Touchwiz* [4.4.2]. The previous ROM was AllianceROM_V5_S5_NG2_Final.
I would like to clear that the problem persist in windows and other phones too. I can't format sd cards with android nor with low level formatting or diskpart! so the problem remains the same!
Anyways.. i hope to get some proper help.
Click to expand...
Click to collapse
What do you mean you cannot LLF in diskpart? Have you deleted the partition in diskpart using a card reader and then ran a chkdsk in Windows to verify there are no issues?
russ18uk said:
What do you mean you cannot LLF in diskpart? Have you deleted the partition in diskpart using a card reader and then ran a chkdsk in Windows to verify there are no issues?
Click to expand...
Click to collapse
Do you know what is Dirty Bit? if yes then you should know you can't write to the Dirty disk nether can format nor can delete it in diskpart or whatever else... i tried everything i could low level format to normal format method!
supermaster said:
Do you know what is Dirty Bit? if yes then you should know you can't write to the Dirty disk nether can format nor can delete it in diskpart or whatever else... i tried everything i could low level format to normal format method!
Click to expand...
Click to collapse
Yes you can format a drive with a dirty bit. It should be fixed using Chkdsk - Windows will tell you if you have a dirty bit and offer you to scan and fix. If you don't then it's probably not a dirty bit but either a bug with your system or a faulty SD card. I never said about writing to the card.
Stop being so condescending and you might get more help from others.
russ18uk said:
Yes you can format a drive with a dirty bit. It should be fixed using Chkdsk - Windows will tell you if you have a dirty bit and offer you to scan and fix. If you don't then it's probably not a dirty bit but either a bug with your system or a faulty SD card. I never said about writing to the card.
Stop being so condescending and you might get more help from others.
Click to expand...
Click to collapse
I am not sure where do you get the idea of such arrogance? if i had anything as such wouldn't i be here asking for help?
well it doesn't format nether can write anything to it ... i tried everything as i said in my posts ChKDSK, format, low level format, alternative methods for formatting using different tools and using hex apps for searching the dirty bit but can't locate. Operating system is Win 7 ult. if it was one sd card then would have been easy to understand and say yeah this should be the sd card but as i have two sd cards and both happen to be in this situation now i dont' know what could be the cause and how to fix.
Both SD cards show dirty as i checked it with the dirty volume command so that's not something i am making up or trying to make my life tough! anyways... i want some help and i am not arrogance that isn't in my character nether i ever been so lets keep that bit aside and rather get some proper help please.
Cheers
OK, well, your last chance before you RMA them would be to try a Linux Live CD/USB, try and find your SD card using ls /dev/m* to find the mmcblk number, unmount it if needed, and then try sudo fsck -a /dev/mmcblk(output of ls). If not you probably have a duff batch or fakes or just plain unlucky.
russ18uk said:
OK, well, your last chance before you RMA them would be to try a Linux Live CD/USB, try and find your SD card using ls /dev/m* to find the mmcblk number, unmount it if needed, and then try sudo fsck -a /dev/mmcblk(output of ls). If not you probably have a duff batch or fakes or just plain unlucky.
Click to expand...
Click to collapse
No luck i am completely speechless what is wrong with it? i never have had such problem with HDD/MMC that i could fix or used any application to fix but wouldn't! now this said it's giving me big headache
i am not sure what happened to these sd cards whilst i take care of them quite good and never let it drop or even overheat etc.
I dont' know what to do next? any other options in hand? maybe someone else have had such problem with Dirty Bit? what is making me angry the most is not being able to format it regardless of methods and apps that i used! what is wrong with this damn thing i have backed up my data and can't write a character to damn SD cards!
Anyone else can help?
cheers
Stilll waiting...
supermaster said:
Stilll waiting...
Click to expand...
Click to collapse
still waiting for help!
Updated the main thread... anyone who is professional and can help?
supermaster said:
Stilll waiting...
Click to expand...
Click to collapse
supermaster said:
still waiting for help!
Click to expand...
Click to collapse
supermaster said:
anyone who is professional and can help?
Click to expand...
Click to collapse
Your replies explain why you don't have more replies.
You spurned an earlier suggestion to provide more detail so that better advice could be offered, so I'll just concur with the poster who concluded
russ18u said:
Stop being so condescending and you might get more help from others.
Click to expand...
Click to collapse
Good luck with your problems
.
I had The same problem with the same card! Take and exchange Thar card probably a bad batch
Sent from my SM-G900W8 using XDA Premium HD app
fffft said:
Your replies explain why you don't have more replies.
You spurned an earlier suggestion to provide more detail so that better advice could be offered, so I'll just concur with the poster who concluded
Good luck with your problems
.
Click to expand...
Click to collapse
I've provided details and if one doesn't know what is Dirty Bit why even bother asking any questions that aren't even helpful? Guess the simple and straight forward answer hurts quite a lot aye? It doesn't bother me when people ask relative questions whether be 1 or thousands but when someone doesn't have a clue what is going on and what's wrong and try to show they know what is going on and can solve the problem and try to ask questions like kids then anyone in my case would reply with whatever i have done.
Am not arrogant or ignorant... i am here to get some help if one can then would regardless of the replies and people like your self else doesn't matter end of the day nothing gain nothing lost...
I know for sure one thing, if i leave this thread to die then one who has problem want to read this thread would like to get some conclusion and help rather than just reading things that aren't worth wasting time on, as one would need help not reading unrelated things!
Ta
It may completely just be an issue with the card itself. My Coworker had to send 3 different SanDisk MicroSD cards back to the company for replacement due to there being a problem with a bunch of cards getting corrupted.
http://www.phonearena.com/news/SanDisk-says-it-produced-some-bad-32GB-and-64GB-microSD-cards_id40986
You can't write to am external SD in android 4.4 u have to get an app to enable a workaround fx file explorer has the work around , this only work if your rooted btw
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
Same issue
supermaster said:
Stilll waiting...
Click to expand...
Click to collapse
I am having a similar problem with my sd card.
SM-G900A Galaxy S5
ScanDisk 64 GB micro HDXD card.
I can read all data on card, but can't write/change/delete anything.
Odd thing is that it doesn't throw any errors when you try to make a change or write to the disk.... It just appears to complete successfully, then the files or whatnot just revert/disappear.
Suggestions?
SanDisk SDXC is most probably the culprit!
Considering I encountered this write protect error TWICE with the exact same product, and after having read forums that show it's a common problem, I conclude that the problem is with either this specific SanDisk product or a particular batch of this product:
Exact product specs: SanDisk Ultra 64 GB MicroSDXC Class 10 UHS-1 Memory Card with Adapter (SDSDQU-064G-AFFP-A)
These carry a lifetime warranty. A word of advice: if you go for a replacement, ask for a different 64GB model, or try a different size of the same model (I got 2 x 32GB cards instead). If they insist on giving back the exact same model, I'd suggest you use that card anywhere except a smartphone!
PS: Although I encountered this error with my Samsung Galaxy S4, I have reason to believe that this problem could occur with other smartphones too... considering the error pattern and the fact that none of the suggested remedies work (SDformat, diskpart, etc.)
The dual boot 6 thread says it creates a secure micro SD partition but Its only for the 128gb devices. I have the 240gb device and I'm wondering if there is another way to make a partition like that.
Unfortunately, I'm not sure what you mean. Do you want to have a split SD partition or reformat the internal "SD card" (storage)?
I want to create a new separate partition one that would not be wiped when you format data. In the dual boot thread it says that it creates a new partition so there is a way I'm just wondering how to do it. Unfortunately the dual boot only works on 128gb device I got the 240...
Macusercom said:
Unfortunately, I'm not sure what you mean. Do you want to have a split SD partition or reformat the internal "SD card" (storage)?
Click to expand...
Click to collapse
jessejamesd2i said:
I want to create a new separate partition one that would not be wiped when you format data. In the dual boot thread it says that it creates a new partition so there is a way I'm just wondering how to do it. Unfortunately the dual boot only works on 128gb device I got the 240...
Click to expand...
Click to collapse
I'm not sure if this is easily possible due to how the super partition works. Unfortunately, this is out of my knowledge. There are ways of repartitioning your device but I'm not sure how it plays together with encryption
I found a guide for doing it but i cant because i need a twrp that has the commands to create or modify partition sizes. I have some knowledge about how to do it because i used to play with linux alot when i was younger. I know how to do it but im worried about encryption & whatever else that i dont know. All i know is they figured out how with the dualsix, I sent him a pm asking how hopefully it was him who compiled the scripts & knows exactly what to do. I really appreciate you taking the time to try to help. I love XDA & its members everyone is quick to try and help and there is not very many people who talk **** and act disrespectful. Thanks for being one of those awesome people!
Macusercom said:
I'm not sure if this is easily possible due to how the super partition works. Unfortunately, this is out of my knowledge. There are ways of repartitioning your device but I'm not sure how it plays together with encryption
Click to expand...
Click to collapse