Related
Please bare with me, as there's a lot to explain. I am in dire need for your help.
Starting off, my specs are as follows:
HTC Desire CDMA from U.S. Cellular
Rooted via Unrevoked (with unrevoked forever)
Current Recovery: ClockworkMod 2.5.0.9
Current ROM: CyanogenMod 6.1.0
Current SD: 8GB
The phone is barely over a week old. I rooted it last week, flashed Cyanogen, and customized everything. Well one thing I wished I had done before was partition a part of my SD to allow for more internal phone space. Even with
Cyanogen's FroYo (2.2.1) capability to move apps to the SD, I kept running a thin line on low memory. This is because, as most of you know, not the entire app is moved. I was faced with the decision of removing apps that I frequently used, or look for other storage solutions.
I found out that there was a way to make the phone think it has extra memory by partitioning a part of your MicroSD card to an Ext3. I researched how to do this with the tools I already had available (this being ROM Manager & ClockworkMod). I first tried ClockworkMod's recovery, which give me the option to partition the SD. I selected 512MB for the size (it's more than enough for me) and a swap size of 0. It completes, and I reboot the phone. I checked the internal storage space, and it's still low (< 15MB). Upon more research, I found that it may have only been an Ext2, and not Ext3. Upon plugging my phone back into the USB/Computer, I noticed the overall size for my MicroSD went from 7.5x GB to 6.9x GB. If the partition didn't work like I wanted, I wanted my space back.
So for hours I scour the forums with nothing helpful in return. I tried Partition Magic to try and merge the partition back to my original card, but it couldn't see it. It only saw a SD card that was 6.9x GB. So further research showed me that ClockworkMod was pretty bad at partitioning the SD card to Ext3, and everyone suggested AmonRa. I found a version of AmonRa that was designed for the HTC Desire. I placed the .img file on the root of my SD card and opened up ROM Manager. The option to "Flash Alternate Recovery" was greyed out, despite the fact that the image was on my SD Card (which was mounted; USB Storage for the PC was turned OFF). So further reading said I needed the premium version of Rom manager. I bought it, installed it, and re-fired it up. The option is still greyed out.
Frustrated, I look for alternate methods. I found one that recommended Terminal and the flash_image script.
I tried doing this with the AmonRa recovery image (which I renamed to recovery.img on my SD card). I rebooted into recovery, but instead of ClockworkMod or AmonRa appearing, I just got the HTC logo with the white
background where it would ultimately freeze. I performed a hard reset and tried again. Same thing. I reboot, went into ROM Manager and tried flashing ClockworkMod 2.5.0.9. It said it installed, so I reboot into recovery. Same HTC Logo freeze.
Freaking out, I tried other solutions, involving one where I placed a script on my SDcard. From there, I would go into Terminal and type the following:
su
sh /sdcard/FR-flashRec-v03.txt
And after the 2nd or 3rd time trying this, I reboot my phone, and instead of going into recovery, it dumps me back into Fastboot. Every time I tried selecting Recovery from bootloader, it would take me to Fastboot. I'm freaking out about now. So I fired up Unrevoked, the tool I used to originally root my phone. After the 2nd attempt, it successfully flashed ClockworkMod back to my phone.
Relieved but still unsolved, I continue to look for a reason why I'm not able to flash a different recovery image. Then I found a thread which dates back to June 2010 and applied to the CyanogenMod 5.0.x Eclair build. There was a disclaimer that read:
DO NOT USE ROM MANAGER TO FLASH YOUR RECOVERY.
DO NOT USE flash_image SCRIPT TO FLASH YOUR RECOVERY IN THE LIVE SYSTEM.
So I figured the problem was with my current ROM. Sure, that referred to CyM 5.0.x, and I'm running 6.1, but there was no documentation saying that the issue had been fixed, and there weren't any other threads regarding my issue.
Not wanting to take a risk losing my current recovery, I restored a backup from my stock ROM I received from U.S. Cellular. I installed ROM Manager and tried to flash the recovery image via the "Flash Alternate Recovery". The option was once again greyed out. I bought premium again and still, the option is still greyed out.
Running out of ideas, I restored my CyanogenMod state I made before I did any changes. And this is where I am.
I'm running out of internal phone space rapidly.
[*]I don't know how to restore the partition I made to get my SD storage space back (in fact, since I made that partition, it's been slower).
[*]I don't know how I can flash AmonRa, or if it's even possible with CyanogenMod.
[*]I don't know how to use ADB shell.
I found a site that has a collection of AmonRa images, and for the Desire, they have the following: recovery-RA-desire-v2.0.0-AW.img, recovery-RA-desire-v2.0.0-CM.img, and finally recovery-RA-desire-v2.0.0.img. I don't know which one I need to install for my HTC Desire CDMA.
If you've made it through this entire thread. Thank you. I really need some answers, and I don't know where else to look or to even ask. Can you please help me?
First of all making a ext partition won't magically provide more space, there is more behind it. See the second post in this thread under 'Still low storage for apps'.
And the partition made with rom manager should be fine however if you want something else use Gparted (can run of a linux live cd so no need to install anything)
For the restoring of the partition also use Gparted.
Not 100% sure but i believe that with unrevoked you can flash a alternative recovery image even if you are already rooted, but if you use Gparted there is no real reason for doing so.
For adb there are enough tutorials.
Hmm, many of these AmonRa releases are designed for HTC Desire GSM. Will these releases also work for CDMA devices?
Also, GParted will not work under Windows 7, and I don't use linux. All these other partitioning programs cannot detect the missing 1GB from my 8GB MicroSD. I have no idea how to restore it.
Here's a lovely and vague one for you all to try wrap your heads around...
Okay, so I started having trouble with my SD card about a year ago after my mate added a partition so I could flash A2SD ROMs (I believe - I was stuck and asked him to sort it and from what I can gather, that's what he did). It was fine for a while, then suddenly it became nigh on unresponsive to Android: I couldn't take photos, install apps to SD, basically any data transfer between the device and the SD storage was not happening. I think this was after I tried to delete some things to make room for videos and **** but I was stuck on about 300MB of the ~2GB available (this may have been my first attempt to delete after the partition, I'm not sure).
That was the birth of a problem I am still yet to fix. My dad needed a new phone and I wasn't using my Desire anymore. He's 53, and so the Sense UI was less than intuitive to him which lead to me offering to make it a bit simpler for him (flash a stock ROM and use a more information-centric launcher). The device badly needed updating anyways as I hadn't done so since my mate partitioned my SD card and some bugs had began to develop on the ROM I was using. So, I downloaded the latest CM build and set about reformatting the storage to see if I could solve some of the issues. In attempting to do so I think I performed a data, cache and dalvik cache wipe which removed the ROM I was currently using. The partitioning was successful, so I transferred the new ROM and attempted to flash - BOOM! Error message. Tried again, same thing. Now I have a phone that'll only boot into a recovery that's 5 full versions old (CM Recovery v2.5.0.7) without a way to flash an update img. I've tried on many different occasions to try and sort the problem and spent relentless hours trying to research a solution to the numerous different error messages this produces. Every error I can remember was a problem with read/write on the SD card, so I purchased a new one to no avail.
The phone CAN'T be bricked, surely. I still have access to things like USB mounting (which works absolutely fine), and most importantly, access to the recovery. Please don't tell me she won't live on, this is my baby and she's going down fighting! :'(
TL;DR SD card read/write issues. I only have access to recovery. I can mount the SD card via USB in CM Recovery, but every time I try to flash a new ROM I get numerous different read/write errors.
Go here:
http://forum.xda-developers.com/showthread.php?t=1408936
There you can download 4ext recovery that can be flashed via fastboot or using some flasher.
When you flash it repartition your sd card, choose only one sd-ext partition (not bigger than 1,5gb), no swap and fat32 for thevrest of your card.
After repartitioning try to flash some rom and see how it will work.
Hi
I have a Desire GSM rooted and S-ON RA-Desire v2.0.1 stock HBOOT Ext 4 1Gb latest radio ends in 23
Have been running on a custom rom for over a year now and want to install the latest copy of the same rom. The md5sum is identical for the zip file to the source.
Booted into recovery wiped all data, cache and then devlik-cache.
I have turned off signature verification and then selected my rom zip on SD card.
Installed the rom rather there were no errors and it took about 20 seconds (seemed too fast).
Next in recovery I did a reboot.
Now the screen went white with green HTC logo in centre for about 1 minute then after this a black screen with android written logo for about another 2 minutes.
Eventually phone boots into rom but it is not the new rom it is the exact same old rom.
I can see from applications listed that I am still super user so not lost root.
In settings software information everything is listed identical to what I had before.
The contents of the zip files are different so it is not the same rom being flashed.
Choosen rom is
[ROM][Cool Sense][5 April]Cool Droid v3|2.3.4|FASTEST|Data++/Stock (currently have Icecream sense v2 installed which is an earlier version of the same rom)
I did not install the alignment zip as I had already setup to use an earlier rom version and ext4.
What have I done wrong in trying to install my choosen rom please?
I feel like I must have missed something.
Not sure which recovery you have, with 4ext I boot to recover, format everything except sd then install zip and it seems to work, obviously everything then needs reinstalling from the backup you'll have made
Sent from my HTC Desire using Tapatalk 2
Hi
Unrevoked 3, as I have one of those odd PVT4 Desire phones 4000 erase size using RA Recovery. (something like that sorry if technical references are not super clear).
I use Titatium backup so reinstalling wont take long just need the ROM to install.
This is a fast glitch free rom using sense so I do not want to try a different rom as it gave me a year without trouble. Only doing this to start again with the space issue needing a refresh.
I have cleared delivk cache again and flashed my original v2 rom and that worked showing expected progress reports.
So I thought would try flashing the new v3 rom, and see if I got any joy this time.
Still no joy, it looks like it starts as two lines appear then it says complete with no obvious error.
So I reflashed the original v2 rom again and will go with that as I need a phone more then I need to play.
Odd.
Maybe the new v3 rom needs sOFF but as far as I could read it does not.
Even installing the previous rom things are still not right.
The apps that normally come with the rom are not installed such as Demon controller, No adds and Busy Box. I can see that they are in the zip file they are just not been added.
I can manually install Busy Box from the market so I know it is not a permission thing.
Titatium Backup is seeing my Ext4 partion (it calls it an ap2sd but it is showing) so I don't think there is a problem with my SD car arrangement.
I stupidly do not have a nandroid of the previous install I can restore.
So any ideas please why the previously working and installed rom is not reinstalling fully with all it's built in apps?
Anything I could try please?
Looks like I have identified the problem, my SD card is flakey and Gparted reports sick partion table that wont fix so the Ext4 partion was not been seen which is probably why the install failed and the apps were not installing.
New Sd card will be ordered and then start again.
Thankfully I dod have an uptodate SD card backup.
Phone is working just as a phone for the next few days.
These micro SD cards do not last long at this rate I get 1 year from them as this will be my third ordered.
Go to S-OFF, is better and mandatory for a lot of rom.
New card and more fiddle work with Gparted and now waiting for setup to complete as old v2 rom is installed. It works fast and is smooth plus has HTCsense so I can keep my sync capability so will be staying with it so I can live without S-OFF
Gparted when I followd the recommendations I kept getting a corrupt card on my phone so this is what worked for me.
Format card on phone
Then put card into usb card reader and place in PC
Reboot PC onto Gparted CD
Select SD card and then I resized the fat32 partion already there and then added a new EXT4 partion.
This worked for me.
Dump gparted, format the card through 4ext recovery
Sent from my HTC Desire using Tapatalk 2
So am trying to install SlimBean on my play, but I am having trouble getting it installed but I don't know if its that or the kernel (Turbo Kernel v3.1) which is causing the trouble. So here is a step by step of what I did;
1. As per Turbo Kernal instructions, flashed FTF in thread for 'vendor-unlocked partition layout'.
2. All fine, booted into stock rom.
3. Flashed Kernel.
4. All fine, boots kernel to welcome screen. (Note: I get the welcome screen all the time, and I don't have to press a key to get to the boot menu, this doesn't seem right to me?)
5. As per Turbo Kernel instructions I did the following - 'Enter Multiboot Menu (Vol-Down key) and go to Internal > Recovery, then format system, data and cache before doing anything else. Very important'
6. Still boots to 'Welcome' screen.
7. Entered the first slot and loaded TWRP recovery.
8. Mounted SD Card and copied SlimBean .zip to the SD Card.
9. Selected 'Install' in TWRP, selected ROM and installed fine.
10. Choose reboot.
11. Phone still boots to 'Welcome' screen.
I have tried the instructions in the Turbo Kernel thread to get rid of the boot loop, (open recovery and choose 'reboot' from there) but still can't get it to load the ROM. Not even sure if it has installed properly. I have also tried switching recovery to CWM, and installing the ROM that way, but I can't get it to mount the SD Card. I also tried the 'Repair' function in Turbo Kernel but that has no effect either.
Does anyone have any ideas where I went wrong, or how I can fix this? Thanks in advance.
Question [Q] Can't seem to install SlimBean correctly, help please?
Right now first of all I am no expert on Turbo Kernel I have used it for a few times on my play but my main phone is arc so I am using a different version of twrp.
Now looking at your instructions one thing I did different than you was never to mount or unmount SD card while in Turbo Kernel,I think CosmiDan even say's not to do this as system .img's are stored on sd card (maybe wrong)
What I used to do was take my SD card out and copy the rom to flash to my SD card with a card adapter or when phone was on via usb never while in recovery!
I would try to flash kernel again delete the system img that Turbo creates on your SD card and do as you have been doing but put Slimbean on SD card first.
Hope that helps :good:
try Clockwork mod recovery and try to install the rom then just give it TIME like 5 min or so till the slimbean logo pops up
crazymonkey05 said:
try Clockwork mod recovery and try to install the rom then just give it TIME like 5 min or so till the slimbean logo pops up
Click to expand...
Click to collapse
Thanks for the reply but perhaps I'm not being clear in the OP. The phone always enters the Turbo Kernel Multiboot menu, regardless of if i press anything or not. I can't install via CWM as when i try to i get an error about not being able to mount the sd card to find the ROM file.
@tallman: Thanks for the tips. Unfortunately i don't have a compatible adapter for the card. I will try flashing the kernel again, any thoughts on why i always get the Multiboot/Welcome Screen?
EDIT: I have sorted it. Turns out I needed to partition the SD card in the recovery menu after wiping. Once I did that, USB Mounting and SD Card mounting worked just fine. Installed the ROM via CWM and it booted automatically. Thanks for the replies anyway chaps, now to go an play.
JimmyDeemo said:
Thanks for the reply but perhaps I'm not being clear in the OP. The phone always enters the Turbo Kernel Multiboot menu, regardless of if i press anything or not. I can't install via CWM as when i try to i get an error about not being able to mount the sd card to find the ROM file.
@tallman: Thanks for the tips. Unfortunately i don't have a compatible adapter for the card. I will try flashing the kernel again, any thoughts on why i always get the Multiboot/Welcome Screen?
Click to expand...
Click to collapse
On the Mulitiboot/Welcome screen issue only thing I can comment about that is what CosmicDan mentions in is post below
Q) My device keeps going into the Boot Menu, even though I never pressed the key to enter!
A) This is a bootloader thing and is rare, to fix it just enter Recovery (for any slot) and select reboot from there.
But I think you tried that anyway Like I said I looked at your post and tried to think what I did different to what you did to get it working and as I said it was only the fact That I copied rom's to my SD card when not in recovery to be honest I transfer all my rom's that way.
Don't forget if you install again to delete the system images on your SD card that Twrp creates so that you have got fresh images and start by installing Slimbean in 1st slot
Have you tried installing Slimbean with another JB kernel then when you have it installed swap back and install Turbo Kernel
Looks like you missed my 'edit'.
I'm all sorted now. Had to partition the SD card in TWRP recovery. Slim Bean is a little disorientating, I can't seem to add my google account, but I think I need to install the add ons for it.
Thanks again.
Prior to today, I had not installed TWRP or rooted my T310 device. I believed I followed the instructions to root my device correctly (found here). Going through TWRP, I rebooted the system to install the Superuser package. I then rebooted the system, loaded up TWRP, and began to do a system wipe (followed instructions found here) to prep the flash of the rom and gapps.
I selected the following partitions to wipe: Dalvik cache, system, data and data. The instructions werent clear, so I checked both 'data' boxes.
After the wipe executed, I went to flash the rom and GAPPS I loaded to the internal sd card aaaaand... there were no .zip files. Crap. I went to reboot TWRP and it alerted me that my device does not appear to be rooted. Double crap. Not panicking, I went to mount and tried to see if I could mount the internet SD card to my device. Nothing. Windows now shows a 'Samsung_Android' device but it is listed under 'unspecified'. Reloading the drivers have done no good.
I'm guessing SuperUSer was never installed correctly *or* I did something during the reset.
I, of course, did not perform a backup prior to all of these. I have rooted my devices multiple times and it was always a breeze so why backup now? Weell...
So now I'm sitting here with a nonSU device, with no OS, no backup, and I'm unable to connect my device to Windows. Outside of loading a rom from an external SD Card, what options do I have?
jaredmac11 said:
Prior to today, I had not installed TWRP or rooted my T310 device. I believed I followed the instructions to root my device correctly (found here). Going through TWRP, I rebooted the system to install the Superuser package. I then rebooted the system, loaded up TWRP, and began to do a system wipe (followed instructions found here) to prep the flash of the rom and gapps.
I selected the following partitions to wipe: Dalvik cache, system, data and data. The instructions werent clear, so I checked both 'data' boxes.
After the wipe executed, I went to flash the rom and GAPPS I loaded to the internal sd card aaaaand... there were no .zip files. Crap. I went to reboot TWRP and it alerted me that my device does not appear to be rooted. Double crap. Not panicking, I went to mount and tried to see if I could mount the internet SD card to my device. Nothing. Windows now shows a 'Samsung_Android' device but it is listed under 'unspecified'. Reloading the drivers have done no good.
I'm guessing SuperUSer was never installed correctly *or* I did something during the reset.
I, of course, did not perform a backup prior to all of these. I have rooted my devices multiple times and it was always a breeze so why backup now? Weell...
So now I'm sitting here with a nonSU device, with no OS, no backup, and I'm unable to connect my device to Windows. Outside of loading a rom from an external SD Card, what options do I have?
Click to expand...
Click to collapse
You can either download the whole firmware and use Odin to flash or get adb setup and push a rom zip to the internal card using adb.
Sent from my SM-N900V using Tapatalk
hi,
you will need a microsd card 32gb and properly formatted that comes with a card reader for your pc.
download your rom and get it onto the card, insert the card into your device
boot to twrp, and flash,
now, if twrp still spits the no os message at you, which is an issue with twrp,
you next need to go to your wipe options, select advanced and do a full data format/wipe,
NOT SYSTEM, DATA. meaning /data and /data/media. when that completes you should be sorted
but expect your initial boot of the new rom to take a little longer.
never wipe system with twrp. the rom's updater-script will manage that function.
m
Thank you both. I lost my SD cards and card reader in a move so while that orders, I will attempt to utilize ADB. I'm pretty green but I'm certain there are guides out there..
moonbutt74 said:
hi,
you will need a microsd card 32gb and properly formatted that comes with a card reader for your pc.
download your rom and get it onto the card, insert the card into your device
boot to twrp, and flash,
now, if twrp still spits the no os message at you, which is an issue with twrp,
you next need to go to your wipe options, select advanced and do a full data format/wipe,
NOT SYSTEM, DATA. meaning /data and /data/media. when that completes you should be sorted
but expect your initial boot of the new rom to take a little longer.
never wipe system with twrp. the rom's updater-script will manage that function.
m
Click to expand...
Click to collapse
I'm having a hell of a time getting the rom to install from the SD card. I believe I am not formatting the card correctly. Is there a guide on how to do so? I have a primary partition in SD in FAT32 and the other partition as EXT4 but no luck. Any help is appreciated.
jaredmac11 said:
I'm having a hell of a time getting the rom to install from the SD card. I believe I am not formatting the card correctly. Is there a guide on how to do so? I have a primary partition in SD in FAT32 and the other partition as EXT4 but no luck. Any help is appreciated.
Click to expand...
Click to collapse
hi,
your external sdcard should be formatted as single partition fat32 unaligned,
if you running windows, use bootice, look it up
On linux , gparted may give you issues, if so, on debian at least there is another better utility
though the name escapes me at the moment, disk manager i think.
m
moonbutt74 said:
hi,
your external sdcard should be formatted as single partition fat32 unaligned,
if you running windows, use bootice, look it up
On linux , gparted may give you issues, if so, on debian at least there is another better utility
though the name escapes me at the moment, disk manager i think.
m
Click to expand...
Click to collapse
Well I was able to find a good stock firmware download, flashed that via Odin and I'm back to square 1. I am going to forego the external SD route. Perhaps too technical for me or some other hang up is abound but I am leaving that method alone for now. Thank you for your help : )