Boot loop from the red eye [Droid 2 Global] - Droid 2 General

I rooted my D2G and installed clockwork recovery on it thru rom manger and was trying to install a theme from available droid 2 themes. It goes past the motorola logo and when It gets to the eye it keeps boot looping the eye. Does anybody know how I can fix this, i know it was quite stupid what i did since there isn't any roms or themes available for D2G yet? I also forgot to make an a backup. The theme i was trying was NexTheme Final Fission 2.12.

try to sbf if you are unable to do that than you might have to take it in. this has happened to me and i had to take it to verizon to get it replaced.

djsat03 said:
I rooted my D2G and installed clockwork recovery on it thru rom manger and was trying to install a theme from available droid 2 themes. It goes past the motorola logo and when It gets to the eye it keeps boot looping the eye. Does anybody know how I can fix this, i know it was quite stupid what i did since there isn't any roms or themes available for D2G yet? I also forgot to make an a backup. The theme i was trying was NexTheme Final Fission 2.12.
Click to expand...
Click to collapse
That theme is made for a Droid2 with Fission 2.2.1. ROM and wont work on any other ROM or phone.

Idk if the clockwork in rom manager will work correctly. I've only ever used koush's bootstrap bc the kernel is locked and regular clockwork doesn't work on the locked kernel. I have a D2 but the principle should be the same bc yours is an updated version of mine with a locked kernel as well.
Sent from my DROID2 using XDA App

Yea i just called verizon and played dumb. Since i got the phone on yesterday and i didn't even activated it. I told them i got my phone and i can't get it to boot to activate it. jeessuussjason: when u took your in did they say anything about being rooted anything? Like how can they check? i installed clockwork recovery on my but seems like the clockwork recovery got erased now too, it doesn't boot into to it, just regular stock recovery.
Learned lesson back up!back up! everything!

nope i played dumb too and said i tried to update it and got a boot loop you're within the 30 days so they should replace it no questions asked they will try to plug it into their computers but it obviously won't do anything

Related

[Q] Can't Install Custom Roms after using TBH 2.2 SBF

First off, I am very familiar with Custom Roms and Never had this problem before.
I had to use the 2.3.13 SBF bc I was in a boot loop from a theme. I am rooted again using rageagainstthecage and can access the ClockworkMod recovery. I have tried multiple times to install 2.3.15 deodexed from the TBH app with no success. ClockworkMod says the install was successful but under system info it states it is 2.3.13. I know that it is 2.3.13 odexed bc Tranquility causes a boot loop. Backup and Restore work fine but not zip files. Does anyone know why it will not install?
I think I just experienced the same thing. Had to use the same sbf last night. This morning I tried to install zapx and seems like nothing happened and I was back at stock. Also I cant get back into clockwork recovery.
SysAdmNj said:
I think I just experienced the same thing. Had to use the same sbf last night. This morning I tried to install zapx and seems like nothing happened and I was back at stock. Also I cant get back into clockwork recovery.
Click to expand...
Click to collapse
You probably need to bootstrap the system again using the koush's app, to get back into recovery.
I installed ZapX but I had network issues with the market. So i reverted using a backup.
I was able to get clockwork back and install a different rom and the rom took this time. Rubix .5 to be exact.
good news- full 2.2 sbf is available now. there are links in x development.
thanks but i think they removed the thread ?
SysAdmNj said:
thanks but i think they removed the thread ?
Click to expand...
Click to collapse
Yeah- they did. there are other android forums with links still. Or search for...
VRZ_MB810_2.3.15_1FF_01.sbf
on megaupload or hot file or one of those sites.

Help.. Can't get phone to boot to recovery through rom manager

