Ive always been running CM roms since I got the phone nearly two years ago, but recently have been reading too many good things about ICS roms. My phone has been laggy as of late, and honestly after nearly 2 years, I wanna see and try something new. I've been reading some stuff about updating 4EXT or something like that. Can someone link me or explain in great details how i do this? What is it? And if I do that, will i still be able to run my old CM rom if i decide the ICS roms arent for me? I dont want to be unable to roll back.
Whats the best ICS roms out there right now?
Many thanks!
___________________
SOLVED AFTER A STEP BY STEP INSTALLATION WITH KB!! MANY THANKS
Sent from my T-Mobile G2 using xda app-developers app
mapheG2 said:
Ive always been running CM roms since I got the phone nearly two years ago, but recently have been reading too many good things about ICS roms. My phone has been laggy as of late, and honestly after nearly 2 years, I wanna see and try something new. I've been reading some stuff about updating 4EXT or something like that. Can someone link me or explain in great details how i do this? What is it? And if I do that, will i still be able to run my old CM rom if i decide the ICS roms arent for me? I dont want to be unable to roll back.
Whats the best ICS roms out there right now?
Many thanks!
Sent from my T-Mobile G2 using xda app-developers app
Click to expand...
Click to collapse
Depends on your definition of best, personally I like EliteMod ICS (in my signature) but you may want to try out Andromadus Mimicry 1.3.0, it's pretty nice out of the box and has a graphical installer (aroma).
Just be aware that due to the fact that the Desire-Z/G2 does not have an official ICS release, that some things such as hardware drivers have their limits.
1) Camera drivers are not fully available, so the camera won't function as well as it would have on a GB rom.
2) No Wireless-N, also due to drivers, but Wifi-B/G are available.
and a number of other smaller issues which are mentioned varying on the roms, but the two above are the most common complaints, something to keep in mind before you start updating the thread about lack of it.
4EXT Recovery is just another recovery, like ClockworkMod is another recovery.
I personally prefer 4EXT Touch Recovery ( http://www.4ext.net/ has the app to install it ), but both ClockworkMod (what you may have now) and 4EXT can create backups, and restore your backups to the phone (just make sure you do a factory-reset/wipe cache, when you're flashing a brand new rom on, and when you wish to restore a backup.)
So i can flash ics roms with clock work mod and not use 4ext?
Sent from my T-Mobile G2 using xda app-developers app
mapheG2 said:
So i can flash ics roms with clock work mod and not use 4ext?
Sent from my T-Mobile G2 using xda app-developers app
Click to expand...
Click to collapse
You can, they're both recoveries and will both apply a rom zip. I just find 4EXT to have quite a bit more features that pertain to ICS (i.e.: the ability to convert some of your partitions from the older ext3 filesystem to the ext4 filesystem which is better, but not all roms support it, most ICS roms do though), as well as the ability to do tar-based backups (compresses, smaller backup size), and the paid version of the app lets you configure a number of settings in 4EXT (much like the paid version of Rom Manager).
Just don't flash roms via the app, always do that from the actual recovery, or you risk causing problems.
Generally speaking: Reboot into recovery (you can do this from the power menu in CM7.2)
1) Perform a backup of your currently installed Rom to the SD card
2) (toggle USB storage and copy over the rom zip if you haven't already done so)
3) Perform a Factory Reset/Wipe and wipe cache
4) Goto Apply zip from SD Card and select the new ROM
5) Flash any additional zips you want on top, google apps, wifi calling, etc (note the thread for any specifics, for example Mimicry doesn't come with Google Apps so need to flash the ICS google apps if you want them, where as EliteMod includes a custom set of google apps already)
6) reboot and enjoy.
If you decide you don't like it, just repeat the above steps, just do a restore at #4 and reboot.
Both of the ones I mentioned (mimicry, elitemod) by no means require a swap partition or sd-ext partition, but you can partition the card via either clockworkmod or 4EXT, just skip the sd-ext2 option (since elitemod doesn't support a secondary one [and not much point either). And don't set a sd-ext size less than 1.5GB (no sense in making it smaller than your /data partition).
For both though, skipping an SD swap is advised, I only have SD swap on mine cuz no other rom I know of supports dataswap and I'd rather have my SD Card partitioned already to test out other roms than to re-do the SD Card each time (since you gota make sure to back up the content of the SD Card to the PC). 4EXT though will let you repartition the SD card without erasing the FAT32 partition, where as clockworkmod will always wipe the whole card before repartitioning (it's just easier to partition from scratch though).
Yeah the whole partition and swapping was the confusing part. But good to hear I don't have to do any of that. I did see the gapps zip included in the mimicry thread, but where can I find a wifi calling apk to install? Also +1 thanks to u for the detailed reply! Thanks!
Sent from my T-Mobile G2 using xda app-developers app
mapheG2 said:
Yeah the whole partition and swapping was the confusing part. But good to hear I don't have to do any of that. I did see the gapps zip included in the mimicry thread, but where can I find a wifi calling apk to install? Also +1 thanks to u for the detailed reply! Thanks!
Sent from my T-Mobile G2 using xda app-developers app
Click to expand...
Click to collapse
In Mimicry the Aroma installer will actually let you pick that option during the graphical install. It's one of those roms that presents you with a nice installation menu after you select the zip to be applied. Just bear in mind though you need the 26.13.04.19 radio in order to use the T-Mobile Wifi calling app (and course be on T-Mobile). EDIT If you're one of those people who end up getting no WIFI at all after flashing the Wifi calling app from the aroma installer and have the 26.13.04.19 radio, in the first post of the mimicry thread there's a mention of a Wifi-Fix app you can install that might be able to fix that.
For EliteMod ICS, you would apply it by downloading the zip in my signature (for the wifi calling) and flashing that after flashing the rom. But again, needs the 26.13.04.19 radio, as the app won't work with an old radio (26.03.*)
The thread on applying the radio is also linked from my signature , if you're on a T-Mobile G2, you can just grab the first 26.13.04.19 zip file, rename it PC10IMG.zip just like the instructions say there, put it on the SD Card, reboot into the boot loader and apply the radio. Also if you're planning on flashing either mimicry or Elitemod immediately after flashing the new radio, both roms already Clean your EFS partition for you when you install them in recovery, so you don't have to run the EFS wipe zip (something you normally need to flash in recovery after changing a radio).
KB suggested EliteMOD to me a few days ago,...... Gota say it is running vnice at the moment, highly recommend it. w/ SD EXT, no swap.
I downloaded the zip file from the Andromadus thread, and proceeded to flash the ROM. It says the flash was successful, however upon rebooting, I would see the HTC screen but it would never make it to the boot animation. I would just get a black screen. I tried flashing through ClockWorldMod v5. I cleared all data and caches, and then flashed the ROM.. still not working?
mapheG2 said:
I downloaded the zip file from the Andromadus thread, and proceeded to flash the ROM. It says the flash was successful, however upon rebooting, I would see the HTC screen but it would never make it to the boot animation. I would just get a black screen. I tried flashing through ClockWorldMod v5. I cleared all data and caches, and then flashed the ROM.. still not working?
Click to expand...
Click to collapse
What's the exact details of your phone, i.e.: hboot information and radio version.
I flashed the radio from your signature. Hboot information: 0.82.0000
blkjack said I needed to do a superwipe. If that is the case, how would I perform one?
mapheG2 said:
I flashed the radio from your signature. Hboot information: 0.82.0000
blkjack said I needed to do a superwipe. If that is the case, how would I perform one?
Click to expand...
Click to collapse
hboot in my signature is a 0.84.2000 which is a desire-z engineering hboot.
0.82.000 would be an S-ON hboot which you wouldn't be able to change much at all. (which would be odd if you managed to get the 26.13.04.19 radio flashed, while S-On since it wouldn't normally allow you to).
May want to reboot into the boot loader mode and verify all your hboot information.
kbeezie said:
hboot in my signature is a 0.84.2000 which is a desire-z engineering hboot.
0.82.000 would be an S-ON hboot which you wouldn't be able to change much at all. (which would be odd if you managed to get the 26.13.04.19 radio flashed, while S-On since it wouldn't normally allow you to).
May want to reboot into the boot loader mode and verify all your hboot information.
Click to expand...
Click to collapse
I flashed a radio in the past. And it clearly says I have S-OFF on the top. I had the (26.03.02.26) radio before. And it did successfully flash the radio linked from your signature. HBoot says 0.82.0000. Where to go now?
EDIT: I found this link (http://forum.xda-developers.com/showthread.php?t=1044992) but dunno if this is outdated or not. If not, which of the three files do I want?
mapheG2 said:
I flashed a radio in the past. And it clearly says I have S-OFF on the top. I had the (26.03.02.26) radio before. And it did successfully flash the radio linked from your signature. HBoot says 0.82.0000. Where to go now?
EDIT: I found this link (http://forum.xda-developers.com/showthread.php?t=1044992) but dunno if this is outdated or not. If not, which of the three files do I want?
Click to expand...
Click to collapse
I think, the -=SuperWipeG2+=-.zip should be the right one, but as I'm not sure, I did a quick Google search for you and found this:
EdKeys said:
I recently flashed the new 4EXT Mod of ClockworkMod Recovery. The 4EXT Recovery is based off of Koush's CWM Recovery but offers additional power options, one of which is the ability to show the file system format your partitions are formatted in. To my surprise my system was formatted in the Ext 4 format and my data and cache partitions were formatted in Ext 3. The new 4EXT Recovery offers the option to convert the format without deleting any of the data. Your ROM will stay intact after the conversion. I selected that option and changed my data and cache partitions to ext 4 to match my system, rebooted, and notice quite an improvement in speed and smoothness in my current CM7 Nightly. After looking into it further I found out that the SuperwipeG2 that many of us have been flashing is formatting our partitions in the Ext 3 format. The reason only my system was formatted in ext 4 is because I used ClockworkMod Recovery the last time I did a full wipe to first flash the Superwipe, and then I immediately formatted system again with ClockworkMod Recovery. If you've used SuperwipeG2 to do a wipe, more than likely your system, data, and cache partitions are now Ext 3. You might want to check with your ROM developer to see if your ROM will run on the Ext 4 format. If its a CM7 based ROM, it will.
You can find more information about the Ext 4 format here.
Tsubus has since modified SuperwipeG2 so that it now formats the partitions into ext 4 when you flash it. I've used it and it also includes the EFS wipe. You can find it here. As I said, if there is no reason to wipe right now the new 4EXT Recovery can convert your partitions if you choose if they are in currently Ext 3. At the very least you can see what format they're currently in with 4EXT. I highly recommend it. You can always flash back to CWM Recovery if and when you choose. The partitions will remain Ext 4 once you choose to convert.
UPDATE: Several users have reported that checking partition information with Terminal Emulator is not reliable.
Click to expand...
Click to collapse
This one should definitely be the right one.
Besides that, the problem might also be a bad download, as your symptom fits a known issue in blk_jack's thread:
blk_jack said:
...
Q) After flashing I'm stuck at the HTC logo screen!
A) This is likely the result of a bad download. Check your downloaded md5sum hash against the one listed next to the download link above....
Click to expand...
Click to collapse
I thought it was a bad download too, so I downloaded from one of the mirrors. Still the same problem.
mapheG2 said:
I thought it was a bad download too, so I downloaded from one of the mirrors. Still the same problem.
Click to expand...
Click to collapse
So you did not check the MD5 hash?
Im a bit of a noob and all of this wasnt around when I was flashing CM roms ages ago. How do I do that? Would that fix my issue??
Sent from my T-Mobile G2 using xda app-developers app
mapheG2 said:
Im a bit of a noob and all of this wasnt around when I was flashing CM roms ages ago. How do I do that? Would that fix my issue??
Sent from my T-Mobile G2 using xda app-developers app
Click to expand...
Click to collapse
An MD5 hash is something like a fingerprint of a file and it was definitely there when you first flashed CyanogenMod ROMs. The MD5 hash/sum is used to compare two files because it is possible that a downloaded file is slightly different from the original file due to mistakes that could have happened during transfer. So "checking the MD5 hash" means using a program to calculate that "fingerprint" of your downloaded file and comparing it with the "fingerprint" mentioned in blk_jack's thread. If the file you have downloaded is slightly different, its MD5 hash will be different from the MD5 hash that it should have and thus will be unusable and lead to a phone being stuck at HTC boot logo.
By the way, downloading a file from two different mirrors doesn't exclude the risk of getting a corrupt file.
I ran "md5 update.zip" from my Mac's desktop where the file is located. I was returned MD5 (update.zip) = 2a314e5f1361825c83a354aea38c6c4b .. which matches the md5sum of what was given. What next?
And I noticed you have the same H-Boot information that KB was talking about earlier, so I guess that can't be the problem either. Should I just try to Superwipe?
mapheG2 said:
Ok, so if it is a bad download, how do you remedy it? Because there are only so many options to download the ROM right. And what program are you referring to
Click to expand...
Click to collapse
There are actually lots of programs to calculate an MD5 hash. If you are on Linux it usally is as easy as typing md5sum <path to file> in a shell and reading the output. If you are on Windows, I'd recommend a Google search for "md5 generator" or something like this. Maybe even your recovery is able to calculate a file's MD5 hash - I'm using 4EXT and it definitely is, though I don't know if ClockwordMod is.
You can't remedy a bad download except trying to download it again, hoping that the file will be transferred right.
---------- Post added at 03:10 AM ---------- Previous post was at 03:08 AM ----------
mapheG2 said:
I ran "md5 update.zip" from my Mac's desktop where the file is located. I was returned MD5 (update.zip) = 2a314e5f1361825c83a354aea38c6c4b .. which matches the md5sum of what was given. What next?
And I noticed you have the same H-Boot information that KB was talking about earlier, so I guess that can't be the problem either. Should I just try to Superwipe?
Click to expand...
Click to collapse
Oh, sorry - didn't update the thread's page before submitting my reply.
Just try it, there should be nothing wrong with it.
Okay, I read that I should manually clear all the data and cache first and THEN run the superwipe, followed by installing the ROM right? And I will be downloaded from the thread I listed because I still have ext3 I guess and don't want to deal with a ext4 change right now.
Related
First, this is not for people whom cannot boot into the recovery at all. If your recovery does not load, or you can't get past the "white screen", there are other threads and options for you (e.g. installing the recovery though fastboot or Unrevoked).
PROBLEM: You boot into the CWM3 recovery fine. You can install compatible zips fine. However, when trying to backup, the recovery locks up at some point during the backup process.
Solutions I tried: RUU to stock. Downgrading to 2.5.0.5 and back up to 3.0.0.5. Deleting the clockworkmod folder on the sdcard. reinstalling ROM Manager. wiping cache/dalvik before backing up. None of these things worked.
Solution that seems to have worked: swap out sdcards, doing battery pulls on the phone inbetween and booting back into recovery, until you find one that allows the backup to complete. Once a backup completes fully, you will be able to swap back to your original sdcard and CWM3 should work as intended.
Specifically here's what I did:
Step 0: Flash 3.0.0.5 through ROM Manager.
Step 0.5: Turn progress bar off in ROM manager settings. I do not believe this is important. But for completeness, I did do this.
Step 1: Boot into recovery
Step 2: run backup with Transcend 8gb class 6: No luck. Battery pull, back to recovery
Step 3: Sandisk 1.0gb class unknown: no luck, battery pull, back to recovery
Step 4: Sandisk 512MB class unknown: worked twice in a row!
Step 5: Back to 8gb class 6: backup works now. Still in testing, but I believe this (obscure, weird) solution works.
I just used ROM Manager to download CM7 #40 nightly, backup and install apps through CWM3 and it worked.
Let me know if this works for you.
EDIT: Well, its not perfect, because I cannot restore a backup because I get the MD5 mismatch error. At least there's progress.
EDIT2: There are deeper problems here. Please post your success or lack thereof.
I can't believe that simply getting a backup to work once fixes the problem. I just can't see the recovery caring that it finally got one right, so now it works from now on. Recovery doesn't know what it has done in the past.
Perhaps repeatedly inserting and removing the cards, just that act itself, somehow was the fix.
not impressed with cwm 3 at all, seems real buggy. Sometimes have problems with it not doing a clean wipe/factory wipe. When I install a rom, it has some wierd stuff going on. Stuff like loading a live wallpaper from the previous roms setting. I never use it to download roms anymore. I might switch over to ra amon recovery. Or maybe back to the 2. series
it seems @koush and @dougpiston had a twatt on the twitter about cwm3 borking on the dinc. you can read the full conversation over there, but the gist is that we should enable "erase recovery" option w/in rommanager settings, reflash recovery.
I guess the recoveries are best flashed clean, rather than over one another. ???
okay. the above fix has been confirmed to work by myself and one other user on the htc incredible cm7 nightly thead, AdhvanIt.
So you want to load cwm through rom manager after you enable "erase (previous) recovery" in settings and it will be puppies and rainbows from now on.
Sent from my dinc using XDA App
Regarding the erase recovery, I had tried it for the backup will not finish problem and the weird fix above is the only thing that worked, but will give it another try for my broken restore issue.
Wow I find odd that I have no problems what so ever with cwm 3
Sent from my Incredible using XDA App
tdiman said:
Regarding the erase recovery, I had tried it for the backup will not finish problem and the weird fix above is the only thing that worked, but will give it another try for my broken restore issue.
Click to expand...
Click to collapse
After going back to 2.5.1.2 with erase recovery enabled, and then back to 3.0.0.5 I'm back to square 1 with not being able to complete a full backup.
I'm going with 2.5.0.5 until either I get a new SD card or someone else comes up with a fix.
tdiman said:
After going back to 2.5.1.2 with erase recovery enabled, and then back to 3.0.0.5 I'm back to square 1 with not being able to complete a full backup.
I'm going with 2.5.0.5 until either I get a new SD card or someone else comes up with a fix.
Click to expand...
Click to collapse
bummer. keep us posted. I too have 16gb sandisk. had many issues with cwm3 but they seem to have stablized with the erase recovery fix... fricking variables...
Sent from my dinc using XDA App
burnmatoaka said:
bummer. keep us posted. I too have 16gb sandisk. had many issues with cwm3 but they seem to have stablized with the erase recovery fix... fricking variables...
Click to expand...
Click to collapse
There were some changes pushed to CM7 a couple of nights ago for the recovery management, as well as the new ROM Manager update, that got me to try again. This time I deleted all partitions on the sdcard and repartitioned it with a large FAT32 partition and a small ext4 partition after it. I deleted my unused swap partition. ROM Manager recognizes both partitions as it is able to format them, so thats good.
I used ROM manager and installed Amon-Ra, then installed 3.0.0.5. Same hang-on-backup problem as before. Back to 2.5.0.5
erase recovery has been on the whole time...
you have a gremlin in there! I assume you've tried full-wipe and all. Maybe install cwm3 from HBOOT with a fresh download and/or md5verified copy of the recovery?
hit up @clockworkmod on the twitter. I know he can be kind of a flake, but he does invite feedback when he drops an update... it was how we found out about the erase recovery thing.
you aren't having any other weirdness with other ROMs, are you? worst, worst case, your hardware is "circling the drain." sucks, but you know plenty of used dincs be hitting the market when Thunderbolt finally drops. See what Koush says though--be persistent, and it wouldn't hurt if you happen to have a RM premium license
good luck, and again, keep us posted.
sent from my dinc using xda app,
burnmatoaka said:
you have a gremlin in there! I assume you've tried full-wipe and all. Maybe install cwm3 from HBOOT with a fresh download and/or md5verified copy of the recovery?
Click to expand...
Click to collapse
In the spirit of the title of this thread, I do believe I have an actual working fix over in the DEV forum. I recompiled CWM3 from source. Please see
http://forum.xda-developers.com/showthread.php?t=970032
and let me know your experiences over there, those of you that may or may not still be following this thread
@clockworkmod just dropped a new version of the inc recovery that supposed to fix "wiping /datadata issue from ROM Manager" Has this been our problem?
sent from my dinc using xda app,
I do not believe that was my original issue as the problems I had were independent of ROM manager, but 3007 fixes whatever my issue was as well as the wipe issue, which is great.
3007 also has the option to power off, thanks Koush!
Has anyone tried the 3.0.0.8? Just flashed and hoping it works better.
phaze one said:
Has anyone tried the 3.0.0.8? Just flashed and hoping it works better.
Click to expand...
Click to collapse
Fast scrolling is back.
zero issues with 3.0.0.8 for me. SLCD.
Sent from my ADR6300 using XDA Premium App
unable to get 3.0.0.7 to boot, though. no big thing, just looking for that mythical multi-touch fix. <sigh>
(and ZOMG my post#10 means i can talk in the grown-folkxx forums. sorry for the fluff)
Sent from my ADR6300 using XDA Premium App
Hello,
Today I attempted to root my HTC Desire. I used this site ( youtube.com/watch?v=kvg0i8in96M ) to do so.
I installed several programs that required SU access to check if the rooting was succesful.
I downloaded SystemAppRemover to remove some of the originally installed pieces of software. Unfortunately that didn’t work out too well: some of the buttons on the Phone aren’t responding anymore. So I figured, let’s turn off the Phone and turn it back on.
Then the next program revealed itself: the Phone wont boot, its trapped in the booting proces. I read elsewhere online that I should try to revert to the original firmware, but I have no idea how to do that.
Can anybody advice on this please? I used android 2.3 before.
Thanks in advance,
Veldscholte
Recovery working? Have you done any back up before you tried that app?
Sent from my HTC Desire using XDA Premium App
First backup is for saving a lot of troubles, like this one... Was it not worth to make it? You can flash any custom ROM or you can flash ruu-see bortak guide from stickies I'm on the phone limitation of resources ATM
Sent from my HTC Desire using XDA Premium App
I see that you're running Runnymede 5.0.3. Looking through the ROM's thread, i've found that it requires that you have an EXT partition on the SD card and that your phone is S-OFF, both of which, i believe, your phone lacks. That might be the reason why it's stuck at the bootscreen.
Runny 5.0.3 ROM's thread said:
REQUIREMENTS:
- CM7r2 or stock HBOOT (from Alpharev)
- Must be S-OFF! (see S-OFF guide).
- A 1GB ext4 partition (see partition guide for 4EXT Recovery).
- A recovery with touch drivers: I recommend 4EXT Recovery. Optional but recommended.
Click to expand...
Click to collapse
Before installing ANY ROM, please read its thread carefully. Some ROMs require various types and sizes of EXT partitions, others require different HBOOTS etc. If you don't follow the instructions properly, you will get bootloops.
From my understanding, you are now running the stock HBOOT (250 MB of /system space). If your phone is network-free (unbranded), you should download the latest 2.2 stock RUU from HTC, install it on your phone and that'll solve all of your problems (use Search). You can root/S-OFF afterwards and install any ROM that your heart desires (making sure you follow instructions, this time).
If you read his first post and watched video, he is s-off with stock hboot as he used revolutionary to get root... i think he is missing only ext4 partition and touch recovery
First off. ALways do a Nandroid backup from within recovery. This would have given you the option to restore your original rom,"with S-Off".
Head over to http://forum.xda-developers.com/showthread.php?t=1200261
download and install from recovery,"Wipe data/factory reset & dalvik cache first"
please read Bortaks Guide before messing to much wth your phone.
Go to http://gparted.sourceforge.net/livecd.php
download Install Gparted Live either on CD or USB
Read instructions from site.
Do not use recovery to format ext3 or ext4. This will only lead to errors.
Veldscholte said:
Hello guys. Thanks for all the reply's. I'm sorry to say it, but I'm a beginner in this area. What is the best thing I can do now? How do I format all my partitions into ext4?
Click to expand...
Click to collapse
Why do you want to format ALL of your partitions to EXT4? You phone needs a FAT32-partition as well.
So if the ROM you flashed or you want to flash needs an EXT4-partition, backup all important data on your SD card, boot into recovery and partition your SD card with FAT32-partition plus an EXT4-partition with 1 GB (I recommend 1 GB because it will be compatible with nearly every ROM you find here) and copy all data back on FAT32-partition.
You can do this operation either in recovery (worked always well for me) or with GParted. Just do not use software like MiniTool Partition Wizard or any other Windows software which "deals" with EXT-partitions, because these types are Linux-partition-types and I would not trust Windows there if you want to have the rewards of your SD card.
In Q&A you can and will find a very good noob guide which will help you a lot:
http://forum.xda-developers.com/showthread.php?t=1016084
If you still have questions / problems, use the search. And if there is still something that bothers you, ask your question here in Q&A.
---------- Post added at 01:04 AM ---------- Previous post was at 12:58 AM ----------
bored_stupid said:
Go to http://gparted.sourceforge.net/livecd.php
download Install Gparted Live either on CD or USB
Read instructions from site.
Do not use recovery to format ext3 or ext4. This will only lead to errors.
Click to expand...
Click to collapse
This is just not true. Recovery is an easy and very good way to partition your SD card and will work well nearly every time. I cannot remember any partitioning errors (can you name at least one anyway?) or rather problems caused by partition with recovery. As far as I remember, the causes were always crap software like Rom Manager or MiniTool Partition Wizard or something like that.
MatDrOiD said:
Why do you want to format ALL of your partitions to EXT4? You phone needs a FAT32-partition as well.
So if the ROM you flashed or you want to flash needs an EXT4-partition, backup all important data on your SD card, boot into recovery and partition your SD card with FAT32-partition plus an EXT4-partition with 1 GB (I recommend 1 GB because it will be compatible with nearly every ROM you find here) and copy all data back on FAT32-partition.
You can do this operation either in recovery (worked always well for me) or with GParted. Just do not use software like MiniTool Partition Wizard or any other Windows software which "deals" with EXT-partitions, because these types are Linux-partition-types and I would not trust Windows there if you want to have the rewards of your SD card.
In Q&A you can and will find a very good noob guide which will help you a lot:
http://forum.xda-developers.com/showthread.php?t=1016084
If you still have questions / problems, use the search. And if there is still something that bothers you, ask your question here in Q&A.
---------- Post added at 01:04 AM ---------- Previous post was at 12:58 AM ----------
This is just not true. Recovery is an easy and very good way to partition your SD card and will work well nearly every time. I cannot remember any partitioning errors (can you name at least one anyway?) or rather problems caused by partition with recovery. As far as I remember, the causes were always crap software like Rom Manager or MiniTool Partition Wizard or something like that.
Click to expand...
Click to collapse
Apologies, what i should have said was," could possibly cause problems ". I have occasionally had problems with some fussy roms boot-looping after installation, but after reformatting in Gparted, they have worked," this could be coincidence though ". I fully agree with you on the likes of Rom Manager and MiniTools.
Veldscholte said:
***This method only works for users with hboot 0.93 and lower. Sorry 1.06 users, but until unrevoked updates, your stuck on stock htc***
I have hboot 6.93.1002..
Edit: Now I have an ext4 partition on my sd card. How can I install any custom rom on that partition? Windows can't read it.
Click to expand...
Click to collapse
Please do some research about installing ROMs etc. You clearly did not even understand the basics.
What hboot do you have? Still the same as first post? Post info from hboot/fastboot, why did you run RUU?
Sent from my HTC Desire using XDA Premium App
Ok, flash recovery via fastboot
Fastboot flash recovery "name of recovery IMG file"
Sent from my HTC Desire using XDA Premium App
Veldscholte said:
What image file do I need to flash?
Click to expand...
Click to collapse
The recovery.img-file.
for rmd recovery see my signature as you have no system yet... flash it then you can flash custom rom
Does RMD backup and restore .android_secure properly now?
Personally I wouldn't recommend anything other than cwm 2.5.0.7 or amonRA 2.0.1 depending on erase size to a newbie
Sent from my HTC Desire using Tapatalk
It should have... i remember there was conversation between you and rastaman if im right... but since new version came out 1.0.3.5, i was using 1.0.3.4 without any problem then I changed over to 4ext... I can't be 100% it was fixed... Can you have a look please?
yes i know cwm or amon ra but these have usb brick function i dont want to have him back if it will happen
Just in case 4EXT recovery
MD5 2D75F6EE7626D98F84E148C2BD8C0855
boot phone to fastboot, connect to pc and run in cmd:
fastboot devices
if you get any HTxxxxxxxxxxxxxxxxxxxxxxx number you can proceed to flashing recovery
kotag82 said:
It should have... i remember there was conversation between you and rastaman if im right... but since new version came out 1.0.3.5, i was using 1.0.3.4 without any problem then I changed over to 4ext... I can't be 100% it was fixed... Can you have a look please?
yes i know cwm or amon ra but these have usb brick function i dont want to have him back if it will happen
Just in case 4EXT recovery
MD5 2D75F6EE7626D98F84E148C2BD8C0855
Click to expand...
Click to collapse
I haven't recommended 4ext to anyone yet, Ive still been recommending what I mentioned, but Ive been using it solidly for a good few weeks now and I think I am about ready to start recommending it...
Veldscholte said:
How can I use fastboot if I can't get an adb connection?
Click to expand...
Click to collapse
adb and fastboot are 2 totally different things. It just happens that they both are command line and used to communicate with your android phone. The similarity ends there.
Do what Kotag said.
If you click the link to my guides in my signature, I have an adb and fastboot faq that may be of use to you.
Is it boot loop or stuck on splash screen?
Sent from my HTC Desire using XDA Premium App
That splash, that means booting process did not started
What hboot you have, I presume you flashed seb15 Runny, what version? Sd ext done properly?
Sent from my HTC Desire using XDA Premium App
Hi All, let me start with a warning…
total Android n00b here, doing his first ROM flash on a newly rooted T-Mobile G2. I’ve read and searched a bit in the forum threads to see if I could solve this on my own, but I do need help.
VISION PVT SHIP S-OFF
HBOOT - 0.82.0000 (PC1010000)
MICROP - 0425
RADIO - 26.02.01.15_M2
eMMC - boot
Aug 20 2010, 16:51:01
This is from using the instructions in Strawmetal’s PDF guide to Downgrading from Gingerbread to Froyo and Root. I am working with a G2 phone that was set to Factory Reset before rooting, so there is no user data to backup or worry about.
1. I downloaded the Andromadus Mimicry 1.1.2 ROM image, and verified the md5 checksum on my sdcard using the AFV Legacy application. The Gapps image also was verified as well.
2. Using ROM Manager 5.0.0.8 from the Google Market, I ran Clockwork Recovery to install the Andromadus image. I left all settings on defaults and the installer ran fine.
3. When it restarted, I was left stuck at the white HTC screen for ages… the longest I left it was 20 mins. After that, I pulled the battery and restarted. Same white HTC screen.
4. I tried using Volume (+) key and Power On to get back to Clockwork Recovery, but the phone vibrated (buzzed) 3x times quickly, and the Power LED lamp pulsed an amber color. Again, yank battery, restart, same white HTC screen.
5. finally I decided to read more of the help for adb, and found the command “adb reboot-bootloader”. This let me get into the default Recovery mode, and it proceeded to find the PC10IMG.zip I still had on the sdcard from doing the Froyo downgrade. Recovery checked it out, ran it and restored the stock Froyo image and my phone did a proper restart. WHEW.
After that, I had to run adb to install the hboot recovery image file, and the busybox checksums were valid according to Strawmetal’s PDF instructions to get permanent root back after restoring the stock Froyo image.
I have done this process about 4 times, and am really good at typing inside adb now
But I’m lost…
-did I pick a ROM that doesn’t work with the G2? Other posters to the forum thread appear to be using the HTC Vision or G2.
-is ROM Manager not a good way to install a ROM?
-when I tried to get back into Recovery, what do the 3x buzzes/amber power LED mean?
-I never got to install the Gapps image; was I supposed to install that first, then the ROM image?
I imagine I did something wrong (duh!), but I can’t spot it. If someone can help me through this, I’d appreciate some advice very much.
thanks!
Rather than clockwork, use 4EXT recovery, much better for our device. ROM manager and clockwork have grown very iffy over the past year. Don't use rom manager to install a rom, download the zip yourself and manually install it in recovery.
Next you need to find the "superwipe+ext4.zip" floating around here, it is indispensable for FULLY wiping your phone when switching roms.
Mimicry works fine on the G2, in fact everything (except a few sense roms that need a Desire Z hboot) in the development section runs fine on the G2.
So....get the ROM, GApps for that ROM, the Superwipe zip (you will flash this right before you begin flashing the rom) on your SD card and make sure you are using 4EXT recovery (find the link in the dev section).
Make sure before you do ANYTHING you make a Nandroid backup (using your recovery).
Your issue is actually addressed in the Mimicry OP, please read it first. That said, the problem is almost certainly because you're coming from GB without a full wipe. You can use 4ext to repartiton/wipe all, or you can use superwipe+ext4 as mentioned by Nospin.
Sent from my HTC Vision using xda premium
Hi Nospin,
Thank you very much for your suggestions!
I will revise my root and remove Clockwork, and switch to 4EXT instead.
I appreciate the idea of "superwipe"; I will look for that as well today.
If I understand everything right...
-replace CWM with 4EXT
-place superwipe.zip, Gapps.zip and the Mimicry ROM.zip on the top level of the sdcard first.
-reboot the phone and run 4EXT recovery
-select superwipe to run first, then the ROM and then Gapps
-then restart the phone
When I used CWM before to install the ROM, it rebooted on its own before I could install Gapps. Will 4EXT let me do each install right after each other or do I have to return to 4EXT for each separate install?
regards,
motionmonk
Nospin said:
Rather than clockwork, use 4EXT recovery, much better for our device. ROM manager and clockwork have grown very iffy over the past year. Don't use rom manager to install a rom, download the zip yourself and manually install it in recovery.
Next you need to find the "superwipe+ext4.zip" floating around here, it is indispensable for FULLY wiping your phone when switching roms.
Mimicry works fine on the G2, in fact everything (except a few sense roms that need a Desire Z hboot) in the development section runs fine on the G2.
So....get the ROM, GApps for that ROM, the Superwipe zip (you will flash this right before you begin flashing the rom) on your SD card and make sure you are using 4EXT recovery (find the link in the dev section).
Make sure before you do ANYTHING you make a Nandroid backup (using your recovery).
Click to expand...
Click to collapse
Hi blk_jack,
I went back to the Mimicry page and re-read the FAQ section.
I think what I got out of it the first time was that if the ROM flash failed, it could be a corrupt ROM image. I will definitely use 4EXT to repartition before I try again with a ROM flash.
I guess I am still getting used to the terms for everything; can 4EXT do the nandroid backup? or is there a better process for setting that up?
thank you!
motionmonk
blk_jack said:
Your issue is actually addressed in the Mimicry OP, please read it first. That said, the problem is almost certainly because you're coming from GB without a full wipe. You can use 4ext to repartiton/wipe all, or you can use superwipe+ext4 as mentioned by Nospin.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Yes, you should be able to flash the rom and then GApps without rebooting. Give me a few and I will send you a PM with a few links....
Shot you a PM.
Thanks! I'll check it out :good:
Nospin said:
Shot you a PM.
Click to expand...
Click to collapse
Update-not working
Ok...
I re-flashed back to stock Froyo, and did a permanent root.
Installed 4ext Recovery (instead of Clockwork), and got a copy of SuperwipeG2+ext4;
I copied new checksum'd copies of Mimicry 1.1.2 ROM and GApps to my sdcard.
Booted into 4ext Recovery and installed from .zip the SuperwipeG2+ext4 file.
System, data and cache are all converted to ext4 partitions.
Wiped the system and data and cache partitions.
Installed from inside Recovery the Mimicry ROM and then the GApps archives.
No errors reported.
Upon reboot, I still get the white HTC screen. UGH.
I've left it on in that state for 30 mins... I had to yank the battery after that in shame...
I have tried to make sure that I read up on background steps, and I feel I do understand the overall process, but something is still getting in the way. I am doing this as I mentioned in an earlier post on a factory reset G2 with a clean erased SD card (has the stock Froyo image, Andromadus Mimicry ROM and GApps only). There is no SIM card installed either, wifi is off (to avoid OTA upgrade requests).
Are there other things I can try, or info I can supply that would help? I think I'm so close to getting this done... I must be overlooking something obvious.
I run that by rom along with Cm9 beta..... Try adding that to your boot process. Just Cm9 beta..... Other than version of crash.... That's just what I have experienced
Sent from my HTC Vision using xda premium
Hi amogil,
Just to be sure I understand, are you saying you are swapping between Andromadus and CM9 beta on your phone?
Did you flash CM9 first? and then Andromadus?
or just carrying the CM9 beta image and running Andromadus?
Sorry, I'm all sorts of confused here lol
thanks
amogil said:
I run that by rom along with Cm9 beta..... Try adding that to your boot process. Just Cm9 beta..... Other than version of crash.... That's just what I have experienced
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Ugh....it's frustrating isn't it?
Can you boot into any other rom? For example if you downloaded CM7.2? If you don't have any problems we can eliminate some possibilities.....
I had a similar problem booting into Mimicry my first time, in that I could get past the white HTC screen but after that my screen would just go black. After a couple frustrating hours what ended up working for me was downloading the older version (1.1.1 I think?) and that booted up fine . Then after letting that boot I went back into recovery and flashed 1.1.2 without wiping (I might have wiped cache and dalvik...). Everything worked great after that. Not the same problem as you, but similar.....
It's definitely a thought, and I believe that's what amogil is telling me too...
Ya, I can try a different ROM and report back.
I guess I should go back to stock Froyo and then start from CM7.2, and if that boots, try Mimicry again?
-from the Andromadus FAQ, it says it if a different ROM is based on ICS9, you shouldn't have to wipe. But with CM7, I'd have to wipe the Dalvik cache, yes?
-since CM7 is obviously not based on ICS9, would being able to launch into that show some details I can't see at present? Just was curious.
Or, do you think it better to go stock Froyo and then the older Mimicry ROM?
Either way, I'll make sure that I use the Superwipe to set things to ext4 first.
thanks guys for the ideas,
motionmonk
Nospin said:
Ugh....it's frustrating isn't it?
Can you boot into any other rom? For example if you downloaded CM7.2? If you don't have any problems we can eliminate some possibilities.....
I had a similar problem booting into Mimicry my first time, in that I could get past the white HTC screen but after that my screen would just go black. After a couple frustrating hours what ended up working for me was downloading the older version (1.1.1 I think?) and that booted up fine . Then after letting that boot I went back into recovery and flashed 1.1.2 without wiping (I might have wiped cache and dalvik...). Everything worked great after that. Not the same problem as you, but similar.....
Click to expand...
Click to collapse
The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium
SUCCESS!
Woohoo!
It works!
Since I had an ICS9 ROM already in place and was planning to wipe back to stock anyways, I tried flashing the older Andromadus 1.1.0 ROM.
What a surprise and treat to see the startup animation!
After poking around for an hour inside it, I then tried Recovery to reflash to the newest 1.1.2 ROM.
YAY! It works!
OMG, having a new ROM is like having a new phone-- there are so many improvements to the UI and it's quick and speedy versus GB. Dang, I'm happy now :victory:
Observations:
1. I did notice that inside Recovery, my touchscreen was barely functional when I tried to update from 1.1.0 up to 1.1.2-- I had to use the Volume +/- and the d-pad button to make selections. After the flash, the touchscreen is as responsive as ever.
2. it's got me thinking, that there must be a setting that is expected in the v1.1.2 ROM that the v1.1.0 ROM installed. Or could something else be the issue? I mean absolutely no disrespect to the developers... but on the technical side, I'm just curious what possibilities exist that might lead to this situation.
3. backup question... when I use MyBackup Pro, I know I can make an archive of the apps I've installed, and an archive of the data (documents, music, settings). Is a nandroid backup different from that? when I see the backup/restore options inside of 4ext Recovery, what are those doing that's different from what I get from MyBackup Pro?
thanks for all the help and encouragement. I have a new ROM installed! :good:
strawmetal said:
The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Oooh, a possibility. We will see if he can boot a different rom.
Whenever you switch roms (even if they are using the same Android version as a base) I suggest a full wipe. (Wipe all user data + Dalvik Cache + Cache, or just flash the superwipe zip). When upgrading the rom you are currently on (say upgrading CM Nightlies or going from Mimicry 1.1.1 to 1.1.2) you only need to really wipe cache and dalvik cache. Unless the dev states otherwise of course.
Hi strawmetal,
It turns out that I did have s-off after all...
1. after one of the many attempts to flash the ROM image and restoring back to stock Froyo, I said that "I'm gonna start this entire process over to be sure." So I get stuck using the fre3vo tool for about 30 minutes, rebooting and trying different address ranges to find the exploit.
Never found one... oh no, what did I do to the phone now??
-then it hit me; if it can't find an exploit... then it must already been used!
2. also, I did check each time I was in bootloader that my S-OFF was there and the radio and hboot were not changing versions.
3. Hehe, and the best indication was... being able to boot up finally!
I also have your Strawmetal.CM.V6.zip on my sdcard; if the downflash (?) to the Andromadus older ROM didn't work, yours was the CM7 image I wanted to try. If it's ok, I think I want to play around inside CM9 for a bit and then try yours out after that. I don't want to overwhelm my poor brain!
thank you for your suggestion... that definitely would be something to check as well.
strawmetal said:
The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Thank You All!
A big shout out to:
Nospin
blk_jack
amogil
strawmetal
for taking the time out to help a total n00b stumble through his first ROM flash.
I really appreciate the points you guys made, and the help provided.
Thank you!
I hope that one day I can help someone else out with a problem and pass the kindness forward.
Yay! I have a working ROM!
motionmonk
motionmonk said:
Hi strawmetal,
It turns out that I did have s-off after all...
1. after one of the many attempts to flash the ROM image and restoring back to stock Froyo, I said that "I'm gonna start this entire process over to be sure." So I get stuck using the fre3vo tool for about 30 minutes, rebooting and trying different address ranges to find the exploit.
Never found one... oh no, what did I do to the phone now??
-then it hit me; if it can't find an exploit... then it must already been used!
2. also, I did check each time I was in bootloader that my S-OFF was there and the radio and hboot were not changing versions.
3. Hehe, and the best indication was... being able to boot up finally!
I also have your Strawmetal.CM.V6.zip on my sdcard; if the downflash (?) to the Andromadus older ROM didn't work, yours was the CM7 image I wanted to try. If it's ok, I think I want to play around inside CM9 for a bit and then try yours out after that. I don't want to overwhelm my poor brain!
thank you for your suggestion... that definitely would be something to check as well.
Click to expand...
Click to collapse
The bootloader can show a false s-off. I've personally experienced this. By the time "HTCDev bootloader unlock" came out i was already rooted. But as curious as I was I decided to try it out. Flashed an RUU ( my my why would I do that ) Got back s-on( guess this was false too) then I used HTCDev method to prove i'm a total noob. Then i relocked it using Nipqer's guide and followed setherio's method again. I was able to use the stock froyo, but no other rom would boot( false s-off being the culprit ). This time I ran to #g2root on freenode. Nipqer saved me.
WOW. i just realized there is SO MUCH I need to catch up on!
I'll have to look up some of these guides later today... but the RUU is the ROM upgrade, right?
Did you ever find a reason why you got the false S-OFF flag? It's clear that the way I was looking at the failed fre3vo exploit as proof of S-OFF isn't always going to be true... but how would you separate a false S-OFF flag from lets say a wrong hboot image?
BTW, your PDF on downgrading and rooting the G2 was a godsend. Very very helpful and clear.
One of the reasons why I took so long to try rooting was that I was confused by the different methods and the replies of X not working, Y is a better way... going through your guide and the info here on xda cleared alot of things up. :good:
strawmetal said:
The bootloader can show a false s-off. I've personally experienced this. By the time "HTCDev bootloader unlock" came out i was already rooted. But as curious as I was I decided to try it out. Flashed an RUU ( my my why would I do that ) Got back s-on( guess this was false too) then I used HTCDev method to prove i'm a total noob. Then i relocked it using Nipqer's guide and followed setherio's method again. I was able to use the stock froyo, but no other rom would boot( false s-off being the culprit ). This time I ran to #g2root on freenode. Nipqer saved me.
Click to expand...
Click to collapse
issue has been SOLVED thanks lo2ay
seems a clear head works wonders.
Ok this is gonna take some explaining which i will try my best to do, hopefully somebody can point out my error or solution.
Today i thought id go back to sense rom (doesnt matter which as i will explain) mtds all reset back to stock p wilfredfire or whatever your called lol) full fresh wipes and temp 2.5 cwm flashed (i dont use rom manager, its deleted from my roms) so temp cwm recovery 2.5 boots and the 1st strange thing occurs... The screen menus are all split in half! Eg have you ever taken a screenshot and found it split in half? Well thats what my menu options look like! On each option selected via up/down using vol key it changes to normal, split, normal split etc etc same in sub menus too.
So i just get on with things and try to flash sense rom....... Now i get some error, something to do with 1.sysE sdext not found? 2.chown xbin a2sd? 3.maybe something else cant read it as its all shown on the split screen lol.
Ive installed permanent 2.5 cwm and get same errors but not split screen issues?
Now ive never had this problem before but i have changed my sdcard and it has a 1gb partition which is only ever used for on sense roms and is partitioned from cwm 5.0.2.8 version just like my previous sdcard was.
I have 2 theories as too whats going on but not convinced.
1. Maybe my sdcard is ****e and it wasnt the sdcard i used to s-off with!! Does a new sdcard need to be goldcarded? I really dont think this is the issue.
2. I was having issues with some data/app duplication files from external roms which i used a while back. I fixed these issues by deleting all found existing files containing a2sd wording but i cant recall the paths of them eg. Some from etc/init'd but also others from outside of system folder! Maybe sys and others too but it was a while back and been on lewa for so long without any issues regarding this problem.
So is it possible ive deleted some file that is not recreated with a fresh rom install? Eg its a phone file that remains no matter what rom or cwm used?
This is only happening when im trying to flash roms/restores that dont require edify i.e 2.5 cwm needed and when im back using cwm 5.0.2.8 all roms and restores are fine. even rempuzzle which is sense but doesnt require using 2.5.
So im stumped as i can flash a sense rom but not older sense roms via temp or permanent 2.5 cwm, its nothing to do with my mtd, if it was a permanent file i deleted then it should be consistent across all roms/cwm but isnt. Ive changed sdcards lots of times but they have been used as goldcards in the past where my new one has not?
Ive tried rom manager too, still get split screen and same errors!?
Tricky one eh!! Lol.
Forum fishing.... Who's biting!
Maybe your cwm zip got corrupted..
saadislam said:
Maybe your cwm zip got corrupted..
Click to expand...
Click to collapse
Was my first thought, too (but I guess you already checked this?)
Indeed a tricky one. For the sd card guess: nah, I've dropped my stock 2 gb (I made the gold card with) for a 8 gb class 4 and later on for a 8 gb class 10 and never had any issues.
Regarding a missing "permanent" file: I'd also doubt this as such a file should be damaged or deleted in many other cases, too (flashing/formatting/factory resets/partitioning etc), at least once in a while. I'm quite sure this would happen more often, at least.
I also thought it could be a problem with the display driver but I don't know enough about the hard- and software to say it could...
Is rempuzzle still froyo or already gb?
If it has to do with leftovers or missing stuff I'd more likely guess that something with the different cwm versions has been messed up. But like I said: I don't really know enough about it.
Swyped from my HTC Wildfire (Buzz)
slymobi said:
Ok this is gonna take some explaining which i will try my best to do, hopefully somebody can point out my error or solution.
Today i thought id go back to sense rom (doesnt matter which as i will explain) mtds all reset back to stock p wilfredfire or whatever your called lol) full fresh wipes and temp 2.5 cwm flashed (i dont use rom manager, its deleted from my roms) so temp cwm recovery 2.5 boots and the 1st strange thing occurs... The screen menus are all split in half! Eg have you ever taken a screenshot and found it split in half? Well thats what my menu options look like! On each option selected via up/down using vol key it changes to normal, split, normal split etc etc same in sub menus too.
So i just get on with things and try to flash sense rom....... Now i get some error, something to do with 1.sysE sdext not found? 2.chown xbin a2sd? 3.maybe something else cant read it as its all shown on the split screen lol.
Ive installed permanent 2.5 cwm and get same errors but not split screen issues?
Now ive never had this problem before but i have changed my sdcard and it has a 1gb partition which is only ever used for on sense roms and is partitioned from cwm 5.0.2.8 version just like my previous sdcard was.
I have 2 theories as too whats going on but not convinced.
1. Maybe my sdcard is ****e and it wasnt the sdcard i used to s-off with!! Does a new sdcard need to be goldcarded? I really dont think this is the issue.
2. I was having issues with some data/app duplication files from external roms which i used a while back. I fixed these issues by deleting all found existing files containing a2sd wording but i cant recall the paths of them eg. Some from etc/init'd but also others from outside of system folder! Maybe sys and others too but it was a while back and been on lewa for so long without any issues regarding this problem.
So is it possible ive deleted some file that is not recreated with a fresh rom install? Eg its a phone file that remains no matter what rom or cwm used?
This is only happening when im trying to flash roms/restores that dont require edify i.e 2.5 cwm needed and when im back using cwm 5.0.2.8 all roms and restores are fine. even rempuzzle which is sense but doesnt require using 2.5.
So im stumped as i can flash a sense rom but not older sense roms via temp or permanent 2.5 cwm, its nothing to do with my mtd, if it was a permanent file i deleted then it should be consistent across all roms/cwm but isnt. Ive changed sdcards lots of times but they have been used as goldcards in the past where my new one has not?
Ive tried rom manager too, still get split screen and same errors!?
Tricky one eh!! Lol.
Forum fishing.... Who's biting!
Click to expand...
Click to collapse
I'm also having the same issue,i used rom manager to get temp. 2.5 recovery to flash the radio, and got split screen. i flashed it anyway successfully.
This might sound noobish, but i think mokee os and a few foreign roms are to blame (roms from the same source you got mokee).
I'm saying this because it all started when i reverted back to cm9 from mokee and few of those foreign ones.
just sharing my experience, i might be wrong coz I'm not technically sound as you ppl are.
Sent from my HTC Wildfire using Tapatalk 2
I've had that split screen before, it happened to me when my permanent recovery was 5.0.2.8
and temporary was 5.0.2.0
any older temp recovery with 5.0.2.8 as permanent will make this bug. But everything is working tho.
That's a tricky one indeed
Sent from my HTC Wildfire using Tapatalk 2
Wasimk32 said:
I'm also having the same issue,i used rom manager to get temp. 2.5 recovery to flash the radio, and got split screen. i flashed it anyway successfully.
This might sound noobish, but i think mokee os and a few foreign roms are to blame (roms from the same source you got mokee).
I'm saying this because it all started when i reverted back to cm9 from mokee and few of those foreign ones.
just sharing my experience, i might be wrong coz I'm not technically sound as you ppl are.
Sent from my HTC Wildfire using Tapatalk 2
Click to expand...
Click to collapse
Its a good point you make, as it could well be that but that would mean that one of the external roms we used has a bogus file sticking after full wipes and rom changes?? I cant see it being that but maybe wrong?
lo2ay said:
I've had that split screen before, it happened to me when my permanent recovery was 5.0.2.8
and temporary was 5.0.2.0
any older temp recovery with 5.0.2.8 as permanent will make this bug. But everything is working tho.
That's a tricky one indeed
Sent from my HTC Wildfire using Tapatalk 2
Click to expand...
Click to collapse
Mmmm so cwm 5028 perm is the split screen cause you say? Will go install 5020 and test.
Forum fishing.... Who's biting!
lo2ay i think i love you man. solved.
and heres how.............
unzipped a pc49img.zip and put in recoveryimg of 5.0.2.0 booted into bootloader and ran the update. rebooted then booted into recovery 5.0.2.0 wiped all and flashed temp 2.5 ( woo woo all full screen) flashed wildpuzzle (woo woo no errors)
SO CONCLUSION IS THAT CWM 5.0.2.8 IS MISSING SOMETHING NEEDED FOR OLDER EDIFY ROM INSTALLS EVEN WHEN USING THE TEMP 2.5 CWM.
I JUST REMEMBERED TOO that in the past i was on 5.0.2.0 and not 5.0.2.8 so i dont know why i started using the 5.0.2.8 anyway ??? well that has now found its way to the recycle bin lol.
so simple in the end lol.
many thanks to lo2ay for sending me in the right direction. xxxxxxxx lol
Glad I helped
Sent from my HTC Wildfire using Tapatalk 2
Did you get the other issue resolved? That chown etc error?
The error came because of the following.
1. You flashed CM rom from sense, you had MTD (For example 135 & 5)
2. This will install system partition and data partition for this MTD
3. Now you decide to go back to sense. and flashed MTD (250 40)
4. Even though you flash this MTD bravo file, your sense rom cant fit into your 135 system partition the 250 partition will be written only on boot of your ROM. Before that sense ROM must be written into your system
5. So error will come throwing all nonsense on the screen like chown error etc
6. How to solve this??
Flash a CM rom with MTD as 250 and 40 MTD. Once your ROM is on, check you have 175Mb as total memory, not more than that in your storage setting
7. Now flash a sense rom booting into recovery.. viola no errors
I guess it worked for you because you got fed up and flashed a CM rom over 250 40 MTD
and then flashed this recovery problem and then turned to sense..
At that point, no issues with system partition and wildpuzzle would have fitted correctly
Am i right???
Sam3087 said:
Did you get the other issue resolved? That chown etc error?
The error came because of the following.
1. You flashed CM rom from sense, you had MTD (For example 135 & 5)
2. This will install system partition and data partition for this MTD
3. Now you decide to go back to sense. and flashed MTD (250 40)
4. Even though you flash this MTD bravo file, your sense rom cant fit into your 135 system partition the 250 partition will be written only on boot of your ROM. Before that sense ROM must be written into your system
5. So error will come throwing all nonsense on the screen like chown error etc
6. How to solve this??
Flash a CM rom with MTD as 250 and 40 MTD. Once your ROM is on, check you have 175Mb as total memory, not more than that in your storage setting
7. Now flash a sense rom booting into recovery.. viola no errors
I guess it worked for you because you got fed up and flashed a CM rom over 250 40 MTD
and then flashed this recovery problem and then turned to sense..
At that point, no issues with system partition and wildpuzzle would have fitted correctly
Am i right???
Click to expand...
Click to collapse
Yes and no ? My mtds had been reset then flashed cm to confirm.so in theory I was all ready to flash sense as partition was showing the size at 250 40 but must have been a false reading! I know exactly what your saying and it makes sense,I triple reset my mtds but obviously something stuck somewhere lol.I've done this 100s of time but like I've said it was always with cwm 5.0.2.0 not 5.0.2.8 which I can't understand why or when I was using this version. I pre edit my roms and normally have a universal mtd setting that is acceptable for any of my roms I flash so its gotta be the cwm. its all fixed now with a clean cwm.cheers though.
sent mysteriously via OTA
slymobi said:
Yes and no ? My mtds had been reset then flashed cm to confirm.so in theory I was all ready to flash sense as partition was showing the size at 250 40 but must have been a false reading! I know exactly what your saying and it makes sense,I triple reset my mtds but obviously something stuck somewhere lol.I've done this 100s of time but like I've said it was always with cwm 5.0.2.0 not 5.0.2.8 which I can't understand why or when I was using this version. I pre edit my roms and normally have a universal mtd setting that is acceptable for any of my roms I flash so its gotta be the cwm. its all fixed now with a clean cwm.cheers though.
sent mysteriously via OTA
Click to expand...
Click to collapse
Oh
Anyways am glad that its working back alright..
I can keep an eye on the "show your display thread" again :good: :laugh:
slymobi said:
Yes and no ? My mtds had been reset then flashed cm to confirm.so in theory I was all ready to flash sense as partition was showing the size at 250 40 but must have been a false reading! I know exactly what your saying and it makes sense,I triple reset my mtds but obviously something stuck somewhere lol.I've done this 100s of time but like I've said it was always with cwm 5.0.2.0 not 5.0.2.8 which I can't understand why or when I was using this version. I pre edit my roms and normally have a universal mtd setting that is acceptable for any of my roms I flash so its gotta be the cwm. its all fixed now with a clean cwm.cheers though.
sent mysteriously via OTA
Click to expand...
Click to collapse
Do you have the off charge bug with 5.0.2.0? That´s the reason I have 5.0.2.8 instead.
DMarzal said:
Do you have the off charge bug with 5.0.2.0? That´s the reason I have 5.0.2.8 instead.
Click to expand...
Click to collapse
I thought that was on 4.0.1.4?
DMarzal said:
Do you have the off charge bug with 5.0.2.0? That´s the reason I have 5.0.2.8 instead.
Click to expand...
Click to collapse
not what i know of but then again i never have my phone off to charge.
I've just bought a used HTC Desire, and after installing only 4 apps (Google Play Store, ES File Explorer, Screen Off and Lock and Swiftkey) it is reporting only 4Mb of free memory. What's the best way of reclaiming memory? Would it be a custom ROM? If so, can anyone recommend something that's very slimline and robust? I don't need the HTC bloatware (including Sense) - just Google Maps, Swiftkey and a few other apps.
The phone is currently running Android 2.2.2, Baseband version 32.48.00.32U_5.11.05.14
Is rooting/ROMing this device pretty straightforward?
The best way is to create an ext partition on your sdcard and use a script (a2sd) to move apps and dalvik cache to the partition. Most custom roms support, or come with these types of scripts. You will also want to change your hboot (internal partition layout) to something more practical that allocates more space to the data partition and less to system and cache. Before doing this you will need to get s-off and a custom recovery. Post your bootloader details (turn phone off, then hold volume down + power to enter bootloader), and i will give you further advice on how to go about doing this.
Chromium_ said:
The best way is to create an ext partition on your sdcard and use a script (a2sd) to move apps and dalvik cache to the partition. Most custom roms support, or come with these types of scripts. You will also want to change your hboot (internal partition layout) to something more practical that allocates more space to the data partition and less to system and cache. Before doing this you will need to get s-off and a custom recovery. Post your bootloader details (turn phone off, then hold volume down + power to enter bootloader), and i will give you further advice on how to go about doing this.
Click to expand...
Click to collapse
Thanks for your help. My hboot version is 0.93.001 - does that help?
itm said:
Thanks for your help. My hboot version is 0.93.001 - does that help?
Click to expand...
Click to collapse
Yep. Your hboot is compatible with revolutionary, which is a tool used to gain s-off. S-off basically gives you the power to do stuff.
Install these drivers on your PC: http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
Enable USB debugging on the phone
Download revolutionary (create and make note of the beta key too): http://revolutionary.io/
Unzip the file, and run the executable. After thats done you should have s-off and a custom recovery installed.
Let me know when thats done, or if you need more help.
Chromium_ said:
The best way is to create an ext partition on your sdcard and use a script (a2sd) to move apps and dalvik cache to the partition. Most custom roms support, or come with these types of scripts. You will also want to change your hboot (internal partition layout) to something more practical that allocates more space to the data partition and less to system and cache. Before doing this you will need to get s-off and a custom recovery. Post your bootloader details (turn phone off, then hold volume down + power to enter bootloader), and i will give you further advice on how to go about doing this.
Click to expand...
Click to collapse
Chromium_ said:
Yep. Your hboot is compatible with revolutionary, which is a tool used to gain s-off. S-off basically gives you the power to do stuff.
Install these drivers on your PC: http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
Enable USB debugging on the phone
Download revolutionary (create and make note of the beta key too): http://revolutionary.io/
Unzip the file, and run the executable. After thats done you should have s-off and a custom recovery installed.
Let me know when thats done, or if you need more help.
Click to expand...
Click to collapse
OK I've run revolutionary and accepted the option to flash a new recovery (clockworkmod). How I do I get to run an a2sd script?
itm said:
OK I've run revolutionary and accepted the option to flash a new recovery (clockworkmod). How I do I get to run an a2sd script?
Click to expand...
Click to collapse
First check to see if revolutionary was indeed successful (look for s-off in bootloader details).
Also I would suggest changing your recovery to a better one such as TWRP or 4ext. (clockwordmod that revolutionary flashes is pretty old and there are much better options for the desire).
After that you can pick a rom from the development section. The majority of them have some sort of a2sd script built in.
Then download the rom of your choice and flash using your recovery. Depending on the rom you choose, activating a2sd will differ. Some have it preactivated, while others will need you to run a few commands in terminal to turn it on.
Chromium_ said:
First check to see if revolutionary was indeed successful (look for s-off in bootloader details).
Also I would suggest changing your recovery to a better one such as TWRP or 4ext. (clockwordmod that revolutionary flashes is pretty old and there are much better options for the desire).
After that you can pick a rom from the development section. The majority of them have some sort of a2sd script built in.
Then download the rom of your choice and flash using your recovery. Depending on the rom you choose, activating a2sd will differ. Some have it preactivated, while others will need you to run a few commands in terminal to turn it on.
Click to expand...
Click to collapse
OK it seems I now have S-Off!
Pardon my ignorance, but what's the best way of flashing TWRP recovery? Do I need to use ADB bridge?
Also, can you recommend a lightweight ROM that has a2sd built-in?
Thanks so much for your help.
itm said:
OK it seems I now have S-Off!
Pardon my ignorance, but what's the best way of flashing TWRP recovery? Do I need to use ADB bridge?
Also, can you recommend a lightweight ROM that has a2sd built-in?
Thanks so much for your help.
Click to expand...
Click to collapse
Sorry forgot the links. If you want TWRP click on the Show Content button in my signature. Ive got a link there to TWRP for the desire. (instructions are in the post).
Do you want to stick with gingerbread or do you want a more recent 4+ rom?
Chromium_ said:
First check to see if revolutionary was indeed successful (look for s-off in bootloader details).
Also I would suggest changing your recovery to a better one such as TWRP or 4ext. (clockwordmod that revolutionary flashes is pretty old and there are much better options for the desire).
After that you can pick a rom from the development section. The majority of them have some sort of a2sd script built in.
Then download the rom of your choice and flash using your recovery. Depending on the rom you choose, activating a2sd will differ. Some have it preactivated, while others will need you to run a few commands in terminal to turn it on.
Click to expand...
Click to collapse
Chromium_ said:
Sorry forgot the links. If you want TWRP click on the Show Content button in my signature. Ive got a link there to TWRP for the desire. (instructions are in the post).
Do you want to stick with gingerbread or do you want a more recent 4+ rom?
Click to expand...
Click to collapse
Perfect - thanks.
A 4.* ROM would be nice, but would it leave me with less memory (and worse performance)?
itm said:
Perfect - thanks.
A 4.* ROM would be nice, but would it leave me with less memory (and worse performance)?
Click to expand...
Click to collapse
Yes, they definitely wont be as fast as a pure AOSP gingerbread rom, but you have to make some compromises if you want the latest and greatest
Chromium_ said:
Yes, they definitely wont be as fast as a pure AOSP gingerbread rom, but you have to make some compromises if you want the latest and greatest
Click to expand...
Click to collapse
TBH I'm more concerned about the memory footprint than the performance (although obviously the two are related). Would a 4.* ROM occupy alot more memory?
Incidentally I tried flashing a TWRP recovery zip from recovery mode, but kept getting "installation aborted". Any ideas??
itm said:
TBH I'm more concerned about the memory footprint than the performance (although obviously the two are related). Would a 4.* ROM occupy alot more memory?
Incidentally I tried flashing a TWRP recovery zip from recovery mode, but kept getting "installation aborted". Any ideas??
Click to expand...
Click to collapse
By memory Im assuming you mean storage rather than RAM. With gingerbread roms the system size is smaller, meaning that you can use an hboot that shrinks down the system partition a lot, thus leaving you with much more space on data (where apps go). With 4+ you can still do this to some extent, but not system sizes arent as small as on gingerbread. To give you an idea, at some point while on a jellybean rom i had around 50 apps installed with room for probably about 5 more.
Im guessing the issue is due to the fact that your current recovery is too old. Your other option is to use fastboot to flash the image, or use the PB99IMG method (easier). Download the file from here, then follow the instructions here (use the PB99IMG that i just gave you, not the one from that thread with instructions).
Chromium_ said:
Yes, they definitely wont be as fast as a pure AOSP gingerbread rom, but you have to make some compromises if you want the latest and greatest
Click to expand...
Click to collapse
Chromium_ said:
By memory Im assuming you mean storage rather than RAM. With gingerbread roms the system size is smaller, meaning that you can use an hboot that shrinks down the system partition a lot, thus leaving you with much more space on data (where apps go). With 4+ you can still do this to some extent, but not system sizes arent as small as on gingerbread. To give you an idea, at some point while on a jellybean rom i had around 50 apps installed with room for probably about 5 more.
Im guessing the issue is due to the fact that your current recovery is too old. Your other option is to use fastboot to flash the image, or use the PB99IMG method (easier). Download the file from here, then follow the instructions here (use the PB99IMG that i just gave you, not the one from that thread with instructions).
Click to expand...
Click to collapse
Since my main problem is not being able to install the apps that I need (due to lack of storage), I guess a Gingerbread ROM would make the most sense (much as it pains me to admit it). Do you have any recommendations for a fat-free Gingerbread ROM?
itm said:
Since my main problem is not being able to install the apps that I need (due to lack of storage), I guess a Gingerbread ROM would make the most sense (much as it pains me to admit it). Do you have any recommendations for a fat-free Gingerbread ROM?
Click to expand...
Click to collapse
Ok, makes sense. I would go with Mildwilds redux rom. Its themed to look somewhat modern, its got a very small system size and its got built in a2sd (you might not even need to use this since system is so small).
With this rom you can switch your hboot to oxygen r2. This will give you over 330mb for apps and app data (quite a lot compared to 147mb, what you currently have). If you think thats enough, then i would suggest not even using a2sd or creating a partition.
Let me know and ill give you further instructions.
Chromium_ said:
Ok, makes sense. I would go with Mildwilds redux rom. Its themed to look somewhat modern, its got a very small system size and its got built in a2sd (you might not even need to use this since system is so small).
With this rom you can switch your hboot to oxygen r2. This will give you over 330mb for apps and app data (quite a lot compared to 147mb, what you currently have). If you think thats enough, then i would suggest not even using a2sd or creating a partition.
Let me know and ill give you further instructions.
Click to expand...
Click to collapse
OK I've now got MildWIld installed - it looks great.
I've looked at the oxygen r2 link but don't quite follow the fastboot instructions - does this require ADB installed on my PC??
itm said:
OK I've now got MildWIld installed - it looks great.
I've looked at the oxygen r2 link but don't quite follow the fastboot instructions - does this require ADB installed on my PC??
Click to expand...
Click to collapse
Fastboot is the harder process. The easier way would be to use the PB99IMG method. On alpharev.nl download the PB99IMG_oxygenr2.zip file. Then rename it to PB99IMG.zip and put it on the root of your sdcard (not in any folders). Turn off the phone, boot into the bootloader and wait a few seconds. It should find the file and ask to install. Press volume up for yes, then reboot once its done.
Chromium_ said:
Ok, makes sense. I would go with Mildwilds redux rom. Its themed to look somewhat modern, its got a very small system size and its got built in a2sd (you might not even need to use this since system is so small).
With this rom you can switch your hboot to oxygen r2. This will give you over 330mb for apps and app data (quite a lot compared to 147mb, what you currently have). If you think thats enough, then i would suggest not even using a2sd or creating a partition.
Let me know and ill give you further instructions.
Click to expand...
Click to collapse
Chromium_ said:
Fastboot is the harder process. The easier way would be to use the PB99IMG method. On alpharev.nl download the PB99IMG_oxygenr2.zip file. Then rename it to PB99IMG.zip and put it on the root of your sdcard (not in any folders). Turn off the phone, boot into the bootloader and wait a few seconds. It should find the file and ask to install. Press volume up for yes, then reboot once its done.
Click to expand...
Click to collapse
OK I now have Oxygen R2 installed and seem to have 145Mb of internal storage free :0)
The only issue I have is that the Play Store app seems to be broken - whenever I open it I get "No Connection" (as if there's no internet connectivity). I'm connected to wifi, and other apps have no problems accessing the net. I've tried rebooting, turning wifi on/off, but no luck. Any ideas??
itm said:
OK I now have Oxygen R2 installed and seem to have 145Mb of internal storage free :0)
The only issue I have is that the Play Store app seems to be broken - whenever I open it I get "No Connection" (as if there's no internet connectivity). I'm connected to wifi, and other apps have no problems accessing the net. I've tried rebooting, turning wifi on/off, but no luck. Any ideas??
Click to expand...
Click to collapse
Google Maps has the same problem - no internet connection. It's as if it's just the Google apps that can't see the internet.
???
Hmmm....the plot thickens. I decided to wipe and re-flash the ROM and Gapps, but after wiping it would not let me re-flash the MildWild ROM - the flash fails. When I boot into Android now the keyboard app seems to be broken - every few seconds I get the error "the application Android keyboard has stopped unexpectedly" (I had previously installed Swiftkey - could that have had anything to do with it?).
So now I seem to have a "broken" ROM - no keyboard and no working Gapps. Any ideas for what I might try??
itm said:
Hmmm....the plot thickens. I decided to wipe and re-flash the ROM and Gapps, but after wiping it would not let me re-flash the MildWild ROM - the flash fails. When I boot into Android now the keyboard app seems to be broken - every few seconds I get the error "the application Android keyboard has stopped unexpectedly" (I had previously installed Swiftkey - could that have had anything to do with it?).
So now I seem to have a "broken" ROM - no keyboard and no working Gapps. Any ideas for what I might try??
Click to expand...
Click to collapse
Wipe and reflash again. Are you still using cwm?