PART1: GTAB 3588 Recovery Pack
IMPORTANT NOTE: THESE WILL ONLY WORK WITH 1.1-BASED ROMS!!!!! The new Viewsonic build 4349 does NOT work with these!!!
What this is
A set of tools to flash recovery within a rooted GTablet. This pack includes stock 3588 and bekit's .8 clockworkmod recovery, the flash_img utility, and a Terminal Emulator. This is completely mod-agnostic and should be able to work on most rooted mods. Do NOT use this on 1.2-based stock or mods!!!!
This pack will be built into TNT Lite 4.3.0 and gADAM 1.3.0. I am supplying this pack for all other rooted "legacy" 1.1-based mods out there.
Installation Instructions
This is in an update.zip format. Extract the rar to the root of your internal memory, so that you have a recovery folder and an update.zip. You'll need the apk folder only if you wish to install the Terminal Emulator via a sideload.
Run either standard or clockworkmod recovery and install the same way you would install any ROM. Again, this is only a small set to tools, not a full ROM!
Usage
a) To flash recovery to 3588 stock recovery, using your GTablet
- Download the app "Android Terminal Emulator", by Jack Palevich. Or sideload it (the apk is in the RAR file)
- Run the app, toggle the soft keyboard and change the font settings, if desired (default is very small)
- Type "su" (Superuser should allow su access. If not, you are not rooted and cannot use this!)
- Type "fixrecovery.sh". This should run the flash_image tool and complete in 5-10 seconds
Reboot into recovery to test. 3588 stock has no options, so assuming you have no update.zip in the root of your /sdcard, it should just error out with an "!" error (that's what we want to see).
b) To flash recovery to clockworkmod .8 bekit version recovery, using your GTablet
- Follow steps 1 to 3, above
- Type "cwmrecovery.sh". You should the flash_image tool run and complete
Reboot into recovery to test. You should see the clockworkmod .8 bekit screen, which means the flash was successful.
c) To flash either recovery with adb
Just use an "adb shell" and then run the shell script needed. Again, this requires root access.
Download
3588 Recovery Pack v1.0 Link: http://www.mediafire.com/?1k1zlrsb4f8tkol
md5sum: 34190022d178a9e22494527103de7eac
(update on 3/23/2011)
=====================================
PART2: Clockworkmod .8 bekit (legacy version)
What this is
This is the legacy clockworkmod for 1.0.1-1.1 ROM's (ie. VEGAn, gADAM, TnT Lite 1.x-4.x, etc). It's an update.zip package to flash to clockworkmod, and is OS and hardware agnostic. Do NOT use this on 1.2-based stock or mods!!!!
Installation Instructions
This is in an update.zip format. Extract the main ZIP to the root of your internal memory, so that you have a recovery folder and an update.zip.
Testing
Reboot into recovery. If you see "clockworkmod .8 bekit" in the title, then it is installed.
Download
clockworkmod .8 bekit Link: http://www.mediafire.com/?dvleg4oatkfxm7w
Alternate Link: http://www.megaupload.com/?d=DHOASVPG
md5sum: d34079a1f0e83d8c4e09efe78cda0cc3
(updated on 11/9/2010)
=====================================
PART3: Stock 3588 Recovery Standalone
What this is
This is the stock 3588 recovery for 1.0.1-1.1 ROM's (ie. VEGAn, gADAM, TnT Lite 1.x-4.x, etc). It's an update.zip package to flash to 3588 stock recovery, and is OS and hardware agnostic. Do NOT use this on 1.2-based stock or mods!!!!
Installation Instructions
This is in an update.zip format. Extract the rar to the root of your internal memory, so that you have a recovery folder and an update.zip.
Testing
Reboot into recovery (and ensure you have no update.zip in the root of your device). Standard recovery is very simplistic - if you get an "!" error, you most likely have standard recovery installed.
Download
3588 Stock Recovery Link: http://www.mediafire.com/?97o1jc7ceth8hp7
md5sum: 983ca4efe81ced2604ccdebc5aedfbb9
(Updated on 3/23/2011)
Is this the 'writing on the wall' concerning 3991? Or just another tool?
joe2262 said:
Is this the 'writing on the wall' concerning 3991? Or just another tool?
Click to expand...
Click to collapse
The need for a way to get back to 3588 recovery has been coming up lately - this is a way to address that.
excellent work as always roebeet...if u don't mind just 1 suggestion...when i write my tutorials and such i try to keep things as generic as possible for easier future changes. might i suggest to make your job easier in the future to change the 3588 wording and such to something like latest vs stock or something similar? then all you have to do is update the link and link's descriptor. same thing with cwm i suppose. regardless, this is definitely sticky worthy IMO. great work
flipovich said:
excellent work as always roebeet...if u don't mind just 1 suggestion...when i write my tutorials and such i try to keep things as generic as possible for easier future changes. might i suggest to make your job easier in the future to change the 3588 wording and such to something like latest vs stock or something similar? then all you have to do is update the link and link's descriptor. same thing with cwm i suppose. regardless, this is definitely sticky worthy IMO. great work
Click to expand...
Click to collapse
I actually worded this with future proofing in mind. It will likely always stay 3588.
I have to see if the next VS firmware changes things - if it does, 3588 is a term we will all be using. Or "1.1" or "legacy".
Roebeet,
Just to clarify, if I wanted to go back to 3588 from TNT 5.0.1 (TwoTapsx), I just use the native recovery mode of TwoTapsx to load the 3588 update.zip file and then install clockworkmod .8?
The 3588 recovery packs and procedures mentioned here would or would not also work to down grade from 3991 to 3588?
Thanks,
Gramps..
roebeet said:
I actually worded this with future proofing in mind. It will likely always stay 3588.
I have to see if the next VS firmware changes things - if it does, 3588 is a term we will all be using. Or "1.1" or "legacy".
Click to expand...
Click to collapse
ahh, gotcha. even better then
Gramps said:
Roebeet,
Just to clarify, if I wanted to go back to 3588 from TNT 5.0.1 (TwoTapsx), I just use the native recovery mode of TwoTapsx to load the 3588 update.zip file and then install clockworkmod .8?
The 3588 recovery packs and procedures mentioned here would or would not also work to down grade from 3991 to 3588?
Thanks,
Gramps..
Click to expand...
Click to collapse
I amcurious about this too. Assume I flash to a rom with the new recovery, can I get back to 3588 with these tools?
ramerco said:
I amcurious about this too. Assume I flash to a rom with the new recovery, can I get back to 3588 with these tools?
Click to expand...
Click to collapse
I have to revamp my instructions, but the gist of it is this: You just run 3588 stock ROM, against the TNT Lite 5 / TTx standard recovery. That standard recovery will downlevel the bootloader, which the critical part to avoid a brick.
TNT Lite 4.3.0 and gADAM 1.3.0 should also work, but for the sake of my sanity I'm just going to recommend running 3588 stock as a backout.
Gramps said:
Roebeet,
Just to clarify, if I wanted to go back to 3588 from TNT 5.0.1 (TwoTapsx), I just use the native recovery mode of TwoTapsx to load the 3588 update.zip file and then install clockworkmod .8?
The 3588 recovery packs and procedures mentioned here would or would not also work to down grade from 3991 to 3588?
Thanks,
Gramps..
Click to expand...
Click to collapse
Yeah ... I'm wondering the same too
Also wondering should I follow PART1, PART2 and PART3 for recovery process?
roebeet said:
I have to revamp my instructions, but the gist of it is this: You just run 3588 stock ROM, against the TNT Lite 5 / TTx standard recovery. That standard recovery will downlevel the bootloader, which the critical part to avoid a brick.
TNT Lite 4.3.0 and gADAM 1.3.0 should also work, but for the sake of my sanity I'm just going to recommend running 3588 stock as a backout.
Click to expand...
Click to collapse
Roebeet,
If I have installed clockworkmod for TNT Lite 5, can I just flash update using CWM from image downloaded from PART3 ?
All of the Part 1-3 instructions address versions 1.0.1 - 1.1 (the first generation of ROMs
and software) as far as I can understand. Will there be a "Part 4" like
them to address the 1.2 software -- 3991 and TTx (since I have both and will have to
go back eventually.
Rev
EDIT -- I changed this post to what I want to know so I wouldn't muddy the waters.
butchconner said:
All of the Part 1-3 instructions address versions 1.0.1 - 1.1 (the first generation of ROMs
and software) as far as I can understand. Will there be a "Part 4" like
them to address the 1.2 software -- 3991 and TTx (since I have both and will have to
go back eventually.
Rev
EDIT -- I changed this post to what I want to know so I wouldn't muddy the waters.
Click to expand...
Click to collapse
thank you butch, so i wait for roebeet to post part 4 then
butchconner said:
All of the Part 1-3 instructions address versions 1.0.1 - 1.1 (the first generation of ROMs
and software) as far as I can understand. Will there be a "Part 4" like
them to address the 1.2 software -- 3991 and TTx (since I have both and will have to
go back eventually.
Rev
EDIT -- I changed this post to what I want to know so I wouldn't muddy the waters.
Click to expand...
Click to collapse
There will be, if it's needed. I might update the title and move things around, or create a new thread. It's hard to know until I see what gets released.
"1.0.1" and "1.1" are the stock ROMs we currently have (3588 is actually 1.1-3588, for example). 3991 UAT is "1.2".
So what would the process be to revert from 3991 and TT?
To make sure -- I run the Part I need above using the recovery
in 1.2 (3991 and TTx).
Rev
dony71,
My bad. I said I was trying not to muddy the waters and in asking what
I wanted to know I did just that. My apologies.
Since I didn't see an option for UAT 3991 and TTx (1.2 versions) in the original first post, I was wondering if roebeet was going to add another section explaining in
detail the procedure for them.
Rev
butchconner said:
dony71,
My bad. I said I was trying not to muddy the waters and in asking what
I wanted to know I did just that. My apologies.
Since I didn't see an option for UAT 3991 and TTx (1.2 versions) in the original first post, I was wondering if roebeet was going to add another section explaining in
detail the procedure for them.
Rev
Click to expand...
Click to collapse
It's going to go into the TTx thread, initially (it's my giant list of To Do's). That's because "1.2" isn't released yet.
Thanks for the clarification.
Rev
Roebeet
This should eliminate many questions from new rooters as the original recovery instructions have been modified so many times. Thanks again for making a fairly simple process even simpler
Easy to understand and simple method to recover. Thanks Roebeet.
Will this work to return to stock 1.1 from 1.2.4349 ?
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...
Hi Everyone, How I can install a custom recovery in a500 On ICS
The Build Number is : 1.031.00_WW_GEN1
Image Version is : RV03RC01_WW-GEN1
If You help me i can help you :highfive:
Sorry For My Bad English
:silly:
________________________________________
Acer A500 Stock ICS
HTC Incredible 2 Stock ( For Now)
1. Install acer recovery installer from market. This apk is free.
2. Keep with you the .zip or .image file of recovery which you want to install and place it in sd card.
3. Run the apk and select install from sd card.
4. If apk do not detect .zip file in your sd card than extract recovery.image from that file and store it in sd card.
---------- Post added at 11:39 AM ---------- Previous post was at 11:27 AM ----------
You can get custom recovery files from tegraowners.com or any other custom recovery in development section.
jancarlos1597 said:
Hi Everyone, How I can install a custom recovery in a500 On ICS
The Build Number is : 1.031.00_WW_GEN1
Image Version is : RV03RC01_WW-GEN1
Click to expand...
Click to collapse
The real answer is if you have ICS, to install a custom recover or custom kernel you must have an unlocked bootloader.
The following resources are related to the new bootloader, a quick read of the OPs of the first two are highly recommended, even if you install with the third link. (This is to have a highlevel idea of what you are changing on your device, as it will help you find what you need to look closer at in future if something goes wrong, or possibly prevent a problem in the first case)
bootloader thread
civato's guide
Afterota tool (windows users bootloader install tool)
If you already have the unlocked bootloader installed, but can't boot into recovery:
This is likely because you have a stock ICS rom overwritting recovery with the stock recovery in every boot; either use fastboot or (if you have root) a program such as acer recovery installer to force the install of a recovery and immediately reboot into it. (Most bootloader installers will also install a recovery that you can immediately boot into)
Once in recovery you can backup/restore/or install a rom modified to prevent the overwrite of recovery. (More advanced users can stop this from adb by removing some files)
Personally I use a lightly modified version of the stock rom you are using now:
http://forum.xda-developers.com/showthread.php?t=1661492
it ought to be safe to do a no wipe update to that and receive a more expected environment with a custom recovery, optional custom OC kernel, and busybox support.
However if you explore the dev section, many other (both more and less modified) versions of ICS roms exist. Themed and otherwise. So feel free to explore.
Closed
:good: MOD Please Close This, I Fix This.
Hi. To introduce myself, I came from iPhone universe and I'm new to Android system.
I'm used to linux systems and I'm also a developer...
Here, I just want some answer about "hacking" actions on my fresh Nexus 7 device because I red a lot of articles but I still don't understand all this stuff..
Correct me if I'm wrong but in order to install a custom ROM (which it's my goal), these are the steps:
1. Unlock bootloader (--> wipe all datas)
2. Root the device (manually with "adb" or automatically with a toolkit : "nexus 7 toolkit" or "wugs")
3. Install custom recovery (TWRP or CWM)
4. Flash a kernel
### My Questions ####
a) Coming from Linux world I can't get with the wiping of data while unlocking the bootloader. A bootloader is a simple portion of code which locate the kernel for booting the system. So, in my head, it just can't wipe or deal with user's data!!!
b) Rooting the device. Huuum, that's the part that I fully understand. I will probably use a toolkit because I'm on Mac and I don't want to download all the SDK packages, drivers, ect.. only to type 5 commands. Althought, I've red all the adb and fastboot commands
c) The purpose of the custom recovery is to replace the bootloader by an advanced one which can deal with flashing partitions and caches, backuping, exact?!
d) Flashing the kernel. LOL, it sounds like "compiling the kernel" which is the noob's favorite expression Personally, I only do one compilation of my kernel for 10 years.. So do I really need to "flash" the kernel?
e) I red that I have to choose a specific kernel to work with the custom ROM. WTF?! And I don't speak about overcloaking or kernel governors/schedulers.... I'm lost
==> All I wan't to do is trying some custom ROMs like CM, Paranoid, Smooth.... to find which fits the best for me
Thank you for your help and sorry for this beginner post but I really need advices and to summary into a single place.
xozeus said:
Hi.
Click to expand...
Click to collapse
Hi
xozeus said:
1. Unlock bootloader (--> wipe all datas)
2. Root the device (manually with "adb" or automatically with a toolkit : "nexus 7 toolkit" or "wugs")
3. Install custom recovery (TWRP or CWM)
4. Flash a kernel
Click to expand...
Click to collapse
#3.5 Make a full Nandroid Backup with the custom recovery. Get a copy of it off the device, too. You will thank me profusely for this later - mark my words.
#4 Should be "flash a ROM", not "flash a kernel" : the boot partition (a binary blob containing a Linux kernel plus it's initial ramdisk) plus 100% of the files that live in the /system mount point). A custom kernel is optional as 100% of ROM devs provide a default boot image, or let you choose one as part of their installation.
xozeus said:
a) Coming from Linux world I can't get with the wiping of data while unlocking the bootloader. A bootloader is a simple portion of code which locate the kernel for booting the system. So, in my head, it just can't wipe or deal with user's data!!!
Click to expand...
Click to collapse
That is a security feature if the tab is stolen - a thief can't get your creds. By unlocking the boot loader you are making things easier for a bright thief. Of course, not using a screen lock, or having a custom recovery on the tab gives a thief the same opportunities.
xozeus said:
b) Rooting the device. Huuum, that's the part that I fully understand. I will probably use a toolkit because I'm on Mac and I don't want to download all the SDK packages, drivers, ect.. only to type 5 commands. Althought, I've red all the adb and fastboot commands
Click to expand...
Click to collapse
Do as you will. Google makes things more difficult than it need be; but all you really need on a Mac is the adb and fastboot executables plus supporting link libraries (I recall using both on a live Linux CD boot with a thumb drive - I think only one additional shared lib was needed - three files total.)
xozeus said:
c) The purpose of the custom recovery is to replace the bootloader by an advanced one which can deal with flashing partitions and caches, backuping, exact?!
Click to expand...
Click to collapse
No concerning the boot loader - Yes sorta for the rest of it. Bootloader is analogous to BIOS - it is not the same as the "boot partition". Just as with a BIOS, you should probably avoid fooling with it. The bootloader and recovery boot are completely separate. There are two Linux kernel bootable partitions: boot and recovery. These partitions both hold a Linux kernel and a ramdisk. In fact, the kernel is usually identical in both - the only difference between them is that the recovery ramdisk starts up *nothing* which needs either /system or /data to be mounted. This means that it has a small toolset built to live in the ramdisk AND can perform offline file system maintenance on /data and /system - including destroying them completely and rebuilding them. Contrast that to booting the regular "boot image" that will start up regular ole Android - all that Dalvik code needs both /system and /data to be mounted, thus making it impossible to do aggressive filesystem updates (e.g. OTAs) without wedging the OS
Think of the recovery as being similar to "single user mode" in Linux. The only difference is that completely separate kernels and ramdisks are used, and the don't live inside file systems... they are stored in raw partitions (boot and recovery)
xozeus said:
d) Flashing the kernel. LOL, it sounds like "compiling the kernel" which is the noob's favorite expression Personally, I only do one compilation of my kernel for 10 years.. So do I really need to "flash" the kernel?
Click to expand...
Click to collapse
By convention, ROMs come with a boot image (Note: NOT bootloader) so flashing a kernel is always optional. When it is done though, it needs to be done after flashing a ROM bundle (see previous sentence for the why of it)
xozeus said:
e) I red that I have to choose a specific kernel to work with the custom ROM. WTF?! And I don't speak about overcloaking or kernel governors/schedulers.... I'm lost
Click to expand...
Click to collapse
Not true. However, there probably are ROM+kernel combinations that don't mix and match well. Some kernel devs ship an entire boot image (kernel + ramdisk), and some of them ship kernel only along with an installer that patches the prior existing boot image. Suffice it to say you should expect some bumps in the road.
They will only be bumps if you have backups, and big headaches if you don't.
Thank you so much, I forgot to reply and thank you because you made me read a lot lol muchas gracias !
Sent from my GT-I9195 using Tapatalk
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.