Database Develop

ClockworkMod Recovery loop and error:-1 during solution

Hi, I was trying to make the backup of my DS 7 wifi stock using ClockworkMod Recovery. After that I try to restore it, but after restore it stucks(Loop) at ClockworkMod Recovery. It's not working! Moreover, I can't change it to fastboot, can you please help me resolve it! Is there any way I can change it to fastboot.
I highly appreciate your help!
--------------------------------------------------------------
Got answere!
mount all the things you can in the ClockworkMod Recovery,
Go to cmd in windows,
c:\ cd android-sdk/platform-tools/
type these in adb shell
flash_image /dev/block/mmcblk3p2 /sdcard/boot_orig.img
flash_image /dev/block/mmcblk3p1 /sdcard/recovery_orig.img
select reboot from the recovery. now it will reboot and it will format misc and it will reboot again. NOW the device will load the os!!!
now that you are here, i also suggest to go to fastboot again and to flash all over again in this order:
flash system
flash recovery
flash boot
------------------------------------------------------------------------------------------
If you are getting failed with error:-1:Make sure: you mount internal sdcard from ClockworkMod Recovery> to copy files downloaded from here!
recovery: http://dl.dropbox.com/u/23637011/recovery_orig.img
boot:http://dl.dropbox.com/u/23637011/boot_orig.img
system: http://dl.dropbox.com/u/23637011/system_orig.img

[Q] system partion mount fail

hey,guys..
i confront a problem
1. when i flash anything contain ( mount /system), the phone will reboot immediately when the script run at the line ( mount /system)
2. when i use rootexplorer copy or move anything to the /system ( rw), it also reboot immediately and when reboot into os ,it wiped the file i copied
os: sense 4.2.2 | stock kernel
ps: already try flash boot.img via fastboot and erase cache
has any one know how-to , thks in adv..:crying:

[Emergency Guide] How to Blank or regenerate Watch (WA 5.01) after clearing \system

[Emergency Guide] How to Blank or regenerate Watch (WA 5.01) after clearing \system
Prerequisit :
Be sure to have latest adb (1.0.32) and fastboot version. Download it from here
Link to know how to enter into fastboot
Under Fastboot
Download boot from here
Code:
- fastboot flash boot bootll.img
Download TWRP recovery from here
Code:
- fastboot flash recovery twrp.img
Go to Recovery and format all twice with TWRP recovery
Flashing back stock recovery :
Download stock recovery from here
Code:
- fastboot flash recovery recoverll.img
Back to stock recovery, format twice
Regenereting system step :
Download rooted AW 5.01 system directory from here
Code:
- fastboot flash system system.img
Go back to stock recovery, Choose apply update from ADB (adb sideload)
Download AW 5.01 update from here
Code:
- adb sideload 149e0c34d0ab10d3e356d6301915dcc04552d9db.signed-lenok-LWX48P-from-KNX01R.149e0c34.zip
Reboot system now. Choose langage, etc.
Nota : At this time, if you don't need root and Chainfire SU (witch is useless at this time) you can go just for flashing TWRP by :
Code:
- adb reboot bootloader
- fastboot flash recovery twrp.img
And that's it.
Or following steps : Rooting back Watch and custom TWRP Recovery support
Download stock rooted AW 5.01 system directory from here
Code:
- adb reboot bootloader
- fastboot flash system system.img
Reboot Watch, autorize adb debug on the watch
Download Chainfire SU 2.40 from here or BETA-SuperSU-v2.42.zip
Note : You can remove Superuser.apk from the zip file into \common recovery which it is not compatible with AW 5.01
Pushing SU to the watch
Code:
- adb push supersu.zip /sdcard/su.zip
Back to Fastmod and flashing TWRP advanced recovery
Code:
- adb reboot bootloader
- fastboot flash recovery twrp.img
Restart watch and go to TWRP recovery, install/flash su.zip from sdcard, reboot
Et Voilà !

Nice write up, I'm not sure doing the adb sideload does anything though. The system image is already patched, it was a backup from my device just rooted. Currently I have busybox working on the device and and working on init.d support so any changes we want to make will survive after reboot.
Sent from my A0001 using XDA Free mobile app

It'ill be nice :good:

HELP
I've done everything to try to get back to AW 5.01 but when I get to the adb sidelload part it says "error: device not found".
It's seem that windows 8 is not detecting my watch. Anyone have any insight on this would be great thanks!
Jay
edit...
Never Mind Got it to Work!

How did you get it to work?

I managed it, too. Turns out I had to reinstall drivers while in sideload mode. You can do it in device manager, select from computer, from list and find ADB composite device.

Hey guys, I accidentaly installed supersu apk on my watch and now I can see it in the menu all the time. How can I remove it from /system/app/SuperSu? Do I have to root first in order to gain rw rights on /system, remove whole SuperSu folder than do a factory reset for example and it won't show up anymore?

