Related
My vibrant is running stock 2.2 Froyo. Lately, it dies silently and so frequently in sleep that I can't rely on it for every day usage. I've missed many important calls. So I am trying prepare my phone to flash another ROM. First, I got the phone rooted no problem at all.
Then the first problem I have is with the ROM manager. I purchased the Premium Version 3.0.1.3 and flashed the latest ClockworkMod Recovery 2.5.1.2. Upon rebooting into Recovery, there is, however, no Nandroid backup, just the normal menu shows up with
Samsung Recovery Utils -for BML-
.reboot now
.reinstall packages
.delete all user data
.delete cache data
.format internal sd card
I remove update.zip on the phone and on the sd card and retried and retried without success. Why don't I have Nandroid backup showing up to save the phone before flashing new ROM?
The second problem is with the Titanium Backup. I downloaded the free version and it works fine and could get root privilege without problem. Then I purchased the donated version and followed the instruction to uninstall the app and reinstall it to get the upgrade through the license file. The license file is read correctly and the upgrade version acknowledges that. However, Titanium Backup paid version now fails to get root privilege. I verify that other apps can get root without problem. I've searched all over yesterday and it seems that few people have the same problem getting root with the upgraded version, but no one has offered a solution.
So here I am paying but not able to backup the phone to start flashing anything. Could someone enlighten me about what I did wrong here?
Thank you.
For recovery, just select reinstall packages. Sometimes you have to do it twice.
For titanium backup, click the problems button to get the latest busybox.
You should be good after that.
Sent from my GT-I9000 using XDA Premium App
What offdutyninja808 said, also check your Superuser app, click Titanium and tell it to forget it if it's there.
We'll get you sorted out!
I have the same set-up and I have the same issue. I've selecting reinstall packages several times. Did not work. I tried different, methods: using Rom Manager and AIO Vibrant Toolbox. Didn't work. At first it said said it wasn't signed, and I four a fix for that. Now It loads and says replacing stock recovery with Clockwork... but boots back into the stock one. Is there anything else I can do?
birgertime said:
What offdutyninja808 said, also check your Superuser app, click Titanium and tell it to forget it if it's there.
We'll get you sorted out!
Click to expand...
Click to collapse
+1 Both Off duty and birgertime are correct. Most of the new roms will delete all things for you unless they say to do something particular (like some of the EDT roms) you should be ok, we are here to help if you run into further problems
If hitting "reinstall packages" don't take you to the clockwork recovery, also you can just reinstall the recovery thru rom manager.
Then once you reboot and if it don't take you to clockwork recovery, then hit reinstall packages again. Ya should get to it the second time.
I had this issue a lot when first rooted the phone and installed clockwork recovery.
Sometimes it will even boot halfway into stock recovery then quickly reboot itself into clockwork.
Also, just make sure that there is only ONE update.zip in there. So delete the update.zip using "my files" then open Rom Manager and choose install clockwork recovery. That way you are sure there is only one update.zip there then try the previous mentioned methods
Thanks for your advice. I still have problem with selecting "reinstall packages" in the Recovery menu. If I select that, it says:
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
This repeats if I keep selecting "reinstall packages" again. My SD card is still the original 2GB card that comes with the phone. It still has plenty of space.
Thanks again for helping
FWIW, I upgraded BusyBox and could solve the Titanium Backup problem. However, still can not do a nandroid backup as mentioned above, even with the donated version. So I abandoned my plan to flash another ROM and stay with the rooted stock.
However, what a difference it makes when I replace the 2GB SD card that came with the Vibrant with a 16GB SD card class 10. The unit comes up faster, the UI is no longer sluggish as before. I hope that this was the issue that caused my Vibrant to die in sleep. I need to phone for daily use and don't have a lot of time to muck around with it. Maybe next year when I have another phone to use as main phone, then I can take some risk to flash without nandroid backup. For now I hope that it no longer dies in sleep. Thanks for all your help.
Just a quick note to end this thread.
Since I have plenty of disk space on the internal memory, I removed the SD which I don't need and the phone seems to become reasonably fast responsive with rooted stock 2.2. It's now quite usable for me so I have no more need to flash it with another ROM. People who complain about slowness of their stock 2.2 ROM should try to remove the SD card first.
Thanks again for all your help.
I have a NC 1.2. I am able to root using a CWM 3.0.2.8 Msd card with Manual Nooter no problem. The problem occurs when I shut it off and then reboot. It gets to the part where the words "Nook Color" start scrolling across the screen. "Nook Color" completes one time successfully and when it starts scrolling again, it stops halfway through the first "o" in "Color", and just repeats indefinitely. The only thing I could do is completely reset, eight failed boots. At first I thought it may be an older version of CWM on my Msd card so I made a new one with v. 3.0.2.8 and rooted successfully, but first time I shut it off and rebooted, it happened again. I am thinking only thing to do is never turn it off. Any ideas would be greatly appreciated.
reebz said:
I have a NC 1.2. I am able to root using a CWM 3.0.2.8 Msd card with Manual Nooter no problem. The problem occurs when I shut it off and then reboot. It gets to the part where the words "Nook Color" start scrolling across the screen. "Nook Color" completes one time successfully and when it starts scrolling again, it stops halfway through the first "o" in "Color", and just repeats indefinitely. The only thing I could do is completely reset, eight failed boots. At first I thought it may be an older version of CWM on my Msd card so I made a new one with v. 3.0.2.8 and rooted successfully, but first time I shut it off and rebooted, it happened again. I am thinking only thing to do is never turn it off. Any ideas would be greatly appreciated.
Click to expand...
Click to collapse
What version MN are you using? You’re not wiping anything when you flash MN, right?
reebz said:
…At first I thought it may be an older version of CWM on my Msd card so I made a new one with v. 3.0.2.8 and rooted successfully, but first time I shut it off and rebooted, it happened again. I am thinking only thing to do is never turn it off.
Click to expand...
Click to collapse
Are you saying that after you flash MN, you remove the SD card, it will fully boot up into the OS, then when you turn off the device and try to turn it back on, it will then not boot up? Or, are you saying that after you flash MN, you remove the SD card, and then the device fails to boot?
It sounds to me like you are wiping the system before you flash MN, but until I get the answers to the above questions, I can’t say for sure. MN is a add on pack for the stock OS, not a full rom, so you don’t wipe before you flash.
I have latest version of MN. I do not wipe anything. I boot into CWM and install MN with a msd card. Upon successful installation of MN, I remove msd card and reboot successfully that one time into a rooted NC. I can use Gmail app, download and install from both Android and Amazon markets. However, if I power down completely and reboot, it loops as explained in my OP.
reebz said:
I have latest version of MN. I do not wipe anything. I boot into CWM and install MN with a msd card. Upon successful installation of MN, I remove msd card and reboot successfully that one time into a rooted NC. I can use Gmail app, download and install from both Android and Amazon markets. However, if I power down completely and reboot, it loops as explained in my OP.
Click to expand...
Click to collapse
Are you updating Adobe Flash? You can't directly update Adobe Flash from the Nook Color. The most common issues that will cause a boot loop on a NC after having a fully working device, are installing the wrong kernel, and updating Adobe Flash from the Market. If you updated Adobe Flash, download the attached file, and flash with CWM. The file should delete the old flash player, and install the updated one. This should give you a working device again. If it does work for you, please report back here so others will know what the fix it.
GMPOWER said:
Are you updating Adobe Flash? You can't directly update Adobe Flash from the Nook Color. The most common issues that will cause a boot loop on a NC after having a fully working device, are installing the wrong kernel, and updating Adobe Flash from the Market. If you updated Adobe Flash, download the attached file, and flash with CWM. The file should delete the old flash player, and install the updated one. This should give you a working device again. If it does work for you, please report back here so others will know what the fix it.
Click to expand...
Click to collapse
I have updated Flash Player from the Market after rooting. If I remember correctly, I've powered down after rooting and installing numerous apps, including Flash, and rebooted . Maybe that's the culprit. I have not installed a different kernel. I'll go ahead and install the attached zip, with much thanks, but I don't know if I want to power off and reboot, for fear of dreaded boot loop.
Ok, I installed Flash Fix and rebooted, and the same boot loop is occurring. Looks like time to reset and reroot, and for now, never turn it off.
reebz said:
I have updated Flash Player from the Market after rooting. If I remember correctly, I've powered down after rooting and installing numerous apps, including Flash, and rebooted . Maybe that's the culprit. I have not installed a different kernel. I'll go ahead and install the attached zip, with much thanks, but I don't know if I want to power off and reboot, for fear of dreaded boot loop.
Ok, I installed Flash Fix and rebooted, and the same boot loop is occurring. Looks like time to reset and reroot, and for now, never turn it off.
Click to expand...
Click to collapse
I just realized that I missed a step in the install script for that file, that is why it did not work for you. Yes, adobe flash is your problem. To update Adobe Flash on the nook color, you have to uninstall the old version, and then install the new adobe flash.
For all future references, I have attached the working Adobe Flash fix file. It includes flash version 10.3.186.3, that was released today. It has been tested to work, and you can allow auto-update in the market without future problems.
Ok, thanks, I will reluctantly give this a try when I get home from work.
Edit: Ok, now. I'm trying to uninstall Flash Player and having difficulties. It doesn't show up in the app drawer, so I go to Market to see if there is an uninstall option, but there is only an update option, so I updated, and then uninstalled to see if that would work, but it still showed up in "my apps", in market. I opened up app drawer and selected manage apps and found it, but selecting the uninstall button does nothing. I then tried installing Titanium Backup and after installing, Titanium Backup won't open and doesn't even show up in my app drawer. So, I'm a little stymied now. Unsure what to do next
reebz said:
Ok, thanks, I will reluctantly give this a try when I get home from work.
Edit: Ok, now. I'm trying to uninstall Flash Player and having difficulties. It doesn't show up in the app drawer, so I go to Market to see if there is an uninstall option, but there is only an update option, so I updated, and then uninstalled to see if that would work, but it still showed up in "my apps", in market. I opened up app drawer and selected manage apps and found it, but selecting the uninstall button does nothing. I then tried installing Titanium Backup and after installing, Titanium Backup won't open and doesn't even show up in my app drawer. So, I'm a little stymied now. Unsure what to do next
Click to expand...
Click to collapse
Titanium Backup is going to be your best bet to do the uninstall process. When you selected update Flash from the market, then went and uninstalled it, you were only uninstalling the update. If TB installed, then it should show up in the app drawer of Zeam launcher. You can go into the market, and select to open it from there. Sometime it will not open on first attempt, because it is trying to ask you to give it root permission. If you still have trouble with it not opening, then uninstall it, and try to install it again. You can also open up the “Superuser” app to make sure that it has not been denied root permission.
TB definitely didn't appear in Zeam app drawer. I'm charging now and give it another shot in a bit.
Edit: Success. I got TB installed. I made a stupid error. I only installed the paid app, not the free also. I got Flash uninstalled and installed your Flash Fix.zip with numerous reboots with no boot loops.
GMPOWER, Thanks for your assistance
GMPOWER said:
For all future references, I have attached the working Adobe Flash fix file. It includes flash version 10.3.186.3, that was released today. It has been tested to work, and you can allow auto-update in the market without future problems.
Click to expand...
Click to collapse
I don't normally bump old threads, but this just saved me
Thanks a lot, I was at wits end figuring out why it was boot looping.
dreadwing said:
I don't normally bump old threads, but this just saved me
Thanks a lot, I was at wits end figuring out why it was boot looping.
Click to expand...
Click to collapse
Same here. Big thanks to GMPower! (My first post here, now I can use the Thanks button!)
Total noob question. This is my first time rooting. I got the root to work fine but updated Flash before finding out about the loop. I'm not sure what I'm supposed to do to fix this problem. OP in this thread said he reinstalled MN 4.6.16 via bootable SD with CWM and could get his nook to boot up. I tried that and rebooted but I'm still getting stuck in the loop.
Do I need to wipe my nook before reapplying MN?
dahcheet said:
Total noob question. This is my first time rooting. I got the root to work fine but updated Flash before finding out about the loop. I'm not sure what I'm supposed to do to fix this problem. OP in this thread said he reinstalled MN 4.6.16 via bootable SD with CWM and could get his nook to boot up. I tried that and rebooted but I'm still getting stuck in the loop.
Do I need to wipe my nook before reapplying MN?
Click to expand...
Click to collapse
Use the zip file in post #7 (in this thread). Drop it onto the same SD card you used to load MN 4.6.16. Put the SD card in and it'll boot to CWM....then flash that zip file the same way you flashed MN. Then, power off the NC, remove the CWM SD card and put in your regular SD and turn the NC back on. That should be it...no more boot loop.
I've got the same issue as the thread started and I downloaded the zip from post 7 and flashed it just like I flashed MN, but it's still boot looping. It gets a bit farther into the "Nook Color" logo but keeps repeating.
Boot Loops NC 1.3
GMPOWER said:
For all future references, I have attached the working Adobe Flash fix file. It includes flash version 10.3.186.3, that was released today. It has been tested to work, and you can allow auto-update in the market without future problems.
Click to expand...
Click to collapse
This problem started for me on Rooted 1.3. October 5th, Applied this fix.
Thanks GMPOWER
I figure I will explain my problem in more detail. I am working with my girlfriend's Nook trying to get it rooted. The first time I did she had 1.2 stock and I rooted it successfully. She updated flash not knowing that it would cause a boot loop. I had no idea how to fix it so she set it back to factory settings and procedded to update to 1.3 to see if that would solve the boot loop. I rooted it again and it started boot looping again. I found this thread and the flash fix. I flashed it onto the Nook and it fixed the loop problem.
Well she found out that the marketplace has limited visibility with 1.3 and wanted to go back to 1.2 to have her full visibility back. So she factory reset it again, I rooted it again and it started boot looping again. This time though the fix from post 7 isn't helping. I flash it and then reboot and it loads the "Nook Color" logo once fully and then stops and starts it over again and gets stuck at "Nook Col".
Is there anyone who might be able to help me with what the problem is, or am I gonna have to reset it back to stock, use Titanium Backup to remove flash and then use the zip from post 7? I know that it's not a root problem because I successfully rooted my mom's Nook before my girlfriends and her's is working fine.
Followed your instructions and my problem solved, many thanks!
johnny15 said:
Use the zip file in post #7 (in this thread). Drop it onto the same SD card you used to load MN 4.6.16. Put the SD card in and it'll boot to CWM....then flash that zip file the same way you flashed MN. Then, power off the NC, remove the CWM SD card and put in your regular SD and turn the NC back on. That should be it...no more boot loop.
Click to expand...
Click to collapse
my first post. thanks GMpower
just had this happen to me too. I've tried the flash update, and I get slightly more of the nook color boot graphic but it still hangs.
any thoughts?
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.
--
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.
I've been a stalker on here for a long time, as I've been interested in custom ROMs but I never pulled the trigger, until last night. My Vibrant has served me well for a many years, I bought it shortly after they came out. All I'd ever done to it was network unlock it so I could keep using it after I moved to the UK.
I've been toying with getting a new phone for a few months now so I decided why not try and flash a custom ROM and get ICS on my Vibrant, if I got the EU error and bricked it, oh well, I'd get a new phone. So I after much reading and research, studying the tutorials on here I went for it. I am vary tech and computer savvy. I build my own computers from scratch, I've flashed my routers and set up networks so I was pretty confident I could do this with the help of the forums here.
I've read every thread I can find on the EU on here and I know that the community needs as much info as possible to try and solve this bug, so I will try and be as specific as possible and list everything I did. But bear in mind, I'm new to this and this was my first time doing much of this so some things may be muddled as I was up til quite late messing with all this.
To start my phone was running 2.2 which was updated using Kies Mini. The only thing I'd ever done to it was network unlock, and for that all I did was find the file on the phone with the code and then enter it to unlock.
I decided to follow Woodrube's guide (http://forum.xda-developers.com/showthread.php?t=1464423)
I followed the guide to the "T".
1. Used Odin to flash back to stock 2.1, worked fine, phone booted back up and everything worked. Phone Data showed I was on 2.1.
2. I put Clockwork Recovery downloaded from Woodrube's sig block on my internal sdcard labeled as Update.zip
3. Created a folder called ICS on my internal sdcard. Found and downloaded CM7 from the forums here and dropped it into the ICS folder. Found and downloaded the ICS Passion ROM from the forums and dropped it into the ICS folder
4. Booted to recovery mode and did Reinstall Packages. It ran but brought me back to the blue recovery screen. so per Woodrube's guide I did it again and the second time it brought me to the green CWR recovery screen
5. I did wipe data/ factory reset
6. I did wipe cache
7. I went to advanced and did wipe dalvik cache
8. I went to mounts and storage and did format system
9. I went to install from sdcard and found the ICS folder I made and ran the CM7 fille I dropped there. It worked the first time and booted right up, I let it sit for about 5 mins waiting for the request to install my google password as Woodrube mentions, but it never appeared, so I moved on after 5-6 min of waiting.
10. I then booted back into recovery mode using the extended power button menu
11. I went to install from sdcard again and this time ran the ICS Passion file. It ran some text lines showed on the screen as id did somethings and then I sw a Random Offset error and a small hex string but then it said successfully installed but didn't leave the recovery screen. So i scrolled up to reboot system.
12. The phone rebooted, showed me the Passion splash screens and a progress bar which filled and completed, then showed a few other splash screens and then it booted up showing my signal strength bar and notifications bar. I thought YES! I did it and it worked. then the screen flashed, it showed a single multi-colored line horizontally across the middle of the screen and then flashed again and I was looking at the Encryption Unsuccessful screen.
13. I DID NOT PUSH THE RESET BUTTON, I set the phone aside and followed Woodrube's link to the Captivate Forums and read up on the error, read all of it, then searched the forums for more threads on the error and read all of those, then I Googled the error and read everything else I could find.
14. First i tried just shutting the phone down with the power button and then restarting it. I did this about 5-6 times. Every time it rebooted it showed me the Passion splash screens then boots up shows my notification bar and signal strength meter and the EU screen. That didn't work. I next tried rebooting 5 times without my external sd card installed. Same results
15. Next I decided to see if I had lost access to my internal sdcard as I had read about. I wasn't sure if I had because I had never pushed the EU screen reset button. So I booted into recovery mode, went to install from sdcard and my sdcard list popped up. I still had access to my internal sdcard.
At this point I was torn... do I stop playing with fire and just got back to stock, update with Kies Mini and go back to using the phone as I had always been and forget all this or do I try and figure this out? Well my stubborn side hating to be stumped had encountered a problem and so wanted to move forward... on i went.
16. I decided, ok, I can still see my internal sdcard so why not try reflashing the ISC Passion and see if maybe it will take this time with no EU. I ran it and exactly the same thing happened as the first time.. right down to the flash with the horizontal line and all. (I did not wipe data, cache or anything, just reflashed. Not sure if I should have or not)
17. Back to recovery mode and check... yes still see my internal sdcard. hmmm
18. Decide ok, how about it I do Woodrube's guide all over again from the start? Maybe that will work. I followed the guide again using all the same files and wound up right back at the EU screen again.
19. Hmmm, how about a different ICS ROM? Went and found ICZen and downloaded it. Hmm, how do I get this unto my internal sdcard if the phone won't boot all the way? Booted it back to the EU screen and just plugged the phone into the usb on my computer, windows recognized it, made the device plugged in noise, and both my internal and external sdcards on the phone showed up as drives. Navigated to the ICS folder in the internal sdcard and dropped the ICZen file into it.
20. Rebooted the phone into recovery mode using the power button menu
21. Used install from sdcard and flashed the ICZen. (Again, I didn't wipe anything before hand. Again not sure if I was supposed to)
22. The ROM installed and got stuck in a boot loop. I pulled the battery and rebooted to recovery and reflashed the ICZen again with no wipes. This time it worked and the phone rebooted and I got the ICZen splash screens, then the notification bar and signal strength meter showed up.. and AGAIN the weird flash with the horizontal bar and then the EU screen. SIGH
23. Booted back to recovery mode and checked if I still had access to internal sdcard. yes it was still there.
24. Shut down and booted to download mode and ran Odin and flashed back to stock 2.1
This is where I am now, It was too late to try anything else and my wife was glaring at me to go to bed so shut off the phone and went to bed.
I tried to put everything I did down with as much detail as I could. I'm sure some of you pros out there might be wincing at stuff I did, but again this is all new stuff for me and I'm slowly learning.
If you have any questions or need clarification just ask and I will try and help/explain better.
Hopefully this might help in the quest to solve this bug or it may just be a waste of time to read, dunno.
I got to:
"To start my phone was running 2.2 which was updated using Kies Mini."
and stopped there
Come back to Froyo - always welcome here
Moped_Ryder said:
I got to:
"To start my phone was running 2.2 which was updated using Kies Mini."
and stopped there
Come back to Froyo - always welcome here
Click to expand...
Click to collapse
LOL, yea I know, but up until this adventure last night, I just used the phone with the Samsung updates as it was, didn't really have a need to do otherwise.
I think that you should flash one of Moped's ROMs and make sure that it will boot up and run ok and that you did, in fact get out of the EU bug safely.
Couple of things:
I did get your PM and I thank you for the info. This post is far more detailed, which is a ton better.
You say that you were unlocked. There was a theory not too long ago about a corrupted EFS file, but AdamOutler uploaded his and someone else replaced theirs with it and it didn't work. But I am thinking that there might be a link here bc I have seen several posts over the last few months that ICS ROMs have been out where someone's data has been borked or their IMIE was gone. Wonder if there is a correlation to that? I'll have to ask some people onver in the Captivate thread and if anyone in the Vibrant thread can chime in too(?).
If you want to flash another ROM, just follw my ICS guide but where it says to install CM7, just install your shiny, new 2.2 instead and there you are.
Great Job dodging that bullet and hope that you no longer lurk, but be a part of the community at large. If your intelligence is reflected in your post, you are welcome here anytime.
Thanks Woodrube,
I was thinking the same thing about loading a 2.2 ROM and be sure I'm all good.
I know the 2.1 I loaded last thing last night seemed to work fine. But I will try a 2.2 once I get home and will update on here after I do.
Funny thing about all this is that my wife now won't let me near her Captivate ROFL.
Can you blame her ?
For the sake of the thread i can chime in on the unlock part. I'm still untouched by the EU bug "touching wood(rube)" . I'm using the i896 version of the Captivate from Rogers and there was never codes inside of it so most app were unsuccesfull at pulling them. I had to use the free SGS Unlock website where you upload your nv_data.bin and it returns you a unlocked version. I also never encountered any efs/imei issue.
hi.
I saw you have not wiped when installing the ROMs. I think maybe you should try and do the wipe before installing the ICS ROM.
Wipe system, data, cache.
Good luck
romitkin said:
hi.
I saw you have not wiped when installing the ROMs. I think maybe you should try and do the wipe before installing the ICS ROM.
Wipe system, data, cache.
Good luck
Click to expand...
Click to collapse
BINGO!
So I followed Woodrube's guide again.. started from scratch... only change I made was I wiped data factory reset, wiped cache, wiped Dalvik cache, and under mounts and storage I format system BEFORE flashing the ICS Passion.
Logged into Google Account and set up phone and now I'm rockin' ICS
Not sure how or why this worked but it did.
Thoughts?