Database Users

[Q] Boot Loop Issues

Alright. Not new to rooting/flashing, all that jazz. I'm having an issue with my X boot looping, but I do a battery pull and it's fine.
I've actually sbf'ed (sp? lol) my phone and everything again to avoid this, thinking it was an issue with my process. Still getting booty loops.
So, I sbf'ed from froyo 2.2/fly x/tranquilty.
Here is what I've done, exact process.
-SBF'ed to stock 2.1
-Boot loop, pulled battery, rebooted into recovery, factory reset/clear cache (i know this one was necessary)
-Back to stock 2.1
-Used Easy Root method to root.
-moved SU from system/bin to system/xbin (to keep root before froyo update)
-downloaded Rom Manager from market, flashed CWR
-used Koush's bootloader apk
-downloaded 2.2 froyo from Rom Manager
-installed 2.2 froyo, booted back up.
First thing I did was download rom manager, backup my rom before flashing Fly X/Tranquility, Rom Manger rebooted me, threw me in a boot loop. Battery pulled, booted fine.
Only thing I can think of is I flashed CWR before using the bootloader apk, but not sure if that would even affect anything? Maybe clear cache partition in CWR might help something?
Any ideas? Thanks for your help in advance.

Try always using the "boot strap recovery" before rebooting from rom manager. See if that helps.
Sent from my DROIDX using XDA App

citanes-26 said:
Try always using the "boot strap recovery" before rebooting from rom manager. See if that helps.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
so, use the bootstrap.apk everytime before I need to reboot into recovery?
Kinda redundant.
Do you use this method?
Thanks for the response btw.

when u sbf, ur suppose to factory reset/clear cache before booting up to avoid that bootloop.
and to avoid bootloop from happing with a new rom, your suppose to bootstrap ive been reading...

Yep, if you reboot or flash I always do the bootstrap, read alot of people having to do it. First thing I do before I try to backup or restore.
Sent from my DROIDX using XDA App

cool, thanks for the responses guys.
i'll just keep boot strapping for the time being.
cant wait til we crack that sob.

BRUTAL BROCK said:
cool, thanks for the responses guys.
i'll just keep boot strapping for the time being.
cant wait til we crack that sob.
Click to expand...
Click to collapse
lol
"-downloaded Rom Manager from market, flashed CWR"
I did this same thing too.... We gotta use bootstrap.

Please pardon my ignorance but what is bootstrap?

Droidx bootstrapper, its in the market. You have to use it to get into clockwork recovery since we still have a locked bootloader.
Sent from my DROIDX using XDA App

[Q] Removing a theme

Just curious, i installed a theme ion my phone and it is already boring me. How do i remove it?

If you made a backup like you should have before you put on the theme, boot into recovery and restore back to before you had the theme. If you didn't make. A backup I think you could just factory reset the phone
Sent from my DROID2 using XDA App

The method of install would be helpful. Ie metamorph, zip flash, or adw/launcher theme.
Sent from my DROID2 using XDA App

@ skipwagner - i didnt do a backup(i know, way to go noob). i did a factory reset and the theme was still on it.
@zibrah3ed - Installation
1. Download file and place on the root of your SD card.
2. Use Koush's Bootstrapper to reboot into recovery.
3. Install .zip from sdcard, choose zip from sdcard.
4. Install Kangerade Blue Theme.
5. Enjoy!
it was the Kangerade Blue for the Droid2

You will have to SBF it back to original

Thanks to everyone who made a post to help me out. @MNDuke - I will definitely try that next.

I would backup your data with titanium backup, after that flash the rom you are on back without wiping data or cache. That should get you back to stock. Think sbf flashing it is a bit over the top, but may be needed.
Sent from my DROID2 using XDA App

Super noob question, please be gentle ...

