Help please - stupid mistake!! - Legend General

Right, this is gonna seem really stupid, but bear with me please! I installed Blayo's ROM a few weeks ago, and enabled A2SD. I've been using CM6.1 for a couple of days, but today I reverted back to Blayo's ROM using a backup I created in ROM Manager. Stupidly, I flashed Darktremor A2SD. I really don't know why I did this. All my apps (including the built in ones) no longer worked (no surprise there). I did a factory reset, and everything seemed fine at first. However, whenever I go to enable Blayo's A2SD it enables Darktremor instead, and I can't flash Clockworkmod recovery anymore! My phone is functional so it's not quite as bad as a total brick. I've reinstalled ROM Manager a couple of times, but this didn't fix it. I can't even get into recovery mode using the computer!
Any help would be much appreciated.

*PS - can you unroot the HTC Legend without booting into recovery? If you can I'll use this as a last resort in a few days if all else fails as the main problem seems to be that I can't boot into recovery.

OK, sorry everyone - I created this thread without thinking properly as I panicked at the thought of wrecking my phone. I hadn't realised you could boot into clockworkmod recovery using vol down + power, vol up + power etc, so I THINK my ROM is being restored from 2 days ago as I backed it up. Fingers crossed!!!
EDIT: Yep, I'm back on Blayo's ROM as I left it 2 days ago. Sorry for this pointless thread - I'll be more careful in the future though as this was a stupid thing to do!

Related

[Q] Can't boot... have been meticulous... Help please?

