Phone always starts into recovery - Droid 2 General

I have rooted with Z4root, and droid 2bootstrap. My question is why does phone when restarted always go into recovery?

First, what exactly did you root with z4. ?It only worked on Froyo, since this is a recent post I have to make sure your not on GB.
That being said, I have had your problem before, solved it by running the bootstrap again, esp if I just reflashed something.
Another thing though, don't bootstrap of your on a 2nd init rom. Just use recovery through rom manager.
Sent from my DROID2 using XDA App

Related

Droid x recovery

Hey I'm going to root my brothers x later tonight using z4root and I was wondering if Rom manager would work on it I'm curious because I know the x and d2 has a fuse built in that will automatically brick it when trying to load a custom recovery so I'm just wondering if I should use Romm or get him to fork over 2$ for bootstrap recovery I do have experience rooting but just not newer droids
Sent from my HERO200 using XDA App
Get bootstrap, as ROM Manager doesn't work the same... nor have they added that feature last I checked. Since the recovery cannot be permanently written, the bootstrap method is required.
Sent from my DROIDX using XDA App
He can still install roms via choose zip from SD card right and do u have to flash bootstrap everytike u use it
Sent from my HERO200 using XDA App
When you use bootstrap, it will reboot your phone into Clockwork Recovery and you will be able to choose the options that Clockwork has always had, the only difference is that you do have to run bootstrap every time you want to use Clockwork Recovery. Install zip from SD is an option in Clockwork. You CAN run the bootstrap program, click the button to bootstrap but NOT the reboot button, then open ROM Manager and proceed as usual, but I prefer just doing all the work in Clockwork. Never use rom manager anymore.
Sent from my DROIDX using XDA App
Sweet so the set up is still the same I'm using clockwork on my hero and I don't have to flash it every time lol and in your opinion what's the best Rom yall have and what is the most stable overclock setting
Sent from my HERO200 using XDA App
Overclocking is trial and error. My first Droid X only was stable up to 1.25Ghz, but replaced due to dead pixel. My new one is very stable at 1.45Ghz with ultra low voltage settings. For me, the best ROM out is Fission 2.1... I didn't like Moto Blur so I love the vanilla Android feel that I had on my Droid 1. It's mostly about personal tastes, honestly.
Sent from my DROIDX using XDA App
You have to have dx bootstrapper and rom mgr. I use rom mgr almost exclusively, as it is very, very easy. I advise getting it.
Steven58 said:
You have to have dx bootstrapper and rom mgr. I use rom mgr almost exclusively, as it is very, very easy. I advise getting it.
Click to expand...
Click to collapse
Rom Manager is completely optional. For some, it's simplicity makes it a must have, but I almost never use it anymore. It wasn't available when I first got my D1, so I'm more comfortable with the manual processes. I will also use a terminal emulator to root a phone, instead of the 1-click options. Just posting to clarify that RM is nice, but not necessary.
Sent from my DROIDX using XDA App
I need to root my DX that I just got yesterday, came 2.2 pre-installed. I've been accustomed to my rooted D1 for so long and I know that the DX root process is different so I need some help.
I would like to just do a "1 click root method" if possible, but I can use ADB/SDK if that is the best way to root the DX, I got some familiarity with ADB. Also, I'm confused on this bootstrap stuff, etc.
In a nutshell, I want to be able to root my DX, use Clockwork Recovery (for backups, flashing roms, etc.), use Rom Manger, be able to unistall system apps, etc.
Thanks guys
- BUD
Yea dude I rooted my brothers dx this morning search the market for z4root its made for the droids on 2.2 it took it two tries but he got it oh yea its a free app good luck its one click
Sent from my HERO200 using XDA App
And for bootstrap u have to flash it every time u go into the recovery but its the same as clockworkmod but its nota perminate recovery screen that's how they bypass the fuse that will brick your dx
Sent from my HERO200 using XDA App
Bierce22 said:
And for bootstrap u have to flash it every time u go into the recovery but its the same as clockworkmod but its nota perminate recovery screen that's how they bypass the fuse that will brick your dx
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Ok, so because we have rooted, and are running as Superuser with Clockworkmod, each time we turn on or reboot it automatically comes up in the Recovery mod that we just reboot from so we don't brick our DX's? If that is correct then it explains a lot and it would also be something that I haven't seen written out. If it isn't correct can you explain why after rooting and installing Superuser and Bootstrap or Clockwork Recovery Mod when I turned on my D2G or rebooted it I ended up in the Recovery mode?
Thanks.
Here is my question. I have used the Rom Manager and currently running Rubix. I have tried to flash to another Rom to try to get the feel of them and Rubix keeps popping up. Do I need to delete it from my X to get the other ROM to load in?
rcnaimee826 said:
Here is my question. I have used the Rom Manager and currently running Rubix. I have tried to flash to another Rom to try to get the feel of them and Rubix keeps popping up. Do I need to delete it from my X to get the other ROM to load in?
Click to expand...
Click to collapse
I would always recommend an SBF in between roms. This removes any traces of the previous rom.
Sent from my DROIDX using XDA App
gio2005 said:
I would always recommend an SBF in between roms. This removes any traces of the previous rom.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
That's a bit overboard, isn't it? I've rooted and flashed a ton of phones, friends, family, Co workers. Only on some circumstances I had to sbf, but from my own doing.
Simple wipe data, cache within bootstrap clockwork recovery, does the trick. Follow the roms instructions. No need to sbf everytime.
Sent from my DROIDX using XDA App

