Related
I'am on LeeDrOiD HD 3.0.2 GB an would like to update to LeeDrOiD HD V3.1.2
Do i HAVE to convert to EXT4 when updating to the latest LEEDROID?
And also is it ok to just install it over the top of my current version or is a wipe necessary,If i just install over the top will i lose anything or will it just be same as before i updated?
Sorry for noobish questions but installed LEEDROID a few weeks ago and love it but this will be my first upgrade.
One more question, Is the Sense 3 stuff all working properly now (weather,Lockscreen etc)
Glyde62 said:
I'am on LeeDrOiD HD 3.0.2 GB an would like to update to LeeDrOiD HD V3.1.2
Do i HAVE to convert to EXT4 when updating to the latest LEEDROID?
And also is it ok to just install it over the top of my current version or is a wipe necessary,If i just install over the top will i lose anything or will it just be same as before i updated?
Sorry for noobish questions but installed LEEDROID a few weeks ago and love it but this will be my first upgrade.
One more question, Is the Sense 3 stuff all working properly now (weather,Lockscreen etc)
Click to expand...
Click to collapse
I think you have to use the ext 4 full vipe first to get everything running smoothly
Glyde62 said:
I'am on LeeDrOiD HD 3.0.2 GB an would like to update to LeeDrOiD HD V3.1.2
Do i HAVE to convert to EXT4 when updating to the latest LEEDROID?
And also is it ok to just install it over the top of my current version or is a wipe necessary,If i just install over the top will i lose anything or will it just be same as before i updated?)
Click to expand...
Click to collapse
If you just flash over the top, all your apps and data will be kept, and all your partitions will become ext4 except for the /data partition, which will stay as ext3.
You only need to wipe first if you want to get ext4 on your /data partition. To be honest, I doubt you'll notice any difference in speed by having ext4 on data, so if you don't want the hassle of setting everything up, just flash over the top. If you decide to do a full wipe later, you can switch to ext4 on /data then.
I think Lee has said in his thread that he just flashes over the top, except when he wipes for testing. So at one point, at least, he still had ext3 on /data as well.
Hi.
My girlfriend is really fed up with the low amount of memory on her Wildfire S, so I've decided to help I've spent large portions of today and yesterday on:
unlocking the bootloader (using htcdev.com),
rooting (using SuperOneClick http://forum.xda-developers.com/showthread.php?t=803682),
partitioning her microSD (kingston 4 GB, class 2, fat32 + 1GB EXT4 + 256 Swap if I remember correctly),
installing recovery (installed ROMManager and flashed CWM recovery from there)
and experimenting with ROMs.
The problem is that I can't get the ROMs to boot.
I've tried:
1. m1ndh4x8r GB2.3.5 - http://forum.xda-developers.com/showthread.php?t=1432259 both odexed and deodexed - bootloop on the white HTC logo
2. Wildfire S Cracker GB2.3.5 - http://forum.xda-developers.com/showthread.php?t=1479002 - waited almost 30 minutes for the HTC logo to disappear and boot animation to start, but that never happened.
3. HenseMod 6 - http://forum.xda-developers.com/showthread.php?t=1434497 - the only ROM that managed to boot without problems. However I need all the HTC widgets, so I'm intending to switch to a different one.
I've also tried staying with the stock ROM and flashing a different kernel (OC Kernel http://forum.xda-developers.com/showthread.php?t=1430677) so that link2SD would work with EXT4, but that didn't boot also.
Does anyone here have any idea what could be the source of all these problems? Maybe you could suggest something? A different Sense ROM, some "procedure" that could help me.
Please, I just want her to be happy
Cheers!
Sound's like a Kernel Panic. I dont know how to solve it. But I had a great Sense rom this worked for me.
Here you are:
http://forum.xda-developers.com/showthread.php?t=1359727
I hope this will fix the Problem, and it's a really great rom.
before you flash the rom，did you wipe data and wipe cache，and what is the version of your recovery？you need use the newest 5.028 is better.
Vilq85 said:
Hi.
My girlfriend is really fed up with the low amount of memory on her Wildfire S, so I've decided to help I've spent large portions of today and yesterday on:
unlocking the bootloader (using htcdev.com),
rooting (using SuperOneClick http://forum.xda-developers.com/showthread.php?t=803682),
partitioning her microSD (kingston 4 GB, class 2, fat32 + 1GB EXT4 + 256 Swap if I remember correctly),
installing recovery (installed ROMManager and flashed CWM recovery from there)
and experimenting with ROMs.
The problem is that I can't get the ROMs to boot.
I've tried:
1. m1ndh4x8r GB2.3.5 - http://forum.xda-developers.com/showthread.php?t=1432259 both odexed and deodexed - bootloop on the white HTC logo
2. Wildfire S Cracker GB2.3.5 - http://forum.xda-developers.com/showthread.php?t=1479002 - waited almost 30 minutes for the HTC logo to disappear and boot animation to start, but that never happened.
3. HenseMod 6 - http://forum.xda-developers.com/showthread.php?t=1434497 - the only ROM that managed to boot without problems. However I need all the HTC widgets, so I'm intending to switch to a different one.
I've also tried staying with the stock ROM and flashing a different kernel (OC Kernel http://forum.xda-developers.com/showthread.php?t=1430677) so that link2SD would work with EXT4, but that didn't boot also.
Does anyone here have any idea what could be the source of all these problems? Maybe you could suggest something? A different Sense ROM, some "procedure" that could help me.
Please, I just want her to be happy
Cheers!
Click to expand...
Click to collapse
try cm7 to see if the rom boots up. Remember to wipe data,cache and dalvik cache
striker280 said:
Remember to wipe data,cache and dalvik cache
Click to expand...
Click to collapse
gq455402012 said:
before you flash the rom，did you wipe data and wipe cache，and what is the version of your recovery？you need use the newest 5.028 is better.
Click to expand...
Click to collapse
I always wipe data, cache and dalvik, just in case.
I can't check it now, but I installed Rom Manager just yesterday so I assume, that it flashes the latest version of the recovery.
I'll be able to experiment more on Wednesday. I'll try different roms, maybe the same roms, but immediately flash different kernel etc.
I'll let you know how it turns out.
Thanks
I have the MetroPCS version of the WFS that I've been messing with. I got the bootloader unlocked, I got it rooted, and I got S-off (without xtc clip).
When I try to flash cm7, it throws up an error and won't install. I tried m1ndh4x8r sense 3.5 and it 'worked' except com.Android.phone kept fc'ing making it unusable. wifi also didn't work. I'd like to have sense 3.5 but would also like cm7. i also tried the cm9 roms but they don't want to install either. Is there a ROM that has both (cm7 and sense) that's stable with working wifi? I'm not using the phone for calling, just messing with mods and such but may activate it at some point if I find a suitable ROM for it.
Sent from my LG-VM670 using XDA
gyanos422 said:
I have the MetroPCS version of the WFS that I've been messing with. I got the bootloader unlocked, I got it rooted, and I got S-off (without xtc clip).
you unlocked the bootloader，your hboot is 1.080099 or 1.090099，but you can s-off without XTC？how you did it？I know if you want s-off，the hboot ony 0.90000，how you downgrade the hbooot from 1.080099 to 0.90000?
Click to expand...
Click to collapse
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.
just wats in the title..it's f****ng my head!
wat am i suppose to do now? im on hboot ***.0029 ,s-On ,UNLOCKED by htcdev..flashed through philz touch recovery..
plz help gyz..i tried two CM11s -already,both m9 though one was released n other was (plus) edition
did you remember to flash boot.img separately?
hussamT said:
did you remember to flash boot.img separately?
Click to expand...
Click to collapse
yes man,ofcourse!
every tym I had a clean flash of the rom, it boots up,,stays a while but when I begin doing multitasks.. or do anything..it just reboots suddenly
Did you format /system before flashing the new rom? when moving between roms, formatting /data and /cache is sometimes not enough.
You may need to manually format /system *before* flashing a new ROM.
I went through that when moving from cfx to cm builds.
hussamT said:
Did you format /system before flashing the new rom? when moving between roms, formatting /data and /cache is sometimes not enough.
You may need to manually format /system *before* flashing a new ROM.
I went through that when moving from cfx to cm builds.
Click to expand...
Click to collapse
yes bro i manually formatted te /system partition too! btw i'll check it again if that would help!
*the phone reboots automatically if any -kinda More RAM consuming app or game is launched..otherwise it stays okay!*
for installing the boot.img I used this command only
'fastboot flash boot boot.img'.. and it boots up the phone nicely..correct me if im missing any stuff!?!
technically the kernel should kill apps when RAM is critically low to free it.
The graphics thing could be a bug. you could try 'adb bugreport' which should get information from previous reboots (according to google) and posting in CM11 thread.
Any chance you are overclocking? overclocking has side effects like overheating and random reboots.
hussamT said:
technically the kernel should kill apps when RAM is critically low to free it.
The graphics thing could be a bug. you could try 'adb bugreport' which should get information from previous reboots (according to google) and posting in CM11 thread.
Any chance you are overclocking? overclocking has side effects like overheating and random reboots.
Click to expand...
Click to collapse
nope, i haven't overclocked either, but it seems the kernel has smartassv2 featured by the dev! i saw so from an app..n yes i tried overclocking ,underclocking too.. device seemed to produce heat like hell! btw, after that i already reflashed the rom couple of times and even before that the problm of auto-reboot prevailed..
you can also "cat /proc/last_kmsg > /sdcard/mylog.txt" and report it in main cm11 builds thread.
first 'mount /sdcard'