hornedfiend said:
Hey guys, I accidentaly installed supersu apk on my watch and now I can see it in the menu all the time. How can I remove it from /system/app/SuperSu? Do I have to root first in order to gain rw rights on /system, remove whole SuperSu folder than do a factory reset for example and it won't show up anymore?
Click to expand...
Click to collapse
simply flash this in twrp > https://hostr.co/3yMSrXUUMD8B and it will remove for you and you will get root also

[Request]Does someone can give me a F2FS formated cache partion img?

Hi,
I know this is a strange requset.
Because my Nexus 6 is stuck at Google logo and can't boot into system or TWRP.
This is begin at when I try to flash 5.11 OTA(TWRP flashable) file.
After install without error, I have stuck at Google logo.
Then I notice that my system is rooted, noforce encrypt and use F2FS filesystem.
I gusee that the problem is new kernel didn't support F2FS, so I flashed Zen kernel with fastboot.
This step let me can boot in to system normally, but I still can't get into TWRP.
Because I want to fix TWRP, so I tried fastboot erase cache.(This is big mistake.....I should backup all file before try this command)
After fastboot erase cache, I still can't get into TWRP, and I lose system again.(Stuck at boot Animation)
I think it is cause by "fastboot erase cache" didn't create F2FS filesystem cache partition.
Does someone can help me that give me a F2FS filesystem cache partition img file?
I just want to get into system and backup all file.
Then do a full factory reset, hope this can bring back my TWRP.

chowtom said:
Hi,
I know this is a strange requset.
Because my Nexus 6 is stuck at Google logo and can't boot into system or TWRP.
This is begin at when I try to flash 5.11 OTA(TWRP flashable) file.
After install without error, I have stuck at Google logo.
Then I notice that my system is rooted, noforce encrypt and use F2FS filesystem.
I gusee that the problem is new kernel didn't support F2FS, so I flashed Zen kernel with fastboot.
This step let me can boot in to system normally, but I still can't get into TWRP.
Because I want to fix TWRP, so I tried fastboot erase cache.(This is big mistake.....I should backup all file before try this command)
After fastboot erase cache, I still can't get into TWRP, and I lose system again.(Stuck at boot Animation)
I think it is cause by "fastboot erase cache" didn't create F2FS filesystem cache partition.
Does someone can help me that give me a F2FS filesystem cache partition img file?
I just want to get into system and backup all file.
Then do a full factory reset, hope this can bring back my TWRP.
Click to expand...
Click to collapse
do fastboot format cache then fastboot format userdata. Then TWRP should work.

Thanks for quick reply,
That is what I want to do.
But it will wipe all my data, so I want to get into system and backup data before do fastboot format userdata.
danarama said:
do fastboot format cache then fastboot format userdata. Then TWRP should work.
Click to expand...
Click to collapse

chowtom said:
Thanks for quick reply,
That is what I want to do.
But it will wipe all my data, so I want to get into system and backup data before do fastboot format userdata.
Click to expand...
Click to collapse
Oh I see.
Have you tried adb access whilst bootloop?
Failing that, another option would be edit the ramdisk to change the /cache mount to ext4. I imagine the kernel you have has set it as f2fs
I'll happily format my cache as f2fs and take a nandroid of it to create a cache image, but im not sure if that would be fastboot flashable?

danarama said:
Oh I see.
Have you tried adb access whilst bootloop?
Failing that, another option would be edit the ramdisk to change the /cache mount to ext4. I imagine the kernel you have has set it as f2fs
I'll happily format my cache as f2fs and take a nandroid of it to create a cache image, but im not sure if that would be fastboot flashable?
Click to expand...
Click to collapse
Try it and I can know is flashable or not.
I have tried adb access, adb can connect my device, but can't access sdcard,
Code:
/system/bin/sh: cd: /sdcard: No such file or directory
/system/bin/sh: cd: /storage/sdcard0: No such file or directory

chowtom said:
Try it and I can know is flashable or not.
I have tried adb access, adb can connect my device, but can't access sdcard,
Code:
/system/bin/sh: cd: /sdcard: No such file or directory
/system/bin/sh: cd: /storage/sdcard0: No such file or directory
Click to expand...
Click to collapse
You can try /data/media/0 for sdcard
Nandroid isnt in .img format.
I've just dd'd a cache.img and fastboot flashed that. Lets see if it boots. If it does, I'll format it and dd it again.
Edit > Well it booted (though it is optimising now)...
I'll try and format and dd the image for you, though not sure it will work. Do I need a special version of TWRP to format F2FS?