[Resolved] dx moto logo boot error

hello all
sorry if this is in the wrong section.
today i decided i didnt like my old rom and tried to install fission using the fission rom manager. in the install screen, i forgot to check the wipe box by mistake.
now my phone WILL NOT go any farther than the white moto logo at the very beginning of the boot animation. Is there anyway I can fix this? i am not that experienced at this stuff, so a good explanation is needed. please help!
i just figured out how to get to (stock) recovery from boot, but even after wiping and retryin a few times, it still wont work....
i have also not upgraded or updated really anything since i got my phone months ago, except root, and deodex, and flyx rom
-matt
You won't lose root, and when you sign back into google all your apps will come back. Did you make a recent backup? If so you can use it from recovery
Sent from my DROIDX using XDA App
You can even wipe and reinstall if you still wanna try fission since you're in recovery.
Sent from my DROIDX using Tapatalk
google has all of my tons of apps? sik. but from recovery there is no option to restore/backup nandroid, like bootstrap
the options are reboot, apply sdcard update.zip, wipe data/factory reset, wipe cache partition
Oh you're in stock recovery... Just wipe and reboot.
Sent from my DROIDX using Tapatalk
well thanks for helping, but even after i wiped 3 or 4 times trying, it still desnt work. any ideas?
idk if fission requires 2.3.32 or somethin, but i dont think i hav updated anything since i got my phone a long time ago, just thought id add that
Try pulling the battery, should reboot to clockwork recovery when you put battery back in, then you can restore a backup or flash a rom from sd card.
Sent from my DROIDX using XDA App
mattmartin77 said:
well thanks for helping, but even after i wiped 3 or 4 times trying, it still desnt work. any ideas?
idk if fission requires 2.3.32 or somethin, but i dont think i hav updated anything since i got my phone a long time ago, just thought id add that
Click to expand...
Click to collapse
Most roms require .320/.340. You definitely wanna upgrade if you plan on flashing in the future.
Sent from my DROIDX using Tapatalk
well neither of those solve my problem, i am debating on whether on not to take it to verizon, but idk if they will even help me.
if you can get to clockwork recovery you can download a rom by computer and transfer to your sd card, or put your card in another phone to download it. Then flash that rom. Be sure to mount the system before flashing
Sent from my DROIDX using XDA App
Hi matt.. soon after getting my X, I got stuck in your situation while flashing a rom. I took it to verizon and after trying to troubleshoot it for a few minutes, they decided to just overnight me another one. I told them that I woke up and the phone was stuck at the M. I didn't mention anything about being rooted or trying to flash a rom.
The phone was also within the one year warranty though. You might want to try this route if all else fails.
Good luck!!
Sent from my DROIDX using XDA App
If everything else fails you can sbf. I'll pm you a link for the 2.2315 full sbf, just download rsd lite 4.8 and google how to do a sbf if your not familiar. Then you can do the official ota and be up to date
Sent from my DROIDX using XDA App
thnx everyone. ive never sbf'ed before, but ill give it a shot. i wish i could get to clockwork, it would make everything so much easier.
i triedflashing a new sbf, but rsdlite gives me the error- could not find initial values in the ini file or somthin... any ideas? its my fisrt time putting on a new sbf.
mattmartin77 said:
i triedflashing a new sbf, but rsdlite gives me the error- could not find initial values in the ini file or somthin... any ideas? its my fisrt time putting on a new sbf.
Click to expand...
Click to collapse
What version of rsd are you using? you can just sbf .320 full then .340 system only and it will be updated no need to sbf an old file.
i am using the newest rsd i could find. 4.9 right? and it seems as if i need pst_flash.ini according to the sbf installation instructions i found here
edit: hey thnx everyone for the help. i took it to verizon and the techs said it was a "complete software crash". yay i bricked my phone:/... the good news is that verizon is overnighting me a new one.
when i get it i am going to root it. i also want it to be the latest sbf or whatever its called so i can get either fission or gummyjar on there. now i need 2 more questions answered.
1. which option in about is the one that tells me what sbf im on?
2. i kinda need a really good tut on how to flash a new sbf and get it to .340 because i clearly failed miserably at it last time, so anyone have a link or willing to write it up?
It should have.340 on it or be ready to update. You can check by going to settings, about phone, build number. It should say 2.2.340
Sent from my DROIDX using XDA App
oh build number. thnx bro, so many confusing numbers, why cant there just be simple names? lol
Full SBF isn't out yet for 2.3.340 you will need the SBF for 2.3.320 and then the patches to get to 2.3.340. Keep it handy just in case!
yah i have the .15 sbf right now for safe keeping but i cant find the .32 or the .34 patch, but it isnt urgent since i heard that the new phone that is coming will be preloaded with the newest everything.
can i just use z4root to root my new phone? or do i have to do the doroot thing in adb like i originally did on my first dx?
I also wanted to know if i could use one of the kernels i saw in the fission rom manager with a rom other than fission, such as gummyjar.

