This has happened to me twice now, I've had to replace my D2 because it keeps bricking for some reason. I don't know why, but now whenever I try to download something from my SD card (a rom or a theme) It just bricks. I go to mounts/storage, click on that then I go to download from SD, I select my rom and it doesn't work. It'll go to the boot logo, show Matt's logo (I used Matts Epic2.5) and won't stop repeating it over and over again.
Sometimes it'll show the whole logo, then after maybe 5 times it'll show half the logo then stop and keep repeating this process. I don't know why, but it used to always work in the past. What am I doing wrong? Do I need to wipe my data and cache every time now? I never had to before.
I really miss my Droid 1 (root wise lol)
BTW, I don't know if this means anything, but do I need to deodex my phone or however you say it :S, sorry I'm really new to droid 2. I don't even know what deodex means lol. Anyone help me on explaining what that means?
Deodexing or de-odex-ing is how it makes more sense to me just means that all of the apk's or applications on your phone are together and don't have stray .odex files in the /system/app folder (or wherever they're located). Phone dev's will leave these .odex files out of the .apk's so that load times are supposedly faster but the file called services.jar which needs to be edited for detailed themes has to be de-odexed before it can be edited and if one file is de-odexed then the others should all be.
I'm not sure what specifically the problem is and please don't be offended if I'm going too far but in order to mount /system the entry in mounts/storage has to read "unmount /system". Make sure the you've got the entire ROM, but wiping cache and data is worth a shot too.
Also if you have a major problem with your droid 2 you just need to flash the .sbf there are two different ways to do it (and two versions of the sbf). One in windows and the other in linux and (thanks to me lol) the linux version is available to anybody with a windows computer too.
Yeah I fixed my phone today using the windows sbf. Do you think it's worth it to deodex my phone? And I don't know what the problem seems to be I have the full rom and I never had to wipe before :/ I guess I'll just wipe every time now.
Most of the ROM's now are de-odexed so you shouldn't have to the only reason you would need to is to theme. To check and see if it's deodexed just use Terminal emulator and enter
Code:
$ cd /system/app
$ ls
This means change directory to /system/app then list the files in there.(it's a lower case L)
If there are files that end in .odex then it's not de-odexed.
UPDATE: I sbf my phone and got it "unbricked". So I just got root access and then I tried to instal the 2.5 Epic Rom. These are the steps I went through.
1. Went to Titanium Backup and restored my Droid Bootstrapper app.
2. Opened the app and did the Flash Recovery, is said success then I went into recovery mode.
4. I went to Mounts and Storage, pressed OK on Mount/system
5. Went to Install from SD Card.
6. Went to EUnleashed2.5 (however it is)
7. It installed only halfway and said install is complete and the screen would just sit there when it was only less than halfway full.
9. Now my phone is bricked again and I am currently unbricking it.
What am I doing wrong?
EDIT: By the way, if those things that I clicked on aren't exactly right, it was because I was typing it from memory because my phone was bricked and I couldn't actually see them.
First, you have not been bricked - you've had bootloops, which means some files are corrupted, missing, or incompatible. You can cure a bootloop, but you can't cure a brick.
My guess is you're trying to install Epic 2.5, which has 2.2.20 baseband/kernel dependencies, over your new 2.3.20 baseband/kernel from the sbf. In other words, Epic 2.5 can't and won't install on your phone anymore. You'll have to wait for Epic 3.0 or use another ROM that has been built off 2.3.20.
karnovaran said:
First, you have not been bricked - you've had bootloops, which means some files are corrupted, missing, or incompatible. You can cure a bootloop, but you can't cure a brick.
My guess is you're trying to install Epic 2.5, which has 2.2.20 baseband/kernel dependencies, over your new 2.3.20 baseband/kernel from the sbf. In other words, Epic 2.5 can't and won't install on your phone anymore. You'll have to wait for Epic 3.0 or use another ROM that has been built off 2.3.20.
Click to expand...
Click to collapse
Lol thanks, that makes a lot more sense to me now. I just saw his post about 3.0, I can't wait till it comes out. Thanks for the help!
Related
Hi guys. I am having a bit of an issue here.
I just got my DX a couple days ago. I have a buddy that has been into modding with his D1 for a while, and he recently got a Fascinate. He convinced me to try doing some stuff with my phone...
I rooted my phone successfully. I then wanted to install the DX Invertnito theme. It said I needed to Deadex my phone. I got the xultimate 2.2.2 deodex pack and successfully deodexed my phone. I then downloaded the zip file for the Invertnito theme. I put the zip file on my phones sd card as stated in the instructions. I then downloaded Koush's DX Bootstrapper from the market and Clockwork Rom manager. Installing the theme automatically through the rom manager didnt work, but the phone did boot normally nonetheless. I then decided to go directly through the Bootstrapper app [clicked the recovery mode right on the menu out of two options]. The phone instantly shut down, then booted into the clockworkmod recovery menu. I followed the instructions given to install the Invertnito from the .zip file on the zd card. I clicked install on that file. Everything seemed to work fine to this point. Installation successful.
Unfortunately, now the phone will not boot at all.... It loads the Motorola M logo and stays there. I've tried waiting for 30 min on the logo and it just doesn't move. If I remove/replace the battery, the phone will then load the clockworkmod recovery menu again just like it did after it shutdown from running the first time. I've tried clearing cache, restarting the phone, replacing the battery 20 times. Always stuck on boot M screen. Sometimes it will go the the Motorola bootloader screen, but when i click reboot system, it just gets stuck on the M logo.
Any help would be appreciated here. I'm hoping I haven't bricked my phone somehow. I didn't expect this as I can't find anyone else who installed this same theme have the same problem. Is there something I can do to get it back to normal? Is it possible to somehow get my OS back to clean stock and go from there?
Thanks
Did you do a nandroid backup before loading the theme?
Unfortunately, no. I just read of someone having a similar issue though. Said he used RSD Lite 4.8 and an SBF and he was able to get back into his phone. Not sure how to dgo about any of that though.
Retriraver said:
Unfortunately, no. I just read of someone having a similar issue though. Said he used RSD Lite 4.8 and an SBF and he was able to get back into his phone. Not sure how to dgo about any of that though.
Click to expand...
Click to collapse
go over to mydroidworld and look in the droid x mods section. It has rdslite and sbf for froyo
rcerulli said:
go over to mydroidworld and look in the droid x mods section. It has rdslite and sbf for froyo
Click to expand...
Click to collapse
Thanks, I will go check that out and see if I can get this fixed.
be carefull i am in the same situation like you and flash the sbf file from THB team i now i think my phone is reall ****ed up bricke nooooooo
trying the 2.1 sbf file i hope its works
well first time failed and then was stuck in bootloader saying code corrupt damn i was so mad... so i tried again the 2.1 sbf adn voila droid x alive again ufffff
i will keep the ota version **** the custom rom relly i dont need it hehehehehe
Also, how can i run the RSDlite and connect it to my phone while my phone is stuck on the M screen?
Retriraver said:
Also, how can i run the RSDlite and connect it to my phone while my phone is stuck on the M screen?
Click to expand...
Click to collapse
hold volume down and camera button while you press power button it will then say ready to program.
if you did the OTA 2.2 DO NOT USE THE 2.1 SBF!!!!
if your on the leaked 2.2 and you try the 2.2 sbf but get errors due the 2.1, if you get a boot loop after that you need to go into the stock recovery and factory reset, hold home button and
ive been there as well. pull out an adapter for ur memory card or get another phone and pop ur memorycard in it and dl the file inside this link.
http://forum.xda-developers.com/showthread.php?t=794007
scroll down to option "2"
2. Update.zip - File
1.Wipe and reboot.
the "File" will be clickable and will send u to a link to dl. place it on the root of memory card(doesnt really matter where as long as its on the memory card) and click
install update.zip(if its in root and named update.zip) or u can go click choose .zip file or whatever and go look for it. hope it works for u. let us know. ill be waiting to hear ur respnse.
djtoonjr said:
ive been there as well. pull out an adapter for ur memory card or get another phone and pop ur memorycard in it and dl the file inside this link.
http://forum.xda-developers.com/showthread.php?t=794007
scroll down to option "2"
2. Update.zip - File
1.Wipe and reboot.
the "File" will be clickable and will send u to a link to dl. place it on the root of memory card(doesnt really matter where as long as its on the memory card) and click
install update.zip(if its in root and named update.zip) or u can go click choose .zip file or whatever and go look for it. hope it works for u. let us know. ill be waiting to hear ur respnse.
Click to expand...
Click to collapse
This worked for me...thanks mate!!!!
So, I've tried following the directions for the "nearly" one-step root, and the process completes, but I get no response when I run the Super app, just a blank screen. Is that normal?
Also, from what I've been able to find, it appears there are no released SBF's for the R2D2, so if I brick my phone, I'm SOL. I don't want to end up with a non-warranted paper-weight, so for now I unrooted it....however...did I do something wrong, and if so can someone fill me in?
Thanks!
which one step? I used the Z4root and had zero issues. Rooted within a minute.
OK, so I did manage to root it using the one-step root, however what ROM manager works on the R2D2? I am trying to use ROM Manager, but when attempting to do a backup, the phone reboots, then I get what appears to be an error, after which the phone boots back up normally. The error is a triangle with an exclamation in it, with the android dude standing next to it.
If I go into manage and restore backups, I have nothing listed, which tells me the backup never worked.
Any ideas?
Also, I was wondering what exactly doing a ROM backup does for me. Does it do a snapshot of the current state of the phone, so if I wanted to rollback any app changes I made, will that be undone?
Just trying to get a feel for what exactly this does for me. I would like to de-blur my phone, and by saying that, I'm not even totally sure what that means. I see a TON of motorola apps in the system/apps folder, but I really don't know what is safe, and not safe, to get rid of.
Thanks!
osufans said:
OK, so I did manage to root it using the one-step root, however what ROM manager works on the R2D2? I am trying to use ROM Manager, but when attempting to do a backup, the phone reboots, then I get what appears to be an error, after which the phone boots back up normally. The error is a triangle with an exclamation in it, with the android dude standing next to it.
If I go into manage and restore backups, I have nothing listed, which tells me the backup never worked.
Any ideas?
Also, I was wondering what exactly doing a ROM backup does for me. Does it do a snapshot of the current state of the phone, so if I wanted to rollback any app changes I made, will that be undone?
Just trying to get a feel for what exactly this does for me. I would like to de-blur my phone, and by saying that, I'm not even totally sure what that means. I see a TON of motorola apps in the system/apps folder, but I really don't know what is safe, and not safe, to get rid of.
Thanks!
Click to expand...
Click to collapse
Super user app is blank until root apps are used.
For now I wouldn't use a ROM manager you need Koush's Bootstrap to be able to do a backup. It's on the market. To use it just tap the Bootstrap button then wait for the success toast (box) and then tap Reboot Recovery and your phone will boot into Clockwork mod. Backup will take an img of the phone as it is at the point where you backed up. To restore if you mess something on a later install but if you can't get into clockwork for some reason you might be out of luck. Because there is no SBF specifically available for the R2D2 D2 but I've heard that the 2.3.20 might unbrick bricked R2D2's but you won' have the same verizon version you have now it'll be a step back.
OK. I do have bootstrap recovery installed and was able to perform a backup.
Also found a link to some of the bloatware you can "safely" remove. I'm still tweaking it....but that being said, what else can you do (i.e. - overclock, etc.)?
You can overclock, install libs and bins that access hardware features locked out by vzw, change roms and themes....yada, yada.....the 2.3.20 sbf is not a step back. The radio update and kernel tweaks for battery life are not in the 2.4.5 system. They had the rom version because some files are different between the two.
Sent from my DROID2 using XDA App
Sadly, I have goofed up my phone right out of the gate. I do not think it is bricked, but I'm unsure how to proceed and more than a little spooked by how quickly things went from great to non-functioning.
I took my stock Epic 4G and followed a tutorial to install Froyo. That went without a hitch. I then used noobnl's one-click script method to root the phone, and that also seemed to work well.
Then I tried to install the Nebula ROM with DK28 modem and pit, using Odin3 v1.61. Since then, my phone will not boot past the Samsung logo. I can still get into Clockwork, but repeating the ROM installation process has not made any difference. I then noticed that I'm running Clockwork Mod Recovery v2.5.1.0, when Nebula apparently requires v2.5.1.5 or newer.
So can anybody help me fix what I've broken? I've tried searching the forum for this problem, but have not been able to find anyone with my particular form of stupid.
Thanks in advance for suggestions.
Cincinnatux said:
Sadly, I have goofed up my phone right out of the gate. I do not think it is bricked, but I'm unsure how to proceed and more than a little spooked by how quickly things went from great to non-functioning.
I took my stock Epic 4G and followed a tutorial to install Froyo. That went without a hitch. I then used noobnl's one-click script method to root the phone, and that also seemed to work well.
Then I tried to install the Nebula ROM with DK28 modem and pit, using Odin3 v1.61. Since then, my phone will not boot past the Samsung logo. I can still get into Clockwork, but repeating the ROM installation process has not made any difference. I then noticed that I'm running Clockwork Mod Recovery v2.5.1.0, when Nebula apparently requires v2.5.1.5 or newer.
So can anybody help me fix what I've broken? I've tried searching the forum for this problem, but have not been able to find anyone with my particular form of stupid.
Thanks in advance for suggestions.
Click to expand...
Click to collapse
Odin back to this http://forum.xda-developers.com/showthread.php?t=794138 then root using this http://forum.xda-developers.com/showthread.php?t=770388 then install this if you want cw3 and ext4 if not skip it http://forum.xda-developers.com/showthread.php?t=897612 but check on the rom ur flashing because most rom are now using ext4 and cw3. Also if you want and ur rom has the option for no journaling flash this before flashing a rom http://code.google.com/p/bonsai/downloads/detail?name=ext4-format_nojournal-1.1.3.zip&can=2&q= . I know Bonsai and Midnight roms have the option for it. Well best of luck to you and if you have any question or concerns please post them here and ill or one the many helpfull people here at xda will assist you.
Thanks, asj2583, for the quick response. For whatever reason, it did not occur to me to try putting the phone in download mode!
So to get the phone back on-track, I:
1. Started Odin3 v1.61
2. Removed the SD card from the phone
3. Plugged the Samsung USB cable from the phone to the computer (which is running 32-bit Windows Vista)
4. Clicked on 'PDA' in Odin3, then selected the Froyo TAR that had worked before, then I clicked on 'START.'
5. Let Odin3 do its thing, and now my phone is back up and running unrooted Froyo.
Moving forward, I:
1. went here and downloaded One Click Root 2.5.5.
2. On the phone, went into Menu/Settings/Applications and enabled 'Unknown sources,' then unplugged the USB cable and clicked on /Development to enable USB debugging and Stay Awake.
3. I plugged the USB cable back into the phone and ran the 'run.bat' file I extracted from the One Click Root 2.5.5 download. In short order my phone rebooted into rooted Froyo. (confirmed by going into Applications and seeing that 'Superuser' is installed)
Now it's time to set up CW3 and ext4:
1. I went here and downloaded a different One Click Root (anyone know if I could have used this instead of 2.5.5?).
2. Again, with USB debugging enabled and the USB cable plugged in, I clicked on 'run.bat' extracted from the One Click Root CWM3 download. After a brief wait, the phone rebooted. Theoretically, at this point I have Clockwork Mod 3.0.0.5 and my phone can handle ext4 filing. (Speaking of ext4, I thought that was intended for handling LARGE files on teranyte-plus HDDs. How is it the right choice for a smartphone?)
And to try a new ROM:
1. I went here and downloaded CyanogenMod 6.2 prebeta 14 and saved it to the root directory of my phone's SD card.
2. Powered down the phone, and reinserted the SD card.
3. Powered up into ClockworkMod Recovery. The screen showed that it was running v3.0.0.5. ClockworkMod automatically checked for ext4 but failed to mount. ClockworkMod suspected my files are still in rfs (admittedly, I never reformatted my SD card to ext4). ClockworkMod created a backup named 'before-ext4-convert-1296478915' in case I need to restore. At this point, I found myself in ClockworkMod's menu.
4. In ClockworkMod, I ,ped data/factory reset 3 times, cache partition 3 times and, under /Advanced, wiped Dalvik cache 3 times. I then went back to install zip from SD card and chose the CyanoGen Mod I wanted to try, but it failed. ClockworkMod noted that Amend scripting (update-script) is no longer supported and that I need to switch to Edify scripting (updater-script and update-binary) to create working update zip packages. So I went back to my SD card and told ClockworkMod to install gapps-hdpi-20101218-EPICv1.0.3.zip, which completed without error. Then I told ClockworkMod to install NebulaMod. The phone rebooted and all seems well.
Thanks! I sure was stuck last night, and just needed a nudge in the right direction.
Whoah. Whatever you do, don't follow my advice. This just bricked the phone. It will not even power up any more. Damn.
Correction. Not bricked. Just really, really scary. Thanks to Koadic I'm back at unrooted Froyo. I think maybe I'll stay here for a while.
Cincinnatux said:
(Speaking of ext4, I thought that was intended for handling LARGE files on teranyte-plus HDDs. How is it the right choice for a smartphone?)
Click to expand...
Click to collapse
Ext4 wasn't intended solely for handling large files. It made some changed to ext3 that allows handling of larger files and also increases the subdirectory limit, which makes it suitable large files or large disks. Ext4 also added journaling. These are not the reasons we use ext4 on our phones. I think all of our ext4 roms mount the disks with the noatime flag, and many people are running the no-journal mod. This makes ext4 act more like ext2 with the ability to allocate extents instead of individual block.
"Amend scripting (update-script) is no longer supported and that I need to switch to Edify scripting (updater-script and update-binary) to create working update zip packages."
My phone also says this when I try to install the Truly-Epic rom. I'm on DK28 like the rom says to be on, and on CWM3 and EXT4...yet...it doesn't want to install. Anyone know what for or what might be any problems?
how long did it take for your phone to power up after rooting with ext4 and cwm3? mine has been at it for a while now. i flashed back to stock dk28 using odin and did the process over and it gets stuck backing up my information and just keeps creating before ext4 back ups til my memory is gone
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
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.