I used the windows one click root method and I have root, however my droid 2 will not boot to CW recovery from ROM Manager.
I have scanned and did not see an answer..
Thanks for all of your hard work!
Sent from my SCH-I500 using XDA App
You need to download bootstrap recovery to boot into recovery
The D2 has a locked bootloader (thanks efuse) which prevents us from installing a custom recover. The bootstrap recovery is the only way to get to clockwork (I don't really know how it works cause im not a dev, but it does so thats all i need! lol).
So, as stated above, just download the bootstrap recovery, install and run it, hit bootstrap recovery (will be prompted to give superuser) and wait till it says success (should just be a few seconds), then hit reboot recovery and flash away!
Note* I believe you only have to hit bootstrap recovery once, then you can just hit reboot recovery when you need to flash. (I think after you flash a new rom you will have to hit bootstrap recovery again though but i could be wrong on that)
Thanks. Bootstrap worked great. Quick question though, how do you do custom ROMs?
Sent from my SCH-I500 using XDA App
Download the rom you want and put it on the sd card.
1: Boot into recovery via bootstrap.
2: Do a backup.
3: Now, go to the mount option and be sure data and cache are mounted.
4: Now wipe data and cache, then go to advanced and wipe dalvik and battery stats.
5: Go back and make sure everything is still mounted.
6: Go back to main menu and select install from sd card.
7. Select choose zip from sd card
8. Scroll down till you see your rom and select it then select yes. and wait for it to complete.
9. Reboot the phone and enjoy your new rom. (Booting the phone for the first time after flashing a new rom can take a few minutes so be patient.)
Sent from my Motorola Droid 2 with Squidly 2.3.0
Wow thanks! You guys are great!
Sent from my SCH-I500 using XDA App
No problem. Hope it helped.
Sent from my Motorola Droid 2 with Squidly 2.3.0
is there still anyone working on cracking the bootloader on the droid2.. droidx and milestones?
Cracking the bootloader seems unlikely. Unless a leak happens it's highly unlikely that a brute force method with crack it (order of magnitude is in years beyond the life of the universe).
aliasxerog is working on instead hijacking the boot process with a custom init that will hot swap a new kernel. In theory this should work just fine since the bootloader can load any kernel it wants and then hands off the rest of the boot process to init. What happens from there is out of Motorola's (and eFuse's) hands.
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
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 .
I am a total noob and am having trouble installing CyanogenMod onto my Nexus S 4G. I barely rooted the darn thing, and I am using a guide that involves ROM Manager. It says I have to mount the SD card using ROM Manager, but I can't figure out how to. If there is a better way to install CyanogenMod, please tell me, because all the guides I have been finding are way too technical for me to understand, and I have been trying. Any help is appreciated.
Can you tell us which guide you are using and which step you are on? I think you must mean ClockworkMod not ROM Manager.
Sent from my Nexus S using XDA App
If you already have clock work then all you have to do is drag and drop cyanogen into the root of your sd card. Then flash through clock work.
ht tp://ww w.redmondpie.com/install-cyanogenmod-7.1-gingerbread-rom-on-nexus-s-4g-how-to-tutorial/
That's the guide I was using, I got stuck on step 4.
Is the rom the .zip file I downloaded from the cyanogen site, or is it inside the folder?
The rom is the zip file. Boot into recovery and select choose zip from sd and navigate to it and install it.make sure to do a back up and wipe cache,dalvic and do a factory rest before flashing the rom
Sent from my Nexus S 4G using XDA Premium App
Paleryder said:
make sure to do a back up and wipe cache,dalvic and do a factory rest before flashing the rom
Click to expand...
Click to collapse
Can you explain this part more? Is this the part of the guide that says "make a nandroid backup"?
1. Mount USB and drag and drop cm7 zip & Google apps into root of SD card.
2. Turn off nexus.
3. Boot into fastboot by holding volume up and then power button.
4. In fastboot go to recovery (power button is used as enter button, volume buttons represent up and down)
5. In recovery go to backup and restore and back up your current rom.
6. Go back and then wipe data factory reset and also wipe cache.
7. Go to advanced -> Wipe delvik cache.
8. Go back and then go to install zip from SD, find cm7 flash it, then flash Google apps. You can flash kernel right now if you want.
Hope this clears anything up
Sent from my Nexus S 4G using XDA App
I got to your step 5, but when I choose Recovery, after showing the Google logo it briefly shows a box and an arrow coming out of the box and an Android logo, then the box changes to a triangle with an exclamation mark. It stayed like that so I just rebooted the phone.
seb0910 said:
I got to your step 5, but when I choose Recovery, after showing the Google logo it briefly shows a box and an arrow coming out of the box and an Android logo, then the box changes to a triangle with an exclamation mark. It stayed like that so I just rebooted the phone.
Click to expand...
Click to collapse
That means you don't have Clockwork recovery installed. You need to download the latest Clockwork recovery image and place it in the tools folder of your Android SDK Folder(wherever you placed it). Then press shift and right click on the tools folder and select "open command prompt here". Then boot your phone into bootloader by pressing volume up and power button at the same time. Connect your phone to your computer via usb cable and in the command prompt you opened type: fastboot flash recovery name of recovery image here.img and press enter and you will see in the command prompt window it will say sending image. When it is done scroll down to recovery on your phone using the volume buttons and press power to enter. Your phone will reboot into Clockwork recovery and from there you can continue on the previous posts steps. Hope this helps. You can download the latest Clockwork by going to this thread: http://forum.xda-developers.com/showthread.php?t=1078213 and clicking on the brown "CWM Recovery" under 'How to: Root the Nexus S 4G'.
well I'm pretty sure I do have clockwork because there's a folder on my phone that is called clockworkmod, and I did root the phone successfully at the very least, but I'll try putting a new one there.
seb0910 said:
well I'm pretty sure I do have clockwork because there's a folder on my phone that is called clockworkmod, and I did root the phone successfully at the very least, but I'll try putting a new one there.
Click to expand...
Click to collapse
Alright here is a little run down on whats going on with your ns4g, you probably already flash clockworkmod on your nexus, but what samsung did was that it will try to revert back to the stock recovery. So what you have to do is flash Clockworkmod again to make it stick. Honestly it is good that it doesn't stick because then it would be easier to unroot the phone.
So now you have 2 different options on how to flash clockworkmod. 1) you can do it through fastboot but you have to have adb set up. I'm not sure what method you used to root your phone so i am just assuming.
2) you can download rom manager and flash clockwork through there. (Honestly i haven't done it through this method so i cant tell you of the pros or cons that are attributed with this).
NOTE: If you dont have super user yet it would be a prime time to flash it once you got CWM going.
For me, I only needed to flash clock work twice through fastboot in order to make it stick.
Good luck.
The guide I originally was using for this had me using rom manager, but it kept telling me I had to mount the SD card even though it was shown up in my computer.
If I were to flash clockwork again with adb setup, how would I do that? Sorry to be so asky, I just want this process to end correctly.
You have to set up adb if you don't have it already, go to ns4g development and go to vandam's thread that has all the list of rom's and rooting guides. Check out wolverines rooting guide, he goes indepth on how to set up adb. It make take awhile to set up but learning how to work in fastboot is essential in rooting the nexus.
Good luck
Sent from my Nexus S 4G using XDA App
Well it was confusing and I almost asked for help again, but I finally got it flashed again and now cyanogen is working. I really appreciate the help and for pointing neon the right direction. As a final note, is there anything else I should know, like updating or something, just general knowledge (basically, "now what?")?
seb0910 said:
Well it was confusing and I almost asked for help again, but I finally got it flashed again and now cyanogen is working. I really appreciate the help and for pointing neon the right direction. As a final note, is there anything else I should know, like updating or something, just general knowledge (basically, "now what?")?
Click to expand...
Click to collapse
Did you get all the Google Apps installed too? That's the only "unusual" aspect of CyanogenMod.
Yep I got the Google apps.
Congrats dude its good you got it all working, BTW when ever you switch roms like from CM7 to miui you always have to wipe data, cache, and delvik cache. Delvik cache is in the advanced tab of CWM. If your just up updating from different versions of the same rom, you just need to wipe cache and delvik cache. That's about it, the hard part is done, enjoy flashing.
chewbz said:
Congrats dude its good you got it all working, BTW when ever you switch roms like from CM7 to miui you always have to wipe data, cache, and delvik cache. Delvik cache is in the advanced tab of CWM. If your just up updating from different versions of the same rom, you just need to wipe cache and delvik cache. That's about it, the hard part is done, enjoy flashing.
Click to expand...
Click to collapse
Actually if you are updating from different versions of the same rom, you don't need to wipe anything, you just flash it.
Ok guys..... newbie here .... literally I'm new to Boot unlocking, root, Flashing etc.
Anyway I have followed this forum for so long that I decided to take plunge yesterday and get my hands dirty.
Here is what I did:
Unlock bootloader, root and install recovery on my Atrix 4G. Atrix was @ 2.3.4 and 4.5.91 during unlocking & root.
Rebooted the phone and everything seems to be in place. Atrix loaded like the way I bought it 7 months back. No problem until now.
Also created a restore folder on my external SD. Worked fine and was successful in creating backup with time stamp
Now here are my steps and subsequent issues that I'm facing:
1. Downloaded CM9 zip file from this thread(http://forum.xda-developers.com/showthread.php?t=1500535) along with Gapps to my external SD
2.Entered recovery mode during bootup and tried to flash CM9 and Gapps. Flashing seem to have gone well and completed (note I did not do clear data, clear cache or clear dalvik cache under advanced options being a newbie)
3. Reboot the phone and can only see red Moto logo and unlocked on top. Left for about 5 minutes and nothing happened.
4.Did a battery pull and entered recovery mode. wiped data, cache & cleared dalvik cache
5.Went to Install zip from sdcard option and tried to reflash CM9. Flashing seems to have gone well and completed
6. Reboot phone and again can only see Moto Red logo with unlock on top and nothing more.
7.Battery pull followed by recovery. But This time I tried to restore from my external SD. also wiped data, cache & dalvik cache
8.Restore took about 3 minutes and completed.
9.Reboot the phone. Now the phone boots and goes to Rethink possible screen and get sstuck.
10. Left it for 1 hr....nothing.
11.tried steps 7-9 again and still stuck in "Rethink possible" screen during boot.
What did I do wrong? Did I soft brick the phone? I can still enter recovery mode and read my internal and external SD and can see all files. i hope I didn't brick my phone doing this. If I did, I would regret!
Here are my options:
1.Try a stable ROM like CM7 and see what happens. I didn't want to do too much damage so haven't tried this option yet.
2.I know there is a way to hide 'unlock' during boot up (if someone can point to it obviously). Hide the 'unlock' and return the phone to ATT and tell them that phone would not boot after 2.3.6 update and get a refurbished one
Please let me know what your thoughts are. I'm currently crapping on my pants
Edit: I just tried Newtrino rom and stuck @ Moto screen which says unlock.
Edit 3/4/2012: Please go to the last post for the solution. Tenfar's CWM is old and cannot deal with latest ROMs. Use ROMRACERS latest CWM or touch based Koush's CWM for future ROM flashing.
Old CWMs will give you sleepless nights!
Ok tried restore again after wiping data, cache & dalvik cache.
Now after reboot, My Moto Logo screen says unlock and just starts flashing.
I can still get into recovery......
can someone please help me......
What you can do is: install a "stable" ROM of Gingerbread:
--Go in recovery, put a .zip of the ROM on your sdcard (with your computer), and after wiping data, install it .zip.
--Or you install a new ROM with fastboot
Anyway, be careful with your battery, because if it is empty, with no ROM on your phone, it'll be crap!
vsg005 said:
What you can do is: install a "stable" ROM of Gingerbread:
--Go in recovery, put a .zip of the ROM on your sdcard (with your computer), and after wiping data, install it .zip.
--Or you install a new ROM with fastboot
Anyway, be careful with your battery, because if it is empty, with no ROM on your phone, it'll be crap!
Click to expand...
Click to collapse
thank you for your response. However I tried that already Nutrino GB ROM. Again, I would go to 'M' screen which says unlocked and its stuck there for ever.
I used tenfar's CWM. Not sure if I need to use any other CWM. Also since my phone doesn't boot, I'm not sure how I can install any other CWM
Masterguy said:
thank you for your response. However I tried that already Nutrino GB ROM. Again, I would go to 'M' screen which says unlocked and its stuck there for ever.
I used tenfar's CWM. Not sure if I need to use any other CWM. Also since my phone doesn't boot, I'm not sure how I can install any other CWM
Click to expand...
Click to collapse
Don't worry, soft bricks are easy to recover on the Atrix thanks to us being able to access fastboot.
For flashing a new recovery:
While your phone is off, press Volume Up + Power to power up, then release when a menu appears on your screen and navigate with volume down until you see Fastboot, select it with the volume up key.
Get the necessary files for fastboot, place them all in a folder called "moto" in your C: drive, and type in the following in a cmd window (assuming you're using windows and that the recovery image is called recovery.img):
C:/Moto> fastboot flash recovery recovery.img
C:/Moto> fastboot -w
C:/Moto> fastboot reboot
Now access your recovery wipe dalvik cache, cache, factory reset and then flash a new ROM. It SHOULD boot without issues. I personally use Koush's Clockworkmod Touch, also remember that Neutrino tends to get "stuck" sometimes after the first attempt to boot and requires a battery pull and then you try to boot again. (It takes a while)
littleemp said:
Don't worry, soft bricks are easy to recover on the Atrix thanks to us being able to access fastboot.
For flashing a new recovery:
While your phone is off, press Volume Up + Power to power up, then release when a menu appears on your screen and navigate with volume down until you see Fastboot, select it with the volume up key.
Get the necessary files for fastboot, place them all in a folder called "moto" in your C: drive, and type in the following in a cmd window (assuming you're using windows and that the recovery image is called recovery.img):
C:/Moto> fastboot flash recovery recovery.img
C:/Moto> fastboot -w
C:/Moto> fastboot reboot
Now access your recovery wipe dalvik cache, cache, factory reset and then flash a new ROM. It SHOULD boot without issues. I personally use Koush's Clockworkmod Touch, also remember that Neutrino tends to get "stuck" sometimes after the first attempt to boot and requires a battery pull and then you try to boot again. (It takes a while)
Click to expand...
Click to collapse
Many people also seem to have suggested RACEROM CWM. Which one would you suggest? I'm so nervous about all this now. Just have this butterfly in my stomach
flash the latest recovery and wipe everything in recovery and flash neutrino again. It should work after that. try neutrino 2.2 though. 2.5 still has it's kinks.
1st off, relax. It's difficult to brick your phone from this point Just don't get any bright ideas with .sbfs lol.
As others have said, make sure you're on latest recovery.
Question: are you installing from internal or external SD? Internal is recommended for flashing most ROMs.
Sent from my MB860 using xda premium
Masterguy said:
Many people also seem to have suggested RACEROM CWM. Which one would you suggest? I'm so nervous about all this now. Just have this butterfly in my stomach
Click to expand...
Click to collapse
As someone else said, the ONLY thing you should NEVER do is flash an .sbf or go through an OTA update, that's a surefire way to hard brick your phone. From this point on it's VERY DIFFICULT to completely brick your phone using software only.
RomRacer's CWM is based I think on v5.0.2.7? Koush's latest recovery is v5.8.1.5. I honestly couldn't name any tangible differences other than the touch interface, which is the reason I use it in the first place. (I hate mashing volume keys like a madman) It really doesn't matter which CWM you use, but when I soft bricked my phone I recovered with CWM Touch.
I would recharge your battery to 100% before trying to recover it, as that is one less headache to worry about, but if your phone starts saying 'Battery is too low to flash', do not panic, you only need a USB cable you don't mind sacrificing (doesn't have to be new). I will go into detail in case you actually need to do this.
Just make sure you use the fastboot -w command and wipe EVERYTHING through CWM before trying to flash anything else.
Solved:boot loop issue
littleemp said:
As someone else said, the ONLY thing you should NEVER do is flash an .sbf or go through an OTA update, that's a surefire way to hard brick your phone. From this point on it's VERY DIFFICULT to completely brick your phone using software only.
RomRacer's CWM is based I think on v5.0.2.7? Koush's latest recovery is v5.8.1.5. I honestly couldn't name any tangible differences other than the touch interface, which is the reason I use it in the first place. (I hate mashing volume keys like a madman) It really doesn't matter which CWM you use, but when I soft bricked my phone I recovered with CWM Touch.
I would recharge your battery to 100% before trying to recover it, as that is one less headache to worry about, but if your phone starts saying 'Battery is too low to flash', do not panic, you only need a USB cable you don't mind sacrificing (doesn't have to be new). I will go into detail in case you actually need to do this.
Just make sure you use the fastboot -w command and wipe EVERYTHING through CWM before trying to flash anything else.
Click to expand...
Click to collapse
Thanks I was able to fix my boot up issue using ROMRACERS CWM. I didn't use any command prompt or anything. I just downloaded zip file from this thread, entered recovery mode -->Install Zip from SD card --> Chose ROMRACERS zip --> it automatically flashed the recovery and I then rebooted recovery under advanced options.
After that Wiped data,cache & Dalvik Cache and proceeded to install CM9 and it booted up up flawlessly.
I'm kind of surprised that tenfar didn't add a not to use his CWM as the latest ROMs use latest ext format.
That seems to be issue. However, I'm pleased with your guidance and final output. Thanks a lot dude.
Masterguy said:
Thanks I was able to fix my boot up issue using ROMRACERS CWM. I didn't use any command prompt or anything. I just downloaded zip file from this thread, entered recovery mode -->Install Zip from SD card --> Chose ROMRACERS zip --> it automatically flashed the recovery and I then rebooted recovery under advanced options.
After that Wiped data,cache & Dalvik Cache and proceeded to install CM9 and it booted up up flawlessly.
I'm kind of surprised that tenfar didn't add a not to use his CWM as the latest ROMs use latest ext format.
That seems to be issue. However, I'm pleased with your guidance and final output. Thanks a lot dude.
Click to expand...
Click to collapse
Thank you sooo much. I was having this exact problem. I did what you suggested and my phone works. Thanks!
Hi guys!
I have Droid Pro Verizon American.
I have put CM7 V8 by VanillaLVL and then Cm7 V9 by vanillaLVL.
After putting this versions, and then installing Droid 2 Recovery Bootstrap from app store, and trying to Reboot to Recovery i cannot load to the OS.
I have tried to restore to factory settings, but nothing - it just freeze with load screen with M letter - it's doesn't go further.
I have sbf'ed it back, then rooted, then put the CM7 again two times, and every time is the same bug - i cannot reboot to recovery with Droid 2 Recovery Bootstrap installed over the CM7. Does anybody have the same problem? It works ok on rooted stock, but not on CM7.
Do you know how to resolve it? Maybe there is other software for clockworkmod instead of Droid 2 Recovery Bootstrap for CM7?
Anyone?
Any ideas, guys? Really it's not simple bug, it would be good to know what is happening?
Maybe somebody could give some tips how to install clockworkmod manually? without application? I cannot find this info on the internet, everybody says to use rom manager or droid 2 bootstrap.
I believe you just cannot install bootstrap over cm7. So just try:
1. Root
2. Bootstrap
3. Cm7
4. Gapps
5. ????
6. Profit
Sent from my MB855
not.a.troll said:
I believe you just cannot install bootstrap over cm7. So just try:
1. Root
2. Bootstrap
3. Cm7
4. Gapps
5. ????
6. Profit
Sent from my MB855
Click to expand...
Click to collapse
I actually don't understand what you mean. I already have cm7 installed on my phone. The problem was that I used Droid 2 Bootstrap on cm7. I actually found the solution, i didn't know that vanillaLVL cm7 has custom bootloader with cwm inside, for this you just need:
sorry yor are right. i was my fault. i found it.
In order to get in to recovery: press power for 3 seconds. ->chose reboot -> chose bootloader -> reboot and wait for the LED to flash BLUE and then PRESS volume down button when its BLUE. it wil take to BOOT MENU. -> select RECOVERY -> then CLOCKWORK RECOVERY.