Database Users

[Q] CWM and some boot questions

Hi guys, i just want to learn something here that i dont quite understund
A) We normally for all roms intall D2Bootsrapper, then boot reboot into recovery
Once in we flash bootmenuv2.zip
and then we start flashing custom roms...
Whats the difference in D2bootstrapper and bootmenuv2? is there a newever version of this files?
B) Some roms used to recomend applying a sbf fix, a small sbf, is that still needed?
cuz i never applied it... lol
C) What kind of boot hackery are we currently using? 2ndinit 2ndboot?
Thanks!

A)
D2Bootstrapper is a hack originally created for DroidX/Droid2. It mimics the /system/bin/logwrapper binary that is normally executed by android initialization scripts on the early stages of system boot. More info here:
http://www.koushikdutta.com/2010/08/droid-x-recovery.html
Bootmenu is hack developed for Defy based on the same concepts of Droid2bootstrapper (actually it hijacks the same binary) but also included the features of 2nd-init which were ported by me from Milestone1 to Milestone2. Details here:
Bootmenu - http://forum.xda-developers.com/showthread.php?t=1026853
2nd-init - http://forum.xda-developers.com/showthread.php?t=998425
B)
You will need to flash SBF if:
- The ROM you're trying to flash requires kernel and devtree from other version than the one currently on your phone; and
- The update.zip doesn't include the images and commands to flash new kernel and devtree (my MIUI ROM includes everything, thats why I call it all-in-one).
C)
2nd-init.

r2beta0 said:
A)
D2Bootstrapper is a hack originally created for DroidX/Droid2. It mimics the /system/bin/logwrapper binary that is normally executed by android initialization scripts on the early stages of system boot. More info here:
http://www.koushikdutta.com/2010/08/droid-x-recovery.html
Bootmenu is hack developed for Defy based on the same concepts of Droid2bootstrapper (actually it hijacks the same binary) but also included the features of 2nd-init which were ported by me from Milestone1 to Milestone2. Details here:
Bootmenu - http://forum.xda-developers.com/showthread.php?t=1026853
2nd-init - http://forum.xda-developers.com/showthread.php?t=998425
B)
You will need to flash SBF if:
- The ROM you're trying to flash requires kernel and devtree from other version than the one currently on your phone; and
- The update.zip doesn't include the images and commands to flash new kernel and devtree (my MIUI ROM includes everything, thats why I call it all-in-one).
C)
2nd-init.
Click to expand...
Click to collapse
Thanks man!

that's very helpful, thanks!
Sent from my ME722 using XDA App

thanks it helped a lot!

[Q] Step by Step Tutorial for XOOM Wifi + Root + ICS + Team EOS Nightlies Rom?

Hi guys. Can someone please post a step by step guide for updating a european Xoom to 4.0.2 ICS, then rooting it and flashing the Nightlies kernel from Team EOS? I couldn't find a tutorial just yet so I would appreciate every help I can get.
Greetings
Faceball

Not to be mean… but stop being lazy. I mean everything you are asking for is basicaly right infront of you.
Sent from my DROID3 using XDA App

Any guide that shows you how to root + install CWM + Tiamat rom but replace tiamat rom with ICS!

Hey, it's pretty difficult to navigate all the threads and guides sometimes, I'm a new to XDA as well.
This thread should help you out, there's a breakdown below from me as well
If anything below is wrong, could someone correct me - my Xoom arrives today and below is what I understand the process to be from my reading ...
http://forum.xda-developers.com/showthread.php?t=1249798
1. Install Motorola USB drivers, Java SDK and Android SDK tools (for adb and fastboot)
3. Unlock the device or "bootloader") allows the flashing or replacement of recovery and boot images
4. Install a modified recovery image (ClockWorkMod recovery for Android). This is known as CWM and is an app that allows you to easily flash new ROMS and Kernals etc to the device.
5. Root the device (Allow r/w access to the device filesystem)
6. Do Nandroid (full backup) with CWM (Optional)
7. Party on and Flash new ROMS / Kernals etc!
====
You can restore your device to Stock by downloading a stock image for your Xoom model and flashing via Fastboot...

Get CWM 6.0.1.4, last build for the i9100, any ROM, include stock - The ZIP version

This update was asked many times in Q&A thread + General thread
I just did it and released the last CWM6 for our i9100
I packed it in a ZIP version applied over any recovery, include stock, just like the old temporary 5.x cwm zip
For more info and support questions, go here:
http://forum.xda-developers.com/showthread.php?t=1840223
I would not be able to maintain 2 threads for support

Updated to v6.0.1.2
Enjoy
Sent from my GT-I9100 using Tapatalk 2