Here's the background: I have a droid x, rooted with the latest z4root. Previously deleted some of the bloat (and yes, completely deleted with no backup).
As most of you know, I cannot use the official ota update from verizon (continually fails to install whether I keep root on or off). Currently have system version 2.3.15 mb810 verizon.en.us and (if it means anything), android version 2.2.
To further complicate this, I have no access to any kind of windows machine, pure Mac only.
Here's the $ 64,000 question; can I simply revert to a factory wipe (to reload all the crap I deleted), update via the official update and then reroot via z4root? Do I need to make a backup of some sort and if so, using what? Or, am I going to lose all data to date?
Any help will be greatly appreciated by this very non-technical, wanna-be rooter.
Please, no flames regarding the winbloze ...
Again, thanks in advance if you have the patience to try and help me. I'm terrified of bricking my phone.
DC
PMs are fine, too
Sent from my DROIDX using XDA App

Factory reset will only delete user data, it doesn't reinstall stock apps.

You will lose your apps and data with this method, but it's the cleanest way to do it. If you choose not to wipe data you may end up with an unstable phone. To be honest since you're coming from a stock image rather than one of the "roms" around here you might be able to get away with it. Just skip step 6. I'm still going to go with the clean route though.
Make sure your phone is fully charged!
1) Get Titanium Backup and back up all your app data.
2) Get Droid X Bootstrapper and install it.
3) Get Rom Manager, goto Download Roms and get the stock 2.2 image. Remember where it downloads to!
4) Go into Droid X Bootstrapper and reboot into (clockworkmod) recovery. In recovery you use the volume up/down keys to go up/down, the camera key to select and the back button to go back.
5) In recovery go into backup and restore, and make a backup. When it's done hit the back button to get to the main menu.
6) Choose to wipe data and then also wipe cache.
7) Go into mounts and storage, mount system and data (you'll know they are mounted because the option will now say "unmount system")
8) Choose install zip from SD card, and pick the image that Rom Manager downloaded.
9) Reboot system
If you get stuck in a boot loop, pull the battery out. Put the battery back in, and then hold down the home and power buttons until a triangle with an exclamation point pops up. Press the search button to get into the stock recovery. Wipe data/cache.

Try the sbf file for your version. Way more simple than the post above and you will be able to upgrade with the new OTA.
Sent from my DROIDX using XDA App

Why bother getting back to a stock .15 build in order to update when you can just go straight to the 2.3.340 and get the same result quicker without having to unroot and then reroot?
My Droid World has all of the necessary pieces in zip files to upgrade the bootloader, kernel, radio, and system. Just flash them in the order that they appear on the post restart between each update.
MDW Update Post

He has a Mac.

milan616 said:
He has a Mac.
Click to expand...
Click to collapse
They aren't sbf files so it doesn't matter, it can be done entirely from the phone. It's just a series of zip file that need to placed on the sd card and installed via clockwork recovery.

Whoops! That's what I get for only reading the first half of your post

pjsockett said:
Why bother getting back to a stock .15 build in order to update when you can just go straight to the 2.3.340 and get the same result quicker without having to unroot and then reroot?
My Droid World has all of the necessary pieces in zip files to upgrade the bootloader, kernel, radio, and system. Just flash them in the order that they appear on the post restart between each update.
MDW Update Post
Click to expand...
Click to collapse
I've downloaded all the files and moved them to my SD card. When I reboot into recovery and select update.zip I get an error saying it can't find the file. I don't see update.zip anywhere on my SD card. Do I need to have this on my card before installing the .zip files?

Are you using the droid x bootstrapper and rebooting into recovery , also mounting system?
Sent from my DROIDX using XDA App

use the "choose zip file" option instead of the "update zip file" option.
seems the same but is different .

Phone hangs on Dual core logo, need help

I had CM7 installed on my phone, and then i proceeded to update to the beta 2. I downloaded the file, then unpacked it on my phone sdcard then proceeded to reboot in recovery mode and cleared cache , dalvik, factory settings and then updated the zip file. then clear everything again and reboot. Get stuck on dual core logo.
I can still access recovery and mount usb to add files. can anyone tell me how to fix this?

did you make a backup before installing the beta?

It seems like you've never installed a ROM before, so I would advise you to read before you try again.
Try and restore it from the 1.8.3 SBF or restore from the CM7 pre-beta2.zip.
Don't unpack the zip file.
Oh and I feel obligated to ask, but did you install romracer's recovery?

