Database Users

[GUIDE] Install ClockworkMod Recovery image after updated to 2.3.4 (GRJ22).

Not applicable
Delete this thread

Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!

Too complicated.
Just:
1. turn on phone by holding volume up + power to go to bootloader
2. fastboot oem unlock (confirm it on the phone)
3. fastboot flash recovery recoveryfilename.img
4. Select recovery on the phone.
5. You're in ClockworkMod. Go flash a new ROM.

Let me answer myself.
I don't think the latest rom 2.3.4 is compatible with the clockwork you supplied. So I have to flash my phone back to GRH78. I downloaded the stock ROM from the internet. and then push all the images file into /sdcard/clockworkmod/backup/2010.xxx.
Next, I restore the image in clockwork menu.
after restore, reboot the phone, now I am back in business.
When the phone is boot, i lost the root again, so i went to modaco.com and get Paul's package. run it, restart, I got the root.
Finally, go to market place and get ROM Manager, install the clockwordmod. and I have a 'proper' phone.
although I don't have the least rom, at least i got a working phone that is rooted.

bante said:
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Click to expand...
Click to collapse
I have the same problem. How did you handle it?

Wow, why risk messing up your phone with flashing a boot.img when you can just rename /etc/install-recovery.sh to something like /etc/install-recovery.bak?
Here's one way to rename (courtesy of Matridom). Another is to use Root Explorer.
Matridom said:
The new update applies the install-recovery.sh script into our phones (not there previously.
Boot into the bootloader
flash CWM
select recovery from the bootloader (DO NOT reboot the phone)
apply the su binary
boot into the OS and test root
make sure busybox is properly installed
run ADB shell
then:
Code:
su
mount -o remount,rw /dev/block/mtdblock3 /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak
Boot back into the bootloader and re-flash CWM, should stay permanent now.l had applied the SU binary at the same time as the OTA update, then renamed the installer script and flashed back CWM.
Click to expand...
Click to collapse

andnaz said:
I have the same problem. How did you handle it?
Click to expand...
Click to collapse
same here someone please help ?

This is a totally unorthodox way to make the custom recovery permanent. If your phone is messed up, good luck fixing it.
There is a much easier and safer way like I mentioned.
PS: flashing recovery for 2.3.4 is the exact same as for 2.3.3!
fastboot flash recovery <recovery .img>
Sent from my Nexus S using XDA App

bante said:
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Click to expand...
Click to collapse
Hi Bante, I am sorry for the inconvenience. I have revert back the CWM Recovery to 3.0.2.4. You can download it at the link above, and try it again
I hope that the problem you mention wont persist anymore

zero383 said:
This is a totally unorthodox way to make the custom recovery permanent. If your phone is messed up, good luck fixing it.
There is a much easier and safer way like I mentioned.
PS: flashing recovery for 2.3.4 is the exact same as for 2.3.3!
fastboot flash recovery <recovery .img>
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I am sorry but not all people can successfully use Command Prompt to do so.
I cant use command prompt, as it says "Image cant be loaded".
So I had to use this method.
I search around the forum and seen this as a quite common problem,
so I decided to share it
Hope you understand.
Anyway, thanks for your method too Cheers

andnaz said:
I have the same problem. How did you handle it?
Click to expand...
Click to collapse
The CWM Recovery I supplied is version 3.0.2.5,
which is not compatible.
So I replaced with version 3.0.2.4.
You just download it at the link above and follow all the step again.
You should able to solve this problem
Do notify me if any problem persist

16vMK1 said:
same here someone please help ?
Click to expand...
Click to collapse
The CWM Recovery I supplied is version 3.0.2.5,
which is not compatible.
So I replaced with version 3.0.2.4.
You just download it at the link above and follow all the step again.
You should able to solve this problem
Do notify me if any problem persist

Wow people like to make things complicated. Why install an entire rom to get ride of a script?
if you can flash cwm, you should have some basic understanding of fastboot, adb and the search options in the forums. the answers are all there already.
Sent from my Nexus S

No disrespect, I agree flashing recoverys should only be done after you understand how to use the tools to do it. there is no reason someone who is going to mod systems on their nexus shouldn't be able to use fastboot and adb properly. all the right drivers are in the sdk.
Sent from my Nexus S 4G using Tapatalk

nxt said:
Too complicated.
Just:
1. turn on phone by holding volume up + power to go to bootloader
2. fastboot oem unlock (confirm it on the phone)
3. fastboot flash recovery recoveryfilename.img
4. Select recovery on the phone.
5. You're in ClockworkMod. Go flash a new ROM.
Click to expand...
Click to collapse
This is what I did.
I rooted my NS, which had 2.3.3
Used phone with stock 2.3.3 until I figured out which ROM I want to flash.
Before I flashed any ROM, did a Nandroid Backup through CWM.
Used the ROM for a few days, but when I saw that official update is ready for download for i9020A, did do a restore from the Nandroid backup I created.
Updated from 2.3.3 to 2.3.4, phone works fantastic, video chat also works great.
After update when I tried using any of the apps required SU permission, they didn't work. I tried installing a couple of .apk files, couldn't either install it or after installation it didn't work.
Thought let me try wiping my phone clean and start all over again, may be I will use a custom ROM again, downloaded ROM, went to ROM Manager to reboot into recovery, nothing happens.
Tried booting into Recovery option manually by pressing Volume Up and Power button, nothing happens but the Bot with an Arrow appears on screen.
So, I thought I will follow this procedure to reflash CWM to my phone and get it going. I was able to use the command FastBoot once, and suceeded pushing .img file to my phone but now whenever I try using the commands from my computer, this error message appears : "This application has failed to start becasue AdbWinApi.dll was not found. Re-installing the application may fix this problem."
Why this error message if I have the sdk on my computer already through which I was once able to push .img file without any troubles?
Can anyone tell me what would be a possible solution?
Also, how can I fix this problem and get ClockWorkMod Recovery installed on my NS again?
How can I get stock recovery image on my phone if I want start all over again from scratch?
Thx a million.
Edit ::: I found the answer as to how to how to install CWM again. Thx anyways.
Other question still remains a puzzle... why am I not able to install certain programs or if did manage to install, can't run them?

I ran your method and I think I'm stuck at some step...
My phone now default boots into CWM 3.0.2.4
Recovery boots to a newer recovery I flashed.
How do I get my phone to default boot into the OS again?
Edit: nevermind, just downloaded the full 2.3.4 rom, extracted and flashed the original boot.img.

dreamsforgotten said:
All the right drivers are in the sdk.
Click to expand...
Click to collapse
After installing the sdk and a platform, I have adb, but where is fastboot?

I was getting the same error as "Image cant be loaded". after hours of struggling I found that It's only because I was not in the same directory as the img file. silly eh?

hi,did you repaiar your phone,i have try everything but it just keep going in clockwork mode,if i than pres reboot now in clockworkmode it stays on google padlock
i realy need phone if you can help or someone else,than ....

just tried this method of window7 (thanks for the work) with cwm 3.0.2.4, but got the same result like the others in this thread: cant boot the android 2.3.4, the system is always booting into the cwm, no way out.
I don't think this tool works as it should.
:-(
EDIT:
I didn't realize that window7's tool would install the cwm into the boot-partition instead of the recovery-partition.
To get my boot partition back I downloaded the 2.3.4 firmware image from http://forum.xda-developers.com/showthread.php?t=1056062 and extracted the boot.img from the zip.
with "fastboot flash boot boot.img" I restored my orginal boot partition an can boot into android again.
(fastboot is part of the android sdk)

DEsire Z/G2 added to official bootloader unlock program

Didn't see this in General so thought it would be worth adding, especially since there have been many threads lately with new users wanting to root their phone and then getting scared of the guides.
Now there is also the option to go the official way to unlock the bootloader.
http://htcdev.com/bootloader/

noob here with a question... rooting is the same as unlocked bootloader??

coldsun15 said:
noob here with a question... rooting is the same as unlocked bootloader??
Click to expand...
Click to collapse
Not quite. It can probably explained more accurately but the gist of it is this:
An unlocked bootloader is what allows you to flash custom roms to your phone.
Root access simply grants you the rights to mess with your phones rom whichever way you want.

thomas_wlc said:
Not quite. It can probably explained more accurately but the gist of it is this:
An unlocked bootloader is what allows you to flash custom roms to your phone.
Root access simply grants you the rights to mess with your phones rom whichever way you want.
Click to expand...
Click to collapse
so, basically whats this means is, now i dont need to root and s-off and stuff to be able to put CM7 (for example)?

coldsun15 said:
so, basically whats this means is, now i dont need to root and s-off and stuff to be able to put CM7 (for example)?
Click to expand...
Click to collapse
I thinks that's pretty much it, once you have unlocked your bootloader you'll be able to flash any custom rom you like. Though it'll probably a bit tricky on the first go since you don't have a custom recovery yet, so I believe you'd have to flash some pc10img.
Still it's commonly to believed to be the better choice to stick with the more exhausting solutions posted around here, since HTC will register your phone if you use their tool. At least for the time being they claim that by using their way, your warranty will be void.

I've unlocked my desire z through the htcdev.com website.
Bootloader is unlocked, S-on..
But I can't get a rom installed, it gave me an error while trying to update from the recovery mode (apply update zip) using a stock rom with root.
Akward..
So now I've unlocked my bootloader, but still can't change my rom..
Anyone know how to do it after you've unlocked the bootloader?

flash custom recovery first, from there flash the rom

if you're s-on, bootloader is still locked....

artov said:
flash custom recovery first, from there flash the rom
Click to expand...
Click to collapse
I'm working on it
Gaining temp root using this guide worked.
http://forum.xda-developers.com/showthread.php?t=1178912
But when I press start clockwordmod, it says that my phone is not rooted..
While I press "flashcockwork" clockword mod recovery, I get an error.
än error occurred while attempting to run privileged commands!
I'm doing something wrong..
pretty annoying

I get unlock my bootloader today, and YES there is S-ON, but on the top is written in hboot menu big letters UNLOCKED (How you thinks, htcdev joke?).
I've installed clockworkmod using fastboot:
Code:
fastboot flash recovery clockwork_mod_for_vision.img
Then put off battery and turn on phone with volume down + power, I pressed 'recovery' menu option. Clockworkmod runs correctly. Then tried last stable CyanogenMod 7.1.0, flash was done without errors, I wiped out what's need (cache, data). Next I tried run phone, but freezes at splash (green htc letters on white background).
I tried also miui mod, but Ive got only MIUI splash screen nothing else.
Then I restored my htc from backup (done before flashing using clockworkmod) and Im still on the stock htc android 2.3.3.
Regards,
Mariusz
p.s Sorry for my poor english.

how can I install CM7 or other roms after unlocking the bootloader
Hi,
I also unlocked using the official method of unlocking the bootloader. How can I get root and install CM7 now? Even to install clockwordmod its asking me root the phone.
Can someone help me out here?
Thanks...
RSK

rskainth82 said:
Hi,
I also unlocked using the official method of unlocking the bootloader. How can I get root and install CM7 now? Even to install clockwordmod its asking me root the phone.
Can someone help me out here?
Thanks...
RSK
Click to expand...
Click to collapse
1. boot to fastboot mode, flash a custom recovery (recommand ClockWorkMod), power down the phone.
2. put your downloaded update_cm7.xxx.zip into sdcard, boot phone into recovery
3. choose in the recovery, first "wipe data", then "install update from sdcard", choose the zip file you just put in.
4. choose "reboot system"
that's all to go.

pentie said:
1. boot to fastboot mode, flash a custom recovery (recommand ClockWorkMod), power down the phone.
2. put your downloaded update_cm7.xxx.zip into sdcard, boot phone into recovery
3. choose in the recovery, first "wipe data", then "install update from sdcard", choose the zip file you just put in.
4. choose "reboot system"
that's all to go.
Click to expand...
Click to collapse
I did it, but CM7 doesnt boot.

rskainth82 said:
Hi,
I also unlocked using the official method of unlocking the bootloader. How can I get root and install CM7 now? Even to install clockwordmod its asking me root the phone.
Can someone help me out here?
Thanks...
RSK
Click to expand...
Click to collapse
flak999 said:
I did it, but CM7 doesnt boot.
Click to expand...
Click to collapse
Booting problem is mostly kernel related, do you have logcat output? (run "adb logcat" and boot the phone)
I encountered with the situation (w. another phone) that the recovery can't flush the boot partition during the recovery installation, I have to extract the boot.img file from the zip and flash it manually in the fastboot mode (fastboot flash boot boot.img)
EDIT:
That was a EVO3D with UNLOCKED HBOOT, I believe you're having the same situation, try my method or may others make out a better perfect solution ? (not my own phone, I just helped with its owner, no time to dig the details)

pentie said:
I encountered with the situation (w. another phone) that the recovery can't flush the boot partition during the recovery installation, I have to extract the boot.img file from the zip and flash it manually in the fastboot mode (fastboot flash boot boot.img)
EDIT:
That was a EVO3D with UNLOCKED HBOOT, I believe you're having the same situation, try my method or may others make out a better perfect solution ? (not my own phone, I just helped with its owner, no time to dig the details)
Click to expand...
Click to collapse
Thanks men thats worked for me. First flash the boot.img from CM7.0.1 then run recovery and run update_cm7.0.1.zip. After reboot everything run corectly.
Once more thanks!

flak999 said:
Thanks men thats worked for me. First flash the boot.img from CM7.0.1 then run recovery and run update_cm7.0.1.zip. After reboot everything run corectly.
Once more thanks!
Click to expand...
Click to collapse
now I confirmed the UNBLOCKED HBOOT somehow blocks the CWM to flash boot.img
My Phone have a S-OFF HBOOT and i was considering flash it to the UNLOCK the last night, now it seems not worth the try ~

pentie said:
I encountered with the situation (w. another phone) that the recovery can't flush the boot partition during the recovery installation, I have to extract the boot.img file from the zip and flash it manually in the fastboot mode (fastboot flash boot boot.img)
Click to expand...
Click to collapse
My friend has an officially unlocked Desire Z as well and I gave him these instructions to try it out, he has the same boot problem (stuck at splash screen). Maybe this information should either be stickied or added to a faq until there is a real solution to the problem (unlike this workaround), updated cwm or something like that.
Anyway thanks for sharing this information.

HTC bootloader unlock tool is quite restrictive. It still leaves you S-ON, so you won't be able to flash a new hboot or radios.
I recommend avoiding it and using the current well-proven methods from the XDA Wiki.
Sent from my Desire Z running CM7.

Its working now...
Steps I followed:
1. flash recovery using fastboot
2. Do a nandroid backup using recovery
3. flash boot.img using fastboot
4. reboot into recovery
5. wipe data/cache
5. install update for CM7, and gapps
Also make sure before doing any of these steps you have copied CM7 and gapps update onto sdcard.
Thanks everyone for helping out.

I am experimenting with this myself and I don't seem to be having the same issues flashing a boot.img from an update.zip in ClockworkMod recovery with the official HTC unlocked bootloader that others are having. Maybe it is the version of the recovery that is the issue? Which version is everyone trying to use? I am using the 3.xxxx version that is linked from the wiki. I have had other problems with the 5.xxx version and tend to stick with the older version for that reason anyways.

[guide] root nexus 4 (4.3) +install custom recovery

hello guys this guide helps you to root your nexus 4 (4.3) and install custom recovery
things needed
1)superuser http://d-h.st/Hhw
2)twrp http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.6.0.0-mako.img
3)andriod sdk (google it)
* [dont have sdk? then download this http://d-h.st/jCU a replacement for sdk/platformtools (this tools include stuff for windows,linux and mac too.)]
4)adb drivers installed (follow the below mentioned guide)
note:- this is almost same process as this guide http://forum.xda-developers.com/showthread.php?t=2018179 but just updated for 4.3 version
ROOTING process
1)I hope your boot loader is unlocked, if not first unlock it and then start the rooting process and turn on usb debugging (follow above mentioned guide for unlocking bootloader and to turn on usb debugging) after unlocking bootloader reboot device and then copy root.zip(links above) into your phones storage and then reboot to fastboot
2)now download the twrp recovery image and rename it to twrp and move it to sdk/platform tools. in the same directory(i.e platformtools directory) open cmd prompt(to open cmd prompt press shift+rightclick at the same time and select open cmd prmpt window option) and type (without quotes) "fastboot flash recovery twrp.img" and thats it you have flashed twrp
3)now go to twrp (recovery mode) and flash the root.zip (that u copied to the phones storage earlier) and that's it u have obtained the root access.
im not responsible if u bricked your device do it at your own risk
follow this wonderful video if u have any problem or trouble http://www.youtube.com/watch?v=jn5ih0omlxI
hit thanks button if this thread helped ya

