Related
Hi all,
I have thus far killed two Defy+ mobiles ($600 worth) following poor instructions on this site. I am now stuck using a 7" tablet as a phone!!!
My latest effort failed after installing 2ndinit 2.0 Stable, rebooting after turning USB Debugging off. Now it boot loops with the red Moto label. I have since read that one should never use 2.0 for Defy+ as it is known to have issues, even though the thread I took these instructions and the link from was referring specifically to a Defy+!!!
The last one I had did the same thing, only I thought it was because of the fact I chose to use the Latest rather than the Stable install of 2ndinit. I then proceeded to attempt to flash an SBF via the bootloader but now it is not booting at all, no logos, cant get to bootloader, nothing.
So, my question is, where can I get the latest Telstra Australia DEFY PLUS SBF from (please link me??) or one that I can flash over it that will work? Does anyone have any tips on how to recover this safely without sending it completely blank?
Also, does anyone have advice on how to recover the blank one?? Or is it useless?
Then, I would like to know, after I successfully recover the Defy+, HOW TO SAFELY 2ndinit it!!! I cannot afford to destroy another handset.
Thank you all for your prompt assistance! =)
which bootmenu did u install?and did u try flashing the SBF file via rsd lite?
fr0dzy said:
I have since read that one should never use 2.0 for Defy+ as it is known to have issues
Click to expand...
Click to collapse
I have run 2ndinit 2.0 on my Defy+ with no problem at all. I installed the latest bootmenu (1.0.7). Do you get the blue LED after powering the phone on?
You could try wiping data and cache in standard recovery. You should still be able to get in to that by holding vol- when you press and release the power button (press vol- and vol+ simultaneously when the android with the "!" in a red triangle appears). Your phone should still be rooted and have 2ndinit in place after a wipe. (Presumably you had rooted the phone? 2ndinit won't work otherwise.)
If that doesn't work then you may need to re-flash the SBF. If you know the build number of the ROM on your you can have a look on this thread to see if there is an SBF for it available online.
As a last resort, you could ask Motorola to fix it. If it's rooted then you've voided the warranty but if all it needs is a ROM flashing then they shouldn't charge you very much to do that. Better spend a few tens of dollars to fix the phone than write it off at a cost of several hundred dollars, surely?
recall while doing the install
did u root first??? did u get superuser permission prompt on downloading 1.0.7?did ur led flash GREEN???ensure that these are all yes
Dont worry brother. I had the same issue. I too got stuck in bootloop i.e at the M !
All I did was went in the stock bootloader ( POWER + VOL UP ) , connected it to my laptop. Downloaded RSDLite and the compatible sbf for my device ( Indian Version ) and then flashed it and it worked like charm
I would suggest you to use WiFi while using 2ndInit.
fr0dzy said:
Hi all,
I have thus far killed two Defy+ mobiles ($600 worth) following poor instructions on this site. I am now stuck using a 7" tablet as a phone!!!
My latest effort failed after installing 2ndinit 2.0 Stable, rebooting after turning USB Debugging off. Now it boot loops with the red Moto label. I have since read that one should never use 2.0 for Defy+ as it is known to have issues, even though the thread I took these instructions and the link from was referring specifically to a Defy+!!!
The last one I had did the same thing, only I thought it was because of the fact I chose to use the Latest rather than the Stable install of 2ndinit. I then proceeded to attempt to flash an SBF via the bootloader but now it is not booting at all, no logos, cant get to bootloader, nothing.
So, my question is, where can I get the latest Telstra Australia DEFY PLUS SBF from (please link me??) or one that I can flash over it that will work? Does anyone have any tips on how to recover this safely without sending it completely blank?
Also, does anyone have advice on how to recover the blank one?? Or is it useless?
Then, I would like to know, after I successfully recover the Defy+, HOW TO SAFELY 2ndinit it!!! I cannot afford to destroy another handset.
Thank you all for your prompt assistance! =)
Click to expand...
Click to collapse
There's always this quote: "Do it at your own risk"..
Never say it's the forumers instructions wrong or incorrect.
Read and double confirmed before taking the plunge modifying any system files.
Besides.. The death of your Defy is not really dead yet. I think your Defy boot just fine in the first place after installing 2nd-init. The only thing you need to do is press -Vol (when the blue light blink in the booting sequence) to enter into bootmenu and select boot normal as default. Because if this is your first installing 2nd-init, it might get you boot 2ndinit which was the cause of your bootlooping. Now you had flashed another sbf.. It's good to flash just Defy+ sbf and start again the process you failed in the attempt to get 2nd-init.
We learned from the mistake and master it over relentless practicing..
farsight73 said:
There's always this quote: "Do it at your own risk"..
Never say it's the forumers instructions wrong or incorrect.
Read and double confirmed before taking the plunge modifying any system files.
Besides.. The death of your Defy is not really dead yet. I think your Defy boot just fine in the first place after installing 2nd-init. The only thing you need to do is press -Vol (when the blue light blink in the booting sequence) to enter into bootmenu and select boot normal as default. Because if this is your first installing 2nd-init, it might get you boot 2ndinit which was the cause of your bootlooping. Now you had flashed another sbf.. It's good to flash just Defy+ sbf and start again the process you failed in the attempt to get 2nd-init.
We learned from the mistake and master it over relentless practicing..
Click to expand...
Click to collapse
+1 for your comment
Same thing happened to me as the OP.
Installed 2ndinit onto my Defy+, said installed and asked to switch off USB debugging and then reboot. I did that and am now in a boot loop. I didn't see the blue led when the phone rebooted, just straight to loop (red M logo, black screen, repeat).
I have tried taking the battery in and out (didn't help), celared cache and also factory wipe/reset (didn't work either). I can get the factory recovery and bootloader, but no android or 2ndinit recovery.
I assume I have to reflash with a full sbf. My question is this -
Does anyone have the stock Defy+ Telstra AU sbf for 2.3.4 (4.5.1-134 DPF-891) or more recent updates?
If not what is closest? I have found a few here but some of the 2.3.4 ones (bl5??) have no links (megaupload etc been pulled) or no root. This one looked promising (here) but no link. Would this one (here) be good?
Can I then apply OTA update to get back to AU firmware if I need? I would use MS2Ginger or CM7 if/when I get the phone working again, but return to stock is still useful.
Thanks for your help,
Nova
i must say u need to flash proper sbf to recover...
just wanna share my experience...
after installing SndndInit v2.0 ( with stock 2.3.6_134 DFP1321 ), i installed stable version of recovery & rebooted my phone...all of this with usb debugging "ON"...n got no errors! maybe there is no need to keep debugging off...
Sent from my MB526 using XDA App
OK, I flashed full sbf and got the phone working again (uses the sbf from the second link in my previous post). Then rooted and install 2ndinit again.
Boot loop again, exactly the same as the first time.
Install goes well, says it is installed, green led is on, however when I reboot, boot loop. There is no recovery screen or anything (except stock).
Is there some more detailed install instructions other than in the 2dninit thread? I have been transferring to sd card root, click apk to run 2ndinit, select 1.0.7 and it says everything worked. Just doesn't when I reboot.
Cheers,
Nova
No-one has any suggestions?
Do I need to put 2ndinit.apk in phone and not sd card?
I am going to try an older version and see if that works.
Cheers,
Nova
i hope you have rooted your phone properly else use SuperOneClick from here
you can download different versions of SndInitDefy.apk form here
go to Setings -> Applications -> Manage Application
look for SndInitDefy & clear its data (your previous install)
put the downloaded apk in SD card & run it (fresh install)
MY NOTE--keep usb debugging ON all the time...
run defy2ndInit - install 2ndInit Recovery - select latest version...
let it download...1st RED led lights then Green...wait for 2 minutes...reboot your phone...
when phone reboots BLUE led flashes for just 3-4 seconds...press VOL DOWN button when its flashing...
i hope this helps..im not a pro but i did follow exact same steps just 2 days back..
PS i did used v2.0 of SndInitDefy.apk...no problems yet..made backup twice & recovered too..
Well I tried v1.7 and that worked. I then updated to version 2.0 and that worked as well so i don't know what was going wrong. The only thing that happened different was the red led came on while 2ndinit 1.7 was loading (this had not happened before), so I would guess that 2.0 wasn't properly installing even though it said that it was installed.
Thanks for all your help.
Cheers,
Nova
hit thanks if I've helped
right now I'm having ICS on my phone thanks to quarx
Sent from my MB526 using XDA
apurvdate said:
hit thanks if I've helped
Click to expand...
Click to collapse
Did that. And thanks again for your help.
Cheers,
Nova
Had exactly same problem
I did the same experience as you after locking up after 2ndInit.
I used your recovery sbf as suggested and the phone works again. Thanks!
Were you able to find a Telstra Defy sbf and were you able to get 2ndInit to work and upgrade to CM9 & ICS?
Cheers,
apurvdate said:
i hope you have rooted your phone properly else use SuperOneClick from here
you can download different versions of SndInitDefy.apk form here
go to Setings -> Applications -> Manage Application
look for SndInitDefy & clear its data (your previous install)
put the downloaded apk in SD card & run it (fresh install)
MY NOTE--keep usb debugging ON all the time...
run defy2ndInit - install 2ndInit Recovery - select latest version...
let it download...1st RED led lights then Green...wait for 2 minutes...reboot your phone...
when phone reboots BLUE led flashes for just 3-4 seconds...press VOL DOWN button when its flashing...
i hope this helps..im not a pro but i did follow exact same steps just 2 days back..
PS i did used v2.0 of SndInitDefy.apk...no problems yet..made backup twice & recovered too..
Click to expand...
Click to collapse
I have rooted phone and tried both the 1.7 and 2.3 apps for 2ndInit Recovery and still on stock ROM but i never get the blue led flashing on boot up.
Any ideas?
Defy Plus indian firmware
nidhish91 said:
Dont worry brother. I had the same issue. I too got stuck in bootloop i.e at the M !
All I did was went in the stock bootloader ( POWER + VOL UP ) , connected it to my laptop. Downloaded RSDLite and the compatible sbf for my device ( Indian Version ) and then flashed it and it worked like charm
I would suggest you to use WiFi while using 2ndInit.
Click to expand...
Click to collapse
Can u please provide me the indian firmware link
Thanks
Zafar
Black camera!
Black camera!
Hey!
Somebody help me!!
Defy +: I put the original ruins of the ruins Rotolo, then the Boot Menu in Hungarian translation, and are followed by the error in the "Blade" my brain that I installed along with the 720p and panorama for Gingerbread Motorola
and since then my camera does not work, just great blackness!
Somebody help me!
green lenses!
---------- Post added at 06:31 PM ---------- Previous post was at 06:23 PM ----------
Black camera!
Hey!
Somebody help me!!
Defy +: I put the original ruins of the ruins Rotolo, then the Boot Menu in Hungarian translation, and are followed by the error in the "Blade" my brain that I installed along with the 720p and panorama for Gingerbread Motorola
and since then my camera does not work, just great blackness!
Somebody help me!
green lenses!
HI there. First i want to excuse for my bad english.
So, right into the question. Week ago i tried to flash CM9 on my moto defy. I flashed it, it ran well, when suddenly, after 2-3 days the trebuchet luncher crashed. I reboot my phone and all i got is boot loop. So, i'm a noob , but i tried to fix the problem whit installing one of the SBF's for moto defy+ (didn't notice that, the sbf is for Defy+ not for Defy). Actually the rom ran great, but the camera don't work. So i have a NANDROID backup but the moto defy original recovery, doesn't flash it (it says: "E: failed to verify whole-file signature"). I can't instal clockworkmod, couse i can't root the rom. So, the question is: is there any chance to root my rom and instal clockworkmod or can i fix the original recovery error, so i can apply my backup and downgrade to 2.2 froyo.
The rom that i flashed is ->
4.5.1-134-DFP-231 - retail, vodafon, tmobile, O2, full Blur
I tried to flash other SBF's but they dont work, or can't root either.
I tried to root the rom with everyone possible root exploits posted in this forum... but they doesen't work. I noticed that, there are some SBF's wich are rootable, but the download links doesen't work.
So, what is the exit of this ****ty situation?
no way out
No way at all???
wait for a miracle.
meanwhile read this :
http://forum.xda-developers.com/showthread.php?t=1542956
DFP-188, DFP-231, DFP-2311 BL7 Root
novaproject said:
HI there. First i want to excuse for my bad english.
So, right into the question. Week ago i tried to flash CM9 on my moto defy. I flashed it, it ran well, when suddenly, after 2-3 days the trebuchet luncher crashed. I reboot my phone and all i got is boot loop. So, i'm a noob , but i tried to fix the problem whit installing one of the SBF's for moto defy+ (didn't notice that, the sbf is for Defy+ not for Defy). Actually the rom ran great, but the camera don't work. So i have a NANDROID backup but the moto defy original recovery, doesn't flash it (it says: "E: failed to verify whole-file signature"). I can't instal clockworkmod, couse i can't root the rom. So, the question is: is there any chance to root my rom and instal clockworkmod or can i fix the original recovery error, so i can apply my backup and downgrade to 2.2 froyo.
The rom that i flashed is ->
4.5.1-134-DFP-231 - retail, vodafon, tmobile, O2, full Blur
I tried to flash other SBF's but they dont work, or can't root either.
I tried to root the rom with everyone possible root exploits posted in this forum... but they doesen't work. I noticed that, there are some SBF's wich are rootable, but the download links doesen't work.
So, what is the exit of this ****ty situation?
Click to expand...
Click to collapse
Okay dude. First thing:
Calm down. If you already are then read on!
Since Defy and Defy+ are more than 90% similar in hardware flashing SBF should not be a problem until you don't want downgradability! So from the name of the SBF I guess its for 2.3.6(GB) So now no way can you downgrade to Froyo kernel or for that matter any ROM using Froyo kernel. Am not sure about your ROM but I use the Asia retail SBF (4.5.1-134-DFP-1321 - retail-asia full Blur multilanguage) and I have rooted it using latest superoneclick and modded, rooted and installed CWM recovery umpteen times! So, what you can do is:
1.) Find out version of Android(2.3.4 or 2.3.6) in your phone at present.
2.) Case a:If it is 2.3.4: You can get any kernel and downgradeability is
preserved. There should be no prob faced!
Case b: If you have 2.3.6: You should try the SBF I have since it is rootable.
3.) Now I presume your phone should be working fine with Android 2.3.6.
Let me know if it works and than we can proceed further..
You can also give a try with Walter's fixed SBF and Nandroid backup
PS: A Defy as I understand is almost impossible to Brick!!! Y? Since its bootloader is locked
HI there, thx for the help
Yes, the installed rom is 2.3.6. I want to change it, couse the battery drain too fast (one day and it's gone) and there's no camera.
I flashed the rom that you said me (4.5.1-134-DFP-1321 - retail-asia full Blur multilanguage), but it's not working.. Doesn't boot at all. After the rom is flashed, the phone reboot and nothing, black screen. Only the white LED light on the upper left corner is activated. I'm giving a try with Walter's fixed SBF now.
Walter's fixed SBF doesen't work too. Same blackscreen...
novaproject said:
Walter's fixed SBF doesen't work too. Same blackscreen...
Click to expand...
Click to collapse
Oh! I think similar thing happened with me once when I installed CM9 kernel! This is what I did:
1.) Flash SBF. (Full)
2.) Boot to stock android recovery.
3.) Wipe data and wipe cache.
4.) Reboot.
Well since you already installed a full SBF of 2.3.6 you cannot downgrade! And from what I have seen till now from users experience(and mine) 2.3.6 gives much better battery life. So from now on whenever u use a nightly or ROM use the one for GB(Defy+) builds
This means, that i cannot change the rom anymore?
novaproject said:
This means, that i cannot change the rom anymore?
Click to expand...
Click to collapse
You can change ROMs. But you can't go back to an old or downgraded ROM(like froyo). That means you will always have to use ROMs made for Defy+ (GB). There are many CM7 nightlies by Quarx for Defy+ and the latest one for me worked great.
However, should you want to go to Froyo again there is a workaround:
A chinese sbf of froyo was found to have an updated bootloader! So the workaround is:
1.) Flash the chinese SBF(Never use the flash as it will burn your flash)
2.) Root, install 2nd init and CWM.
3.) Now you can flash CM and ROMs for Defy(Froyo) since you got a froyo
kernel(And use your flash now )
This is something I gave a try and it worked for me. I am sorry don't remember which thread it was with this tutorial. May be you can give it a search...
Thanx again.
I tried the chineese sbf but it didn't work. Same black screen...
Is there any way to instal .zip rom (like CM7) with program like RSD lite?
novaproject said:
Thanx again.
I tried the chineese sbf but it didn't work. Same black screen...
Is there any way to instal .zip rom (like CM7) with program like RSD lite?
Click to expand...
Click to collapse
Did you do a data wipe from stock recovery after installing the chinese SBF?
I dint quite get your second question! If you asked :
a.) Can zip be flashed using RSD lite.. No!! You cant. RSD lite understand only proper SBF files with correct checksum!
b.) Can zip be installed from stock recovery: No!! To instal a zip from stock you need the zip to be signed by motorola. That is why the whole concept of 2nd init comes up! It is a recovery menu which comes before the system boots up
It was the first question
Yes, i did the data wipe, and nothing... I think, no other SBF works except mine... I don't know what to do now.
novaproject said:
It was the first question
Yes, i did the data wipe, and nothing... I think, no other SBF works except mine... I don't know what to do now.
Click to expand...
Click to collapse
Sorry dint see that! I am afraid i think the SBF you flashed has BL7 as someone in the thread mentioned earlier! just to be sure:
1.) Download this .
2.) Extract the sbf and check the cmg versions. Check the version for cmg39.
3.) If it is 7. I am afraid there is no way out yet!! For the time being you are stuck with that SBF!! You are unable to boot because the SBF I gave you and most others has BL6 !!
Sorry again as I dint thought of this possibility earlier! And don't worry much. For now reflash the SBF that is working for you and wait till a way to root it is found!!
And speaking of it I welcome myself to the group!!
Just got back my Defy+ from service center and after I switched it ON I saw the lockscreen interface was different! A quick check told me that it is the latest SBF they flashed. I kept my fingers crossed. Once back home I checked and found this phone is not rootable!!! Now I am stuck too!!
Wooow, they flashed you BL7??
OK, man, im gonna donate you one AK47!
novaproject said:
Wooow, they flashed you BL7??
OK, man, im gonna donate you one AK47!
Click to expand...
Click to collapse
Oh that is so very nice of u!!!!
Sent from my MB526 using XDA
I Want To Flash New Rom & I'm Not Able To Switch To Boot Loader Nor The Phone Is Charging When Connecting To Charger. It Just Showing Me White Light While Connected To Pc. I Don't Know What Happen To My Defy, Not Able To Switch On Nor Able To Switch To Boot Loader Nor It Stuck To Motorola Logo. It Just Blank. No Reaction At All. Please Help Me Out. I Was Having Froyo First Then I Updated To CM7 Then I Again Tried To Restore Back To FrOyo. But I Failed To I Suck Up To Google Logo, Then I Tried To Flash The SBF File(Downloaded From xda Developer) I Got Successfully Passed But It Doesn't Affected My Defy & The Next Day I Tried To Switch To Boot Loader But I'm Not Able To. DEFY Is Giving Me No Reaction Wheater I Tried To Switch It On Or Try To Switch To Boot Loader Or To Charge The Phone. JUST Blank Screen.
cooperation escsua
i got the same problem but in my case i don't know which SBF i tried to install ... i am recharging my phone with external battery charger.. i gonna try to install all sbf i can find on the net and see if it will work
the black screen when show that u flash sbf low android version on ur phone.
dont wory.
u charge battery with external charger and try another sbf.
just careful that SBF is defy or defy +.
use this
http://forum.xda-developers.com/showthread.php?t=966537
i've tried all, but in my case the problem is that the phone is not getting in bootloader mode. i charged battery externally but it didn't work. i tried Go McGyver method also but phone did not start. so defy is not recognized by rsd also!!
i don't wanna go to service centre bcoz my phone is rooted and had all possible hack for defy installed thus guarantee is void.
can't root gingerbread 2.3.6
after all useless efforts to unbrick my defy i finally went to customer care! they flashed my defy with android 2.3.6., i was enjoying the new interface of gingerbread and was happy until i came to know the fact that i can't Root it now as any of the rooting tools like superoneclick (latest version) , z4root etc are not working!
is there any working method for rooting android 2.3.6 without flashing????
help!!
washi.sasoriza said:
after all useless efforts to unbrick my defy i finally went to customer care! they flashed my defy with android 2.3.6., i was enjoying the new interface of gingerbread and was happy until i came to know the fact that i can't Root it now as any of the rooting tools like superoneclick (latest version) , z4root etc are not working!
is there any working method for rooting android 2.3.6 without flashing????
help!!
Click to expand...
Click to collapse
I guess they've flashed a BL7 firmware. The above rooting tools will not work. They only way of rooting is mentioned in the below post:
http://forum.xda-developers.com/showthread.php?t=1595013
I have installed 4.0.3 leaked version but have issues with not being able to send emails from stock email software.
Ive now decided to just use it to try different custom roms.
I rooted it a while back with some one click solution I found on you tube. All worked fine...
Then I installed Acer Recovery Installer v3.03 and pushed on CWM 1.7 by thor onto the device.
But when I reboot I get "recovery verified failed" error.
Im stumped as to what to do now...
I looked at other posts and tried to follow them but the instructions dont seem to be for my situation so I thought Id post this.
If someone can help it would be great.
Hi All,
I picked up a Defy MB525 on ebay, mostlly to mess with but I need to use it as my daily driver for a while because I am buying a house and my money is tied up for that.
Anyway, it arrived with stock unrooted t-mobile froyo which I am sure you will all agree is unacceptable so i used framroot to root it and installed sndinit 2.3 and followed the instructions in the general section for installing KitKat. I followed the instructions including the note to update the phone to CM10 first which went fine. At one point, I had it running CM10.1 fine but when I installed KitKat, the phone got stuck at the boot screen. The instructions say that it is normal for it to take a long time and you will think you are stuck but I let it sit more than an hour. At that point I thought I was soft bricked so I went back and used RSD Lite to install the t-mobile eclair SBF on it, which is the only one I can find. All links to the Froyo SBF I can find are broken.
That is where I am stuck. When I try to install sndinit, I get no blue light on reboot and on the older versions and I get an SD mount error in the recovery.
I think the probably I am having are related to not having the Froyo firmware installed but when I try to install it the regular way, the phone reboots and I get the triangle with an exclamation point. As I said, I can't find the Froyo SBF. The links I can find are broken and I don't think it is listed here, which is where I found the eclair sbf:
http://sbf.droid-developers.org/phone.php?device=27
My questions are:
Does anyone know where to find the most recent t-mobile sbf file? Do you think that is my problem? If not, what is?
richdaley said:
Hi All,
I picked up a Defy MB525 on ebay, mostlly to mess with but I need to use it as my daily driver for a while because I am buying a house and my money is tied up for that.
Anyway, it arrived with stock unrooted t-mobile froyo which I am sure you will all agree is unacceptable so i used framroot to root it and installed sndinit 2.3 and followed the instructions in the general section for installing KitKat. I followed the instructions including the note to update the phone to CM10 first which went fine. At one point, I had it running CM10.1 fine but when I installed KitKat, the phone got stuck at the boot screen. The instructions say that it is normal for it to take a long time and you will think you are stuck but I let it sit more than an hour. At that point I thought I was soft bricked so I went back and used RSD Lite to install the t-mobile eclair SBF on it, which is the only one I can find. All links to the Froyo SBF I can find are broken.
That is where I am stuck. When I try to install sndinit, I get no blue light on reboot and on the older versions and I get an SD mount error in the recovery.
I think the probably I am having are related to not having the Froyo firmware installed but when I try to install it the regular way, the phone reboots and I get the triangle with an exclamation point. As I said, I can't find the Froyo SBF. The links I can find are broken and I don't think it is listed here, which is where I found the eclair sbf:
http://sbf.droid-developers.org/phone.php?device=27
My questions are:
Does anyone know where to find the most recent t-mobile sbf file? Do you think that is my problem? If not, what is?
Click to expand...
Click to collapse
I figured this out if anybody needs to know. I had to do a full system reset then restore the eclair sbf so that the phone is in the exact state it was in out of the box. Then the OTA install worked fine. I am still working on getting KitKat installed. It seems like I need to find the right combination of recovery and rom to get 10.1 installed.
richdaley said:
I figured this out if anybody needs to know. I had to do a full system reset then restore the eclair sbf so that the phone is in the exact state it was in out of the box. Then the OTA install worked fine. I am still working on getting KitKat installed. It seems like I need to find the right combination of recovery and rom to get 10.1 installed.
Click to expand...
Click to collapse
To install KK, root, 2ndinit, then go to recovery and flash this and reboot - http://d-h.st/dWr. Then after reboot, go back to recovery (don't go back to the system). Then flash this - http://d-h.st/dz8 and immediately flash KK and gapps.
hotdog125 said:
To install KK, root, 2ndinit, then go to recovery and flash this and reboot - http://d-h.st/dWr. Then after reboot, go back to recovery (don't go back to the system). Then flash this - http://d-h.st/dz8 and immediately flash KK and gapps.
Click to expand...
Click to collapse
Beautiful. It worked perfectly.