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
Related
I flashed update 4.2.1 factory image from Google website. And flashed latest CWM recovery and supersuV0.98 both. It goes well for root explorer and Titanium backup apps and so on.
Problem is, I couldn't use "adb shell mount -o remoun, rw /system" on my laptop！Only we could do is by adb shell, then type su to get root to operate system files. It seems system couldn't get completed root! Something must goes wrong... Anybody can help?
I've encountered this issue before. I ended up booting to recovery and doing it there.
Sent from my Nexus 7 using xda app-developers app
issak42 said:
I've encountered this issue before. I ended up booting to recovery and doing it there.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
So didn't you solve this problem or just go to recovery to mount system?
Now I must type adb shell to go in shell and type su to get root...
350d said:
So didn't you solve this problem or just go to recovery to mount system?
Now I must type adb shell to go in shell and type su to get root...
Click to expand...
Click to collapse
What I needed done could be done trough recovery, so once I fixed my issue ( there was no launcher installed) I wasn't investigating further.
Sent from my LT18i using xda app-developers app
350d said:
I flashed update 4.2.1 factory image from Google website. And flashed latest CWM recovery and supersuV0.98 both. It goes well for root explorer and Titanium backup apps and so on.
Problem is, I couldn't use "adb shell mount -o remoun, rw /system" on my laptop！Only we could do is by adb shell, then type su to get root to operate system files. It seems system couldn't get completed root! Something must goes wrong... Anybody can help?
Click to expand...
Click to collapse
Don't you need an insecure boot.img to use adb remount?
hopscotchjunkie said:
Don't you need an insecure boot.img to use adb remount?
Click to expand...
Click to collapse
Thanks! I did this, fastboot erase boot, so that I lost insecure boot.img before. Where is JOP40D's insecure boot.img ? I just downloaded boot-insecure-jop40c from Nexus 7 toolkit..., it does work. Fixed.
Oh, couldn't get permanent insecure boot, even I flashed superboot from Paul...
350d said:
Oh, couldn't get permanent insecure boot, even I flashed superboot from Paul...
Click to expand...
Click to collapse
I rooted my Nexus 7 with CWM using ADB's sideload feature. I'm using ubuntu linux with fastboot and adb at my fingertips. I simply typed in this
adb sideload (filename.zip) (Be sure to navigate to where the .zip su is located.)
example: sudo ./adb sideload supercwm.zip (Sudo on linux gives root permissions and the ./ runs the specific program in the current location)
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 ) ..
I was rooted on 4.2.2 and checked for the system update for 4.3. It was there so I got really excited and installed it immediately, without writing a thread about it, making sure I'm not doing something wrong. Well, I was.
It updated to 4.3 and it works fine, but I can't access TWRP (I get an opened Android with a red X over it). Also, when I go into SU, I get a message saying "There is no SU binary installed. ... If you've just upgraded to 4.3, you need to manually re root your device."
How do I do this? Thanks.
Sent from my Nexus 4 using Tapatalk 4
I followed instructions as given in the following video: www (dot) youtube (dot) com/watch?v=jn5ih0omlxI
Worked for me. Simple instructions to follow.
rabrot said:
I was rooted on 4.2.2 and checked for the system update for 4.3. It was there so I got really excited and installed it immediately, without writing a thread about it, making sure I'm not doing something wrong. Well, I was.
It updated to 4.3 and it works fine, but I can't access TWRP (I get an opened Android with a red X over it). Also, when I go into SU, I get a message saying "There is no SU binary installed. ... If you've just upgraded to 4.3, you need to manually re root your device."
How do I do this? Thanks.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Toolkits cannot flash the recovery on Android 4.3 so you have to download the recovery image and flash the recovery image using "fastboot flash recovery [Replace_this_with_image_name]" and enter while your Nexus 4 is on bootloader mode to flash the recovery properly.
Now you need to transfer the SuperSU v1.51 zip file to the root of your internal storage and install it via TWRP recovery and then you are fully rooted without any TB restore issues or anything like that.
Sent from my Nexus 4 using xda app-developers app
andyabc said:
Toolkits cannot flash the recovery on Android 4.3 so you have to download the recovery image and flash the recovery image using "fastboot flash recovery [Replace_this_with_image_name]" and enter while your Nexus 4 is on bootloader mode to flash the recovery properly.
Now you need to transfer the SuperSU v1.51 zip file to the root of your internal storage and install it via TWRP recovery and then you are fully rooted without any TB restore issues or anything like that.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thank you so much, but I don't quite understand the first part since I've only rooted my Nexus 4 once, using a toolkit. I hope you don't mind, I have a few questions: Where do I download the recovery image and where do I type the text you wrote?
Thanks so much!
Sent from my Nexus 4 using Tapatalk 4
rabrot said:
Thank you so much, but I don't quite understand the first part since I've only rooted my Nexus 4 once, using a toolkit. I hope you don't mind, I have a few questions: Where do I download the recovery image and where do I type the text you wrote?
Thanks so much!
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
I rooted and unlocked my device with a Toolkit but the problem is that you do not know what is exactly going on since you cannot see the commands.
You have to get the Android SDK for this one, I already have it all in a zip file but that is on my laptop and I will be working on my phone today by installing PA.
One you get the SDK you have to go into the SDK manager and download/update the ADB tools, after that open the CMD in the folder which says "Platform-tools" and type the command from there.
Has for the image you have to put it in platform-tools has well for this to work:
http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.6.0.0-mako.img
Sent from my Nexus 4 using Tapatalk 4
I see there is a root out there already but it seems to be the international and not Asia.
Does anyone know an Asia SM-G900I Root available.
Thanks in advance.
hi dude i have this model as well and have spoken to chainfire and he is waiting for the stock firmwares to be released to create the root for our model,
hopefully will have to be soon, i havnt found one anywhere else for now
Brent
Flash CWM.
Once done, do a backup and try CF Root for another model of s5. If it works, report this useful anwser. If it doesn't works, say it and restore your backup.
Can you inbox me Chainfire details, i might be able to give him a stock rom.
cheers
QUOTE=Brentpn;51840673]hi dude i have this model as well and have spoken to chainfire and he is waiting for the stock firmwares to be released to create the root for our model,
hopefully will have to be soon, i havnt found one anywhere else for now
Brent[/QUOTE]
successful Root SM-G900I
when i say i spoke to him i meant pm'd on here at the forums,
but on another note i have succesfully rooted the sm-g900i using the cf-auto root for the 900f using odin 3.07
it all worked fine no glitches no problems
Happy rooting
Brent
Brentpn said:
when i say i spoke to him i meant pm'd on here at the forums,
but on another note i have succesfully rooted the sm-g900i using the cf-auto root for the 900f using odin 3.07
it all worked fine no glitches no problems
Happy rooting
Brent
Click to expand...
Click to collapse
yes!!! best news ive heard all day!!
---------- Post added at 09:01 PM ---------- Previous post was at 08:18 PM ----------
i can also say that ive successfully rooted my SM-G900I Galaxy S5 with the SM-G900F method no problems at all!
Hey guys so does this mean we could possibly flash a SM-G900f firmware on the the SM-G900i phones?
Sent from my SM-G900I using Tapatalk
Ooh great news!
If u flashed g900f u will have a different modem so prob best not to
Sent from my SM-G900I using xda app-developers app
I don't wanna risk it, gonna wait for an official 900I root release. Cant wait xD
Root works for the 900i atm just use the 900f cf-root method if you dont care about knox.
Is there a way that I can possibly upload the 900i firmware to flash back to if something goes wrong?
Sent from my SM-G900I using Tapatalk
Is there a version of CMW for G900I version. I found it one for H but it warns not to use on other variants.
Thanks
dekefake said:
Flash CWM.
Once done, do a backup and try CF Root for another model of s5. If it works, report this useful anwser. If it doesn't works, say it and restore your backup.
Click to expand...
Click to collapse
stuart123 said:
It warns not to use on other variants.
Click to expand...
Click to collapse
I don't kwow but you can do a backup of your recovery using DD in ADB shell and try to flash CWM for another model of s5. If it doesn't works, restore the img file using DD in ADB shell
Thanks.
Could you explain how to DD backup as ive never done that way before,
thanks
dekefake said:
I don't kwow but you can do a backup of your recovery using DD in ADB shell and try to flash CWM for another model of s5. If it doesn't works, restore the img file using DD in ADB shell
Click to expand...
Click to collapse
stuart123 said:
DD backup
Click to expand...
Click to collapse
You must connect your phone in ADB and enter this command :
adb shell su -c "/dev/block/mmcblk0p10 of=/sdcard/recovery.img bs=4096"
I don't kwow if the recovery partition is right mmcblk0p10 for your phone. The SG-900H recovery partition is mmcblk0p10 and for SM-G900F it's mmcblk0p16.
Try to backup the two partition with the commands :
adb shell su -c "/dev/block/mmcblk0p10 of=/sdcard/recovery-h.img bs=4096"
adb shell su -c "/dev/block/mmcblk0p16 of=/sdcard/recovery-f.img bs=4096"
Look at the recovery.img size. A recovery image amount of size is 10 mb.
I think this command may be universal but i not tested it :
adb shell su -c dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recovery.img
Hope this helps
Thanks for all your help just anohter question.
My phone is 100% new without any root etc so how do i get su?
Should i be doing this in normal op mode on the phone as when i try recovery mode it wont install drivers or find the phone,
when u use in normal mode i get this.
C:\android>adb shell su -c "/dev/block/mmcblk0p10 of=/sdcard/recovery.img bs=409
6"
/system/bin/sh: su: not found
C:\android>adb devices
List of devices attached
634e9700 device
C:\android>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $
dekefake said:
You must connect your phone in ADB and enter this command :
adb shell su -c "/dev/block/mmcblk0p10 of=/sdcard/recovery.img bs=4096"
I don't kwow if the recovery partition is right mmcblk0p10 for your phone. The SG-900H recovery partition is mmcblk0p10 and for SM-G900F it's mmcblk0p16.
Try to backup the two partition with the commands :
adb shell su -c "/dev/block/mmcblk0p10 of=/sdcard/recovery-h.img bs=4096"
adb shell su -c "/dev/block/mmcblk0p16 of=/sdcard/recovery-f.img bs=4096"
Look at the recovery.img size. A recovery image amount of size is 10 mb.
I think this command may be universal but i not tested it :
adb shell su -c dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recovery.img
Hope this helps
Click to expand...
Click to collapse
I will be a Samsung owner for the first time coming from HTC, but will wait for the Youtube video on how to root.
stuart123 said:
Is there a version of CMW for G900I version. I found it one for H but it warns not to use on other variants.
Thanks
Click to expand...
Click to collapse
Philz recovery works on 900i. I am using it at the moment
Sent from my SM-G900I using Tapatalk
txr33 said:
Philz recovery works on 900i. I am using it at the moment
Sent from my SM-G900I using Tapatalk
Click to expand...
Click to collapse
txr33 im really counting on you to make us a nice rom like ripper rom was with the s3! been using that since day 1.
have u rooted it yet mate? what process did u go through?
prot- said:
txr33 im really counting on you to make us a nice rom like ripper rom was with the s3! been using that since day 1.
have u rooted it yet mate? what process did u go through?
Click to expand...
Click to collapse
I will be helping goldie with alliance rom for the s5. Yes I have rooted it by using chainfires cf auto root for 900f with the packaged odin in the zip then flashed philz latest recovery from the philz thread with odin as well.
Sent from my SM-G900I using Tapatalk
FYI, some stock SM-G900I firmwares are up at live.samsung-updates.com
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