There is new SuperSU v1.51:
http://forum.xda-developers.com/showthread.php?t=1538053
Your uploaded SuperSU is still v1.44.

thank you
gogol said:
There is new SuperSU v1.51:
http://forum.xda-developers.com/showthread.php?t=1538053
Your uploaded SuperSU is still v1.44.
Click to expand...
Click to collapse
Thank you I will update that!

thank you
gogol said:
There is new SuperSU v1.51:
http://forum.xda-developers.com/showthread.php?t=1538053
Your uploaded SuperSU is still v1.44.
Click to expand...
Click to collapse
BTW you can update that manually via WiFi from playstore as chainfire mentioned in the thread that "if u already have root root access then update it from playstore"

Except the bug fixed version of supersu, there's nothing different from the original thread...
*****Save your fingers the work and hit "Thanks" instead of typing it...!!*****
NEXUS⁴ Stock Android 4.3
---------- Post added at 12:40 AM ---------- Previous post was at 12:39 AM ----------
gogol said:
There is new SuperSU v1.51:
http://forum.xda-developers.com/showthread.php?t=1538053
Your uploaded SuperSU is still v1.44.
Click to expand...
Click to collapse
The latest su version is not compatible with 4.3 yet...only v1.43 is compatible presently...
*****Save your fingers the work and hit "Thanks" instead of typing it...!!*****
NEXUS⁴ Stock Android 4.3