danarama said:
You can try /data/media/0 for sdcard
Nandroid isnt in .img format.
I've just dd'd a cache.img and fastboot flashed that. Lets see if it boots. If it does, I'll format it and dd it again.
Edit > Well it booted (though it is optimising now)...
I'll try and format and dd the image for you, though not sure it will work. Do I need a special version of TWRP to format F2FS?
Click to expand...
Click to collapse
https://twitter.com/dhacker29/status/568070387306766336
This one can format F2FS, but I am not sure TWRP will check kernel support F2FS or not.
And I can't access /data/media via adb.
Code:
[email protected]:/ $ cd data
cd data
[email protected]:/data $ cd media
cd media
/system/bin/sh: cd: /data/media: Permission denied

chowtom said:
https://twitter.com/dhacker29/status/568070387306766336
This one can format F2FS, but I am not sure TWRP will check kernel support F2FS or not.
And I can't access /data/media via adb.
Code:
[email protected]:/ $ cd data
cd data
[email protected]:/data $ cd media
cd media
/system/bin/sh: cd: /data/media: Permission denied
Click to expand...
Click to collapse
Yeah I found that one eventually and it let me format.
Now I just need to find somewhere to upload a 256MB image

danarama said:
Yeah I found that one eventually and it let me format.
Now I just need to find somewhere to upload a 256MB image
Click to expand...
Click to collapse
MEGA or Google driver?

chowtom said:
MEGA or Google driver?
Click to expand...
Click to collapse
Dev-host.
---------- Post added at 10:40 AM ---------- Previous post was at 10:17 AM ----------
Had to go Mega in the end
Here you go:
https://mega.co.nz/#!UoF0RIpA!ew9AYAqn-C2vxxO8VMjXnp1jOM8eD6JqXdsrEyJimGM
Not sure it will work though.

danarama said:
Dev-host.
---------- Post added at 10:40 AM ---------- Previous post was at 10:17 AM ----------
Had to go Mega in the end
Here you go:
https://mega.co.nz/#!UoF0RIpA!ew9AYAqn-C2vxxO8VMjXnp1jOM8eD6JqXdsrEyJimGM
Not sure it will work though.
Click to expand...
Click to collapse
It works!!!
Huge thanks for your help.
Now I can start to backup my data.:laugh:

chowtom said:
It works!!!
Huge thanks for your help.
Now I can start to backup my data.:laugh:
Click to expand...
Click to collapse
wow, that was surprisingly easy.
Well dd copies at block level, so it *should* have worked, but I've never really tested it before.

Finally, I recover my data and didn't lost any one.
The step what I do is:
1. Use fastboot to flash cache img which provided by danarama.
2. Reboot to test, result is System ok and TWRP still fail.
3. Boot to system and backup all data with MTP.
4. Use fastboot erase userdata to factory reset my Nexus 6.
5. After step 4, I can get into TWRP. Redo the Convert to F2FS procedure.
6. Reboot to system and skip all initial SETUP. Copy all sdcard data to nexus 6 by MTP.
7. Back to TWRP, restore the data partition(F2FS) which backup a weekago.
8. Reboot to test, both System and TWRP boot correctlly.

Error fastboot when i flash the recovery

