I have just put Leedroid 2.0 on my DHD and everything was fine but after looking round I decide last night that I would go to 2.3, so I dwnlded it and put it onto my SD card with the md5 file no problems. I then used clockwork mod to wipe my old Rom for a fresh start still no problem. When I went to install the new Rom it kept saying error which had alarm bells ringing in my ear I powered odd and removed the SD card and put the old 2.0 zip file on there and removed the error file and inserted it into the phone. This gave me a flashing Orange light and not able to power on so I removed the battery and waited for ten seconds and put it in and powered up the phone. Now I thought could just install the zip from there but the phone booted up (took ages for first boot but I waited) and followed the on-screen instructions for setting up the phone and then I used titanium backup to reinstall my apps.
The version of leedroid is the same but it boots up differently without the r2d2 sounds and different boot up screens
Not sure what I did seeing as I never installed from the zip file it has installed from somewhere.
I think I will do it again but just wanted any thoughts as to what actually happened with the install and what is the latest leedroid Rom because I can't seem to find it anywhere I look I keep getting different numbered versions.
Thanks
Sent from my Desire HD using XDA App
TheKaptone said:
I have just put Leedroid 2.0 on my DHD and everything was fine but after looking round I decide last night that I would go to 2.3, so I dwnlded it and put it onto my SD card with the md5 file no problems. I then used clockwork mod to wipe my old Rom for a fresh start still no problem. When I went to install the new Rom it kept saying error which had alarm bells ringing in my ear I powered odd and removed the SD card and put the old 2.0 zip file on there and removed the error file and inserted it into the phone. This gave me a flashing Orange light and not able to power on so I removed the battery and waited for ten seconds and put it in and powered up the phone. Now I thought could just install the zip from there but the phone booted up (took ages for first boot but I waited) and followed the on-screen instructions for setting up the phone and then I used titanium backup to reinstall my apps.
The version of leedroid is the same but it boots up differently without the r2d2 sounds and different boot up screens
Not sure what I did seeing as I never installed from the zip file it has installed from somewhere.
I think I will do it again but just wanted any thoughts as to what actually happened with the install and what is the latest leedroid Rom because I can't seem to find it anywhere I look I keep getting different numbered versions.
Thanks
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
If you wiped, and can now boot, you MUST have flashed the zip otherwise you would have nothing to boot into, does phone info not tell you what version of leedroid your running?
Yeah it days Android 2.2.1 and leedroid 2.0.0 which is what I thought I had but it seems a little different
Sent from my Desire HD using XDA App
so what is the latest version of Leedroid and is there a link direct to it
Thanks Again
TheKaptone
TheKaptone said:
so what is the latest version of Leedroid and is there a link direct to it
Thanks Again
TheKaptone
Click to expand...
Click to collapse
Go to the Development thread, it's one of the top ones there called LeeDroid.
First post in that thread has download links.
latest version 2.3 is a beta. yuu should back to 2.2.2 again if there is so much problem!
dont forget,
2.2.2 is based on the current 2.2 version.
2.3.x is based on the leaked 2.3 version.
2.2.2 is great.. use it myself and love it.
havent tried 2.3.x but i would sugest reading the posts to see if there are any bugs ect.
i also had the issue that my boot screen looked stock again.
this happened after messing around with flashing the roms..
after i flashed it again the normal way.. it got back to the fancy boot screen.
dont forget to use clockwork 2.x.x.x not the clockwork 3.x.x.x
thanks for that I have done it again and it is now 2.2.2 and is grrrreat , watching closely the 2.3 thread and nearly ready to make the jump
Related
Apologies for the double post but I'm dying to get my wildfire back working.
Rooted it yesterday with unrevoked, attempted to add the Openfire ROM this morning with everything going fine untill the reboot. I'm now stuck on the white HTC screen and have been for the last hour. Any help would be great, cheers.
did u do nandriod back up first
Sent from my Archos5 using the XDA mobile application powered by Tapatalk
I backed up the stock firmware I already had manually, before it prompted on the flash.
did you do a full wipe before flashing the rom?
No i didn't, thought it would be safer incase something went wrong?
run your restore then I couldn't get it to work either
Sent from my Archos5 using the XDA mobile application powered by Tapatalk
if you did a nandroid backup of your stock rom then you should be fine to wipe, since you did not wipe and flashed the new rom over your stock rom, apps and settings will conflict, therefore not work...
Right I see, I'm currently going through what I'm guessing is the restore....recovery - Nandroid, I'll let you know how I get on.
Thanks again.
Nope I seem to be getting nowhere here, can someone point me in the direction of the restore?
you didn't do nandroid backup did you haha, you'll have to install an RUU file to return to stock rom, or just do a full wipe and flash a new rom like openfire or wildpuzzle.
Where can I find the RUU file and how do I access my SD card? USB won't let me get to it, I'm guessing the phone is in charge mode?
go into recovery - partitons menu - mount sd card (or somthing like that) to open your memory card
Spot on, I'm on downloading an ruu file now, going to load it up with a stock rom then try flashing it again, but wiping it this time.
Infact how do I do a full wipe? I'm after the easiest way to get the phone booting up so I can flash it properly?
Anyone?
I'm still no further than I was three hours ago!
EDIT:
BREAKTHROUGH!!! =D
Restored it to before I flashed it incorrectly. Nearly threw the phone across the room in excitement.
go into clockwork recovery and click the title "wipe data/factory reset" and then flash the ROM you want to use.. to install a ROM:
- "install zip from sdcard"
- "Choose zip from sdcard"
- "click the zipfile"
- "yes"
- "reboot"
and if you want to install RUU dont ask me never done that
Reggie24 said:
Anyone?
I'm still no further than I was three hours ago!
EDIT:
BREAKTHROUGH!!! =D
Restored it to before I flashed it incorrectly. Nearly threw the phone across the room in excitement.
Click to expand...
Click to collapse
How did u restored it .....????
sunny_16977 said:
How did u restored it .....????
Click to expand...
Click to collapse
From the HBOOT screen go to recovery, then nandroid, restore, and to the appropriate time/date.
I've still had no luck with actually flashing the phone though. Back to Android 2.1 for me.
I'm 99% percent sure you have the OC issue some ppl incl myself on here have - try reinstalling openfire if thats what you wanna use - and then go to wildpuzzle thread - dl 0050 and flash it. If i'm correct phone will be fine and use openfire - but will NOT be overclockable. I wish Jacob had my phone or got hold of a phone w that problem...
I had problems with the Wildpuzzle 8.0.11 ROM, it would just sit there (did a ADB logcat on it, but I've lost the actual log... sorry! ) ignoring a duplicate entry (yeah, I did a full wipe . Removed WP and put on the latest OpenFire ROM... omg... what a difference to the stock ROM! Soooo much faster, even before I overclocked it.
I'd say, if you have boot issues with WP give OpenFire a go. Certainly worked a treat on my Wildfire.
This post is only for discussing all issues regarding the use of the Bonsai roms. We can talk here about any version from 1.0.0 to x.x.x
Due to some political issues please do not post any links to the Bonsai website! This thread is just for us users and don't expect the developers of Bonsai to ever visit here.
One last thing >
nor
Yes this try to keep this thread open.
Sent From My Evo Killer!
So is there a way to get a 600mhz step in the kernal for bonsai 4.0 last i heard he was going t put it in back in 3.0.1 but still not there. Or is there an easy way to included it in the kernal page file or something that set cpu uses? Also is there a way to get the voodoo color fix or a tweak that works that will make the brightness lower at the lowest setting for 4.0 becase the brightness on this screen is way to brght at night time. I used to have a tweak like this in syndicate rom for 2.1 it was great. Any info would be great thanks guys.
Sent from my SPH-D700 using XDA App
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
forcelite said:
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
Click to expand...
Click to collapse
Were you using CWM 3.0.0.6 or 3.0.0.5 ?
Sent from my SPH-D700 using Tapatalk
Good question as i was just going to as a question about EXT4 and CW.
The rom manger is version 3.0.1.4
however the CW mod flashed is version 3.0.2.4
It only has 2 to choose from in rom manger, 3.0.2.4 or an older 3.0.1.4
Not sure were people are getting these other versions from.
Force
PS I booted into CW and saw it was v2.5.1.0
am I way off?
abrcrmdl23 said:
So is there a way to get a 600mhz step in the kernal for bonsai 4.0 last i heard he was going t put it in back in 3.0.1 but still not there. Or is there an easy way to included it in the kernal page file or something that set cpu uses? Also is there a way to get the voodoo color fix or a tweak that works that will make the brightness lower at the lowest setting for 4.0 becase the brightness on this screen is way to brght at night time. I used to have a tweak like this in syndicate rom for 2.1 it was great. Any info would be great thanks guys.
Click to expand...
Click to collapse
I can't remember what stepping is on the kernel as we have been beta testing 4.0.1 and have been mainly dealing with a new setCPU governor called interactive. Were also still working on the other governor called smartass as well. I think that the stepping goes directly from 400 to 800, but we are always looking to go faster and with better battery life. I'll bug Randy and Mammon about it.
The sound will be Voodoo version 7, but I don't think the Voodoo color fix is going to make it into 4.0.1. Sorry, but we can't do everything...at least not all at the same time.
forcelite said:
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
Click to expand...
Click to collapse
Did I see a similar post on the Bonsai website earlier today? I just want to verify that you were using CWM 3.0.0.6 as anything else will cause problems like that. Also when you get to these kinds of problems you should attempt a second flash of Bonsai before going to the trouble of a ODIN job. A second flash seems to fix a whole variety of odd kind of problems.
As you can imagine with all the beta testing I do I'm always finding ways to corrupt my phone. Some days I have managed to bork it 3-5 times.
I decided to test out today a 4.0.1 install directly from DI18 > CWM 3.0.0.6 > Bonsai 4.0.1 full rom. It went great with no problems at all and running just fine, so far
I think that is my problem, I am using a the CW that came with the one click unroot.
So I guess I need to do this, even if I am already rooted?
http://forum.xda-developers.com/showthread.php?t=897612&highlight=EXT4
PS
I booted into CW and saw it was v2.5.1.0
bluetooth
I could not get bonsai 3.0.1 or 4.0.0 to pair with my bluetooth headset. Tried pairing on an epic with acs 1.1 and paired fine. Anyone else have a pairing problem?
forcelite said:
Good question as i was just going to as a question about EXT4 and CW.
The rom manger is version 3.0.1.4
however the CW mod flashed is version 3.0.2.4
It only has 2 to choose from in rom manger, 3.0.2.4 or an older 3.0.1.4
Not sure were people are getting these other versions from.
Force
PS I booted into CW and saw it was v2.5.1.0
am I way off?
Click to expand...
Click to collapse
Do not use Rom Manager to be installing the beta CWM files. The correct way is with one of the 1 step CWM tools in the development forum. 3.0.2.4 is half-finished and is very difficult even to navigate through the various menu's. I know this because I tried out that CWM version for some grins one day. It will majorly screw your Epic if your not extremely careful. When DI18 was prevalent Rom Manager worked great to root your phone. When we started the move into the Froyo roms Rom Manager quit working and that is why the 1 click then became more prevalent.
Just follow the directions posted all over the place and Bonsai will install just fine and you will be a happy camper.
I am installing it now after updating to CW3 (from CW2.5) . I think it will come out fine now, I am an idiot and didn't realize the original one click root installed an older version of CW.
Thx All,
Force
forcelite said:
I think that is my problem, I am using a the CW that came with the one click unroot.
So I guess I need to do this, even if I am already rooted?
http://forum.xda-developers.com/showthread.php?t=897612&highlight=EXT4
PS
I booted into CW and saw it was v2.5.1.0
Click to expand...
Click to collapse
The linked one is the correct one for Bonsai version 4.x.x.
olddocwhite said:
I could not get bonsai 3.0.1 or 4.0.0 to pair with my bluetooth headset. Tried pairing on an epic with acs 1.1 and paired fine. Anyone else have a pairing problem?
Click to expand...
Click to collapse
Some people do and some don't I do know that Randy has instituted quite a few bluetooth linux upgrades into 4.0.1 rom. Some people are able to clear the data, but the problem usually reappears. Mattalica76 has the link to a more permanent fix to this problem, give him a PM.
Duplicate... Sorry
forcelite said:
I am installing it now after updating to CW3 (from CW2.5) . I think it will come out fine now, I am an idiot and didn't realize the original one click root installed an older version of CW.
Click to expand...
Click to collapse
Don't beat yourself up as we all have been there. It's a process of learning new skills and a new language. Give yourself a pat on the back for getting through this when 98% of the world would have said screw it or not even tried at all.
Actually it didnt boot this time either, it installed the firs ttime fine, then kept booting after samsung in a loop,
So I went into CW3 and tried to flash bonsai 4.0.01 again and it gave me this error. It is long, however I shortened it, I have the whole error photo copied)
Finding package
Opening package
Install update
Assert failed getprop (“ro.product.device)”)
Sph-700
E:error in /SDcard/bonsai……….
(status 7)
Installation aborted
Top Nurse said:
Don't beat yourself up as we all have been there. It's a process of learning new skills and a new language. Give yourself a pat on the back for getting through this when 98% of the world would have said screw it or not even tried at all.
Click to expand...
Click to collapse
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
forcelite said:
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
Click to expand...
Click to collapse
CWM3 will convert your filesystem to ext4 the first time you boot into it. It won't touch the sdcard so that won't be converted. After CWM is finished with the conversion, do not reboot the phone, you will then flash Bonsai.
forcelite said:
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
Click to expand...
Click to collapse
After flashing the boot script of cwm 3.0.0.6 you then have to power off. Then hold down the camera button, vol down, and power keys at the same time and the EXT4 script will automatically start to format your system. Please keep in mind that it is not formatting the SD card, but only the read only memory of the phone.
After you finished a few beers it will be done and will drop you back to cwm. Do not reboot, but flash bonsai. After bonsai is finished then reboot.
Sent from Bonsai 7.0.3
Hi guys. I seem to have outdone myself and am now stuck with a phone that plain refuses to boot any more. Let me give you some history so you get the full story.
Not long after I got my U8800 (18 months ago, 'ish) I decided to change my ROM to MIUI because I wanted to get rid of Froyo and Huawei were being incredibly slow to update officially. I did this with minimal troubles and ran it for a long time, updating etc. as needed to be done. Then along came ICS ports and I admit it, I had to fiddle once more...
I downloaded Aurora and read up in here on how to get it on my phone. It seemed before I did anything I needed to set my phone back to the defaults I had and this involved installing Froyo then the latest stock ROM for the U8800. I did all this without hassle and then tried to get the ICS on.
I don't know if it was me, bad reading, something built into the new stock ROM or what, but I could not get the ICS ROM on my phone no matter what I tried. It seemed to have issues deciding if it was rooted or not, it said it was but then failed to work when I needed it to, plus CWM Recovery completely failed to work for me and I just kept getting the stock recovery when trying to boot into it. ROM Manager was also being a pain and kept insisting my phone was a U8160 when previously it had worked as a U8800 (I may have flashed to the U8160 and having thought this I assumed this was my mistake).
I tried various methods of getting to my cust_ folders and manually changing the recovery.img but everything I tried ran into the same "is it or isn't it rooted" problem.
At this point I gave up and stayed with the official stock ROM from Huawei for a bit.
Two days ago I decided I couldn't hack the defaults any more, my phone was slower and I missed the MIUI way of doing things. I decided to have another go!
Ok, we are up to date, thanks for reading so far if you have.
I decided to try getting to the recovery.img again by doing the pink screen and connecting to my PC, problem was when I did this nothing ever showed on my PC, so I looked for other methods.
I uninstalled ROM Manager, because it still insisted I had the wrong phone and found the app, Root Explorer, it worked! Wish I'd have found it weeks ago. I instantly had access to the folders I needed and could mount them etc to overwrite/backup my recovery.img and as I was a little worried about the rooting thing again, despite Root Explorer working I though what harm can it do to overwrite the boot.img too. I did both by copying the originals to my SD Card and pasting the new ones that I had previously placed on my SD Card through the USB connection. I used the files recommended here: http://android.modaco.com/topic/340...-and-then-some-for-the-huawei-u8800-ideos-x5/ and here: http://forum.xda-developers.com/showthread.php?p=14870348
I rebooted the phone and again failed to get into CWM Recovery, just the default Android one.
I then hunted down another recovery and found this: http://www.androidxpert.com/2011/08...k-work-mod-recovery-on-huawei-u8800-ideos-x5/
It worked! I could finally get into CWM Recovery and figured I was home free.
Not so
I then downloaded the same stockwell MIUI I had used previously as I knew that worked, his latest stable version, and dropped the zip on my SD Card. Went to install it and found that CWM Recovery refused to mount my SD Card (16 gig sandisc). Tried a couple more times because I had issues with this card before and then the card ended up corrupted or something because it just refused to work now on anything I had. This was fairly major because I had backed up to this SD Card and forgot to take the backup off and into my PC for safer storage... I know... I do have the back up of recovery and boot.img though on my PC.
It was at this point I noticed I had a boot loop but could still get into CWM Recovery.
Not panicking too much, I tried my old 4gig SD Card, it mounted! I copied the MIUI Rom across to this card, booted into recovery and selected it. It stated it was installing etc but seemed to go pretty quickly. It said it was done so I rebooted as is the norm. Boot Loop. Damnit! Tried this a couple more times, made sure I once again wiped cache, dalvik etc, all of the things it states to do on the ultimate guides etc. Nothing.
Again, still not panicking I thought, fine, I will go back to stock rom. Downloaded the correct one, dropped dload into root, booted using vol + and - and up comes the unpacking screen. Trouble is it refuses to unpack. I quickly look on the net and find that some say if you take the battery out and connect just using the USB it will install it that way, maybe it does for them but it doesn't for me, it just boot loops again.
I am now at my wits end.
I have the feeling its something to do with my changing of the boot.img and I have the original should it be that but I cannot access the insides of my phone through Windows to change anything, plus of course I can't boot the phone due to the loop to change it back using Root Explorer (otherwise it would work anyway).
Is there anything you guys can help me with?
I can install Linux if needed, I read that it lets you view the phones file system better compared to Windows and with my slight knowledge of Linux Id quite expect this but even so, I am not sure what to do.
Any advice/solutions are extremely welcome.
Sorry for the long post, figured I should give as much info as possible.
So what was the latest Huawei official firmware you had on your phone?
What version of CWM are you trying to use?
What version of the huawei official rom did you have on the phone when you tried to install aurora?
What was the last huawei stock rom you tried to install?
Try and get a 2.2 froyo stock rom and flash it using the vol+and- method. This should hopefully get your pink screen back and access to recovery and boot.img. You can then use any recovery earlier then 5.0.2.6 and install stockwells miui.
It sounds like you have a Gingerbread based official rom flashed which you would have needed to flash aurora and are dropping bits into it like boot.img, roms and recoveries which are for froyo.
If this is the case and you can still get into recovery, I would try flash another rom like sbasils miui or wipe everything and format /system and then flash aurora again.
Ok, not sure what changed but, I figured whilst I wait for a reply I may as well keep playing and try to fix it myself still. So I stick my battery back in, was out all night, plug it in the USB as I wasn't sure what juice it had left and turn it on with vol + and - down for that one last try at the default install.
It starts unpacking!
I have no idea what changed, I did nothing different bar having left the battery out all night. Can it have had something in the residual memory?
Anyway, short version. Installed the default froyo, updated to the beta gingerbread (stock and latest).
Back up everything to internal storage this time, just incase and went to superclick to see if I could root it again, it did so. Used Root Explorer to copy CWM Recovery.img over, backed up it all again using CWM to internal, rebooted, worked.
At this point I got silly again and having it all backed up a few ways now decided to try Aurora again, 2.4 this time. It works.
Again, no idea what changed but its going again and after an initial mess with the SC Card again, that works too now.
Sorry to have wasted any ones time with this, though I still really appreciate the reply even if it seems to have fixed itself.
I just wish I was sure what fixed it so It could help others who have the same issue, unfortunately I don't
great stuff, seems upgrades are just a bit hit and miss on this phone. glad it all worked out.
Ok.. so.
I had a not-working clockwork mod, and like an idiot I used the rom manager via android to flash a new rom. So - that rom is stuck in its boot up logo over and over (team kang). And isn't moving despite waiting 10 minutes, and my clockwork mod is non functional. I can see the options in CMW but if I click one of them - I dont get the options to chose a zip/it does reboot. It simply gives me the hat with the refresh logo and no options. So CWM is not functional.
Fastboot boots, but recovery sends me to non functional CWM.
S = off, and the phone is/was rooted.
Any advise?
I hope someone is awake... lol
Try to use adb/fastboot to flash 4ext recovery. Or a new cwm recovery. You really need a functioning recovery.
Sent from my HTC GLACIER using xda premium
Just sayin.. 4ext is a better recovery. However, if you prefer cwm, that is up to you. But if you can use adb to flash recovery, please do it, then from hboot go into recovery and flash a known working Rom...
Sent from my HTC GLACIER using xda premium
So your saying volume down while power on, boot up adb on the computer/fastboot on the phone and I can somehow push a 4ext to the phone? I'll give it a try but I'm lost at the moment.
Closest I came up with was downloading the stock rom/putting it on SD card and loading it up that way.
I'll go back to DEV and check into how to flash it, but I was under the impression you had to have a working rom.
...are you making selections in recovery using the trackpad?
There is no trackpad? Volume up and down.
I just flashed 2 versions of CWM and finally got options with the touch version - then of course I lost MY sd card somewhere? Which is such a joy because I'll never find it. So I am now going to load up a rom on the SD card then install it.
Ok, got the rom installed, for my personal SD card - the other phone is booting up now, if it doesn't work atleast I can mount the SD card through CMW and such. TY original poster, I didn't actually realize you could flash files directly from the computer to the phone.
This all started when I rooted this phone because it was having battery issues/wasn't running right, then it needed to update but wouldn't because CWM was installed - so I tried to put a different rom on it but that didn't work.
YES!!!! It has booted into android just now. Score.
TY posters.
nimkiel said:
There is no trackpad? Volume up and down.
I just flashed 2 versions of CWM and finally got options with the touch version - then of course I lost MY sd card somewhere? Which is such a joy because I'll never find it. So I am now going to load up a rom on the SD card then install it.
Ok, got the rom installed, for my personal SD card - the other phone is booting up now, if it doesn't work atleast I can mount the SD card through CMW and such. TY original poster, I didn't actually realize you could flash files directly from the computer to the phone.
This all started when I rooted this phone because it was having battery issues/wasn't running right, then it needed to update but wouldn't because CWM was installed - so I tried to put a different rom on it but that didn't work.
YES!!!! It has booted into android just now. Score.
TY posters.
Click to expand...
Click to collapse
no trackpad? do you have the Mytouch 4G?
the trackpad is the square like button in the bottom middle of the phone...
well anyway, i'm glad you figured it out and got it working.
nimkiel said:
There is no trackpad? Volume up and down.
I just flashed 2 versions of CWM and finally got options with the touch version - then of course I lost MY sd card somewhere? Which is such a joy because I'll never find it. So I am now going to load up a rom on the SD card then install it.
Ok, got the rom installed, for my personal SD card - the other phone is booting up now, if it doesn't work atleast I can mount the SD card through CMW and such. TY original poster, I didn't actually realize you could flash files directly from the computer to the phone.
This all started when I rooted this phone because it was having battery issues/wasn't running right, then it needed to update but wouldn't because CWM was installed - so I tried to put a different rom on it but that didn't work.
YES!!!! It has booted into android just now. Score.
TY posters.
Click to expand...
Click to collapse
Cmon...not even a clik on the thanks button? Those are like battle scars! I'm just kidding..glad it worked out for you. It hurts me to hear about a bricked mt4g. They are a dying breed...
Sent from my HTC GLACIER using xda premium
I actually didn't know there was a like button as this was one of my first posts really. But if you want an update, I flashed it through ADB and got a working bootloader then loaded ICS which completely didn't work.
This phone is for my mom's so I reflashed it to that Virtuous Unity rom/shes now complaining of some battery drain. I didn't install setcpu because they have something else running I saw? But maybe it needs to be setup? Either way I'll just install setcpu next time I see her.
Oh, as for the trackpad... *cough*. I've held the phones many times (hundreds), but never actually realized there was a trackpad on it. My mom used it in front of me shortly after I fixed her phone..
Getting more than a day out of a Sense 4 rom with decent use. Releasing this to the public in a couple days as INDIAN MADNESS, give it a shot
I did everything needed. When i use de DFT flasher i finally got a working image file (The DFT desire rom). But i have no CWM available anymore.. When i converted the IMG files from the DFT install to upgrade.zip and installed it. It worked, well the install did. But as soon as i run the phone i get errors. The same kind i got when i started useing the eclipse mod (3.52). Which is weird. Since i cannot locate the problem. why do all these errors keep comming up.
Other then that i was kinda happy with the stock desire rom which runs completely from the HD2 internal memory, but the i tried makeing changes in the system folder and it seems i have no superuser abilities. So why is this? Or do i need to root this standard desire rom and if so. How does that work cause i imagine its different from the way you would root a untouched phone. Weird enough it does show a superuser icons in my list of programs.
Im almost there i need to figure out these minor tweaks to fully enjoy all those nice roms out there.
Hope anyone is out there to get a light shining on it
That's a really old rom and flash method,,thereare no other roms that work that way.it was the original proof of concept .
Find any other rom,findout what popartition size it requires, use the nand toolkit to set that size, which will apply cwm too, thenflash the rom from within cwm.
Here is the problem every flash I do with a rom. I end up getting errors after the boot. I have a 8gb sd card. Formatted to 2048 ext 4 and 128 swap (useing cwm).
For now I'm running the DFT Rom. I edited the install and added the cwm img aswell. So now o can boot CWM to even though useing the DFT Rom. I used CWM to root the DFT Rom. To be honest for now it will do. But I'd love to have some more eye candy. But I can get the toms installed. After installing CWM 3 TIMES with different sizes and useing the CWM to install 3 different roms I get the same error on every install. I assume something goes wrong accessing the ext4 partition on the sd card. But I have no idea.
I suppose there is no 400mb Rom with sense 3 or 3.5 that runs without sd ?
Sent from my HTC One X using xda app-developers app
You say that you get the same error each time, but you haven't actually mentioned the error message (as far as I can see). What is the error that you get?
Its the same kind of errors I get from installing the eclipse Rom.
Com.xxxxxxx.xxxxx
Errors. That they stopped for some reason. Xxxxx is Google and phone and all kinds of programs. I just don't understand why flashing with CWM keeps going wrong. But I updated a couple of things and installed su.2.xxxxx.signed.zip and a couple of changes o wrote. With CWM and that all works fine.
I just think that for some reason when booting the first time all those Roma that need ext4 on sd. For some reason can't find them.
Sent from my HTC One X using xda app-developers app