when i enter the command line the command window gets stuck at <waiting for device> ........ I made sure that i have the drivers are properly configured and the nexus unlocked ...... any ideas why this happens ??

M.Zaki said:
when i enter the command line the command window gets stuck at <waiting for device> ........ I made sure that i have the drivers are properly configured and the nexus unlocked ...... any ideas why this happens ??
Click to expand...
Click to collapse
Hi,
I can suggest you some thing but i am not responsible if u bricked your device do it at your own risk
I had same issue " waiting for device" SO you need to install correct drivers for your device i can suggest you to download nexus 4 toolkit version 2 from here http://forum.xda-developers.com/showthread.php?t=1995688 and you need disconnect your nexus from usb and open your toolkit and you need :
1.choose option 13 "13. Android 4.2.2 [Build JDQ39]" (I know that your version is 4.3 but the drivers for PC is samething)
2.It will download drivers for your pc
3.Now choose option 1 that say " 1. Install Device Drivers on your PC [DO THIS FIRST] [UnPlug Device First] "
4. After driver installation you can close this tool and try again to flash your recovery like you did it before with (See above "ROOTING process")
Let me know if you succeed
Good luck

When I try to load the YT vid it says "invalid request"...
Oh its more than a vid. I am sorry in the android app it doesnt show the whole post for any reason.
And why download the whole sdk? Grab the platform tools from efrant's tutorial on how to flash a factory image. Then just place the desired recovery in the same directory and you can flash the recovery.
Sent from my Nexus 4 using xda app-developers app