I have Tenfar's recovery. Does it matter?
When you say restore, do you mean going in recovery mode and then apply the beta-update2.zip?
I also beleive my recovery got updated to Clockwork's when I had CM7 beta installed?
I have read another post on here that suggest I should RSD flash the 1.8.3 SDF and just start anew.
Should I do that? I was on 1.8.3 prior to installing CM7 beta

I understand I probably come across as a complete noob, but I did read before I did anything.
And now this happened and I just need help fixing it, you can just say. Yes flash back to 1.8.3 with RSD, I don't need a dot point instruction on how to do that.
Now my recovery is "ClockworkMod Recovery v4.0.1.4" even tough i originally flashed Tenfar's
and my phone is unlocked.
I have tried many times to clear all caches and update the beta zip again and it does not work, I just get stuck on dual core logo again.
Thanks in advance for any help.

Redownload beta 2 again (I've had problems related to bum d/l's). Install romracers recovery. Wipe. Reinstall.
If that fails use fastboot -w to wipe and reinstall.

quicklyspent said:
Redownload beta 2 again (I've had problems related to bum d/l's). Install romracers recovery. Wipe. Reinstall.
If that fails use fastboot -w to wipe and reinstall.
Click to expand...
Click to collapse
Legend, thanks a lot now I can go back to sleep.
I installed romancer's recovery (unlike tenfar's it took like 5 times longer to clear cache and install the rom) but it did work.
thanks for taking the time man.

I think that you forgot to wipe cache and Dalvik cache from within CWM.
For me that did the trick ...
Sent from my Atrix using Tapatalk

Rayan said:
I think that you forgot to wipe cache and Dalvik cache from within CWM.
For me that did the trick ...
Sent from my Atrix using Tapatalk
Click to expand...
Click to collapse
No I had wiped dalvik and cache prior and after update.
Either beta 2 doesn't like tenfars recovery or it was an issue with the download . Since I installed romancers recovery before I tried the new download we will never know
Sent from my MB860 using XDA Premium App

Why use tenfar's recovery when you can use CWM real recovery now.
That might help a lot...

im having the same problem but i used romracers recovery in the first place. ive tried everything and i tried to restore my alien backup but the recovery cant find it... did prebeta1 change the directory? im lost.

Fastboot -w.
Sent from my Motorola Atrix 4G MB860 using Tapatalk

Magnetox said:
Fastboot -w.
Sent from my Motorola Atrix 4G MB860 using Tapatalk
Click to expand...
Click to collapse
i tried that before and it didnt work.
edit- i found how to mount phone as usb in recovery. going to try the whole process again. i think my file was corrupt.
edit-- still cant get it to work even after redownloading teh file...

[Q] droid x borked?

So on a wild hair i decided to try out the latest official firmware. Stupid i know.
Now when i SBF back to the old firmware as stated in the cyanogenmod full update guide, root and bootstrap i can get into CWM recovery but no matter what rom i use it just bootloops. Then if i try to go back into CWM i of course find its the stock 3e recovery.
Did i perma-bork my phone from having custom roms or is there a problem between the chair and monitor? lol

did you wipe data and cache?
http://forum.xda-developers.com/archive/index.php/t-914110.html
DX .605 ROOT

marculous said:
did you wipe data and cache?
http://forum.xda-developers.com/archive/index.php/t-914110.html
DX .605 ROOT
Click to expand...
Click to collapse
Yeah, after I got the first bootloop I tried with apex and liberty and on each attempt wiped data and cache 3x

wipe data and cache, factory reset, then sbf? idk, I've been where you are many times and i always have to go back to the guides to get the process right, in the correct order.
DX .605 ROOT

So is there no reason that the newest OTA* would ruin the ability to put custom roms on?

i wouldn't think so, but i know for cm7 to get on my phone i had to sbf back to 2.2 from the. 596 i was on. guess it depends on the rom. me personally, i just left cm7 for. 605, rooted because i like the blur camera and hdmi support. took off most of the bloat but not all, it jacked up my contacts.
DX .605 ROOT

just treid it again, SBF'd back, rooted, bootstrapped, wiped data and cache and installed Liberty to come to a boot loop. i think .605 has locked me out of custom roms

