Database Info

NANDROID RESTORE WITHOUT FASTBOOT?? - does it really work?

ok so im confused. I was reading the "how to flash cupcake" thread and came across this post by ridli. i tried following the instructions below but they failed, it seems like it works for him. if this truly works then there is no need for fastboot to reflash a nandroid back up. please help. thnx. BTW dudes .8 G build is awesome. (posted from my G1-modded w/root and gloss suite theme)
I tried the below on my G1 using recovery mode from JF-RC33 and i get:
error opening /sdcard/bu/system.img: no such file or directory.
I have checked the sdcard and its there, please help.
ridli said:
You can do the same without linux or any other SO.
1) Download cupcake
2) copy IMG files to a DIR in your SDCARD
3) reboot the phone in recovery mode
4) press ALT+X for go to console
5) #mount -a (for mount all partitions, without this you dont have flash_image becouse it is in /system/bin/)
6) use flash_image for flash the partitions
Code:
#flash_image system /sdcard/<dir>/system.img
#flash_image boot /sdcard/<dir>/boot.img
#flash_image userdata /sdcard/<dir>/data.img
7) #reboot
Optional: Do a backup of the phone with nandroid from the recovery mode, this do a img of system, data and boot partitions of your phone and copy to your sdcard. If you have any problem you can reflash your phone with you img.
Click to expand...
Click to collapse

It didn't work for me either, but it said I could not remount system as r/w because it was busy.
Anyway, I find instructions on how to do it via PC a lot easier. And if your phone would not boot, and you are stuck without backup, you can always pull it with adb.

Karolis:
System shouldn't be busy in recovery mode... also, it shouldn't be mounted if you're trying to write a fs image
And... no, if your phone can't boot, it can't boot. That includes starting adbd.
If you can enter recovery/spl, it's booting just fine.
flak0:
Have you checked the sdcard from the shell in android, or from your computer?
If it's the latter, you should make sure you can access the file from android.
I would recommend that you copy the flash_image binary out of /system (and /data), because you're rewriting that partition

Okay, don't use the forums when on a bad connection... my browser thought it lost connection, and decided to refresh, and send my post again... *Looks for a delete button*

this does not work
just so everyone is clear
DOES NOT WORK!
Note To Self, do not follow tutorials from junior members

arteshiftedscreen said:
this does not work
just so everyone is clear
DOES NOT WORK!
Note To Self, do not follow tutorials from junior members
Click to expand...
Click to collapse
Ummmm actually this does work if you do itcorrectly. Note to self no bashing people that are just trying to help.

so how is it done?
korndub said:
Ummmm actually this does work if you do itcorrectly. Note to self no bashing people that are just trying to help.
Click to expand...
Click to collapse
And could a Gscript or similar be written to do something like this? I'd be psyched to have the option to restore my phone on the fly. And of course, if you could do that, what would stop you from having a Nandroid restore point saved for a number of different builds? I would love that.

Out of curiosity, and I've never tried this method myself, are you just entering the following exactly?
#flash_image system /sdcard/<dir>/system.img
#flash_image boot /sdcard/<dir>/boot.img
#flash_image userdata /sdcard/<dir>/data.img
Click to expand...
Click to collapse
Or are you changing <dir> to the directory of your nandroid backup? Because if you aren't it certainly won't work.

ei8htohms said:
And could a Gscript or similar be written to do something like this? I'd be psyched to have the option to restore my phone on the fly. And of course, if you could do that, what would stop you from having a Nandroid restore point saved for a number of different builds? I would love that.
Click to expand...
Click to collapse
But it would be very unsafe to flash a fs image when the partition is actually mounted and your gscript is probably in it.
the only way is to do it in recovery mode.
one little problem though: i copied flash_image to /cache and chmod, but the shell kept telling me no such file. why is that?

billc.cn said:
But it would be very unsafe to flash a fs image when the partition is actually mounted and your gscript is probably in it.
the only way is to do it in recovery mode.
one little problem though: i copied flash_image to /cache and chmod, but the shell kept telling me no such file. why is that?
Click to expand...
Click to collapse
flash_image is a binary, should not be moved. why did you move it to cache? of course it wont work...

Unfortunately, flash_image does not support writing yaffs2 images. Look in the code, there's no support for writing the OOB data to the NAND. If it was possible I would've integrated backup AND restore in nandroid 2.0, and JesusFrekes recovery image would then also have a restore option. But alas, it's not to be.
Perhaps in a future release I can find a C coder who can add the code to the flash_image source, so that this becomes possible. But I'm not even sure if that can be done (because you need kernel driver support as well).