amnon.m said:
Hi,
I can suggest you some thing but i am not responsible if u bricked your device do it at your own risk
I had same issue " waiting for device" SO you need to install correct drivers for your device i can suggest you to download nexus 4 toolkit version 2 from here http://forum.xda-developers.com/showthread.php?t=1995688 and you need disconnect your nexus from usb and open your toolkit and you need :
1.choose option 13 "13. Android 4.2.2 [Build JDQ39]" (I know that your version is 4.3 but the drivers for PC is samething)
2.It will download drivers for your pc
3.Now choose option 1 that say " 1. Install Device Drivers on your PC [DO THIS FIRST] [UnPlug Device First] "
4. After driver installation you can close this tool and try again to flash your recovery like you did it before with (See above "ROOTING process")
Let me know if you succeed
Good luck
Click to expand...
Click to collapse
I succeeded but I don't know exactly what I did to make it work ....... I got bored after posting my question when I returned I tried it again without looking to the thread and it worked ..... but thnx for your concern

M.Zaki said:
I succeeded but I don't know exactly what I did to make it work ....... I got bored after posting my question when I returned I tried it again without looking to the thread and it worked ..... but thnx for your concern
Click to expand...
Click to collapse
I am very happy

M.Zaki said:
I succeeded but I don't know exactly what I did to make it work ....... I got bored after posting my question when I returned I tried it again without looking to the thread and it worked ..... but thnx for your concern
Click to expand...
Click to collapse
so it might not have recognized your adb drivers at the first time.or you could have just downloaded the nexus4toolkit by mrskip and installed adb from it. anyways did u root it?

