hey can anybody guide me to the right way of partitioning my hd2 nand(tmobile) so i can install dl desire z from dandiest and get faster smoother working rom....plus 2 see 3000 on my quadrant scores.......i already have desire z 4.1 but its not as smooth as i thought it would be....i heard running the rom from a partition would increase read and write speeds...so before i install 4.2 i would like to know how to partition my nand to run the rom off of it....thank u.
Have you tried the video guide posted by locn?
http://forum.xda-developers.com/showpost.php?p=11656790&postcount=3943
there's also a lot of partition tutorials all over that thread, xda & the web, I could link them for you, but that would deprive you of all the joy you will get when you actually find such info for yourself.
Good luck
Kam
Yeah I found partition videos and tutorials...a lot ...but they were all for partitioning memory cards not nand memory ..
Sent from my DL DesireZ v4.1 using XDA App
trinfinate said:
Yeah I found partition videos and tutorials...a lot ...but they were all for partitioning memory cards not nand memory ..
Sent from my DL DesireZ v4.1 using XDA App
Click to expand...
Click to collapse
Exactly. I'm running HyperDroidGBX and it says my internal storage is only 729MB, out of 1024MB. So just roughly 256MB Of the nand is being used for the system/data/cache partitions. What I want to do is resize all my nand partitions to allow for a data partition of atleast 900MB of internal storage and still have sufficiently sized system/cache partitions as necessary. What are the sizes of the partitions by standard? How do we use Android SDK and AVD "Andriod Virtural Device" on a Windows desktop to adjust the partition sizes?
THANKS!
BTW - It's called the mtd partitions. So look up how to resize mtd partitions android sdk avd.
Look in the folder where your cwm instal files are.one is called flash.cfg. open that in notepad, each line is one of the partitions. Adjust size and flash.
(Allsize means all the leftover space)
If you aren't using a clockwork rom, then the same applies.... in the daf rom folder is flash.cfg
If it is a daf rom, if you merge the partition info from your flash.cfg with the info in a cwm flash.cfg, and copy in the recovery.img you can flash your daf rom with your partition layout and apply cwm recovery at the same time.
samsamuel said:
Look in the folder where your cwm instal files are.one is called flash.cfg. open that in notepad, each line is one of the partitions. Adjust size and flash.
(Allsize means all the leftover space)
If you aren't using a clockwork rom, then the same applies.... in the daf rom folder is flash.cfg
If it is a daf rom, if you merge the partition info from your flash.cfg with the info in a cwm flash.cfg, and copy in the recovery.img you can flash your daf rom with your partition layout and apply cwm recovery at the same time.
Click to expand...
Click to collapse
Wow! Your great man! Ok I'm using HyperdroidGBX v11 and CWM 1.13. Do i need to edit the hyperdroidgbx flash.cfg and the CWM flash.cfg? What do you mean by copy in the recovery.img. So what should I do? Should i just adjust partition sizes in the cwm flash.cfg and then just flash hyperdroid or even better i could perform a nandroid backup and just restore right?
Ok so its a cwm rom so only the cwm flash.cfg exists.
However you should find the data part is already set to allsize meaning it takes up all the space after the small fixed size parts are done.
Do you have an ext partition on your SD card? If so, the rom is automatically putting apps there instead of on the phone.
(At least that's my understanding of app2sd+ enabled roms, certainly I never manually move apps to the SD card, yet there they are on my SD in the ext part. If you manually choose to move apps to SD in app manager, it takes them from the ext part and puts them on the fat32 partition.)
Get rid of your ext part and re try before you bother editing flash.cfg
If someone who knows yes or no could confirm my understanding of apps2sd+, that would be great.
Ok so i downloaded the recovery_150M is what i had on it. Edited the partition sizes. Now after flashing MAGLDR 1.13 edited flash.cfg, I'm stuck at the boot screen where the android is and it doesn't do anything. Do i need to edit a flash.cfg within a CWM folder? I tried several different sizes. IDK why it won't boot.... No ext3 and no i don't want apps installed to sd automatically, i have 1 fat32 partition on class 10 32gb stick. I want all apps to be installed to nand and i don't want my sd to be used at all unless i specify to move the data to sd card. Do i need to flash in HARDSPL? or on FLASHER in MAGLDR?
There was no need to do magldr again, only cwm, having looked in flash.cfg in the cwm folder.
Going back to your post 1 "how do I partition",,, that's what cwm is doing, creating partitions as per instructions in flash.cfg. you can't run nand android without partitioning first, therefore the answer to your original question is "it already is partitioned"
Related
Hi All,
I need real help with ClockworkMod Recovery. I have been installing Android on HD2 using storage card (haret.exe) method. Then I moved to NAND without any problems.
But I am not able to understand ClockworkMod Recovery at all. I looked at lots of threads and also the main thread for ClockworkMod Recovery. I know how to install it. I have installed it on my phone. But for some reason I was stuck in the loop after installing the ROM {[22 JAN] -=MDJ's CyanogenMod 7 v. 2.6 [A2SD+][GRH78C][RMNET][Kernel: MDJ S10.4 OC]}. I did exactly same as the video tutorial says. My radios and HSPL is fine. Coz I am able to use the same ROM in NAND mode. But still in ClockworkMod Recovery mode the phone kept restarting and never got to the main screen.
I also do not know what ext2, ext3, ext4 partitions are. Do I need to make them before installing the ROM? Also on the main thread for ClockworkMod Recovery, it has 3 partition files. 250MB, 350MB and 450MB. I do not know what that is. Which one to use for which ROM and what are the differences between them?
What is the use of ClockworkMod Recovery if I have to flash this partitions every time I install new ROM?
Also can someone tell me what backing up the ROM means? Does it mean I can back up my current one and flash new one, and if I do not like the new one I can restore the old one in the same state (with my APPS and SETTINGS)?
Please please help me with ClockworkMod Recovery fundamentals. I would really appreciate it.
One more thing, I would not post a question if I haven't looked around enough for answers. As you can see I have been doing this from months, but only asked one question before and this is the second one. So please do not take me for someone who does not look around for answers. I do, its just that I did not find anything real good to explain me from the bottom. So please someone help me out.
Thanks in advance.
EXT partitions can be thought of as extended partitions on your SD card. They are used to "extend" your storage capacity. Some ROMS place some of the ROM files on the SD-EXT partition. This is done particularly for the EU HD2 where it has only half the storage on-board that the TMOUS HD2 does. If you are using a ROM that requires one you do have to create the partitions before installing/flashing the ROM.
The three different flash.cfg files on the CWM thread are files used to instruct DFT how to re-partition your on-board storage (NAND). There are several partitions, up to 16 at the moment. Some ROM's use 4 partitions, some use 6 or more. Typically, non-CWM ROM's use only 4 partitions (boot, system, data, cache), whereas CWM ROM's use those same ones as well as a miscellaneous and recovery partition.
The main reason for the different files is that some ROM's use more space for the system partition. The different flash.cfg files just simply allocate more or less space to the system partition.
You don't technically have to flash new partitions every time you flash a new ROM. As long as you know how to modify the ROM to work with your current partition setup it will work. Or, get ROM's that use the same type of partition layouts. Since the release of CWM, more ROM's are becoming available for installation via the ZIP deployment method in CWM, which means they ALL use the same partition (with exception of the system partition size) setup.
If you have a TMOUS HD2 with plenty of onboard storage it's easier to just create a larger system partition and never have to worry about repartitioning. That's what I did. I have a 450 MB system partition and every time I deploy a new CWM ZIP ROM I don't have to repartition anything.
You nailed it on the head about backing up via CWM. It backs up all your partitions (boot, system, cache, sd-ext, data, etc) and saves them to your SD card. That way you can flash a new ROM or do a hard reset. Then later if you want you can do a full restore and be exactly where you left off before doing so. That is, if you flash a ROM that has the same partition layout. If you flash a ROM with a different partition layout, the restore may or may not work until you repartition the same as the original ROM was when you flashed it.
The only issue with all this is that since there isn't a set standard yet for ROM's and their partition layouts any ROM chef can define their own partition scheme which can make for a hassle when trying different ROM's. I expect that at some point there will be a standard set of partitions that will be used between all different chefs to make things easier. CWM ROM deployments and updates are definitely the future of this and how all native Android devices are handled. I imagine that will become the case down the road for the HD2 as well.
Hopefully that clears it up for you a bit. Sorry about writing a novel...
Digital Outcast said:
EXT partitions can be thought of as extended partitions on your SD card. They are used to "extend" your storage capacity. Some ROMS place some of the ROM files on the SD-EXT partition. This is done particularly for the EU HD2 where it has only half the storage on-board that the TMOUS HD2 does. If you are using a ROM that requires one you do have to create the partitions before installing/flashing the ROM.
The three different flash.cfg files on the CWM thread are files used to instruct DFT how to re-partition your on-board storage (NAND). There are several partitions, up to 16 at the moment. Some ROM's use 4 partitions, some use 6 or more. Typically, non-CWM ROM's use only 4 partitions (boot, system, data, cache), whereas CWM ROM's use those same ones as well as a miscellaneous and recovery partition.
The main reason for the different files is that some ROM's use more space for the system partition. The different flash.cfg files just simply allocate more or less space to the system partition.
You don't technically have to flash new partitions every time you flash a new ROM. As long as you know how to modify the ROM to work with your current partition setup it will work. Or, get ROM's that use the same type of partition layouts. Since the release of CWM, more ROM's are becoming available for installation via the ZIP deployment method in CWM, which means they ALL use the same partition (with exception of the system partition size) setup.
If you have a TMOUS HD2 with plenty of onboard storage it's easier to just create a larger system partition and never have to worry about repartitioning. That's what I did. I have a 450 MB system partition and every time I deploy a new CWM ZIP ROM I don't have to repartition anything.
You nailed it on the head about backing up via CWM. It backs up all your partitions (boot, system, cache, sd-ext, data, etc) and saves them to your SD card. That way you can flash a new ROM or do a hard reset. Then later if you want you can do a full restore and be exactly where you left off before doing so. That is, if you flash a ROM that has the same partition layout. If you flash a ROM with a different partition layout, the restore may or may not work until you repartition the same as the original ROM was when you flashed it.
The only issue with all this is that since there isn't a set standard yet for ROM's and their partition layouts any ROM chef can define their own partition scheme which can make for a hassle when trying different ROM's. I expect that at some point there will be a standard set of partitions that will be used between all different chefs to make things easier. CWM ROM deployments and updates are definitely the future of this and how all native Android devices are handled. I imagine that will become the case down the road for the HD2 as well.
Hopefully that clears it up for you a bit. Sorry about writing a novel...
Click to expand...
Click to collapse
Amazing explanation. Thanks a lottt man. Just one more question, I have TMOUS HD2 abd I did the same thing as you said. 450MB of partition. And then tried to install the MDJ's CM7 ROM. I got the message saying the ROM is successfully installed. and then I rebooted my phone. But it kept rebooting itself. Any particular reason you know of?
jalshah05 said:
Amazing explanation. Thanks a lottt man. Just one more question, I have TMOUS HD2 abd I did the same thing as you said. 450MB of partition. And then tried to install the MDJ's CM7 ROM. I got the message saying the ROM is successfully installed. and then I rebooted my phone. But it kept rebooting itself. Any particular reason you know of?
Click to expand...
Click to collapse
Is this using the 400 MB flash.cfg file from the CWM thread? The reason I ask is that I checked that flash.cfg file and the boot partition is flagged as the bootable partition. I'm not familiar with the CM7 ROM from MDJ, but is it set to deploy via CWM with a boot folder in the ZIP file?
Also, have you run logcat (if you're familiar with that) while the issue is happening to see what is going on?
To be very frank I did not understand what you just told me sir. Only thing I can tell for sure is I downloaded the .zip file from the thread at http://forum.xda-developers.com/showthread.php?t=877777 . And I do not know what logcat is. I am sure you must be thinking that I am an idiot. Forgive me for my ignorance.
Google is your friend!
I'm a better one: http://wiki.cyanogenmod.com/index.php?title=Logcat
Edit: very interesting read by the way, Digital Outcast. Much appreciated!
Digital Outcast said:
Is this using the 400 MB flash.cfg file from the CWM thread? The reason I ask is that I checked that flash.cfg file and the boot partition is flagged as the bootable partition. I'm not familiar with the CM7 ROM from MDJ, but is it set to deploy via CWM with a boot folder in the ZIP file?
Also, have you run logcat (if you're familiar with that) while the issue is happening to see what is going on?
Click to expand...
Click to collapse
Thanks a lott Digital Outcast for this amazing explanation. I hope I can get the Recovery mode working. I will try some different roms and see what can be done. meanwhile if you get chance please explain me your response "Is this using the 400 MB flash.cfg file from the CWM thread? The reason I ask is that I checked that flash.cfg file and the boot partition is flagged as the bootable partition. I'm not familiar with the CM7 ROM from MDJ, but is it set to deploy via CWM with a boot folder in the ZIP file?
Also, have you run logcat (if you're familiar with that) while the issue is happening to see what is going on?"
Thanks a lott once again.
Hi.
After getting my HD2 last week I tentatively but successfully flashed my first ROM, which was the Rafdroid 4.0.2.
I had correct radio.
I installed HSPL 2.08.
I installed MAGLDR 1.13
I got the Rafdroid ZIP file
Prepared SD card with Primary Partition and 1GB ext3 partition.
Downloaded the 400MB CWM partition and flashed to HD2
Then installed the Rafdroid Zip from SD card via CWM.
Everything seemed to go fine and I've been using the Rafdroid for a week. But now I want to try a new ROM, specifically the NexusHD2-Gingerbread V2.7 ROM.
Now I'am a bit unsure on how best to proceed still being new to the world of NAND. A few things in the Nexus ROM thread confuse me.
Installing CWM_Recovery_for_NexusHD2 (135MB system and 2MB cache)
Does this mean I need to reflash to CWM partiton size 1.3v 150MB? I'm unsure what the 2MB cache means.
Enter ClockworkMod Recovery when you're on MAGLDR 1.13 (hold "Power" button during boot) and select "AD Recovery" or "Boot AD SD" (if ever copied CWM's initrd.gz and zImage to SD).
The first part of this I understand but I don't know what the bold bit is. Do I need to copy these files to my sd card? I didn't do anything like this when I flashed Rafdoid.
Thanks for your time. Hopefully a few pointers can get me on my way
Yes, reflash cwm but with a different partition layout.
(look in cwm folder find flash.cfg, open it in notepad, you will see the numbers to change)
The bit in bold - ignore that, there are two types of cwm, one that installs to the nand, like you have, and one that runs from sd, so ignore the sd bit.
So,
Into magldr,,
usb flashing,,,
flash the new layout with the sizes the rom suggests, (you can tinker with your own sizes as you get used to changing, it's the system size that is important, a few meg bigger than the unzipped size of the system folder in the rom.zip)
When that completes, back into magldr,
Ad recovery (option 8 I think) to boot cwm, and flash the rom.
You can set the system size to what you like, so long as it is bigger than the roms system folder, but anything over is wasted, it doesn't count towards internal storage, so if the rom says 135 and you flash 150 layout, there is 15meg wasted space. (that being said, 150 is a good size to use, since quite a few roms use that or smaller,, sense free roms will mostly all fit in 150 layouts,) meaning you can switch between them without flashing cwm again. Also means you can restore cwm backups from any of them into that layout, so you can set one up, take backup, flash another, take backup, flash a third, then any time restore either of the backups.
Use flash.cfg to change partition.. Btw. I read in NexusHD rom topic you need to flash 135MB system and 2MB cache.
About the second problem:
Just make sure you have zipped rom on your sd card, enter MAGLDR, select AD Recovery and flash zip.
I think the second way is possible if you manually copy those files, never tried it.
Hi Sam and volv.
Many thanks for taking the time to answer my queries!
Should I get rid of the Rafdroid sd card layout and just re format the card to FAT32? I don't think I'll be going back to it.
Another thing about the backup - where are they stored - in the NAND memory or on the sd card for loading back into NAND?
Everything else you've posted has been very clear and super helpful. I'll definitely be a lot more confident at flashing the ROM tomorrow!
Thank you.
Warren_Orange said:
Hi Sam and volv.
Many thanks for taking the time to answer my queries!
Should I get rid of the Rafdroid sd card layout and just re format the card to FAT32? I don't think I'll be going back to it.
Another thing about the backup - where are they stored - in the NAND memory or on the sd card for loading back into NAND?
Everything else you've posted has been very clear and super helpful. I'll definitely be a lot more confident at flashing the ROM tomorrow!
Thank you.
Click to expand...
Click to collapse
Hi,
Before starting anything,BACKUP YOUR STUFF.
Go to ad recovery>backup and restore and make a backup of your current system and data.This is stored on your sd card in clockworkmod/backup.
Next ,flash your new partition.
Then go to ad recovery and wipe data,cache partition,and dalvik(advanced)
Then go back and choose install zip from sd card(having placed your new ROM zip on the root of your sd card using a card reader)
Most roms support using the ext partition, so definitely keep it.
Before you flash, in cwm, do a 'wipe data/factory reset','wipe cache', and then 'advanced - wipe dalvik cache'. This will clear out the data and such from the previous rom, so no need to format it. (there may be some leftover folders from certain apps in the fat32 partition, you can manually delete them as and if necessary, shouldnt cause any problems)
backups get saved to the sd card, in a folder called clockwork, so be sure and back that up if you plan on formatting your sd card.
Hi again.
I just want to say the flash went like clockwork (no pun intended ) The NexusHD ROM has a really nice feel to it. Its my first taste of stock Android and I like it.
I was going to sell the HD2 and keep my old Hero, but I'm not so sure now after trying NEXUS HD ROM.
Hmmn decisions decisions.
Once again thanks for all your help. It definitely filled in the missing blanks.
Ta Ta
you can use every flash.cfg and change the values to the needet. Run the flash tool and after that flash the zip via recovery
I want to re-partition my NAND, and don't have windows around. So I downloaded cwm-sd.zip and cwm.zip. I extracted cwm-sd.zip to the root of my sd card , copied cwm.zip with appropriate flash.cfg inserted. I will reboot, go to Mahler, ad sd. (As described)
But I will get sd kernel open failed.
I try with the latest stable clockworkmod. 5.0.26
Any ideas what the problem might be.
I want to repart nand only, so any other ideas not including windows pc are welcome, I have pc with Ubuntu on it.
Sent from my HTC HD2 using xda premium
1st-sorry, don't know why its not entering cwm
But
2n- it doesn't work like that. you can't repartition magldr from SD. If it did boot "ad SD" it would run cwm, nothing more. The SD cwm is so you can backup/flash roms without having nand cwm, but it relies on the nand already being partitioned.
If you want to partition from SD use clk instead of magldr.
I have a working CWM installed. I just want to re-part, really.
According to this thread,
http://forum.xda-developers.com/showthread.php?t=987531
it seems this should be possible. I dont want to re-install CWM though, I just want to re-part. I can cope with terminal and adb , I think, and these options are (I think) available under linux, but I dont know how to do it
Well, I disagree, but hey, you have the info. I'll be interested in reading your how-to if you manage it.
(Also, from your other threads you seem not to have noticed that partitioning also installs cwm at the same time)
deckoff said:
I have a working CWM installed. I just want to re-part, really.
According to this thread,
http://forum.xda-developers.com/showthread.php?t=987531
it seems this should be possible. I dont want to re-install CWM though, I just want to re-part. I can cope with terminal and adb , I think, and these options are (I think) available under linux, but I dont know how to do it
Click to expand...
Click to collapse
Even with this link i failed at setting up ADB on my Ubuntu machine but you may have better luck than i.
I am almost 100% sure I managed to do this way back in time. What I don't know is if I can use adb to partition NAND , and if so, how. Not to mention that the phone is not the typical android phone.
Sent from my HTC HD2 using xda premium
samsamuel said:
Well, I disagree, but hey, you have the info. I'll be interested in reading your how-to if you manage it.
(Also, from your other threads you seem not to have noticed that partitioning also installs cwm at the same time)
Click to expand...
Click to collapse
I have noticed it, I assume it will install over the existing one...
I dont have any info, I just cite a source. The process apparently fails for me, so I am stuck. I am probably misunderstanding it.
You CAN install cwm over the current one, by booting into cwm and then using flash zip from sd card, and selecting the new cwm.zip from your sd (just like flashing a rom), BUT this doesn't partition anything, it is just loading the contents of the zip into the recovery partition that already exists.
trust me, if you want to partition the phone without a pc, you need to be using cLK.
From the link above:
For MAGLDR up to 1.13, booting from SDCard (SD-files version):
Download the file attached
Extract the files to the root directory of your sdcard
Start recovery within MAGLDR with menu point "AD SD"
Recovery should start
You're done
Click to expand...
Click to collapse
What exactly is this used method used for? It is described in the Install CWM methods(if I am not wrong)
Flash.cfg files in clockworkmod.zip are used to re-part data and user partitions. What happens if I re-flash CWM.zip with custom flash.cfg file inside via method at the top of the post. Or just flashing CWM.zip with flash.cfg via the installed CWM. What and when reads the flash.cfg files and act accordingly?
It is not a question of trust, I would love to know the basic workflow of the process
The cwm that comes with a flash,cfg is for flashing to nand via usb - magldr - usb flasher, or the cLK equivalent.
the cwm-sd version, and the process outlined in your quote, is used to boot into a valid working copy of cwm from sd card instead of the nand recovery partition.
For example if your nand version of cwm gets corrupted, .. for example trying to use rom manager under magldr, corrupts the nand copy of cwm, so you can load to the sd version of cwm, and use that to do a backup of your rom and/or reinstall cwm into the nand partition. It does NOT let you repartition the nand in the process. The partitioning happens via teh daf.exe and flash.cfg, , its daf.exe that does it. cwm just works with teh contents of teh partitions, not teh actual partitions.
If you were really tight on space, you could omit the nand recovery partition altogether and only ever run cwm from sd, gaining a whole FIVE MEG to put towards the data partition!
Hello.When i install a ROM like Touchwizmod 3.0 on my HD2 on Clockworkmod recovery (i select NAND with data on SD) and after i reboot from AROMA i get a bootloop.Why?
I have:
NAND : FAT32 ;2,00 GB ;Primary
EXT4 : Ext4 ;5,82GB ;Primary
What i make wrong?
What size /system partition did you flash? Make sure it's big enough for the ROM you chose. If it is big enough but the ROM still doesn't work, try increasing it to account for any bad blocks.
Nigeldg said:
What size /system partition did you flash? Make sure it's big enough for the ROM you chose. If it is big enough but the ROM still doesn't work, try increasing it to account for any bad blocks.
Click to expand...
Click to collapse
Im not sure what /system partition i use,but i know:
For nand i use 2,00GB partition,i use MAGLDR 1.13 and i have a 8GB Kingsdon.
What partition do you use for install NexusHD2 4.2.2?
I use NAND with data on ext
You need to partition your nand (internal phone memory) not the sdcard for system partition. Get the hd2 toolkit to do this. Ext4 (on sdcard) is for your data and fat32 (on sdcard) is for photos music etc..
Sent from my NexusHD2 using xda premium
jurgen99 said:
Im not sure what /system partition i use,but i know:
For nand i use 2,00GB partition,i use MAGLDR 1.13 and i have a 8GB Kingsdon.
What partition do you use for install NexusHD2 4.2.2?
I use NAND with data on ext
Click to expand...
Click to collapse
Your Hd2 in Magldr ,(5) usb flasher
On your Pc you ave to flash a recovery with the good size for the system partition (in the config(.cfg) file)
running the Daf.exe in the folder of the recovery as an administrator...
As the two above posters stated, it's the size of the part of the NAND allocated to the system when you flash CWM in USB Flasher mode in MAGLDR. Either use the NAND toolkit like shanman suggested (probably the simpler method) or do what bhzmobile said and edit the flash.cfg in your CWM folder on your PC before flashing it. As for the partition for your specific ROM, it will say it in the OP of the ROM you're trying to flash.
bzhmobile said:
Your Hd2 in Magldr ,(5) usb flasher
On your Pc you ave to flash a recovery with the good size for the system partition (in the config(.cfg) file)
running the Daf.exe in the folder of the recovery as an administrator...
Click to expand...
Click to collapse
Nigeldg said:
As the two above posters stated, it's the size of the part of the NAND allocated to the system when you flash CWM in USB Flasher mode in MAGLDR. Either use the NAND toolkit like shanman suggested (probably the simpler method) or do what bhzmobile said and edit the flash.cfg in your CWM folder on your PC before flashing it. As for the partition for your specific ROM, it will say it in the OP of the ROM you're trying to flash.
Click to expand...
Click to collapse
QUOTE=bzhmobile = I used this procediment for installing recovery,i downloaded the 250MB Package .zip,flashing with Daf.exe in Administrator Mode,i reboot AD RECOVERY,wipe data,cache and dalvik,installing Touchwizmod 3.0,used NAND with data on ext,rebooted and it's stucked on the Android logo.
I do the same procediment with Miui V5,but it's stucked
I'don't have problems with PACman rom full installed on NAND (i have a htc hd2 european),i'ts fluid and stable
QUOTE=Nigeldg = If i make a simpler mode,i do reinstall MAGLDR and install the 250MB Clockworkmod recovery,i not have problems?
And if i make a simpler mode,i do recreate the EXT4 partition?
Flash a 285mb partition since that's what NexusHD2 requires
Sent from my Nexus 4 using xda app-developers app
+1 for the size of your recovery. 250 is to small.
Flash a recovery size 380 for system and it 'll be good
Q&A for [30 OCT 2012][DEV] NativeSD Rom Boot Script for HD2
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [30 OCT 2012][DEV] NativeSD Rom Boot Script for HD2. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Unexpected end of archive
File: adbfixed_ramdisk_NativeSD_AOKP.zip
Archive seems to be corrupted.
rebgershon said:
Thanks for your speedy reply.
I have some further questions though:
1. which 'recovery' do you mean and where will I find Titanium backup and tytung tool?
2. I have downloaded the paragon software to copy the sd card contents which I will try to do now. However, what are the 'normal' methods used to resize as I mentioned in my previous post that the ext4 partition seems fixed when using the mini tool partition software?
TIA,
Geoff.
---------- Post added at 10:05 AM ---------- Previous post was at 09:59 AM ----------
Robbie,
I have put the sd card into the slot on my computer (which is a year old HP laptop) and also tried in a USB port but the Paragon software is not recognising the card at all, with only the c drive being shown. However, I am able to see the contents of the fat32 partition of the SD card through explorer as normal. Am I doing something wrong??
Click to expand...
Click to collapse
Which recovery did you use to install the rom? does it have facility to backup ext partitions? I know macs18max edited SDrecovery can do this from the first post here http://forum.xda-developers.com/hd2-android/nand-dev/nov-17-2015-kernel-3-0-101-t3251438 others can too.
titanium backup can be found in play store, free and paid versions. haven't used it myself for a while and only used free one. people on this forum swear by it though.
tytung's NativeSD backup might have to be searched for, I'm afraid.
Don't know why your ext partition is not showing up. What rom(s) are you using?
magldr or clk?
Sounds like you will have to use a backup method from the phone as opposed to pc, to store the contents on your FAT partition, then move/copy them to pc.
does this make sense?
Robbie P said:
Which recovery did you use to install the rom? does it have facility to backup ext partitions? I know macs18max edited SDrecovery can do this from the first post here http://forum.xda-developers.com/hd2-android/nand-dev/nov-17-2015-kernel-3-0-101-t3251438 others can too.
titanium backup can be found in play store, free and paid versions. haven't used it myself for a while and only used free one. people on this forum swear by it though.
tytung's NativeSD backup might have to be searched for, I'm afraid.
Don't know why your ext partition is not showing up. What rom(s) are you using?
magldr or clk?
Sounds like you will have to use a backup method from the phone as opposed to pc, to store the contents on your FAT partition, then move/copy them to pc.
does this make sense?
Click to expand...
Click to collapse
Thanks again Robbie. Tis whole thing gets wierder as follows:
I'm using Nexus HD2 Jellybean-CM10_V1.3a as the rom. In the recovery directory of the SD card there's the Jellybean rom as mentioned, clrcad (dated 8/7/2010, haret, initrd.zip, startup text document & zImage (dated 5/9/2012).
There's also a NativeSD directory with the same files as the recovery directory.
Running Haret from the recovery directory takes me to 4EXT Recovery v2.2.7 RC5.
It also shows: E: can't find misc
E: failed to find "cache" partition to mount at "/cache".
In the info section it lists the sd-ext partition ext4 1012MiB free 135.5mb, sdcard fat32 14175 MiB free 8.0gb.
Attempt to backup fails as can't find cache partition, boot, recovery logs on E:
I loaded the Paragon software on my newer laptop but no ext partition was found. I then loaded the Paragon software on an older laptop and hey presto the partition was there. I tried to back this up on the pc but had repeated problems with files not being read. Then suddenly the ext partition disappeared on the pc but phone booted into Android-phew!.
I tried on the 1st pc and suddenly it recognised the ext partition. I tried backing up the partition but again had read problems. The fat32 partition backed up without 1 error.
So where do I go now? I don't want to loose the data in the ext partition but don't seem to be able to backup. Any suggestions welcome.
Geoff.
rebgershon said:
Thanks again Robbie. Tis whole thing gets wierder as follows:
I'm using Nexus HD2 Jellybean-CM10_V1.3a as the rom. In the recovery directory of the SD card there's the Jellybean rom as mentioned, clrcad (dated 8/7/2010, haret, initrd.zip, startup text document & zImage (dated 5/9/2012).
There's also a NativeSD directory with the same files as the recovery directory.
Running Haret from the recovery directory takes me to 4EXT Recovery v2.2.7 RC5.
It also shows: E: can't find misc
E: failed to find "cache" partition to mount at "/cache".
In the info section it lists the sd-ext partition ext4 1012MiB free 135.5mb, sdcard fat32 14175 MiB free 8.0gb.
Attempt to backup fails as can't find cache partition, boot, recovery logs on E:
All the above is normal for NativeSD, your sdrecovery doesn't allow for backing up the ext partition
I loaded the Paragon software on my newer laptop but no ext partition was found. I then loaded the Paragon software on an older laptop and hey presto the partition was there. I tried to back this up on the pc but had repeated problems with files not being read. Then suddenly the ext partition disappeared on the pc but phone booted into Android-phew!.
I tried on the 1st pc and suddenly it recognised the ext partition. I tried backing up the partition but again had read problems. The fat32 partition backed up without 1 error.
So where do I go now? I don't want to loose the data in the ext partition but don't seem to be able to backup. Any suggestions welcome.
Geoff.
Click to expand...
Click to collapse
perhaps paragon wasn't the best choice for backing up. Try the recovery linked-to above, put it on your sdcard and run haret from its folder (you might have to change the folder name so that it is not the same as your other recovery folder). then select backup, then scroll down to sdext, tick it and swipe, it should copy to your FAT, and it seems you have plenty of space there. I haven't tried this backup method, which is why I said use 2 methods to backup. the more the merrier.
There are free sms, phone and app backup applications such as superbackup in playstore.
There was also a way to copy the whole sdcard as an image, partitions included, I will have a look for it.
Robbie P said:
perhaps paragon wasn't the best choice for backing up. Try the recovery linked-to above, put it on your sdcard and run haret from its folder (you might have to change the folder name so that it is not the same as your other recovery folder). then select backup, then scroll down to sdext, tick it and swipe, it should copy to your FAT, and it seems you have plenty of space there. I haven't tried this backup method, which is why I said use 2 methods to backup. the more the merrier.
There are free sms, phone and app backup applications such as superbackup in playstore.
There was also a way to copy the whole sdcard as an image, partitions included, I will have a look for it.
Click to expand...
Click to collapse
Robbie thanks again.
I downloaded the recovery folder from your link but there's only 2 files in it namely initrd.gz and zImage, there's no haret. I have copied the haret, clrcad & startup text files files from the old recovery directory but it just hangs on running haret.
Geoff.
Sorry Geoff, I am not giving you very good advice. That recovery has a 3.0 kernel in it, and won't boot from haret. Am working ATM, will reply later.
Robbie P said:
Sorry Geoff, I am not giving you very good advice. That recovery has a 3.0 kernel in it, and won't boot from haret. Am working ATM, will reply later.
Click to expand...
Click to collapse
Hi again Robbie,
I have good news and bad!!
I managed to eventually get the Paragon software to recognise the ext4 partition on my new laptop. What's odd is that the ext4 partition is listed under the name of the c drive. I then unmount and remount the ext4 with a new drive letter and I can then read/write. So having managed to mount, I was able to copy off all the files from the FAT32 & ext4 partitions to my hard disk. That's the end of the good bit.
As its 3 years since I did the last Jellybean install, I'd forgotten what to do and kept seeing posts about magldr and custom radio roms. I tried to boot into magldr on the phone while doing the sd card backups but it wouldn't go into it. I had assumed I must have installed it when I did the original SD rom install and I then wrongly assumed I needed to reinstall the HSPL4 and custom radio roms to get it on again. The former was ok but the latter caused the phone to hang on reboot at the HTC logo. At this point I went to the bootloader screen but after having the 4 colour screen I then got the white screen with blue writing for updating the rom from an sd card (there must have been an unzipped rom on the card). I mistakenly hit the install rom button and this erased all the phone's data before I'd had chance to use SD Backup, a programme I hadn't bothered using since long before I converted to Android.
I then looked back in my old bookmarks and came across a facebook guide to the Native SD installation which didn't mention magldr at all and it was at this point that I realised I'd not previously loaded it on the phone, although I did eventually manage to get it on after downgrading the HSPL to 2.08 and successfully flashing the custom radio only to be permanently booting into magldr-so I again reflashed the stock rom to get rid of it! What a waste of time!!
Having backed up the sd card partitions, I erased the partitions and made a new ext4 of 3gb and copied back the files to both partitions. I tried to boot the haret in the native SD folder but the phone hung at the HTC logo and then rebooted itself back into windows. I tried installing the jelly bean rom as an update using ext4 recovery but no joy. I tried wiping the ext4 partition and reformatting with EXT4 recovery then installing the rom as a new install which then booted into Android ok after which I overwrote the ext4 files with the previously saved ones. Now I get a boot into the CyanogenMod screen but no further even after waiting 30 mins. I also tried using NAtiveSD onetouch recovery to try and make a backcup of the old system and then restore over the new install (but not the boot files) but again I just get the hung CyanogenMod screen.
So do you have any idea of how I might get a successful boot with my old data? Perhaps I'm missing something else in the overwrite/restore process but I can't see what.
Any further help would be grateful-perhaps you have forum contact who might be able to help as well.
TIA,
Geoff.:crying: