Database Info

[Recovery] that Toastcfl provided when unlocking NAND

If This has been posted already, I apologize...I Take No Credit For This.....This is the Recovery that was released with Toastcfl's Unlocking NAND. It's not much different from R.A-evo-v1.7.0.1 but I like it.
Assuming you have adb and fastboot access.....
TO INSTALL USING FASTBOOT:
1. Unzip NANDrecovery.zip and put attached file (NANDrecovery.img) in sdk/tools
2. Boot into Fastboot USB
3. Open command prompt and execute this command: fastboot flash recovery NANDrecovery.img
4. Reboot Recovery
ALTERNATE INSTALL:
1. Make sure the "flash_image" that Toastcfl provided during NAND unlock is in the /system/bin folder and also put NANDrecovery.img on root of sdcard(Unzip flash_image.zip)
2. Go into adb shell and execute command: mount /system ENTER execute command: mount /sdcard ENTER
3. Execute command: flash_image recovery /sdcard/NANDrecovery.img
4. Reboot Recovery

Can you post a couple images?

snandlal said:
If This has been posted already, I apologize...I Take No Credit For This.....This is the Recovery that was released with Toastcfl's Unlocking NAND. It's not much different from R.A-evo-v1.7.0.1 but I like it.
Click to expand...
Click to collapse
It's Toastcfh, fyi

if you wouldve posted this 2 days ago, i wouldve been estatic but after going through my files for 2 days i finally found the recovery image. the recovery image in the part2 thread doesn't work.

what is this, is it recovery 1.7.0 vs 1.7.0.1

This is the recovery you had to plug into usb and run the windows.bat file after flashing Toastcfl's PC36IMG...To temporarily see what it looks like and does: Boot into your recovery mode, open up the evo-recovery file from when you unlocked NAND, for windows; run recovery-windows as admin and the recovery will push to your phone temporarily; for linux do recovery-linux and for mac do recovery-mac ....These recovery files are in the "evo-recovery" folder

ahh i rememeber that recovery

Can I help you to unbrick your phone

Hi all,
I begain to understand file system of O3D and I want to TRY to help who have brick her phone.
Need some information :
Do you have acces of adb command in your phone?
Do you have acces to recovery menu? What is your recovery ( original or cwm)?
Please describe in detail the brick.
++
Sorry for my bad english.
Sent from my LG-P920 using XDA App

Yes please. I have Rogers O3D P925G. I have adb but no recovery
Ps: i am using my developers O3D, but got the Rogers version as a gift
Sent from my LG-P920 using XDA App

A thread already has been open regarding this issue...
http://forum.xda-developers.com/showthread.php?p=17592878#post17592878
i'll make it shortly ... my phone bricked ... no Recovery mode and doesn't recognize ADB commands... the only thing it does is installing OMAP4430 drivers on attaching and thats all

@largo79 try this to install CWM recovery :
Place recovery.img into your internal SDcard
After this, type
Code:
adb shell
Shell in the phone
Code:
SU
for root right
Backup your old recovery
Code:
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
Flashing CWM recovery (download CWM recovery):
Code:
dd if=/data/recovery.img of=/dev/block/mmcblk0p6 bs=4096
and reboot
Code:
reboot
@chudik
fastboot command is working or not?
Install android sdk
in tools folder type
Code:
fastboot devices
++

First of all, thanks for this thread. My problem is really weird. I have installed a cript that swaps internal sd with the external one, without a problem. Later when i intended to format the internal one my phgone rebooted only to recovery one (cwm). But i made a big mistake and tried service recovery using lg update. After that my recovery is the 3e otriginal recovery of lg and keeps booting to recovery. None of the unbricking (i tried them all) seems working. What i think is we need simply a method that formats and wipes all nand partitions such as fast boot or smart flash software that exists for optimus 2x. I am clueless now since i can only get to recovery mode and unbricikng doesn't work.

[Q] Stuck in TWRP 2.1.1 with no Sideloader

Hi All,
I wanted to change the stock ROM on my tf700t so I downgraded to V10.6.1.14.8 from V10.6.1.14.10 installed unlocker and installed GooManager. Now when GooManager went to InstallOpenRecovery Script it got stuck on the 'download has started' screen. I looked for alternative options and found out that you could install via the ADT/SDK options using latest twrp.blob file. So I went to the twrp site and got latest blob file but rather stupidly they list the oldest at the top and the newest at the bottom?. So I ended up installing the 2.1.1 version using adb terminal via these instructions:
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Then reboot to complete installation.
Now I did this but I didn't put the Roms that I wanted into the default SD Card first and this version of TWRP doesn't support microSD or ADB Sideload. It now just keeps rebooting into TWRP and when I connect to PC in TWRP the PC just recognizes the driver as Transformer but none of the ASUS drivers work. I have no idea where to go from here, backup doesn't seem to work....?
I've been looking around but seems perhaps I've hit a unique issue.
Any help on how I can progress from here to get the latest version of TWRP or indeed any decent ROM - I was originally going for cm-10.2-20131112-NIGHTLY-tf700t.zip and googleapps.
Help would be most appreciated.
Thanks,
Kavster

