Database Users

[Q] I have S=OFF But I cant get SU to grant permissions?

What gives?
Example, i rooted, and booted up, then i go into ROM Manager and thry to flash recovery and upon entering RM it says cant find SU and I need to root?
SU doesnt give permissions on Terminal Emulator..

CoNsPiRiSiZe said:
What gives?
Example, i rooted, and booted up, then i go into ROM Manager and thry to flash recovery and upon entering RM it says cant find SU and I need to root?
SU doesnt give permissions on Terminal Emulator..
Click to expand...
Click to collapse
Power off the device. Once its completely off, hold volume down ans the power button. Once you enter hboot, look all the way on the top. It should say s off.
Sent from my HTC Glacier using xda premium

CoNsPiRiSiZe said:
What gives?
Example, i rooted, and booted up, then i go into ROM Manager and thry to flash recovery and upon entering RM it says cant find SU and I need to root?
SU doesnt give permissions on Terminal Emulator..
Click to expand...
Click to collapse
do you get superuser access when you type "su" in terminal emulator or adb?

Were all good. I got it working, I'm running RoyalGinger 3.0 at the moment because I like AOSP, will switch to unity this weekend when I have time to customize and plat with it
Sent from my HTC Glacier using xda premium

Fastboot command flashing recovery SOLVED

Hi guys,
Got my Nexus 4 today and want to root it, allready unlocked it but can get the recovery to get flashed. On earlier Nexuses i recall placing the recovery.img in android-sdk/platform-tools and in fastboot the command fastboot flash recovery recovery.img would do the job. But now it isn`t, what an i doing wrong? Fastboot drivers are properly installed as i was able to unlock the phone with adb.
Would appreciate some helpfull tips.

did you rename it recovery.img?
Sent from my Nexus 4 using xda premium

Does it return an error or is it just not sticking?

El Daddy said:
Does it return an error or is it just not sticking?
Click to expand...
Click to collapse
Yes i named it recovery.img and it doesn`t seem to find to file, no other messages like misstakes/fc.

gee2012 said:
Yes i named it recovery.img and it doesn`t seem to find to file, no other messages like misstakes/fc.
Click to expand...
Click to collapse
Why not just use the toolkit...makes it 1000000000 times easier...

gee2012 said:
Yes i named it recovery.img and it doesn`t seem to find to file, no other messages like misstakes/fc.
Click to expand...
Click to collapse
This may be a silly suggestion but windows auto names the extension. So really you just have to name the file "recovery"

zbt1985 said:
Why not just use the toolkit...makes it 1000000000 times easier...
Click to expand...
Click to collapse
That`s true, but i would like to be able do it with adb also.

El Daddy said:
This may be a silly suggestion but windows auto names the extension. So really you just have to name the file "recovery"
Click to expand...
Click to collapse
Will try that bro, thanks

zbt1985 said:
Why not just use the toolkit...makes it 1000000000 times easier...
Click to expand...
Click to collapse
Because he won't be the one to come crying when he "bricks" his phone...
And he'll be learning.
And cutting out the middle man...
All the toolkit is is a GUI interface for fastboot commands.
One wrong line on the developer's side could literally brick devices (yes, unlikely).
Why don't YOU stop relying on toolkits?
ADB and fadtboot are even simpler.

whats the error message

Did you CD into the fastboot folder properly?
Sent from my Nexus 4 using Tapatalk 2

After renaming the recovery the flash succeeded, but when in CWM i cannot see the SU/Busybox zip. Do i need to flash a unsecure boot first?
Sorry for the noobish questions, been with Samsung devices a long time, and they didn`t have fastboot

gee2012 said:
After renaming the recovery the flash succeeded, but when in CWM i cannot see the SU/Busybox zip. Do i need to flash a unsecure boot first?
Sorry for the noobish questions, been with Samsung devices a long time, and they didn`t have fastboot
Click to expand...
Click to collapse
I'm not familiar with how you are rooting, I just flashed everything with fastboot. I assume you flashed recovery and are flashing su in recovery? I do believe you need an insecure boot first.
Sent from my Nexus 4 using Tapatalk 2

joshnichols189 said:
Did you CD into the fastboot folder properly?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Yes i guess so, cd c:\android-sdk\platform-tools , fastboot is located in platform-tools afaik.

gee2012 said:
Yes i guess so, cd c:\android-sdk\platform-tools , fastboot is located in platform-tools afaik.
Click to expand...
Click to collapse
I thought it was in the adb folder?
Forgive me, but I keep a folder called adb on the root of my C: drive with fastboot.exe in it.
Sent from my Nexus 4 using xda app-developers app

Adb is also in platform-tools
Sent from my Nexus 4 using xda premium

Did you place the .zip file on your phone before or after you unlocked the bootloader?
Unlocking the bootloader completely wipes the phone so the file would be gone.
The good news is you can push the file with adb while booted into recovery.
adb push nameoffile.zip /storage/sdcard0
Sent from my Nexus 4

gee2012 said:
After renaming the recovery the flash succeeded, but when in CWM i cannot see the SU/Busybox zip. Do i need to flash a unsecure boot first?
Sorry for the noobish questions, been with Samsung devices a long time, and they didn`t have fastboot
Click to expand...
Click to collapse
make sure you're looking in the correct path in cwm i think its sdcard0 or something like that. or just flash twrp it goes straight to the storage directory by default
Sent from my Nexus 4 using xda premium