Everytime i tell it too boot into recovery it just shows the little android guy with a triangle and exclamation and then reboots. I've installed bootstrap and run clockwork recovery. What am i doing wrong? last time i did this and was able to manually go into recovery but when i flashed a rom i just got stuck at motorola bootscreen and had to use sbf. Please enlighten me someone.
Ok.. i tried skipping clockwork and just booted into recovery through bootstrap.. Works. I try and flash a rom and the orange bar comes up and says it's installing. The bar never fully goes across but it says the installation is complete. When i try and reboot to try the rom i get stuck at the boot screen. Any ideas what is going on?
boredmug said:
Ok.. i tried skipping clockwork and just booted into recovery through bootstrap.. Works. I try and flash a rom and the orange bar comes up and says it's installing. The bar never fully goes across but it says the installation is complete. When i try and reboot to try the rom i get stuck at the boot screen. Any ideas what is going on?
Click to expand...
Click to collapse
are you using 2.2? what ROM? you need to run the bootstrap once for it to work, and it will say clockworkmod installed is version 2.5.0.7 in ROMManager thats the bootstrapped version of clockwork mod.
then download the ROM, and don't touch anything after you hit the ok button on the screen that asks to backup current ROM and wipe user data. just let it work.
The system info says 2.1update1. I did as you described. I just used bootstrap to boot to recovery and tried flashing a rom and it does the same thing. Just sits at the motorola bootscreen. I'm gunna try my nandroid recovery to go back to the rooted stock rom.. I really don't know what to do from here though because neither way is working for me.
Also, my clockworkMod Recovery is v2.5.0.6 not .7. Maybe this is the issue? when i used rom recovery it said i had the most recent version. I'm Nandroiding right now which seems to be working.
boredmug said:
The system info says 2.1update1. I did as you described. I just used bootstrap to boot to recovery and tried flashing a rom and it does the same thing. Just sits at the motorola bootscreen. I'm gunna try my nandroid recovery to go back to the rooted stock rom.. I really don't know what to do from here though because neither way is working for me.
Also, my clockworkMod Recovery is v2.5.0.6 not .7. Maybe this is the issue? when i used rom recovery it said i had the most recent version. I'm Nandroiding right now which seems to be working.
Click to expand...
Click to collapse
you should update to version 2.2
check http://rootzwiki.com/ it has the files you'll need
ok. Thanks. Maybe this is the problem? I'm trying to flash a 2.2 rom and currently have 2.1 on my phone? So i've already done sbf back to 2.1 once last night. I'm assuming this procedure is pretty much the same. I'm guessing i will have to reroot my phone. Can i use the same method as 2.1 or is there another method for the droid x with 2.2? Thanks for the help!
boredmug said:
ok. Thanks. Maybe this is the problem? I'm trying to flash a 2.2 rom and currently have 2.1 on my phone? So i've already done sbf back to 2.1 once last night. I'm assuming this procedure is pretty much the same. I'm guessing i will have to reroot my phone. Can i use the same method as 2.1 or is there another method for the droid x with 2.2? Thanks for the help!
Click to expand...
Click to collapse
just check the website i posted, it has guides for everything you need
well.. Now i have 2.2 on my phone but no root. adb can't find my phone.. WTF
Thanks for pointing me in the right direction. Was finally able to get it all working. Now I have a working 2.2 custom Rom and can proceed with flashing this thing to cricket. Kinda sucks because I'm doing all this for a friend and using this phone I've kinda come to the conclusion that its a better made phone than my evo. Colors look better on the lcd, camera takes better pictures and the aluminum case is certainly nice too. Only drawback I see is the dev. Much more development for the evo, but then again it is an older phone.
boredmug said:
Thanks for pointing me in the right direction. Was finally able to get it all working. Now I have a working 2.2 custom Rom and can proceed with flashing this thing to cricket. Kinda sucks because I'm doing all this for a friend and using this phone I've kinda come to the conclusion that its a better made phone than my evo. Colors look better on the lcd, camera takes better pictures and the aluminum case is certainly nice too. Only drawback I see is the dev. Much more development for the evo, but then again it is an older phone.
Click to expand...
Click to collapse
I like my DX and it does have a few advantages over the EVO (e.g. battery life and build quality). However, I would gladly trade it for an EVO, since that device has 4G access, a front camera, cyanogenmod support, more accessible bootloader, etc.

recovery crashes and roms not loading?

