did something dumb. help? - Droid 2 General

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

Related

[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.

Correct me if I am wrong.......

Had my X for a week now. It is rooted and running DarkSlideBlur 4.2, I have several other ROM's I am wanting to try out......
If I understand what I have been reading right, I can use Nandroid Backups to return to ROM's I like, or is it better to reflash them?
Trying to avoid the whole setup process....
Thanks in advance
Mace
A nandroid would be the route to go. It restores your phone to the exact state it was when you backed it up. Every call text message everything will be as it was.
Nandroid all the way. Works every time
Sent from my HTC Glacier using XDA App
MaceBewley said:
Had my X for a week now. It is rooted and running DarkSlideBlur 4.2, I have several other ROM's I am wanting to try out......
If I understand what I have been reading right, I can use Nandroid Backups to return to ROM's I like, or is it better to reflash them?
Trying to avoid the whole setup process....
Thanks in advance
Mace
Click to expand...
Click to collapse
As already stated, a nandroid is a best bet. Just keep in mind if you do any updates (OTA) and the radio gets updated (i.e. 2.3.15 to 2.3.340) an old nandroid will brick your phone due to an older bootloader
Sent from my DROIDX using XDA App
Thanks guys! I thought that was the case, as I have been all over these forums "researching" for a couple months before I got the X!
Now off to research "Radio"?? (thats a new one to me)
But what if you mount your system and get stuck in the bootup. i cant even get to the recovery. i dont know what to do.
Nandroid always has your back. Something gets screwed and you are stuck in a boot loop, plug in the usb or charger, pull the battery, put it in and boot up. That will hijack back into Clockwork.
Always Wipe Data/Factory Reset, Wipe Cache/Advanced/Wipe Dalvik before you flash a new ROM and you "almost" always avoid a boot loop.
Sent from my DROIDX using XDA App
that is clockwork recovery, the stock recovery is accessed with a combination of hard keys which i am not sure which they are off the top of my head. in that you can wipe, but unfortunately no nandroid restore.
I tried every rom out there. The fastest most stable best battery life is stock. Deodexed stock. You can theme and font.
Sent from my DROIDX using XDA Premium App
mattmartin77 said:
that is clockwork recovery, the stock recovery is accessed with a combination of hard keys which i am not sure which they are off the top of my head. in that you can wipe, but unfortunately no nandroid restore.
Click to expand...
Click to collapse
The hard keys are volume down and camera button if you wanted to know
Thats to get to the bootloader. Recovery is home and power and hold on until it comes up. To get into safe mode you hold power and the menu button
Sent from my DROIDX using XDA Premium App

Downloading .596 rooted from TBH now...

Downloading .596 rooted from TBH now...
Thanks for letting us know
Where is Team Black Hat's Website/host?
Do you have a link?
They've done it already? Please provide link. Can it be done on x not activated, just using on wifi?
Sent from my DROIDX using XDA App
You have to buy their app for $1.99 @
http://shop.teamblackhat.info/Software_c3.htm
Well worth it. Otherwise, it will be on this and other websites by the end of the day. P3droid rocks. I've been messing around with it, and everything seems super smooth.
jideay, I got it from their website. Did you do method 2 (part 1 and 2)? If so I'm confused if I have to hit both downloads at the same time or do part one, then part 2. Do we need bootstrap or bootstrap2. I have both. Want this on my phone but a little confused.
milski65 said:
jideay, I got it from their website. Did you do method 2 (part 1 and 2)? If so I'm confused if I have to hit both downloads at the same time or do part one, then part 2. Do we need bootstrap or bootstrap2. I have both. Want this on my phone but a little confused.
Click to expand...
Click to collapse
This is what I did.... Download part 1 and part 2 then use droid2 bootstrap then install part 1 AND part 2 before you exit bootstrap and it should work fine
Did you have to do a "wipe" of any kind in recovery before installing? Also did you do a nandroid backup first before even downloading 596?
milski65 said:
Did you have to do a "wipe" of any kind in recovery before installing? Also did you do a nandroid backup first before even downloading 596?
Click to expand...
Click to collapse
nope no wipe or nandroid.... all I did was install the who files, very easy install :-D
Okay, so I go into tbh app, find 2 part download, hit download 1 first or do I have tohit both at the same time.; It says "these need to be loaded at same time". Not sure what they mean by that. Then droid2 bootstrap, hit bootstrap recovery, then reboot recovery and then install zip from sd. Is that correct. Will tbh app download automatically to zip od sd? Reason i ask is I tried a coustom rom about 2 months ago, thought I did evewrything correctly, but coulsn't find darkslide rom on sd. Wound up having to sbf. Prefer not to go through that again.
milski65 said:
Okay, so I go into tbh app, find 2 part download, hit download 1 first or do I have tohit both at the same time.; It says "these need to be loaded at same time". Not sure what they mean by that. Then droid2 bootstrap, hit bootstrap recovery, then reboot recovery and then install zip from sd. Is that correct. Will tbh app download automatically to zip od sd? Reason i ask is I tried a coustom rom about 2 months ago, thought I did evewrything correctly, but coulsn't find darkslide rom on sd. Wound up having to sbf. Prefer not to go through that again.
Click to expand...
Click to collapse
2 things.
1. Someone told you what he did and it worked. Do that.
2. Why didn't you download the rom you couldn't find onto your pc and move to SD in recovery to where you could find it?
I'm in the process of downloading these files (1 THEN 2 because you can't download two at the same time) and we'll see how this goes.
Thejron, I was waiting for clarification on the tbh apparently, which you just provided. Thank you. I did load roms from computer, as I did the tbh 596 root. Why I couldn't find it on bootstrap recovery I have no idea. My screw up. It was there in astro. Sorry about offtraking on post.
Sent from my DROIDX using XDA App
http://www.mydroidworld.com/forums/...-5-596-release-thread-something-everyone.html
This is what people are looking for...
Running .596 rooted, did method 2.
eyepopper said:
This is what people are looking for...
Running .596 rooted, did method 2.
Click to expand...
Click to collapse
That is exactly what I was looking for, I also did method 2. Everything seems to be running great.
In case anyone was wondering I'm using an unactivated droid X (rooted, stock .340), with wifi. I used my computer to download the files and copied them to my sdcard. I did a factory wipe, cache wipe and delvik (I think thats how you spell it.)wipe from clockwork using the droid2 bootstrap(not the droidx bootstrap). Installed the two .zip files in order and rebooted it came up fine.
Thanks - had it running now a couple of hours, may be psychosomatic, but it seems faster than .595.
yeah, i like it - transition was easy, i did had to re install a few things but over all very easy coming from .595 using the tbh app. very nice.
what was the Easter egg p3 mentioned something about a dx2 lwp? i downloaded and flashed patch but still dont see the wallpaper... anyone else see it? and yes I flashed the rooted version from tbh
Sent from my DROIDX using XDA App
taterDX said:
what was the Easter egg p3 mentioned something about a dx2 lwp? i downloaded and flashed patch but still dont see the wallpaper... anyone else see it? and yes I flashed the rooted version from tbh
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Rapidly tap the android version in settings > about phone. That is an Easter egg from google :3
Go into settings, about phone, and multiple tap on android version.
Install worked great on wifi only x. No issues with Netflix or anything else. Does anyone know if I have to sbf my other x that's froyo with clockwork mod backup done?
Sent from my DROIDX using XDA App