Having Issues Installing Custom ROMs

Earlier, I mistakenly posted this thread in the Droid 2 global forums. This is where it shoud've been posted.
As you can see from the title of this thread, I am having problems installing ROMs on my rooted Droid 2. No matter which one I try to install (gummyjar, liberty, etc.), after I boot into recovery and follow the instructions for installing the ROMs, they don't; everything on my phone always looks the same as before. What might be the problem?
As a side note, Webroot, one of my mobile security apps, seems to quarantine the zip files a day or two after I download them. Might Webroot be the problem? Should I uninstall it and try installling these ROMs after doing that?
Try mounting system and data before flashing the roms. This sounds like it may be your issue.
Sent from my DROID2 using XDA App
How do I do that?
Sent from my DROID2 using XDA App
Did you
1. Root your phone successfully?
2. Install Koush Bootstrap and successfully bootstrap recovery?
3. Follow the directions correctly when installing the ROM's?
tattedupboy said:
How do I do that?
Boot into clockwork, select mounts and storage, then mount system and data. Then go install rom from sdcard.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Sent from my DROID2 using XDA App
Finally, success! What I was doing incorrectly all this time was not using Koush Bootstrap recovery for the recovery. I had been attempting to do that portion of the process from the ROM Manager instead. Thanks for the help guys.
P.S. the ROM I ended up installing was the Big DX Serenity. Except for it not enabling vibrate on keypress, I like it so far.
Sent from my DROID2 using XDA App
From what I hear, Liberty ROM is one of the quickest and most customizable ROM's out there right now. I was excited having just gotten Fission set up, but I think I'll be switching there.
Now that you've started swapping ROM's around too, you'll definitely want to be making backups of your phone. To do this, use Koush's Bootstrap to create a nandroid backup. This way, while trying out different things, you can try all sorts of ROM's with minimal hassle by just loading up your saved states.

[Q] What next?

