Related
I tried to root again even though I have root. I dont see the ninja but I do see the Superuser Permission icon in the app drawer and have granted a few apps su priveleges. I tried to reflash clockwork it in rom mananger and nothing. How can I get clockwork back?
I just got it back, these are the steps I took although I have no idea which order is correct or why this happened to me.
1. Rom manager - fixed permissions(first I had to force stop, clear data in manage applications as I was getting an error)
2. Rom manager - web connected
3. Rom manager - flashed clockwork recovery like 3 times in a row
4. DroidxBootstrapper - bootstrap recovery
5. DroidxBootstrapper - reboot recovery
Had to do this after I installed a different rom. Is this normal to do after every rom?
I don't think this is normal, what ROM was it?
Sent from my DROIDX using XDA App
Happened after zapx and then after rubix. First time I experienced this with rubix, so I'm thinking its zapx related or even ota 2.2 sbf related(Since I had to use this last night.) Not sure.
all you had to do was open the bootstrapper app and bootstrap recovery. these ROMs format system thus ridding of everything that was in there prior. so you have to bootstrap every time you flash a ROM.
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.
What is the best/easiest method to return to out of the box stock and how do you do it?
-I've never used sbf.
-I have a nandroid backup of stock ota 2.2.1 but reverting back to it still leaves somethings like the liberty text when first booting up.
-To my understanding madderstock is a .zip file that you just flash the same a rom. Is that correct?
-Is there something better/easier?
Thanks
Sent from my DROIDX using XDA App
Jon El Canche said:
What is the best/easiest method to return to out of the box stock and how do you do it?
-I've never used sbf.
-I have a nandroid backup of stock ota 2.2.1 but reverting back to it still leaves somethings like the liberty text when first booting up.
-To my understanding madderstock is a .zip file that you just flash the same a rom. Is that correct?
-Is there something better/easier?
Thanks
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
just use the sbf
it takes a bit longer than flashing a .zip file but its better imo
Sbf is the only way to get to pure stock imo its super easy check out my video tutorial
http://www.youtube.com/watch?v=N0jrXqqiepI&feature=youtube_gdata_player
Sent from my DROIDX using XDA App
SBF is generally the most "100%" way to get completely back to stock... However if you are more comfortable flashing a zip file, then maderstcok is the way to go... Does the same thing as the 2.3.340 system only sbf.
SysAdmin-X said:
SBF is generally the most "100%" way to get completely back to stock... However if you are more comfortable flashing a zip file, then maderstcok is the way to go... Does the same thing as the 2.3.340 system only sbf.
Click to expand...
Click to collapse
If flashing the .zip does the same thing as the sbf why is the sbf better, or the only thing that is 100%. What is the difference?
Sent from my DROIDX using XDA App
Jon El Canche said:
If flashing the .zip does the same thing as the sbf why is the sbf better, or the only thing that is 100%. What is the difference?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
It kind depends on the situation that you are in. If you have only messed up the /system portion of the phone, then flashing the zip is easier for those who aren't super android savvy. You just run the zip file, and when it finishes, it achieves the same result as the sbf, but that is only for the /system portion of the phone.
The reason I say the SBF is the best way to "100%" redo your phone is the sbf is an official moto file. If you download the latest full sbf, it completely wipes your current phone image and then loads the default image on the phone, leaving no remains of you phone prior to the sbf.
That make a little more sense?
Ya that's great, thanks. And thanks for the video Owenbeals.
Sent from my DROIDX using XDA App
Glad I could help!
Sent from my DROIDX using XDA App
maderstcok does more them just the system folder, it just doesn't do it the same way as SBF does (from the devs that made it: This is the FULL, OTA 2.3.340 - contains radio, kernel, and all other updates, even those EXCLUDED by the 2.3.340 system only sbf.).
If you can reboot into bootstrap recovery maderstcok is fine, if not the SBF may still be able to fix your phone. Just remember if you flash maderstcok or sbf you still have to reboot into recovery and wipe your phone for it to be bootable again.
for more info on the maderstcok:
http://www.droidforums.net/forum/droid-x-rooted-help/112152-maderstcok-ota-2-3-340-update-zip.html
Still up to you which you use but either should get it done the say way.
PS: Its a good idea to have maderstcok, z4root, the SBF, and RDS lite on your SD card incase your phone gets messed up and your not at your primary pc.
Instructions:
Using the Droid X Bootstrapper make a backup. (more information here)
Browse (using volume buttons) to "install zip from sdcard" and select it with the camera button.
Select "choose zip from sdcard".
Select "maderstcok340.zip"
Confirm the install.
Be patient, wait for the install to finish.
Reboot the Droid X. DO NOTHING ELSE IN CLOCKWORKMOD!!!!!!!
Activate the phone with VZW (more instructions below).
If you attempt to create a backup or flash a rom post maderstcok installation you're going to have a paperweight. This seems to be because maderstcok removes root and the clockworkmod recovery area, so it doesn't like you playing around in there. Re-root and reinstall the bootstrapper, then create a backup or flash a new rom, DON'T DO IT BEFORE REBOOTING THE DX AFTER ISNTALL.
Formatting Data and Cache is optional; however, if you want a really clean install do so. If you factory reset you'll be forced to activate the phone automatically while if you don't you'll have to follow the quick and dirty activation instructions below - the choice is ultimately yours.
EDIT: coming from ANY non-blur based ROM and doing Maderstcok is guaranteed to bootloop due to mismatch in framework without a data/cache wipe
__________________________________ These are the instructions for the maderstcok. In the second to last paragraph it says that if you want a really clean install you should format data and cache. When is this step performed? The last step in the list of instructions after flashing the .zip is to reboot NOT DOING ANYTHING ELSE IN CLOCKWORKMOD. So before I reboot should i wipe data and cache or do I need to re-root, run bootstrap recovery, and then wipe data and cache?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Maderstock will erase bootstrap/recovery right? I need to send my phone in to Motorola for repair. Thanks
Sent from my DROIDX using Tapatalk
These are the instructions for the maderstcok. In the second to last paragraph it says that if you want a really clean install you should format data and cache. When is this step performed? The last step in the list of instructions after flashing the .zip is to reboot NOT DOING ANYTHING ELSE IN CLOCKWORKMOD. So before I reboot should i wipe data and cache or do I need to re-root, run bootstrap recovery, and then wipe data and cache?
http://www.droidforums.net/forum/droid-x-rooted-help/112152-maderstcok-ota-2-3-340-update-zip.html
Sent from my DROIDX using XDA App
Anyone know when to wipe cache and data? Explained above
Sent from my DROIDX using XDA App
ok ive tried everything in the sticky thread regarding reverting back to froyo using the 2.3.34 SBF file. i flash the file, root, and use the bootstrap to load the Blur_Version.2.3.340 Part 1 and Part 2 files from the sticky thread, but i get the following error.
Verifying Current System....
assert failed: apply_patch_check (/system/app/AccountAndSyncSettings.apk)
then gives a bunch of numbers....then shows the sd file i was trying to apply with "Status 7) Installation Aborted.
i figured the SBF was bad so i redownloaded it from somewhere else, same errors. i even tried to load up the 3 parts to GB .588 hoping to then goto .596, same error.
finally i installed maderstcok340 update file using recovery. everything worked and i was able to install the GB updates. but once i rebooted the phone after it said everthing was successful, it loads into the bootloader screen and wont let me out of it.
im so frustrated. does ANYONE have any idea why this isnt working???
SBF to 2.3.340 (Froyo), root, install Droid 2 Bootstrapper, then install the two part 596 rooted build.
I recommend using Linux to SBF. There's a bootable disc floating around the forums somewhere that you can use. Just Google for it.
Root using Z4root, then install the Droid 2 Bootstrapper application. Be sure that it is the DROID 2 version. The Droid X version doesn't work with Gingerbread.
Lastly, you need to boot into ClockworkMod Recovery. To do this open the Droid 2 Bootstrapper application and select the top button, when it gives you the success message press the reboot button to reboot into ClockworkMod Recovery.
Lastly lastly, wipe data, then install both part one and part two of the Gingerbread zip files. NOTE: You must install both the zip files one right after the other, if you leave recovery before flashing part two you will have to SBF.
Completely lastly, reboot the phone, and if you bootloop boot into stock recovery and wipe data/cache.
Hope this helps ^_^
Sent from my DROIDX using XDA App
ive done all of this. my problem is after i SBF, root and load the bootstrap, the install of the zip gives me the error seen above in bold. i cant get past the installation. is something wrong with the SBF??
i finally got it to work. the SBF i downloaded was bad. i found a new file and used it, now its working just fine.
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...........