This may "wreak of non-search" and I am sorry if it does. While I have searched, the overall panic that one experiences when you suspect a brick and cannot afford to have a brick.... (that, plus a friend purchased this Glacier for me to help me get back on my feet with respect to career/employment, etc., so a good amount of guilt is thrown into this mix)... all prevents me from rationally and methodically searching thread after thread to figure out why I am having the problem I am having.
I will be as precise as possible.
1. Back in Feb., I perm rooted with visionary... then about 2 weeks later, I read that this root was not true radio s=off perm root, so I used adb and the scripts to perm root again--using the wiki as a guide. Saved a copy of the partition 7 bin on my laptop as an added precaution. Also, BTW, I never flashed the engineering HBOOT. It didn't seem essential to do so... PLUS, in almost every guide it warned that this was the most likely chance for one to f*ck up and brick, so in the interest of erring on the side of caution, I skipped that.
2. I kept stock ROM for several weeks after that... just enjoying root and freezing bloatware with Ti, and doing other root-enabled mods... nothing too involved.
3. About 1 week ago, I finally decided to flash my ROM. I had Rom Manager (paid version), and had flashed ClockworkMod Recovery 3.0.0.5. Further, as an FYI, I had/have numerous nandroid backups on the SD, plus several Ti backups of apps/data... even sync'd this with dropbox, so I can access those now (which are not of any help obviously).
4. I first flashed a CM7 nightly build--wiped data and cache, and as far as I know followed the guides precisely. All was well...new ROM worked alright... some bugs, but it was nice to have the new features, etc.. And of course the mental gratification of having 2.3.3 (GB) instead of 2.2.1 (boring old froyo). I updated the nightly maybe 2 times... in each case, I simply flashed without backing up those ROMS or wiping data/cache as they didn't seem necessary, plus I still had all my stock rom nandroid backups on the SD.
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Since I cannot get into the phone... I am of course panicked... I have ADB on my laptop if needed, but I really am at a loss as to why this happened, and what I can do at this point....
Please, please advise. My utmost appreciation and sincerest gratitude in advance for any assistance.
Thank you!!!
syntropic
syntropic said:
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Click to expand...
Click to collapse
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
should come up to a white screen.
take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Sent from my HTC Glacier using XDA App
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
Click to expand...
Click to collapse
No... that is what I meant when I said tried to "boot into recovery". And I got the 3 vibrate alerts and a blank screen, and nothing........
take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Click to expand...
Click to collapse
Will do... Thank you. DO you have any idea of where I f*cked up here??
Could be a number of things. Like wipe didn't go through completely , bad download, or just random crap out like a few others. Even flashing with the wrong cwr version can less to your issues. Lol like I said could be a number of things. Sorry I couldn't be more helpful.
Sent from my HTC Glacier using XDA App
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Sent from my HTC Glacier using XDA App
syntropic said:
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
Click to expand...
Click to collapse
What recovery are you using? 3.0.0.5? and you're trying to flash a 2.2 ROM. Thats where the problem lies. See my post regarding this. It's in my signature, the green one.
I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Click to expand...
Click to collapse
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
EDIT: MUSTKll20... Well, you were right... This is not ROM specific. I tried Re-Flashing RC3, which previously worked fine. Now, since I have CWModRec 3.0.0.5, I need to use a 2.3 ROM.... So I thought I would start with this idea. So, I guess, I need to get whatever is corrupt deleted... So my only question thus remains: How do I wipe everything except the SD from within CWR?
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
syntropic said:
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
Click to expand...
Click to collapse
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
and android phone have a method of using a section of the SD card for their memory banks. I'm not really sure how it works either, but it does. You can wipe the internal w/o wiping the SDcard.
Wiping the phone from with in the recovery image will not touch the SDcard, it will only wipe the internal. You can format the SD card from the Recovery Image, but i'll leave that dog sleep so we do not it accidentally.
last little clean-up question.
Sorry to bump this... last LAST question...
Mustkll20: I realized that you were correct to suggest to wipe everything except the SD... Something is corrupt.
But I am not real sure exactly how to wipe EVERYTHING except the SD, from within CW recovery... Since that is the only mode I have available to me. Once I wipe, I will reinstall CM RC3, then update Clockworkmod Recovery to 3.0.0.6, and then try and download RC4 again using another method, and re-flashing.
I would trial and error this, but do not want to wipe the SD.
Thanks guys... seriously.
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
Click to expand...
Click to collapse
I didn't see your reply... ummm. and I do need to wipe.. Because I have tried to re-flash both RC3 and RC4, and I get what must be a "bootloop": During the CM splash, it stops and then reboots---over and over. It never did that before.... so my problem is something else...
I don't know what else there is besides the SD and the ROM, but whatever it is, I need to delete it. So should I do a factory reset???
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
lowandbehold said:
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
Click to expand...
Click to collapse
Yep... I know the thread is not for thrillseekers (i.e., its boring), but I mention that I discovered this phenomenon... so I really wasn't in all that bad a spot to begin with.
I still need to figure out how to fix my current problem.... all CM RCs (I can only flash 2.3 ROMs because of CW 3.0.0.5) go into what I guess is a bootloop. In other words, they do not ever boot, just crash and restart. And the RC3 ROM I used worked fine before this... so something else is causing this problem. I need to wipe everything I guess, but I just don't know how... without touching the SD card and from within Clockwork Recovery.
Ok. Go into recovery.
1. Wipe data/factory reset
2. wipe cache partition
Both of these are on the main screen.
Go to advanced
3. Wipe Davlik Cache
Go back to main screen
Go into mounts and storage
4. format boot
5. format system
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
lowandbehold said:
Ok. Go into recovery.
{...}
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
Click to expand...
Click to collapse
Thank you for the concise and thorough response!!!!!!! Id thank you, but have used up my allotment. get ya tommorow!!
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
syntropic said:
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
Click to expand...
Click to collapse
You can thank the Google c&d order for that. Go to cyanogenmod.com. there is a link there for the gapps zip.
Sent from my HTC Glacier using XDA App
OK... I thoght Gapps.zip was just Google Docs. Luckily, I had that on my SD card from one of my many ROM downloads. I see why they had to make it separate.
But I am installing it, and everything is great... And I learned a lot too... Which can only mean trouble.
Thanks!

[Q] tabbonay cookbook update issue