infernix said:
Unfortunately, flash_image does not support writing yaffs2 images. Look in the code, there's no support for writing the OOB data to the NAND. If it was possible I would've integrated backup AND restore in nandroid 2.0, and JesusFrekes recovery image would then also have a restore option. But alas, it's not to be.
Perhaps in a future release I can find a C coder who can add the code to the flash_image source, so that this becomes possible. But I'm not even sure if that can be done (because you need kernel driver support as well).
Click to expand...
Click to collapse
Can't we just use nandwrite from mtd-utils to do this? I haven't tried it yet (I'll build it for ARM when I get home from work), but it appears to be the right tool for the job. I'm really interested in getting a menu-driven restore in my recovery image.

cyanogen said:
Can't we just use nandwrite from mtd-utils to do this? I haven't tried it yet (I'll build it for ARM when I get home from work), but it appears to be the right tool for the job. I'm really interested in getting a menu-driven restore in my recovery image.
Click to expand...
Click to collapse
Oh that would be sooooooooo sweet!

Clockwork Recovery for Coby Kyros MID-7015--Updated

All credit for this goes to Razor950
Coby Kyros MID-7015
Download recovery.img from Sendspace.com - send big files the easy way
use flash_image and flash recovery to tablet. (ex flash_image recovery /sdcard/recovery.img)
Navigating:
Home is down
Menu is select
Back is back
Everything works and I'll post stock nandroid dumps on here soon.
Update some are reporting that they are unable to Flash to the recent firmware update that was posted
on the coby website do to the clockworkmod being installed.
Thanks to Kasten for coding this then thanks to adamdietrick for creating a new zip
That can be flashed with the clockworkmod installed.
Clockworkmod Coby Firmware update
Donate if you like Razor950's work!

thanks for posting
any issues that anyone gets with this recovery, please pm me.
enjoy

havic said:
Everything works and I'll post stock nandroid dumps on here soon.
Donate if you like Razor950's work!
Click to expand...
Click to collapse
Here's my backup
http://www.megaupload.com/?d=5ALHYN80

You must be rooted (I assume z4root or universal android root works)
then either using terminal (grab terminal app from market) or using adb.
Grab the recovery.img and drop it into sdcard via usb or adb push.
Open terminal and type su and then flash_image recovery /sdcard/recovery.img
or if using adb, its adb shell and then su and then flash_image recovery /sdcard/recovery.img
Note: I am not the best at writing noobie guides but hopefully it helps

Thanks for this. I do not have mine yet( lol, just ordered it) but I donated for your work!
Thanks!

Anyone have a idea on how to get back into recovery? I have it installed but have tried holding every button to get me back and nothing kinda sucks since I have been testing new mods for this and cant get to my backup because the first shot at the mod was a fail.

I was able to get clockwork installed thanks to you. Do you know of any images that are out for the 7015?

Lawful123 said:
I was able to get clockwork installed thanks to you. Do you know of any images that are out for the 7015?
Click to expand...
Click to collapse
Aside from stock(rooted) dump, there is nothing, I'll work with havic to get a rooted dump with google apps(market mostly) working correctly.
Besides that there is nothing else from my end for now. I personally don't like telechip tablets, bad experience from a gentouch :X
Also telechip company are retards and don't release kernel source, it'd help developers optimize a 2.1 rom and also be able to port kernel to a newer one for 2.2

I can see that this model gained popularity this black Friday. We are just now starting to see android tablets hit " Joe User ". I think that the telechip tabs will become popular so long as the price is on point. Thanks for all you do.

what exactly is this recovery for?
does installing this offer me additional features, or is it merely what we would restore to in case of disaster?

Deenybird said:
what exactly is this recovery for?
does installing this offer me additional features, or is it merely what we would restore to in case of disaster?
Click to expand...
Click to collapse
For now it is a good way to backup your unit so that if you screw it up you can go back. In the future people will make images for it. Hopefully someday android 2.2

Which version of flash_image tool is needed to flash this recovery or is the tool stock on the tablet?
EDIT: figured it out. stock. Looking through the dump now =)

adamdietrick said:
Here's my backup
http://www.megaupload.com/?d=5ALHYN80
Click to expand...
Click to collapse
If you try and recover from the backup that is in the link you may or may not get a error.The error is md5 mismatch. So the recovery fails to install.
What needs to be done is need to have busybox installed then shell in and run the following commands.
This has to be ran from the dir. that contains the backup files.
Which will more than likely be similar to this
/sdcard/clockworkmod/backup/2010-12-01.20.41.18
#busybox md5sum -c nandroid.md5
boot.img: OK
cache.img: OK
data.img: OK
recovery.img: OK
system.img: OK
# reboot recovery
reboot recovery
Once in clockwork then run a recovery.
If you have a Issue let me know I will try my best to get you some answers.

razor950 said:
You must be rooted (I assume z4root or universal android root works)
then either using terminal (grab terminal app from market) or using adb.
Grab the recovery.img and drop it into sdcard via usb or adb push.
Open terminal and type su and then flash_image recovery /sdcard/recovery.img
or if using adb, its adb shell and then su and then flash_image recovery /sdcard/recovery.img
Note: I am not the best at writing noobie guides but hopefully it helps
Click to expand...
Click to collapse
When I type this it it says its file not found.
I double checked and in astro I see
sdcard/recovery.img
any ideas?

beccaannabell said:
When I type this it it says its file not found.
I double checked and in astro I see
sdcard/recovery.img
any ideas?
Click to expand...
Click to collapse
where are you when you type that? does it not find the flash_image binary or the .img?

Worked for me
I got it working by doing the following.
1. Download and installed "Android Terminal Emulator" on to the device.
2. Download and installed Z4Root 1.3.0.apk from here http://forum.xda-developers.com/showthread.php?t=833953
3. Run it and pressed the "Permanent Root" button. It took a bit and it auto rebooted.
4. Place the recovery.img on the root of my sd card. (Razor950's recovery.img is from post#1 on this thread.)
5. Opened "Android Terminal Emulator".
6. Entered the following.
su
flash_image recovery /sdcard/recovery.img
7. Locked everything up for about 5 min and it went back to # prompt when it was done.
8. I powered off the device.
9. After it turned off I pressed and held the back button then pressed the power button. Kept holding it until you see clockworkMod v2.5.1.3. (If it says Android it's too late.)
I have a question myself what is sd-ext on clockwork? Also is there a way to do a selective backup? Just system with no data?
Thanks.

Thanks for your procedure, will try it when I receive my tablet.
Regarding your question about sd-ext, it's a partition of your sdcard. One will be in fat32 and the other in ext2 or ext3. Usually ext2 is used when you have app2sd or 12sd+. The purpose of this is to have more apps in install by installing them on your ext partition instead of internal memory. I use it for my HTC desire (smartphone)
Regarding your second question, I don't know anyway of doing a backup without data but pretty sure it's possible, for example, if you go in your Android do a factory reset. reboot in recovery then do your backup. Not sure if there's another way to do it

Yezir!
Kasten said:
I got it working by downing the following.
1. Download and installed "Android Terminal Emulator" on to the device.
2. Download and installed Z4Root 1.3.0.apk from here http://forum.xda-developers.com/showthread.php?t=833953
3. Ran it and pressed the "permit root" button. It look a bit and it auto rebooted.
4. Place the recovery.img on the root of my sd card.
5. Opened "Android Terminal Emulator.
6. Entered the following.
su
flash_image recovery /sdcard/recovery.img
7. Locked everything up for about 5 min and went back to # prompt when done.
8. Powered off device.
9. Press and held the back button then pressed the power button. Kept holding it until I saw clockworkMod v2.5.1.3. (If it says Android its too late)
I have a question myself what is sd-ext on clockwork? Also is there a way to do a selective backup? Just system with no data?
Thanks.
Click to expand...
Click to collapse
this is perfect!!!!! thanks for thinking of us dummies

Daali said:
where are you when you type that? does it not find the flash_image binary or the .img?
Click to expand...
Click to collapse
same thing for me
"error opening /sdcard/recovery.img:No such file or directory"
Help

noonerealy said:
same thing for me
"error opening /sdcard/recovery.img:No such file or directory"
Help
Click to expand...
Click to collapse
Can you see the recovery.img on your sd card from a file manger app like Astro? If so when your in the terminal can you cd to /sdcard? If so can you enter ls -l recovery.img? Check the size to make sure it is all there.
I have anther question myself.
At cobyusa.com/?p=prod&prod_num_id=10498&pcat_id=1013 there is a firmware update. in the update.zip in system in the build.prop file i see a line that says "ro.build.version.incremental=eng.enzo.20101125.200217". I notice that the build number on the device says "MID7015 1.6a_20101105-2". Looks like they may have changed somethings but not sure what. What would be bet best way to figure out what they changed?
I tried to run it from clockwork and i get
assert failed: getprop("ro.product.device") == "tcc8900" || getprop("ro.build.product") == "tcc8900"
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
To install this update would I just have to unroot my device? Not sure how to look what the current ro.build.product is now.
Thanks.

A701 rooting

Got A701 with following version:
Acer_AV_043_A701_RV08RC02_EMEA_DE
Acer_AV043_A701_1.017.00_EMEA_DE
trying to use rooting methods don't help much.
Got unlock and installed CWM, got su copied over to /system/xbin/ or to /system/bin, but not too much use. Any ideas how to get root without reflashing a different rom?

fix found
OK...got a fix...i guess
0) install CWM
1) nandroid backup (you're crazy if you don't do it)
2) download backup to your PC
3) PM me for a modified boot.img (or use some kitchen to mod the boot.img and get rid of the pesky ro.secure) (or let me know if you have time to write some proper content)
4) adb reboot fastboot
5) fastboot flash boot newboot.img
6) reboot to recovery
6) adb push su /system/bin/
7) reboot
8) happy days
Works for
Acer_AV_043_A701_RV08RC02_EMEA_DE
Acer_AV043_A701_1.017.00_EMEA_DE
for others most likely will cause a nuclear disaster though

