For me, when I use Clockworkmod Recovery, whether it's preinstalled into a rom, or from the bootstrap, it always boots up while my ROM is fine. Whenever I'm stuck in a bootloop or stuck on the splash screen though, it NEVER works. BP-Tools does nothing for me. My only option at this point is to reinstall the OTA and root it all over again to return to my previous rom. How can I fix Clockworkmod?
This is an unfortunate side effect of the manner in which the D3 alternate recovery method (CWM Recovery) is implemented. On phones with unlocked boot loaders, the stock recovery is replaced by CWM recovery, but on this and other locked phones it is hijacking but not replacing the stock recovery. In more simple terms, if you crash your phones software the hijacked recovery (CWM) is crashed along with it. Before making any changes to a functional setup, you should always make a backup so that even if you crash the phone, you can SBF, reroot, reinstall CWM and then restore to exactly where you were before the change that crashed you.
There is, of course, an easier alternative to this. Thanks to Hashcode, there is another CWM based recovery for the D3 called Safestrap, you may have heard of it already. It essentially acts more like a virtual machine in that it does not overwrite the existing phone software, but allows you to ROM a secondary system where if at any time you crash that system, your original software is still intact. I HIGHLY recommend that you try it out, especially if you have had to frequently completely restore your phone.
Related
Okay Im trying to go into this amazing world of roms and kernals and boots and flashboots I started this trip just because I hear you can OVER CLOCK CPU
I just started when I got my droid 3 on the 14th, so far Ive gotten the hang of
ROOT with pete one click
root manager to check things out or rename *.apk to *.bak
titanium backup, to make back ups? and freeze (same as above?)
script manager to run a remove bloat (same as above??)
do these 3 really do things all that different?
now im getting deeping into the rabbits hole.
bootstrap, I made my first NANDroid which is a NAND or back up I think, for the droid... how clever
Rom manager to manage roms i guess, i think this was the one that wouldnt be ready until the boot loader was unlocked right?
If the boot loader is locked then what is
fast/flashboot for??? same as boot strap or different?
CYANOGEN or CM7??? no idea what this is... a ROM???
last but not least do any of these have to do with changing the KERNAL so I can finally overclock on setcpu???
nandroid which is a complete backup of the internal flash memory.
rom manager is use to manage roms, duh, this will be useful once we get the ability to flash roms through CWM
ROMs may or may not come with a kernel, we can't flash kernels because they require an unlocked bootloader because they are loaded by the bootloader as part of the initial booting
fastboot is part of the phones bootloader (i assume or is on a similar level), it allows basic interaction with the phones hardware and software
cyanogen or CM7 is a custom rom, often with a kernel included but doesn't need a custom one per-say
im new here too and this is what i have gathered so far correct me if im wrong.
kayelemenohpee said:
CYANOGEN or CM7??? no idea what this is... a ROM???
Click to expand...
Click to collapse
http://www.cyanogenmod.com/
You started off with a bad first device for android development since it's locked down. However, I'm amazed at the progress being made already. We will not be able to flash custom kernals, because we are locked out of the bootloader. We will be able to over clock in the long run though, just give it time.
Rom Manager is used to browse, select and flash custom roms using an easy to use app. The problem is that we can't boot to recovery directly, we have to go though the reboot and BP Tools method so all you can really use Rom Manager for is to download roms to your phone which you can then manually flash. It will be empty right now because we have no roms.
Titanium Backup's primary purpose is to back up apps with DATA. So all your game saves, settings, things like that can be easily restored after you flash to a new ROM.
Fastboot files are used to recover different partitions on your phone should you brick it.
The term 'bootstrap' is bothering me a bit. Can somebody clarify it?
As I understood it bootstrap was a method of loading a custom recovery, but not the same method as the 2nd init that we are using here. I was under the impression that bootstraps were a bit lower, requiring an unlocked bootloader.
In any case the program that allows you to create backups and flash custom roms is called a 'Recovery' or 'Custom Recovery'. The one you have on the phone right now is ClockWorkMod.
calash said:
The term 'bootstrap' is bothering me a bit. Can somebody clarify it?
As I understood it bootstrap was a method of loading a custom recovery, but not the same method as the 2nd init that we are using here. I was under the impression that bootstraps were a bit lower, requiring an unlocked bootloader.
Click to expand...
Click to collapse
This was written for DX/D2 but I imagine it's the same basic process.
The Internets said:
Bootstrapper works by doing the following.
When you hit the "Bootstrap Recovery" button the app renames logwrapper to logwrapper.bin, adds a file called Hijack and symlinks a new logwrapper file to Hijack. (For you windows people, a symlink is like a shortcut...)
At boot, init.rc calls for logwrapper, which now calls Hijack (by way of symbolic link) which is how we can load into Clockwork recovery.
When Hijack runs, it checks for a file called /data/.recovery_mode if it finds that file, it unmounts /system and boots into Clockwork recovery, if it doesn't find that file, it creates it and calls logwrapper.bin (the factory logwrapper file) and boots normally.
When the OS is completely booted, Droid 2 Bootstrapper (the app) is loaded and deletes the file /data/.recovery_mode. Since the boot was successful, it assumes you don't want to boot into recovery next time.
If on the other hand, the OS doesn't boot normally, and Droid 2 Boostrapper never loads and therefore never removes /data/.recovery_mode, it should let you into Clockwork on your next boot.
Now, when you open the Bootstrap app and hit the "reboot recovery" button, it manually adds the /data/.recovery_mode file and then begins the reboot process. Upon reboot, Hijack finds the file /data/.recovery_mode, and boots into Clockwork.
Click to expand...
Click to collapse
Basically the title.
I removed the Tweaked Bootstrap.apk and just downloaded and installed Safe Strap. Rebooted and performed my first backup in Safe Strap. Tried to boot into primary and got black screen.
My current ROM is the latest (11-16) version of CM7.
I don't really need Safe Strap, I kinda just want to be able to boot again. Any help is greatly appreciated.
EDIT: Formatted /system and reflashed CM7 and GApps in SAFE MODE. Can boot now, going to try booting in NON-SAFE MODE.
EDIT2: Still can't boot into non-safe mode. My whole reason for switching was to test out ICS, so I guess I can just flash it and if I need to go back, I'll just reflash CM7.
Regardless, if anyone can tell em what I'm doing wrong, I'd be appreciative.
Did you wipe everything including dalvik? and its best if you start from a stock system. No custom ROMs. then install CWM and install whatever rom you want. uninstall CWM and install safestrap. now boot into safestrap and wipe cache and all taht. Now install ICS/CM9. I found tahts the best way to do it recieve none of the errors many people are having.
Well, since safestrap can't flash nonsafe (yet) its obvious you still can't boot nonsafe if you couldn't before. What you need to do is reflash cm7 using the old bootstrap, install safestrap, make backup, then switch to safe system and flash ics.
First off, let me make this clear very clear(prerequisite) I do not want to hear the word "safestrap", or any variation. I apologize for sounding arrogant , but I am not interesting in wasting my disk space(no offense against the quality work of Hashcode) or dual booting a ROM. I noticed some interesting issues with CWM recovery both the default that comes with Bionic Bootstrapper(4.x.x.x), and ROM Manager(5.x.x.x) in regards to any ICS leaks. So here is the situation, after installing the .232 leak using the "stock recovery option" it went smoothly without any issues, as well as rooting with motofail for ICS. The problems start when I first attempt to install any ROM(AOKP, CM, liquidsmooth etc etc) using 4.x.x.x CWM it appears to install correctly(even booting the ROM up and everything) but when I reboot the phone will continue to boot directly into CWM, and using the reboot option only to boot loop.(I have done the standard Wipe System/Factory reset, Wipe Cache, Wipe Dalvik Cache prior to installing any ROM). Finally, when I attempt to install an updated CWM 5.x.x.x via ROM Manager, it appears to install, but forcing the device to reboot in to recovery does not work, even the two button solute(PWR+VOL UP) as used in the second stage to force CWM to boot into the menu(worked in 4.x.x.x) it is as if it is not corretly installed.. Both CWM installs are clean, and no previous 1st/2nd stage boot loaders are installed, I would like to rule out me being a dumbf*** and it being a case of error on my part. Like I said before please do not mention "SAFESTRAP" as an option, unless it can flash over current baseline install's, having the safe option(noob proof) is not an option. If anyone can assist me with the installation or even a solution to getting CWM recovery to work after installing the ICS leaks it would be greatly appreciated. Thanks again!!! Also I have tested CWM 5.x.x.x install from .905 based roms and it works flawlessly.
Sorry for this being lengthy, I wanted to make sure I gave enough info.
Neither of the two most popular recovery tools are working for me. They both state the backups are successful but the restores have flaws. Is anyone experiencing the problems I am? If so, does anyone know what to do about them?
CWM Recovery Touch (and non-touch): Data restores leave certain things not working. I'm not sure what processes are stopping because it flashes and disappears to fast. I know that it causes the ROM Manager for CWM, Titanium Backup Pro, Google Play, and likely more to crash (disappear) immediately upon opening. Chrome browser *might* bright up the keyboard on the first click but it won't work then it will disappear and not come back (but the keyboard does work in other areas, I use Swype Keyboard). I've tried clearing cache and/or data on all 3, uninstalling them then re-installing via APK and various other things. This occurs regardless of whether a factory reset (data/cache) wipe is performed before the restore. However, if I restore with CWM Recovery *then* do a factory reset, Google Play will work and nothing crashes, nor are their long delays.
TWRP does not boot after a restore. It will pass the initial screen showing the phone model, the phone carrier splash screen, then sit on Samsung with the LED solid bright blue and hang.
My goal is to simply trust my backups. The CWM Recovery problem is workable in a terrible situation since my Titanium backups will get my phone *almost* to where it was (barring widgets, which are pain to re-setup, and a few other things).
Titanium Backup Pro question: Is it normal when you remove a system app with Titanium Backup Pro, then do a restore in CWM for that app to still be gone? Since I use the Swype keyboard I removed the other once, did a restore with CWM, had the problem so I did a factory reset and my stock keyboard was missing still (I think it's a Samsung keyboard)
App Details:
CWM Recovery Touch 6.0.4.7 (for Samsung Galaxy S3 LTE (GT-I9305))
TWRP 2.6.3.0 (for Samsung Galaxy S3 LTE (International i9305))
Phone Details:
Carrier: T-Mobile (Germany)
Model number: GT-I9305
Android Version: 4.3 (stock from Kies, so I do have Knox and it's disabled via SuperSU 1.91 from chainfire)
Baseband version: I9305XXUEMK1
Kernel version: 3.0.31-2051278
Build number: JSS15J.I9305XXUEML5
Titanium Backup Pro question: Is it normal when you remove a system app with Titanium Backup Pro, then do a restore in CWM for that app to still be gone?
No a Nandroid backup wipes the phone .
make a Nandroid then in recovery format system sdcard data cache .
You now have an empty phone and restoring the Nandroid should return exact same state .
All this reads as you are doing something wrong .
JJEgan said:
All this reads as you are doing something wrong .
Click to expand...
Click to collapse
I hope it is as simple as that. I'm booting up in recovery mode (Volume Up + Home + Power) choosing the backup or restore option, then backing up to the External SD card. Then on the restore I'm doing the same except selecting restore from the SD card (I've re-created the CWM problem 5 times, once was with advanced restore of just data the rest were basic restores doing everything). I'm not really sure what I could be doing wrong.
I have the 4.3 stock ROM before I did any custom stuff to the phone (which installed KNOX). I used chainfire's tar.md5 auto root image with Odin 3.09 in download mode when I root the phone, and I've installed CWM Recovery with ROM Manager and with an Odin tar flash in download mode. The install of TWRP was from an Odin 3.09 tar flash in download mode too.
With regard to the TWRP and CWM Recovery, I'm not really sure how easy it is for me to have messed up that part. Do you have this same model phone? Is it possible KNOX is involved in my issues? Maybe I should downgrade one of the recovery tools?
Downgrade your recovery and try again.
jonesjw362 said:
Downgrade your recovery and try again.
Click to expand...
Click to collapse
That's what I was thinking might be the best solution. Since the flaw in the restores with CWM Recovery are workable for me, I figured I may just wait until I have a need to restore to do that though. Once I do, I'll probably do a bunch of tests until I find something that works solid.
I've already restored my backups and widgets etc. a couple of times and don't really want to do it over again only to test. If there's a way to restore all of that without my having to set it up myself then I'll do it. Right now my Titanium restores don't include wallpaper (except lock screen), most of my widgets (maybe all, can't remember), and I think there was one other thing.
Advanced restore in recovery restore data only .
JJEgan said:
Advanced restore in recovery restore data only .
Click to expand...
Click to collapse
I tried that once, that's why I believe the CWM Recovery issue to be specifically with data. I'm going to do it again right now though and if things are messed up again I'm going to try jonesjw362's suggestion.
Downgrading didn't help (6.0.3.6 had a constant barrage of 4-5 apps re-crashing over and over again during the process).
I tried the following with CWM Recovery Touch 6.0.3.6, 6.0.4.5 and 6.0.4.7:
Factory reset wipe, open and test Google Play (more things break but that's the one I chose to test). Reboot into recovery mode and backup to the SD Card (not the external). Immediately advance restored data only (no wipe). Booted up, Google Play crashed, rebooted back into recovery and factory reset (data/cache) and advance restored data again with the same result.
I didn't try a downgraded version of TWRP (probably won't for now). I'm back to 6.0.4.7 and restoring my backups to get my phone back fully. Hopefully CWM Recovery comes out with a new version sometime in the near future that works for me or someone has some insight into what I can do to fix it with the existing (I'm out of ideas).
Issue Samsung stock 4.3 ROM
I ended up switching to CM 10.1.3 (was going to hold off until 11 was stable) but the Samsung stock 4.3 ROM was destroying my battery. After switching, I tested a NANDROID backup and restore with CWM Recovery Touch 6.0.4.7 (same version I was having problems with). The restore worked as it should, no problems.
End Result: As far as I can tell, the cause of the CWM Recovery data partition problem is due to the Samsung 4.3 ROM.
Edit: I was going to mark the post Resolved but I can't seem to find the drop down to do so (at least not in the same place I thought it was).
Edit: The flashable zip seemed to be a good workaround and got everything done in one go. Fingers crossed from here on in.
Hi guys, this is my first post here, so please go easy on me.
So recently my phone screen cracked and I had to send it off for recovery.
The company wiped and upgraded my firmware, but I did my data backup as a nandroid backup, so I have to get a recovery installed to restore it.
I have managed to unlock the bootloader and flash this version of the firmware : - D5803_23.4.A.1.264
I am simply trying to root the phone so I can get SuperSU onto it and the method I used last time uses CWM. However, when I try to install CWM I can access CWM, but otherwise, it goes into a boot loop and I have to reflash that firmware to restore it, which deletes the CWM. The CWM version I can flash does not seem to be able to restore nandroid, so it's fairly useless.
i have tried downgrading but then the phone crashes on startup. I noticed when I restored to the current firmware above, the phone had kept all my settings, so I don't know if there's extra I need to wipe, or if I'm not flashing correctly.
Now I have used PRF tool to create a flashable zip, that I thought might be able to do the job for me if I can get something to install it. It has the working firmware, SuperSU and dualrecovery in it.
I have done this all before without issues, but the new firmware version is making things more difficult.
So questions are;
1. Am I flashing incorrectly when downgrading? Or is there some other factor at play preventing me from doing so?
2. Is there a way I keep the CWM and flash the working firmware? Like it would go into boot-loop but then I could get the normal systems operating again and have the phone rooted, continuing the work. I figured there might be an option in flashtool, but I didn't want to press anything without confirmation from someone.
3. Is there an easier way to froot this? Last time I was able to use giefroot, but now it says my kernel isn't supported.
Any help would be greatly appreciated. I'm not new to modding my phones, but I'm not advanced either. Let me know if there are other details I can give that might help.
Thanks.