running taboonay 2 and villian. Tried to update using the taboonay cookbook to get a new boot animation and home button. Boot animation works great' but when i push the home button it says system ui stopped unexpectedly. I really like the new buttons though. Tried installing again to no avail. How do i fix it and keep the buttons?
bitterevp said:
running taboonay 2 and villian. Tried to update using the taboonay cookbook to get a new boot animation and home button. Boot animation works great' but when i push the home button it says system ui stopped unexpectedly. I really like the new buttons though. Tried installing again to no avail. How do i fix it and keep the buttons?
Click to expand...
Click to collapse
Check the taboonay thread, vache stated he fixed the problem. Kitchen has been fixed, just re-cook what you want and flash
Sent from my A500 using XDA Premium App
Yes it's fixed indeed.
Just cook again ;-)
I'm about to give up hope on root. I think I messed something up with my lack of experience. Here's the story.
Rooted and everything went well. Installed clockwork and taboonay 2 with villian and everything was going great. Then I tried the cookbook thing on taboonay. And got a system UI failure constantly. So I decided I had made a mess of my sdcards trying to figure things out. So I was going to reset everything back to factory, to include clockwork, and start over. I used clockwork to restore things back to before I put on taboonay and villian. Then, without thinking I unrooted the tab before changing clockwork back. I moved my backups from clockwork to my computer and formatted my sd cards. Now the tab won't reroot. I tried to move my backup files back to path sdcard/clockwork/backups but clockwork says it can't find them. How do I get clockwork to find my backup files? And if I restore to a point the tab was rooted, will it again be rooted? How do I reset everything back to factory and start over?
think I figured it out. Rooted again anyway. Is there an easy way to reset everything at one time? Including recovery?
As far as I know the answer is "NO".
You may restore kernel and OS with a nand backup/retore and you can flash the recovery in tree ways : adb, zip, Acer Recovery app but not all at the same time.
First thing to do :
install the recovery
then flash kernel and rom from sdcard or you restore a nand backup.
Your clockwork backups should work if you put them back in the /clockworkmod directory of the external SD card. Did you pay attention to the directories structure ?
For Thor recovery, the path you mentioned is wrong to me.
On the external sd it should be :
/clockworkmod /backup/[date of backup]/*
The [date of backup] is like : 2011-08-26.20.00.12
(date and time)
id pay for an app that did it if anyone has any ideas.... OK. I got clockwork off. I'm going to unroot again and reset the whole thing again and start over.
I 've edited my previous post, will this help you ?
yes, very helpful. Got everything put back together, and even got the mods from taboonay cookbook working. You all are awesome. Learned more from xda in two days than two years of college. Ofcourse, that probably says something about my effort in college. Ive got another question though. Think im going tonstart a new thread for it. Ive got adfree on my tab. Every time it blocks an ad it puts the little green android picture in where the ad should be. Wouldnt it be cool if you could personalize that pocture that pops up? Is that possible?

[MIUI] CWM problems.

I made the switch from CM7 (froyo kernel) to MIUI Gingerbread a few days ago.
The "cool factor" on my phone has definitely improved. MIUI is sweet! I've no idea why I held my nose up to it for so long.
Anyway.
It seems The DXC 1.9.23 MIUI that I flashed seems to have automatically updated me to CWM 5.0.2.0.
Bummer. My understanding is these backups aren't compatible with 2.5.0.7?
I THINK that may have something to do with my problem...maybe.
I can't seem to get the "Power Menu" to reboot me into CWM.
I wanted to flash my old BootAnimation back on now that I've decided to stick with MIUI.
Holding the power button and selecting Reboot into CWM brought up an expected SU dialog.
I accepted. I'll attach a screenshot of the package...as it just seems funny to me.
Nothing happens.
No reboot. Nothing.
All the other options work.
Hotboot...bootloader...stock recovery...reboot...
https://lh3.googleusercontent.com/-v...001_063054.jpg
Also, that file on my SD card that it's referencing to doesn't seem to exist.
But I've no idea if that is normal or not.
=] <----Noob.
Rebooting into CWM via ROM manager works fine, however. So I'm confused.
Any ideas?
Hey Jubakuba! I too recently installed MIUI on my Droid X over the Gingerbread kernel. After searching through multiple forums and posting all my troubles, I've come to the conclusion that MIUI and CWM don't play so nicely together. Apparently you must use ROM Manager for all flashing, backups, and recoveries. I was using Droid2Bootstrapper and it caused my phone to factory reset every time, the result being a loss of any settings I had on MIUI (it looked like I just flashed it), Torch not working at all, themes not working, and a factory reset on every subsequent reboot. Try using ROM Manager for all your backup/flashing needs. I'm putting MIUI back on my phone as we speak and I'll be testing ROM Manager out. If you need me to post my results, I will. Good luck!
Sometimes you have to reflash CWM after installing a new ROM. Do it through ROM manager and see if that helps.

Boot Loop and my efforts to fix it, all failed. Help?

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.

Possibly bricked.

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

Categories

Resources