17 Sep 2012: Update non touch version to 6.0.1.3
Touch version stays at 6.0.1.2: if you know about a kernel with touch 6.0.1.3 or source changes for touch cwm6, let me know please
6.0.1.3 many bug fixes and performance issues.
Click to expand...
Click to collapse

Phil3759 said:
17 Sep 2012: Update non touch version to 6.0.1.3
Touch version stays at 6.0.1.2: if you know about a kernel with touch 6.0.1.3 or source changes for touch cwm6, let me know please
Click to expand...
Click to collapse
acant update the speedmod kernel to cwm6.xx howcome???

this is temporary cwm6
For permanent, look at PhilZ kernel in my signature

Updated to 6.0.1.4

Important update for non touch version
20 Sep 2012: Update non touch version to 6.0.1.4 ** Recommanded Update from previous 6.0.1.4 attached here **
Now, CWM6 is built from source to fix possible issues related to previous dynamically linked binary
Big big thanks to Tallustus from Team SkyFire for the support
Click to expand...
Click to collapse
People using my previous non touch versions 6.0.1.3 and 6.0.1.4 are strongly advised to move to this updated 6.0.1.4
Previous version was not a static binary and could behave unexpectedly under some circumstances
Actual 6.0.1.2 touch and non touch are fine to use
I removed previous 6.0.1.3 and 6.0.1.4 files to avoid confusion

08 oct 2012:Update to new custom touch recovery included in PhilZ-cwm6 kernel
Thread: http://forum.xda-developers.com/showthread.php?t=1840223
Wipe safely on a stock kernel
WARNING: flashing update.zip files with format commands (without a patched update-binary can still brick your phone. Only fixed kernel is safe for that)
now using CWM6 based custom touch recovery 6.0.1.4 (internal build 1.15) * Siyah source code *
DUAL USB MOUNT in recovery is now supported * Special thanks to [email protected] *
semi-touch interface with right slide to select disabled for safety: use slide up/down and left for back
include bottom virtual buttons for easier navigation
revised GUI with bigger fonts and larger menus for better readability
transparency effects in recovery menus
fixed backup format selection menu in original Koush cwm6 (was echoing previous menu)
added power off and reboot to download mode options in recovery menus
battery % level displayed in recovery
fixed some menus spelling and aspect in original recovery
Click to expand...
Click to collapse

[Q] confused with the right procedure for flashing a custom rom

hello,
after reading almost everything i could read on the forums about the procedure of flashing roms, i'm left with a few questions that i couldn't find answers to, or i found more then one answer.I read all the following, and more:
1. [GUIDE] All-in-One Defy Beginner's guide by Zephyrot here: http://forum.xda-developers.com/showthread.php?t=1216982
2. [JB] CM10 Android 4.1.2 for the Defy(+) by Quarx here: http://forum.xda-developers.com/showthread.php?t=1768702
3. [GUIDE][KitKat][CM11] Updating to 4.4 by coolshahabaz here: http://forum.xda-developers.com/showthread.php?t=2568325
4. [Kitkat][Nightlies] CM11 Android 4.4 for the Defy(+) by Quarx here: http://forum.xda-developers.com/showthread.php?t=2515036
5. http://forum.xda-developers.com/showthread.php?t=2597719
6. http://forum.xda-developers.com/showthread.php?t=2644812
7. http://forum.xda-developers.com/showpost.php?p=49558697&postcount=3
8. http://forum.xda-developers.com/showpost.php?p=49558744&postcount=4
My devicee is a Defy+ with Gingerbread 2.3.6. I found here: http://sbf.droid-developers.org/phone.php?device=28 "Android 2.3.6 Blur_Version.45.0.1610.MB526.Partner.en.IL" rom which is supposed to be my stock rom.
1. My main concern is always to keep the option to go back to stock rom. As i read here, this might be a problem with Defy+, but only if i flash SBF files, which i dont plan to. Is it correct that i will be able to flash the stock rom with RDS_lite, motorola drivers and bootloader (power up with VOL up) at any time?
questions about recovery:
2. I understand that i need TWRP 2.3.6 in order to flash new roms, and since recovery is protected in Defy, i must use 2nd_init to bypass stock recovery. Is 2nd_init include the custom recovery in it? if so, which one? and what version?
3. can i install CWM or TWRP without using 2nd_init?
4. What is rom_manager (for CWM) or goo.im (for TWRP) and do i really need them?
5. what is update_recovery.zip mentioned as part of the procedure here http://forum.xda-developers.com/showthread.php?t=2515036 does it update the custom recovery or the stock recovery? is it really needed since some of the procedures described above skip this step?
choosing a custom rom:
6. I'm looking for adnroid 4.4. what is the difference between this: http://forum.xda-developers.com/showthread.php?t=2597719 (AOSP Android 4.4 for the Defy(+)) and this http://forum.xda-developers.com/showthread.php?t=2515036 (CM11 Android 4.4 for the Defy(+))
7. If i want a as-close-as-possible to google original kitkat 4.4, which one should i use?
Thanks,
Roy.

