Database Info

Lollipop and TWRP/CWM Recovery Problem

Hi everybody,
I upgraded to Lollipop using the original image. Everything was fine. No problem of any kind. Then I decided to flash the TWRP recovery. At the first run (just after installation) it was there and worked fine (I even made a backup). However, after a reboot when I went to the recovery I found that it was the stock recovery and TWRP was gone. The back up is also gone from my internal storage. The same thing happened when I flashed the latest version of CWM. After a reboot the flashed recovery is gone.
Please help. Thanks in advance.

joojooman said:
Hi everybody,
I upgraded to Lollipop using the original image. Everything was fine. No problem of any kind. Then I decided to flash the TWRP recovery. At the first run (just after installation) it was there and worked fine (I even made a backup). However, after a reboot when I went to the recovery I found that it was the stock recovery and TWRP was gone. The back up is also gone from my internal storage. The same thing happened when I flashed the latest version of CWM. After a reboot the flashed recovery is gone.
Please help. Thanks in advance.
Click to expand...
Click to collapse
are you using.. fastboot flash recovery recoveryname.img or fastboot boot recovery recoveryname.img?

simms22 said:
are you using.. fastboot flash recovery recoveryname.img or fastboot boot recovery recoveryname.img?
Click to expand...
Click to collapse
I have used "fastboot flash recovery recovery.img"

joojooman said:
I have used "fastboot flash recovery recovery.img"
Click to expand...
Click to collapse
well, if you used boot instead of flash, itll only boot the recovery for a one time use. flash should make it stick. if not sticking, flash a recovery 2 or 3 times, itll stick eventually.

simms22 said:
well, if you used boot instead of flash, itll only boot the recovery for a one time use. flash should make it stick. if not sticking, flash a recovery 2 or 3 times, itll stick eventually.
Click to expand...
Click to collapse
Thank you, I will try that and then report...

Do you have the latest version of the recovery and the root files?
I used CF Root as Chainfire is the man. I ran it first, then I added the recovery.
It stuck for me.

Remove the scripts etc that install recovery such as inatall-recovery.sh and recovery.boot.p in system and system/bin
Just double check your install-recovery.sh isn't one used to call su because you don't want to remove that if it is.

simms22 said:
well, if you used boot instead of flash, itll only boot the recovery for a one time use. flash should make it stick. if not sticking, flash a recovery 2 or 3 times, itll stick eventually.
Click to expand...
Click to collapse
I flashed ( flash .img ) the recovery 2 or 3 times (even more) but it won't stick. If I do not reboot to system it remains there but as soon as I reboot to system it is gone.

joojooman said:
I flashed ( flash .img ) the recovery 2 or 3 times (even more) but it won't stick. If I do not reboot to system it remains there but as soon as I reboot to system it is gone.
Click to expand...
Click to collapse
you want to find and rename or delete install-recovery.sh in /system/. thats whats replacing your recovery with stock.

simms22 said:
you want to find and rename or delete install-recovery.sh in /system/. thats whats replacing your recovery with stock.
Click to expand...
Click to collapse
I actually tried that, but had the following problem:
Code:
sudo adb shell mv /system/bin/install-recovery.sh{,.bak}
mv: rename /system/bin/install-recovery.sh to /system/bin/install-recovery.sh.bak: Read-only file system
Do you have an idea how I can come around this issue?
edit: I have figured that out, check post #15

tweaked said:
Do you have the latest version of the recovery and the root files?
I used CF Root as Chainfire is the man. I ran it first, then I added the recovery.
It stuck for me.
Click to expand...
Click to collapse
I do not want to root. Is it possible? I just want to have recovery. The problem is remained.

joojooman said:
I do not want to root. Is it possible? I just want to have recovery. The problem is remained.
Click to expand...
Click to collapse
From my understanding you need root to be able to edit files in /system. And in there is the script that "misbehaves" for us.
But I've not quite understood how to come by the read only file system problem

naro said:
From my understanding you need root to be able to edit files in /system. And in there is the script that "misbehaves" for us.
But I've not quite understood how to come by the read only file system problem
Click to expand...
Click to collapse
Does it mean that lollipop behaves differently from KitKat? I could have recovery without root there. It stuck at the first flash. But now it is removed every time I boot to the system.

I've ran into the same problem except for me I'm not even getting stock recovery. I don't even have one lol

