Ok, so Was using my nexus s today and I kept getting the notification to perform a system update to the newest version of gingerbread (2.3.4). Prior to pressing update my phone was at 2.3.1 default with 2.5.### ClockworkRecovery and it was rooted. Everything worked on it perfect. So I proceeded to download and install the update, and CWR fails to install the update and I would have to take out the battery to restart the phone. I had been doing this multiple times and I wanted to get it updated. So I go into CWR and try installing it manually:
I look around and try to find the file and I couldn't, I reset user data to see if it would fix it and it didn't, then I go back and start formatting the following folders, /system, /cache, /data and one other but I did not format /boot, so Then (noob me) I restart to phone and of course the rom is gone. I get back to recovery and try to restore from update.zip but the console said the file could not be found, I look up my model and look for a full verison rom and the mount my usb storage and place the rom .zip on the storage and try to install from .zip on sd but it did not work so I end up grabbing this and installing it and now I'm stuck, when I do adb shell it doesn't pick up the phone any more, it can fast boot on the phone but it can't go into recovery and I have no idea what I should do to try to fix this problem.
NOTE: before I ened up installing and replacing the recovery, my /system folder would not mount due to "invalid arguments"
Model is i9020T
I don't have firmware version access
and if there is any other information I can provide please let me know
Update:
I got the device to be recognized by fastboot but not by "adb shell", when I type adb shell no device is found, so I guess my question now is do I need to just flash a new recovery and then try to flash a new rom?
Solution:
1. fastboot your phone, (volume up+lock/power button)
2. place the recovery image you want to install in the "Android SDK"/tools/ folder
3. in your cmd/terminal, while in "Android SDK"/tools/ execute:
Code:
fastboot flash recovery "NAME-OF-RECOVERY.img"
4. once that is installed and it should work, then restart your recovery mode
5.clear all your data/factory reset, including davlik cache
6.mount your sd to your computer so you can place the Rom you want on your phone's sd
7. In recovery choose zip from sdcard to install.
8. It should install, if it gives you problems try another rom, I had problems with rAv 1.2.2, keep restarting every minute. I used "NS-2.3.4-GRJ22-Stock-Deodexed-signed.zip" and it worked.
9. Restart the phone and be patient the phone will start up and you should be set.
Hope this helps someone!
HI,
2 of my PC (Windows 7 64) does not see my transformer in USB Debug mode. I installed the 64 bit Dell driver on each PC. Could someone provide me with some options to try.
Is there a way to completely reset the Transformer to stock without USB or being able to load a kernel from SD card?
2 ways to reset -
If you can boot then go into settings --> backup and reset --> factory data reset.
If you can't, hold volume-down then press power, and wait till wipe data appears, use vol keys to select it.
and search for the Universal Naked Drivers, those may help.
Thanks. That seemed to wipe the user settings and data, but not the recovery app "CWM-based Recovery v5.5.04 roach-tf101-r2". As a result the following happened after I reset.
System reboots
System comes up clean and runs setup (wifi, gmail account, etc).
System downloads firmware update.
System reboots to install update
Android appears and runs for a few seconds
Mesages appear: CWM-based Recovery v5.5.04 roach-tf101-r2
Finding update package, opening update package, Verifying update package
E: failed to verify whole-file signature
E:signature verification failed
Installation aborted
At this point the TF still will not install zip from sd card since as you told me before I need a different recover and is not found by the PC with a naked driver.
However, the unit is functional.
Any other options to root and get a new recovery installed and finally a new ROM.
Note: the PC does see the TF if I am in the recovery. However, as soon as boot the TF and enable USB debug the TF us not seen.
To go back to totally stock including stock recovery, download and flash an official ROM from Asus website.
baseballfanz said:
To go back to totally stock including stock recovery, download and flash an official ROM from Asus website.
Click to expand...
Click to collapse
I have no problem doing that, but how do I do it if I cannot connect the TF to PC via USB or load a zip file via recovery? Both of these do not work!
Did you update cwm via ROM manager? That's the issue there, you can run Roach2010's fix to fix that.
If terminal emulator app works you can flash a downloaded and extracted
(through es file explorer) recoveryblob with
Code:
su
dd if=/sdcard/recoveryblob of=dev/block/mmcblk0p4
reboot
Then you have working recovery and can either flash ROM or Stock.
Thanks for all the replies.
I finally got it working. It took me forever to understand that having a recovery that could only read from the internal memory was not a big deal. I created a folder on the internal sd and dropped in the zip for the external version of CWM . I rebooted and loaded the new restore and from then on I could load ROMs from my external uSD card. I am now happily running the latest version of Revolver.
Jerry
It's been a rough morning over here.
I've had a lot of issues with the latest update (12.1) so I decided to download the .zip for CM12s and install it from recover - the exact same way I updated it initially (before I got the 12.1 OTA update).
I used the same .zip file from before, builds.cyngn.com/cyanogen-os/bacon/12.0-YNG1TAS0YL-bacon/2263178b74/cm-12.0-YNG1TAS0YL-bacon-signed
After installing from internal storage from the menu, it seems to install fine, and then it takes me back to the menu and I select Restart System.
After 20 minutes looking at the Cyanogen boot logo, I'm assuming it's stuck.
When I plug the phone into the computer, it says it's charging but neither Windows or my Chromebook recognize the device to allow file transfer.
If I press down+power, I can still get to the Cyanogen menu, but without a new .zip file I'm not sure what else to try.
Any advice? I'm pretty worried!
nagem145 said:
It's been a rough morning over here.
I've had a lot of issues with the latest update (12.1) so I decided to download the .zip for CM12s and install it from recover - the exact same way I updated it initially (before I got the 12.1 OTA update).
I used the same .zip file from before, builds.cyngn.com/cyanogen-os/bacon/12.0-YNG1TAS0YL-bacon/2263178b74/cm-12.0-YNG1TAS0YL-bacon-signed
After installing from internal storage from the menu, it seems to install fine, and then it takes me back to the menu and I select Restart System.
After 20 minutes looking at the Cyanogen boot logo, I'm assuming it's stuck.
When I plug the phone into the computer, it says it's charging but neither Windows or my Chromebook recognize the device to allow file transfer.
If I press down+power, I can still get to the Cyanogen menu, but without a new .zip file I'm not sure what else to try.
Any advice? I'm pretty worried!
Click to expand...
Click to collapse
Have you tried using fastboot to flash the stock images?
Are you using twrp?
1.I suggest installing twrp vor any recovery you like.
2. Than redownload rom and gapps (just to be sure)
3. Mount your device as mtp storage in twrp and put Rom and gapps in it
4. Than wipe /system /data /cache
(data wipe will delete all apps, your internal storage will be untouched)
5. flash rom and gapps
6. reboot your phone
If that does not help try Heisenbergs solution.
I recently bought a second hand TF700T that has been rooted with Katkiss 6.0 but it has numerous problems that I need to know which is the best way to resolve. This is what I have:
Model: TF700T
Android Version: 6.0.1
Kernel Version: 3.1.10 katkernel-tf700
Build: Katkiss-024.6.0.1
ClockworkMod Recovery v6.0.4.7
The problems I have are:-
1. It has no Play Store and I am able to download the apk file but 'can't read/open' so it won't install from download (yes I have allowed apps from unknown sources). I managed to pull the apk file using ADB but the Play Store simply opens and closes a white page.
2. If I go to settings there is a SuperSU – clicking on it I get 'Unfortunately, settings has stopped'. I don't think this should happen. I don't know how to check if Super SU Beta 2.52 is installed.
3. If I go to Accounts I have Personal (IMAP) and + Add Account where I only have Exchange and Personal (IMAP). So I can't seem to be able to select a Google Account.
Presently I have nothing on the tablet I need (i.e. no data I need to keep) so if I have to start again I am happy to do that but I'm just learning so saying 'flash the rom' or such is too vague for me at this stage. I'm also not sure what or how to get 'data as f2fs' if that is important.
If someone could assist with a clear step by step of how I might resolve these issues I'd be very grateful. Happy to provide any other info sought. Not sure if this was caused when the seller wiped his personal data before selling or what, he says Play Store was working, so don't know if he bungled the rooting or what.
I got your PM and first of all, congrats you did a good amount of reading and you are on the right track.
Your problems with Google account and Play Store are probably due to either the wrong gapps (Google apps) version or the previous owner did a wipe of /data and did not reflash properly. Yep, arm 6.0 is right, but it has to be the pico edition. Since you did buy the tablet used, it probably would be a good idea to start from scratch. At least you would then know that if something won't work, it's because of something you did.
And yes, I agree with the advice to flash the Kang TWRP recovery. I have no idea if CWM supports f2fs but I don't think so. Most people use TWRP as recovery - it's the right way to go.
So let's get you prepped:
Download the rom, gapps and SuperSU from the links in Tim's thread (first post) and put them on a microSD. http://forum.xda-developers.com/transformer-tf700/development/rom-t3282166
Then head here and download the flashable zip of the Kang TWRP recovery: http://forum.xda-developers.com/showpost.php?p=59299365&postcount=2
Also copy that to the microSD
Boot into CWM recovery, go to Install and navigate to the Kang TWRP zip.
To tell the truth I can't even remember if CWM supports the microSD but I think it does. If it doesn't you have to use adb to push the zip to internal memory and then flash it from there.
Anyway, flash the Kang TWRP and then reboot. Let it boot up, then turn the tablet off and boot via buttons (Power and Vol Down to get into bootloader, VolUp on flashing RCK) into recovery which should be TWRP at this time.
Go to Wipe > Format data > type "Yes" and go have a beer (did I mention the battery needs to be full before you start?). This will take 60 minutes plus and may look as if nothing happens but it does, don't mess with it!
Once that is done follow this guide to convert internal data to f2fs: http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
Start at step 4 and ignore any instructions related to data2sd/rom2sd.
Alright, now you got a squeaky clean tablet itching for a rom.
In TWRP go to Install > navigate to the microSD and select the rom zip. If you like, you can line up the other two files to be flashed right after the rom zip:
Touch: Add another zip, and repeat this for both the gapps and the supersu zips.
Or you flash them one by one - doesn't matter. But all 3 have to be flashed without rebooting in between and the rom has to be first!
Make sure "verify zip signature" is not checked, then swipe the button.
Have another beer
Once it's done, reboot to system and set up your new rom.
You definitely want to install the SuperSU app from the Play Store. You gain root by flashing the SuperSU zip, but you need the app to manage root.
If anything is unclear: Ask!
Have fun!
I'm up to the part where I get to have a beer...haaa. Wasn't all plain sailing. Having TWRP as an img file wasn't recognised on the sd card so I was unable to flash twrp that way. I managed to push twrp using ADB. (The small issue I had here originally was when I renamed the img file from say twrp-2.8.x.x-xxx.img to twrp.img (for ease of typing in adb) it was really twrp.img.img as it appears with a zip icon on my XP. After realising this it was straightforward after putting twrp.img into the adb folder and connecting the device and accessing the command prompt:
C:\adb>adb devices (to check I'm connected)
response:
List of devices attached
(numbers&letters here) device
C:/adb>adb reboot bootloader
This reboots the device into the bootloader and you hear the device buzz
C:/adb>fastboot flash recovery twrp.img
response
sending 'recovery' (7038kb)
Okay
writing 'recovery'
Okay
finished total time etc
then
c:/adb>fastboot reboot
rebooting....
I then used the power vol down buttons and yahoo I'm in TWRP and currently at the wipe data phase.
Can't tell you how much I appreciate this help and I'll repost a report after I get further along. Hope this helps others also.
Unexpected Clean Android waiting for a ROM
Beers were great. I finished the bit of 'convert internal data to f2fs' and thought when I rebooted, well don't know what I expected but 'squeaky clean tablet itching for a rom' wasn't a still present KatKiss rom logo start but that's what happened. Then I went to 'Install > navigate to the microSD and select the rom zip' and nothing on the SD card seemed to be recognised other than a self created 'LOST.DIR' directory so I copied the files into this directory ( Heh, at least it can see this directory). So I'm now in the process of installing KatKiss, Gapp 6 pico and SU User Beta.
If I'm on the wrong track here please let me know. Cheers
Paul;
No, you're doing good. You formatted /data, so did not touch /system where the rom lives. That's why your old room still boots. /system gets formatted during installation of the new rom = squeaky clean.
Sent from my Nexus 5X using Tapatalk
berndblb said:
No, you're doing good. You formatted /data, so did not touch /system where the rom lives. That's why your old room still boots. /system gets formatted during installation of the new rom = squeaky clean.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I've completed all the instructions - changed data to f2fs and then starting with the Katkiss, then Gapp pico and SuperSU (adding one zip after the other) and rebooted. Rebooted and device installed 73 apps and took me to a welcome screen with a language dropdown and a swipe button. I can access and change the language but the swipe button won't work so I'm locked on this screen. I went back to TWRP and pressed 'reboot' but what happened was the reboot button(located bottom right), settings button above it and the two bottom buttons on the left disappeared... so from there it wouldn't reboot. I had to hold the power button down to reboot and back in the flash screen but still can't get past that.
plato2 said:
I've completed all the instructions - changed data to f2fs and then starting with the Katkiss, then Gapp pico and SuperSU (adding one zip after the other) and rebooted. Rebooted and device installed 73 apps and took me to a welcome screen with a language dropdown and a swipe button. I can access and change the language but the swipe button won't work so I'm locked on this screen. I went back to TWRP and pressed 'reboot' but what happened was the reboot button(located bottom right), settings button above it and the two bottom buttons on the left disappeared... so from there it wouldn't reboot. I had to hold the power button down to reboot and back in the flash screen but still can't get past that.
Click to expand...
Click to collapse
Heck! I did not think we needed to check your bootloader if it had Katkiss on it, but now I think we do:
Boot into fastboot and read the tiny text top left. The part with 10.6.1...... is what we need
Bootloader problem now! More beer required....
berndblb said:
Heck! I did not think we needed to check your bootloader if it had Katkiss on it, but now I think we do:
Boot into fastboot and read the tiny text top left. The part with 10.6.1...... is what we need
Click to expand...
Click to collapse
OK, I went back to the wipe data bit and did it all again.... I noted that when installing the Katkiss, Gapps and SuperU zips I saw 2 lines:
checking for md5 file
skipping md5 check: No md5 file found
Have no idea if it matters or not....
OK the tiny writing at top on fastboot (why does this have to be so small....really).
Anyway it says:
Key Driver not found.. booting as
Android CardHU-User Bootloader <2.0 e> released by "ww_epad-10.6.1.14.10-2013601" A?3
It is hard to be exact with it that small so hope that helps, but the 10.6.1.14.10 is correct can't be as sure with the last numbers though.
Thinking about a solution
plato2 said:
OK, I went back to the wipe data bit and did it all again.... I noted that when installing the Katkiss, Gapps and SuperU zips I saw 2 lines:
checking for md5 file
skipping md5 check: No md5 file found
Have no idea if it matters or not....
OK the tiny writing at top on fastboot (why does this have to be so small....really).
Anyway it says:
Key Driver not found.. booting as
Android CardHU-User Bootloader <2.0 e> released by "ww_epad-10.6.1.14.10-2013601" A?3
It is hard to be exact with it that small so hope that helps, but the 10.6.1.14.10 is correct can't be as sure with the last numbers though.
Click to expand...
Click to collapse
I've done a bit of reading and I'm currently downloading ww_10_6_1_18_SDupdate.zip
I think my next step will be to unzip this file and find the T4_SDupdate file and put it on the sdmicro in root and boot into recovery. I'm guessing it will be located and the update begin. After that I'm not sure of what to expect. Will I have to go and flash twrp, wipe date, change to f2fs and install Katkiss,Gapps and SuperSU again? Will it matter if other files (TWRP, Katkiss, Gapps,SuperSU) are also on the microsd while this happens. If you could let me know if I'm on the right track that would be great.
plato2 said:
I've done a bit of reading and I'm currently downloading ww_10_6_1_18_SDupdate.zip
I think my next step will be to unzip this file and find the T4_SDupdate file and put it on the sdmicro in root and boot into recovery. I'm guessing it will be located and the update begin. After that I'm not sure of what to expect. Will I have to go and flash twrp, wipe date, change to f2fs and install Katkiss,Gapps and SuperSU again? Will it matter if other files (TWRP, Katkiss, Gapps,SuperSU) are also on the microsd while this happens. If you could let me know if I'm on the right track that would be great.
Click to expand...
Click to collapse
Sorry, that should be 22_10_26_1_18_SDupdate.zip
plato2 said:
Sorry, that should be 22_10_26_1_18_SDupdate.zip
Click to expand...
Click to collapse
Third time luck...(should be) ww_10_26_1_18_SDupdate.zip
plato2 said:
Third time luck...(should be) ww_10_26_1_18_SDupdate.zip
Click to expand...
Click to collapse
Don't do that!!
Whatever it is that is not firmware for the TF700!
You are on the latest bootloader, no reason to mess with it!!
---------- Post added at 09:29 AM ---------- Previous post was at 09:28 AM ----------
Give me some time, I'll get back to you
Sent from my Nexus 5X using Tapatalk
That was TF701 firmware you were thinking to flash. It is totally incompatible with your tablet and the T4 SD Update method works only with stock recovery. But all that aside....
Ok, what you experience is quite weird and I have no idea what caused it. Maybe a bad download maybe something went wrong during the flash - I have no idea...
So what is your situation now? Can you reboot from TWRP? Does the recovery work normally?
Because if not, that is the first thing you need to fix.
You may want to reflash TWRP anyway - just to be sure it did not get corrupted. You know how to flash in fastboot - excellent! Then let's do it that way.
Download from the first link for Kang TWRP 2.8.7.4. https://www.androidfilehost.com/?fid=24352994023705509
Look at the info under "Download information" on that page: You'll see the md5 checksum for that file. That is control value to make sure the file you downloaded is complete and not corrupted.
You'll need a small program like Hashtab on your PC to check the md5. Install it, then right click on a zip, go to Properties and there you'll see a new tab: FileHashes. Copy the string from the download page into the "Compare" box and it instantly tells you if the file you have on your PC matches the one on the server. TWRP has a feature that it will compare the md5 if you have it along with the zip in form of a small text file on your microSD. If it doesn't find a md5 it just skips the integrity check.
Your microSD - something else to check. That TWRP doesn't see the downloaded files unless they are in the LOST directory is totally crazy. How is that microSD formatted? You got another one you can use? One that actually works and does not add another question mark to this situation? If not, at least format the microSD to fat32 on your PC, load your files and then check if TWRP sees them. Also check the md5 AFTER copying the files to the card.....
Do that with all the files you downloaded.
So, first thing is to flash TWRP again. Then make sure it works, you can reboot from it etc.
Then just perform a quick wipe in TWRP. From Home select Wipe > swipe the button > done
Then reflash the rom zip, gapps and supersu on which you checked the md5.
Let me know how that goes.....
Thanks for that info. No I wasn't going to do anything stupid without you OKing it first.
I redownloaded Kang TWRP 2.8.7.4 and pushed it again successfully with adb no problem. I am still unable to reboot from bootloader using adb or pressing reboot... these problems weren't present prior to installing Katkiss, Gapps and SuperSU. Still frozen on front screen of rom. I put the twrp.img file onto the micro SD Card and tried to flash. It gives me an option to select staging which I didn't tick so it tells me no partitions selected for flashing. Didn't want to tick something and stuff it up. I think TWRP is OK as it did work fine before I installed the other 3 programs.
The micro SD is fine it's FAT32 formatted. The issue with the recovery program not seeing the zip files in the root dir was when I was using CWM - no longer a problem.
plato2 said:
Thanks for that info. No I wasn't going to do anything stupid without you OKing it first.
I redownloaded Kang TWRP 2.8.7.4 and pushed it again successfully with adb no problem. I am still unable to reboot from bootloader using adb or pressing reboot... these problems weren't present prior to installing Katkiss, Gapps and SuperSU. Still frozen on front screen of rom. I put the twrp.img file onto the micro SD Card and tried to flash. It gives me an option to select staging which I didn't tick so it tells me no partitions selected for flashing. Didn't want to tick something and stuff it up. I think TWRP is OK as it did work fine before I installed the other 3 programs.
The micro SD is fine it's FAT32 formatted. The issue with the recovery program not seeing the zip files in the root dir was when I was using CWM - no longer a problem.
Click to expand...
Click to collapse
There's some fundamental flaw in your thinking: You cannot flash the .img file in TWRP.
twrp_tf700t_kang_2.8.7.4.img - this file you have to flash in fastboot (fastboot flash recovery twrp_tf700t_kang_2.8.7.4.img)
twrp_tf700t_kang_2.8.7.4-signed.zip - this is the same recovery packaged into a flashable zip. This you can flash in recovery
I am still unable to reboot from bootloader using adb or pressing reboot... these problems weren't present prior to installing Katkiss, Gapps and SuperSU
Click to expand...
Click to collapse
You mean rebooting from recovery??? That sentence does not make sense. And something else is going on. Flashing a rom, gapps, supersu cannot have anything to do with your recovery not working properly. The recovery lives on it's own partition and boots from there.
Maybe time to take a break and retrace your steps. I cannot put my finger on it but somewhere you are doing something wrong.
Edit: Ha! Interesting! Just remembered that something changed in TWRP and yes, this latest version lets you flash an .img file to staging (from where it will get installed to it's proper partition during the next boot). I have no idea how solid this new feature is, so I'd still recommend falshing TWRP in fastboot.
But 2.8.7.4 works fine flashing Katkiss and associated files. Tried it myself this afternoon. All the components work. So the problem is most likely in the "how", not the "what".....
Sorry for the confusion. Really can't see what I may be doing wrong here. I followed exactly the same procedure as I did when I installed TWRP over CWM initially. I re-downloaded twrp_tf700t_kang_2.8.7.4.img , placed it in the adb folder and renamed it twrp.img. I then followed the same procedure I did originally:
C:\adb>adb devices (to check I'm connected)
response:
List of devices attached
(numbers&letters here) device
C:/adb>adb reboot bootloader
This reboots the device into the bootloader and you hear the device buzz
C:/adb>fastboot flash recovery twrp.img
response
sending 'recovery' (7038kb)
Okay
writing 'recovery'
Okay
finished total time etc
then
c:/adb>fastboot reboot
rebooting....
However, this time the response to the last command:
c:/adb>fastboot reboot
(waiting for device) and it hangs and the device doesn't reboot from recovery. However, all the other stuff before it is the same. Not sure what to try next.
plato2 said:
However, this time the response to the last command:
c:/adb>fastboot reboot
(waiting for device) and it hangs and the device doesn't reboot from recovery. However, all the other stuff before it is the same. Not sure what to try next.
Click to expand...
Click to collapse
Elaborate on this please.
You are in fastboot.
The command fastboot reboot does nothing?
Then what? Did you reboot manually?
You are not in recovery here, so i do not understand "the device does not reboot from recovery".....
Sorry, my lack of understanding. I suppose I mean I am in the bootloader which is where adb>reboot>bootloader puts me so that I can flash twrp.img. Then to get out of there and go back to the rom fastboot>reboot would put me back into the rom and I would get the response >rebooting. Now that doesn't happen it simply says (waiting for device)....So I have to reboot manually.
Just got home and playing around with it. I went into the bootloader and installed just the katkiss rom. It installed fine and then I clicked reboot and it rebooted no problem. But of course that doesn't give me any Play Store or SuperSU.... so there's still hope. So now I'm back in the bootloader and going to try the 3 together again and see what happens.Let you know shortly
Setup wizerd stopped - google play services stopped
plato2 said:
Just got home and playing around with it. I went into the bootloader and installed just the katkiss rom. It installed fine and then I clicked reboot and it rebooted no problem. But of course that doesn't give me any Play Store or SuperSU.... so there's still hope. So now I'm back in the bootloader and going to try the 3 together again and see what happens.Let you know shortly
Click to expand...
Click to collapse
So now when I install the katkiss, Gapps and SuperSU from TWRP and reboot I get 2 repeating messages Setup wizerd has stopped' and Google Play Services has stopped. It just goes from one to the other when I press OK....
I was trying to apply the installation of the eXistenZ (https://forum.xda-developers.com/xz...om-existenz-pie-v3-5-0-beta-31-01-19-t3895452)
But aside from that I found the following problem:
Following the instructions I downloaded the last ROM, I specifically downloaded the G8141_Customized UK_1308-5320_47.2.A.10.62_R3C
First of all I made a clean flash and restart, then I installed the TWRP v.3.3.1 via ADB, next the Magisk 19.3, later reboot the system normally and finally a tried to do the part of rebooting in the recovery and wiping data, cache, dalvic, etc.
However I noted that when the system started up the first time (after flashing) it appears a legend describing a process of encryption, it said the cel phone was going to be encrypted and it restarted once again.
When I start in the recovery mode and slide the bar to authorize to modify system partition nothing happens.
The first try I stored the Magisk.apk file in the internal memory but in TWRP interface the system partition is not mounted, the storage space says is 0 GM (or mb).
I started up the system one more time, trying to disable the encrypted function but is not possible, I disable Find my Device function as administrator maybe thinking it was the reason deactivating encryption was blocked but nothing.
I have to mention that when I enter recovery mode is not asking me to enter any pass or pin as it does when there is a pin protected phone.
Please can anyone help me to find the solution to this problem
Zur75 said:
I was trying to apply the installation of the eXistenZ (https://forum.xda-developers.com/xz...om-existenz-pie-v3-5-0-beta-31-01-19-t3895452)
But aside from that I found the following problem:
Following the instructions I downloaded the last ROM, I specifically downloaded the G8141_Customized UK_1308-5320_47.2.A.10.62_R3C
First of all I made a clean flash and restart, then I installed the TWRP v.3.3.1 via ADB, next the Magisk 19.3, later reboot the system normally and finally a tried to do the part of rebooting in the recovery and wiping data, cache, dalvic, etc.
However I noted that when the system started up the first time (after flashing) it appears a legend describing a process of encryption, it said the cel phone was going to be encrypted and it restarted once again.
When I start in the recovery mode and slide the bar to authorize to modify system partition nothing happens.
The first try I stored the Magisk.apk file in the internal memory but in TWRP interface the system partition is not mounted, the storage space says is 0 GM (or mb).
I started up the system one more time, trying to disable the encrypted function but is not possible, I disable Find my Device function as administrator maybe thinking it was the reason deactivating encryption was blocked but nothing.
I have to mention that when I enter recovery mode is not asking me to enter any pass or pin as it does when there is a pin protected phone.
Please can anyone help me to find the solution to this problem
Click to expand...
Click to collapse
Wipe cache and data
To factory reset and then boot your system
Turn off / flash twrp/ restart/turn off / enter twrp/ magisk / restart to twrp/flash existenz/ reboot
You will loose all data
Yes i have same problem. When use TWP Swipe but always failed
I try use flashtools, flash .ftf firmware .62 and choose all swipe in box Flashtools.
Now, folder is working.
You can try.
ngocthang26 said:
Yes i have same problem. When use TWP Swipe but always failed
I try use flashtools, flash .ftf firmware .62 and choose all swipe in box Flashtools.
Now, folder is working.
You can try.
Click to expand...
Click to collapse
I'm sorry, didn't understand you, did you fallow the sequence karrouma gave me in the first answer?