I have some of the same questions you have... will follow this topic, hoping for some info! thx!

1. You can always go back to stock ROM using RSDLite. There is no such problem with the Defy+.
2. After rooting, install the 2ndinit app to install ClockworkMod recovery (which is now outdated). Then reboot, and flash this - http://forum.xda-developers.com/showpost.php?p=48501247&postcount=1250 in the recovery. This way you will get TWRP recovery required to flash newer ROMs such as 4.4.x ROMs.
3. The 2ndinit app installs custom recovery. This info is clearly given in Zephyrot's guide -
Here is where 2nd Init comes to play, this little awesome app kicks in right after the Bootloader and allows the Defy to load a different, non-Stock Android.
With this, you can also install a Custom Recovery, which runs from the Internal Memory, and is not ran from the Recovery Partition (remember: locked, not accessible) what does this means? That even screwing up your phone, deleting all your stuff, or screwing /system partition the phone can still get into Recovery, be recognized by RSD Lite in Bootloader Mode and be flashed with a Stock or modified Rom (more on this later) and it will come back to live normally.
Click to expand...
Click to collapse
4. You don't need them.
5. None of the recovery updates touch the stock recovery. The stock recovery is built-in, and due to the locked bootloader, it cannot be removed or modified. For 4.4.x ROMs, it is sufficient to follow step 2. This guide explains the steps for installing KitKat - http://forum.xda-developers.com/showthread.php?t=2568325.
6. The AOSP ROM is severely outdated, I recommend you to try SlimKat or CM. AOSP is pure android (stock android you find in Nexus devices).
7. Using CM or Slimkat is sufficient. Also there is no 'Best ROM'. It depends on the user's opinion and requirement.

hotdog125 said:
1. You can always go back to stock ROM using RSDLite. There is no such problem with the Defy+.
2. After rooting, install the 2ndinit app to install ClockworkMod recovery (which is now outdated). Then reboot, and flash this - http://forum.xda-developers.com/showpost.php?p=48501247&postcount=1250 in the recovery. This way you will get TWRP recovery required to flash newer ROMs such as 4.4.x ROMs.
3. The 2ndinit app installs custom recovery. This info is clearly given in Zephyrot's guide -
4. You don't need them.
5. None of the recovery updates touch the stock recovery. The stock recovery is built-in, and due to the locked bootloader, it cannot be removed or modified. For 4.4.x ROMs, it is sufficient to follow step 2. This guide explains the steps for installing KitKat - http://forum.xda-developers.com/showthread.php?t=2568325.
6. The AOSP ROM is severely outdated, I recommend you to try SlimKat or CM. AOSP is pure android (stock android you find in Nexus devices).
7. Using CM or Slimkat is sufficient. Also there is no 'Best ROM'. It depends on the user's opinion and requirement.
Click to expand...
Click to collapse
Many many thks!
Im trying to up to CM 11 from 2 months.Now Im on 10.0(4.1.2).Every try to update recovery with "update-recovery.zip" or TWRP 2.6.3.0 finished with bootloop or without custom recovery and balck screen.And them flash stock .sbf and start all from the begining.And try and try....In your guide it have link to update recovery.It have something about 30+ seconds waiting after TWRP update.So I try.

[ROM] Odin + Custom ROMs + CF Root Recovery + SuperSU & CWM

Here are just some general files that some of you guys might want, had no hassle at all installing all of them onto my Samsung Galaxy S3 as I tested them all before posting. I put the ZIP file together after doing some customizations to my phone and just after having a mess around with them. I wanted to post this for you guys because I know the files really were pretty useful to me so might be useful to you all as well. Enjoy guys!
BEFORE YOU READ ON / DOWNLOAD PLEASE NOT THAT THESE FILES DO NOT BELONG TO ME AND I HAVE NOT CREATED THE FILES. I TAKE NO RIGHTS OVER THESE FILES.
The download includes the following files and their formats.
TAR Files:
CWM 6.0.4.4 I9300.tar,
CF Root SGS3 v6.2.tar.
ZIP Files:
SR4 SuperSU v2.78.zip,
SlimKat 4.4.4 Build.zip,
Odin 1.85.zip.
RAR Files:
I9300 International Stock Firmware.rar.
- DOWNLOAD HERE -

Forgot to include in the OP that you will need to install Gapps ( I did not include Gapps download for either ROMs )

Cwm is very outdated. For newer custom ROMs, twrp is required.

audit13 said:
Cwm is very outdated. For newer custom ROMs, twrp is required.
Click to expand...
Click to collapse
Thanks for letting me know