Related
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
linkthanks go to mioze7Ae/brianlili/mchlbenner/J.Y.Daddy/fifalcon.
Please give feedback.
P.S. THIS SBF NOT MEANT TO BOOT.
download OR.rar and apply it first its your open recovery make sure you move your updates to it.
delete your present open recovery or move off main sdcard.
xt720mod sbf. it will not work on cm6.
this has up to 250 mb internal storage depending what rom your using. this sbf doest boot use it to get to open recovery.
how to get to recovery simple go to moto stock recovery and click update.zip it will take you to open recovery.
their a bootfix for cm7 ours.
their a bootfix for JY.Daddys cm7 and miui ics.
let me know if links don't work or any other problem.
DONT FLASH SBF FIRST.
yesterday i spent about 6 hour with bravo trying to get a sensor fix but did not I will trying to get a fix for all
I have been running this for a few weeks and it is great. The recovery is what the Milestone A853 people call a "vulnerable recovery". This means that the Motorola stock recovery in the sbf has a security vulnerability--it does *not* check that update.zip has been signed by Motorola before applying it (on all the others it does check that). Also like mchlbenner says, the /data partition is much larger (256mb)--actual amount free after boot will depend on the ROM's configuration. To reiterate the wonkyness:
You MUST prepare your sdcard with the OpenRecovery before flashing (or you will be forced to put your sdcard in a computer). You must have /sdcard/update.zip from OR.rar and an update or nandroid to apply.
After you flash the sbf, it will not boot anything except Motorola stock recovery until you get into OpenRecovery (from stock recovery) and flash a ROM.
The rotation sensor is somehow rotated by 90 degrees. mchlbenner's bootfixes fix that for Gingerbread ROMs. We don't have a fix for eclair or froyo (yet?).
Hi could you post link to xt720mod sbf mine will not work.
I flashed clockwork mod and it worked!
Sent from my XT720 using xda premium
mchlbenner said:
Hi could you post link to xt720mod sbf mine will not work.
Click to expand...
Click to collapse
http://www.multiupload.com/4I3FIFTD68
Mioze7Ae said:
I have been running this for a few weeks and it is great. The recovery is what the Milestone A853 people call a "vulnerable recovery". This means that the Motorola stock recovery in the sbf has a security vulnerability--it does *not* check that update.zip has been signed by Motorola before applying it (on all the others it does check that). Also like mchlbenner says, the /data partition is much larger (256mb)--actual amount free after boot will depend on the ROM's configuration. To reiterate the wonkyness:
You MUST prepare your sdcard with the OpenRecovery before flashing (or you will be forced to put your sdcard in a computer). You must have /sdcard/update.zip from OR.rar and an update or nandroid to apply.
After you flash the sbf, it will not boot anything except Motorola stock recovery until you get into OpenRecovery (from stock recovery) and flash a ROM.
The rotation sensor is somehow rotated by 90 degrees. mchlbenner's bootfixes fix that for Gingerbread ROMs. We don't have a fix for eclair or froyo (yet?).
Click to expand...
Click to collapse
So, I'm a bit confused on what all this means. I understand the part about the /data partition being larger, but is that at the expense of the /cache partition? Also, as I understand it the Clockwork Mod is the equivalent of AOR, is this correct? What is the benefit of CWM vs AOR?
thejaycan said:
So, I'm a bit confused on what all this means. I understand the part about the /data partition being larger, but is that at the expense of the /cache partition?
Click to expand...
Click to collapse
Both the /system and /cache partitions are slightly smaller (the partition layout is the same as the Motoroi 50R froyo sbf, but this uses a Milestone XT720 kernel instead of a Motoroi kernel). The other implication is that if you are running this sbf, you will always be able to enter OR (assuming you have a valid sdcard). With other sbf's if you do something to make your system unbootable and you can't re-enter OpenRecovery, your *only* option is to flash sbf. In other words, a bootstrap recovery is not needed with this sbf.
Also, as I understand it the Clockwork Mod is the equivalent of AOR, is this correct? What is the benefit of CWM vs AOR?
Click to expand...
Click to collapse
I have not tried the clockworkmod. Mostly because I haven't had time to study it, but I have studied AOR. So for me at least it's more of a devil-I-know sort of thing at the moment.
Hi
I'm using clockwork mod and I'm using minimod recovery I prefer are recovery.
Rom manager is oka but if you flash cm7 with it you only have edge not 3g I could not fix this issue yet.
I would recommend to stay with are open recovery for know.
Sent from my XT720 using xda premium
I Know this is prob a stupid question... But are there any performance increases with this? or just more space? and always be able to get into OR?
The answer is yes less on sdcard will help with performance that's my opion.
I personal have got better performance on this sbf.
Sent from my XT720 using xda premium
Are there plans for a froyo fix ? I saw MZ say (YET?) lol
The plan is it to get it work on cm6 and eclair but I have searching for this fix but I not found it yet their must be a fix will find it.
Sent from my XT720 using xda premium
HI.
First off all, thanx for this.
SBF is installed, and flashed with J.Y.Daddy CM 7.1.1 with bootfix.
I'm actually restoring all my apps, will let you know if it's good or not.
---------- Post added at 12:59 PM ---------- Previous post was at 12:06 PM ----------
Just for the fun, and because it's not really simple, here is the way to use this SBF.
Prepare you're SDCARD:
Copy the content of AO.rar from the first post to your sdcard
be sure to get a valid rom update in your sdcard/OpenRecovery/updates directory.
(I personnaly used CM 7.1.1 from J.Y.Daddy)
Flash your phone:
Boot your phone in flash mode (power + cam key)
Flash your phone using rsd lite and the xt720-2.1-mod.sbf file
After succesfull flash, restart your phone by pressing Power key + Camera Key + GalleryKey to bring up the recovery screen.
Don't wait for your phone to boot! This SBF can't!
When the Triangle/Exclamation point screen appears, press Volume Up + Gallery Key down and tap the camera key to show the recovery menu.
Apply the update.zip to get the OpenRecovery menu
Apply your ROM update
Apply the fix for your rom provided in the first post
Wipe data / cache / dalvik
Reboot
Enjoy.
I m flashing it for the third time and it don t boot after the rsdlite flash....
It stay with the motorola logo for a long long time (i m waiting for about 10minutes now...)
Anyone had this problem? I think i m gonna try to go to the moto recovery without waiting for the first boot
edit it works without waiting for the first boot... Sorry
B_e_n said:
I m flashing it for the third time and it don t boot after the rsdlite flash....
It stay with the motorola logo for a long long time (i m waiting for about 10minutes now...)
Anyone had this problem? I think i m gonna try to go to the moto recovery without waiting for the first boot
edit it works without waiting for the first boot... Sorry
Click to expand...
Click to collapse
thats whats supposed to happen isnt it? you have to go straight to moto recovery, select update.zip. and that will bring u to the custom AOR, and from there, u can flash the rom that u want, and apply the bootfix.
That's normal. This SBF can't boot!
You have to remove your battery and restart your phone by pressing Power key + Camera Key + GalleryKey to bring up the recovery screen.
Then you just need to follow my previous post.
Sorry I m so tired this days.....
Hi mchlbenner... nice to finally see something from you (not forgetting the help from the other devs). this modded sbf thing is really cool, hope to see more improvements, it would be awesome if there were fixes for the simpler roms (2.1 and 2.2)! keep the good work up!
I hope to find a fix cm6 and 2.1.
Not to long ago we did not have many choices at all and now we have a ton choices.
Sent from my XT720 using xda premium
can you post the kernel cmdline?
/proc/cmdline
trying to slide the above onscreen
peshovec said:
can you post the kernel cmdline?
/proc/cmdline
Click to expand...
Click to collapse
console=ttyS2,115200n8 console=ttyMTD10 rw [email protected] init=/init ip=off brdrev=P3_TABLET_SKT androidboot.bootloader=0x0000 mtdparts=omap2-nand.0:[email protected](pds),[email protected](cid),[email protected](logo),384k(misc),3584k(boot)ro,[email protected](recovery),8960k(cdrom),[email protected](system),[email protected](cache),265344k(userdata),1536k(cust),[email protected](kpanic)
The boot.img is identical to the one in the UK and Central Europe SBFs:
eff22955e8e91eb19545a3af39973934 xt720-2.1-mod/CG35.img
eff22955e8e91eb19545a3af39973934 STR_U2_01.1E.0/GAS_EMEA_UCASHOTBRTLRTCEE_P001/boot.img
eff22955e8e91eb19545a3af39973934 STR_U2_01.1E.0/GAS_EMEA_UCASHOTBRTLRTGB_P021/boot.img
uname: Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Tue Jul 13 17:19:35 IST 2010
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...........
after the OTA update to 2.3.4 my rooted droid 2 boots into ClockworkMod Recovery 2.5.0.8.
From what I'v read it isn't possible to to restore my phone to 2.3.3. So I'd like to remove clockwork mod recovery so it boots normally. Currently I have to choose "reboot system now" from recovery,when I do a cold restart, then the phone boots normally.
So far I'v only wiped my user data, but thought i'd better check what would be the best course of action. Don't want to brick my phone.
Sorry if it's a noob question.
Don't think about downgrading to 2.3.3 you'll be bricked and have to install 2.3.4 and lose cwm and root
Sent from my DROID2 using xda premium
Yeah saw the posts (of people trying to downgrade). I'm thinking of selling it, but need to remove the clockwork recovery. Any ideas on how to get it off of there?
Use the 2.3.4 SBF as mentioned above.
devinpatterson said:
Yeah saw the posts (of people trying to downgrade). I'm thinking of selling it, but need to remove the clockwork recovery. Any ideas on how to get it off of there?
Click to expand...
Click to collapse
if your not worried about losing root, SBF use http://forum.xda-developers.com/showthread.php?t=1662091
if you just want to fix cwm, read Proper Use Droid 2/X Bootstrapper
the logwrapper or hijack is the problem,
also read Droid Wiki: SBF, Recovery, CWM info
When I was on the stock Verizon ROM I was able to simply run the Droid 2 Bootstrapper and it booted into recovery. From there I installed this Galnet MIUI ROM. I'd like to check out some other ROMS but I cannot get CWM to install.
In ROM Manager 3.0.1.4 I tap on Flash CWM and it says "An error occurred while downloading your recovery"
I tried installing the D2 bootstrapper and when I click on boot into recovery my device simply reboots back into MIUI and everything has been reset to default. I'm kind of new at all this and tried searching but didn't really come up with a solution. I've heard something about SBF but not sure what that is. Any help would be appreciated. Thanks.
Here, try this. CM7 is the best ROM for this phone anyways
http://wiki.cyanogenmod.com/wiki/Motorola_Droid_2:_Full_Update_Guide
Cool I will check it out. I figured out how to get back to stock using RSD Lite. Slowly but surely I'm getting all this Android stuff.
So now I'm running into another issue. Once I get the SBF installed and I'm back on stock 2.2 I can't seem to get any other ROM flashed. At all.
On 2.2 I root the device using z4root. Then I install the D2 bootstrapper and reboot into recovery. The standard CWM screen comes up. I wipe cache. Clear Davlik cache, etc, etc. I install the update.zip and everything seems fine. Says process is complete but when the phone is restarted I'm stuck in an endless boot loop of the white Motorola logo.
Did you only wipe the cache or did you wipe data/factory also?
I did both. When I got this device it was on 2.3.7 I think. It's not activated and I plan on using it as a PDA/MP3/WIFI device. Seems like I can't do any factory updates without cellular data so it's on 2.2.
I can't even get MIUI 2.2.10 back on there.
You need to be on GB not Froyo to run Galnet. There's an SBF for 2.3.7 posted here on the forums.
there is no 2.3.7
2.3.4/4.5.621 is latest and it is unrootable and can not flash older sbfs
use 2.3.3/4.5.601 aka 1FF-p2a_droid2_cdma_droid2-user-2.3.3-4.5.1_57_DR2-31-110719-release-keys-signed-Verizon-US.sbf
find here http://1kds.tk/
2.3.4; you knew what I meant =p
I got it all worked out. Are there any overclocking enabled kernels for the D2?
I recommend Milestone Overclock. It doesn't load on boot with all Roms, but it does on most and it's free and doesn't come with AirPush like some apps.