Okay guys so I figured out how to get it to work (and the recovery to stick!)
First of all, get root. CF Auto root is your friend here.
Now to the problem: The recovery seems to be "reflashed" at every boot. (with an "empty" recovery).
To fix it, boot your phone up and connect it to a pc that has adb installed.
remember to not use sudo under windows, just keep that part out
Code:
sudo adb shell
Now you are on a shell in your android. Since /system is mounted readonly, we first have to remount it:
Code:
[email protected]:/ $ su
[email protected]:/ # mount -o rw,remount /system
now change the install script (I just added a .bak to the name so we do not have to delete it) and remount the filesystem and read only again:
Code:
[email protected]:/ # mv /system/bin/install-recovery.sh{,.bak}
[email protected]:/ # mount -o ro,remount /system
Finally flash the recovery as you are used to, it will now stick:
Code:
sudo adb reboot-bootloader
sudo fastboot flash recovery openrecovery-twrp-2.8.1.0-hammerhead.img
sudo fastboot reboot
From here on, you are back in android and your recovery should have sticked

Maybe you should go to system and find a file like this
recover --from--boot
then delete it

Alright, well the above solution definitely helped, but now when i try to enter super su, it tells me the binaries arent updated and the root needs to be done manually.....but didnt i just do this?

naro said:
From my understanding you need root to be able to edit files in /system. And in there is the script that "misbehaves" for us.
But I've not quite understood how to come by the read only file system problem
Click to expand...
Click to collapse
joojooman said:
Does it mean that lollipop behaves differently from KitKat? I could have recovery without root there. It stuck at the first flash. But now it is removed every time I boot to the system.
Click to expand...
Click to collapse
You can have a recovery without root. Also root is only "in" android. If your recovery has a file manager, it can edit /system files without root because android isn't running lg, ergo no protection. Its just like taking a hard drive out of a computer and adding it as a 2nd in another computer. You don't need that computers password to get the data.
So flash the ROM and see if you can delete them using the recovery file manager or adb whilst booted into recovery
---------- Post added at 08:45 AM ---------- Previous post was at 08:43 AM ----------
naro said:
Okay guys so I figured out how to get it to work (and the recovery to stick!)
First of all, get root. CF Auto root is your friend here.
Now to the problem: The recovery seems to be "reflashed" at every boot. (with an "empty" recovery).
To fix it, boot your phone up and connect it to a pc that has adb installed.
remember to not use sudo under windows, just keep that part out
Code:
sudo adb shell
Now you are on a shell in your android. Since /system is mounted readonly, we first have to remount it:
Code:
[email protected]:/ $ su
[email protected]:/ # mount -o rw,remount /system
now change the install script (I just added a .bak to the name so we do not have to delete it) and remount the filesystem and read only again:
Code:
[email protected]:/ # mv /system/bin/install-recovery.sh{,.bak}
[email protected]:/ # mount -o ro,remount /system
Finally flash the recovery as you are used to, it will now stick:
Code:
sudo adb reboot-bootloader
sudo fastboot flash recovery openrecovery-twrp-2.8.1.0-hammerhead.img
sudo fastboot reboot
From here on, you are back in android and your recovery should have sticked
Click to expand...
Click to collapse
This was all unnecessary.
boot recovery
Flash ROM
mount system
adb shell
rm /system/blah
That was all.

Re
I had the same problem yesterday except that i was intending to install both root and TWRP recovery. I flashed TWRP and ran it then installed supersu, the root did not work and TWRP was gone after rebooting the system.
I used the "cf auto root" utility made by chainfire. It worked (even though the root has few bugs)
I noticed that cf-auto-root flashed some boot img before installing root and twrp. I think you may want to give it a look.

rootSU said:
This was all unnecessary.
boot recovery
Flash ROM
mount system
adb shell
rm /system/blah
That was all.
Click to expand...
Click to collapse
This is what I did:
Boot to recovery-->
Flashing TWRP img-->
Then immediately going to TWRP file manager-->
Changing install-recovery.sh to install-recovery.sh.old -->
Then immediately made a backup --> reboot to system, turning the cellphone on and off several times
TWRP is there BUT:
The only point is that I cannot see the backup folder in my internal storage. It is clear that it has taken some
space (almost 2GB) but I cannot see the TWRP backup folder.

Can't push files via ADB