ive been trying to back up my current rom with rom manager and everytime its backs up the rom and when it goes to start up again it crashes and the screen goes hay wire. also when i tried to boot the gingerbread roms on my phone it says "installation aborted" then the screen goes hay wire and it just loads up the phone as if nothing happened.
so im not really sure what to do, i was able to load a beta gingerbread the other day and it worked fine but when i went to sample the others i started having problems. hope i didnt break my phone
Having same issue
evo, It's the poop!
Same problem here..but I don't think the evo is poop lol
Its not the evo, its the new clockwork and rom manager. It is seriously screwing up everybody's phone that is using it. If your phone doesn't have the new partitions that are coming out with the latest phones then clockwork won't work properly. The developer needs to pull it from the market before there is revolt. Try to flash aman ra 1.8 and hopefully you will be able to flash again. If you have the hboot 2.02 or 2.10 you need to find the modified aman ra recovery to properly flash.
damn i had a feeling there was something fishy goin on with the plethora of updates they recently had -____- well hopefully they get it fixed cuz this is seriously tickin me off haha. hopefully this doesnt do any damage to my phone tho. i love this thing to death
http://forum.xda-developers.com/showthread.php?t=894331
how do i get amon_ra on my phone?
I have the new hboot and the new clockwork and it wont flash a lot of zips. Just aborts them. What is the easiest way to get modified amonra and flash it without a computer lol.
evo, It's the poop!
I went up to CWM 3.0.0.0 and ran into tons of issues similar to what you said. I mostly had bootloops and force closes in both AOSP and Sense roms.
I got back to CWM 2.5.1.2 and all is good. Get back to an older version if you can till this gets sorted out.

Tranquility just about killed my phone - any theories?

So I decided to give Tranquility a test and see how it compares to my currently running ApeX. I followed the usual procedures, data wipe/factory reset.....twice.
then installed TranQ and the TranQ App update.
The phone then boots up and freezes on the animation screen. So i reset it, then it won't boot at all past the Logo screen. Randomly it decides to boot up fine, but then 30 seconds of android and it reboots and freezes up.
So for some reason it won't let me boot into clockwork recovery, so i decide to just do the system only SBF it and be done.
So I've SBF'd it twice now, the first time it did a random restart and froze, and also kept the tranq boot animation. I did the 2nd sbf and it's got rid of the animation screen and back to droid, however the tranq boot logo is there.
I haven't proceeded to reactivate the phone yet, and just leaving it alone it hasn't restarted itself. I'm planning on rerooting and reinstalling clockwork recovery and see if i can get one of my old backups going.
But, any theories to what would have jacked it up so bad? and why the stock moto logo wasn't put back when SBF'ing?
update:
rerooted just fine using Z4, installed clockwork recovery just fine too.
Right now I'm doing a data wipe and reinstalling ApeX 1.3.1 from scratch from clockwork recovery. Then I'm gonna restore one of my backups.
Hopefully all goes well
update:
recovered to my backup just fine. Still didn't get rid of the tranq boot logo, thankfully i had a zip stored away of the stock logo so I installed that.
All is now well in the world.
Lesson from this......if it's working fine, leave yo sht alone!
Logo is stored in different place then a system sbf will update. That's not tranQ 's fault. I still use gummyJar though. Too much blur in TranQ for me
I had the exact same problem when I went from fission to tran q. I literally had to do the. 320 sbf then the. 340 sbf to get tran q to install right. Didn't like it and put fission back on
yea i had to do the same thing comming from fission, and because of it i am just staying on tranquility until Obsidian is more stable, then GOODBYE BLUR :-D
The trick to installing TranQ is to install it over stock. If you try to install it over another custom ROM you will have nothing but problems.
Sent from my DROIDX using XDA App
davidukfl said:
Lesson from this......if it's working fine, leave yo sht alone!
Click to expand...
Click to collapse
I feel your pain, but you shouldn't be discouraged (as long as you Nandroid, Nandroid, Nandroid!).
I also spent a week fiddling with TranQ before giving up due to random reboots. But I went ahead and installed GummyJar. It was worth it!
When you're ready to climb back onto the horse, you should try GummyJar. If you prefer a no-bur ROM, it's probably the best in terms of speed and stability.
well i had tried Gummy before, but it was a little buggy for me. Phone would restart after calls, hardware buttons wouldn't always work and a few other little things.
I actually just switched to Fission and it's pretty brilliant thus far. No problems at all, and the fission manager helps a lot
fmkaiba said:
Logo is stored in different place then a system sbf will update. That's not tranQ 's fault. I still use gummyJar though. Too much blur in TranQ for me
Click to expand...
Click to collapse
IT IS TranQ's fault. It is the only ROM that does this. Before you get rid of Tranq, you have to go in to the tools and set your boot logo back to stock. I have flashed many different ROMs and it is the ONLY ONE that makes sure to "leave its mark," LITERALLY.
had same problem when I went from fission. I had to sbf .32 then sbf .34 then did the tran q and it worked just fine after that. I didn't like it to much so I went back to fission. To get rid of the tran q I just did the same sbf method I did and went back to fission.
z06mike said:
IT IS TranQ's fault. It is the only ROM that does this. Before you get rid of Tranq, you have to go in to the tools and set your boot logo back to stock. I have flashed many different ROMs and it is the ONLY ONE that makes sure to "leave its mark," LITERALLY.
Click to expand...
Click to collapse
You're right on w/this..Its too bad I found out the hard way..

