Related
Ok so i'm fairly new (only 3 and a half months although been lurking until my hero purchase for around 6 months) and catch on quickly.
I have a cdma hero running darchlegendv.4.3 and forgive me for forgetting his name(The Blue theme his name starts with a g,sorry g*****,lol) but anyhow, i've tried flashing a few roms now and am getting stuck in a constant boot...
I Backup,Wipe Everything but sd,flash the update zip and it installs and boots..
The Problem is It boots and boots and then finally freezes for about 20 seconds then starts the boot animation over and over.What could be the cause of my constant boot???
1)Is It A Bad PRI or PRL???
2)I've Flashed Fresh 2.0d,Darchlegend 5,DC5.6,and Darchvanilla with this problem..
3)(While I'm Asking Questions)I'd Like To start developing and making roms and/or applications for my favorite little green robot. Can anyone take the time out to PM me possibly??
Thank you sooo much for any contribution it's very appreciated
abov3dis said:
Ok so i'm fairly new (only 3 and a half months although been lurking until my hero purchase for around 6 months) and catch on quickly.
I have a cdma hero running darchlegendv.4.3 and forgive me for forgetting his name(The Blue theme his name starts with a g,sorry g*****,lol) but anyhow, i've tried flashing a few roms now and am getting stuck in a constant boot...
I Backup,Wipe Everything but sd,flash the update zip and it installs and boots..
The Problem is It boots and boots and then finally freezes for about 20 seconds then starts the boot animation over and over.What could be the cause of my constant boot???
1)Is It A Bad PRI or PRL???
2)I've Flashed Fresh 2.0d,Darchlegend 5,DC5.6,and Darchvanilla with this problem..
3)(While I'm Asking Questions)I'd Like To start developing and making roms and/or applications for my favorite little green robot. Can anyone take the time out to PM me possibly??
Thank you sooo much for any contribution it's very appreciated
Click to expand...
Click to collapse
I hope you're trying to wipe and then adding the theme... flash or recover your 4.3.1 (although I recommend flashing 4.5) and then flash your darkstar theme over it
Oh no I have the them on top of darchlegend 4.3 , I applied that right i just don't know why it constants boots when i try to flash to a new rom(i do wipe)I just don't know..
abov3dis said:
The Problem is It boots and boots and then finally freezes for about 20 seconds then starts the boot animation over and over.What could be the cause of my constant boot???
Click to expand...
Click to collapse
So plug in the cable, do a logcat, and find out.
How exactlt do i do that? Thanks for the reply
do adb logcat from command prompt.
ALSO,
were you sure that this was in fact a theme for DarchLegend? Cause if it didn't specifically say that, then that is why. Different frameworks between that rom and the sprint roms.
yes I haven't a clue what's wrong, I'm in recovery wipe and it installs but conatantly boots . Note:this is when i flash a new rom,te current will boot
abov3dis said:
yes I haven't a clue what's wrong, I'm in recovery wipe and it installs but conatantly boots . Note:this is when i flash a new rom,te current will boot
Click to expand...
Click to collapse
what are you wiping just data? ive had this happen before, wipe everything dev., ext, data everything then flash again then wipe data again.
Any flash that wipes dalvik cache like a rom our flipz's vanilla lock screen fix can take up to twenty minutes to boot the first time. This also means anytime you wipe the dalvik cache from recovery.
I have been using Rubix Focused 1.8.9 on my DX for a weeks or so and I was super happy with it. I have been getting a little ROM crazy though and had been reading up on Tranquility 3.5.1 and it seemed pretty cool so I decided to try it.
I think I messed something up in the install process because things were FCing left and right and it was just super laggy. So I decided to restore my nandroid backup that I had made right before installing Tranquility.
I was doing all this on a bus so I didn't realize that my batter was pretty low. Well halfway through my nandroid restore my batter died. Suffice it say that I was freaking out.
I got home and booted the phone and got the Tranqulity splash screen, followed by the Rubix splash screen. Then the phone booted up into Rubix exactly like it was in the backup.
I have no idea what is going on. I dont really mind the splash screens but I am afraid there may be some issues if there are files from both installs running at the same time.
Should I try restoring the backup again and let it go all the way through or do I have nothing to worry about?
Actually - and you can correct me if I am wrong - you got the tranquility boot logo and the rubix flash screen? If that is correct - you don't really need to worry about it. For whatever reason - the nandroid does not over write the boot logo.
I actually performed and sbf and when I rebooted my phone I still had my custom boot logo! It actually kind of bothered me. I thought the whole purpose of an sbf was to COMPLETELY restore your phone to its factory state.
So anyways - I wouldn't worry about it too much. I know it would drive me crazy to have the "wrong" boot logo. Here is a link to a thread with tons of boot logo's to choose from...
http://www.droidforums.net/forum/droid-x-hacks/91707-droid-x-custom-boot-logo-ill-create.html
good luck.
Some details:
HD2 512.
Typhoon 3.5.6.
MAGLDR 1.13.
Recovery 4.0.0.0.
Some things I know:
CM7 takes a while to load anyway.
I believe having lots of media (I have 7GB MP3's) can lengthen boot times. (~Theory is crapped all over with my SGS2 but some people have mentioned this fact).
The problem here is not at the loading stage where the bootanim kicks in, it's the stage before with the static logo after GO GO GO.
My SGS2 literally loads and is ready to use in 10 seconds to OS and 30 seconds to functionality after media scan/widgets etc.
So what's my HD2 doing at the static logo screen? It basically doubles the entire loading time but from my little knowledge, nothing actually happens until the bootanimation? I don't like waiting up to 2 minutes to be using my phone.
I hear CLK has a faster boot option. In anyone's opinion, have they sorted data out enough to come away from MAGLDR?
Thanks in anticipation of any responses.
dkl_uk said:
Some details:
HD2 512.
Typhoon 3.5.6.
MAGLDR 1.13.
Recovery 4.0.0.0.
Some things I know:
CM7 takes a while to load anyway.
I believe having lots of media (I have 7GB MP3's) can lengthen boot times. (~Theory is crapped all over with my SGS2 but some people have mentioned this fact).
The problem here is not at the loading stage where the bootanim kicks in, it's the stage before with the static logo after GO GO GO.
My SGS2 literally loads and is ready to use in 10 seconds to OS and 30 seconds to functionality after media scan/widgets etc.
So what's my HD2 doing at the static logo screen? It basically doubles the entire loading time but from my little knowledge, nothing actually happens until the bootanimation? I don't like waiting up to 2 minutes to be using my phone.
I hear CLK has a faster boot option. In anyone's opinion, have they sorted data out enough to come away from MAGLDR?
Thanks in anticipation of any responses.
Click to expand...
Click to collapse
Don't remember stuck with GO GO GO for long in my Mag days. I am now on cLK, and from the second boot onward, my phone is usable within 45 seconds - this is with a lot of apps, most of with run all the time right from boot.
I am using MAGLDR with Tytung's Nexus HD2 v2.9 build and it takes about 45-50 seconds to load. Much faster than when I was using Cmylxgo's TMOUS Froyo build which took a little over 2 minutes to load for comparison.
ph03n!x said:
Don't remember stuck with GO GO GO for long in my Mag days. I am now on cLK, and from the second boot onward, my phone is usable within 45 seconds - this is with a lot of apps, most of with run all the time right from boot.
Click to expand...
Click to collapse
It's not stuck at GO GO GO, it's stuck at the static boot image for a while, then the animated boot logo begins. Maybe it's the fact the phone looks like it's doing nothing while it's showing the static boot logo but like I mentioned above the SGS has the same amount of media and also it has the same apps as the HD2 and it's usable in under 30 seconds.
Thanks for the response anyway.
dkl_uk said:
It's not stuck at GO GO GO, it's stuck at the static boot image for a while, then the animated boot logo begins. Maybe it's the fact the phone looks like it's doing nothing while it's showing the static boot logo but like I mentioned above the SGS has the same amount of media and also it has the same apps as the HD2 and it's usable in under 30 seconds.
Thanks for the response anyway.
Click to expand...
Click to collapse
If you want to experiment, try Tytung's Mag kernel - get it from his thread and flash it. Mind you, ensure it also has the wifi drivers (bcm4329.ko), else wifi may not work. In my experience, Tytung's implementation of his Kernel boot faster.
Also, CWM 4.0.0.0 is not supposed to be stable (has something with backup/ recovery). Get the latest, or go with 3.2.0.0
I had the same problem when I was using that rom.
I tried to find the prob using logcat, and I saw a lot of errors being thrown at me, and also quite a few a2sd zipalign's, so I removed a2sd scripts from init.d, it started booting faster; but I still had the other errors.
ph03n!x said:
If you want to experiment, try Tytung's Mag kernel - get it from his thread and flash it. Mind you, ensure it also has the wifi drivers (bcm4329.ko), else wifi may not work. In my experience, Tytung's implementation of his Kernel boot faster.
Also, CWM 4.0.0.0 is not supposed to be stable (has something with backup/ recovery). Get the latest, or go with 3.2.0.0
Click to expand...
Click to collapse
Thanks for the heads up. I obtained that version of CWM through the HD2 Toolkit, and so far I haven't had any issues using it for the last few months.
Assuming I find the Kernel you've pointed me to, would it not be in CWM flashable mode and therefore i'd just be overwriting the zImage and not actually flashing a new ROM - therefore keeping my current /system (and bcm4329.ko)? Apologies if that was literally the most noob statement you've ever seen.
Moon2 said:
I had the same problem when I was using that rom.
I tried to find the prob using logcat, and I saw a lot of errors being thrown at me, and also quite a few a2sd zipalign's, so I removed a2sd scripts from init.d, it started booting faster; but I still had the other errors.
Click to expand...
Click to collapse
I actually have live logcat bootanimation and I am pretty sure i've seen a lot of errors too. It goes too fast to debug anything, and i've not taken the next step which is of course to do what you did and actually read the logcat, but these errors take milliseconds during the boot phase and I don't believe it's this bit that is the issue - it's the bit where the static logo shows and I don't truly know what the phone is doing at that stage.
Thanks for your helps also guys
dkl_uk said:
Thanks for the heads up. I obtained that version of CWM through the HD2 Toolkit, and so far I haven't had any issues using it for the last few months.
Assuming I find the Kernel you've pointed me to, would it not be in CWM flashable mode and therefore i'd just be overwriting the zImage and not actually flashing a new ROM - therefore keeping my current /system (and bcm4329.ko)? Apologies if that was literally the most noob statement you've ever seen.
Click to expand...
Click to collapse
The Mag and the cLK version of the kernel are here- use the one that says 2.3.4 only, even if you or on 2.3.5
I use this in cLK, and know for sure that the required Wifi drivers are in it. Note that the cLK version has cedesmith's data wrapper b5, but the b4 wrapper works better for me. This is in case you choose cLK, and are having data issues after flashing the kernel.
http://forum.xda-developers.com/showpost.php?p=10429937&postcount=3
ph03n!x said:
The Mag and the cLK version of the kernel are here- use the one that says 2.3.4 only, even if you or on 2.3.5
I use this in cLK, and know for sure that the required Wifi drivers are in it. Note that the cLK version has cedesmith's data wrapper b5, but the b4 wrapper works better for me. This is in case you choose cLK, and are having data issues after flashing the kernel.
http://forum.xda-developers.com/showpost.php?p=10429937&postcount=3
Click to expand...
Click to collapse
That's literally the post I came across once I did a search based on what you'd already told me. Thanks for confirming further.
Timed my boot - was 35secs on the watch and 33secs according to logcat. To put things in perspective, I have trillian (5 accounts), gtalk, gmail, 3 email accounts, google+, current widget, CallRecorder, CSipSimple, ClockSync, DSP Manager, Easy Filter, Swype and Where's My Droid loading at boot - in addition to whatever Android loads (Maps, Calendar, Settings...)
dkl_uk said:
Thanks for the heads up. I obtained that version of CWM through the HD2 Toolkit, and so far I haven't had any issues using it for the last few months.
Assuming I find the Kernel you've pointed me to, would it not be in CWM flashable mode and therefore i'd just be overwriting the zImage and not actually flashing a new ROM - therefore keeping my current /system (and bcm4329.ko)? Apologies if that was literally the most noob statement you've ever seen.
I actually have live logcat bootanimation and I am pretty sure i've seen a lot of errors too. It goes too fast to debug anything, and i've not taken the next step which is of course to do what you did and actually read the logcat, but these errors take milliseconds during the boot phase and I don't believe it's this bit that is the issue - it's the bit where the static logo shows and I don't truly know what the phone is doing at that stage.
Thanks for your helps also guys
Click to expand...
Click to collapse
You have to use the following command to get logcat to make a file of it.
adb logcat > anyfilename.txt
ph03n!x said:
Timed my boot - was 35secs on the watch and 33secs according to logcat. To put things in perspective, I have trillian (5 accounts), gtalk, gmail, 3 email accounts, google+, current widget, CallRecorder, CSipSimple, ClockSync, DSP Manager, Easy Filter, Swype and Where's My Droid loading at boot - in addition to whatever Android loads (Maps, Calendar, Settings...)
Click to expand...
Click to collapse
At what point are you timing this boot from? Power on? GO GO GO? Splash screen?
If I were to time my boot from the animated boot screen then i'd say possibly 30 seconds too, it's just that for another 30 seconds it's sat on the static boot animation.
Also my launcher screen takes an awful amount of time to parse. You can definitely tell the HD2 is ageing when you compare it with the SGS2. I know it's in a class of its own but still, i'm beginning to lose faith in the longevity of my HD2.
I am on the same boat, I use aMAGLDR 1.13 + MIUI Rom and the boot process is very very slow.
I just timed it:
1. From T-mobile Stick together to go go go: 9 secs.
2. A static splash screen, black background and green HTC logo: 1min 52 secs.
3. From MIUI globe animation kicked in to locked screen: 29 secs.
So basically I have no idea why step 2 takes such a long time. Is there anyway to see any error msg during this stage?
I tried to remove SIM card and/or SD card, it is about the same, so I guess there is something happening in the NAND...
Thanks!
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.
Hello, This is my first post, and after a few weeks of unsuccessful struggle, I need help. I am hoping someone on here can assist me.
I have a Acer A500 tablet. Some time ago I arranged to get ROOT permissions, then I installed Ice Cream Sandwich, and I have been happy with it for the past 6 months.
But in the past few weeks it got slower and slower as I read online news, etc. It seemed like it was halting for a few seconds on internal memory accesses. I even noticed if I removed the adapter power cord it would speed up, but if the power cord was installed, it seemed to halt more often. Finally the tablet got so slow, it became too frustrating to use. I decided I needed to install a new kernel and system ROM.
I managed to install a JellyBean System ROM, and it booted ok, but I found this interface to be inferior to ICS for my tastes.
I then managed to install an ICS, but the WiFi would not work.
I then spent some time in the various forums, and downloaded every kernel and system ROM I could find. Various kernels seem to go with each type of System ROM.
I have tried different mixes of kernels, and System ROMs ranging from ICS, to Honeycomb 3.2 and Honeycomb 3.1. In all cases after installing the kernel and then the System ROM, I reboot the tablet, and the droid animation begins flashing on the screen and it just keeps flashing forever. Sometimes the flash rate changes from fast to slow, then back to fast again, but it repeats endlessly and never seems to complete the booting process.
Can anyone recommend a kernel and System ROM that support ICS, that are currently available for me to download.
If not, then how about Honeycomb System ROM and kernel.
Are there some steps I am missing that explain why the bootup droid animation continues endlessley and the boot never concludes?
I gratefully appreciate any insight anyone can offer.
Thanks,
Eric
ericdormer62 said:
Can anyone recommend a kernel and System ROM that support ICS, that are currently available for me to download.
If not, then how about Honeycomb System ROM and kernel.
Are there some steps I am missing that explain why the bootup droid animation continues endlessley and the boot never concludes?
I gratefully appreciate any insight anyone can offer.
Thanks,
Eric
Click to expand...
Click to collapse
Well, telling which rom is the best, is like asking a million questions, each with a different answer.
However, I "can" tell you what's going on with your tablet.
Generally, the android OS pretty much takes care of memory tasks and such pretty good. So the issue you have with the slow downs, is more than likely caused by;
a. Way too many apps running in the background.
b. A "rogue" or poorly programmed app.
c. Apps incompatible with the system. (usually TB related)
Your wifi issue you mentioned, is caused by;
a. Didn't do full wipes/formats before installing rom.
b. Used a backup and tried restoring old apps, possibly not compatible.
You're getting the little dead android guy, because that's the stock recovery, and it's missing some critical files from the OS. Or it doesn't match the bootloader version, or a combination of both. Or it's trying to boot some "update.zip" off your SD card, and it ain't working.
My advice, would be to use a rom by Ezterry or smaury or the "Slim" by ktmdave. These are as close to stock as you want. You can always flash a kernel from linuxsociety or ezterry later.
The roms by Civato, are also some of the best, but customized heavily in some areas, but great nonetheless.
If your tablet slows down, it's because of what I listed earlier. Also remember, restoring old data from a titanium backup, on a new rom, is pretty much a big NO-NO. Asking for issues.Sometimes that game data just has to go.
MD