Thibaultvw said:
When I try to load the YT vid it says "invalid request"...
Oh its more than a vid. I am sorry in the android app it doesnt show the whole post for any reason.
And why download the whole sdk? Grab the platform tools from efrant's tutorial on how to flash a factory image. Then just place the desired recovery in the same directory and you can flash the recovery.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
now try the link i fixed it

punitthereddevil said:
Except the bug fixed version of supersu, there's nothing different from the original thread...
*****Save your fingers the work and hit "Thanks" instead of typing it...!!*****
NEXUS⁴ Stock Android 4.3
---------- Post added at 12:40 AM ---------- Previous post was at 12:39 AM ----------
The latest su version is not compatible with 4.3 yet...only v1.43 is compatible presently...
*****Save your fingers the work and hit "Thanks" instead of typing it...!!*****
NEXUS⁴ Stock Android 4.3
Click to expand...
Click to collapse
as i mentioned in the thread "this is the similar guide as that is mentioned above just updated for 4.3 version"

Just one question do the recovery flashed this way stick after reboot even on stock ROM? I remember something about having yo flash an additional ZIP for that...
Sent from my Nexus 4 using Tapatalk 4 Beta

Hi guys,
I know this topic is about installing custom recovery, but does anybody knows hot to root android 4.3 without flashing custom recovery? Yesterday I tried to boot both CWM and TWRP using:
Code:
fastboot boot recovery.img
All I got was a blank screen...

bartiki said:
Hi guys,
I know this topic is about installing custom recovery, but does anybody knows hot to root android 4.3 without flashing custom recovery? Yesterday I tried to boot both CWM and TWRP using:
Code:
fastboot boot recovery.img
All I got was a blank screen...
Click to expand...
Click to collapse
i have the same problem with "fastboot boot xxxx.img"!! both CWM and TWRP , return blank!

I actually found this today:
http://forum.xda-developers.com/showthread.php?t=2380675
they say:
the new version of bootloader shipped with Android 4.3 factory image changed some of the "fastboot boot" command so you need to specify a kernel commandline to use "fastboot boot" command.
Click to expand...
Click to collapse
for Nexus 4, it's:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
although I don't have time to test it out right now

bartiki said:
I actually found this today:
http://forum.xda-developers.com/showthread.php?t=2380675
they say:
for Nexus 4, it's:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
although I don't have time to test it out right now
Click to expand...
Click to collapse
yes.. now i find this me too and work!!!
i install the SuperSU , but now do n't installing the binary file. stuck on "installing, please wait..." any ideas?
EDIT: uninstall the update of SuperSU (v.1.51) and return to stock (that flashed before v1.43) AND WORKING!! ( no prompt to update the binary file..) any ideas? the v.1.51 maybe not working??

bbsnick said:
yes.. now i find this me too and work!!!
i install the SuperSU , but now do n't installing the binary file. stuck on "installing, please wait..." any ideas?
EDIT: uninstall the update of SuperSU (v.1.51) and return to stock (that flashed before v1.43) AND WORKING!! ( no prompt to update the binary file..) any ideas? the v.1.51 maybe not working??
Click to expand...
Click to collapse
Somebody mentioned this on first page newest su not compatible only v1.43
Sent from my Nexus 4 using Tapatalk 4 Beta

boysetsfire said:
Just one question do the recovery flashed this way stick after reboot even on stock ROM? I remember something about having yo flash an additional ZIP for that...
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yep it still works after reboot . no problem with that

Root stock 5.1 - Ub only

I'm no expert, so maybe a better way, but it worked for me, so try if you want...
Needed: stock ftf, (I used this https://shry.me/9L9OQ); CM boot img; TWRP img; Flashtool; fastboot, Supersu flashable zip.
1. Flash stock ftf with Flashtool, boot phone, and check 'android debugging ' and 'unknown sources'
2. Power off, hold volume up, and connect in fastboot mode
3. cd to adb directory on PC, type 'fastboot flash boot (CM file).img', and 'fastboot flash recovery (TWRP file).img'
4. disconnect phone, power on, volume up when you see led to enter recovery. Install > Supersu zip.
5. Power off, open Flashtool, and again flash ftf, but in 'exclude' box on right side, check everything except 'boot bundle, kernel, and fotakernel. (hopefully I'm remembering right).
When done, reboot, and you're rooted.