MIUI on my DX - And my DX experience so far.

Hey guys, I just wanted to share my experience so far. I can't post on the MIUI page because I don't have enough posts, so I'll share here for anyone interested.
For anyone wanting to try MIUI for the DX, here's my experience, some tips, and suggestions.
-Beware, installing or trying to install ANY ROM may brick your phone. although it's very rare and unlikely to be unable to find a solution to problems, it can and has happened. so take caution and read instructions and so-forth carefully.
Some history of my DX. I soft-bricked my phone back in the early months of the DX trying to deodex it to install themes. It was stuck on M logo for 2 days before i learned enough from scratch to find out what an SBF was, where to find it, and how to flash my phone back to stock. Ever since then these nice folk on XDA-developers forums and other droid forums have helped me successfully mod my phone many times, through Q&A, detailed instructions, and a little luck.
I've rooted my phone using the command method, Z4Root, and several other processes. Some were hard to figure out, some soft-bricked my phone, most were easy as pie. I'm on a Z4Root atm.
The first successful ROM I installed was GUMMY-JAR. I liked it, it was good to me. nothing like the comprehensive ROMs out now though.
Then I jumped to Liberty 1.5, Liberty x.x etc... Liberty was awesome, but was still basically Froyo with advanced options. I loved it.
Now, just today, I've installed MIUI. And let me tell you, its amazing!
For anyone running Froyo Liberty ROMs, I believe that you can install MIUI right over the top. I didn't think it was going to work, as I hadn't seen anyone mention if it did or not over the top of Liberty 1.5.
If you want to install MIUI, go here. http://forum.xda-developers.com/showthread.php?t=1181486
You MUST be rooted, and be running FROYO, NOT GB! You must also have the Droid X bootstrapper.
I won't give instructions, as I'm not qualified to do so. But I can tell you what I did from Liberty 1.5. MAKE SURE TO MAKE A BACKUP FIRST! 1) I downloaded the MIUI ROM from the above XDA post to my SD card on my phone. 2) I clicked 'bootstrap recovery' on the DX bootstrapper app, then 'reboot recovery.' My phone booted into clockwork recovery mode. 3) wiped data/factory reset. 4) cleared cache. 5) install from SD Card. 6) install MIUI.zip i downloaded from the link i posted above. let it run it's course. rebooted. DONE.
It's really that easy if you are running the DX stock Froyo kernal.
Keep in mind with MIUI, it does NOT auto-sync your Google account. you need to go into the options>>accounts/sync and add your Google account. You can then re-install apps from your backup or just re-download them. Make sure you've synced your contacts with your Google account so they will be there when you add your Google account.
Some thoughts on MIUI...
There is NO STOCK APP DRAWER. I recommend ADW launcher or Launcher PRO. The MIUI launcher inst bad, but it's like iOS in that there's no app drawer. It's just a bunch of screens with all your app icons like an iPhone.
You can download theme's and customize themes through settings>>personal>>theme manager. MIUI allows you to change fonts, boot animation, boot audio, lock-screen style, status bar, icons, launcher, wallpapers, text style, dialer style etc. There's tons of pre-made packages, but you can also change them all individually and create one you like best. You can do all of this directly from the settings menu including looking up new themes, downloading them, and applying them.
MIUI is running on 2.3.4 GB. So it wont say 2.2 anymore after you install. (I believe the kernal is still Froyo though? Please correct me if I am wrong)
I really hope this helps some of you newbies. I am thankful for all of you that have made posts like this that I have found useful in the past.
Note- some people are having issues installing MIUI. They are getting bootlooped on the M logo for some reason. I have no idea why this is, it worked perfectly for me first try. Just remember to follow the instructions on the ROM page, and that you are running the correct version of Android. You shouldn't get a boot-loop if you do so.
Hope this helps!
i have a question.... and this question is what will decide if i keep this or go back to liberty gingerbread....
how the hell do i flash anything.. i can't even install clockwork mod without getting bootloops.... and i'd love to flash certain apps onto this.... but if this can not be done i will have to go back.... the only thing going into recovery does is use the retarded original recovery... and that is a big deal.. if i ruin my phone on the go and need to pullup a backup i can not do this with this rom and i will end up phoneless until i can get to a computer to sbf
nosboost300 said:
i have a question.... and this question is what will decide if i keep this or go back to liberty gingerbread....
how the hell do i flash anything.. i can't even install clockwork mod without getting bootloops.... and i'd love to flash certain apps onto this.... but if this can not be done i will have to go back.... the only thing going into recovery does is use the retarded original recovery... and that is a big deal.. if i ruin my phone on the go and need to pullup a backup i can not do this with this rom and i will end up phoneless until i can get to a computer to sbf
Click to expand...
Click to collapse
What exactly are you asking? "Flashing" is the process of basically overwriting your current Android OS with an Android OS SBF. If you are trying to install MIUI, you cannot do it with Gingerbread installed on your phone. "You MUST be on CyanogenMod 7 or .340 Froyo to flash this rom!" (MIUI)
If you want to install MIUI, i think the best bet would be SBF flashing to stock DX 2.2 .340 FROYO, re-rooting, then using the DX boot-strapper to boot into recovery. Then installing the MIUI .zip from SDcard in the recovery menu. Everything should work fine after that. Rmember you CANNOT go into recovery using DX boot-strapper once this ROM is installed. you CAN go into recovery with this ROM using ROM-manager. This is what I have experienced so far, and what others have said also.
no.. i already have the rom installed... i just want to be able to go into recovery without needing to be booted up.
i'm trying to install some zips through clockwork such as the old blur camera and a few other things... i will install rom manager and see how it goes from there... i love the UI of this rom but as far as being comfortable and stable.. liberty gingerbread has my vote as of now
i've cleared my cache and data several times and i get force closes alot. and this is a clean install coming straight after an SBF.
with liberty gingerbread i had the ability to set it so every phone reboot, even if a battery pull, would boot directly into clockwork mod.. making it easy for me in case i installed a zip that would get me into bootloop
Hmm, sorry mate, I dunno what to tell ya. Try looking aroudn forums or startign a new thread. someone more knowledgable than you or me will help you out.
thanks for everything though!! this really is a beautiful rom and i'd love to stick with it... i'll bite the bullet for the meantime and post around to get some help... i'd love to post in the developer section but i don't have enough posts yet.. haha
nosboost300 said:
no.. i already have the rom installed... i just want to be able to go into recovery without needing to be booted up.
i'm trying to install some zips through clockwork such as the old blur camera and a few other things... i will install rom manager and see how it goes from there... i love the UI of this rom but as far as being comfortable and stable.. liberty gingerbread has my vote as of now
i've cleared my cache and data several times and i get force closes alot. and this is a clean install coming straight after an SBF.
with liberty gingerbread i had the ability to set it so every phone reboot, even if a battery pull, would boot directly into clockwork mod.. making it easy for me in case i installed a zip that would get me into bootloop
Click to expand...
Click to collapse
You need to install Rom Manager, and select flash Clockwork Recovery. Make sure you select Droid X (2nd Init). Then you can reboot into recovery with Rom Manager :-D
laxattack said:
You need to install Rom Manager, and select flash Clockwork Recovery. Make sure you select Droid X (2nd Init). Then you can reboot into recovery with Rom Manager :-D
Click to expand...
Click to collapse
but the problem is that i would like to be able to go into recovery without having to do it through an app... i'd like to make it so every reboot (including battery pull) makes it boot into recovery. thats how i had liberty gingerbread doing it... if not.. i can live with it.. i'll just be a little more careful on what i'm installing
Just wanted to chime in about MIUI rom, I just flashed it yesterday and am ABSOLUTELY loving it thus far. I had no trouble at all installing the rom what-so-ever. I used ROM Manager to do the whole thing: downloaded newest ver. of MIUI, backup current ROM, wipe data and dalvik. Let it run its course and it rebooted and was up and running in no time flat!

Categories

Resources