If you have CWM, rooting is as easy as flashing the Superuser zip from
http://androidsu.com/superuser/
Sent from my GT-I9000 using xda app-developers app

Pawitp
nop, it is not enough.
With firmware that i 've got, the ro.secure has to be disabled, and even after that when i have everything running from root i can't remount system as rw.
Using any of the older firmwares isn't an option, as i apparently seem to have the "latest" one and i wanna stick to it to share at a later stage

andlommy said:
Pawitp
nop, it is not enough.
With firmware that i 've got, the ro.secure has to be disabled, and even after that when i have everything running from root i can't remount system as rw.
Using any of the older firmwares isn't an option, as i apparently seem to have the "latest" one and i wanna stick to it to share at a later stage
Click to expand...
Click to collapse
Having root and being able to remount /system as rw are 2 different things. Acer's kernel has some block which disallow /system from being remounted as rw. You'd need to flash a source-built kernel or just make the modifications you want in /system from recovery.

So it's the kernel doing a remount block? Wow...recompiling means I'd need to get source etc. Sounds quite a job...
Sent from my A701 using Tapatalk 2

Ezterry provided a script in github or pastbin cant remember to do this and ez explained it to me on how to use it.
If you send me the original boot.img I can patch it for you so you have full system /RW.
It takes 10 minutes to do it.
Pm me as I don't come in here very often. Or go true MD as he's my rusky homeboy.
But only if you are interested. I can do this for A700 and A701 ICS and JB boot.img