Hi so I recently flashed a rom and I didnt realize that the file was broken(wiped the device before of course) so when it gave me the error message flashing it I just rebooted and it went back to the previous rom. But I cant access the sd card anymore, so i cant download stuff, put files on it etc.(I guess its because of the dirty flash). Problem though is that I also can't push files via adb. Gives me this error message(when I give the adb command 'adb push C:\cm12.zip sdcard'): failed to copy 'C:\cm12.zip' to 'sdcard': Is a directory. I also sometimes get the Read-only file system error message
What am I doing wrong?

Wrong command syntax.
Correct syntax would be:
Code:
adb push C:\cm12.zip /sdcard/

Timoooo said:
Hi so I recently flashed a rom and I didnt realize that the file was broken(wiped the device before of course) so when it gave me the error message flashing it I just rebooted and it went back to the previous rom. But I cant access the sd card anymore, so i cant download stuff, put files on it etc.(I guess its because of the dirty flash). Problem though is that I also can't push files via adb. Gives me this error message(when I give the adb command 'adb push C:\cm12.zip sdcard'): failed to copy 'C:\cm12.zip' to 'sdcard': Is a directory. I also sometimes get the Read-only file system error message
What am I doing wrong?
Click to expand...
Click to collapse
Maybe you must first flash userdata.img and then use correct syntax as @beekay201 wrote it.

beekay201 said:
Wrong command syntax.
Correct syntax would be:
Code:
adb push C:\cm12.zip /sdcard/
Click to expand...
Click to collapse
This what I got:
Code:
failed to copy 'C:\cm12.zip' to '/sdcard//cm12.zip': Permission denied
zagorteney said:
Maybe you must first flash userdata.img and then use correct syntax as @beekay201 wrote it.
Click to expand...
Click to collapse
Where do I find that?

Timoooo said:
This what I got:
Code:
failed to copy 'C:\cm12.zip' to '/sdcard//cm12.zip': Permission denied
Where do I find that?
Click to expand...
Click to collapse
Code:
adb push C:\cm12.zip /sdcard/cm12.zip

Timoooo said:
Where do I find that?
Click to expand...
Click to collapse
Userdata.img is a part of a factory image. If you wiped also internal storage in TWRP (BTW-make it sure that it is for hammerhead) and you can't see you sd card and adb won't recognize it, flashing userdata.img will fix this.

zagorteney said:
Userdata.img is a part of a factory image. If you wiped also internal storage in TWRP (BTW-make it sure that it is for hammerhead) and you can't see you sd card and adb won't recognize it, flashing userdata.img will fix this.
Click to expand...
Click to collapse
but that wipes everything doesnt it?
beekay201 said:
Code:
adb push C:\cm12.zip /sdcard/cm12.zip
Click to expand...
Click to collapse
still permission denied

@Timoooo
Do you use encryption?

zagorteney said:
@Timoooo
Do you use encryption?
Click to expand...
Click to collapse
Don't think so lol

Timoooo said:
Don't think so lol
Click to expand...
Click to collapse
Recovery you use?

so... get the userdata.img put it on the same directory as fastboot/adb.exe and
"adb reboot bootloader"
then "fastboot devices" (just to make sure u have it)
then "fastboot flash userdata userdata.img"
when that succeeds... "fastboot erase cache" and then boot into recovery or even into system.

Timoooo said:
but that wipes everything doesnt it?
still permission denied
Click to expand...
Click to collapse
If you run 'adb devices', do you see your device's sn? Instead of pushing to /sdcard/, try pushing to /data/media/0 (iirc)

bitdomo said:
Recovery you use?
Click to expand...
Click to collapse
Twrp

beekay201 said:
If you run 'adb devices', do you see your device's sn? Instead of pushing to /sdcard/, try pushing to /data/media/0 (iirc)
Click to expand...
Click to collapse
I'll try that when I get home later. Yeah the device is listed in adb mode

beekay201 said:
If you run 'adb devices', do you see your device's sn? Instead of pushing to /sdcard/, try pushing to /data/media/0 (iirc)
Click to expand...
Click to collapse
same as before :/ permission denied
androidcues said:
so... get the userdata.img put it on the same directory as fastboot/adb.exe and
"adb reboot bootloader"
then "fastboot devices" (just to make sure u have it)
then "fastboot flash userdata userdata.img"
when that succeeds... "fastboot erase cache" and then boot into recovery or even into system.
Click to expand...
Click to collapse
doesn't that erase everything though?!

I wonder if fix permissions in twrp would work. Just trying to avoid flashing userdata.

beekay201 said:
I wonder if fix permissions in twrp would work. Just trying to avoid flashing userdata.
Click to expand...
Click to collapse
now I'm stuck in a boot loop :/