Not so random reboots

I updated to EI22, stock w/OTA update. I then rooted and things were working great. Then about 1 week ago, I did a CWM backup and when I restarted the phone just kept automatically rebooting approx. every 3 -4 minutes. I could not stop it no matter what I did. Then I restored the backup and it worked fine. A few days later, I turned the power off to put in a my extra battery, and when I turned it on, the same thing happened. I had to restore twice fir it to stop this time. Then this morning, I did a reboot to see what would happen, and again it happened. Mind you it was working flawless before I restarted it. I have tried everything from removing programs, turning off the wifi, leaving the battery out for a half hour, but nothing. Sometimes after it reboots, I leave it alone for 15 minutes and then when I hit the power button, it just restarts.
Any ideas before I put back froyo??
Sounds like a bad flash. I would Odin all the way to Stock EC05 then root then flash a Gingerbread ROM. Your error is either in the kernel or recovery to happen immediately after boot. It could even be a flaky partition table.
Sent from my SPH-D700 using XDA App
OK. Funny, I flashed backed to a stock EC05 and did the OTA update so as to possible avoid any problems like this.
mszach said:
OK. Funny, I flashed backed to a stock EC05 and did the OTA update so as to possible avoid any problems like this.
Click to expand...
Click to collapse
I figured that but the problem may lie in the rooting which required you to flash a kernel or in your recovery module.
Sent from my SPH-D700 using XDA App
mszach said:
Any ideas before I put back froyo??
Click to expand...
Click to collapse
Your not alone on this issue. I am also considering going back to froyo
ADW was nice enough to bring up a crash report that I emailed myself. In the stack trace I see that android Package manager has died as a cause of the exception. I am not a java programmer so am at a loss here to what's happening.
See also this related post
So I flashed to the ACS ICS rom and so far no problems. What a great ROM!! Many thanks to Marcusant and ACS.
Sent from my SPH-D700 using XDA App
don't use the OTA.
just root ec05, flash CWM 5, flash modem update ec05 to EI22, flash a rom of your choosing. it's that simple. i don't see why people go the OTA route. it just causes problems with the recovery.
EDIT: also if you want Rom manager, check the kernel(or rom) for compatibility.
Why use ROM MANAGER at all? All the same tasks can be done from Clockwork Mod directly?
Sent from my SAMSUNG-SGH-I777 using xda premium
robmoney215 said:
Why use ROM MANAGER at all? All the same tasks can be done from Clockwork Mod directly?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
I'm lazy sometimes and like to use a GUI...
Sent from my SPH-D700 using XDA App
robmoney215 said:
Why use ROM MANAGER at all? All the same tasks can be done from Clockwork Mod directly?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
It was not supported for the Epic before but with the new CWM5 it is. It is much faster to boot into recovery from ROM Manager rather than powering down and 3 fingering into it. Plus ROM Manager supports renaming your backups when you are doing them. Also ROM Manager will continuously update your CWM if new versions come out. There is also OTA updates available if the developer supports it on their ROM.

[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

Categories

Resources