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.
Hope someone might be able to help.
Just got my vega and first thought was to root, backup rom and flash. Im used to doing iit with my desire so thought it would be easy!
so i,m using Visionary to root, first temp then perm. Run titamium backup that should root and backed up a couple of apps no problem. Installed rom back up v3. Back starts by reboot and then sits at android out of the box before i have to switch it off after 10 mins or so. I i still try and flash after this (or before if i miss this stage) with new rom, cant open apps or force close and wifi just says error.
Great device though
Thanks
bRim
Which rom are you trying to flash?
I use the built in applications backup, located in settings/software tool to backup apps, with no problems.
Ive tried the r8 version and one other and ive also used the app backup but wanted to get the whole rom done before a full flash.
I'm on 2.2.1 and tried rooting with visionary and now my phones all messed up ! I hard reset several times and sometimes ill get stuck on a bootloop or it'll go to start up screen and freeze.
I tired flashing stock rom using the PD15IMG.zip method in stock recovery but it wouldn't takesaying no image or wrong image.
Is there any way I can reflash a stock rom ? I've done it on the Vibrant using Odin and the Nexus1 with the passing.zip method but I'm having trouble on the mt4g.
Any help would appreciated ! Thanks in advance .
You don't flash it in the recovery. You flash it in the Hboot.
[sent via Cyanogen powered Android]
Lol I think I phrases that wrong. I did flash the stock zip in hboot,it reads the file and the blue status bar on the side goes up then it checks the image and just goes back to hboot. I double checked to make sure it wasn't named .zip.zip and turned off fastboot in application settings like the rom thread said to do and no go.
After hard resets ill get Android.process.acore not responding and process.com.htcandroid.htcsetupwizard has stopped so some stock files were messed up when I tried to root. Everything was running fine until I tried rooting.
I'm wondering are there any important files that come on the stock sd card ? I formatted,erased my sd card before hard resetting and wonder if that's why I'm getting so many stock android processes stopping or freezing ?
If there are necessary files that come on the sd card where can I find them or should I just go a tmo store and borrow and copy a card lol ?
Hey Guy's could somebody give me some advice here as i'm well and truly stuck with adding ROM's to my wildfire. . .
Right i'll try break this down as easy as i can, i bought my wildfire 3 days ago, and its running 2.2.1, i watched one of the latest video tutorials on how to root using Unrevoked (which i now know doesnt work), I installed HTC Sync to get the drivers, then uninstalled it. I then Added the modded Android USB Drivers. Run Alpharex to change my Hboot, and set to S-Off, Then tried running the latest version of Unrevoked, i got the dreaded "Is your firmware to new" message. . . I've always got debugging mode running and allow 3rd party apps!
I then mentioned this to somebody who told me of a different way around rooting my device so . . .
I then downloaded Gingerbreak.apk, then i got Astro off the Market and run Gingerbreak, my phone restarted and WAYHEY I've now got superuser access!
I got ROM Manager off the Market, then i downloaded Clockwork recovery mod 2.5.0.7, CM 7.03, Gapps 20110115, formatted my SD to fat32, put the zips directy onto the root of the SD card. . .
I made a flash recovery, go to install ROM from SD, phone restarts then i get the "Red Exclamation mark triangle"??? i've tried two different SIGNED versions of CM with no luck with either. I've tried running the Anonimo ROM and yet again i get the same red exclamation mark. . .
I've manually tried running recovery from hboot and yet again i get the same problem. . . .
I'm not doing nothing wrong here am i? As ive watched/read/researched dozens of how to's and followed every step exactly as it says!
I will be watching this post constantly as i'm itching to get rid of this nasty FROYO.
Thank you for your time.
I just had to reboot into recovery from hboot menĂ¹ and selected the zip I put there before (SD root)... If you're trying to istall cm then you don't need to use Rom manager, u can use the usual recovery.
I just tried to istall the latest CM Nightly Builds and 7.1.0 release candidate, I dind't have problems!
EDIT :
Oh dude, it seems you don't have recovery istalled, just follow this tips :
Put the file attached into root of your sd card, then power down your phone, and boot into hboot menu.
let the phone check for a "PC49IMG.zip" file and then press volume up.
after that remove the "PC49IMG.zip" from your sd card and put the rom you want to istall always into root of your sd card, then just istall the rom from there!
Install Clockworkmod Recovery on your NAND Memory. There are 2 ways to achieve this:
1) Using Fastboot: (My preferred method)
http://forum.xda-developers.com/showthread.php?p=14693680
2) PC49IMG
http://forum.xda-developers.com/showthread.php?t=1130044
If you face issues using the Fastboot technique (I haven't tried the other one), let me know, I'll help you sort it out.
WOW!!!!! It's actually doing it!!! You've both got a thanks vote off me but one thing now (sorry) . . . . ive rebooted my phone and its shown up the blue cyogen mod 7 screen with the blue circle, and it spins round a few times then shows the droid on the skateboard again and starts spinning again, its been doing this for way over 10 minutes now, is there something missing? do i have to boot Gapps from recovery off my sd card before i restart?
MC-ARNIE said:
WOW!!!!! It's actually doing it!!! You've both got a thanks vote off me but one thing now (sorry) . . . . ive rebooted my phone and its shown up the blue cyogen mod 7 screen with the blue circle, and it spins round a few times then shows the droid on the skateboard again and starts spinning again, its been doing this for way over 10 minutes now, is there something missing? do i have to boot Gapps from recovery off my sd card before i restart?
Click to expand...
Click to collapse
No, Its not necessary to flash GApps beforehand. What you are getting is a bootloop.
Reflash Cyanogenmod, but, before doing that, make sure you do a wipe. (Factory Reset / Data Wipe Option in Clockworkmod). Also make sure you wipe cache, dalvik cache (Under advanced), and format /system partition (Also under advanced)
After clearing all this, then reflash the CM Zip file and try again.
Thank you kind sir i did these exact steps just after i wrote my last post and i'm now VERY HAPPILY running 2.3.4
Only problem i've come across so far is the vibrate option for calls/texts in any status (silent etc) doesnt work whats a bit of a shame, but with the improvement in my handset i won't complain!
I could get used to this android business
MC-ARNIE said:
Thank you kind sir i did these exact steps just after i wrote my last post and i'm now VERY HAPPILY running 2.3.4
Only problem i've come across so far is the vibrate option for calls/texts in any status (silent etc) doesnt work whats a bit of a shame, but with the improvement in my handset i won't complain!
I could get used to this android business
Click to expand...
Click to collapse
Glad your sorted!
Sent from my HTC Desire using Tapatalk
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.