civato said:
Ezterry provided a script in github or pastbin cant remember to do this and ez explained it to me on how to use it.
If you send me the original boot.img I can patch it for you so you have full system /RW.
It takes 10 minutes to do it.
Pm me as I don't come in here very often. Or go true MD as he's my rusky homeboy.
But only if you are interested. I can do this for A700 and A701 ICS and JB boot.img
Click to expand...
Click to collapse
I already posted the modified boot image you did for the 701
http://forum.xda-developers.com/showthread.php?t=1934056
Should just have to unlock, fastboot the boot image, Download SU and BB and be good to go.
MD

Moscow Desire said:
I already posted the modified boot image you did for the 701
http://forum.xda-developers.com/showthread.php?t=1934056
Should just have to unlock, fastboot the boot image, Download SU and BB and be good to go.
MD
Click to expand...
Click to collapse
I see it know, I tought it was for different img.
And you got only 5 thank you's for posting that ?Only 5 A701 sold ? Or people are so big hearted these days?

[02-01-2013][CWMR] Trekstor Surftab Breeze 7

!!!!!CAUTION: This recovery works only flawlessly on Breeze tabs with the serialnumbers containing a C! E.g. 93016Z3Cxxxxxxx!!!!!
Hi,
Finally I made it to get CWM Recovery up and running for Trekstor Surftab Breeze.
Before starting a huge thanks to my tester X-On, who tested every crappy CWM Image I made until we got a good one! Also thanks to my other tester Snackez, whose tab didn't make it as I made a silly mistake, which caused the tablet to just display a black screen.
The usual stuff:
I am not responsible for any bricks or other damages made to your tablets! But chances are minimal now.
For the reference I pasted here the contents of the recovery.fstab file:
Code:
# mount point fstype device device2
/boot emmc /dev/block/nandc
/system ext4 /dev/block/nandd
/data ext4 /dev/block/nande
/misc emmc /dev/block/nandf # here the flag to boot from the recovery partition is set. 16MB wasted for this!
/recovery ext4 /dev/block/nandg
/cache ext4 /dev/block/nandh
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/nandk
Current status:
So, after the 2nd fiasco with the 6.x.x.x CWM, I reverted back to the 5.0.X.X base, where at least the power button works. Also I found out how to break the CWM boot loop, unless you got a working adb shell:
Code:
dd if=/dev/zero of=/dev/block/nandf conv=notrunc count=20 bs=1
In my new release I've soft linked the sh binary to /system/bin, so adb should work right out of the box. Also I've added a new service calling sh, which calls postrecoveryboot.sh (containing above code snippet), so that it should definitely be executed.
Now, 02-01-2013, Backup to internal and external SD is possible without problems...see the known problems section for any other bugs.
So, here it is!
http://ul.to/fx8vsnj3
or attached.
Instructions:
1. Download the rar archive and unpack it onto your internal SD card
2. Fire up either ADB shell or download any terminal emulator from the play store and type:
Code:
$ su
# dd if=/dev/block/nandg of=/sdcard/recoverystock.img
# dd if=/sdcard/recoveryBreezeNew.img of=/dev/block/nandg
3. Turn of your tab.
4. Keep pressed the volume- key and press power until the screens lights up
5. Keep volume- pressed until you see the CWM menue
If for some reason you want to switch back to your stock recovery, you need to fire up adb shell again or your terminal emulator and type:
Code:
$ su
# dd if=/sdcard/recoverystock.img of=/dev/block/nandg
I will make a flashable CWM zip for getting the stock recovery back while being in recovery mode. Should be comfortable doing so
Known problems
1. Mounting USB Storage is not possible while getting an error message like "cannot open ums lunfile". I googled a bit it doesn't seem so easy to fix...
Regards
TheSSJ