also worth mentioning i did a wipe data via the switch on with volume down and the 3rd icon of wipe as I was following this guide - cannot get boot recovery now just boots into TWRP...
android.sc/update-asus-transformer-pad-tf700t-to-cm-10-2-android-4-3-jelly-bean-rom
am I screwed..???

Kavster76 said:
also worth mentioning i did a wipe data via the switch on with volume down and the 3rd icon of wipe as I was following this guide
Click to expand...
Click to collapse
This option causes the bootloader to force starting the recovery until the wipe is done. The problem: The ancient recovery that you flashed cannot access the eMMC due to bootloader incompatibilities.
So your only chance to unbrick now is to get adb shell access working, then try "adb reboot bootloader" and see if you can get back to the bootloader menu. Then choose Android and run the following in Terminal or via adb shell:
Code:
su
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=32 count=1

The problem is that the TF700T is only recognized just as 'transformer' in Windows 7 device manager and I don't have a driver that will allow me to see the device via adb. Any ideas on how I can get the right driver so that I can see it again in the adb devices:
C:\Users\Kavster\Documents\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb devices
List of devices attached
C:\Users\Kavster\Documents\adt-bundle-windows-x86-20131030\sdk\platform-tools>
Then I can the adb shell.....
Thanks.

Kavster76 said:
The problem is that the TF700T is only recognized just as 'transformer' in Windows 7 device manager and I don't have a driver that will allow me to see the device via adb. Any ideas on how I can get the right driver so that I can see it again in the adb devices:
C:\Users\Kavster\Documents\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb devices
List of devices attached
C:\Users\Kavster\Documents\adt-bundle-windows-x86-20131030\sdk\platform-tools>
Then I can the adb shell.....
Thanks.
Click to expand...
Click to collapse
Have you tried the Universal Naked Drivers?
http://forum.xda-developers.com/showthread.php?t=1426502

flumpster said:
Have you tried the Universal Naked Drivers?
http://forum.xda-developers.com/showthread.php?t=1426502
Click to expand...
Click to collapse
Yes the Naked Drivers worked and device is now recognised. But it wont boot back into bootloader using the "adb reboot bootloader". It reboots but goes back to TWRP so how can I rebuild the bootloader from here.? Can I also install new version of TWRP..??
Cheers...

Kavster76 said:
Yes the Naked Drivers worked and device is now recognised. But it wont boot back into bootloader using the "adb reboot bootloader". It reboots but goes back to TWRP so how can I rebuild the bootloader from here.?
Click to expand...
Click to collapse
Hmmm, OK, try this:
Download and extract this to your computer:
http://forum.xda-developers.com/attachment.php?attachmentid=1985941&d=1369339132
then run:
Code:
adb push bootit.ko /
adb shell insmod /bootit.ko
If you are lucky, this reboots into the bootloader menu from which you can use fastboot to flash a working recovery. At least it helped this user: http://forum.xda-developers.com/showthread.php?t=2291974

