Related
This method doesn't rely on any root exploits & will work with any Android version on the ZTE Blade (and all variants). It should work on any phone with an unlocked bootloader (all zte android devices are sold with unlocked bootloaders).
Software needed:
adb (windows/linux/mac versions available as part of the android sdk - http://developer.android.com/sdk/index.html You will find adb in the tools directory.)
fastboot (windows/linux/mac versions available here: http://koushikdutta.blurryfox.com/G1/ )
windows drivers for the phone (if you use windows: http://support.zte.com.cn/support/news/NewsDetail.aspx?newsId=1000442 )
ClockworkMod (http://clockworkmod.com/rommanager - download zte blade clockwork recovery image)
SuperUser ( http://androidsu.com/superuser/ Download Eclair/Froyo/Gingerbread/Honeycomb (2.1 – 3.2) version) - Alternatively you can use any rooted custom rom
If your phone is running Android 2.1, then it is probably a 'gen1' device, search for "Mr Pigfish" on Android market if you're unsure. Gen1 blades will need an older version of clockworkmod, 3.0.1.4 - http://download.clockworkmod.com/recoveries/recovery-clockwork-3.0.1.4-blade.img
Method:
Download/install adb & fastboot. Install drivers for the phone if needed (on Windows).
Plug your phone into your pc using the usb cable, mount usb storage, then copy the Superuser or custom rom zip onto it & unmount usb storage.
Make sure that usb debugging is enabled on your phone, there should be an icon in the status bar, you can enable it in settings (settings -> applications -> development -> usb debugging).
Open a command terminal window & change to the directory that you downloaded recovery-clockwork-[version]-blade.img to. Type...
Code:
adb reboot bootloader
This will make the phone reboot, wait for the android logo (or custom splash screen) on the phone then type...
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-blade.img
fastboot reboot
You have just installed ClockworkMod recovery. Your phone will reboot back into android, when it has done that turn it off, then turn it on with the vol- button held to start clockworkmod. Use vol+/- to navigate, home button to select an option, back button to go back. You should create a backup now before you flash anything, when that backup is complete use 'install zip from sdcard' to either install superuser to root your stock rom, or install a custom rom. If you're installing a custom rom then you'll need to wipe data/factory reset too (you will lose all data). reboot, you're done.
I'm not sure if this is the right section for the thread, it'd probably be better in blade general. I forgot that newbies can't reply here.
Anyway, for those that can reply, can you suggest any improvements? I'll find links for adb, fastboot & windows drivers later.
Everything is clear except where to find adb and fastboot for noob users... (like me).
I did a little search and found out that adb is installed with the Android SDK... so, i installed it, installed the android platform-tools package, the usb driver but i am stuck with fastboot...
There is no fastboot in the Android SDK installation directory... and i can't find it on the web... so, i can't install clockworkmod recovery and i'm stuck...
Can u help me plz ?
Yeah, as I said, I'm still looking for links. you get fastboot when you compile android from source, but that is a bit of a long & complicated way.
Here is a pre-compiled version of fastboot for windows, linux & macos http://koushikdutta.blurryfox.com/G1/
adb works without the sdk too, I'll see if I can find links for that.
The windows driver is on zte's site somewhere, but that's a pain to find anything on. I'm not sure if the Google driver works. I don't even run windows, so if anybody can help write that part...
Probably best to for XP use the exe driver installer (Thats in the pcsuite.iso in the official 2.3.5 rom)
Windows 7 just works (gets drivers from windows update).
Does the superboot apk deal with changing default.prop (to allow adb remount etc).
If not could do that (use the same thing the CM7 universal converter uses to split the boot.img).
unrandomsam said:
Probably best to for XP use the exe driver installer (Thats in the pcsuite.iso in the official 2.3.5 rom)
Windows 7 just works (gets drivers from windows update).
Click to expand...
Click to collapse
Not everybody is running the official 2.3.5 rom, it's probably a tiny fraction of users. 2.1 roms don't have the driver iso. I found the drivers & updated the first post. The drivers on the phone should work fine, if you are running an unmodified 2.2 or 2.3 stock rom, just plug the phone in & it should mount a driver cd image over usb to install the drivers.
Does the superboot apk deal with changing default.prop (to allow adb remount etc).
Click to expand...
Click to collapse
It's superuser, it's a clockworkmod zip file & no, it doesn't change default.prop. It installs superuser & su.
If not could do that (use the same thing the CM7 universal converter uses to split the boot.img).
Click to expand...
Click to collapse
Tell ChainsDD, it isn't my software, I just wrote a quick idiot's guide.
Hi wbaw....
nice to see you posting helpful stuff here....
Can I ask what is perhaps a silly question, about the rooting process for ZTE devices, without relying on root exploits?
How is this different, or better, than using the z4Root modified by kallt_kaffe App, which I have linked (MoDaCo).
Is it just the use of the exploit, or is there another reason?
I have used it on my OSF/Blade, and never lost root or had any other problem, AFAIK.
Also, I see you are not showing your previous GEN1/Gen2 all-in-one TPT for GSF any more...is it available any more for ppl who may want to try it?
Thanks in advance
The exploit that z4root uses doesn't work on newer versions of Android (2.2.2 & above), ZTE are selling some phones with these newer versions of Android.
If z4root works for you, then that's fine, there's nothing wrong with it. It just doesn't work for everybody.
If you are using a version of Android that z4root (or other root exploits) do work on, then you should update Android asap. Otherwise a malicious app could use the same exploit to take over your phone. Root exploits themselves aren't bad (as long as you're doing it to your own device, or with permission of the owner) - the fact that root exploits work is bad & a sign that you need to update the software asap.
GSF has it's own thread. You can get the same effect by using the gen1 to gen2 tpt & then installing gsf. It is buggy & old, I think there is a nasty remote root exploit out there for 2.3.4 too. Just use CyanogenMod, it's much better, less buggy, more secure, they keep up with the latest Android fixes & it has more customisation options.
Thank you for the explanation...I will go ahead and do what you have advised.
I am just continuing to use good old Swedish Spring RLS5, which I think was kallt_kaffe (Cold Coffee) also......GEN 2 thanks to your Gen 1>Gen 2 TPT.
I think t is 2.2.
If I want to proceed to permanently root as you describe, should I use z4root to unroot first?
I will probably move to CyanogenMod, so I should use your exploit-free root instructions first.
BTW, I will be sad to move on from SS, as it does seem to be as near a perfect fit as I have found for the Blade.
I did put on GSF ,some time ago, and to be very honest, I just lasted a night with it, then restored the SS Nandroid.......it didn't feel at all as satisfactory a UI experience as SS.
Perhaps it was me, you know, you get used to an old pair of sneakers, etc.
As you said, it was and is always beta...it was an early version!!!
Thanks again, and keep up the good work in these calm(er) waters
Custom roms are already rooted. You don't need to root a custom rom, you just install it with clockworkmod.
If you already have a custom rom installed then you don't need any of this guide, you've already got clockworkmod. All this guide does is tell you how to install clockworkmod.
This is for people with phones on a stock rom who want to be able to install clockworkmod to root their stock rom or install a custom rom.
You shouldn't still be using Android 2.2 because the root exploit in z4root works on it, therefore other more malicious apps could use a similar exploit without asking you first.
Hi..... does this work on any Android phone?
I have in mind the new Samsung W i 8150.
Getting one for Xmas.... AFAIK
Sent from my ZTE-BLADE using Tapatalk
It should work on some other android phones, but they'll need adb & an unlocked bootloader, so it wont work with every phone. It should work on any ZTE android phone or tablet (except maybe the tureis?).
Hi!I have a Zte Blade with 2.3.5 OS. I tried to root my phone using this tutorial, but when i write : "fastboot flash recovery recovery-clockwork-5.0.2.0-blade.img" in Comand Prompt program, i get this message : "error: cannot load : recovery-clockwork-5.0.2.0-blade.img".
Can anyone help me, please?
Thanks!
stanangel said:
Hi!I have a Zte Blade with 2.3.5 OS. I tried to root my phone using this tutorial, but when i write : "fastboot flash recovery recovery-clockwork-5.0.2.0-blade.img" in Comand Prompt program, i get this message : "error: cannot load : recovery-clockwork-5.0.2.0-blade.img".
Can anyone help me, please?
Thanks!
Click to expand...
Click to collapse
You need to download clockwork recovery & be in the directory that you downloaded it to, to run that command.
Thank you!It works. Now, can I put Cyanogenmod 7.1 on 2.3.5 OS with this root and clocworckmod ?
stanangel said:
Thank you!It works. Now, can I put Cyanogenmod 7.1 on 2.3.5 OS with this root and clocworckmod ?
Click to expand...
Click to collapse
You can put clockworkmod on, but cm7 might not work without a bit of fixing, it is designed for 2.2 blades, zte's 2.3.5 has a different radio firmware.
Is this a 2.3.5 blade? where did you buy it?
Well, first time i had 2.1 update-1.After that I updated the version to 2.2 Boygues (or something like this) and then i found on this forum the official image.bin (2.3.5) and I decided to update.But now, i want to try CM.
stanangel said:
Well, first time i had 2.1 update-1.After that I updated the version to 2.2 Boygues (or something like this) and then i found on this forum the official image.bin (2.3.5) and I decided to update.But now, i want to try CM.
Click to expand...
Click to collapse
I see, you'll need to use another image.bin to go back to 'gen2' - the zte froyo radio firmware. Otherwise you wont get any phone signal, 3g or gps on CM7 because the 2.3.5 image.bin that you installed contained new radio firmware.
You don't need to root it first, you can install clockworkmod with a gen2 radio firmware using a custom image.bin like this one that http://www.mediafire.com/?jb4crw3em2m4r4x Amphoras made.
The 2.3.5 image.bin contained another new version of the radio firmware, which isn't compatible with CM7.
Uhuuu, it works.Thank you a lot! CM7.1 is awsome.This forum is awsome.
Hey I cant acess adb after doing adb reboot bootloader. When I come to the chinese letter I cant do nothing. So i cant fastboot flash recovery recovery-xxx.img.
What im i doing wrong?
1. Place the superuser.zip file attached at the end of the post on your sd card.
2. Flash recovery in bootloader with "fastboot flash recovery <filename>.img". I recommend CWM 5.0.2.3 found in this thread - http://forum.xda-developers.com/showthread.php?t=988686&highlight=recovery
3. Go to recovery, in "mounts and storage" select "mount system" and then flash su-install.zip (EDIT : Mounting system not necessary, the script does it automatically while flashing the zip, but just in case)
4. Fix Permissions and reboot system.
5. Use any root explorer (i recommend ROM Toolbox, free in market) and go to /etc and either rename "installrecovery.sh" to "installrecovery.sh.old" or just delete it (its not needed).
6. There it is - Rooted ICS with a recovery that sticks.
EDIT -- IF, by any chance, after following the above steps, you find that you're stuck without a recovery (android exclamation screen), just flash a recovery via fastboot and you'll be fine. This time the recovery WILL stick. I think its something to do with the su-install.zip. I dont know for sure because I found it off the internet, its not mine.
Also, I did the superuser market update and I DID NOT lose root. I have an I9020T. So others with the same can safely update, imo.
Thanks to ab.grafix for being a part of the team.
IMPORTANT -- The su-install.zip posted previously is NOT mine. I didnt know who made it but just found out. All credit to dzo binary and Chamb'. I just made a guide coz it worked for me and I thought it might help others too.
Tested on I9020T and I9023
Don't forget to click on that thanks button if this helped.
UPDATE -- Superuser was updated by ChainsDD to support ICS 4.0.3. Thank you ChainsDD! Updated zip is now attached.
So now that we have root we need a overclocked kernel...
Sent from my Nexus S using XDA App
works great but very old cwm
Worked as described. Thanks !
Old cwm? Wich version? Is it possible to flash the latest one with rom manager?
So I am on ICS alpha13.
I9023
- wipe everything and Flash Android 2.3.6/GRK39F/XXKF1 Radio/KA3 Bootloader via clockworkmod
- Reboot in stock recovery and flash stock ICS
- Boot in ICS enable debug mode
- Run the bat follow instruction?
Is it ok?
Thanks
Hi will it work on the rogers i9023a? Can someone tell me which stock ICS to flash?
Thanks
Thanks, it worked and nothing was wiped since I was already unlocked. With apps that require root you no longer get asked for root permission nor do they show in app list in superuser but it seems to have root for now
For the guys using linux (like me ) , just download the archive in the first post , retrieve from there 2 files: root.zip and recovery.img and use them with your current ADB setup.
HOW-TO:
Prerequisites: you have installed Android SDK, fastboot and you have set-up correctly the udev (ubuntu).
1. Place the above mentioned 2 files in the working directory
2. reboot in bootloader mode (vol-up + power)
3. connect USB cable
4. run "./fastboot-linux-i386 flash recovery recovery.img"
5. reboot bootloader
6. reboot recovery
7. mounts and storage -> usb mass storage
8. copy root.zip in the phone storage
9. go back -> install zip from sd card -> root.zip
DONE !
I just tested and is working fine.
If there are newbies out there trying to understand the nonsense I wrote, try following the rooting guide for Gingerbread and just use the 2 files I mentioned in this post instead of the ones in the archive for gingerbread.
when in BL i dont have Unlock option :|
Thanks for your effort.
But I'm curious about the flashable zip file.
What's the difference of the zip file between the orignal superuser ?
And did the recovery do some magic which CWM can't do?
After reading the script , I just see the zip is important ,maybe the recovery is doing some magic too.
I'll just flash the zip and see what happen.
ro_explorer said:
For the guys using linux (like me ) , just download the archive in the first post , retrieve from there 2 files: root.zip and recovery.img and use them with your current ADB setup.
HOW-TO:
Prerequisites: you have installed Android SDK, fastboot and you have set-up correctly the udev (ubuntu).
1. Place the above mentioned 2 files in the working directory
2. reboot in bootloader mode (vol-up + power)
3. connect USB cable
4. run "./fastboot-linux-i386 flash recovery recovery.img"
5. reboot bootloader
6. reboot recovery
7. mounts and storage -> usb mass storage
8. copy root.zip in the phone storage
9. go back -> install zip from sd card -> root.zip
DONE !
I just tested and is working fine.
If there are newbies out there trying to understand the nonsense I wrote, try following the rooting guide for Gingerbread and just use the 2 files I mentioned in this post instead of the ones in the archive for gingerbread.
Click to expand...
Click to collapse
In fact, you can use any recovery image you want, including the latest clockwork for example. I used TWRP to do this and it worked just fine. On linux, just flashed root.zip.
I've done it, thanks a lot. I've also replaced the recovery.img file with the last cmw and all went well.
Now the rom doesn't show the root permission request toast but it works however.
I'd ask if its possible to manually update the superuser.apk or its better to mantain this one?
sakisds said:
In fact, you can use any recovery image you want, including the latest clockwork for example. I used TWRP to do this and it worked just fine. On linux, just flashed root.zip.
Click to expand...
Click to collapse
Great .. I'll do that because I miss my "old" cwm
EDIT: it worked, thanks!
thanks, working here on 9023. warning for other users - do not update superuser from the app itself, or it'll stop working. at least it did for me, when i updated it to 3.0.3
confirmed working I9020a...
[INFO] Working root for ICS 4.0.3
Credits to Chamb'.
Flash via CWM and you're done.
Tested working for ICS 4.0.3 I9020T.
Enjoy!
Source: http://forum.xda-developers.com/showpost.php?p=20394635&postcount=4
It seems to have worked like a charm, thank you!
I was even able to flash the latest CWM Recovery using ROM Manager
can I flash stock 2.3.6 with cwm?
Im on ics alpha13
Anyone got a download link for the stock 2.3.6?
bratfink said:
Anyone got a download link for the stock 2.3.6?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1063664
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.
As i understand - there is no more upgrade to the operation system.
mine is the newest (4 )and i'm not satisfied with it.
Can someone tell me how to root it and what os to install and how. there are some guides but i do not know if they actual and good for os4 ver.
thanks.
libal said:
As i understand - there is no more upgrade to the operation system.
mine is the newest (4 )and i'm not satisfied with it.
Can someone tell me how to root it and what os to install and how. there are some guides but i do not know if they actual and good for os4 ver.
thanks.
Click to expand...
Click to collapse
Please don't start another *how do I root* thread there are dozens if not hundreds of postings on here explaining in great detail how to achieve root.
sorry but....
1. I ask for the best and easy way to root android 4
2.also for the best firmware.
thank you anyway...
To get root & custom recovery, the following methods are reported to be working with the latest Asus ROM:
http://forum.xda-developers.com/show....php?t=1689193
http://forum.xda-developers.com/show....php?t=1681155
http://forum.xda-developers.com/show....php?t=1688012
The first method ( [TOOL]PERI-0.4 One click root+recovery/fix-bootloops+soft-bricks ALL Devices V0.4) works well for me on TF101G with latest ICS . Just install it on the PC, run the .BAT file and follow the instructions to root and install Custom Recovery and Root / SU on the Transformer.
The only issue I've had is that this custom Recovery won't seem flash the ASUS stock ROM for some reason. So what I do now is use the above tool to get root and Custom Recovery, then use that to flash ClockWorkMod Recovery v6.0.1.4 NoTouch Hybrid from http://forum.xda-developers.com/show....php?t=1855686 - click the Download link and get the cwm-6.0.1.4-notouch-hybrid.zip file (apparently the Touch version is currently broken).
From CWM recovery you should be able to flash any custom ROM and kernel etc., and also return to stock by flashing the ASUS stock ROM from their download site (make sure you select the right one for your model and unzip it first - for some reason they put the zip ROM inside another zip).
If you do return to stock, don't forget you'll also lose root and custom recovery so you'll need to start over.
I'm using Android Revolution HD 3.4.3 3G which seems pretty stable. I've also heard good things about Revolver, but I couldn't get 3G working on the 3G version.
Good luck.
1 click root
http://forum.xda-developers.com/showthread.php?t=1689193
This worked for me. Just make sure you download version for your transformer.
well thank you all ...
thank you all...
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.