Hello
I try to install a custom recovery on my tf701 (android 4.3, USB debug ON)
here are the previous steps i did :
1/ i have unlock the bootloader using ASUS tools : OK
2/ i have root the TF701 : OK
for this, I installed Minimal ADB and Fastboot
I copy the files found here
and I lauch the command : adb reboot bootloader
then : fastboot boot zImage_dtb ramfs.img.gz
the root is ok
-------------------------------------------------------------------
3/ i try to install recovery
i download the file here : droidbasement.com/asus/tf701t/recovery/
i put the file in the folder of Minimal ADB and Fastboot
and i launch the commande : adb reboot bootloader
then, when the fasboot usb mode is ready on the device : fastboot flash recovery recovery.img
first time :
target reported max download size of 64382
sending 'recovery' (6652 KB)...
FAILED (data write failure (Unknown error)
finished. total time: 5.050s
second time :
target didn't report max-download-size
sending 'recovery' (6652 KB)...
FAILED (remote: (Timeout))
finished. total time: 2.010s
Can you help me please ? I add that, when the device is ON in a normal mode (not fastboot) and connected to the PC with USB, the adb driver interface are ok :
"
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
E1OKCY174091 device
"
i have tried to plug on other usb port ... it's the same ...
i have tried to reboot my computer : ... it's the same ...
i have tried to download another version of adp/fasboot (platform-tools_r28.0.2-windows.zip) : it's the same
without this installation, I can't install a custom rom ..
Many thanks in advance !

There are only two working recoveries for the TF701, one CWM without touch interface which I don't quite trust and a pretty good TWRP with touch here https://www.google.com/amp/s/forum....-kang-twrp-tf700t-2-8-x-xarea51-t3121989/amp/
The one you have there is probably the stock recovery...
The Kang TWRP is a little buggy though. You may come to a point where TWRP tells you it cannot mount /system or any other partition for that matter. All you have to do is convert the file system on /system to ext2, then convert it right back to ext4 and proceed with rom installation.
Good luck!
Sent from my Pixel 2 using Tapatalk

Hello berndblb
Many thanks for your help
The recovery I try to install is Recovery v6.0.4.6 CWM 11.
Which one is the easier to install for a beginner ?
Because what you said previously seems difficult for me ("convert the file system on /system to ext2, then convert it right back to ext4 and proceed with rom installation.")
Can you explain me how to do ?
Recovery v6.0.4.6 CWM 11 or Kang TWRP : can i install then the Rom "
ROM][N 7.1.2] [ KatKiss - Nougatella #037 ] for asus tf701
?
Many thanks in advance

They are equally easy to install since you just flash both of them in fastboot
But if you are asking which is easier to use, then it is the Kang TWRP. CWM does not have the drivers for the touch interface and you have to navigate everything with the vol buttons. More importantly I do not trust the "format data" function in CWM and that is crucial to install a custom rom. The issue with the corrupt file system in the Kang TWRP is a minor nuisance and you fix it right in TWRP. If you get the "cannot mount....." error, you just go to Wipe > Advanced > Change or repair file system, check the System partition and convert it to ext3 (or ext2 - does not matter). Swipe the button and when it is done (less than a minute) you repeat the step and change it back to ext4. After that everything should be good. If you want to read more about this issue search the Katkiss thread for "cannot mount"
Actually, there is another custom recovery out there which I have not tried and cannot vouch for. But maybe you go for that one, it does not seem to have the same issue and is based on a later version of TWRP: https://forum.xda-developers.com/tr...lopment/recovery-twrp-3-2-1-x-tf701t-t3720912
Read the thread, it seems to work fine. The Kang TWRP is 2.8, that one is based on 3.2.1 - both are fine to flash a Katkiss rom.
You do know that you have to fully format /data before you can flash a custom rom, right? You do that in your custom recovery (in TWRP: Wipe>Format Data, swipe the button). TWRP does a secure erase which wipes and trims every block. That's why this formatting takes around 60 minutes. Do not interrupt it!! CWM does not have this functionality, another reason I prefer TWRP..

hello berndblb and all helpers !
i have installed the Kang TWRP: it's ok
then I copy the custom rom KatKit for TF701 on /sdcard
i do a full wipe : error : "cannot mount..." : so I convert to ext2 and then I convert to ext4 the partition System and data
then i do a full wipe
my problem ... i'm sure you find it : i have erased all my data on /sdcard. No kitkat.zip yet !! :crying::crying::crying:
how to copy the rom on my tablet ?
for your information, when I am in TWRP, i can do "adb devices" on my computer :
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
15C4110C61C00000009FB01C0 recovery
But push commande is failed
C:\Program Files (x86)\Minimal ADB and Fastboot>adb push KatKiss.zip /sdcard/
adb: error: failed to copy 'KatKiss.zip' to '/sdcard/KatKiss.zip': no response:
Connection reset by peer
i put kitkat.zip on a USB Key and I plug it on my docks : it seems not be recognized ...
i 'm really lost
please help !!

Put the Rom on a microSD, mate. You can navigate in TWRP to the card and flash from there
Sent from my Pixel 2 using Tapatalk

Hello !!
I have nevers seen the microsd port ! I discover it 2 days ago !
Just before your answer, a 'adb push' was successfull ! I don't know why, and the next 'adb push' for gapps ans supersu were unsuccessful...it's strange !
But all IS ok now !
I have just a last 2 questions :
1/ next Time, where Can i copy the rom (.Zip) , somewhere it will not be deleted ?
2/my tablet is not rooted now ... Is the way to root depends on the Rom ?
If I follow the steps i did when my tf701 has the rom stock, IS still good ? (https://forum.xda-developers.com/showthread.php?t=2516215)
Thanks for your help !

1) the safest place is a microSD. You can flash the Rom straight from there. But as long as you do not format your data partition - and you only need to to that if you install a different rom - you can keep it on internal storage. In most cases you only need to wipe /data, not format, and that leaves /data /media where your files live, untouched.
2) First the question is: Do you need root? You should only root your rom for a good reason. If you are not sure if you need root - you don't.
Cyber threats are multiplying. You're safer if the tablet is not rooted.
That said: you can root by just flashing the zip in recovery.
BTW, if you did not flash gapps yet, you always should flash it together with the rom, not separate. To install gapps now flash the rom, then gapps, then root (if needed), reboot
Sent from my Pixel 2 using Tapatalk