The 2 files i see in CWM are not located on sdcard0 but in the emulated file. So how to get in sdcard0 when in CWM, that is the question.
Is this the correct adb command: adb push C:/android-sdk/platform-tools/SU_Busybox_Package sdcard0/SU_Busybox_Package for pushing the file to sdcard0?

gee2012 said:
The 2 files i see in CWM are not located on sdcard0 but in the emulated file. So how to get in sdcard0 when in CWM, that is the question.
Is this the correct adb command: adb push C:/android-sdk/platform-tools/SU_Busybox_Package sdcard0/SU_Busybox_Package for pushing the file to sdcard0?
Click to expand...
Click to collapse
if u can get to them from the emulated irectory , just flash from there. it shouldn't make a difference
Sent from my Nexus 4 using xda premium

[Q] Making backup/dump of Stock Recovery

I'm looking for some instructions on how to make a complete backup/dump of my current Stock Recovery.
I'm running djembey's pre-rooted ROM on an i9505 and everything works fine. Looking to flash a Custom Recovery to continue fiddling around with my device, but I would like to backup my Stock Recovery before proceeding, yes I am aware that there are Stock Recovery images floating around but this is for my own knowledge/reference. Would be great if someone could point me in the right direction!
Cheers.

qkevin. said:
I'm looking for some instructions on how to make a complete backup/dump of my current Stock Recovery.
I'm running djembey's pre-rooted ROM on an i9505 and everything works fine. Looking to flash a Custom Recovery to continue fiddling around with my device, but I would like to backup my Stock Recovery before proceeding, yes I am aware that there are Stock Recovery images floating around but this is for my own knowledge/reference. Would be great if someone could point me in the right direction!
Cheers.
Click to expand...
Click to collapse
Install terminal emulator from play store. Open it and type (enter after each command)
Code:
su
dd if=/dev/block/mmcblk0p21 of=/mnt/sdcard/recovery.img
Sent from my Galaxy Nexus using xda premium

samersh72 said:
Install terminal emulator from play store. Open it and type (enter after each command)
Code:
su
dd if=/dev/block/mmcblk0p21 of=/mnt/sdcard/recovery.img
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Legend! Thank you for the straight forward solution.
EDIT:
If anyone wanted to double check, I believe:
Code:
su
ls -al /dev/block/platform/msm_sdcc.1/by-name/recovery
confirms that the recovery block is indeed mmcblk0p21.

wanna know how-to
samersh72 said:
Install terminal emulator from play store. Open it and type (enter after each command)
Code:
su
dd if=/dev/block/mmcblk0p21 of=/mnt/sdcard/recovery.img
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Could you please tell me how you know that the recovery is in that Block ... ( mmcblk0p21 ) ..

How to flash TWRP using Android terminal emulator

Guys i want to ask how do i flash the recovery.img (TWRP) using Android terminal emulator on Nexus 7 2012 3G 4.3 JWR66Y ?
I tried many ways but did no success,so please help.Thanks.

Ben Ling said:
Guys i want to ask how do i flash the recovery.img (TWRP) using Android terminal emulator on Nexus 7 2012 3G 4.3 JWR66Y ?
I tried many ways but did no success,so please help.Thanks.
Click to expand...
Click to collapse
Hi, Ben Ling...
Using Android Terminal Emulator to flash a Custom Recovery is syntactically complicated, and is prone to typographical errors. You have to type in a long, complicated and potentially error prone command line argument.
First off, you already need to be rooted. If you aren't, then forget it... it simply won't work.
Anyway... here is the command line...
Code:
$ su
# dd if=/sdcard/recovery-image-file.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
Whilst this does work, I think it's significantly easier to just use something like Flash Image GUI or Flashify to flash a Custom Recovery directly from the Nexus 7.
I haven't used the <dd, if, of> syntax via Terminal Emulator for ages... preferring instead to just use Flashify to flash the latest version of TWRP (or for that matter, CWM) on my Nexus 7.
You will of course, already need to be rooted first, as both Flash Image GUI or Flashify, request SU access on first use.
So... if you're looking to flash a Custom Recovery in order to acquire root in the first place... you'll need to do it the old fashioned way first... ie., fastboot flash recovery recovery.img... and then using that Custom Recovery, flash Chainfire's v1.75 SuperSU root .zip..
All of these methods... Using Terminal Emulator, Flash Image GUI or Flashify to install a Custom Recovery, are only useful if you're seeking to UPGRADE to the latest version of TWRP/CWM... as they all assume you're ALREADY have root - and won't work if you aren't.
Hope this helps.
Rgrds,
Ged.

