Related
I've been trying to help a friend flash ROM's to his X. We've installed the paid Bootstrap and Rom Manager. We then utilized the bootstrap utility, and flashed clockworkmod recovery. We then go to the Download rom section of Rom Manager and choose FlyX, it downloads, we then check backup current rom, and wipe data, continue. The phone attempts to boot into clockworkmod but wont. It does the update package part, fails, and then reboots normally. I should also note that when I attempt to boot into clockworkmod recovery via bootstrap it is successful. Could I find the downloaded Rom via the menu in clockworkmod and install it that way? Is there a step in installing Clockworkmod that I'm missing? I've been checking the forums but all I can find for solutions is people saying to install bootstrap again. I've uninstalled and reinstalled both programs twice and nothing has changed. Thanks so much in advance for the help.
open rom manager and click on flash clockworkmod recovery.
everything you download with rom manager goes into the /clockworkmod/download folder on your mem card.
Tried that.didn't work.
Sent from my ADR6300 using XDA App
You need to open up Bootstrap and select the top option... then you can proceed to Rom Manager.......Rom Manager cannot flash CW onto the DroidX that why we need Koush's Droidx Bootstrapper. Give that a try also Note i hope that you have booted into CW and made a Nandroid backup of your friends current phone state.. If that still doesnt work for you.. download the ROM off a forum and do it manually.
mptrh336 said:
I've been trying to help a friend flash ROM's to his X. We've installed the paid Bootstrap and Rom Manager. We then utilized the bootstrap utility, and flashed clockworkmod recovery. We then go to the Download rom section of Rom Manager and choose FlyX, it downloads, we then check backup current rom, and wipe data, continue. The phone attempts to boot into clockworkmod but wont. It does the update package part, fails, and then reboots normally. I should also note that when I attempt to boot into clockworkmod recovery via bootstrap it is successful. Could I find the downloaded Rom via the menu in clockworkmod and install it that way? Is there a step in installing Clockworkmod that I'm missing? I've been checking the forums but all I can find for solutions is people saying to install bootstrap again. I've uninstalled and reinstalled both programs twice and nothing has changed. Thanks so much in advance for the help.
Click to expand...
Click to collapse
YOu need to download Koush bootstrap http://koush.tandtgaming.com//motorola/droidx/DroidXBootstrap.apk
So after I gain root, I open Bootstrap? I then hit the "Bootstrap Recovery" button? Then I open Rom Manager and click "flash the latest ClockworkMod Recovery", which I beleive is 2.5.0.7? Do I hit the "Reboot Recovery" button in Bootstrap after I flash the latest CW recovery?
that will get you into clockwork mod yes.
This helped, thanks everyone
Having the same problem. Im trying this hopefully I can get clockwork recovery to work
Sent from my PC36100 using Tapatalk
I have tried this several times, even re-installing rom manager and boot strap and everytime i reboot it will not go into the rom manager recovery mode. any ideas/and or advice will help
P.S. I have wiped several times and i am running .596
I had an earlier version of cyanogenmod installed, I went into rom manager and pressed update (or something like that). It did the whole installation thing but now it's just hanging at the cyanogenmod splash screen.
What do?
silverback88 said:
I had an earlier version of cyanogenmod installed, I went into rom manager and pressed update (or something like that). It did the whole installation thing but now it's just hanging at the cyanogenmod splash screen.
What do?
Click to expand...
Click to collapse
Have you tried to boot into recovery ? (turning it on by pressing the power button and the - volume button)
Did you backup? Always, always backup.
If not try downloading the ROM and flashing that, don't wipe just yet, if that fails you will probably need to wipe and flash again.
ok so i did a recovery of the backup i did just before trying to install cyanogen 7
FFUUUUU.... now everything is pretty much lost! even the old cyanogen is gone. What can I do?!
Was your old backup from a pre 2.3 ROM?
^^ how can i tell?
sorry for being a noob
What was the ROM you backed up before flashing CM7?
the backup i did just before trying to install cyanogen 7
Click to expand...
Click to collapse
it was cyanogenmod 6.1.3
Ok, your problem now is that the file system changed from 2.2 (Froyo) to 2.3 (Gingerbread) and you will need to flash a new version of ClockworkMod Recovery to restore that backup.
Do you have ENG S-OFF? You will be able to flash it via fastboot, if not you will have to start again from CM7 and downgrade ClockworkMod Recovery from there, then restore your backup.
I flashed the latest ClockworkMod Recovery (3.0.0.6) - I think before I tried to install CM7.
Restoring the backup means almost everything is gone, apps, settings, etc (but not everything). Did I **** it up? Will I have to redo everything?
If I have to do that anyway I might as well use CM7, but installing that means the splash screen hangs (I had the same problem with CM6, I dont remember how I fixed it)
Your right, to flash CM7 you needed CWM 3.x.x.x
Restoring that backup 6.1.3 will take you back to pre-CM7 so yes everything will be gone.
Have you tried just flashing CM7 again?
ok, trying to install cm7 again...
Don't wipe just yet, if it still hangs after flashing again you will then have to wipe.
****, it's hanging at the CM7 splash screen again
Ok, you will need to perform a wipe.
In CWM you have "mounts & storage"
Format boot & system, then flash CM7 again, (btw which CM7 ROM are you flashing?)
I did that (through the recovery or w/e) and then it was hanging at the HTC logo....
I had to restore the backup once again and am back where I was before
What can I do?
btw it's CM 7.0.0-RC2
Ok sounds like a full wipe is needed.
Again in CWM "mounts and storage" format everything except scdard, then back out and go into "advanced" and wipe dalvik cache.
Flash CM7 again, it should work now.
can i flash CM7 through the recovery console? because if i wipe everything then obviously i cant boot back into it?
Don't worry you can't wipe recovery from within recovery, so after a full wipe it will still be available.
before I do that, how exactly do i install CM 7 from recovery console? I think it was downloaded to my SD card but I dont see a straight forward option in the recovery console
Hi guys,
I need help! I messed up my phone
I tried installing Cyanogen mod as advised here:
http://forum.xda-developers.com/showthread.php?t=1338183
and it seemed to work fine and booted into the mod. However, I then noticed that I did not have any Google apps (I thought they would be there), so I checked the thread on XDA that said that you needed to flash those too. So when I tried to do that, by using Bootstrap recovery and rebooting, my phone is now stuck booting with the red "M". Nothing else happens.
I have tried booting into recovery, but only stock recovery is available. I have tried wiping data/cache, it did not work. I have tried renaming the mod to update.zip and applying that, but it says "signature verification failed".
Please, please help! What can I do?
PS: I did try posting in the relevant thread, but the forum will not let me post in the development section.
Thanks a million!
Do this = http://forum.xda-developers.com/showthread.php?t=1032372
o/
Thanks so much for your reply. Not sure which SBF file to choose? I am in the UK. Thanks!
I'm not sure.. but I think "2.2.2 Service Version" -> UK
Negruslito said:
Do this = http://forum.xda-developers.com/showthread.php?t=1032372
o/
Click to expand...
Click to collapse
Thanks so much! That guide was very useful, with a few modifications:
Phone needs to be UNPLUGGED first, then powered on like this: camera + volume down + power. Then connect USB cable. You also need Motorola drivers and the latest version of RSD that MUST be run as admin. The SBF file MUST be in the RSD application folder. Then it worked! Phew!
A million, million thanks!
Lisali said:
Thanks so much! That guide was very useful, with a few modifications:
Phone needs to be UNPLUGGED first, then powered on line this: camera + volume down + power. Then connect USB cable. You also need Motorola drivers and the latest version of RSD that MUST be run as admin. The SBF file MUST be in the RSD application folder. Then it worked! Phew!
A million, million thanks!
Click to expand...
Click to collapse
Do not use bootstrap with any custom.. will brick your phone
Instead turn your phone on.. when 2nd M logo appears the led light will turn on (blue).. just press VOL-.. then go to Recovery, Latest Recovery.. this time use vol +- to navigate and power button to choose
Sorry about my poor English..
Hi there
Thanks so much for your reply.
But it says here to use bootstrap to install Cyanogen mod? Don't you have to use that?
http://forum.xda-developers.com/showthread.php?t=1338183
Thanks! Oh - and your English is great!
You have to use bootstrap, when you are on stock and want to custom rom. Without bootstrap, you can't install custom rom
After installing bootstrap, it's recommended to install newer CWM by installing http://forum.xda-developers.com/showthread.php?t=1196590 from current CWM from bootstrap... And after that you can finally install custom ROM from updated CWM 3.1.
And AFTER installing custom rom, THEN you should NOT install bootstrap. You should not install bootstrap from custom rom Hope it's clear now.
tl;dr: you MUST install bootstrap, to go into custom rom; you should not install bootstrap when/after you are actually on custom rom*
* (because custom rom has own 2nd init etc. and by installing bootstrap you would destroy it and cause brick (not permanent of course)
Anonymous_ said:
You have to use bootstrap, when you are on stock and want to custom rom. Without bootstrap, you can't install custom rom
...
And AFTER installing custom rom, THEN you should NOT install bootstrap. You should not install bootstrap from custom rom Hope it's clear now.
tl;dr: you MUST install bootstrap, to go into custom rom; you should not install bootstrap when/after you are actually on custom rom*
* (because custom rom has own 2nd init etc. and by installing bootstrap you would destroy it and cause brick (not permanent of course)
Click to expand...
Click to collapse
Thanks SO much for that, it makes sense now!
So once I have installed Cyanogen, and an update for it is released, how do I flash that? And will that delete all my data & apps?
Thanks!
Lisali said:
Thanks SO much for that, it makes sense now!
So once I have installed Cyanogen, and an update for it is released, how do I flash that? And will that delete all my data & apps?
Thanks!
Click to expand...
Click to collapse
Once you have CM installed, then when update is released, you simply go into recovery (hold power and select reboot, then recovery, then it will reboot into bootmenu, where you are supposed to choose boot, then recovery and then latest), where you find option named "install zip from sdcard". So you choose this option, then select zip file with update on your sd card and after success installation, select wipe cache and advanced wipe dalvik cache, then reboot and it should boot ok, with your apps and other data - but I always recommend to backup via titanium backup, before flashing any update, because if you meet any error, you have to wipe also data from recovery... and you lose your data and apps after data wipe
Anonymous_ said:
Once you have CM installed, then when update is released, you simply go into recovery (hold power and select reboot, then recovery, then it will reboot into bootmenu, where you are supposed to choose boot, then recovery and then latest), where you find option named "install zip from sdcard". So you choose this option, then select zip file with update on your sd card and after success installation, select wipe cache and advanced wipe dalvik cache, then reboot and it should boot ok, with your apps and other data - but I always recommend to backup via titanium backup, before flashing any update, because if you meet any error, you have to wipe also data from recovery... and you lose your data and apps after data wipe
Click to expand...
Click to collapse
Thanks so much for your thorough explanation! This should be added to the main threat sticky. You're a star!
I have had my N7 for a week now, and have unlocked and rooted it. I flashed the jr5 rom and it worked ok, but i decided I wanted to try the pure AOSP rom, so I did a data/cache/dalvik wipe and flashed the rom. It proceeded to boot and freeze at the Google screen. I rebooted into recovery, and attempted to restore from my backup (failed), flash the jr5 rom (failed), and reflash the AOSP rom (failed). I then decided to follow the instructions on ROOTZwiki and restore back to stock (although still unlocked). I restored to the factory image, and attempted to flash the CM10 AOKP rom, and was again met with the frozen Google screen. I made sure to wipe data and both caches each time i tried to flash a rom, but I always end up stuck at the Google screen. What could be causing this? I would really like to know if anyone has any idea, because I fully plan on running the full version of CM10 when it is released.
By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app
redmonke255 said:
By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
yes i did a factory data reset each time. I am currently running v5.8.0.2 of cwm
could that be the problem? that my cwm is just outdated already?
No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium
CharliesTheMan said:
No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thank you for taking the time to help me. Before I do the goo-manager/twrp install, are there any inherent advantages or disadvantages of using twrp as opposed to cwm? Also, I hadn't thought to check md5s after moving the roms, so I will be doing that from now on.
Twrp works just fine.
In your recovery, can you mount and unmount all your partitions without any errors?
Sent from my Nexus 7
am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?
crache said:
am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?
Click to expand...
Click to collapse
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.
simms22 said:
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.
Click to expand...
Click to collapse
I don't like Twrp not being able to boot into recovery from holding the buttons, especially running into these loops during installs. Had the sameresults with cwm though.Now I am having this boot loop with TeamEOS as well as Skanky (neither package gapps) I however only loop if installing gapps after the rom or wiping caches.
If caches and system are wiped, gapps installed, then the rom I get a functioning system.Can anyone shed some light on what trigers specific loops or how to review tje errors / panics?
I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?
spked said:
I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?
Click to expand...
Click to collapse
Do you flash the rom and gapps and then reboot, or flash the rom, reboot, then flash gapps?
Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.
dirtyhamster73 said:
Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.
Click to expand...
Click to collapse
Can you get to bootloader?
If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2
Jordanooo said:
Can you get to bootloader?
Click to expand...
Click to collapse
I finally got in, so I'm all set. Thanks! I have no idea why I was having a hard time...twrp wouldn't pop up once I was in boot loader. I must of tried like 20 times. Anyway....I'm in and I just reflashed and it was fine.
---------- Post added at 05:42 PM ---------- Previous post was at 05:40 PM ----------
armyboy11b said:
If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'm using twrp...for whatever reason I couldn't get it to pop up to reflash. But I'm good now. Thanks!
I read this post:
http://forum.xda-developers.com/showthread.php?t=1768702
and I was eager to try to have Android 4.1 on Defy. Amazing that this guys put it on the defy.
I read the FAQ where it says;
Your phone has to be roooted.
► If this is the first time that you install custom rom (if you have stock froyo) you'll have to do some other things before this procedure. Please search the forum.
► Download all the files that you need and put them on the sdcard.
► Charge your phone until you have 80-100% battery.
► Make a backup of your apps and a nandroid backup of your rom (everything you have on your phone will be deleted).
It was rooted I have stock froyo, it doesnt say what to do before the procedure. I Imagine that it means that I need a Kernel for 2.3 or above.
I made a backup of apps with Titanium and I installed System recovery apk ( defy-recovery-1218-0326). I think this is Clockworkmod recovery... but not really sure, very nooby.I reboot the phone and back it up.
then I re read the part that says that i have other things before installing 4.1, so I decided to download CM9 kernel and sndinitdefy2.0 apk. I run the apk. After it booted in development mode i change the 2nd init with the recovery menu. then reboot again.
After that the screen only showed the Motorola Logo with a black screen.
I screwed up. So I decided to install RSD lite 5.6 to flash the original Froyo rom again to see if it works.
It did, I flashed it back, then I installed all over again, but when trying to install defy-recovery 1218 it fails.
so I looked for sndinitdefy and found the 2.3 version which i installed.
So now, I have stock froyo working again and sndinitdefy 2.3 installed, but dont know if its ok.
When I boot in developer mode, the screen says:
---------------------------------------------------------------------------------
Android System recovery 3e
Android system recovery utility (which is unreachable with the volume keys.)
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
and then at the botom
e: cant open /cache/recovery/command
e: cant open/cache/recovery/caller.
----------------------------------------------------------------------
So, I cant even recovery my aplication data because its not on the recovery menu.
Also in the FAQ it says go stable recovery. I dont know how to do that or what to install or to do.
1) Go to Stable Recovery.
2) Wipe data/factory reset, wipe cache and go to advanced ► Wipe dalvik.
3) Go to Install zip from sdcard ► Choose zip from sd card.
4) Flash CM9 Kernel (JUST FOR DEFY RED LENS USERS).
5) Flash CM10-2012xxxx-NIGHTLY-mb526.zip.
6) Flash Gapps and Battery fix for red lens.
7) Wipe Cache and Dalvik again (recommended).
8) Restart.
2- it doesnt have advanced to wipe dalvik.
3-I have defy but red lens. it says to flash cm9 kernel, i imagine that i have to do it from install zip from sdcard and have the file on the phones root.
Anyway, my recovery screen is not ok and im not sure what to do. Can anybody help!?
narrowing the stuff.
I have Android 2.2 and a red lens defy with a faulty recovery menu sndinitdefy 2.3 and i want to install Android 4.1. Also I want to be able to go back if there is any trouble. please let me know how to go forward from here.
Also it would be great if I have the backup/restore menu in the recovery so I can restore my apps, but dont know how to do that.
Or maybe I should flash the CM9 kernel with RDS lite as i did with 2.2... but then again, i dont know if that is a fixed SBF or what, i dont want to screw my phone...
Thanks!
Ok, problem solved! I had to wait for the blue led to enter sndinitdefy2.3. I was entering elsewhere, To the Normal recovery I think.
installed from Custom Recovery instead of Stable Recovery. Stable Recovery was not available,but it worked perfectly for me, now running Android 4.1 and its AWESOME.