Related
Help for a newbie.
I followed this procedure:
1 - Copied file to sd card and renamed to update.zip (in a windows computer)
2 - turned xoom on and wento to rom manager
3 - wiped user and dalvik cache
4 - Tried to load file from zip, but it was not possible to find the update .zip file.
I get the following message:
E: Can't open /sdcard/update.zip
(bad)
Tried also without renaming and got:
E: Can't open /sdcard/update_US-Xoom-Wifi-3.2_HTJ85B-from HMJ37_stachre-solarnz-boot-img_v05.zip
After many trials rebooted.
System info showed the same 3.1 and Tiamamat 1.4.4
Opened rom manager again.
seleced install rom from sdcard
System backed up info and rebooted.
Had to reload all apps from store.
System info shows I am running 3.1 and Tiamat 1.4.4.
Also I keep receiving a message that there is a system update available.
I can't understand what I did wrong.
I g
Can anyone help?
Thank you
rogerodd said:
Help for a newbie.
I followed this procedure:
1 - Copied file to sd card and renamed to update.zip (in a windows computer)
2 - turned xoom on and wento to rom manager
3 - wiped user and dalvik cache
4 - Tried to load file from zip, but it was not possible to find the update .zip file.
I get the following message:
E: Can't open /sdcard/update.zip
(bad)
Tried also without renaming and got:
E: Can't open /sdcard/update_US-Xoom-Wifi-3.2_HTJ85B-from HMJ37_stachre-solarnz-boot-img_v05.zip
After many trials rebooted.
System info showed the same 3.1 and Tiamamat 1.4.4
Opened rom manager again.
seleced install rom from sdcard
System backed up info and rebooted.
Had to reload all apps from store.
System info shows I am running 3.1 and Tiamat 1.4.4.
Also I keep receiving a message that there is a system update available.
I can't understand what I did wrong.
I g
Can anyone help?
Thank you
Click to expand...
Click to collapse
You may have the wrong version of CWM recovery installed. You need Tiamat v3.2.0.0 R4c. If you are trying to flash thru Rom manager it may have had you update to v4.0.0.4 which is not compatible with the external sdcard. If this is the case, re-install the correct recovery version, and then redo your backup so that it is on the external sdcard where it can be safe if you need to wipe/factory reset. You can use Rom manger just to reboot into recovery, or df Quick Boot from the market and use that instead.
Good luck!
okantomi said:
You may have the wrong version of CWM recovery installed. You need Tiamat v3.2.0.0 R4c. If you are trying to flash thru Rom manager it may have had you update to v4.0.0.4 which is not compatible with the external sdcard. If this is the case, re-install the correct recovery version, and then redo your backup so that it is on the external sdcard where it can be safe if you need to wipe/factory reset. You can use Rom manger just to reboot into recovery, or df Quick Boot from the market and use that instead.
Good luck!
Click to expand...
Click to collapse
Rom manager says it is 4.0.0.4 but when in recovery is say CWM recovery-Tiamat-R4c-100611-1150-cwm or Tiamat v3.2.0.0 R4c ( I don't remember exectly) and the error is the same.
Also, I tried reflash recovery-Tiamat-R4c-100611-1150-cwm.zip from the SD card and get an error.
I really don't have a clue of what to do.
Any help would be welcome.
rogerodd said:
Rom manager says it is 4.0.0.4 but when in recovery is say CWM recovery-Tiamat-R4c-100611-1150-cwm or Tiamat v3.2.0.0 R4c ( I don't remember exectly) and the error is the same.
Also, I tried reflash recovery-Tiamat-R4c-100611-1150-cwm.zip from the SD card and get an error.
I really don't have a clue of what to do.
Any help would be welcome.
Click to expand...
Click to collapse
The problem is that you can't flash anything from the external sdcard with v4.0.0.4. In rom manager, see if you can find"all clockwork recoveries" and find 3.2.0.0. If not, find 3.0.2.8 or 3.0.2.5 and flash one of them, preferably the latest of those I have listed. I think those will at least recognize your sdcard. If you can't do that, you will need to reflash the correct recovery the same way you did when you rooted. Remember, never flash a zip file through adb.
Good luck!
I tried to flash recovery-Tiamat-R4c-100611-1150-cwm.img via adb.
I could flash boot sector. Then I reboot into recovery and try to apply zip from card with file update_US-Xoom-WiFi-3.2-HTJ85B-from-HMJ37_stachre_solarnz-boot-img_v05.zip, but there is a NO at the end of the name of the file and I can't go on.
Trying to rename as update.zip and run apply zip from card results in same error:
E: Can't open /sdcard/update.zip
(bad)
what should I do?
Thank you
possible bad download... download again... also, don't think this would be an update... leave it as originally named, just choose the option to choose which zip file to install from the sd card
rogerodd said:
I tried to flash recovery-Tiamat-R4c-100611-1150-cwm.img via adb.
I could flash boot sector. Then I reboot into recovery and try to apply zip from card with file update_US-Xoom-WiFi-3.2-HTJ85B-from-HMJ37_stachre_solarnz-boot-img_v05.zip, but there is a NO at the end of the name of the file and I can't go on.
Trying to rename as update.zip and run apply zip from card results in same error:
E: Can't open /sdcard/update.zip
(bad)
what should I do?
Thank you
Click to expand...
Click to collapse
It sounds like you are flashing recovery ok, but you keep overwriting it with the stock recovery.
Here is some important information that should help a lot with making your new recovery "stick"and this was taken from the Idiot's guide to flashing...in the Development section, and originally written by publicanimal:
4. Install recovery image (CWM)
Download the recovery image file and save it to your computer
Boot into flash mode with 'adb reboot bootloader'
Install your downloaded recovery image
C:\Documents and Settings\Anders> fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo this section
Enter CWM with the following procedure
Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work, experiment with the timing ...
When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for reaching this far .
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery. If that happens, or if you see "starting fastboot protocol " your timing wasn't right and you need to reflash the recovery image and try it again.
See original post,below for more information.
http://forum.xda-developers.com/showthread.php?t=1130996
I just got a used TF700t 64gb US version and I'm trying to flash it to CROMBI-KK. I was able to get it unlocked and TWRP 2.8.3.0 installed (the latest version as of 12/22/2014). However, every time I boot to recovery, it begins with a serious looking error. The output screen always starts off with this:
Updating partition details...
... done
Full SELinux support is present.
E:Failed to get default contexts and file mode for storage files.
MTP Enabled
No other errors are shown at first and I was able to flash the ROM. I tweaked something and it failed to boot so I went back in to reflash it. The error was still there. I have tried several wipes and changed to F2FS but the same error remains. I don't know if it's related to the error or not, but when I try to install while configured for F2FS, it always ends with another error and no OS installed. I didn't get the exact wording, but something about recursion and that something failed (it's quite vague).
Right now it is back to working, but it had to be on regular EXT4 and data journaling to work. Anyone know if there is any way to remove the storage error? Are there any other options I could try to get F2FS working?
You are only changing /data to f2fs, right?
Try to get the recovery log whenever something fails that shouldn't.
In TWRP: Advanced > Copy log
From PC: adb pull /tmp/recovery.log
berndblb said:
You are only changing /data to f2fs, right?
Try to get the recovery log whenever something fails that shouldn't.
In TWRP: Advanced > Copy log
From PC: adb pull /tmp/recovery.log
Click to expand...
Click to collapse
I was trying to do F2FS on all three available locations (/system, /cache, and /data). I didn't realize that I was only supposed to do it on /data, though when I looked at my older device, that's how it was configured as well.
So the F2FS error is figured out, but then there was the issue of the error in TWRP immediately on loading it. I rebooted my older TF700 into recovery and it did not have the error line. However, I noticed that it was running TWRP 2.8.0.1 and my newer one was running TWRP 2.8.3.0. I upgraded the older device to 2.8.3.0 and, lo and behold, the error appeared. So I'm relieved that the error doesn't seem to be an actual problem with my new device, but I'm curious still on what it means and how to resolve it. Is this something that is just inherently funky with TWRP now, or is there something I can do to configure my device so it will register as TWRP is expecting?
techturtle said:
I was trying to do F2FS on all three available locations (/system, /cache, and /data). I didn't realize that I was only supposed to do it on /data, though when I looked at my older device, that's how it was configured as well.
So the F2FS error is figured out, but then there was the issue of the error in TWRP immediately on loading it. I rebooted my older TF700 into recovery and it did not have the error line. However, I noticed that it was running TWRP 2.8.0.1 and my newer one was running TWRP 2.8.3.0. I upgraded the older device to 2.8.3.0 and, lo and behold, the error appeared. So I'm relieved that the error doesn't seem to be an actual problem with my new device, but I'm curious still on what it means and how to resolve it. Is this something that is just inherently funky with TWRP now, or is there something I can do to configure my device so it will register as TWRP is expecting?
Click to expand...
Click to collapse
It seems to be a bug in TWRP 2.8.3. I just flashed that version (was on 2.8.1 before), flashed data2sd.zip an got the E: Failed to get default context.... error. I am dirty flashing ZOMBi now and got the same error although the flash seems to be going fine.
I'll post the logs in the TWRP thread. Let's see what the experts have to say....
Hi all,
First off, I am not familiar with alot of the technical wording in these forums so I hope that I am able to communicate properly with my issue.
I was not happy with how slow the stock version of this tablet was so I decided to install a custom rom, however, I managed to get to the point of unlocking it but that's about as far as I got out of being overwhelmed with what came next! Here is where I am at:
I am currently on Android version 4.2.1 and my laptop is running Windows 10.
I have downloaded latest TWRP image file and renamed that twrp.img and it is stored in the main root folder of my tablet (SD Card aka Internal Storage). USB debugging has been enabled after I activated the Developer Options.
The custom rom I am looking at is CyanogenMod version 11 which I have downloaded, however it should be noted that on the download page it says that there is no recovery available for this build?? whatever this means? I also downloaded Minimal ADB and Fastboot but when I connect the tablet to the laptop (the tablet connects fine) I type in the command prompt "fastboot devices" but nothing happens.
I am at a point now where do I try to continue with the custom rom? or go back to stock?
Can anyone help with basic instructions please?
Thanks in advance.
Head to the General section and read the Beginners Guide. It's the first sticky, so it's easy to find.
It's your decision which rom you run, but you should give Katkiss LP or Katshmallow a good look.
The latter is the only rom for this tablet that is still under active development.
Sent from my Nexus 5X using Tapatalk
Can I ask questions in this thread with reference to the beginner guide?
Sure. Ask away
Sent from my Nexus 5X using Tapatalk
I managed to now Root the device and when I turn on the device in recovery mode it says the following:
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.3.1.14.10-20130601" A03
Starting Fastboot USB download protocol
then it has 3 options - RCK, Android, Wipe Data
I am trying to install 6.0.1 KatKiss Custom Rom (it's downloaded onto the device already)
Thanks
binx77 said:
I managed to now Root the device and when I turn on the device in recovery mode it says the following:
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.3.1.14.10-20130601" A03
Starting Fastboot USB download protocol
then it has 3 options - RCK, Android, Wipe Data
I am trying to install 6.0.1 KatKiss Custom Rom (it's downloaded onto the device already)
Thanks
Click to expand...
Click to collapse
Read this: http://forum.xda-developers.com/showthread.php?t=2688891
As many times as it takes to understand it. :laugh:
In the meantime I will update post #2 a little.
After installing a recovery you have to:
Format data
Convert /data to f2fs http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
flash Katkiss, gapps and SuperSU in the same session (follow instructions in the OP of the Katkiss thread)
I am not understanding about the installing a recovery. RCK is the stock recovery according to the beginners guide, however it also mentions TWRP.
In order to get KatKiss, what steps do I actually need to do? given where I am currently at?
binx77 said:
I am not understanding about the installing a recovery. RCK is the stock recovery according to the beginners guide, however it also mentions TWRP.
In order to get KatKiss, what steps do I actually need to do? given where I am currently at?
Click to expand...
Click to collapse
It's all in my Beginner's Guide - you just have to read it:
Basically the process of flashing a custom ROM on the TF700 involves three steps:
1) Unlock the bootloader using Asus' Unlock tool
2) Install a custom recovery on the tablet
3) Flash a custom ROM of your choice using said custom recovery
Click to expand...
Click to collapse
And I gave you the remaining steps in my last post....
Now it's up to you to read and read again. And google terms you do understand. Then read again
After installing a recovery you have to:
Format data
Convert /data to f2fs http://forum.xda-developers.com/tran...p-2-8-t3073471
flash Katkiss, gapps and SuperSU in the same session (follow instructions in the OP of the Katkiss thread)
Click to expand...
Click to collapse
This is where I am up to now as per the beginners guide
Place the TWRP file into the same directory as your fastboot.exe.
Again check the connection with
Code:
fastboot devices
If you get the connection, in the command window type:
Code:
fastboot -i 0x0B05 flash recovery <name-of-file>
the error I get says "cannot open twrp" (I renamed the TWRP file that I downloaded) even though this image file has been moved into the fastboot directory on my PC (I downloaded and installed the ADB, Fastboot and Drivers tool)
How did you rename the file? Enable file extensions in Windows Explorer and make sure you did not add a double extension
Sent from my Nexus 5X using Tapatalk
berndblb said:
How did you rename the file? Enable file extensions in Windows Explorer and make sure you did not add a double extension
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I renamed the file just in windows explorer and I can confirm that the file name is twrp.img
That's with file extensions enabled? Do you see the extensions for all the files in that folder or just for TWRP?
BTW, which TWRP version do you try to flash? Downloaded from where?
Sent from my Nexus 5X using Tapatalk
Ok I got past this point, I hadn't added .img to the command prompt.
Now I am in TWRP and attempted to install KatKiss but it came up with "Zip Signature Verification Failed!" Error installing zip file '/sdcard/download/katkiss-6.0_TF700T_026.zip".
It did say that it could not find MD5 file?
I now have 2 options
1 - Wipe Cache/Dalvik
2- Reboot System
Just hit the Home button in TWRP, go back to Install and this time uncheck the box that says "verify zip signature" then flash the rom. It always checks if you have a md5 checksum file, but it doesn't matter if you don't. The flash goes through anyway
Sent from my TF700T using Tapatalk
Excellent, I successfully installed KatKiss 6.0.1!
Thanks for your help mate!
well, I thought I was in the clear until I realised that I hadn't formatted the data (which apparently is why I don't have file manager and other apps).
I have gone back into recovery to format data and re-flash relevant zip files but now the tablet has frozen during formatting with "unable to mount /data/media/TWRP/.twrps" and also "Failed to Mount '/data' (invalid argument)
binx77 said:
well, I thought I was in the clear until I realised that I hadn't formatted the data (which apparently is why I don't have file manager and other apps).
I have gone back into recovery to format data and re-flash relevant zip files but now the tablet has frozen during formatting with "unable to mount /data/media/TWRP/.twrps" and also "Failed to Mount '/data' (invalid argument)
Click to expand...
Click to collapse
You got it resolved?
Katkiss Marshmallow - Can't run Goggle Services/Play
I converted my TF7000T from 4.2.1 to KatKiss Marshmallow, using TWRP Manager on the installation end. Steps included boot access, rooting, wiping/formatting and flashing. Marshmallow functions fine. My problem is that I can't get Google Play or Google Services to run. I tried one installation that was a 'moderate' Gapps installation. It was completely unstable despite some of the apps actually updating. I then repeated the wipe and reinstall of KatKiss-026 and Android 6.0.1 with a minimal Gapps installation - just Google Play Store and Google Play Services. Google Play Services flashes constantly that it is not working. I am also not able to log into my Google Play Store account. I'm afraid I have an outdated version of Google Play. However, I cannot figure out a way to update Play Store or Play Services. Does anyone have a solution to this problem? If I could download a minimal Gapps zip that contained either the current, or update-able version of these two apps, I would also be in business. Help!!
You are running the wrong gapps package I think. You need to install the pico gapps and only the pico gapps package that is linked in the KatKiss OP.
And you have to flash rom, gapps and Supersu(if you want root) in the same recovery session together in that order. Every time. You cannot just flash a gapps package on MM rom anymore.
ROM, pico gapps, supersu - reboot
Oh - and to start out with I'd highly recommend you wipe, better format data before flashing. Wiping of cache and Dalvik goes without saying right?
Sent from my TF700T using Tapatalk
Yes I did thanks, I haven't played around too much with it though - I did experience it to be very slow when trying to install Facebook app though. I do plan to start using it more often so time will tell.
Hi,
firstly I apologise if this is the wrong way to do this but I'm having trouble finding the info I need.
I have a TF700 (WW sku) running CWM and Omnirom 5.1.1
I want to install Katkiss Nougatella which requires TWRP Kang instead of CWM (I think).
I have downloaded TF700K_all_WW_USER_V5.0.4.17.raw from Asus' website as I believe this will restore the tablet to its original factory state and then I can proceed to install TWRP and Katkiss.
But I cannot install the .raw file, #fastboot devices# doesn't show my device, #adb devices# does but when I copy the .raw file to the device I cannot install it via CWM.
My laptop is running Linux Mint 18.1 I have tried running #sudo fastboot devices# but that doesn't work either...if anyone knows what I'm doing wrong I'd love to hear from them. Thanks in advance!
The short answer to your thread title is: You don't. :cyclops:
I have no idea what file you dug up there, but it could well be something for the TF700KL - or something entirely different, I have no idea. what I do know is that it is NOT firmware for the TF700T.
But you don't need to do that anyway.
All you need is:
1. Flash a current TWRP version (kang or official - doesn't matter as long as it is 2.8.+)
2. Format /data in TWRP
3. Convert /data to f2fs
4. Flash the rom, gapps and supersu if so desired.
Best would be if you did figure out how to get fastboot working in Linux. Should be a breeze but I can't help - I'm illiterate in Linux.
Then you could fastboot flash the latest TWRP 3.x from Teamwin's website: https://twrp.me/devices/asustransformerinfinityTF700T.html
If that fails Kang TWRP 2.8.x comes conveniently packaged into a flashable zip: https://forum.xda-developers.com/tr...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395
To convert data to f2fs follow this: https://forum.xda-developers.com/tr.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
Enjoy
Hi,
Thanks a million for the prompt and detailed response, I will try this out as soon as I have time and report back with how it went!
blimey74 said:
Hi,
Thanks a million for the prompt and detailed response, I will try this out as soon as I have time and report back with how it went!
Click to expand...
Click to collapse
So installed the Kang TWRP zip with no problems and followed your instructions to format /data and change the file system to f2fs. Flashed Katkiss but for whatever reason it wouldn't boot up. Checked file system again and it was still ext4. Reformatted and switched to f2fs and this time Katkiss works. Tablet is reborn, really happy with it thanks again for the help :good:
Need custom recovery for Mobiistar C1 shine 4g mt 6739 device as m stuck need it urgently and want install android 10 gsi image my device has arm32 a only architecture some suggest me some good and lite gsi images please firstly I need custom recovery twrp please someone help.
It would be hard to support a 2018 device I guess.
[CLOSED] I Will build TWRP for your device!
I wanna build twrp for your device! Pls give info about your device! if possible give stock firmware!
forum.xda-developers.com
i can upload recovery.img file for if you want
its Mobiistar C1 shine (MT6739) arm 32bit a only supported device running on 8.1 i was some how able to root it but unable to install custom recovery if u can please build one for this device i will upload stock recovery.img in few minutes presently its bricked but i will recovery it because i have stock firmware and flashing tool of it....so dont worry just please build a custom recovery like twrp for this device asap if possible
Again: You request a TWRP build for your device going to this thread
[CLOSED] I Will build TWRP for your device!
I wanna build twrp for your device! Pls give info about your device! if possible give stock firmware!
forum.xda-developers.com
any custom recovery bro sorry for that (twrp)
my phone back running again i have flashed it with stock firmware recovery images i have attached earlier and so does phone details screenshot now present situation is 8.1 not rooted stock recovery and firmware so i hope if anyone can help i will be glad
installed latest magisk apk and .zip also by patching boot.img file and flashing that with sp tool to install magisk and got root privilege's
all now i want is proper running and fully functional custom recovery to install custom roms and mods
copvaibhav said:
its Mobiistar C1 shine (MT6739) arm 32bit a only supported device running on 8.1 i was some how able to root it but unable to install custom recovery if u can please build one for this device i will upload stock recovery.img in few minutes presently its bricked but i will recovery it because i have stock firmware and flashing tool of it....so dont worry just please build a custom recovery like twrp for this device asap if possible
Click to expand...
Click to collapse
I am not responsible for any wrongdoing by you. Always have ROM stock files. Any error, install stock recovery again.
First you need to unlock the bootloader if necessary! Unzip file attached and look 2 files.
Then, the installation plan:
0) Flash the TWRP with SPFT or fastboot;
1) Enter TWRP IMMEDIATELY without starting in the system, otherwise TWRP can revert to the stock;
2) When asked to enter the password, select Cancel;
3) Load the file with Magisk (look for any magisk19.zip for TWRP and the decryption file for EXTERNAL memory;
4) Flash Magisk immediately and then install the file data_decrypt_Mobiistar_C1_Shine.zip immediately;
5) Make FORMAT DATA - bottom left button - Type: YES. Go back to the TWRP menu;
6) Make Wipe: data, cache, dalvik (reset to factory settings! Save your data!);
7) Reboot to TWRP (password must not ask);
8) Restart on the system, root is received.
thanks bro for making recovery.img when installing magisk 19.zip its giving error on last step failed to mount /vendor/persist (invalid argument). done
after that i tried to install your data decrypt .zip after one reboot to recovery because i have tried before without reboot recovery once so this time rebooted and installed your data.zip file and again on the last step same error as magisk failed to mount /vendor/persist (invalid argument). done
after that i tried to format by typing yes but again same error failed to mount /vendor/persist (invalid argument).done
just to inform you i have formatted phone from inside by turning it on factory reset but nothing happened....and internal space is not mounting i some how managed to install these things via OTG USB but same error again and again. i am attaching screenshot also which i captured from other phone of mine.
kindly help asap
copvaibhav said:
thanks bro for making recovery.img when installing magisk 19.zip its giving error on last step failed to mount /vendor/persist (invalid argument). done
after that i tried to install your data decrypt .zip after one reboot to recovery because i have tried before without reboot recovery once so this time rebooted and installed your data.zip file and again on the last step same error as magisk failed to mount /vendor/persist (invalid argument). done
after that i tried to format by typing yes but again same error failed to mount /vendor/persist (invalid argument).done
just to inform you i have formatted phone from inside by turning it on factory reset but nothing happened....and internal space is not mounting i some how managed to install these things via OTG USB but same error again and again. i am attaching screenshot also which i captured from other phone of mine.
kindly help asap
Click to expand...
Click to collapse
This is Ok. I made TWRP fast and not remember if the stock partitions has \vendor\persist. So if has that's message is normal. Therefore messages about \vendor\nvdata;nvram;nvcfg is normal too. Very pacth zip files can delete that and the device cannot have IMEI.
First: Is good know the file TWRP worked;
- - You can't install any zip without FORMAT DATA first because FORMAT DATA process can view internal storage. If you don't FORMAT DATA maybe the zip file going wrong with MicroSD & OTG.
In this moment you understand: not use external storage! Put zip in the internal storage an try again.
About MTP: Has anything wrong wiht A8.1 & TWRP. Most devices with A8.1 and TWRP do not have access to MTP. I don't know what happens because I don't know why TeamWin was unable to resolve this.
Now you need put zip with adb command (search how to do) or use sileload on the TWRP.
PS: the picture attached by you show about decrypt. In the first moment you need acept modifications and password you press CANCEL.
lopestom said:
This is Ok. I made TWRP fast and not remember if the stock partitions has \vendor\persist. So if has that's message is normal. Therefore messages about \vendor\nvdata;nvram;nvcfg is normal too. Very pacth zip files can delete that and the device cannot have IMEI.
First: Is good know the file TWRP worked;
- - You can't install any zip without FORMAT DATA first because FORMAT DATA process can view internal storage. If you don't FORMAT DATA maybe the zip file going wrong with MicroSD & OTG.
In this moment you understand: not use external storage! Put zip in the internal storage an try again.
About MTP: Has anything wrong wiht A8.1 & TWRP. Most devices with A8.1 and TWRP do not have access to MTP. I don't know what happens because I don't know why TeamWin was unable to resolve this.
Now you need put zip with adb command (search how to do) or use sileload on the TWRP.
PS: the picture attached by you show about decrypt. In the first moment you need acept modifications and password you press CANCEL.
Click to expand...
Click to collapse
sideload is not starting forgot to mention it i have tried that also booted phone normal put the file in internal but in recovery cant have access to internal storage and yes i have press cancel first and that accepted modification but nothing happened no internal storage access only some how otg thats it i dont know what to do
copvaibhav said:
sideload is not starting forgot to mention it i have tried that also booted phone normal put the file in internal but in recovery cant have access to internal storage and yes i have press cancel first and that accepted modification but nothing happened no internal storage access only some how otg thats it i dont know what to do
Click to expand...
Click to collapse
Okay. Wait my free time and I'll create other TWRP for your device.
Reflash stock recovery if you want & test other file soon.
Update
\|/ Lucky file attached today. So install and test. You can install zip that I put before or Donwload acoording your device cpu has. Read instructions about that again.
Reference Download: https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/
thanks bro i dont know how it worked but it worked again i have to use otg but this time it worked by downloading different force disabler.zip after that i have formatted the data by typing yes it worked then again i flashed your disabler and new recovery image and phone booted magisk installed phone rooted.....thanks a ton i dont know how to say thanks you but thank you all .
can please suggest me as my mt 6739 is 32arm a only device some light gsi for my device actually i want custom mods in gsi so if u can suggest me which also supports my device i will be very thankful
copvaibhav said:
thanks bro i dont know how it worked but it worked again i have to use otg but this time it worked by downloading different force disabler.zip after that i have formatted the data by typing yes it worked then again i flashed your disabler and new recovery image and phone booted magisk installed phone rooted.....thanks a ton i dont know how to say thanks you but thank you all .
can please suggest me as my mt 6739 is 32arm a only device some light gsi for my device actually i want custom mods in gsi so if u can suggest me which also supports my device i will be very thankful
Click to expand...
Click to collapse
Look correct app to know about your device: Treble Info
You need try install AOSP 8 & 9: https://github.com/phhusson/treble_experimentations/releases
Look "bugs"; try solving; keep your time with experiments.....
After you can try LOS, RRMix, Havoc, etc.....
About this thread/ask help about Custom Recovery so Solved. @jerryhou85
Good Lucky!
system-arm-aonly-vanilla-nosu.img.xz
system-arm32_binder64-aonly-vanilla-nosu.img.xz
bro which file shpuld i download as i told you mine is 32bit arm a only (what is arm first link and arm32binder64 aonly difference) kindly tell.
just to clarify i have download both removed.xy from ext. and flashed from recovery system image but phone goes into fastboot after reboot and when rebooting in recovery at the top it shows no os installed.
lopestom said:
Okay. Wait my free time and I'll create other TWRP for your device.
Reflash stock recovery if you want & test other file soon.
Update
\|/ Lucky file attached today. So install and test. You can install zip that I put before or Donwload acoording your device cpu has. Read instructions about that again.
Reference Download: https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/
Click to expand...
Click to collapse
Sir it's stuck on password screen touch not working please fix it, I will always be grateful to you.
Honey2012 said:
Sir it's stuck on password screen
Click to expand...
Click to collapse
The first start need choose the CANCEL. I think you not know about TWRP (unofficial) and the process with device/TWRP without encryption/decryption process.
If you want that so send me some device to develop/have the possibility of getting that option.
Honey2012 said:
touch not working please fix it, I will always be grateful to you.
Click to expand...
Click to collapse
As you read, I not have your device in my hands!
Many 32bits and few 64bits devices have problem with touch screen from kernel. That's not my error! It's from device company.
I not know about touch screen work or not since copvaibhav not write about. But I won't fix this. There is also the possibility to use OTG and plug in a USB Mouse to use in TWRP.
There are solutions to fix the touch screen but I don't have the device and I don't have time to do it. Search and you will know. So solve it yourself and thank your self for it.
Ask copvaibhav for more process and using TWRP.