Still can't boot up anybody got an idea?

If you are not afraid of losing anything just wipe all and flash a factory image. Seems you have few other options.

wangdaning said:
If you are not afraid of losing anything just wipe all and flash a factory image. Seems you have few other options.
Click to expand...
Click to collapse
This.

No System (Erase)

Hello everybody,
Trying to install Xposed for Lollipop (x64), I had bootloop when my device restart. I didn't see that a uninstaller exist when it bootloop and I've decided to restore my system previously backup yesterday thanks to DallasCZ .bat. But I couldn't flash the system 'cause of system.img was too big for fastboot. The device accept only 256mb max file. So I used SparseConvertor to sparse my system to 11 files (like Motorola devices). But when I wanted to flash the first, it erase automatically the system. So, I can't flash and we can't flash the system previously backup with .bat.
Now, my /system is wiped and I don't have a backup of system made with TWRP. Could someone upload a backup of his 6045Y system made with TWRP ? It's more than 2gb I know, but it will be save my Idol 3 and other if they have a problem.
I have my system_image.emmc.win and mmcblk0p28 file, and my system file dump from /dev/blocks/mmcblk0p28 so if someone have a issue to help me without upload his backup of the system, tell me.
Thanks for all in advance !!!

Since you have your system image dumped from the partition you can push that to your internal sdcard. Boot twrp and run the commands from adb shell or the terminal inside of TWRP.
Code:
dd if=/sdcard/system.img of=/dev/block/bootdevice/by-name/system
It will take a while , but it will work.
Sent from my LGMS395 using Tapatalk

Unjustified Dev said:
Since you have your system image dumped from the partition you can push that to your internal sdcard. Boot twrp and run the commands from adb shell or the terminal inside of TWRP.
Code:
dd if=/sdcard/system.img of=/dev/block/bootdevice/by-name/system
It will take a while , but it will work.
Sent from my LGMS395 using Tapatalk
Click to expand...
Click to collapse
OMG ! IT WORKS ! Thanks a lot !!!!!!

Is this the U.S. version of the Idol 3?So you were able to root it?

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)

persist.img backup and restore

Hey guys! I was doing some forum surfing and I heard about this image called persist.img. I found out that it's specific to each device and you lose widevine if you flash a generic one. So I have 2 questions to ask you guys.
1. If I have a backup of my own persist.img, can I flash it and not lose widevine?
2. How do I actually back up the image?
Thanks on advance guys! ⊂((・▽・))⊃

1. not sure honestly, but I backup anyway to try if it does when time comes.
(Root is needed)
From computer:
adb shell dd if=/dev/block/bootdevice/by-name/persist of=/tmp/persist.img
adb pull /tmp/persist.img persist.img
Or from phone from terminal emulator;
su
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
Make a copy of this to somewhere else(drive/pc etc).
Not completely sure about restoring it, I think you can just flash it via fastboot.

Lossyx said:
1. not sure honestly, but I backup anyway to try if it does when time comes.
(Root is needed)
From computer:
adb shell dd if=/dev/block/bootdevice/by-name/persist of=/tmp/persist.img
adb pull /tmp/persist.img persist.img
Or from phone from terminal emulator;
su
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
Make a copy of this to somewhere else(drive/pc etc).
Not completely sure about restoring it, I think you can just flash it via fastboot.
Click to expand...
Click to collapse
That's great! Thanks for the help

Hey. How can we backup it without root?

Lossyx said:
1. not sure honestly, but I backup anyway to try if it does when time comes.
(Root is needed)
From computer:
adb shell dd if=/dev/block/bootdevice/by-name/persist of=/tmp/persist.img
adb pull /tmp/persist.img persist.img
Or from phone from terminal emulator;
su
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
Make a copy of this to somewhere else(drive/pc etc).
Not completely sure about restoring it, I think you can just flash it via fastboot.
Click to expand...
Click to collapse
where can i find the persist.img file in the device ? i search using google files app and it wasnt there.

Kagetane Hiruko said:
where can i find the persist.img file in the device ? i search using google files app and it wasnt there.
Click to expand...
Click to collapse
There is a app from play store called partitions backup it shows all partitions including persist and let's u make a copy for back up

hammered58 said:
There is a app from play store called partitions backup it shows all partitions including persist and let's u make a copy for back up
Click to expand...
Click to collapse
Needs root though.
You could do an msmtool readback i think it's called using msmtool. to backup without root. you do need windows for it though.