@levone1 link isn't working! pls fix.

itskapil said:
@levone1 link isn't working! pls fix.
Click to expand...
Click to collapse
Sorry, the parentheses got included in link. It's better now. By the way, I got it from here http://forum.xda-developers.com/son...al/ftf-xperia-z1-compact-d5503-5-1-1-t3201650.
Also, here's a couple more links to make it easier...
https://mega.nz/#!E4UQwIoZ!UFpur2wY3tIAU7SdjuEg5fUA6N4BAVwX_TeK_CFpTyo
https://mega.nz/#!k5E0kQpC!XdTudAe5ISAVyfQAHHMkgvjmNuY6TDxm62HzyOAEgmU
I'll post a CM boot link later if needed, or just download one.

http://forum.xda-developers.com/son...root-init-d-support-recovery-busybox-t3202799 is a nice addition to this method, (to get recovery and busybox after root). You can flash it with Rashr app on phone with root, (version 2.2.8).

levone1 said:
I'm no expert, so maybe a better way, but it worked for me, so try if you want...
Needed: stock ftf, (I used this https://shry.me/9L9OQ); CM boot img; TWRP img; Flashtool; fastboot, Supersu flashable zip.
1. Flash stock ftf with Flashtool, boot phone, and check 'android debugging ' and 'unknown sources'
2. Power off, hold volume up, and connect in fastboot mode
3. cd to adb directory on PC, type 'fastboot flash boot (CM file).img', and 'fastboot flash recovery (TWRP file).img'
4. disconnect phone, power on, volume up when you see led to enter recovery. Install > Supersu zip.
5. Power off, open Flashtool, and again flash ftf, but in 'exclude' box on right side, check everything except 'boot bundle, kernel, and fotakernel. (hopefully I'm remembering right).
When done, reboot, and you're rooted.
Click to expand...
Click to collapse
Links to these files?

NRG1975 said:
Links to these files?
Click to expand...
Click to collapse
3rd post has everything but CM boot. I'll post it if you need it. Or you could just download a ROM and extract.

NRG1975 said:
Links to these files?
Click to expand...
Click to collapse
This should work for boot IMG - https://mega.nz/#!Jh0DETBQ!E-9WTlINpfq5r3PIiKaIXRId7ar8g3c8YHTJha1N6LM

This really is not that easy .... While it may be the easiest way, it is far from easy with Win 8 or Win 10. I am gonna forego root till an easier way is found. Thank you for your efforts.

No Busybox
I was able to root my phone following your method. It was easy.. however I can't install busybox or use apps which requires busybox installation. Is there any workaround for this issue?!

aravindclpy said:
I was able to root my phone following your method. It was easy.. however I can't install busybox or use apps which requires busybox installation. Is there any workaround for this issue?!
Click to expand...
Click to collapse
Use stericson busybox from play store. I tried the other one and it didn't work, but that one worked for me. You can also manual push busybox if you have to.

aravindclpy said:
I was able to root my phone following your method. It was easy.. however I can't install busybox or use apps which requires busybox installation. Is there any workaround for this issue?!
Click to expand...
Click to collapse
You can also use this - http://forum.xda-developers.com/son...root-init-d-support-recovery-busybox-t3202799
Since this came out, I recommend it over my method, since everything is included, and it's faster than using FT a second time.

Hey,
Usually this kind of stuff isn't a problem for me, but here I'm stuck at step 4.
When I try to flash superSU.zip, TWRP reboots by itself.
Also when TWRP boots, I'm asked to choose "keep read only" or "allow modifications" for the system partition. Both choices results in a reboot of TWRP.
Any idea ?
(I tried with the method in the link above, same thing happens)

Jackhass said:
Hey,
Usually this kind of stuff isn't a problem for me, but here I'm stuck at step 4.
When I try to flash superSU.zip, TWRP reboots by itself.
Also when TWRP boots, I'm asked to choose "keep read only" or "allow modifications" for the system partition. Both choices results in a reboot of TWRP.
Any idea ?
(I tried with the method in the link above, same thing happens)
Click to expand...
Click to collapse
Only time I ever got that from twrp was after doing ta update and booting into the new recovery. I just picked 'allow' and everything was fine. Are you booting into recovery the new way, or old? Are you using all of the files I posted, or a different boot, etc? My first shot would be to try a different recovery IMG, like an older twrp,and see if it works. I did all the above with the old recovery method, (wait for LED and vol up). Let me know...