spockmeat said:
just treid it again, SBF'd back, rooted, bootstrapped, wiped data and cache and installed Liberty to come to a boot loop. i think .605 has locked me out of custom roms
Click to expand...
Click to collapse
can you sbf back to an earlier version?
DX .605 ROOT

Yes I can go back to the froyo SBF without any problem. The issue is, once i do that, then repeat the steps and flash a custom rom, no matter what rom i use, i get a bootloop. the stock SBF and OTA work fine, its just once a custom rom is installed.

spockmeat said:
just treid it again, SBF'd back, rooted, bootstrapped, wiped data and cache and installed Liberty to come to a boot loop. i think .605 has locked me out of custom roms
Click to expand...
Click to collapse
How long did you bootloop? Liberty 3 2.0 can take up to 10 mins to load first time around... I'm assuming you are just seeing the spinning eagle? I thought I was bootlooping too, luckily I got caught up doing something else set the phone down and 10 mins later I had liberty running
sent from my Droid X running Liberty 3

hootowlserenade said:
How long did you bootloop? Liberty 3 2.0 can take up to 10 mins to load first time around... I'm assuming you are just seeing the spinning eagle? I thought I was bootlooping too, luckily I got caught up doing something else set the phone down and 10 mins later I had liberty running
sent from my Droid X running Liberty 3
Click to expand...
Click to collapse
No, it bootloops at the M Logo screen.
the M logo comes up for like 2 seconds, then the phone reboots.
The only variance to this is when i flash the AIO APEX rom, then it just sits at the google logo indefinitely. But on any other rom including Cyanogenmod and Libery it bootloops at the "M" Logo.

There is no reason for this to happen. Sticking at the Motorola's logo shows that something didn't flash correctly.
My only guess is a md5sum mismatch on every rom you are trying to flash, either that or you are trying to flash Froyo roms while using the Gingerbread kernel.
What you should do is SBF again to .602. AFTER you SBF, format data and cache via stock recovery then reboot. If it asks you to update don't take it.
Go to Rootzwiki and download a rom such as Vortex, MIUI, or ICS. Make sure that the md5sum on the rom you select matches the one given in the thread.
Root your phone with Pete's Motorola's Root Tools. Then install ClockworkMod Recovery with Droid 2 Bootstrapper. After you install ClockworkMod Recovery download Rom Manager from the market. Set your device to 'Droid X', and it will download and update ClockworkMod Recovery to the latest version.
Once this is complete, reboot into the newly updated ClockworkMod Recovery (which should be blue), and install your chosen rom.
Once you have installed it wipe data and cache, as well as the dalbik cache. Then reboot your phone.
If you have followed my directions down to every last comma, then your phone should boot into your newly flashed rom. If this doesn't work then something is very wrong. Something beyond my understanding that probably won't be fixable.
Feel free to message me if you have any questions. Best of luck to you!
Sent from my DROIDX using XDA App

infazzdar said:
There is no reason for this to happen. Sticking at the Motorola's logo shows that something didn't flash correctly.
My only guess is a md5sum mismatch on every rom you are trying to flash, either that or you are trying to flash Froyo roms while using the Gingerbread kernel.
What you should do is SBF again to .602. AFTER you SBF, format data and cache via stock recovery then reboot. If it asks you to update don't take it.
Go to Rootzwiki and download a rom such as Vortex, MIUI, or ICS. Make sure that the md5sum on the rom you select matches the one given in the thread.
Root your phone with Pete's Motorola's Root Tools. Then install ClockworkMod Recovery with Droid 2 Bootstrapper. After you install ClockworkMod Recovery download Rom Manager from the market. Set your device to 'Droid X', and it will download and update ClockworkMod Recovery to the latest version.
Once this is complete, reboot into the newly updated ClockworkMod Recovery (which should be blue), and install your chosen rom.
Once you have installed it wipe data and cache, as well as the dalbik cache. Then reboot your phone.
If you have followed my directions down to every last comma, then your phone should boot into your newly flashed rom. If this doesn't work then something is very wrong. Something beyond my understanding that probably won't be fixable.
Feel free to message me if you have any questions. Best of luck to you!
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
^This werk'd! I owe you vigorous oral.

spockmeat said:
^This werk'd! I owe you vigorous oral.
Click to expand...
Click to collapse
wow...........