So, I SBF'd 2.3.4, rooted, and flashed Eclipse 1.2rc3. Ran great. Today, I accidentally hit recovery in Eclipse Parts without installing it first. Now it loops at the Eclipse boot animation. First try: factory reset and wipes, flashed Eclipse again- same problem. Second try: factory reset, SBF'd again, root, wipe, flashed Eclipse- same problem. I don't know what it could be. Suggestions? Any help is greatly appreciated.
Very strange.
Did you try a fresh download of the rc3 zip? Maybe bad download? Rare but I hear it happens.
how long was it at bootanimation? Mine played the eclipse bootanimation for almost ten minutes when I first flashed it.
ashclepdia said:
Very strange.
Did you try a fresh download of the rc3 zip? Maybe bad download? Rare but I hear it happens.
how long was it at bootanimation? Mine played the eclipse bootanimation for almost ten minutes when I first flashed it.
Click to expand...
Click to collapse
Yes, I got new downloads of the SBF and Eclipse. I should clarify: from reflashing and doing a new SBF, I'm able to access the phone once. After doing a single reboot, the phone then bootloops and I'm forced to do a factory reset/start the process all over because it will sit at the boot animation for forever. Previously, I had no problems. Ran 2.3.3 with the latest Eclipse and did all necessary steps in transitioning to 2.3.4. I have no idea what to do.
[edit]
The issue may have been resolved. I did another factory reset and have been able to reboot a few times without a bootloop, so far.
Thread closed @ OP request.
Related
Im very dissapointed, my Streak has gone to silicone heaven and there is no reason for this either.
I got up this morning, got dresst and went to work as normal, I noticed my Streak vibrated in my pocket so when I got to work I had received a text so I proceed to unlock the device only to find it lagging to death and generally un-responsive.
This cleared and I started writing my responce to the text and the haptic feedback stopped and then the phone became fully un-responsive, so it was time for a bettery pull, I did this a further 3 times as it kept locking up (I though it was due to a media player I installed from the market last night so was going to uninstall it but it wasnt in the list of installed apps)
Then after the 3rd reboot I was then stuck at the boot screen and it would not go any further, I have gone into the recovery menu, cleared partitions etc etc and still its the same, I have also flashed back from DJ_steve 1.6.1 to 1.5.1 in the vein hope that it was something to do with 1.6.1, but no still the same.
Im going to try and put a stock rom on there and see what happens (as im able to flash etc etc it just seems to be when something is initializing during boot)
Im just wondering if anyone else has had this issue?
Try going to 1.5.1, allow it to boot fully. Go back into Recovery and do a factory reset. Option 4 in the Dell Menu, not StreakMod/ClockWorkMod. Allow 1.5.1 to fully boot up again. Go back to recovery and then flash 1.6.1 Hopefully this should get you up and running again. Do remember that 1.6.1 will take a while to boot up the first time.
Edrill said:
Try going to 1.5.1, allow it to boot fully. Go back into Recovery and do a factory reset. Option 4 in the Dell Menu, not StreakMod/ClockWorkMod. Allow 1.5.1 to fully boot up again. Go back to recovery and then flash 1.6.1 Hopefully this should get you up and running again. Do remember that 1.6.1 will take a while to boot up the first time.
Click to expand...
Click to collapse
Hi Edrill, thanks for the response, I have flashed 1.5.1 back on and factory reset, at 1st it didnt work but I tried again and was in the front room and I heard my alert tone back up and running on 1.5.1 think ill stick with that for now as its 2.2 anyways.
Thanks again bud.
No problem! Glad I could help.
Now that you've got a factory-resetted phone, going up to 1.6.1 shouldn't create any issues really. Just that the first boot after flashing 1.6.1 may take unusually longer than the first boot on any previous build, is all.
Edrill said:
No problem! Glad I could help.
Now that you've got a factory-resetted phone, going up to 1.6.1 shouldn't create any issues really. Just that the first boot after flashing 1.6.1 may take unusually longer than the first boot on any previous build, is all.
Click to expand...
Click to collapse
Ive opted for 1.5.3 for the time being, I had that for a few weeks without any issues so going to stick to that and see how the phone goes.
For now she's up and running without any issues *touches wood*
I was running eclipse ver 1.3 on my phone and decided that i wanted to sbf in order to get the next version of the ROM. everything went fine (sbfing to 2.3.4, then flashing the 2.3.5 412 build) then i flashed the eclipse 2.0.2 rom and the phone bootlooped. pulled that battery, factory reset from recovery and nothing happened and it kept bootlooping through the eclipse bootanimation. i had a nandroid backup from the day before that i restored to which brought my phone back to the way it was (rooted on 2.3.4 with eclipse v1.3 and all programs the same as they were) but when i applied a battery fix and rebooted it wouldnt stop bootlooping until i factory reset again, resulting in losing all my apps and going back to base rooted with eclipse 1.3.....altogether very confused about whats going on/ what i should do if i still want to get to eclipse 2.0.2
I'm wondering if the 2.0.2 Eclipse ROM image was bad? Try downloading it again and then see if it works.
Here is what I do starting from scratch:
Reboot into stock recovery and do a factory reset/wipe data/wipe cache
SBF to 2.3.4 stock
Apply 2.3.5 update via stock recovery (rename the 2.3.5 zip file to update.zip and store it on the external SD card)
Root 2.3.5
Apply BSR
Copy Eclipse 2.0.2 to external SD card
Reboot into BSR
Wipe data/cache
Apply Eclipse 2.0.2
I'm assuming that is pretty close to what you did, so that's why I'm assuming the Eclipse 2.0.2 zip file might be corrupted.
One more step you COULD do after applying Eclipse 2.0.2 is to again, wipe data/cache. It's not necessary, but I sometimes do that JUST to make sure everything is wiped out that needs to be before I reboot. Again, as long as you did it before you applied Eclipse, you should be fine.
yeah thats exactly the process. to be clear, BSR is bootstrap recovery? and ive already started downloading the zip again. also i noticed that the link from nitros thread is an eclipse ver 2.0.1, but the dl link for eclipse from http://forum.xda-developers.com/showthread.php?t=1391824 is ver 2.0.2 ... could that be an error or just that nitro hasnt updated the build yet? thanks for the quick response
wileydl527 said:
yeah thats exactly the process. to be clear, BSR is bootstrap recovery? and ive already started downloading the zip again. also i noticed that the link from nitros thread is an eclipse ver 2.0.1, but the dl link for eclipse from http://forum.xda-developers.com/showthread.php?t=1391824 is ver 2.0.2 ... could that be an error or just that nitro hasnt updated the build yet? thanks for the quick response
Click to expand...
Click to collapse
The link in the Eclipse thread hasn't been updated. The actual link was posted via his Twitter page.
You can get the actual 2.0.2 Eclipse from this link:
http://t.co/6MA95QBB
I *thought* I had a boot loop problem as well when I installed Eclipse 2.0.2, but that wasn't the case. Turns out I just didn't let the boot loading screen run long enough
First, make sure BEFORE you flash the Eclipse 2.0.2 rom that you WIPE CACHE and WIPE ALL DATA. Once those are both wiped, then install Eclipse 2.0.2. I'm sure you know that, just re-iterating.
Now reboot and you should be good. The Eclipse boot loading screen took 5-10 minutes before it finally finished and the phone started. At first I thought it was a boot loop because it was taking so long. The next time I got to this boot loading screen (after doing the entire SBF/Flash process over again), I just left the boot loading screen go. After about 5-10 minutes, it was good to go.
Just my 2 cents, but make sure you give the boot loading screen enough time for the initial boot
wesf90 said:
I *thought* I had a boot loop problem as well when I installed Eclipse 2.0.2, but that wasn't the case. Turns out I just didn't let the boot loading screen run long enough
First, make sure BEFORE you flash the Eclipse 2.0.2 rom that you WIPE CACHE and WIPE ALL DATA. Once those are both wiped, then install Eclipse 2.0.2. I'm sure you know that, just re-iterating.
Now reboot and you should be good. The Eclipse boot loading screen took 5-10 minutes before it finally finished and the phone started. At first I thought it was a boot loop because it was taking so long. The next time I got to this boot loading screen (after doing the entire SBF/Flash process over again), I just left the boot loading screen go. After about 5-10 minutes, it was good to go.
Just my 2 cents, but make sure you give the boot loading screen enough time for the initial boot
Click to expand...
Click to collapse
10 minutes I would say is the longest I have waited
motcher41 said:
10 minutes I would say is the longest I have waited
Click to expand...
Click to collapse
Yeah, definitely longer than I thought it would be.. sometimes I'm too impatient with these things
Just so everyone knows what a REAL bootloop is:::
When in an ACTUAL BOOTLOOP you will feel the haptic feedback(little vibrate pulse before your locksreen comes up)
Then u MIGHT even make it to the lockscreen.
But from there the phone will seem to lock down and shut itself off
then it will start back up again.
U might even see the Motorola dual core splash screen again.
But it will go through this whole process multiple times if u are indeed bootlooping.
If you ONLY see the bootanimation but u don't feel the haptic feedback pulse or the screen doesn't get brighter like its about to take u to the lockscreen then BE PATIENT. You system is loading all new caches and building dalvik cache and actually "setting the system up" so it will turn on and run.
this can take anywhere from 5-15(longest I've had was what felt like 10 but more likely was like 5-6mins) minutes.
And if you pull the battery during this "initial boot" after installation then you are almost guaranteed to bootloop. Since the system wasn't done completely installing and u interrupted it.
patience is key on the initial boot after installing a rom.(or after wiping data or dalvik cache..)
Ok, simply out of frustration I have exhausted all my options and my phone is acting weird I think. I did the factory reset, tried fruitcaking, and even doing sbf. I am at a stock 2.3.4 however when I want to upgrade to try different roms it is extremely unstable and I always get boot loops. Yes I did try the wiping caches and everything before and even after.
So my question is am I doing something wrong? I had even relocked my device from sbf and unlocked it again by cleaning my device. My phone is rooted and unlocked stock rom atm. I'm not sure what to do at this point but either throw the phone at the wall or sell it.
Please help thanks. I tried searching but I believe my situtation is different.
Let me note that I was able to run the Alien rom just fine on my atrix it is 2.3.4 based I believe.
Have you tried the fastboot wipe option? http://forum.xda-developers.com/showthread.php?t=1421522
I've been using this as of late as some of my flashes (even factory resetting in recovery) have had lingering settings and artifacts.
I will definetely try this when I get home. Thanks I'll keep this updated.
Either it wont boot and it just restarts or it starts to boot and wont complete the process its just an endless loop. I have had it on ICS before but for some reason it took over 20 bootloops and it finally showed... I'm not sure where to start.
bump, that method doesnt work... I still need help any other alternatives please..
Are updating roms on romracers latest recovery or old recovery versions?
I have my phone rooted and BSR/busybox/superuser installed. How do I flash it and actually put the rom on the phone?
(P.S. Its eclipse 2.1)
Well you have a lot of reading to do but let me give you a few important tips:
1) Before doing anything else make sure to go into your BSR and make a nano back up of your stock system. If you do not know how to do nano back ups then read up on that. You will be doing that for different roms. http://forum.xda-developers.com/showthread.php?t=1318083
2) Make sureyour kernal matches the version of the rom. For example you want to flash eclipse 2.0+ this is made for 2.3.5 update. If you are stock you are probably 2.3.4 Some have flashed eclipse 2.0+ and had no issues but it is not recommended.http://forum.xda-developers.com/showthread.php?t=1313103
this thread should help you out a lot also.
3) Once you get your stock Rom backed download the rom of your choice onto your sd card. Go back into BSR and first wipe data factory reset, wipe partion cache, go into advance and wipe Dalvik cache. Once you wiped the big 3 go to install from sd. Locate the rom using your volume buttons and power button to select. Sit back and let the rom run. Once it is done you can reboot now or flash one more safety step. It is the rerecovery zip. This actually allows you to restore your phone easy in the case of something bad happens. If you boot loop or something goes wrong then you just pull your battery and give it about 30 seconds. Put the battery back in and leave the phone off and just plug it into the wall charger. This will bring you straight to BSR. Here is that link http://forum.xda-developers.com/showthread.php?t=1426062
Also remember as long as you can get into BSR you can restore your nano backup of choice. Good luck and have fun. If you run into trouble we can help you out. The phone is pretty easy to fix.
I have made my recovery but was told it is ok to install Eclipse 2.1 on 2.3.4. I have the file downloaded but am I going to have to reprogram my phone for service?
If I'm not mistaken, flashing eclipse 2.1 on Android 2.3.4 can cause some Wi-Fi and data problems, so I highly recommend sbf-ing android 2.3.5 before flashing eclipse. Ill link a comprehensive sbf guide at the end of this post. To answer your question, though, you shouldn't have to activate your phone again if you havent sbf-ed or updated android. If you do decide to use 2.3.5, you will have to activate your phone again, though it only takes about 30 seconds in my area (could take more or less time depending on your signal strength).
http://forum.xda-developers.com/showthread.php?t=1317707
Hope I could be of assistance. If you need help, feel free to ask. I have no life so ill be here all day.
theredvendetta said:
If I'm not mistaken, flashing eclipse 2.1 on Android 2.3.4 can cause some Wi-Fi and data problems, so I highly recommend sbf-ing android 2.3.5 before flashing eclipse. Ill link a comprehensive sbf guide at the end of this post. To answer your question, though, you shouldn't have to activate your phone again if you havent sbf-ed or updated android. If you do decide to use 2.3.5, you will have to activate your phone again, though it only takes about 30 seconds in my area (could take more or less time depending on your signal strength).
http://forum.xda-developers.com/showthread.php?t=1317707
Hope I could be of assistance. If you need help, feel free to ask. I have no life so ill be here all day.
Click to expand...
Click to collapse
I have managed to softbrick my phone. No it is stuck on the "dual core technology" screen and I can't do anything
Spanks906 said:
I have managed to softbrick my phone. No it is stuck on the "dual core technology" screen and I can't do anything
Click to expand...
Click to collapse
Have you pulled you battery and tried it again? If you have I'd sbf back to 2.3.4 and then update to 2.3.5 then root it, and then install BSR and go into recovery and like said above, wipe the "big 3," install the ROM and then reboot and see if that helps.
Spanks906 said:
I have managed to softbrick my phone. No it is stuck on the "dual core technology" screen and I can't do anything
Click to expand...
Click to collapse
I tried installing it just now... It gets past the dual core but sticks on the ECLIPSE loading screen... wtf? any idea how to load the original os?
GaryMcDroid said:
I tried installing it just now... It gets past the dual core but sticks on the ECLIPSE loading screen... wtf? any idea how to load the original os?
Click to expand...
Click to collapse
Sbf back to 2.3.4....its not too hard. Search for it.
Sent from my MB870 using xda premium
I have been runnig CM9 for about two weeks. Really liked it.
Thought I would flash the build.props mashup. After I did I started getting the following message:
process com.android.phone is not responding. Couldn't do anything but pull the battery.
Plugged into power strip.
Went into CM7 Patched Recovery recovery. Wipe Cache and Dalvik. No change.
Wipe Data. No change.
Also ran Fix Permissions. No change.
Don't ask me why but I ran Key Test.. BAD MOVE. Couldn't get out of Key Test.
Pulled battery again.
Still plugged into power strip. Now I am stcuk at the red Motto M and can't get past it.
If I unplugged and reboot CM9 will start but again I get process com.android.phone is not responding.
Any help would be greatly appreciated.
The reason it messed up is because the mash up is already built into CM9 and probably has different tweaks by dragonzkiller. If you can still get into the recovery, try flashing the CM9 ROM zip again. It should overwrite the problem.
EDIT: Actually if you already wiped data, you may not be able to get into BSR. So if you cant get into the system, you may have to SBF. Unless you can use ADB to push BSR to the phone which I dont know how to do or even if it will work. I've never used that but read people talking about stuff like that.
If you cant fix it, follow the instructions here to reset your phone:
http://forum.xda-developers.com/showthread.php?t=1317707
Thanks - nnow on the root!
SBF worked fine. Thanks.
Back on 2.3.4. On to root, except my employer has blocked to down site..
and then on to CM7 and CM9.
Thanks again JS
jsgraphicart said:
The reason it messed up is because the mash up is already built into CM9 and probably has different tweaks by dragonzkiller. If you can still get into the recovery, try flashing the CM9 ROM zip again. It should overwrite the problem.
EDIT: Actually if you already wiped data, you may not be able to get into BSR. So if you cant get into the system, you may have to SBF. Unless you can use ADB to push BSR to the phone which I dont know how to do or even if it will work. I've never used that but read people talking about stuff like that.
If you cant fix it, follow the instructions here to reset your phone:
http://forum.xda-developers.com/showthread.php?t=1317707
Click to expand...
Click to collapse
Glad you got it back to working condition. Next time you have a problem like that, flashing the ROM again should take care of it. If not, try to always have a ROM backup on hand.
And also, stay away from mashup when on CM9 as well as the Test Keys function in CM7 recovery.
If I hadn't foolishly done Test Keys my next step was to flash the ROM again.
Thanks again.
jsgraphicart said:
Glad you got it back to working condition. Next time you have a problem like that, flashing the ROM again should take care of it. If not, try to always have a ROM backup on hand.
Click to expand...
Click to collapse