Related
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.
This thread is about DL701Q tablet.
Specs uploaded here.
http://www.specdevice.com/showspec.php?id=bcad-973e-0033-c5870033c587
http://www.bestbuy.com/site/digiland-7-8gb-black/8610212.p?id=1219354106671
This is a cheap quad core tablet that includes bluetooth and GPS, Specs http://specdevice.com/showspec.php?id=a1a0-8080-0033-c5870033c587
The tablet's one short cumming is Ram (512 MB), The tablet works well despite the amount of Ram, it uses swap partition to help balance out the lack of Ram.
CWM Recovery now backs up and restores, use caution as with anything you use, you could damage your tablet.
micro sdcard required to use this recovery.
Code:
Do not use format commands at anytime.
format /data
format /cache
format /system
to install
adb reboot bootloader
fastboot flash recovery DL701Q_dual_boot_recovery.img
fastboot reboot
after tablet reboots
adb reboot recovery
unmount cache
mount system
mount data
mount cache
go back
backup/restore
backup
to restore almost same process
adb reboot recovery
unmount cache
mount system
mount data
mount cache
go back
backup/restore
restore
CWM Recovery
download
https://www.androidfilehost.com/?fid=95916177934541508
To root this tablet, use the CWM recovery, I ported to flash SuperSU
download
http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Firmware
download
http://www.panduoduo.net/r/9960566
http://www.mediafire.com/download/0au4z5j9leao9ft/mid713l-lp-lvds-20141226.rar
https://mega.co.nz/#!18wVWTRR!sa1ua8cWoczNT6cTdqzBgaqXRyYoyNPzVah_NaZzNcc
If you choose to flash firmware not needed if your tablet is working fine.
I would recommend flashing only system, then flash gapps. This firmware is older than what comes with DL701Q tablets, plus it doesn't include gapps or wifi update. This version can't be updated, so make sure to backup your system before flashing this system.
If DL701Q tablet gets wifi updates you need stock system to get them, so keep a copy of your stock system handy.
Gapps I used pa_gapps-modular-micro-4.4.2-20140608-signed.zip
https://www.androidfilehost.com/?fid=23501681358543824
Below are some pics of battery life and GPS, GPS test taken inside my house, too much snow to go outside. I haven't tried offline maps yet, I have navfree installed on tablet, will test when roads are clear.
Good battery life also.
to flash recovery
enable usb debugging setup adb and fastboot
adb reboot bootloader
or from power off
press power and volume up at same time, when you come to a selection screen use volume up to select fastboot volume down to boot into fastboot.
fastboot flash recovery /path/to/recovery
credits
Carliv
Chainfire
TKruzze
Tested GPS, via navfree usa works great, If you are going to try navfree usa, use older version, the latest version doesn't work very well, lot of bugs, very slow.
I am going to give MapFactor a try today, very lite navigation app.
Added new recovery to OP.
UBIFS filesystems are not as easy to use as ext4,use caution with this type of tablet, I have uploaded a cwm version that backs up and restores, You use this recovery at your own risk.
For the recovery to work correctly the process must be preformed correctly, below is the process that works.
I am sure the question why unmount cache and later remount cache, this is needed cause cache mounts wrong partition during initial start up. I could force cache to mount correct partition, but this is a dual recovery, so it would be counter productive to do that.
Anyway it only takes a few seconds to unmount cache, then mount system, data and cache in that exact order to get recovery to see partitions correctly. DO NOT USE FORMAT COMMAND PERIOD.
EG
format /data
format /cache
format /system
When restoring backup, recovery will wipe partitions, not format them, wipe is all that's needed
micro sdcard required to use this recovery.
Code:
Do not use format commands at anytime.
format /data
format /cache
format /system
to install
adb reboot bootloader
fastboot flash recovery DL701Q_dual_boot_recovery.img
fastboot reboot
after tablet reboots
adb reboot recovery
unmount cache
mount system
mount data
mount cache
go back
backup/restore
backup
to restore almost same process
adb reboot recovery
unmount cache
mount system
mount data
mount cache
go back
backup/restore
restore
On other thread you were working on flashable rom via cwm recovery, how is that going?
tomtom1265 said:
On other thread you were working on flashable rom via cwm recovery, how is that going?
Click to expand...
Click to collapse
Yes, I have two flashable roms, one is made from my tablet dl701q system, other one is made from mid713l system.
They both work well, both roms are ubifs systems, both are rooted and allow adb remount.
Sent from my Venue 8 3830 using Tapatalk
Uploaded specs see OP.
Sent from my DL701Q using Tapatalk
Will this recovery work with other mt8127 tablets? Got a nextbook 7 and I'm interested in making/flashing a custom recovery as safely as possible (I've already exchanged it twice, trying to avoid a third trip) any help would be appreciated
corruption said:
Will this recovery work with other mt8127 tablets? Got a nextbook 7 and I'm interested in making/flashing a custom recovery as safely as possible (I've already exchanged it twice, trying to avoid a third trip) any help would be appreciated
Click to expand...
Click to collapse
I have no ideal, I made this recovery for this tablet, if your tablet is ubifs and partitions and kernel are the same recovery should work, if not it won't.
sent from my kingSing T1 via taptalk
There are two versions of DL701Q tablet.
1. ro.sf.hwrotation=90
2. ro.sf.hwrotation=0
Version 1 has full software on Digiland website.
http://www.digi-land.net/Photo_Show.asp?InfoId=487&ClassId=56&Topid=53
If you have version one you should be able to use software as is, if you have version 2, like I do you will need to edit build.prop else touch screen will be wrong, plus screen will be upside down.
You can flash full software if you want, I only flash system.
this is my method to flash system, once you have downloaded the software unpack it, need to have custom recovery, boot tablet into custom recovery.
Code:
adb reboot recovery
unmount cache
mount system
mount data
mount cache
rm -rf /system/*
rm -rf /data/*
rm -rf /cache/*
adb reboot bootloader
fastboot flash system system.img
power off tablet, or press reset button in back
hold power up + volume up to get into boot selection
choose recovery then tab volume down.
when recovery fully loads.
unmount cache
mount system
mount data
mount cache
adb pull /system/build.prop
change ro.sf.hwrotation=90 to ro.sf.hwrotation=0
adb push build.prop /system/build.prop
adb shell
chmod 644 /system/build.prop
reboot
You should now be able to use the software, somethings may be a little off camera and so on but non the less software is usable.
Don't like software use recovery to restore your back up.
vampirefo said:
There are two versions of DL701Q tablet.
1. ro.sf.hwrotation=90
2. ro.sf.hwrotation=0
Version 1 has full software on Digiland website.
http://www.digi-land.net/Photo_Show.asp?InfoId=487&ClassId=56&Topid=53
If you have version one you should be able to use software as is, if you have version 2, like I do you will need to edit build.prop else touch screen will be wrong, plus screen will be upside down.
You can flash full software if you want, I only flash system.
this is my method to flash system, once you have downloaded the software unpack it, need to have custom recovery, boot tablet into custom recovery.
Code:
adb reboot recovery
unmount cache
mount system
mount data
mount cache
rm -rf /system/*
rm -rf /data/*
rm -rf /cache/*
adb reboot bootloader
fastboot flash system system.img
power off tablet, or press reset button in back
hold power up + volume up to get into boot selection
choose recovery then tab volume down.
when recovery fully loads.
unmount cache
mount system
mount data
mount cache
adb pull /system/build.prop
change ro.sf.hwrotation=90 to ro.sf.hwrotation=0
adb push build.prop /system/build.prop
adb shell
chmod 644 /system/build.prop
reboot
You should now be able to use the software, somethings may be a little off camera and so on but non the less software is usable.
Don't like software use recovery to restore your back up.
Click to expand...
Click to collapse
Digiland has made the update files,etc available on their website http://www.digi-land.net/upload/DL701Qupdate_software.rar
There are no instructions on the site. Maybe someone can help a noob reflash/update with these files? I have a rooted device, but can't do the wireless update because it says system was damaged and update is disabled. I would like to update and re-root.
SYN1ST3R said:
Digiland has made the update files,etc available on their website http://www.digi-land.net/upload/DL701Qupdate_software.rar
There are no instructions on the site. Maybe someone can help a noob reflash/update with these files? I have a rooted device, but can't do the wireless update because it says system was damaged and update is disabled. I would like to update and re-root.
Click to expand...
Click to collapse
If you can't follow the instructions included with the update, Then you need to contact Digiland.
This thread isn't about teaching newbies to install updates. You can start your own thread, How to install updates for Digiland tablets if you want.
sent from my kingSing T1 via taptalk
vampirefo said:
If you can't follow the instructions included with the update, Then you need to contact Digiland.
This thread isn't about teaching newbies to install updates. You can start your own thread, How to install updates for Digiland tablets if you want.
sent from my kingSing T1 via taptalk
Click to expand...
Click to collapse
A bit hard to follow instructions that DON'T exist
vampirefo said:
fastboot flash recovery DL701Q_dual_boot_recovery.img
Click to expand...
Click to collapse
I'm flashing this file, but I'm still ending up in the stock recovery, not CWM. Has anyone else had this issue?
Code:
> adb reboot bootloader
> fastboot flash recovery DL701Q_dual_boot_recovery.img
sending 'recovery' (6248 KB)...
OKAY [ 0.155s]
writing 'recovery'...
OKAY [ 0.888s]
finished. total time: 1.044s
freakified said:
I'm flashing this file, but I'm still ending up in the stock recovery, not CWM. Has anyone else had this issue?
Code:
> adb reboot bootloader
> fastboot flash recovery DL701Q_dual_boot_recovery.img
sending 'recovery' (6248 KB)...
OKAY [ 0.155s]
writing 'recovery'...
OKAY [ 0.888s]
finished. total time: 1.044s
Click to expand...
Click to collapse
No ideal why it doesn't work for you, you could try the splashtool.
Sent from my Venue 8 3830 using Tapatalk
freakified said:
I'm flashing this file, but I'm still ending up in the stock recovery, not CWM. Has anyone else had this issue?
Code:
> adb reboot bootloader
> fastboot flash recovery DL701Q_dual_boot_recovery.img
sending 'recovery' (6248 KB)...
OKAY [ 0.155s]
writing 'recovery'...
OKAY [ 0.888s]
finished. total time: 1.044s
Click to expand...
Click to collapse
I'm having a similar issue. Tried this way and the TWRP guide. Ever attempt says successful but ends up frozen on the normal boot splash screen when trying to manually or adb into recovery.
Could be your device is different, you made need to use your own kernel.
Unpack your boot.img, then unpack my recovery and swap out kernels then repack and flash.
Sent from my BLU STUDIO 5.0 C using Tapatalk
Hello. Just bought 2 of these tablets from Best Buy today. It would seem I have all the correct drivers installed, both adb and fastboot see my device but even though I have the custom recovery .img on both my micro sd card and the tablets internal storage when i type the command "fastboot flash recovery DL701Q_dual_boot_recovery.img" I get back the error "error: cannot load 'DL701Q_dual_boot_recovery.img'. What am I doing wrong? Where does the file have to be for fastboot to find it?
EDIT: Nevermind. Been awhile since I've tinkered with flashing a tablet. For others that might not know the file to be flashed needs to be in the same folder as the fastboot.exe.
Okay installing the custom recovery went great but I've tried numerous times to install the root zip file from recovery and haven't gotten root even after about 5 tries. I think I read somewhere that this method was somehow blocked in newer firmware. Perhaps I have that firmware. Kernel version on my "About Tablet" says "3.4.67 [email protected] #1 Fri Apr 3 15:55:00 CST 2015" and "Build number is " ALPS.KK1.MP10.V1.45" if that means anything to anyone.
Tried some iRoot crap which is probably exactly what it is and didn't end up with anything but a bunch of chinese bloatware on my tablet, which I promptly deleted, but no root.
Would flashing one of the older firmware definitely get me root?
InfernoShark said:
Okay installing the custom recovery went great but I've tried numerous times to install the root zip file from recovery and haven't gotten root even after about 5 tries. I think I read somewhere that this method was somehow blocked in newer firmware. Perhaps I have that firmware. Kernel version on my "About Tablet" says "3.4.67 [email protected] #1 Fri Apr 3 15:55:00 CST 2015" and "Build number is " ALPS.KK1.MP10.V1.45" if that means anything to anyone.
Tried some iRoot crap which is probably exactly what it is and didn't end up with anything but a bunch of chinese bloatware on my tablet, which I promptly deleted, but no root.
Would flashing one of the older firmware definitely get me root?
Click to expand...
Click to collapse
You have to follow OP exactly, what is happening is you are just trying to flash a zip without doing the mounts and umounts in OP.
Unmount cache
Mount system
Mount data
Mount cache
Now flash root zip.
Sent from my NXA8QC116 using Tapatalk
vampirefo said:
You have to follow OP exactly, what is happening is you are just trying to flash a zip without doing the mounts and umounts in OP.
Unmount cache
Mount system
Mount data
Mount cache
Now flash root zip.
Sent from my NXA8QC116 using Tapatalk
Click to expand...
Click to collapse
I love you man! LOL! Root is a go, verified by Root Checker! :good:
Hi.
I am pretty new to the world of Sony and I want to relock my bootloader so I can get stock firmware from my region so it looks legit (Reselling)
I have taken a TA backup but I don't know how to flash it again. Tried TWRP with no luck and I also read som other threads around here that didn't make sense to me.
I am on Windows 10 and have the single SIM Xperia XZ.
https://forum.xda-developers.com/showpost.php?p=69972315&postcount=20
First push TA.img to the folder he mentions.
Do not flash TWRP.
Boot it. fastboot boot TWRP.img
After restoring your TA-Partition flash a stock ROM. If you reboot your phone before flashing stock it will bootloop.
DHGE said:
https://forum.xda-developers.com/showpost.php?p=69972315&postcount=20
First push TA.img to the folder he mentions.
Do not flash TWRP.
Boot it. fastboot boot TWRP.img
After restoring your TA-Partition flash a stock ROM. If you reboot your phone before flashing stock it will bootloop.
Click to expand...
Click to collapse
Okay. But the part I was wondering about is:
- Pushed TAbackup.img (I renamed it) to /data/local/tmp and verified md5sum is same as original backup. (Data/local/tmp - Is this on the phone? How?)
KazuhiraDokky said:
Okay. But the part I was wondering about is:
- Pushed TAbackup.img (I renamed it) to /data/local/tmp and verified md5sum is same as original backup. (Data/local/tmp - Is this on the phone? How?)
Click to expand...
Click to collapse
Follow this instruction, i was restored my TA successfully. Boot into TWRP and enter adb command
https://forum.xda-developers.com/showpost.php?p=70903982&postcount=256
THANK YOU!
Haha christ I see it now. Never noticed before I can push commands when it is in TWRP. Thank you so much. Been wondering about this for quite some time.
Would this also work ?
Flash stock ROM using Emma -> Temporally boot TWRP (fastboot boot TWRP.img) -> dd TA Partition ->reboot.
_mow_ said:
Would this also work ?
Flash stock ROM using Emma -> Temporally boot TWRP (fastboot boot TWRP.img) -> dd TA Partition ->reboot.
Click to expand...
Click to collapse
Have not used emma personally...
But: yes, as I wrote above for Flashtool.
Thank you for your answer.
I was just wondering if there is any particular reason for first restoring TA and then flashing the Stock ROM.
flashing ROM first is safer
I just posted the link where I read about the first sucsessful restore.
It is less dangerous (no potential boot loop) to flash the ROM first and then restore the TA partition.
The only thing you have to remember that way is to enable adb (developer options) and only boot into recovery and not flash it.
Flashing Stock first with Emma worked for me. However on the first boot-up I was asked to enter my password (i didn't set a password) so I had to enter 30 random Passwords until the Phone resets itself. But now everything seems to work.
Thank you.
_mow_ said:
Flashing Stock first with Emma worked for me. However on the first boot-up I was asked to enter my password (i didn't set a password) so I had to enter 30 random Passwords until the Phone resets itself. But now everything seems to work.
Thank you.
Click to expand...
Click to collapse
For me, i flashed rom with flashtool, i checked wipe all (apps_log, userdata, ssd,....). On first boot-up it doesn't ask me for the password .
rain_effect said:
Follow this instruction, i was restored my TA successfully. Boot into TWRP and enter adb command
https://forum.xda-developers.com/showpost.php?p=70903982&postcount=256
Click to expand...
Click to collapse
I tried this but it's not working. I backed up the TA img and cant restore it. I am in twrp recovery mode and did the adb devices to check if it showed up and it does. It's when I put the command "adb push TAbackup.img /data/local/tmp/TAbackup.img" it gives me an error saying "adb: error: cannot stat 'TAbackup.img': No such file or directory". I installed the minimal and fastboot drivers under C drive. I moved the backup up TA img to this folder and running the adb commands from this folder. It keeps on failing regardless. Please can anyone help me with this?
You need to change tabackup.img with the Real file name of your ta Backup
Bitti09 said:
You need to change tabackup.img with the Real file name of your ta Backup
Click to expand...
Click to collapse
so I shouldn't rename it ? All the guides say to rename it. I don't remember the original name of my backup since I renamed it to TAbackup.img
breakwaterr said:
so I shouldn't rename it ? All the guides say to rename it. I don't remember the original name of my backup since I renamed it to TAbackup.img
Click to expand...
Click to collapse
then
adb push TAbackup.img /data/local/tmp/TAbackup.img
and
adb shell dd if=/data/local/tmp/TAbackup.img of=/dev/block/bootdevice/by-name/TA
should work if you renamed the backup to TAbackup.img
Bitti09 said:
then
adb push TAbackup.img /data/local/tmp/TAbackup.img
and
adb shell dd if=/data/local/tmp/TAbackup.img of=/dev/block/bootdevice/by-name/TA
should work if you renamed the backup to TAbackup.img
Click to expand...
Click to collapse
I already renamed it to TAbackup.img and it doesn't work. it says no directory file error
breakwaterr said:
I already renamed it to TAbackup.img and it doesn't work. it says no directory file error
Click to expand...
Click to collapse
are you doing the commands in same folder as the TAbackup file is ?
If you use Windows its possible that windows is hiding the file extension so that you've possible renamed the file to TAbackup.img.img which is shown as TAbackup.img
Bitti09 said:
are you doing the commands in same folder as the TAbackup file is ?
If you use Windows its possible that windows is hiding the file extension so that you've possible renamed the file to TAbackup.img.img which is shown as TAbackup.img
Click to expand...
Click to collapse
OMG thank you so much man. renaming the file to only TAbackup worked. THANK YOU SO MUCH!!
hi everyone! i need someone to help me create an image for my phone. to make the story short, my data/userdata partition (11.62 gb) has not been created using sp flash tool during flash using format all+ download. but luckily i did the partinfo before..
C:\Program Files\Minimal ADB and Fastboot>adb shell cat /proc/partinfo
Name
userdata
Start
0x00000000a4000000
Size
0x00000002fed80000
since i dont have the partition anymore, is it possible to create one?
if it is, can someone teach me? im currently using windows 7 x32 bit.
hi everyone! i couldn't sleep so i was messing around on my phone.. so heres the fix.
note: you must have a custom recovery like twrp to fix the prob.
boot to recovery..
tap on wipe, format data
type yes..
goback to wipe, advanced wipe
check all except for the external sd-card (if you have)
then swipe
done!
that's it!! you should be able to get back /data partition!
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)