Hi TheSSJ,
I would be interested in testing the CWM but is there a way to backup the original system since no firmware or ROM are available right now?
Keep the good working !!

Hi,
unfortunately not...I don't know why trekstor is so slow at releasing the original firmwares...
Still wanna do it?
regards

Hell Yeah!

new?

Push! Updated now with a working release! Thanks snackez and X-On for your help in testing!

good news! : Good:
thank you
have you managed to get the source code to make us a nice custom rom?
in any case, thank you for your work!
sorry for my bad english, i'm french

Hi,
no, unfortunately I'm no good ROM cooker (also there are no sources available, don't know why ). But the CWM is the first step to begin testingfor new ROMS...
Greets

If I understand, you know save / retrieve the original rom?
So this principle, it remains to find a cook to modify / improve the rom?
On the new recovery that you do, I test tonight ...
Thank you for your work, hoping that other developers are also working on

I just installed your CWN and it works great!
I did a Backup of the ROM and then removed a Hell of a lot Stock apps and added some new. The tablet got significantly faster (It feels faster).
Thanks a lot!

New update with fixed mount points. Only the mount usb storage function doesn't want to work...

Great new !
Thank you for your job !

Original Firmware
I have done your task. Works great.
But i have done a mistak.
Now i dont have a backup from the original.
Where can i found original Trekstore Firmware for breeze 7.0 ?
I have to flash my pad.

thank you for your work. no problem for installation

der-blizzard said:
I have done your task. Works great.
But i have done a mistak.
Now i dont have a backup from the original.
Where can i found original Trekstore Firmware for breeze 7.0 ?
I have to flash my pad.
Click to expand...
Click to collapse
https://www.dropbox.com/s/xtwzqq2sjmgastr/708_FW_updatepack.zip

TheSSJ said:
https://www.dropbox.com/s/xtwzqq2sjmgastr/708_FW_updatepack.zip
Click to expand...
Click to collapse
someone found some rom for this tablet?

TheSSJ said:
https://www.dropbox.com/s/xtwzqq2sjmgastr/708_FW_updatepack.zip
Click to expand...
Click to collapse
Sorry, but the link does not work.

rik81 said:
Sorry, but the link does not work.
Click to expand...
Click to collapse
Maybe because my post was from 18th January?
http://ul.to/w8vrr5oj
Regards

TheSSJ said:
Maybe because my post was from 18th January?
http://ul.to/w8vrr5oj
Regards
Click to expand...
Click to collapse
Yes of course
But i can't open the last one
Thank you

Hey guys i search for cwm for the d Serie can anybody help me ?
Send from my Samsung Galaxy S3 I9300

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.