Ok so i've flashed my phone a good few times and i'm also an experienced linux user. So i have a fair idea about what i'm doing. The last 2 months i've been running the latest Xrom, and yesterday it started doing some funky stuff. My phone would randomly not wake up when pressing the menu button, had to open it up etc to wake it. Then it randomly shut off. So i started it up and it went through the android screen and then constantly on a black screen.
So i wiped it and went back to 1.5 using the RC7 image. That worked ok, but i wanted to flash it again. I must have tried flashing/wiping/restoring to 1.5 about 6 times. I'm trying to run cyanogen's mod, tried all different versions too, even the one i had tried before switching to Xrom. Everytime it just sticks at the G1 screen, no light on. I can leave it for 30+ mins before getting annoyed and going back to pre-cupcake. But it's unusable like that.
I'm thinking it might be a partition issue. What is the recommended filesystem to use? I have a 2GB card and i can't remember what partitons i have atm. I think it's half ext4 & half fat32 or something like that. Can i set the whole 2GB as fat32, then flash the rom? Is that recommended? If so, how do i do it without using the partition script?
Thanks in advance
I dont remember if ext 4 is supported in CyanogenMod, I reccomend ext 3. No its not required to have a ext partition, itll just store apps in the phones internal memory.
It was actually ext2 i was using, couldn't remember. I tried to fix the filesystem in the console and it gave me an error. So, stupidly i went into gparted and deleted the partitions, thinking i could create them again. But i'm having a little trouble now, i'm stuck in the console and i know if i reboot, i won't be able to get back into recovery mode...
How can i create a single fat32 partition in the console?
I can't do it in Linux or in Windows
Nvm, got it back into pre-cupcake...let's see if it'll flash properly with a fresh fat32 partition
How about using Paragon Partition Hardisk Manager 9, it should work, I used it...
Amon Ra's recovery image 1.5.1 allows you to format and upgrade partitions from the console.
Cyanogenmod supports ext 4
Ext 2 sux if you're trying to run apps2sd
ext 4, 10 mb hack, and zipaligned = Super FAST rom!
Ok, i tried installing cyanogen. It got to the android screen, then just went black. It was illuminated, but black. This is the same strange behaviour i was having with Xrom. It seems like my phone can't use anything but official roms now. I dunno what has happened to it. I did drop it for the first time a few days ago, but surely then the vanilla roms wouldn't work. I'm back on 1.6 now, and it seems to be working ok...I'll give cyanogen another try later i think.
Hmmm, so i bought a new sd card and now i'm running cyanogen flawlessely. Thanks for the help
Related
A little over a month ago I flashed the damagecontrol ROM and haven't looked back. Aside from having 2.1 early, I was also able to access su features, blah blah blah. My question is: I am still losing internal memory even after enabling A2SD, partitioning my SD card into three sections (ext3, swap, and probably fat32 or something). I noticed a gain of about 40mb right away but each time I download a program my internal memory shrinks. Any ideas? I'm not a pro at this but really wanting to learn.
-------------------------------------
Sent via the XDA Tapatalk App
joshuaharp said:
A little over a month ago I flashed the damagecontrol ROM and haven't looked back. Aside from having 2.1 early, I was also able to access su features, blah blah blah. My question is: I am still losing internal memory even after enabling A2SD, partitioning my SD card into three sections (ext3, swap, and probably fat32 or something). I noticed a gain of about 40mb right away but each time I download a program my internal memory shrinks. Any ideas? I'm not a pro at this but really wanting to learn.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Even with A2SD there are still files that get written to internal storage for cacheing. You will see your memory go down.
Ah. I didn't realize that. Are there other ways to free up the internal memory? I'm down to around 25mb...
-------------------------------------
Sent via the XDA Tapatalk App
If you have a nice class of sd card you could move dalvik to sd. That freed up a good spot of memory for me.
the same thing is going on with my phone i only see an added 40mb onto the internal storage when i put on a2sd,when i hear about other kids that get around 90mb when using a2sd.
willowmp said:
If you have a nice class of sd card you could move dalvik to sd. That freed up a good spot of memory for me.
Click to expand...
Click to collapse
I just threw a 4GB Class 6 in and partitioned it. Before that I was running the stock 2GB (Class 2 I think). I've been considering a few options but not sure what the process should be and how to proceed:
- dalvik cache to sd
- jit compiling (alhtough, I've almost completely ruled this out due to rumors of instability issues)
- swapping sd (I'm not sure if this will have ill-effects on my system or not)
I would feel at more liberty to experiment if I knew what to do if my phone ran into an error that crippled it (i.e., stuck in boot loop). I'm really fresh to this, so it's a bit intimidating at first.
joshuaharp said:
I would feel at more liberty to experiment if I knew what to do if my phone ran into an error that crippled it (i.e., stuck in boot loop). I'm really fresh to this, so it's a bit intimidating at first.
Click to expand...
Click to collapse
Before you read one more post on this forum go install RA-Amon's recovery and make a nandroid backup. Then copy the backup folder onto your computer.
That is if you haven't already done so. This will save you a lot of trouble should something go wrong, unless you really do something spectacular.
Edit: Just checked my internal memory. 149mb free and I have a handfull of apps installed atm.
On another note I flashed the godmode overclocked kernel, the 768 one or whatever, and installed setcpu, and my god my phone is fast. Current settings are max 767, min: 518. Yes my min is fairly high but at 518 it is butter smooth and I have multiple batteries so...
willowmp said:
Before you read one more post on this forum go install RA-Amon's recovery and make a nandroid backup. Then copy the backup folder onto your computer.
That is if you haven't already done so. This will save you a lot of trouble should something go wrong, unless you really do something spectacular.
Edit: Just checked my internal memory. 149mb free and I have a handfull of apps installed atm.
On another note I flashed the godmode overclocked kernel, the 768 one or whatever, and installed setcpu, and my god my phone is fast. Current settings are max 767, min: 518. Yes my min is fairly high but at 518 it is butter smooth and I have multiple batteries so...
Click to expand...
Click to collapse
This kernel (.29 kernel, right?) is one I've been recently considering. I've made a nandroid backup through ROM Manager (is this as good as RA-Amon's recovery?). I'm not sure what to do with this should something go wrong...unless I can boot up and have access to the ROM Manager app – I'll cross that bridge when I come to it. Some questions:
concerning flashing a recovery
- what exactly does this do? (as I understand it, it writes a recovery file to my sd card, so that i can boot up in recovery mode should something cause my os to fail...is this correct?)
concerning the godmode overclocked kernel
- how long have you had this flashed on your phone?
- can I flash over my current ROM (damagecontrol 2.08.1)?
- will I lose info and have to wipe everything not on my SD card?
- I've partitioned my sd card for A2SD, will this cause problems?
- how long is your battery life on average?
Thanks dude.
willowmp said:
Before you read one more post on this forum go install RA-Amon's recovery and make a nandroid backup. Then copy the backup folder onto your computer.
That is if you haven't already done so. This will save you a lot of trouble should something go wrong, unless you really do something spectacular.
Edit: Just checked my internal memory. 149mb free and I have a handfull of apps installed atm.
On another note I flashed the godmode overclocked kernel, the 768 one or whatever, and installed setcpu, and my god my phone is fast. Current settings are max 767, min: 518. Yes my min is fairly high but at 518 it is butter smooth and I have multiple batteries so...
Click to expand...
Click to collapse
What did you set your swap and ext on when you partitioned your sd
xxxk15 said:
What did you set your swap and ext on when you partitioned your sd
Click to expand...
Click to collapse
ext: 1024 (or whatever the first 1gig choice is, I believe it is something like this)
swap: 30 (I believe, or whatever it automatically pops up as when formatting)
Through Dconfig I have apps2sd, dalvik to sd, and sd swapping with the default 30mb enabled.
Dalvik heap is set to 16mb and lowmemkiller set to less. JIT not enabled.
Current version DamageControl, the 768 overclocked kernel and toast's newest radio.
joshuaharp said:
This kernel (.29 kernel, right?) is one I've been recently considering. I've made a nandroid backup through ROM Manager (is this as good as RA-Amon's recovery?). I'm not sure what to do with this should something go wrong...unless I can boot up and have access to the ROM Manager app – I'll cross that bridge when I come to it. Some questions:
concerning flashing a recovery
- what exactly does this do? (as I understand it, it writes a recovery file to my sd card, so that i can boot up in recovery mode should something cause my os to fail...is this correct?)
concerning the godmode overclocked kernel
- how long have you had this flashed on your phone?
- can I flash over my current ROM (damagecontrol 2.08.1)?
- will I lose info and have to wipe everything not on my SD card?
- I've partitioned my sd card for A2SD, will this cause problems?
- how long is your battery life on average?
Thanks dude.
Click to expand...
Click to collapse
RA-Amon's custom recovery is a must and is vastly more important than a back-up app. RA-Amon's recovery is an actual recovery image, thus as long as your phone boots up to the HTC logo you should be able to access RA-Amon's recovery and thus restore the backup before the phone is even accessing the rom.
Flashing a recovery image is like flashing a rom, but instead of a rom you are flashing a recovery image. Your phone has a stock recovery image on it right now, I don't know the key combo but hold a certain pattern of keys down while turning the phone on and you will enter it. It looks I think like a triangle with an ! in the middle or something. This is sorta useless for us though because I don't think you can really do much with it.
When you flash a recovery img (RA-Amon's) that stock recovery image is just replaced with Amon's. After you do flash the recovery holding the HOME and power button to turn the phone on and continuing to hold it will cause you to enter Amon's recovery, which is a green menu. From this menu you can amke backups/restore them, wipe the data on the phone (factory reset), flash .zips (roms, bootscreens, themes, kernels) and other things.
What you are referring to the writing backup to sd card is called nandroid. Nandroid is an option in the recovery, so yes if you do flash the wrong rom or your phone won't boot up (boot loop or whatever) as long as you can access recovery which is one of the first things loaded when you hit the power button (unless you really do something spectacular like flashing a gsm hero's radio you almost always will be able to get into recovery. don't even touch radios right now, flash the wrong one and your phone won't even turn on/charge. aka your motherboard will be totaled) so you will almost always be able to nandroid recovery your os if something does go wrong.
In short before you do anything flash the recovery.
Now on to your other questions. I have been running the overclocked kernel for one day, but it appears stable and seems to be working good for me. When you flash a kernel you always flash it over a rom, because if you do it the other way the rom will replace the kernel. So yes once you have damagecontrol or another rom that supports that kernel you can simply go into recovery and use flash .zip to flash the kernel over the rom. As always make sure to make a nandroid before doing so.
DamageControl supports apps2sd, and you enable it to use a2sd using the Dconfig app that is included in the rom. It is generally a good idea to partition your sd card whenever you switch between roms unless they say it is fine. You should go ahead and copy over a backup of your sd card to your computer, however you need not format or wipe your sd card when flashing roms. Honestly I don't think you need to partition your sd card again, unless after you flash the rom the os won't boot up all the way or loops/crashes. If it does then partition the sd card and try rebooting the phone and it should fix it.
Also you can format and partition your sd card in recovery under Other.
As for my battery life I have been switching b/w roms and such and I just started using the OC kernel, but with the DamageControl rom back when I only had that flashed my batt life was good.
However I do have 3 batteries and an external battery charger for my phone. Check out the accessories section of this forum, 2 batteries and the charger for 11 bucks from Hong Kong on ebay.
Hope I helped.
So, through the damagecontrol dconfig app I banned "sense", rebooted and now my phone is stuck in a bootloop. Do I restore from previous nandroid backup or do I need to flash my phone? Suck.
joshuaharp said:
So, through the damagecontrol dconfig app I banned "sense", rebooted and now my phone is stuck in a bootloop. Do I restore from previous nandroid backup or do I need to flash my phone? Suck.
Click to expand...
Click to collapse
Just want to say first off: "I am an idiot". Nandroid backup from 5 days ago, booted up by holding *home and *power, then selecting to restore. Very easy. I can actually breathe now. Back in business. Sorry to waste your guy's time. We can keep the thread going minus my drama...
joshuaharp said:
Just want to say first off: "I am an idiot". Nandroid backup from 5 days ago, booted up by holding *home and *power, then selecting to restore. Very easy. I can actually breathe now. Back in business. Sorry to waste your guy's time. We can keep the thread going minus my drama...
Click to expand...
Click to collapse
It's all good.
See why I emphasized flashing your recovery before messing with anything? xD
xxxk15 said:
What did you set your swap and ext on when you partitioned your sd
Click to expand...
Click to collapse
I set the swap to 32mb and ext3 to 512mb I believe...does this sound right?
willowmp said:
RA-Amon's custom recovery is a must and is vastly more important than a back-up app. RA-Amon's recovery is an actual recovery image, thus as long as your phone boots up to the HTC logo you should be able to access RA-Amon's recovery and thus restore the backup before the phone is even accessing the rom.
Flashing a recovery image is like flashing a rom, but instead of a rom you are flashing a recovery image. Your phone has a stock recovery image on it right now, I don't know the key combo but hold a certain pattern of keys down while turning the phone on and you will enter it. It looks I think like a triangle with an ! in the middle or something. This is sorta useless for us though because I don't think you can really do much with it.
When you flash a recovery img (RA-Amon's) that stock recovery image is just replaced with Amon's. After you do flash the recovery holding the HOME and power button to turn the phone on and continuing to hold it will cause you to enter Amon's recovery, which is a green menu. From this menu you can amke backups/restore them, wipe the data on the phone (factory reset), flash .zips (roms, bootscreens, themes, kernels) and other things.
What you are referring to the writing backup to sd card is called nandroid. Nandroid is an option in the recovery, so yes if you do flash the wrong rom or your phone won't boot up (boot loop or whatever) as long as you can access recovery which is one of the first things loaded when you hit the power button (unless you really do something spectacular like flashing a gsm hero's radio you almost always will be able to get into recovery. don't even touch radios right now, flash the wrong one and your phone won't even turn on/charge. aka your motherboard will be totaled) so you will almost always be able to nandroid recovery your os if something does go wrong.
In short before you do anything flash the recovery.
Now on to your other questions. I have been running the overclocked kernel for one day, but it appears stable and seems to be working good for me. When you flash a kernel you always flash it over a rom, because if you do it the other way the rom will replace the kernel. So yes once you have damagecontrol or another rom that supports that kernel you can simply go into recovery and use flash .zip to flash the kernel over the rom. As always make sure to make a nandroid before doing so.
DamageControl supports apps2sd, and you enable it to use a2sd using the Dconfig app that is included in the rom. It is generally a good idea to partition your sd card whenever you switch between roms unless they say it is fine. You should go ahead and copy over a backup of your sd card to your computer, however you need not format or wipe your sd card when flashing roms. Honestly I don't think you need to partition your sd card again, unless after you flash the rom the os won't boot up all the way or loops/crashes. If it does then partition the sd card and try rebooting the phone and it should fix it.
Also you can format and partition your sd card in recovery under Other.
As for my battery life I have been switching b/w roms and such and I just started using the OC kernel, but with the DamageControl rom back when I only had that flashed my batt life was good.
However I do have 3 batteries and an external battery charger for my phone. Check out the accessories section of this forum, 2 batteries and the charger for 11 bucks from Hong Kong on ebay.
Hope I helped.
Click to expand...
Click to collapse
Dude...helped IMMENSELY! I'm still digesting it.
That's good to know about flashing radios. I was going to flash the most recent one for 2.1 roms on CDMA heros, but I think I'll wait to hear more about it.
I think I feel comfortable flashing the .29 kernel over my current ROM. I gotta be honest though, the DConfig thing kind of weirds me out now, after trying to use it. I'm not sure which button is going to cause my phone to freak out.
If you have a nice class of sd card you could move dalvik to sd. That freed up a good spot of memory for me.
Click to expand...
Click to collapse
I'm considering doing this but have read that this causes issues with nandroid backup. Have you experienced this?
-------------------------------------
Sent via the XDA Tapatalk App
Where to begin...
So I based my install off of this YouTube Video: youtube.com/watch?v=88qRbLLEAPQ and after I got done following everything to the T, I was not able to format /data. I feel this may be my problem. After doing all the steps minus that one I tried to install CM7 and it would boot the second time around in CM7 (Something I read was common). IT would get the the skateboard screen and then it would just stay there with the arrow continuously looping around and around. I let if sit for quite some time before I had to power it off.
I called up my buddy who told me I would more then likely have to install it manually with the Android Developer tools (Or whatever he called it). I did not have those tools so I kept poking around online. I found that sometimes the SD card caused problems so I bought a new 4Gb class 4 card. This was not the issue.
I poked around alittle more in CWR and I accidentally formatted /boot. The unit froze up so I restarted it. It booted into CWR just fine and after trying to wipe the /system, /data (Still not working) and /cache and rebooting, it has now just turned to a black screen that I can't even boot from a card.
Now before I just cash in on my protection plan, What can I do to get this running again? I hate having a paper weight sitting on my desk..
Thank you so much!
tl;dr, Tried to install CM7, can't format /data, tried new card and re installing, accidentally formatted /boot and now it won't boot at all.
Honestly, I can't watch Youtube at work so I am clueless what instructions you are following.
1. What version of your NC? 1.2? 1.1? 1.0?
2. What version of CwMR?
3. You tried to install CM7 in the eMMC or uSD?
I don't know which Nc it is... I just got it 2 weeks ago today.
I do believe that the cwr was 3.0.0.3 or something like that... it was supposedly the newest.
and it was the latest stable version of CM7.
My problem now is that my computer has totally crashed and it won't start in safe mode even. I am fairly sure it has something to do with having the files on my computer.. I just have to get that part figured out, then I can get the rest of it working..
Latest CW is 3.2.0.1 if I recall.
I know when I leave my imaged microsd card in my adapter on the laptop that the laptop won't boot. You don't have the card in an adapter on the system do you?
Also, I assume you are trying to install CM7 to internal memory?
You have to use CWR v. 3.2.0.1. Earlier versions will not wipe/clear everything. Do that and you should be ok....
If it has been around 2 weeks ago, then it most likely be v1.2 which you need CwMR v3.2.0.1, which reportedly fixes the format /data issue.
Give it a try again.
Ok, got the Nook to boot back to the Nook software. Won't get past the loading screen, but atleast it is booting..
I got my computer working finally after booting in Safe mode and deleting all the zip files and images from the computer. So now I am back to a clean slate.
Where do I get CWR 3.2.0.1? And then where do I get the CM7 latest release? I feel like I should be listening to you guys rather then listening to the YouTube video.. It was nice to see things happen on there, But it did not work for me.
Thank you guys SOOO much for having this forum and the "How to fix the black screen" tutorial! I would be lost without it!
Yellow XDA!
I've got this thing when trying to get a new Sense 3.0 rom. I've been looking for a good one and found that one. (Please point me to your favorite sense 3.0 ROM)
When installing, I've had some trouble with partitioning SDCard, installing a ROM (status 0 error, aborting installation)
I'm using 2.08 HSPL, MagLDR 1.13, CWM v4 & Radio 2.15.50.XX
I'm able to install a ROM (tried http://forum.xda-developers.com/showthread.php?t=733649)
But when I reboot after installing (in CWM), when it should load, it doesn't go past the Android loading screen
So It boots, MagLDR shows up, no errors, gogogo thingy, then it freezes (splash screen I guess)
I've been looking for some solutions but haven't found anything that works.
Tried other radios, CWM versions, ROMs...
I've got no idea what to do
Any help is appreciated.
Syntax1993
Tmous or regular? If regular, do you have the 1gb ext partition set? Also, that rom will take a while to set up since it requires a lot of stuff to be unpacked onto the SD card.
I've not used that rom but I know some of the big ones take tens of minutes for first boot
samsamuel said:
Tmous or regular? If regular, do you have the 1gb ext partition set? Also, that rom will take a while to set up since it requires a lot of stuff to be unpacked onto the SD card.
I've not used that rom but I know some of the big ones take tens of minutes for first boot
Click to expand...
Click to collapse
I used the EU version. I did indeed (try to) partition the SDCard but when clicking advanced, partition, 1024, 0, It told me to wait, and wait, and wait, and wait, and when after like half an hour, I pulled out the SDCard, it's 1GB smaller in Windows so it should be done.
Installing works fine.
I'll try starting the ROM again & look if it works after a couple of hours.
Doesn't work. It ran all night, didn't get past the Android screen.
I ran into a similar problem. I downloaded a file from the forum called Wipe_it_CWR.zip before installing the new rom and that resolved my issue
You mean just installing it via CWM before the ROM right? Nothing else special?
Trying it now. So far, it seems like it won't work.
EDIT: Nope sorry. It's really weird.
Hi,
I've got an HTC HD2 here, with Android installed on it. (NAND, I believe.)
It was bought second-hand with Android pre-installed.
Because it was still linked to the google account of the previous owner, I had to restore the whole phone to factory settings. Since that didn't work, I've just decided to install another Rom.
After some messing around, I managed to install Clockworkrecovery. (It wouldn't boot for some mysterious reason) And then I installed an Android Rom. (Energy™ -.¸¸.·´¯ Sense 3.5 Runnymede)
After some time, the phone rebooted and got stuck on the Android boot screen.
I tried to install another Rom, but now they all get stuck on the boot screen. (I have tried another Runnymede rom, and RCMix3D)
Does anybody know how I can fix this?
I wiped my Dalvik Cache, I wiped my Cache partition, I wiped my data/factory reset. I am using the MAGLDR as boot thingie, but that's working perfectly.
I have formatted my SD-card with G-Parted, on my Ubuntu-PC. (First partition FAT32-750MB, Second partition EXT3 - 1GB and a Linux-Swap of 100MB)
For some strange reason, ClockworkRecovery cannot format my SD-card. (Well, it says it can, but as soon as I stick the card in my PC, the PC tells me it's corrupted. (Windows XP on my Father's PC tells me it has to be formatted, on my Ubuntu it doesn't show up as mountable)
Thank you in advance
P.S. I don't mind losing data, there's no personal data on it. Any solution (which doesn't involve buying a new phone) will do.
Quickest solution I would try is format the entire card to fat32, and see if your pc detects it. Once it does, put the rom on it, put in in the phone, boot into clockwork format data/cache/dalvik install the rom then reboot and see if it goes past the bootscreen (keep in mind first boot takes a while, but if it takes more than 2-3 minutes theres still a problem.
Do you know what partition layout of clockwork you installed by any chance? Some roms require specific layouts in order to work correctly.
Thank you for your reply.
Unfortanetly, that didn't work.
I have installed Clockworkmod like they say on jayceooi dot com. (I cannot past links yet, but here's the step-by-step guide:
Step by Step Guide
Power on your phone and don’t let go power button.
DFT MAGLDR Bootloader will be loaded.
Use volume down button to go down to 5. USB Flasher.
Then press call button to load USB Flasher mode.
Connect USB cable from PC to phone.
You should see Wait USB…USB.
At PC, right click on DAF.exe and select ‘Run as administrator’.
Click ‘Yes’ if User Access Control prompt up.
Follow onscreen instructions to install.
Phone will be rebooted after installation finished.
DFT MAGLDR Bootloader will be loaded then.
Disconnect USB cable from phone.
Use volume down button to go down to 8. AD Recovery.
Then press call button.
ClockworkMod Recovery will be loaded then.
That’s all.)
I used the 150MB-Partition one.
Didnt work how? Does the pc detect the sd card now after you formatted?
The directions you posted are right, so maybe try a different partition layout. The roms that you said you tried use different layouts than what you have and that may be a problem. Test a CM7 rom and see if it will boot, they tend to have less problems and are overall more stable than sense roms.
I recommend Typhoons rom: http://forum.xda-developers.com/showthread.php?t=933951
Try to install it and see if it boots. It uses the same partiton layout that you have now. If it boots, thats indication that you may need a different layout if you want to run a sense rom.
Well, I could re-format my sd-card and re-partition it, but it (Android) still got stock at the boot screen.
Using the Typhoon rom, I got the same problem. The Rom appears to be succesfully installed, but it didn't really boot.
I now tried to installed Windows Phone 7, this works fine. (I don't want to install WP7 however, I want to install android)
I tried the following too: (Post by a3r0n1)
http://forum.xda-developers.com/showpost.php?p=18868874&postcount=14
/
At the "Using "HD2 Toolkit" select "Magldr repartition" Make sure that you are using the recommended partition size for your rom!" part, I got an error that the file was too big when I tried to choose a partition of 300MB, I honestly have no idea what the partition size should be. (I want a sense-rom, I don't have a clear preference which)
I did install the Clockworkmod with 400MB with succes now.
However, still got the same problem. Android seems to get in a loop somewhere in the boot screen
EDIT:
I noticed that the Micro-SD card always corrupts after CWM installs the Android-Rom.
I think that may be the core of the issue here.
Does anybody know how I can install Android without CWM?
Are u repartitioning the phone? That might be the problem. Hope this helps
Sent from my Nexus One using XDA App
I manager to install an old Desire-based rom with Android 2.2 through a daf installation.
This one works fine but I still would like to install a Rom with Android 2.3 via a more regular way.
One problem I'm facing with this Rom is a very limited amount of internal storage. (about 55MB)
And I've got a big battery leak, the battery drains very fast. Much faster than my Desire HD. (The HTC HD2 we're talking about isn't mine, It's my mother's)
So does anyone know how I can install a regular Rom (preferably runnymede based) without CWM? Or does anyone know how I can resolve my problem?
@akaruna: I do not know how to partition the phone, I believe I didn't do that. Should I? I did partition the SD card. (CWM made unreadable cards for some obscure reasons, so I partitioned the SD card using gparted on Ubuntu)
Thanks in Advanced
Sjoerd
If you have limited internal storage then the main problem is the partition table is not correct. This is also why the roms you install are stuck on the bootscreen. When you install roms that require a bigger partition table than what you already have on your phone they will be stuck in a bootloop.
Go and download the HD2 NAND TOOLKIT: http://forum.xda-developers.com/showthread.php?t=1090783
Check out the video to familiarize yourself with the features, then repartition your MAGLDR with the correct partition table that the rom you want requires. Go into clockwork and install rom from zip.
Yes the tool kit is the best.
Yea the toolkit works wonders. Even though I still do it the original way ;p I do everything faster that way for some reason
Sent from my Nexus One using XDA App
Oh and yes, always read the thread from that certain Tom so that way u know exactly what partition table/size to use. Usually linked also.
Sent from my Nexus One??? (HD2) using XDA App
I tried it again with this rom: "[18Dec 2011] [CMR] Sensation xl Sense3.5/2.3.5 v2.7 BETA OC & marc1706 0.1.3 kernel" (I believe I'm still not allowed to post links)
I used the NAND toolkit this time for the System Partition Size.
The only thing I actually did was clicking 350MB as System Partition Size and then I clicked repartition. And then I followed the on-screen instructions, which involved clicking next and after some installing some drivers everything went fine. (With the HD2 in USB-flash mode of course, it also said the job was completed succesfully)
I wasn't able to choose a bigger size for some reason, it told me the 400MB was too big.
Still the same problem, the phone gets stuck at the Android boot-screen.
Does anybody have an idea? Thanks in advance (Again, I'm not scared of losing any data, if anyone has any solution at all: I'm more than happy to hear it)
I tried another DAF rom and got the following error:
"Error Description: Size is too big.
Info: .\RSPL\RSPL.cpp (800)"
So I tried repartitioning the System Partition Size (MAGLDR) to 400Mb.
However, It gave me the exact same error.
Does anyone know has any idea? (For example, how I can change the partitions in another way)
(Partitioning it at 360MB works fine)
Not sure what it is but the DAF file I use let me partition to 445...... those sense time are heavy and if the partition isn't right it will bootloop or not
Sent from my HTC HD2 using XDA App
" sense time " and do you have the sdcard partition at 1gb?
Sent from my HTC HD2 using XDA App
............ sense rom.........
Sent from my HTC HD2 using XDA App
Can someone please help me? I have a Samsung focus that was recently acting up.. Games wouldn't open etc.. so I decided to reset it.. After I reset it.. Its now stuck at the Samsung logo after resetting.. I am guessing that I need to reflash it.. If so, I need to make sure my battery isn't dead. Does the Phone charge while showing the Samsung boot logo?? Help Please..
I dont have a focus but with a Google search looks bout the same as I wud do on my epic ..found this if it helps http://forums.androidcentral.com/dr...ks/130642-help-stuck-samsung-boot-screen.html
Alright, heres what I did.1. Rebooted in*CWM2. Wiped data/factory reset3. Wiped cache partition4. Wiped dalvik cacheAt this point I couldn't reflash because I forgot I couldn't access my SD card, I kept getting the "e:can't mount /sdcard" message whenver I went to install zip from sd card.5. Took off the back and pooped out the SD card and put it right back in. Seemed to work6. Flashed 2.07. Flashed kejar's sd card fix8. Rebooted through*CWMPhone starts up, do all the set up stuff, but still can't access my sd card or anything. Booted back into*CWM*just to see and was getting the "e:can't mount /sdcard" error again and couldnt reflash anything, so back to step 1.Here's a list of other things I have done since the original crap out a few days ago that might be affecting this.*1. Yesterday I tried reflashing 2.0 and it seemed to be boot looping again. So I just wiped data and cache partition and flashed 1.9.1 that I had on my SD card. Was having the same problems so that was the only time I tried it. Not sure if built in kernels might affect anything or whatever.2. After it seemed like I had a stable 2.0 again last night. I flashed blue*CWM*because I've had yellow this whole time. I also flashed EP1 radios through ODIN because I was planning on going to GG 2.1 (I was following your video dave! its awesome btw*).I'm not sure at what point I lost access to my SD card. Ive read a lot this morning about voodoo lag fix affecting things. Could this be a problem with what I've done?
Sent from my SPH-D710 using Tapatalk 2
jpeclf said:
I dont have a focus but with a Google search looks bout the same as I wud do on my epic ..found this if it helps http://forums.androidcentral.com/dr...ks/130642-help-stuck-samsung-boot-screen.html
Alright, heres what I did.1. Rebooted in*CWM2. Wiped data/factory reset3. Wiped cache partition4. Wiped dalvik cacheAt this point I couldn't reflash because I forgot I couldn't access my SD card, I kept getting the "e:can't mount /sdcard" message whenver I went to install zip from sd card.5. Took off the back and pooped out the SD card and put it right back in. Seemed to work6. Flashed 2.07. Flashed kejar's sd card fix8. Rebooted through*CWMPhone starts up, do all the set up stuff, but still can't access my sd card or anything. Booted back into*CWM*just to see and was getting the "e:can't mount /sdcard" error again and couldnt reflash anything, so back to step 1.Here's a list of other things I have done since the original crap out a few days ago that might be affecting this.*1. Yesterday I tried reflashing 2.0 and it seemed to be boot looping again. So I just wiped data and cache partition and flashed 1.9.1 that I had on my SD card. Was having the same problems so that was the only time I tried it. Not sure if built in kernels might affect anything or whatever.2. After it seemed like I had a stable 2.0 again last night. I flashed blue*CWM*because I've had yellow this whole time. I also flashed EP1 radios through ODIN because I was planning on going to GG 2.1 (I was following your video dave! its awesome btw*).I'm not sure at what point I lost access to my SD card. Ive read a lot this morning about voodoo lag fix affecting things. Could this be a problem with what I've done?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your help but seeing as your phone is an Android phone, I don't think the same process applies. But thanks for the effort, I have this baby up and running now.. I just had to reflash the ROM.. Thanks again :good:
FocusHelp said:
Can someone please help me? I have a Samsung focus that was recently acting up.. Games wouldn't open etc.. so I decided to reset it.. After I reset it.. Its now stuck at the Samsung logo after resetting.. I am guessing that I need to reflash it.. If so, I need to make sure my battery isn't dead. Does the Phone charge while showing the Samsung boot logo?? Help Please..
Click to expand...
Click to collapse
If you have decided to reflash then use ROM provided by 'voluptuary' (3.10a). And moreover, to flash, it would not matter if your battery is getting charged. Just plug the device to your PC using the USB cable and flash the device.
Be VERY sure you flash the correct ROM for your phone. If you have a version 1.3, then ONLY flash 1.3 ROMs to it. If you have a version 1.4, then ONLY flash 1.4 ROMs to it. You can find the version number under the battery on the sticker. If you flash the wrong version of ROM to it, you will end up with a brick.
When having problems like this, I would recommend flashing the Stock ROM to it first to set everything back to normal. Then, if that works fine, go to custom ROMs if desired. Stock flashing will replace everything back to new settings, including spl, radio, etc... Some of the custom ROMs are truly worth flashing, FASTER, stable, nice features.
Unokashi01 said:
If you have decided to reflash then use ROM provided by 'voluptuary' (3.10a). And moreover, to flash, it would not matter if your battery is getting charged. Just plug the device to your PC using the USB cable and flash the device.
Click to expand...
Click to collapse
I know I had 3.05a and reflashed 3.10a Clean Rom.. It works great now... I remember I use to have problems with the 3g but not after reflashing it works great