_that said:
Hmmm, OK, try this:
Download and extract this to your computer:
http://forum.xda-developers.com/attachment.php?attachmentid=1985941&d=1369339132
then run:
Code:
adb push bootit.ko /
adb shell insmod /bootit.ko
If you are lucky, this reboots into the bootloader menu from which you can use fastboot to flash a working recovery. At least it helped this user: http://forum.xda-developers.com/showthread.php?t=2291974
Click to expand...
Click to collapse
Excellent stuff !!!! - that worked I now am back to the original bootloader screen. Now I have RCK / ANDROID / WIPE-DATA what should I now do to get the stock rom (I'm too nervous now)..?

Kavster76 said:
Excellent stuff !!!! - that worked I now am back to the original bootloader screen. Now I have RCK / ANDROID / WIPE-DATA what should I now do to get the stock rom (I'm too nervous now)..?
Click to expand...
Click to collapse
I'd use fastboot to flash a proper version of TWRP now.

OK So clicking Android has taken me back to 4.2.1. Think I'll do some more reading before messing about with it again - Thanks for all your help - Much Appreciated !!!!!

Trying to get back to the latest TWRP I have renamed openrecovery-twrp-2.6.3.1-tf700t.blob to twrp.blob I then put it in /sdcard root copied it over and ran the following:
C:\Users\Kavster\Documents\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
12212+1 records in
12212+1 records out
6252648 bytes transferred in 3.658 secs (1709307 bytes/sec)
[email protected]:/ #
everytime I reboot it is still in 2.1.1 TWRP and not the 2.6.3.1 version..?
and I have to run bootit.ko to get back again.

Kavster76 said:
everytime I reboot it is still in 2.1.1 TWRP and not the 2.6.3.1 version..?
and I have to run bootit.ko to get back again.
Click to expand...
Click to collapse
You have to clean the misc partition (mmcblk0p3) before the bootloader will cooperate again, see my previous answer.

_that said:
You have to clean the misc partition (mmcblk0p3) before the bootloader will cooperate again, see my previous answer.
Click to expand...
Click to collapse
Meaning he has to flash TWRP in fastboot not in adb shell - correct?
If yes - how is it different?

So I did the following - copied openrecovery-twrp-2.6.3.1-tf700t.blob to twrp.blob and then put it in same directory as fastboot.exe but still same issue after reboot - still on twrp 2.2.1:
C:\Users\Kavster\Documents\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6106 KB)...
OKAY [ 2.605s]
writing 'recovery'...
OKAY [ 1.482s]
finished. total time: 4.087s
C:\Users\Kavster\Documents\adt-bundle-windows-x86-20131030\sdk\platform-tools>
Surely that should of worked..?

Kavster76 said:
So I did the following - copied openrecovery-twrp-2.6.3.1-tf700t.blob to twrp.blob and then put it in same directory as fastboot.exe but still same issue after reboot - still on twrp 2.2.1
Click to expand...
Click to collapse
You have to clean the misc partition (mmcblk0p3) before the bootloader will cooperate again, see my previous answer. In post #3.

_that said:
You have to clean the misc partition (mmcblk0p3) before the bootloader will cooperate again, see my previous answer. In post #3.
Click to expand...
Click to collapse
OK Cheers (sorry wasn't sure what post you were on about), all sorted now phew...
Backing up system now and I'm ready to install latest CyanogenMod...

_that said:
run the following in Terminal or via adb shell:
Code:
su
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=32 count=1
Click to expand...
Click to collapse
Just out of curiosity: Is this command equivalent to
Code:
fastboot erase misc
to wipe the misc partition?
Thanks!

berndblb said:
Just out of curiosity: Is this command equivalent to
Code:
fastboot erase misc
to wipe the misc partition?
Click to expand...
Click to collapse
In theory, yes. However, when asking the bootloader for supported partitions (fastboot getvar all), "misc" is not among them, so I don't know if it really works.

Latest CyanogenMod all installed and looking good....
Thanks for all the help (I have added thanks) !!!
Kavster.

about qoute #8
hi friend.I have this problem too but my phone is samsung i9001.as you said,I downloaded the file and extracted it and then conected my phone to the pc and went to this path {start*accessories*command prompt} and entered the command "adb push bootit.ko" ,but responsed " adb is not recognised as an internal or external command, operable program or batch file" . I m too unhappy now,because my phone just boot to TWRP and like Kavster I have used TWRP 2.2.1 without adb sideload option.please help to rescue my phone.tanks dear friend

How to extract recovery.img from the ASUS firmware? [7.0/8.0] [ZE552KL/ZE520KL]

Hello guys, some time ago this device had more support from developers, someone could extract the recovery.img in order to keep it updated.
I wonder if anyone would know what the procedure is for extracting.
My device is the ZE552KL (Z012D).
I followed the steps in this tutorial, however, I did not succeed: https://tinyurl.com/yd3w4pxa
I followed all the steps and tried to extract recovery.img from the Zenfone 3 ZE552KL (Z012D) Asus firmware, however, there was a problem after applying the applypatch directive.
Error: patch boot.img: Only patches to EMMC targets are supported.
And I can not solve it.
install-recovery.sh (original extraction): https://hastebin.com/lupoqovila.bash
install-recovery.sh (change): https://hastebin.com/ofuqofezat.bash
Apllypatch directive used at the prompt: applypatch -b recovery-resource.dat boot.img recovery.img 28e9d4088f51c9dafb9189eb15f061c78be55a57 18791676 4a9f7c48e01aed3a46ac8d06618239dff9834caf: recovery-from-boot.p
Error:
https://imgur.com/a/JWfyr
I also asked for help at Zentalk, but so far no one has spoken.
https://www.asus.com/zentalk/tw/thread-147621-2-1.html
Please, I'll be grateful if anyone can help.

The recovery partition is #59, therefore to back it up you can use terminal emulator and type;
Su
dd if=/dev/block/mmcblk0p59 of=/sdcard/recovery.img
To flash, go to fastboot and type
Fastboot flash recovery recovery.img
Fastboot reboot
You need root for all this. You can convert the recovery image to be flashable via recovery but it only works with twrp, not stock.

wang1chung said:
The recovery partition is #59, therefore to back it up you can use terminal emulator and type;
Su
dd if=/dev/block/mmcblk0p59 of=/sdcard/recovery.img
To flash, go to fastboot and type
Fastboot flash recovery recovery.img
Fastboot reboot
You need root for all this. You can convert the recovery image to be flashable via recovery but it only works with twrp, not stock.
Click to expand...
Click to collapse
Thanks for taking note of my question, but what I really need to know is about recovery stock. It would not be logical for my use to perform custom recovery extraction, since it is already found in the .img format from the developer's available links (TWRP).
Following the tutorial steps of the links I indicated it is possible to make a kind of compilation using the official OTA file, processing on the device itself to generate the file recovery.img stock.
Again thank you for trying to help, any and all help is very welcome.

+1

Can someone post here stock recovery.img for ze520kl newest oreo firmware?

I'd like to know how to do this as well. I went through a lot of trouble to get Oreo installed after rooting and installing TWRP on my phone running Nougat, ended up having to go back to stock and install updates incrementally. As you noted, root is required to save the stock recovery.img, but since my device is not rooted now I can't root without installing TWRP first. That would put me in the same situation as the OP. The google translate of the link posted by the OP is a bit hard to understand, can someone else give an english explanation of how to extract recovery.img from firmware zip?
TIA
Update: I managed to follow the instructions in the OP's link, ended up with a similar applypatch command as he did and also encountered the same error with running the command over adb. I'm not sure if those instructions are for all asus devices, the one in the link is Asus P028 (Zenpad 10)
applypatch -b recovery-resource.dat boot.img recovery.img f448eeec56d4d87173858cd7aec25c36a7dfaaa7 18736380 9ebabd3eb6a59cfcaf0f4f048e2d8d6d870d7924:recovery-from-boot.p

ktl20 said:
Can someone post here stock recovery.img for ze520kl newest oreo firmware?
Click to expand...
Click to collapse
Here

Error
I keep getting
/sbin/sh: f448eeec56d4d87173858cd7aec25c36a7dfaaa7: not found
whenever i go through this. what am i doing wrong? T_T

wang1chung said:
The recovery partition is #59, therefore to back it up you can use terminal emulator and type;
Su
dd if=/dev/block/mmcblk0p59 of=/sdcard/recovery.img
To flash, go to fastboot and type
Fastboot flash recovery recovery.img
Fastboot reboot
You need root for all this. You can convert the recovery image to be flashable via recovery but it only works with twrp, not stock.
Click to expand...
Click to collapse
when I type su and enter, on adb shell show error "/system/bin/sh: su: not found". my device is unrooted. I did this for boot and recovery backup before rooting. I'm using Zenfone x00rd (Live L1)

20e semi stock fastboo/twrp flashable images

Hey guys,
This is for people who already unlocked the bootloader!!
Since there hasn't been any flashable images via twrp or fastboot, I have decided to create one for the stock 20e. Now it's semi stock because the twrp is included with the boot image I uploaded. I'm doing just 20e because im too lazy to go back and forth firmwares just to upload different versions of fw of stock.
You can flash them via fastboot or twrp.
To access fastboot you need to be rooted in your custom rom or stock:
1. Use terminal or adb shell and do these commands
Code:
Su
dd if=/dev/zero of=/dev/block/bootdevice/by-name/laf_a
Then reboot and hold the vol+ button while it's plugged into the PC
Don't worry about losing download mode on slot_a cause the other slot will still have it and you can switch to the other slot via fastboot or twrp then you can have download mode
To flash via fastboot:
Code:
Fastboot flash boot_a twrpboot_a.img
Fastboot flash system_a system_a.img
Fastboot flash vendor_a vendor_a.img
To flash via twrp:
1. Move these files to your internal sd or external.
2. Get into recovery mode and then hit install
3. Tap on select image and find the image files
4. Then flash them one by one.
5. Format data and reboot.
https://drive.google.com/folderview?id=1-1tRMeDK7sVzta9kKhAvfVF2B9XZu2ki
If you want to help out and upload the other firmwares, here are the steps:
1. Be on the firmware you want to make the image files for.
2. Make sure you are rooted!!
3. Use terminal from the play store or use adb shell
4. And do the following for each partition.
A. First SU in shell then
For system-
Code:
dd if=/dev/block/bootdevice/by-name/system_a of=/sdcard/system_a.img
For boot:
Code:
dd if=/dev/block/bootdevice/by-name/boot_a of=/sdcard/boot_a.img
For vendor:
Code:
dd if=/dev/block/bootdevice/by-name/vendor_a of=/sdcard/vendor_a.img
Then upload them to Google drive or wherever and share them if you can.

Does it work on G710EM?

Resync said:
Does it work on G710EM?
Click to expand...
Click to collapse
In theory it should.

can you upload the twrpboot for ulm21d?

Can you make the v35 twrp , thanks