Related
Update 20111117: Updated .zip file to Adobe Flash 11.1 and AIR 3.1.
Update 20111020: Updated .zip file to reinstall Flash and AIR, previous version didn't properly fix AIR.
Steps I used to update Adobe Flash (to version 11.0) and AIR (version 3.0) so it doesn't update automatically and thus get me back into the boot loop cycle (again):
Go to Titanium Backup ( Pro )
You need to uninstall with this since these are system apps
Buy a Pro key and keep it on your SD card root, since this app will save your bacon
Uninstall Adobe AIR and Adobe Flash Player from Titanium Backup
It will warn you that you are uninstalling a system app, that's OK
I think that is why the update through Market isn't working
Open Market, Install Adobe Air (3.1.0.488 as of this post) and Adobe Flash Player (version 11.1 11.1.102.59 as of this post)
Nook seems to be working after several reboots. Also, note that Adobe updated their apps. After following the procedure above, I was able to update via Market without any problems with bootlooping.
Obviously, the above steps only work BEFORE Adobe gets auto-updated and you get in the boot loop cycle. If you are already in the boot loop cycle, download this file (Updated link, should work better this time):
FlashPlayer11.1_AIR3.1_Update_Fix_20111117
and install it using a ClockworkMod Recovery SD card.
Get a ClockworkMod Recovery SD card
http://forum.xda-developers.com/showthread.php?p=11987469
Put the zip from the above post on the SD card
Reboot your Nook with the SD card inserted
Install from Zip, Select zip from SD card, select the flash update
This basically will uninstall flash and air as system apps and install as a user apps. This is based on the zip from GMPOWER which updated flash to 10.3, which worked for some but not others, perhaps because it didn't touch Air:
http://forum.xda-developers.com/showpost.php?p=16526691&postcount=7
Also note, I have been through several cycles of restoring backups, restoring to factory, re-rooting, etc. this last week, so I was getting very annoyed and cautious. I think I was able narrow it down to just the Adobe updates causing my problems. I have been able to update ROM Manager, Superuser, and just about everything else with updates; and besides the Adobe updates, everthing worked, and I don't currently have a boot loop problem.
Note, I didn't update Superuser or ROM Manager until after I applied the above updates to Flash and AIR. After several reboots, my Nook is still working fine.
For those of you who are still having trouble getting your Nook back, and the attached zip doesn't work for you, you can do the following. Using the instructions on this site, I got my Nook back up and running to factory new condition:
http://mrm3.net/nook-color-recover-any-bricked-device/
(Quick method at top, not older methods below; instructions slimmed down from several posts here at XDA, updated for stock 1.2) also here on XDA:
http://forum.xda-developers.com/showthread.php?t=914690 (original restore to stock post)
http://forum.xda-developers.com/showthread.php?t=1050520 (update for stock rom 1.2)
Then, I registered my Nook (again).
At this point, I could have tried to update to 1.3, but my patience was a bit low, so I didn't go for it. If you do, be sure to follow the appropriate ManualNooter instructions here:
http://forum.xda-developers.com/showthread.php?t=1054027
Since I was still on Stock 1.2, I rooted using ManualNooter 4.6.16
(while in CMR, after running ManualNooter, I also applied update-Froyo1.2-dalingrin-OC-emmc-090111.zip, and that seemed to work without a hitch)
Then I reinstalled all the other apps I wanted on my Nook,
=== BUT DID NOT YET UPDATE ADOBE FLASH OR AIR ===
Flashed ClockworkMod Recovery, updated a lot of my apps using Market and Amazon Appstore, restored data and other apps from Titanium Backup,
Then I made a full backup of my Nook using CMR. (still booting normal, running fast and clean)
After confirming my Nook was as I wanted it, and that I had a good backup, I did the steps at the top of this post to update Adobe Flash and AIR.
After confirming that was working, and getting another backup on my SD. I then did the updates to ROM Manager and Superuser. It seemed like those updates happened at the same time as the boot loop, so I was cautious. My Nook is still working well without boot loops as of yet.
Results:
Kernel: Stock 1.2
Rooted with: ManualNooter 4.6.16
Additional Mods:
update-Froyo1.2-dalingrin-OC-emmc-090111.zip,
ClockworkMod Recovery 3.2.0.1,
ROM Manager 4.5.0.1, Titanium Backup 4.5.2,
Adobe Flash 11.1, Adobe AIR 3.1 (uninstalled system app, reinstalled via Market, updated via Market)
[Update Zip] CMR zip to update Flash Player and Air
I updated the original post with a link to the zip to fix the FlashPlayer and Air apps. I had intended to post it here, but since I'm new, I can't link externally in a reply.
Please let me know if there are any problems with the zip and I will get it updated. It worked on my Nook.
I updated the zip file 20111020 to fix a problem with the AIR reinstall.
Wow, thank you so much for this! I wish I had known this on the weekend when I was gong crazy trying to figure out why I was getting bootloops over and over. I can't seem to give you thanks though (probably because I never post, just lurk).
So far I haven't done the uninstall/re-install with TB. I am just making sure my Adobe air and Flash don't update, and when Air did I went into Nook Color Tools and uninstalled the update to set it back to what it was originally. That worked but it is a pain if it keeps happening. I will try the TB to uninsall the programs.
I too did a update on ROM Manager and Superuser (and a binary update), and all is still well. No bootloops. I hold my breath though every time my NC gets to the "color" part until the N appears and it all disolves.
thanks for this!!! this was really getting very frustrating.
Well while I would like to report that the flash fix worked, it didn't. It was already on the boot loop so I installed the update with a flashed SD card and nothing. Still stuck in a boot loop. At this point I am just about ready to give up on this device being a fully functional tablet.
Thanks for this information. My nc is currently in a bootloop and won't load CWR. It shuts off before getting to that point (my bootloop is adobe air related). None of the restore to stock via SD card have worked for me. I'm now looking at ADB options, the post you referenced with the fix has some instructions for that. Did you use the ADB or the SD card instructions? I was actually rooted with CM7 before the bootloop.
Thanks,
shy guy1 said:
Well while I would like to report that the flash fix worked, it didn't. It was already on the boot loop so I installed the update with a flashed SD card and nothing. Still stuck in a boot loop. At this point I am just about ready to give up on this device being a fully functional tablet.
Click to expand...
Click to collapse
I realized that my zip was not working to uninstall and reinstall Air properly. Try the updated zip file in the post.
shelly29 said:
Did you use the ADB or the SD card instructions?
Click to expand...
Click to collapse
I used the SD card instructions. Unless you have done something strange to your nook (not sure what), it should always boot from the SD card first, so you should never have problems booting into CMR from an SD card.
If the link in the original post doesn't work for you to get a CMR SD card, try the instructions here:
http://mrm3.net/nook-color-updated-clockwork-recovery-bootable-sd/
If you have a newer Nook, you may need to repartition your Nook's internal memory and use CMR version 3.2.0.1. See details here (this guy just condenses the instructions you can find on various posts on XDA, and tries to keep it up-to-date)
http://mrm3.net/nook-color-how-to-blue-dot-nook-color/
Also note that I updated the zip file in the post to correctly uninstall and reinstall Flash. I re=bootlooped my nook, and after applying the new zip, my nook was working.
Just an update....
I wanted to let U guys know that I had updated Adobe Flash, Air and Super Users and this has worked for me. I also went to double check the versions of both Flash an Air and they are the newest versions!? I still went to uncheck the "Update Automatically" setting in the market for them both just in case for future updates for the time being. Back up and Running! Thanks Again to ALL involved who put contributions to this
This may have worked for me
I tried the updated fix posted here, and the Nook booted properly. Thank you for this fix; I hope it continues to work for me.
I will have to locate the automated back up mentioned here (Titanium), and I will see how this works. I had been leaving my Nook on at all times to avoid the reboot until I turned it off yesterday, forgetting that I did not want to do that.
Awesome post.
So...after all this is said and done and I manage to get a restore image to load and actually boot, now the library doesn't sync and the shop won't load and I get error messages such as " internal error exception executing the command ". It is like the B&N servers are confused. Any ideas about that?
I'm having the boot loop issue and neither the zip nor the 1.2 restore work to get past it. Does anyone have any ideas?
Thanks!!!! You are my new best friend. XD I ended up reflashing several times before I found this post. Followed the instructions and my Nook is happily running Android again without reinstalling (again!). I thank you. My Nook thanks you. And the Angry Birds who would have had to start from scratch thank you.
Thank you! It appears to work now. I've restarted a few times with success!
Took me about an hour to find this thead. I knew there would be an easier fix than starting from scratch. The zip worked on my rooted 1.2
Thanks! Keep up the good work
Thanks! That worked for me.
Stagnation1 said:
I'm having the boot loop issue and neither the zip nor the 1.2 restore work to get past it. Does anyone have any ideas?
Click to expand...
Click to collapse
From my previous searches, it seems the boot loop is usually caused by either an incompatible installation of Adobe flash, or an incompatible kernel (central part of the ROM). Hopefully the OP zip will fix the first, but I'm not sure of another way to fix the second, other than reflashing and rerooting. How far in the reflash/reroot process do you get before it boot loops again?
mastigia said:
So...after all this is said and done and I manage to get a restore image to load and actually boot, now the library doesn't sync and the shop won't load and I get error messages such as " internal error exception executing the command ". It is like the B&N servers are confused. Any ideas about that?
Click to expand...
Click to collapse
Hmm, haven't seen that error. I'm not sure whether its related to the same problem. It sounds like you might need to re-register your nook with B&N. I'm not sure if you can do this without restoring to stock. Not much help, sorry.
I can't post a reply to this ([NC][1.2][1.3] ManualNooter 4.6.16) thread yet - Still new to these forums... I was one of the many in that thread who had installed ManualNooter 4.6.16 on Nook Stock 1.3 only to end up with a boot loop.
Wish I had found this thread last week - would have saved me a lot of headaches!
It's okay though - every boot loop is another opportunity to learn something new.
Thanks much for the easy walkthrough and I hope others find their way here too.
Just saw another new update for Flash & Air .. released yesterday I believe. Has anyone try them yet ? Just don't want to was my time getting into a boot loop again by updating it.
--
hey i just attempted to root my wife's nook color, 1.3, using this method http://forum.xda-developers.com/showthread.php?t=1054027
i have made the boot disk and pushed both nooter zips to disk, cwm comes up and it runs both zips just fine, ive tried both one after other ten reboot, reboot in between, wipe dalvik and the run but i always get stuck in the boot loop
can anyone tell me what im doing wrong here
and the plot thickens... so i did the 8 failed manual reset, and rebooted to stock, repeated process.. im out of bootloop but it appears the touch screen doesnt work anymore???
yeah so no matter how many times i 8 fail reset still no touch screen, all other buttons work, tried reinstalling clockwork and nothing...i bought the insurance, do i need to run it over cause im outta ideas, my first thought was ui was missing file but it should go back if i reset shouldnt it???
just shoot me..please
ok back to stock, re root, boot loop again, re stock , cm7 (update-cm-7.1.0-encore-signed) + gapps (gapps-gb-20110307-signed) and now application setup wizard has stopped unexpectedly.....stuck...thoughts? please am i over thinking/looking something
day two...
i created sd boot img with cwm 3.2.08, im seeing that i need to use cwm 3.2.01 in a few places.. when i get the file from clockwork (recovery-clockwork-3.2.0.1-encore) and try to write the image to the sd card something is wrong, its not a format that the windows recognizes and so i cant add zips to it and i get nothing in the nook. ive tried to reformat from the pc and in an old android phone i have but its always the same when i try to write to sd , is this the wrong image, can i find it somewhere else
i am using same 8gb sd card i made first boot disk out of, do i need to use a new one??
i got it to work i have good cwm 3.2.01 on nook...
stock + root?
ok it seems that cwm 3.2.0.8 was definitely my problem, i switched to recovery-clockwork-3.2.0.1-encore which i got from http://tinyw.in/0Vw
problem remains that when i flash man nooter 18 then 16 i get nothing, I was stuck on "n" load screen not even a boot loop
i then pushed cm7 again and i am operating as a full android tablet, i want the stock nook image with gapps can anyone help.. im leaving be till i get a answer, didnt want to update to 1.4 or downgrade to 1.2 havent seen a stock img of 1.3 anywhere
Hi All,
I am new here and this is my first post. But i have been reading this forum for quite sometime and know that u guys are now my final stone. I am a proud owner of a Motorola Defy. And I am having this strange behavior, which is effectively rendered the phone almost useless. The phone is acting like its got a restore point in itself, and every time i restart.. it gets back to that point in time.
This includes app installs, uninstalls, stuff placed in system through adb push, theme, everything in the OS. I tried installing a different ROm through clockworkmod, but its not taking effect. Its saying install success but as soon as it restarts, its going back to the old ROM. (takes time to load, so i guess it reinstall back/restored the old version)
Details of device : I am from India and the phone was manufactured in India in around April/May 2011. Its a red lens Defy and and came with Eclair. I updated it officially to the first Froyo release for SEA region. After that i rooted the phone with superone click, and installed WIUI rom. I have been updating the ROM with newer versions around each month. The last one was 1.11.18 though as i waiting for a good ICS version to flash.
The problem occurred after i started installing some gold apps from getJar. It restated in between and install... and that point is kind of acting like a restore point even now.
Things I did: Tried installing different rom by CWM method. Reinstalling second init and CM, both old and new version. Tried restoring nandroid backup of my official ROM. Tried fixed and full sbf flash through rsdlite 4.9.5.2 and now 5.6. First 3 things reset as soon as i restart. For RSDLite, it gives checksum error for each and every ROM i tried. I tried all SEA releases, JORDN_U3_97.21.51, Defy Plus Rom 2.3.6, 2.21 first eclair rom, everything gives the same error. From the RSDLite logs, i could see that there is something wrong as.. say the last successful CG was 33, and the error came for 34, the log says its expecting the checksum on the sbf to be equal to that of CG 33. Its taking the last successful checksum validation and expecting that for all the CGs henceforth. its not showing what the device actually has.
I atlast could somehow, but trial and error, removed all the CGs which were throwing error, and recompiled the sbf to make it pass the RSDLite flash. The CGs present in the ROM (JRDNEM_U3_3.4.3-36-1.7) were 32, 34, 42, 53, 61, 64, 65. And as soon as it booted, it restored back to the checkpoint. Even after i formatted by card and put it in, the app shortcuts remained on the home screen, but as the apps on the card were gone, they are just junk and doesnt open anything.
Thanks in advance. Please let me know what you need from me to help me resolve this issue.
Any help... Anyone?
Can someone please suggest something?
This is what i got from some people. I am not sure how far this is possible, but somehow the theme i installed just before this all happened, from MIUI market.. somehow managed to change something inside phone's kernel, past the locked bootloader? I am totally a noob in this and just a wild imagination?
Or may be some sort of cache wipe is happening everytime the phone boots up, So even when i install the ROM, when it boots up, it gets back the old ROM.. like what would probably happen if i do a factory reset soon after i instal a rom before the restart..?
I would really appreciate it if anyone could help me out with this...
Checksum errors were for me also.
I tried my office computer for flashing and instantly flash was done. The checksum error occurred 7 times on my good computer before that.
Reflashing froyo must take care of all errors happening
Thanks Kapil fr the response. Are you from india? Which sbf did u flash? And waht all did u install in the office pc? I have a pc of my friend where i can try to reflash if you tell me the exact steps that u took in the fresh pc.
Also, can anybody tell me how to use adb commands in CWM mode? Its recognizing my phone in normal mode but as soon as it boots in Moto recovery of CWM, its not recognizing anymore. Want to use adb format commands from recovery.
Hi I was able to use adb in CWM, but format commands were not working. How can i format the system partition? please help me with this.
Is there anyone here who know how to restore a nandroid backup manually using adb commands for MB525???!!!!!
Sounds weird and impossible. Try this. Wipe everything though cwm and flash new rom. Try ms2ginger.
Thanks darshanonline for the suggestion. I tried to wipe everything.. factory reset+cache+dalvik cache wipe. And then tried to install cyanogenmod 7.1 as well as 3 different wiui builds. Everytime it shows that the install was successful, ut as soon as i restart, it would go back to the old ROM.
Is there any checkpoint system in android, seeing the init.rc, i can see comments on something about saving a checkpoint. Is there any particular condition under which this checkpoint may be getting used on very restart?
Also.. is there any way for RSDLite to skip the chksum validations and get the install anyways?.. Some sort of a hack into it?
Ok.. Found something else thats happening. I dont need to shutdown for the system to revert back. Say i install a few things new after a reboot.. After some time.. 1 day at max, i am not able to open them, and neither am i able to open manage applications or market. Everything force closes. I have Ti Backup installed, and i opened it, and i didnt find the new apps to back up. I connected the device and checked through adb, and they were not present in the app folder. They just vanished... So basically after a certain point of tiime, the new stuff just gets deleted on its own.
Guys i know i may sound dumb and stupid with my questions, but i really couldnt find any solution on the net for this. Please tell me waht i should do, and i'll do it. But tell me something. Dont ignore please!
and you did wipe data from within stock recovery (vol down+power etc.), i presume..
Sent from my MB526 using Tapatalk
Yes i did that too.
wiped data and cache. Restarted to cwm and installed update.zip (renamed cm 7.1 stable) and by selecting zip from sd card. Same results. Installs successfully but reverts back as soon as i restart.
Same problem here:
http://forum.xda-developers.com/showthread.php?p=22617834
Soumik84 said:
Yes i did that too.
wiped data and cache. Restarted to cwm and installed update.zip (renamed cm 7.1 stable) and by selecting zip from sd card. Same results. Installs successfully but reverts back as soon as i restart.
Click to expand...
Click to collapse
DL WIUI 1.12.16 ICS > copy to SD card > Boot in CWM > select zip to install > Install WIUI 1.12.16
Hopefully your problem should be solved.
I found 1.12.16 ICS with lesser FC than the 2.21
labsin said:
Same problem here:
http://forum.xda-developers.com/showthread.php?p=22617834
Click to expand...
Click to collapse
Thanks for the link. Now i know that i am not the only one having this issue. But even there its not resolved yet.
@ headers.chennai - Thanks. I will try that ROM, along with Pikachu ROM with Aroma installer, might be a different installer can try fix it?!
BTW.. does anyone have the TI OMAP board utility? Any chance that it can be available outsite here?
I tried the arora installer and it supposedly formatted the system partition and remade it.. but as soon as it finishes and i restart.. I get back the same ROM.
Is it some way that the files are not getting deleted, like some hardware lock or fault?
Soumik84 said:
I tried the arora installer and it supposedly formatted the system partition and remade it...
Click to expand...
Click to collapse
Hi, bro! What is "arora"? I should try it asap, and all other chance.
My trouble here, same as your.
Hey man.. looks like we are having same problem...
Sorry abt the typo... its Aroma Installer. Its with the Pikachu ROM in this link :
http://forum.xda-developers.com/showthread.php?t=1498843
Its a new installer that launches from cwm when u try and install this ROM. u got some options to select and on selecting the complete install option,, the log shows that it formats the system partition and then creates it. I saved the log file, but for some reason the file shows up blank now. Might be problem with the launcher.. or my phone.. dont know.
Soumik84 said:
Its a new installer that launches from cwm...
Click to expand...
Click to collapse
Not for me, my checkpoint without cwm
Something got messed up when I tried to flash my acer a500 from a rooted version of 3.1. One problem I have (and I admit it was my fault) is I did not move my backed up ROM to my external card - so I don't have anything to restore.
My device will boot to CWM (v5, rev 1.3.4), I've tried loading several different ROMs just to flash something on there to get my device back to square one.
I got in this predicament because I had regular OTA 3.2 and couldn't root. I downgraded to 3.1 (buggy and endless FC), but I was able to run gingerbreak for rooting, do a backup (titanium) and my impression at that point was I could flash a custom mod through CWM.
Nothing is working. I have formatted the sd card in CWM and tried ROMs like Thor 14.2, Tabooney 3.0 and several 3.1/3.2 Acer stock ROMs. After wiping data/factory, wipe cache, wipe Dalvik and Battery Stats and then trying to load a zip file from /sdcard it either tells me the installation fails (which most believe is a bad dl), or (in the case of CWM_ROM_A500_701414_GEN1.zip), the install actually goes through - Finding update...opening update...Installing update... - but whenever I reboot after a *successful* install my device just hangs at the Acer logo/splash screen forever.
I've tried resetting the device (power/ + vol /lock on/off/on/off) and it hangs for a long time Erasing Cache.
I'm overwhelmed. I just want to get a stock ROM on that will install successfully so I can have a functional machine back. Can someone tell me if I'm doing something wrong or what I can do here? Thanks
Never mind
I used a different SD card and that did the trick
jcs1 said:
I used a different SD card and that did the trick
Click to expand...
Click to collapse
Enjoy the little things in life
Probably have a corrupted SD. Might just do a full format on it and still be usable.
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.