So i ended getting stuck in a reboot loop while trying to use droid x recovery bootstrap. Ultimately, i used rsd lite and sbf 2.3.320. So the question is what next? i tried to get the ota gingerbread update from verizon by updating through my phone, but it says that it is up to date. Do i need to re root my phone and flash a current version of gingerbread.
I did make a full titanium backup before is crashed my phone. I am still a little root shy after my first experience.
Try rebooting a few times and checking again. You could always just do a Gingerbread SBF if need be, though.
Sent from my Transformer TF101 using XDA App
Thanks. i will try that. If i end up using a gingerbread sbf, do i need to be rooted? Otherwise, just follow the same sbf directions i used before?
SBFing does not require root, if that is what you're asking.
Sent from my Transformer TF101 using XDA App
I ended up sbf back to 602 and got an OTA update to 605. Then rooted with 1 click root. Reloaded app from titanium back up.
Feeling a little more comfortable with the whole rooting thing. I think i ended up in a boot loop because i used droid x bootstrap which is not compatible with gingerbread.
So now i want to make sure i understand what i am doing. droid 2 bootstrap will prevent my stock rom from loading and instead will allow me to replace the rom manually. Once i reboot, it will boot into the new rom. i downloaded rom manager which will essentially automate to process of using a new rom.
One question though. Can i use rom manager to back up the stock 605 rom and go back to that if i want?
Hope this noob is starting to learn
You definitely should be able to.
Sent from my Transformer TF101 using XDA App
From personal experience I have had problems with ROM manager on gingerbread...i would download Droid 2 bootstrap from the market and press (bootstrap recovery) then (OK) followed by (reboot recovery)
That should get you right into Clockwork mod Recovery without problems....then use the volume down button and go to (backup and restore) then just press your camera button to select backup...
Once finished just hit the back button and reboot and you should have a perfectly good Nandroid backup of your current system
Sent from my DROIDX using xda premium
Boarder277 said:
From personal experience I have had problems with ROM manager on gingerbread...i would download Droid 2 bootstrap from the market and press (bootstrap recovery) then (OK) followed by (reboot recovery)
That should get you right into Clockwork mod Recovery without problems....then use the volume down button and go to (backup and restore) then just press your camera button to select backup...
Once finished just hit the back button and reboot and you should have a perfectly good Nandroid backup of your current system
Sent from my DROIDX using xda premium
Click to expand...
Click to collapse
This is the method I use and it has worked fine.
Sent from my GT-i9100 using Tapatalk
Thanks for your help. I got the the phone running on liquid rom. Pretty cool. I guess the 2nd init roms only work on older, rooted versions for the dx? I will do a manual rom flash also, just to understand what i am doing with the rom manager.
Gadget_Guru said:
Thanks for your help. I got the the phone running on liquid rom. Pretty cool. I guess the 2nd init roms only work on older, rooted versions for the dx? I will do a manual rom flash also, just to understand what i am doing with the rom manager.
Click to expand...
Click to collapse
2nd init can work on either Froyo kernel based (older) or Gingerbread kernel (newer) roms.
Check the rom's thread to find out what kernel it uses and for installation instructions.
Sent from my Transformer TF101 using Tapatalk

did something dumb. help?

I had encounter ICS, which was great, but isn't ready to be a daily rom, so I use koush's app to reboot into recovery.
then I got stuck at the boot animation, so I decided to open up the stock recovery, and wiped data/factory reset like an idiot. So now all i have is stuck at the M logo, or stock recovery.
Am I going to have to use an official update.zip to flash, then root my phone again?
You are going to have to sbf.
Sent from my DROID2 using xda premium
okay, so I sbf'd back to stock froyo (only GB sbf I can find around the net is a megaupload link, which is obviously not very helpful nowadays) and let it do an OTA update to GB.
I then root, just like i have before, using the motorola one click root program on my computer.
I get root, install koush's bootstrap, and reboot into recovery. I then try to install libertyv3 2.0, which seems to go well...
until i reboot. once i reboot my phone, I'm stuck back at the bootloader, and can't do anything except SBF all over again.
seriously, what's going on? maybe this liberty .zip is broken or something? (i had to find a mirror, because A team gummy's site seems to be down, and B the only other official mirror is megaupload)
I'm going to try another rom, probably encounter ICS because i already have it on my SD card.
this time, I actually read the instructions and tried to install Liberty with clockwork recovery instead of koush.
still. effing. happening.
I reboot after flashing the zip and I can't get past the bootloader screen.
Code:
Bootloader
D2.37
Err:A5,69,35,00,23
Battery OK
OK to Program
Connect USB
Data Cable
I'm seriously at wit's end here. I just got this phone but a couple days ago after I lost my original. it's an insurance replacement. I rooted with the moto one click root, and used koush to install encounter ICS. after not knowing about encounter's wonky way of activation the custom bootloader, I mistakenly wiped the phone with the stock bootloader. I SBf'd back to stock froyo, then OTA updated to gingerbread.
That is my entire history with this phone. what the hell could possibly be wrong with it?
Do you wipe data/cache/dalvic once before you flash and twice after? Liberty is dead use ICS.
Sent from my DROID2 ICS using xda premium
Albinoman said:
Do you wipe data/cache/dalvic once before you flash and twice after? Liberty is dead use ICS.
Sent from my DROID2 ICS using xda premium
Click to expand...
Click to collapse
I did certainly wipe before flashing, but have never not once heard of wiping twice after flashing. wouldn't that undo the flash? what's the point of that? And like I said, I would use encounter ICS, but it's nowhere near stable enough for daily use.
When you wipe after its just to make sure everything is stock. As long as you don't wipe /system the rom will still be there. Actually if you can live without a camera EncounterICS is an amazing daily driver. Also never use bootstrap unless you're on stock gb.
Sent from my DROID2 ICS using xda premium
I can live without a camera, but google music barely works, which is something I can't live without. I'm thinking about going back to Apex until encounter gets really good (had apex for months up until i lost my original phone)
Google music is working fine for me. Good idea apex is great.
Sent from my DROID2 using xda premium

Categories

Resources