su
flash_image recovery /sdcard/recovery.img
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
su
flash_image recovery /sdcard/recovery.img
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've used the flash_image command myself, on my Advent Vega. But it's a stand alone binary/executable... and on my KitKat Nexus 7, TE reports it as 'not found'... and I have busybox installed.
Here is my Nexus 7 TE output... both without and with root...
Code:
[email protected]:/ $ flash_image
/system/bin/sh: flash_image: not found
127|[email protected]:/ $ su
[email protected]:/ # flash_image
su-mksh: flash_image: not found
127|[email protected]:/ #
It would be useful, though, to have flash_image installed. Kind of puzzled why busybox doesn't have it.
Rgrds,
Ged.

Just Google search
Install flash image binary android
Its fast to install and for the most part universal, although I can't say I've ever used it on kitkat (havet had a chance to flash kitkat yet)
Sent from my Nexus 4 using XDA Premium 4 mobile app

I just flashed the TWRP recovery image for 2.6.3.3 on my HTC One from within Flasify.
After flashing the .img file with Flasify, my HTC One is at the "Entering Recovery" splash screen, and won't proceed beyond that.

Use fastboot
Sent from my Nexus 4 using XDA Premium 4 mobile app

@demkantor, thanks

Backing up Recovery

Is there anyway to backup stock recovery from stock firmware?

till now i don't think so, but u can download stock recovery and then flash stock firmware
---------- Post added at 08:16 AM ---------- Previous post was at 08:15 AM ----------
yograjfire18 said:
till now i don't think so, but u can download stock recovery and then flash stock firmware
Click to expand...
Click to collapse
i hav a stock recovery(1.17.x.x) don't remember full one

If you still have stock recovery installed then yes, you can enter it on terminal or adb shell
Code:
dd if=/dev/block/bootdevice/by-name/recovery of=/sdcard/orwhereveryouwanttosave/yourstockrecoveryname.img
Sorry for my bad english
Sent from my ASUS_Z00RD using XDA Labs

NOt working
testeraphy said:
If you still have stock recovery installed then yes, you can enter it on terminal or adb shell
Code:
dd if=/dev/block/bootdevice/by-name/recovery of=/sdcard/orwhereveryouwanttosave/yourstockrecoveryname.img
Sorry for my bad english
Sent from my ASUS_Z00RD using XDA Labs
Click to expand...
Click to collapse
this code is not working:silly::silly::silly:

Really? Do note, you should grant superuser (su) before executing that command
Edit : actually, that command is just make a "copy" current recovery, if you have twrp installed, then, well you got twrp not stock
Sent from my ASUS_Z00RD using XDA Labs

Lazyfox007 said:
Is there anyway to backup stock recovery from stock firmware?
Click to expand...
Click to collapse
What is your model?

For ze500kl. Root and usb debugging.
Commands:
adb shell
su
cat /dev/block/mmcblk0p35 > /mnt/sdcard/recovery.img
Recovery img will be saved in the internal storage.
This way you can back up all partitions to file img.
Then can using fastboot mode to restore partition.
Command from fastboot mode:
fastboot flash partition file.img
For example:
fastboot flash recovery recovery.img
Partition recovery will be overwrite file recovery.img.
Partition names are in the folder
/dev/block/platform/soc.0/7824900.sdhci/by-name

testeraphy said:
Really? Do note, you should grant superuser (su) before executing that command
Edit : actually, that command is just make a "copy" current recovery, if you have twrp installed, then, well you got twrp not stock
Sent from my ASUS_Z00RD using XDA Labs
Click to expand...
Click to collapse
if it needs su right, so mobile must be rooted and it would have done with TWRP if i m not wrong, then what about stock recovery

yograjfire18 said:
if it needs su right, so mobile must be rooted and it would have done with TWRP if i m not wrong, then what about stock recovery
Click to expand...
Click to collapse
Yes, this need root. When installing su, just boot twrp, don't flash them.
You can use that "temporary" twrp to flash su, and stock recovery still intact.
Sent from my ASUS_Z00RD using XDA Labs

Lazyfox007 said:
Is there anyway to backup stock recovery from stock firmware?
Click to expand...
Click to collapse
Install RASHR OR ANY FLASHIFY
Bsckup
.that's it

akhil850 said:
Install RASHR OR ANY FLASHIFY
Bsckup
.that's it
Click to expand...
Click to collapse
then how to install su binary,bcs those need su approval