Hello, I have a Droid 2 Global, with OTA .629, but already rooted and everything, but i have constant reboots since i had the phone (with .330, .607, .608 and .629) maybe its a defective phone, i dont know really, but the problem i have actually it is:
I installed the newest clockwork recovery using Rom Manager, but the recovery it doesnt do anything, it says it wipe data/cache, and very quickly, but it doesnt, it gives me error formating /system, etc...
It says that installed sucessfully Cyanogenmod 7.2 (latest nightly) but, it freezes at M logo... what should i do?
stop using rom manager
use a different cwm version
Sent from my DROID X2 using xda premium
suggestions?
try droid 2 bootstrap
or you already have rom manager, you can get different cwm versions, with that
try last version that worked for you
This is hardly discussed or documented anywhere, but if you're using CWM, you have to flash Droid X 2nd Init and NOT Droid 2 Global as your recovery.
projektorboy said:
This is hardly discussed or documented anywhere, but if you're using CWM, you have to flash Droid X 2nd Init and NOT Droid 2 Global as your recovery.
Click to expand...
Click to collapse
thank you, it worked... i used d2g recovery cmw, and didnt work...
projektorboy said:
This is hardly discussed or documented anywhere, but if you're using CWM, you have to flash Droid X 2nd Init and NOT Droid 2 Global as your recovery.
Click to expand...
Click to collapse
that's because Rom Manager isn't recommended
I used Droid 2 bootstrap, with 2.4.33 and 4.5.608 and it worked fine
i used d2g recovery cmw, and didnt work...
Click to expand...
Click to collapse
your cwm was likely corrupt, selecting Droid x just installed a complete cwm
edit: if you are using rom manager you have to use Droid X 2nd Init, or just use Droid 2 bootstrap
sd_shadow said:
that's because Rom Manager isn't recommended
I used Droid 2 bootstrap, with 2.4.33 and 4.5.608 and it worked fine
Click to expand...
Click to collapse
You aren't quite right.
The correct way is installing Droid 2 Bootstrap Recovery and using that to hijack. This will give you CWM 2.0.0.x. Once done, install the Droid X (2nd init) CWM via ROM Manager, and you'll end up with a fully functional CWM 5.0.0.x.
(Custom ROMs like CM7, CM9, and MIUI come with 5.0.0.x preinstalled, and restoring a backup made with 5.0.0.x is impossible if running 2.0.0.x.)
ok, i dont really get it...
using Droid X 2nd-init, it wipes and everything, and flashes CM9-D2G-04162012 and update-cm-7-20120420-NIGHTLY-droid2we-signed, coming from stock .629 firmware, and it freezes at M logo after rebooting, then is necessary sbf'ing again .608, and unbrick it againg, and is a loooong process....
again there are no roms built for .629, so you need to search for ones that are reported to work, and how they got them to work
In general, according to people who use CM9 on top of .629, any .608 ROM works on .629. There are no differences.
joel_sinbad said:
ok, i dont really get it...
using Droid X 2nd-init, it wipes and everything, and flashes CM9-D2G-04162012 and update-cm-7-20120420-NIGHTLY-droid2we-signed, coming from stock .629 firmware, and it freezes at M logo after rebooting, then is necessary sbf'ing again .608, and unbrick it againg, and is a loooong process....
Click to expand...
Click to collapse
have you tried, wiping cache/data, after flashing
not for me, used latest CM9 and CM7 nightlies, freezes at M logo... only before flashing update.zip for getting from .608 (hybrid?) to .629... custom roms work somewhat ok, without wi-fi, Sound Settings fc, and other little details...
sd_shadow said:
have you tried, wiping cache/data, after flashing
Click to expand...
Click to collapse
yeah, after, and before... no sucess
sd_shadow said:
have you tried, wiping cache/data, after flashing
Click to expand...
Click to collapse
yeah, after, and before... no sucess
you could try
1-wipe data,cache,davlick
2-mount and format system
3-mount system and install zip
done, no results...
I get the same results after flashing MIUI over .629. It flashes ok using Droid X(2-int) recovery but after that its bugy as hell. I cant switch to GSM, tried dialing 46xx number and using network toggle. GSM doesn't see to work at all and when i try to restore my old rom it gets stuck on M logo.
Transceiver issues are in no way related to CWM.
It would be nice if someone who is on .629 can confirm that GSM works on CM7,9 MIUI or any other room. I want some ICS goodness but it looks like it would be just a waste of time flashing again.
Well, .629 doesn't really differ from .608 if you're looking at it from a custom ROM's point of view. Same kernel and modules, and that's all a custom ROM needs from the “base” system.
Related
hello,
during the restore with clockworthmod recovery, the phone hangs up.
now is the system damage and no boot the phone. bootloader and menu for hard-reset(X+power works).
i need a sbf file for the european milestone 2 with motoa953 chipset for flashing with rsd lite.
gives a update.zip for the sdcard with clockworthmod revory to start from the menu "apply sdcard update.zip) with verifying
many thanks
try data wipe/factory reset and wipe cache in the clockwork or stock recovery..might fix the problem.
Sent from my DROID2 using XDA App
this only delete cache and data. during the restore with clockworthmod, the system is erasing and then copied the system from backup. and in copy mode the sdcard hangs and now is the systems files all erased an the phone doesn´t boot:-(
Rennert said:
this only delete cache and data. during the restore with clockworthmod, the system is erasing and then copied the system from backup. and in copy mode the sdcard hangs and now is the systems files all erased an the phone doesn´t boot:-(
Click to expand...
Click to collapse
Look on the forums and see how to sbf, that should fix the problem. And if not, you "bricked" it..if you can get into the stock recovery by holding the x button down and it comes up and what not then its salvageable but if all you get is the motorola m then it might be toast. Give sbf'ing a try.
Edit: Sorry I didn't really read your original post, sorry, you know how to sbf but don't have the file..I couldn't tell you where to get that...go to androidforums.com or droidlife.com and maybe someone can help over there because obviously im the only one responding...
Sent from my DROID2 using XDA App
The problem is, the milestone 2 have another chipset (a953) like droid2. Rsd lite says: firmware is not compatible with this phone. On recovery mode with update.zip can i only flash original firmware (verifization).
Today i go in the vodafone shop, the phone is only 1 week old.
Can i create a working sbf file from my clockworthmod* .img? I have many complete backups on my sdcard.
Or how can i make a sbf file from the system of another milestone 2. This would i flash into my ms2 with rsdlite
Sent from my Milestone using XDA App
http://www.mydroidworld.com/forums/android-hacks/1207-milestone-sbf-files.html
Stumbled apon this but im not sure if this is for the milestone 1 or 2...
Sent from my DROID2 using XDA App
@Rennert,
How did you get the Clockwork recovery installed on the Milestone 2 (A953) ?
I have the same phone myself but I've not found any information on how to proceed. I've rooted permanently with the z4root-app but that is about it.
I stumbled on this one (similar) to the one above when looking up bootstrapping the Milestone 2
hXXp://and-developers.com/sbf:milestone2
Dunno if it helps (sorry as I'm a lurker I have to HXXP).
dogei22 said:
@Rennert,
How did you get the Clockwork recovery installed on the Milestone 2 (A953) ?
I have the same phone myself but I've not found any information on how to proceed. I've rooted permanently with the z4root-app but that is about it.
Click to expand...
Click to collapse
With Droid X/2 recovery Bootstrap you can install ClockworkMod v2.5.0.8.
Edit: Please read instructions before you try the application.
Thx,
Installed ClockworkMod recovery with Droid 2 Bootdtrap. Not sure if there is any joy out of it as there are no ROMs around yet... nandroid backups works well though.
dogei22 said:
Thx,
Installed ClockworkMod recovery with Droid 2 Bootdtrap. Not sure if there is any joy out of it as there are no ROMs around yet... nandroid backups works well though.
Click to expand...
Click to collapse
For now only backup just in case.
I am doing some tests and hoping that if something goes wrong I can restore my phone with that backup.
Edit: Droid Overclock can be useful for example to change some Build Props(Dalvik VM, Max EVTs, etc)
Sent from my MotoA953 using Tapatalk
Try it, appear the original european firmware.
http://modmymobile.com/forums/593-m...558715-milestone-2-firmwares-superthread.html
Tell us if everything is ok.
Alright, I rooted my Nexus S 4G this guide. My phone was running 2.3.5 but I figured that these steps in Terminal wouldn't really change. When I flashed the "recovery-clockwork-3.0.0.5-crespo.img" it didn't install properly (I assume because it was out of date/wrong version) Anyway, I flashed this instead with no problems.
In my euphoria over solving my clockwork problem, I forgot to flash the "su-2.3.6.1-ef-signed.zip" and flashed the current version of MIUI. I am now stuck in a bootloop and I cannot enter recovery by using power+volume. I cannot turn the phone off. I can load the bootloader screen using Terminal while I plug it into my computer, but I don't know what to flash to fix the phone, and start over/end up with a Nexus running MIUI.
i dont know much about macs but you can flash the img files through fastboot.
imgs files are here
thank buglesspete
chewbz said:
i dont know much about macs but you can flash the img files through fastboot.
imgs files are here
thank buglesspete
Click to expand...
Click to collapse
I can handle the mac part if you can show me which files to flash in which order to make my phone work again.
Okay this will take your phone back to stock. Download the grj22 image files. When you open it up it should have like 4 or 5 img files. After that open up cmd and type in the commands buglesspete has in his first post. It should be under "return to stock" or sometime like that.
Sent from my Nexus S 4G using XDA App
XikkeN said:
Alright, I rooted my Nexus S 4G this guide. My phone was running 2.3.5 but I figured that these steps in Terminal wouldn't really change. When I flashed the "recovery-clockwork-3.0.0.5-crespo.img" it didn't install properly (I assume because it was out of date/wrong version) Anyway, I flashed this instead with no problems.
In my euphoria over solving my clockwork problem, I forgot to flash the "su-2.3.6.1-ef-signed.zip" and flashed the current version of MIUI. I am now stuck in a bootloop and I cannot enter recovery by using power+volume. I cannot turn the phone off. I can load the bootloader screen using Terminal while I plug it into my computer, but I don't know what to flash to fix the phone, and start over/end up with a Nexus running MIUI.
Click to expand...
Click to collapse
Just a general hint... if oyu own a Nexus S 4G, Crespo isn't the right codename to look for.. it's crespo4g. Get the cwm recovery from here and flash the 4G version via "fastboot flash recovery <recoveryname>.img": http://forum.xda-developers.com/showthread.php?t=988686
rentaric said:
Just a general hint... if oyu own a Nexus S 4G, Crespo isn't the right codename to look for.. it's crespo4g. Get the cwm recovery from here and flash the 4G version via "fastboot flash recovery <recoveryname>.img": http://forum.xda-developers.com/showthread.php?t=988686
Click to expand...
Click to collapse
I know. I linked to that thread in my first post. What step am I skipping to run MIUI without a bootloop?
XikkeN said:
I know. I linked to that thread in my first post. What step am I skipping to run MIUI without a bootloop?
Click to expand...
Click to collapse
I have no experience with the 4G version of this phone but I can tell your that bootloops are usually caused by failing permissions (fix permissions in cwm rec) or missing wipes before isntalling the actual rom.
So I'd go back to start, flash the 4g recovery, wipe everything (including "mount and storage"'s /boot and then flash MIUI for 4g from here afterwards.
Basically, that MIUI (and most other custom roms) includes superuser.zip aka root. No need to root the devices before, all you need is an unlocked bootloader.
rentaric said:
I have no experience with the 4G version of this phone but I can tell your that bootloops are usually caused by failing permissions (fix permissions in cwm rec) or missing wipes before isntalling the actual rom.
So I'd go back to start, flash the 4g recovery, wipe everything (including "mount and storage"'s /boot and then flash MIUI for 4g from here afterwards.
Basically, that MIUI (and most other custom roms) includes superuser.zip aka root. No need to root the devices before, all you need is an unlocked bootloader.
Click to expand...
Click to collapse
What he said, I always wipe 3x everything just to make sure it is a clean install. And some people will also suggest to let the rom boot up normally before flashing a different kernel.
Sent from my Nexus S 4G using XDA App
chewbz said:
What he said, I always wipe 3x everything just to make sure it is a clean install. And some people will also suggest to let the rom boot up normally before flashing a different kernel.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
wiping 3 times is senseless! and the kernel should be flashed right after the rom install!
oh and wiping the dalvik cache and chache after a rom-update is also senseless! the updater-script do this automatic!
Sent from my Nexus S using XDA Premium App
Borky_16 said:
wiping 3 times is senseless! and the kernel should be flashed right after the rom install!
oh and wiping the dalvik cache and chache after a rom-update is also senseless! the updater-script do this automatic!
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
your assuming that the devs took the time to make sure to include that
OK so we know the bionics bootstrap recovery doesn't work. I was messing around with Rom manager and flashed the bionics recovery and was successful. Recovery version 5.0.2.5. Then I booted into recovery from Rom manager and performed a successful backup! Gonna hold out on flashing the backup right now but I'm hoping someone that knows a lot more then me will look into this also and see what they think about it and can we possibly use everything without fearing a bricked device .
i successfully created a backup using the bionic bootstrap recovery, but im leery of trying to do a restore without having an sbf handy
Well I got brave and clicked the restore button using the bionic bootstrap recovery. I have 20+ days left to return the phone if anything went wrong. I backed up using the recovery, then clicked restore. Everything restored perfectly. I did not choose wipe data though, as I didn't think it would matter. Just thought I would add that bit of information. Hope this helps guys.
Sent from my MB865 using XDA App
I just used CWM 5.0.2.5 to restore the system backup I made before updating, and indeed it worked fine. I'm back down to 55.11.16 android 2.3.5 (from 55.13.16 - 2.3.6) with seemingly no ill effects. IIRC, I made this system image with the bionic bootstrap recovery app.
Im still on 55.11.16 android 2.3.5 also, I know using Rom manager to make a backup took a lot longer then what I was used to on my OG. Just went through a restore with no seemingly ill effects. Has anyone tried flashing a zip yet? Just glad we seemingly have a recovery that is working.
my vivid will be here in the next day or 2. once i have that, i will risk the Atrix2 and start working on a rom.
Oh no Pirate your switching over to the HTC Vivid? I have been looking at the reviews on that device and it looks as thick as my A2 with the defender otterbox. I'm going to kick my cat if people start abandoning ship on the A2, bummer!
Awesome work on getting CWM to backup and restore. I would love to see some custom roms being dumped onto this device.
Nice! Recovery loads up smoothly on rom manager. This could get interesting...
If your bootloader is not unlocked be very careful as to what you flash!
Try a theme or something that does not affect kernals,
Just my thoughts
sent from my Atrix via XDA premium
Pirateghost said:
my vivid will be here in the next day or 2. once i have that, i will risk the Atrix2 and start working on a rom.
Click to expand...
Click to collapse
I still have 20 days to be a guinea pig LoL
If you really feel like being a ginuea pig you should try flashing the zip from this thread. It's a few posts down.
http://forum.xda-developers.com/showthread.php?t=1331644
sent from my Atrix via XDA premium
marko! said:
If you really feel like being a ginuea pig you should try flashing the zip from this thread. It's a few posts down.
http://forum.xda-developers.com/showthread.php?t=1331644
sent from my Atrix via XDA premium
Click to expand...
Click to collapse
i wouldnt. i havent even modified the updater-script to be right yet....
hell, i made it, and even i wouldnt flash it in that state
I dont see any zip in that thread? Are you referring to the system.img.zip pirateghost posted? That was in the recovery thread?
Pirateghost said:
i wouldnt. i havent even modified the updater-script to be right yet....
hell, i made it, and even i wouldnt flash it in that state
Click to expand...
Click to collapse
Thanks for the heads up!!
I'm unable to reapply the patch up to 55.13.15
Code:
contents of partition "boot" didn't match MTD:boot:8388608:9651a551679347926bb7589bb4b57d8dea357cb4:8388608:b56beaeb976b10b86cdbd38e87024ab16fe1197f
I've supposedly restored the boot partition with cwm, oh well.
This is probably to be expected. I'm guessing I can only get the stock boot partition back with a proper fxz flash to stock...
edit: I don't think cwm is even saving a boot image. I don't see one in any of my backups.
Makes me wonder what it's doing when I restore boot
JRW 28 said:
I dont see any zip in that thread? Are you referring to the system.img.zip pirateghost posted? That was in the recovery thread?
Click to expand...
Click to collapse
he was talking about this post:
http://forum.xda-developers.com/showpost.php?p=19033826&postcount=7
Just because I'm willing to try things doesn't mean I'm willing to knowingly brick my phone.
Thanks PG!!
Oddly enough it was the Bionic recovery installed from Mod Manager is what I had installed when I bricked my phone.
Pirateghost said:
i wouldnt. i havent even modified the updater-script to be right yet....
hell, i made it, and even i wouldnt flash it in that state
Click to expand...
Click to collapse
well thhats good to know !
does any flashing work with cwm? ie flash files to system? i can see nandroid not working, but simple flashing should.
svtfmook said:
does any flashing work with cwm? ie flash files to system? i can see nandroid not working, but simple flashing should.
Click to expand...
Click to collapse
No. I built several zip files to flash and cwm nor the bionic bootstrap worked.
I think we may have to wait for the official cwm release, with our device in it.
Jim
Sent from my MB865 using XDA App
Ok, Ive unlocked my bootloader, installed CWM, rooted my device and checked that it worked, and when I go to the boot loader and select recovery it takes me to CWM. Ive made backups from it and and they restore fine. I even installed a custom kernel and it worked because noFrills let me OC/choose a different governor. Yet from the three ROMs Ive tried so far, they install fine, no errors from CWM, but when I boot up it just gets stuck booting forever. Ive tried wiping everything, Ive tried wiping some things, heck I even tried wiping nothing but I still get the same issue. Id really like to try a new ROM now that I went through the trouble of voiding my warranty, so please try to help me. Thanks in advance, alexbenh
Same here
Gonna try out this guy's method real quick except with CWM
http://forum.xda-developers.com/showpost.php?p=49668571&postcount=5
I know this seems obvious, but are the ROMs you are flashing specific for your device?
Sent from my ST18i using xda app-developers app
yes, I have the Moto G XT1034 and have flashed ROMs before on my old galaxy exhibit and never had any trouble with that
Join the club, same here, done everything right but no custom rom joy for me
Sent from my XT1032 using XDA Premium 4 mobile app
If you're flashing a kitkat ROM, make sure you're already running KitKat. If you're still on 4.3, then fastboot flash the stock 4.4.2 image first, then try custom roms
Sent from my XT1034 using Tapatalk
WOOOHOOO, I reinstalled the stock 4.4 firmware and everything, I couldnt root it with superboot so I just skipped the rooting step. Then I flashed CWM through the bootloader although I decided to take a risk and instead of "fastboot flash recovery recovery.img", I did "mfastboot flash recovery recovery.img" just to see if it would change anything. Not sure if thats why it works for me now, but its worth a try. Good luck to the rest of you who have this problem.
lowrider262 said:
If you're flashing a kitkat ROM, make sure you're already running KitKat. If you're still on 4.3, then fastboot flash the stock 4.4.2 image first, then try custom roms
Sent from my XT1034 using Tapatalk
Click to expand...
Click to collapse
Yes, I was already running the stock 4.4 ROM the only differences was that I had a custom kernel which could possibly be an issue, but I wouldnt think so
http://forum.xda-developers.com/showthread.php?t=2620060&page=2
BBOXPT said:
http://forum.xda-developers.com/showthread.php?t=2620060&page=2
Click to expand...
Click to collapse
huh, I had not tried using TWRP, but I thought CWM had a fix permissions command as well.
alexbenh said:
huh, I had not tried using TWRP, but I thought CWM had a fix permissions command as well.
Click to expand...
Click to collapse
My experience. I tried CWM then loaded a Rom, the first one I tried being CM11 = Bootloop, Then I tried several other Rom's and always the same result, spinning on Bootloop
I then put the phone back to stock firmware 4.4.2 and tried TWRP version TWRP2630, no joy even the bootloader wouldn't work right.
Finally put the phone back to stock AGAIN (now getting frustrated!) and tried installing TWRP2631 using fastboot. That did the trick, now all ROM's load and run fine. This version of TWRP appears to be working well. Backup/restore works, and no problems at all.
Other's report CWM works well, but not for me unfortunately.
Dear guys, so here is my issue. I previously used the 4.2.2 rom by edison and has managed to flash it using the Atrix 2 bootstrap methodhttp://forum.xda-developers.com/showthread.php?t=1346977. And now, I wanted to try out the 4.4 ROM using the same bootstrap method as well. However, after I pressed "Bootstrap Recovery" and "reboot Recovery", the phone reboots into the M logo, and then its screen just stays black and blank forever.
The first method I tried to fix it is by getting into the Recovery (Home+Vol Up+Vol Down), and after trying out several reboot options, still to no avail. And now, I have performed "wipe data factory" and "wipe cache" in the recovery option. So what should I do now? I cant access the CWM or bootstrap to install my ROM or to perform any restorations.
Sorry guys that I have to asked this, but I did it to prevent myself from further plunging into the hard brick state.
kenlohwj said:
Dear guys, so here is my issue. I previously used the 4.2.2 rom by edison and has managed to flash it using the Atrix 2 bootstrap methodhttp://forum.xda-developers.com/showthread.php?t=1346977. And now, I wanted to try out the 4.4 ROM using the same bootstrap method as well. However, after I pressed "Bootstrap Recovery" and "reboot Recovery", the phone reboots into the M logo, and then its screen just stays black and blank forever.
The first method I tried to fix it is by getting into the Recovery (Home+Vol Up+Vol Down), and after trying out several reboot options, still to no avail. And now, I have performed "wipe data factory" and "wipe cache" in the recovery option. So what should I do now? I cant access the CWM or bootstrap to install my ROM or to perform any restorations.
Sorry guys that I have to asked this, but I did it to prevent myself from further plunging into the hard brick state.
Click to expand...
Click to collapse
You installed rom with bootstrap. That's outdated method which only works with wang's CM10/10.1 builds. Newer builds is using BMM only. So with any 4.2< ROM you must use Boot Menu Manager. So you'll need to reflash stock rom via RSD Lite. By the way what's your phone model (MB865 Retail, ME865 China or MB865 at&t?)? First thing before flashing is correct fxz.
-edited-
turffe said:
You installed rom with bootstrap. That's outdated method which only works with wang's CM10/10.1 builds. Newer builds is using BMM only. So with any 4.2< ROM you must use Boot Menu Manager. So you'll need to reflash stock rom via RSD Lite. By the way what's your phone model (MB865 Retail, ME865 China or MB865 at&t?)? First thing before flashing is correct fxz.
Click to expand...
Click to collapse
thank you so much for the prompt reply. So my location is in Malaysia>South East Asia, and it should be MB865. Do i use the 'Android 4.0.4
Blur_Version.67.220.3.ME865.Retail.en.05' file to fxz it? found from the sbf developer site
My previous OTA was 4.0.4, i was worried that if i used it on the earlier custom ROM 4.2.2 that i had, i will hard brick it. So will there be any cause for concern?
and what do they do with the .xml file in the file prior to fxz it? is it fine if i skip that step?
On the phone's back is written ME865 or MB865? Is there any AT&T logo on it? If your phone model is Retail MB - you should flash 6.7.2-EDEM-18.
Sent from my Atrix 2 using Tapatalk
turffe said:
On the phone's back is written ME865 or MB865? Is there any AT&T logo on it? If your phone model is Retail MB - you should flash 6.7.2-EDEM-18.
Sent from my Atrix 2 using Tapatalk
Click to expand...
Click to collapse
MB865, therefore i suppose it should be Blur_Version.672.1.18.MB865.PSHAsiaRetail.en.03. Unfortunately I had sent the phone to a repair guy, so no chance for me to try it out yet. Will update you tomorrow!
that guy wasnt able to repair it, so I did it myself using "Blur_Version.672.1.18.MB865.PSHAsiaRetail.en.03" as the sbf file, and TADAA, problem solved within 10 minutes! Thanks alot for the help, RSD is truly the all-in-1 safe kit
kenlohwj said:
that guy wasnt able to repair it, so I did it myself using "Blur_Version.672.1.18.MB865.PSHAsiaRetail.en.03" as the sbf file, and TADAA, problem solved within 10 minutes! Thanks alot for the help, RSD is truly the all-in-1 safe kit
Click to expand...
Click to collapse
I'm glad you got it figured out. :thumbup: