The format of recovery that we download from official website is .img. How can we make it a cm flashable zip?
Sent from my HTC One X+ using xda premium
Siddharth121 said:
The format of recovery that we download from official website is .img. How can we make it a cm flashable zip?
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
If you are talking about making a stock ROM (.img) into a flashable zip file then you will need android kitchen.
1. Place both boot.img and system.img into Original_Update folder
2. In kitchen click option 1
3. Pick the option that says system.img and boot.img
4. Follow the onscreen instructions
5. Build using option 99.
6. Flash in CWM or TWRP!
Siddharth121 said:
The format of recovery that we download from official website is .img. How can we make it a cm flashable zip?
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
To make the recovery.img flashable in CWMR recovery you would have to create a flashable zip that writes the raw .img file to the recovery partition. The commands to flash it to the recovery partition would be similar to this:
Code:
ui_print("ClockworkMod Recovery v6.0.3.1");
ui_print("for Your Device Name Here");
show_progress(0.500000, 0);
ui_print("Writing recovery image");
package_extract_file("recovery.img", "/tmp/recovery.img");
run_program("/sbin/busybox", "dd", "if=/tmp/recovery.img", "of=path/to/recovery/partition");
delete("/tmp/recovery.img");
ui_print("Complete!");
Note: The ui_print and show_progress commands are just to make it easier for the user to understand what is going on and for a clean look.
The structure for the folder of the flashable zip would be similar to:
META-INF->com->google->android->update-binary and update-script
recovery.img (In the same folder as your main zip do not put this in the META-INF folder)
I would also recommend checking out this guide to edify scripting and creating flashable zip's. Let me know if you still have questions .
[PATCHER][APP] Dual boot any ROM on all Galaxy S4 variants!
So from there, download Dual Boot Switcher app and DualBootUtility zip.
And loki-doki from here.
The unzip whatever ROM you're wanting to dual boot. Go to META-INF/com/google/android/updater-script and edit the updater-script manually. The instructions for that are in the post up top I linked to.
Patch the boot.img with the automatic patcher tool, patch-ramdisk.sh. It will create boot_dualboot.img. I just renamed that to boot.img.
Then I put the new boot.img back into the ROM folder.
Create a file named dualboot.sh, and put this in there dualboot.sh.
Put this file in the base of the ROM folder, the same place where the boot.img is.
Zip this all up. the gapps zip I just patched automatically with the patcher app, also in the downloads from the first link.
Instructions for dual booting
Before doing anything, download the Dual Boot Switcher app and the DualBootUtilities.zip from the download section below.
Follow these steps.
chenxiaolong said:
Before doing anything, download the Dual Boot Switcher app and the DualBootUtilities.zip from the download section below.
Note: Only the secondary ROM and other zips that should be installed for the secondary ROM need to be patched. Nothing needs to be done for the primary ROM.
Boot into your primary ROM and install the Dual Boot Switcher app
Open the app and set the current kernel as the primary kernel (screenshot)
If the primary ROM is TouchWiz, you will need to remove some bloatware. Otherwise, two ROMs won't be able to fit on the /system partition. You can also convert some system apps to user apps with this tool: https://play.google.com/store/apps/details?id=de.j4velin.systemappmover&hl=en
Patch the ROM (see the "How to use the patcher" section)
Reboot into recovery
Flash the patched zip files.
Reboot
Install the Dual Boot Switcher app again in the secondary ROM. If you have a locked bootloader, set the kernel for the secondary ROM (just in case).
Enjoy!
Click to expand...
Click to collapse
Then just flash your ROM.zip, gapps.zip, and loki-doki.zip. Don't wipe anything. Just reboot. It should boot into your second ROM. Install the ROM switcher app again, set the current kernel as the secondary kernel.
If you want to boot back into your primary ROM, just pick it in the ROM switcher app.
Note: When manually patching, you can go off the examples, and it makes it easier, BUT be careful because not all updater-scripts are the same. I copied off of aokp.dualboot.patch and it kept ruining my ROM. I could boot into AOKP all day long, but if I tried to boot into HyperDrive, it'd just stick at the Samsung splash screen. I looked over my patched updater-script and there was another line with:
format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system");
that I missed. So, just be sure to make a nandroid backup.
I'm including a copy of the AOKP updater-script that I edited. It's for the official 10-18 nightly. I tried to make a patch info file to send to the guy who came up this awesome app/mod, but for some reason I'm just inept in this area. I suck at how-to's as well, but I don't see anyone else trying to explain this for our phone
Since you said you had to do some steps, care to share them for users in general? Might save your inbox from getting slammed.
Well I had to remove/add a few lines to the updater script, which I kept messing up because I seem to get deslycix when reading code at 2 am.
Then the boot.img needs to be patched, but there's a tool for that in the OP of the thread I linked. It will create a file called boot_dualboot.img. I renamed that to just boot.img, and removed the original from the zip.
Then I put dualboot.sh at the base of the ROM zip.
Patched gapps automatically with the patcher tool.
Flashed patched ROM, patched gapps, and loki-doki. Just Google loki-doki, it's the first result.
Patching the boot.img removes loki. Flashing loki-doki will loki the kernel again.
Edit: I'll do up a better How to later. I'm at school right now though.
Sent from your mom's smartphone
Updated OP. If you have any problems, just post and I'll help where I can. I'm no expert, I'm just good at following instructions.
Hey, thanks for doing this thread. How do you remove dual booting when you want your phone back to normal again? haha
Restore a nandroid. Or do a clean flash from recovery and you'll be on one ROM.
Sent from your mom's smartphone
If anyone can do a precise and accurate video tutorial for this, that would be awesome! I'm more of a visual learner.
That is way beyond my level of knowledge lol.
Sent from your mom's smartphone
thats pretty ill. i personally do not see a reason to do it, but i like that its possible, LOL
[Caveat emptor: adopt/follow this guide at your own risk].
[Important Note: this process is applicable for CM11 builds that still maintains two separate partitions for /data and /media – as in CM10.x and stock ROMs (see http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more info). If/when these two partitions get merged in some future CM11 builds (as being contemplated by our NT CM developers – see http://forum.xda-developers.com/showthread.php?t=2560827&page=28) this "CM10 to CM11" update process will not be valid for those future builds with merged /data+media partition].
Below is the process that can be used to update your NT EMMC from CM10.x to CM11.
Download the following files to a location in your user content-media storage space on the NT:
the flashable_CWM_6.0.4.5_chrmhoffmann.zip file from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet which contains the CWM recovery v0.2 provided by Chris Hoffmann (in the first post of the XDA Official CM11 thread http://forum.xda-developers.com/showthread.php?t=2560827).
the zip file of CM11 ROM build of your choice from http://download.cyanogenmod.org/?device=acclaim (see http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items for considerations in choosing nightlies vs. snapshot/stable builds)
the zip file of the Gapps package corresponding to CM11 – e.g., from http://wiki.cyanogenmod.org/w/Google_Apps
Boot into your current emmc recovery
Select install zip and install flashable CWM recovery zip file (obtained in step 1(a)).
Select reboot to boot into the new emmc recovery (flashed in the preceding step).
Select Wipe data & factory reset.
Select install zip and install CM11 zip file.
Select install zip and install Gapps zip file.
Reboot into the new CM11.
Once the NT boots up, set up the wifi connectivity and your google account info. If you had previously enabled Google backup service on your CM10.x your Google Playstore apps will be auto-downloaded (but their settings will not be auto-restored).
If the NT on occasion boots or reboots into a black screen (in lieu of CM boot animation), then you have encountered one of the "random boot crashes" – more info and potential remedies, see http://forum.xda-developers.com/showpost.php?p=48941796&postcount=94 and http://forum.xda-developers.com/showthread.php?p=48301259#post48301259.
A few additional points worth noting:
Flashing CM11 requires CWM version 6.0.4.5 or later, or TWRP version 2.6.3.0 or later. To create a flashable recovery zip file for TWRP, use an archive file manager such as 7-zip to delete and replace the recovery.img inside the flashable recovery zip file (obtained in step 1(a) above) with your choice of TWRP internal recovery image file from http://techerrata.com/browse/twrp2/acclaim (e.g., openrecovery-twrp-2.6.3.1-acclaim.img). Remember to rename the downloaded TWRP .img file to recovery.img before inserting it into the recovery zip file, and also rename the resulting new recovery zip file to some other name like flashable_TWRP_2.x.y.z.zip to avoid future mix-up.
Installing CM11 ROM and Gapps will override your NT's CM10.x boot, recovery, ROM, and Apps, so make sure that you backup all this stuff using recovery backup function, for easy in reverting to CM10.x if desired. See my post at http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more "Info and Tips for Mitigating Risks in Rooting and Flashing Custom-ROM".
I would advise against using any other functions of the recovery without first carefully researching to understand what they really do.
My thanks to all the developers who collective work created the wonderful CM11 ROM for the NT as well as the tools and info I made use of to install it.
A day before i moved from CM 10 to CM 11 , with the help of mikeataol
Anyway Thanks a lot for this guide.
Few questions
* Any good custom kernel ? I tried Bexus but its giving me "android.phone" stopped responding error and wont allow me to do anything , it just keeps on coming even after pressing "OK"
* What happend to multi touch feature ? any ROM , way to enable it ?
* Is it only me or others too feel that the screen lags a lot wrt to touch input ? Its more evident during scrolling or reaading pdf. Also anyway to resolve it ? I desperately need a fix for this.
* I used gapps from here : http://wiki.cyanogenmod.org/w/Google_Apps
CM 11 20140105 , is it fine or i should use PA Gapps only ?
naveen_reloaded said:
...
* What happend to multi touch feature ? any ROM , way to enable it ?
Click to expand...
Click to collapse
Look for the Touch FW Flasher app on the App Drawer screens.
* Is it only me or others too feel that the screen lags a lot wrt to touch input ? Its more evident during scrolling or reaading pdf. Also anyway to resolve it ? I desperately need a fix for this.
Click to expand...
Click to collapse
Did you do wipe /data and /cache in the CM11 installation process?
* I used gapps from here : http://wiki.cyanogenmod.org/w/Google_Apps
CM 11 20140105 , is it fine or i should use PA Gapps only ?
Click to expand...
Click to collapse
The Gapps KK package you installed is fine, the PA package just has a few more apps (such as Maps and YouTube, etc. -- all of which you can get from the Google Playstore) and is more frequently updated (-> less likelihood/need for updates for the apps in the package immediately after first installation).
digixmax said:
Look for the Touch FW Flasher app on the App Drawer screens.
Did you do wipe /data and /cache in the CM11 installation process?
The Gapps KK package you installed is fine, the PA package just has a few more apps (such as Maps and YouTube, etc. -- all of which you can get from the Google Playstore) and is more frequently updated (-> less likelihood/need for updates for the apps in the package immediately after first installation).
Click to expand...
Click to collapse
Thanks , I heard that multitouch has bug which makes tablet slow at <50% battery , is it so ? also does that app work on cm 11?
Yes , i did wipe everything and installed CM 11 , still the screen is stuttering. very annoying. Is there a way to increase the fps ? or see if GPU drivers are working properly ?
The default Gapps are giving error when flashed with Bexus kernel
---------- Post added at 08:12 AM ---------- Previous post was at 07:32 AM ----------
https://play.google.com/store/apps/details?id=com.aatt.fpsm&hl=en
Used this app and saw that fps varies and it varies like from 7 - 50 during reading pdf.
On slow scrolling of pdf , it only shows 11 or so fps , which is why i think shows the stuttering effect
Used the same app on my GS3 to see the difference and it holds its FPS at 60+ and not dropping below 50.
I think if i can make this tablet to render everything at 30+ fps i might not feel this stuttering effect.
https://dl.dropboxusercontent.com/u/15488514/nooktablet.mp4
here is the video i tried to take regarding the screen lag.
its all real time , there is no , afaik any camera lag ( taken with sg3) , its pretty much how it looks . Also i have shown the FPS . You can see when i scroll slowly , the FPS drops to 20 or so making it jerky. if i do it fast , it reaches 50+ but not stable and not very responsive to my touch feedback either.
digixmax said:
[Caveat emptor: adopt/follow this guide at your own risk].
[Important Note: this process is applicable for CM11 builds that still maintains two separate partitions for /data and /media – as in CM10.x and stock ROMs (see http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more info). If/when these two partitions get merged in some future CM11 builds (as being contemplated by our NT CM developers – see http://forum.xda-developers.com/showthread.php?t=2560827&page=28) this "CM10 to CM11" update process will not be valid for those future builds with merged /data+media partition].
Below is the process that can be used to update your NT emmc from CM10.x to CM11.
Download the following files to a location in your user content-media storage space on the NT:
the flashable_CWM_6.0.4.5_chrmhoffmann.zip file from https://www.mediafire.com/#xjwc1a482a6ll which contains the CWM recovery v0.2 provided by Chris Hoffmann (in the first post of the XDA Official CM11 thread http://forum.xda-developers.com/showthread.php?t=2560827).
the zip file of CM11 ROM build of your choice from http://download.cyanogenmod.org/?device=acclaim (see http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items for considerations in choosing nightlies vs. snapshot/stable builds)
the zip file of the Gapps package corresponding to CM11 – e.g., pa_gapps-modular-mini-4.4.2-20140301-signed.zip from http://goo.im/devs/paranoidandroid/roms/gapps-mini
Boot into your current emmc recovery
Select install zip and install flashable CWM recovery zip file.
Reboot into the new emmc recovery (flashed in the preceding step).
Select Wipe data & factory reset.
Select install zip and install CM11 zip file.
Select install zip and install Gapps zip file.
Reboot into the new CM11.
Once the NT boots up, set up the wifi connectivity and your google account info. If you had previously used Google backup service your apps will be auto-downloaded (but their settings will not be auto-restored).
If the NT on occasion boots or reboots into a black screen (in lieu of CM boot animation), then you have encountered one of the "random boot crashes" – more info and potential remedies, see http://forum.xda-developers.com/showpost.php?p=48941796&postcount=94 and http://forum.xda-developers.com/showthread.php?p=48301259#post48301259.
A few additional points worth noting:
Flashing CM11 requires CWM version 6.0.4.5 or later, or TWRP version 2.6.3.0 or later. To create a flashable recovery zip file for TWRP, use an archive file manager such as 7-zip to delete and replace the recovery.img inside the flashable recovery zip file (obtained in step 1(a) above) with your choice of TWRP internal recovery image file from http://techerrata.com/browse/twrp2/acclaim (e.g., openrecovery-twrp-2.6.3.1-acclaim.img). Remember to rename the downloaded TWRP .img file to recovery.img before inserting it into the recovery zip file, and also rename the resulting new recovery zip file to some other name like flashable_TWRP_2.x.y.z.zip to avoid future mix-up.
Installing CM11 ROM and Gapps will override your NT's CM10.x boot, recovery, ROM, and Apps, so make sure that you backup all this stuff using recovery backup function, for easy in reverting to CM10.x if desired. See my post at http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more "Info and Tips for Mitigating Risks in Rooting and Flashing Custom-ROM".
I would advise against using any other functions of the recovery without first carefully researching to understand what they really do.
My thanks to all the developers who collective work created the wonderful CM11 ROM for the NT as well as the tools and info I made use of to install it.
Click to expand...
Click to collapse
The mediafire link does work anymore. Could you reupload the zip file?
Hannibal2050 said:
The mediafire link does work anymore.
Click to expand...
Click to collapse
Link fixed.
digixmax said:
Link fixed.
Click to expand...
Click to collapse
WHen I pressed to Install zip from sd card, the screen only show the symbol of ROM Manager (a hat), and stucked.
What should I do now?
Hannibal2050 said:
WHen I pressed to Install zip from sd card, the screen only show the symbol of ROM Manager (a hat), and stucked.
What should I do now?
Click to expand...
Click to collapse
What version of CWM do you currently have on emmc?
digixmax said:
What version of CWM do you currently have on emmc?
Click to expand...
Click to collapse
Sorry, I handled this issue.
But now if I selected the ZIP file I downloaded from the first post, CWM reported that this file is BAD, and I cannot install.
I am using CWM 5.5.0.4.
I downloaded this file several times, but the issue does not disaapear
Hannibal2050 said:
Sorry, I handled this issue.
But now if I selected the ZIP file I downloaded from the first post, CWM reported that this file is BAD, and I cannot install.
I am using CWM 5.5.0.4.
I downloaded this file several times, but the issue does not disaapear
Click to expand...
Click to collapse
You need a newer version of CWM 6.0.[1-3].x to install CM10.x.
If you have a SD card handy, try the method outlined at http://forum.xda-developers.com/showpost.php?p=51377882&postcount=163.
digixmax said:
You need a newer version of CWM 6.0.[1-3].x to install CM10.x.
If you have a SD card handy, try the method outlined at http://forum.xda-developers.com/showpost.php?p=51377882&postcount=163.
Click to expand...
Click to collapse
Hi,
I did exactly like that. I tried to update CWM to 6.0.45 and the current CWM reported that the zip file of CWM 6.0.45 is BAD
Hannibal2050 said:
Hi,
I did exactly like that. I tried to update CWM to 6.0.45 and the current CWM reported that the zip file of CWM 6.0.45 is BAD
Click to expand...
Click to collapse
For CM10.x you need 6.0.[1-3].x (e.g., 6.0.2.8).
6.0.4.5 and later versions are for CM11 only.
If you follow the SD-based CWM recovery method in the referenced post the CWM recovery you'd be using (to flash the new CWM, ROM, Gapps) is provided by the file recovery.img (downloaded and copied to the SD card) rather than your current 5.5.0.4 on emmc. Make sure that you boot the NT off the SD card as prescribed in step #3 (otherwise you will end up booting emmc cyanoboot and CWM).
FYI, i'm pretty sure TWRP 2.7 (official from GooManager/TWRP site) doesn't work. if you click on the console button (square with lines in it, top) it'll say "This kernel doesn't support configuring SELinux" or something like that. i tried wiping stuff and it would just do a soft reboot. i may go file a proper report to TeamWin but i have CWM on there now and i don't particularly feel like reflashing a broken recovery.
TL;DR don't use TWRP
Hello, I'm new and trying to learn so please don't be too harsh. In following the instructions I somehow overwrote the stock rom and now duel boot CM 10.1 and 11. Any clue as in what I have done wrong?
Thanks in advance.
phrozen_flame said:
Hello, I'm new and trying to learn so please don't be too harsh. In following the instructions I somehow overwrote the stock rom and now duel boot CM 10.1 and 11. Any clue as in what I have done wrong?
Thanks in advance.
Click to expand...
Click to collapse
This thread OP is for updating the NT Internal Emmc to CM11 (from CM10.x), i.e., CM11 would be installed internally. If you were still running stock ROM internally, it wold be replaced by CM11.
good looking out
digixmax said:
[Caveat emptor: adopt/follow this guide at your own risk].
[Important Note: this process is applicable for CM11 builds that still maintains two separate partitions for /data and /media – as in CM10.x and stock ROMs (see http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more info). If/when these two partitions get merged in some future CM11 builds (as being contemplated by our NT CM developers – see http://forum.xda-developers.com/showthread.php?t=2560827&page=28) this "CM10 to CM11" update process will not be valid for those future builds with merged /data+media partition].
Below is the process that can be used to update your NT emmc from CM10.x to CM11.
Download the following files to a location in your user content-media storage space on the NT:
the flashable_CWM_6.0.4.5_chrmhoffmann.zip file from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet which contains the CWM recovery v0.2 provided by Chris Hoffmann (in the first post of the XDA Official CM11 thread http://forum.xda-developers.com/showthread.php?t=2560827).
the zip file of CM11 ROM build of your choice from http://download.cyanogenmod.org/?device=acclaim (see http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items for considerations in choosing nightlies vs. snapshot/stable builds)
the zip file of the Gapps package corresponding to CM11 – e.g., pa_gapps-modular-mini-4.4.2-20140301-signed.zip from http://goo.im/devs/paranoidandroid/roms/gapps-mini
Boot into your current emmc recovery
Select install zip and install flashable CWM recovery zip file.
Reboot into the new emmc recovery (flashed in the preceding step).
Select Wipe data & factory reset.
Select install zip and install CM11 zip file.
Select install zip and install Gapps zip file.
Reboot into the new CM11.
Once the NT boots up, set up the wifi connectivity and your google account info. If you had previously used Google backup service your apps will be auto-downloaded (but their settings will not be auto-restored).
If the NT on occasion boots or reboots into a black screen (in lieu of CM boot animation), then you have encountered one of the "random boot crashes" – more info and potential remedies, see http://forum.xda-developers.com/showpost.php?p=48941796&postcount=94 and http://forum.xda-developers.com/showthread.php?p=48301259#post48301259.
A few additional points worth noting:
Flashing CM11 requires CWM version 6.0.4.5 or later, or TWRP version 2.6.3.0 or later. To create a flashable recovery zip file for TWRP, use an archive file manager such as 7-zip to delete and replace the recovery.img inside the flashable recovery zip file (obtained in step 1(a) above) with your choice of TWRP internal recovery image file from http://techerrata.com/browse/twrp2/acclaim (e.g., openrecovery-twrp-2.6.3.1-acclaim.img). Remember to rename the downloaded TWRP .img file to recovery.img before inserting it into the recovery zip file, and also rename the resulting new recovery zip file to some other name like flashable_TWRP_2.x.y.z.zip to avoid future mix-up.
Installing CM11 ROM and Gapps will override your NT's CM10.x boot, recovery, ROM, and Apps, so make sure that you backup all this stuff using recovery backup function, for easy in reverting to CM10.x if desired. See my post at http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more "Info and Tips for Mitigating Risks in Rooting and Flashing Custom-ROM".
I would advise against using any other functions of the recovery without first carefully researching to understand what they really do.
My thanks to all the developers who collective work created the wonderful CM11 ROM for the NT as well as the tools and info I made use of to install it.
Click to expand...
Click to collapse
Ive been trying to update for a while now and i just couldn't figure it out until i came across your thread.and as right now i am running cm 11 and its all good so far.you made my day.
Help
digixmax said:
[Caveat emptor: adopt/follow this guide at your own risk].
[Important Note: this process is applicable for CM11 builds that still maintains two separate partitions for /data and /media – as in CM10.x and stock ROMs (see http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more info). If/when these two partitions get merged in some future CM11 builds (as being contemplated by our NT CM developers – see http://forum.xda-developers.com/showthread.php?t=2560827&page=28) this "CM10 to CM11" update process will not be valid for those future builds with merged /data+media partition].
Below is the process that can be used to update your NT emmc from CM10.x to CM11.
Download the following files to a location in your user content-media storage space on the NT:
the flashable_CWM_6.0.4.5_chrmhoffmann.zip file from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet which contains the CWM recovery v0.2 provided by Chris Hoffmann (in the first post of the XDA Official CM11 thread http://forum.xda-developers.com/showthread.php?t=2560827).
the zip file of CM11 ROM build of your choice from http://download.cyanogenmod.org/?device=acclaim (see http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items for considerations in choosing nightlies vs. snapshot/stable builds)
the zip file of the Gapps package corresponding to CM11 – e.g., pa_gapps-modular-mini-4.4.2-20140301-signed.zip from http://goo.im/devs/paranoidandroid/roms/gapps-mini
Boot into your current emmc recovery
Select install zip and install flashable CWM recovery zip file.
Reboot into the new emmc recovery (flashed in the preceding step).
Select Wipe data & factory reset.
Select install zip and install CM11 zip file.
Select install zip and install Gapps zip file.
Reboot into the new CM11.
Once the NT boots up, set up the wifi connectivity and your google account info. If you had previously used Google backup service your apps will be auto-downloaded (but their settings will not be auto-restored).
If the NT on occasion boots or reboots into a black screen (in lieu of CM boot animation), then you have encountered one of the "random boot crashes" – more info and potential remedies, see http://forum.xda-developers.com/showpost.php?p=48941796&postcount=94 and http://forum.xda-developers.com/showthread.php?p=48301259#post48301259.
A few additional points worth noting:
Flashing CM11 requires CWM version 6.0.4.5 or later, or TWRP version 2.6.3.0 or later. To create a flashable recovery zip file for TWRP, use an archive file manager such as 7-zip to delete and replace the recovery.img inside the flashable recovery zip file (obtained in step 1(a) above) with your choice of TWRP internal recovery image file from http://techerrata.com/browse/twrp2/acclaim (e.g., openrecovery-twrp-2.6.3.1-acclaim.img). Remember to rename the downloaded TWRP .img file to recovery.img before inserting it into the recovery zip file, and also rename the resulting new recovery zip file to some other name like flashable_TWRP_2.x.y.z.zip to avoid future mix-up.
Installing CM11 ROM and Gapps will override your NT's CM10.x boot, recovery, ROM, and Apps, so make sure that you backup all this stuff using recovery backup function, for easy in reverting to CM10.x if desired. See my post at http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more "Info and Tips for Mitigating Risks in Rooting and Flashing Custom-ROM".
I would advise against using any other functions of the recovery without first carefully researching to understand what they really do.
My thanks to all the developers who collective work created the wonderful CM11 ROM for the NT as well as the tools and info I made use of to install it.
Click to expand...
Click to collapse
So, will pa_gapps-modular-mini-4.4.2-20140608-signed.zip work with any cm11?
11lump said:
So, will pa_gapps-modular-mini-4.4.2-20140608-signed.zip work with any cm11?
Click to expand...
Click to collapse
Yes.
Can't seem to figure this out myself. I have Twrp 2.6.3.0 and it won't let me flash CWM or CM11. Just gives the standard flashing error. Any ideas?
Sent from my XT1058 using XDA Free mobile app
this is a cwm wish can be flashed from cwm 5.0.2.8 OR higher
install method
1-reboot your phone to recovery
2-select install zip from sd card
3-select cwm_6.0.3.7.zip
4-reboot recovery
5-enjoy
THIS CWM IS EDITED FROM @ironman38102
http://forum.xda-developers.com/showthread.php?t=2631926&page=6
DOWNLOAD LINK http://www8.zippyshare.com/v/85889388/file.html
I'M A NEW DEVELOPER SO I CAN'T POST IN DEVELOPMENT THREAD BUT I HAVE GREAT ROMS TO POST SO SUPPORT ME BY PRESSING THANKS BUTTON THIS WON'T HARM YOU
The x man said:
this is a cwm wish can be flashed from cwm 5.0.2.8 OR higher
install method
1-reboot your phone to recovery
2-select install zip from sd card
3-select cwm_6.0.3.7.zip
4-reboot recovery
5-enjoy
THIS CWM IS EDITED FROM @ironman38102
http://forum.xda-developers.com/showthread.php?t=2631926&page=6
DOWNLOAD LINK http://www8.zippyshare.com/v/85889388/file.html
I'M A NEW DEVELOPER SO I CAN'T POST IN DEVELOPMENT THREAD BUT I HAVE GREAT ROMS TO POST SO SUPPORT ME BY PRESSING THANKS BUTTON THIS WON'T HARM YOU
Click to expand...
Click to collapse
Stock based roms?
We are waiting for it..
i think cwm has already been posted(the flashing from 5.xx part too)
btw have u uploaded roms anywhere?
The x man said:
this is a cwm wish can be flashed from cwm 5.0.2.8 OR higher
install method
1-reboot your phone to recovery
2-select install zip from sd card
3-select cwm_6.0.3.7.zip
4-reboot recovery
5-enjoy
THIS CWM IS EDITED FROM @ironman38102
http://forum.xda-developers.com/showthread.php?t=2631926&page=6
DOWNLOAD LINK http://www8.zippyshare.com/v/85889388/file.html
I'M A NEW DEVELOPER SO I CAN'T POST IN DEVELOPMENT THREAD BUT I HAVE GREAT ROMS TO POST SO SUPPORT ME BY PRESSING THANKS BUTTON THIS WON'T HARM YOU
Click to expand...
Click to collapse
Can you please tell me what have you edited??
Code:
[email protected]:~/android/boot_tools/recoverytest$ find . | xargs md5sum
md5sum: .: Is a directory
md5sum: ./doc: Is a directory
c220e9181d5f152e9240d3b4e7e96c19 ./doc/zImage
b4b1812f4dd326225f69bb7a3e20d17a ./doc/initramfs.cpio.gz
md5sum: ./xman: Is a directory
c220e9181d5f152e9240d3b4e7e96c19 ./xman/zImage
b4b1812f4dd326225f69bb7a3e20d17a ./xman/initramfs.cpio.gz
If i'm not wrong.. This seems like the same recovery built by doc.
reply
If i'm not wrong.. This seems like the same recovery built by doc.[/QUOTE]
Actually doesn't install from internal sd card it is the same
It's been madded because I have found some problems in other
Like 1- change directory of backup from \extsdcard\clockworkmod to \extsdcard\0\clockworkmod\
so first can't find the backup of the second
2-problems in installing roms like t3romv2 (causes a bootloop)
So making this one will help solve this problems without need to Odin
The x man said:
Actually doesn't install from internal sd card it is the same
It's been madded because I have found some problems in other
Like 1- change directory of backup from \extsdcard\clockworkmod to \extsdcard\0\clockworkmod\
so first can't find the backup of the second
2-problems in installing roms like t3romv2 (causes a bootloop)
So making this one will help solve this problems without need to Odin
Click to expand...
Click to collapse
okay... looking at the /etc/recovery.fstab i don't see any mount point named extsdcard o_o
and i don't know about bootloop on t3romv2 cause i havent flashed it..
and it seems like you have dumped the recovery partition.. that's why your recovery.img exactly 10mb ...
did you made changes with adb push while on recovery?? if so changes made are lost with reboot.. and i guess you ended up with the unmodified version.. .
The x man said:
If i'm not wrong.. This seems like the same recovery built by doc.
Click to expand...
Click to collapse
Actually doesn't install from internal sd card it is the same
It's been madded because I have found some problems in other
Like 1- change directory of backup from \extsdcard\clockworkmod to \extsdcard\0\clockworkmod\
so first can't find the backup of the second
2-problems in installing roms like t3romv2 (causes a bootloop)
So making this one will help solve this problems without need to Odin[/QUOTE]
so if my rom didnt work other roms also wud give a bootloop...
Have u tried others?
What is PhilZ?
PhilZ Touch recovery is an advanced edition of cwm recovery, that provides more options and you can use the touch.
The original thread was posted by @karthick mostwanted who created this recovery for this device. He did it flashable with Rashr on a .img file, but the developer @Leonnard made it flashable with Odin. In my case, I tried with Rashr but did not flashed the recovery, so I tried the Odin version, and it worked. I think it was due to the ROM I installed to my cell phone, because the developer posted it on the original development section. So in conclusion, this should work in case you have a ROM installed. See the original thread.
Requisites: To know how to use Odin :silly:
Instructions
After you flash the recovery,do the following:
-Get into the recovery mode and go to <Recovery Settings>GUI preferences>Toggle Virtual Keys and disable them, because they don´t work, only the one to go back
-In that same menu, select "Menu Height" and select it up to get number 20, wich is the smallest, perfect for the little screen of the phone.
-Go to /sdcard/clockworkmod/ and create the folder "aromafm" and "custom_res"
-Go to /storage/extSdCard/clockworkmod and create the "custom_res" folder too (ih this carpets you can save pictures in .png files and then use those pictures as the background of the recovery)
-Download Aroma filemanager and place it in /sdcard/clockworkmod/aromafm/ and you will can use Aroma filemanager getting in Advanced Options>Aroma filemanager
Features
-Based on ClockWorkMod recovery v6.0.5.1 (lastest)
-Root Explorer built
-Binaries SuperSu
-Target sdcard
-Choose from check Root on/off
-Save and load the Recovery Settings
-Enter password in the Recovery
-Change colors and background
-Gestures
-Virtual buttons
-Size and sensitivity of menus
-Option "Clean to Install a New ROM"
-Custom option BackUp
-Shows Progress
-And much more
Some piece of advice, touch works only for scrolling, when selecting an option, you will NEED to press the home button.
Downloads: http://sh.st/bgGAf
I decided to create odin package because sometime Rashr fails and when reboot, the old recovery still there
Big thanks to Img to tar devs
Sent from my GT-S5312 using XDA Free mobile app
Lennoard said:
I decided to create odin package because sometime Rashr fails and when reboot, the old recovery still there
Big thanks to Img to tar devs
Sent from my GT-S5312 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, you're right. That happened to me
I have discovered some errors, for example you can´t put a background image. Developers should maybe improve this recovery
I was incorrect, the method is not the best one but is the only one I've discovered. Take a screenshot in the recovery and modify that image. Good luck!
Mine is fine
David Masa said:
I was incorrect, the method is not the best one but is the only one I've discovered. Take a screenshot in the recovery and modify that image. Good luck!
Click to expand...
Click to collapse
Don't need to do it
Just drop the PNG image in ClockworkMod directory in SdCard1
Which is:
sdcard1/clockworkmod/custom_res
After this
Change the image normaly