@levone1 Thanks for your answer
I redownloaded all your files, did it again (exactly as it's said in the OP) and... it worked. I've done nothing more or less than last time I tried.. Unexplainable
Thanks anyway

Jackhass said:
@levone1 Thanks for your answer
I redownloaded all your files, did it again (exactly as it's said in the OP) and... it worked. I've done nothing more or less than last time I tried.. Unexplainable
Thanks anyway
Click to expand...
Click to collapse
Great... If you want busybox, etc., see the posts before yours.

Update (.216)
Just bumping thread for new fw. After FT flash, there is no r/w access. Can't use method in this forum without busybox, so to get busybox, just download nut dual recovery 'installer' option, and run on pc. Steps are same otherwise. I posted an ftf here - http://forum.xda-developers.com/sony-xperia-z1-compact/general/216-stock-ftf-read-flashing-t3243728

levone1 said:
Just bumping thread for new fw. After FT flash, there is no r/w access.
Click to expand...
Click to collapse
The steps I took with UL BL...
Used the Flashtool and XperiFirm to download and flash 216.
Hot booted 368 kernel and flashed SU zip, confirmed root with TB and Root Explorer after reboot to stock 216 kernel.
Installed Busybox from Play Store.
Extracted kernel.sin from ftf and used @[NUT]'s Kernel Builder to add XZDualRecovery.
Extracted boot.img from zip and flashed with Fastboot.
Now I'm in the process of removing bloatware then I'm going to theme it.

Can someone please create a thourough start to finish guide on converting, rooting

Can someone please create a thourough start to finish guide on converting, rooting, recovery, and rom installations?
listen im no noob but im no mater either ive been rooting since the original TMO G1 and it has gotten very complex on top of that ive missed alot since i got my note 4 retail (out of the game) anyways someeone please compile a step by step list of what to do and where to find the neccasary files. and in what order.
please and thank you

For BL unlocking follow this
For rooting
If staying on stock:
Boot into download mode (VOL-DOWN + HOME + POWER) and flash twrp-3.0.2-0-trltevzw via ODIN (MAKE SURE YOU UNCHECK AUTO-REBOOT!!!).
Battery pull phone and then boot straight into recovery (VOL-UP + HOME + POWER) to finish the recovery install process or else it will install the default android recovery.
Then flash the Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P kernal via recovery.
Then flash the BETA-SuperSU-v2.71-20160331103524 via recovery.
Reboot.
If going to a different rom, you should just be able to flash the rom via recovery and get right in. But results may very, check the forums.

refusedchaos said:
For BL unlocking follow this
For rooting
If staying on stock:
Boot into download mode (VOL-DOWN + HOME + POWER) and flash twrp-3.0.2-0-trltevzw via ODIN (MAKE SURE YOU UNCHECK AUTO-REBOOT!!!).
Battery pull phone and then boot straight into recovery (VOL-UP + HOME + POWER) to finish the recovery install process or else it will install the default android recovery.
Then flash the Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P kernal via recovery.
Then flash the BETA-SuperSU-v2.71-20160331103524 via recovery.
Reboot.
If going to a different rom, you should just be able to flash the rom via recovery and get right in. But results may very, check the forums.
Click to expand...
Click to collapse
thank you very much i was a little frustratrated because it seems like the info is very fragmented

Can someone please tell me where I have gone wrong.
I have gotten temproot via kingroot installed and was able to get the unlocker to run and I can see that the device is now a developer device. I am trying to get root to work but not having any luck.
I follwed the instructions at http://forum.xda-developers.com/note-4-verizon/general/guide-noobs-guide-to-perm-root-twrp-t3360883 and had problems in step 8 when trying to run super-sume. I ran it successfully for stage 1 but then it hung when trying to run stage 2. However, I was able to move on to step 9 and install TWRP and the emotion kernel. I have done a full reset and tried a 2nd time but still no luck in getting permament root access.
Root checker shows no root access and superSU is installed but shows no su binary installed.
If I run SuperSUME-Pro then it shows the device is wrte=protected
It seems I can run kingroot again to gain temp root access but not perm root access.
Any ideas on how to proceed from here?

mlcampbe said:
Can someone please tell me where I have gone wrong.
I have gotten temproot via kingroot installed and was able to get the unlocker to run and I can see that the device is now a developer device. I am trying to get root to work but not having any luck.
I follwed the instructions at http://forum.xda-developers.com/note-4-verizon/general/guide-noobs-guide-to-perm-root-twrp-t3360883 and had problems in step 8 when trying to run super-sume. I ran it successfully for stage 1 but then it hung when trying to run stage 2. However, I was able to move on to step 9 and install TWRP and the emotion kernel. I have done a full reset and tried a 2nd time but still no luck in getting permament root access.
Root checker shows no root access and superSU is installed but shows no su binary installed.
If I run SuperSUME-Pro then it shows the device is wrte=protected
It seems I can run kingroot again to gain temp root access but not perm root access.
Any ideas on how to proceed from here?
Click to expand...
Click to collapse
Install SuperSU from TWRP. Does that work?

If you Developer mode and twrp but no root, then what you need to do is install emotional kernel from twrp and reboot device then boot back into twrp and install SuperSU zip and reboot device you should be fine.

After re-checking my recovery I do not believe that I have TWRP installed after all. I was booting into android recovery and it hit me I was not seeing what I expected to see. I need to work on getting TWRP installed. I do indeed have the custom kernel and developer mode enabled!!

refusedchaos said:
For BL unlocking follow this
For rooting
If staying on stock:
Boot into download mode (VOL-DOWN + HOME + POWER) and flash twrp-3.0.2-0-trltevzw via ODIN (MAKE SURE YOU UNCHECK AUTO-REBOOT!!!).
Battery pull phone and then boot straight into recovery (VOL-UP + HOME + POWER) to finish the recovery install process or else it will install the default android recovery.
Then flash the Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P kernal via recovery.
Then flash the BETA-SuperSU-v2.71-20160331103524 via recovery.
Reboot.
If going to a different rom, you should just be able to flash the rom via recovery and get right in. But results may very, check the forums.
Click to expand...
Click to collapse
So what you posted above is all that you need to do for root? You definitely have a much more concise explanation than the main thread. The other instructions made me feel like I was back on my old Droid 2 working from the giant tutorial threads over on rootzwiki, hah.
I'm also guessing that as you mentioned elsewhere that if we wish to run a custom ROM we'll have to reflash the stock kernel before doing so?

Does it matter whether or not its 4.4.4 or 5.1.1
refusedchaos said:
For BL unlocking follow this
For rooting
If staying on stock:
Boot into download mode (VOL-DOWN + HOME + POWER) and flash twrp-3.0.2-0-trltevzw via ODIN (MAKE SURE YOU UNCHECK AUTO-REBOOT!!!).
Battery pull phone and then boot straight into recovery (VOL-UP + HOME + POWER) to finish the recovery install process or else it will install the default android recovery.
Then flash the Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P kernal via recovery.
Then flash the BETA-SuperSU-v2.71-20160331103524 via recovery.
Reboot.
If going to a different rom, you should just be able to flash the rom via recovery and get right in. But results may very, check the forums.
Click to expand...
Click to collapse
Does it matter whether or not its 4.4.4 or 5.1.1

ttall8ball said:
Does it matter whether or not its 4.4.4 or 5.1.1
Click to expand...
Click to collapse
If you're wanting to unlock the bootloader, root and install TWRP then no it doesn't matter. Now if you want to install a custom ROM that is 5.1.1 then you WILL have to be on that firmware if you are currently on 4.4.4
If anyone helps, plz give thanks?
N910V ? BL / KYUBI ROM

MissionImprobable said:
So what you posted above is all that you need to do for root? You definitely have a much more concise explanation than the main thread. The other instructions made me feel like I was back on my old Droid 2 working from the giant tutorial threads over on rootzwiki, hah.
I'm also guessing that as you mentioned elsewhere that if we wish to run a custom ROM we'll have to reflash the stock kernel before doing so?
Click to expand...
Click to collapse
The instructions for rooting suggest installing the Emotion kernel first.
Many of the ROMs available to flash will suggest which kernel to use. You can go directly to that kernel.

I need a little info, my note I just got is already rooted. So I didn't have the joy to do it. A co worker just picked up a refurbished and it has 5.0.1 ., is the 2bog5 able to be rooted?

bingo6104 said:
I need a little info, my note I just got is already rooted. So I didn't have the joy to do it. A co worker just picked up a refurbished and it has 5.0.1 ., is the 2bog5 able to be rooted?
Click to expand...
Click to collapse
Yes it can. But I am pretty sure that you must unlock the bootloader first unless you already have a DevEd.
If anyone helps, plz give thanks?
N910V ? BL / KYUBI ROM

stajam said:
Yes it can. But I am pretty sure that you must unlock the bootloader first unless you already have a DevEd.
If anyone helps, plz give thanks?
N910V ? BL / KYUBI ROM
Click to expand...
Click to collapse
Thanks, I thought that from what I have been reading. To many guides, need to be complied into 2 guides and sticky on the forum for rusty people like me lol
Sent from my SM-N920V using Tapatalk

No problem bruh.
If anyone helps, plz give thanks?
N910V ? BL / KYUBI ROM

ttall8ball said:
Does it matter whether or not its 4.4.4 or 5.1.1
Click to expand...
Click to collapse
Thanks, I got it done
---------- Post added at 08:52 AM ---------- Previous post was at 08:49 AM ----------
stajam said:
If you're wanting to unlock the bootloader, root and install TWRP then no it doesn't matter. Now if you want to install a custom ROM that is 5.1.1 then you WILL have to be on that firmware if you are currently on 4.4.4
If anyone helps, plz give thanks?
N910V ? BL / KYUBI ROM
Click to expand...
Click to collapse
Thanks stajam, I got it done last night.

ttall8ball said:
Thanks, I got it done
---------- Post added at 08:52 AM ---------- Previous post was at 08:49 AM ----------
Thanks stajam, I got it done last night.
Click to expand...
Click to collapse
Good to hear glad you got it going. ?
If anyone helps, plz give thanks?
N910V ? BL / KYUBI ROM

refusedchaos said:
For BL unlocking follow this
For rooting
If staying on stock:
Boot into download mode (VOL-DOWN + HOME + POWER) and flash twrp-3.0.2-0-trltevzw via ODIN (MAKE SURE YOU UNCHECK AUTO-REBOOT!!!).
Battery pull phone and then boot straight into recovery (VOL-UP + HOME + POWER) to finish the recovery install process or else it will install the default android recovery.
Then flash the Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P kernal via recovery.
Then flash the BETA-SuperSU-v2.71-20160331103524 via recovery.
Reboot.
If going to a different rom, you should just be able to flash the rom via recovery and get right in. But results may very, check the forums.
Click to expand...
Click to collapse
can u get a new link to the twrp to flash..I just want root is all...I've download several twrp with same numbers but no luck flashing
thanks so much
Sent from my SM-N910V using XDA-Developers mobile app