I originally had Katkiss 4.3 v19 and it was working fine. I then wanted to update to the recent 4.3.1 v27 but when I tried to flash the new ROM, it says that it can't open the zip file and failed. I backed up beforehand, so I wiped the cache and dalvik. I then tried to flash the ROM again, but it still says failed. I went to restore the backup to go back and for some reason, it is also failing.
I have TWRP 2.6.0.0 and I am stuck in recovery where I can't flash anything. Not even when I wanted to flash to stock.
I have the Asus EEE transformer tf101 tablet.
How do I fix this?
Please Help.
Are you trying to flash from Micro SDCard ?
Maybe the card has corrupted - try formatting the card in a PC, then copy #27 back to it, and try flashing again
Or try another MicroSD Card
*Detection* said:
Are you trying to flash from Micro SDCard ?
Maybe the card has corrupted - try formatting the card in a PC, then copy #27 back to it, and try flashing again
Or try another MicroSD Card
Click to expand...
Click to collapse
I did this and it says successful but I don't think it's completely flashed because the last line says E:Unable to mount '/staging'. Plus when I reboot, it just goes back to recovery. I flashed SuperSU but it didn't change anything.
EDIT: Ok. So I tried flashing any rom and it says 'successful', yet it seemed like it flashed the rom too quickly. Afterwards, I'd reboot but it just goes from the Eee transformer logo to twrp recovery. This happens to all of the 'successful' flashes. When I tried to flash the stock rom, it would just say failed.
I really don't know what to do at this point. I tried formatting the SD card, changing the SD card, reinstalling twrp using the EasyRecovery app and I wiped my internal and external data (which I think is the problem and IDK how to recover them). I even tried flashing a new recovery (CWM) and, like the other 'successful' flashes, still goes back to TWRP.
gigases said:
I did this and it says successful but I don't think it's completely flashed because the last line says E:Unable to mount '/staging'. Plus when I reboot, it just goes back to recovery. I flashed SuperSU but it didn't change anything.
EDIT: Ok. So I tried flashing any rom and it says 'successful', yet it seemed like it flashed the rom too quickly. Afterwards, I'd reboot but it just goes from the Eee transformer logo to twrp recovery. This happens to all of the 'successful' flashes. When I tried to flash the stock rom, it would just say failed.
I really don't know what to do at this point. I tried formatting the SD card, changing the SD card, reinstalling twrp using the EasyRecovery app and I wiped my internal and external data (which I think is the problem and IDK how to recover them). I even tried flashing a new recovery (CWM) and, like the other 'successful' flashes, still goes back to TWRP.
Click to expand...
Click to collapse
The /staging/ error is normal, nothing to worry about.
Question, if you shut down the tablet from recovery. Then turn it on with a 3 second power button press, does it go directly to recovery?
If so, this is causing your tablet NOT to finish the flash when it reboots. It needs to reboot normally and you should see the Eee Pad logo with a progress indicator.
If you do have a recovery boot loop, try this. Boot to recovery and go to the Advanced section and open a terminal window.
Code:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Then reboot normally (not to recovery). Then after it tries to boot not into recovery, boot back to recovery and try restoring your 019 backup.
frederuco said:
The /staging/ error is normal, nothing to worry about.
Question, if you shut down the tablet from recovery. Then turn it on with a 3 second power button press, does it go directly to recovery?
If so, this is causing your tablet NOT to finish the flash when it reboots. It needs to reboot normally and you should see the Eee Pad logo with a progress indicator.
If you do have a recovery boot loop, try this. Boot to recovery and go to the Advanced section and open a terminal window.
Code:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Then reboot normally (not to recovery). Then after it tries to boot not into recovery, boot back to recovery and try restoring your 019 backup.
Click to expand...
Click to collapse
Yes. When I reboot/shutdown from recovery, it shows the eee pad and nvidia logo on the bottom and then goes to recovery. I did what you said with the terminal window. I also typed in the code. and it says:
5+0 records in
5+0 records out
5 bytes (5B) copied,
0.006015 seconds, 831B/s
Afterwards, I rebooted normally and it still goes back to recovery. It doesn't even go to the 'ASUS' logo where there is a wheel on the bottom.
gigases said:
Yes. When I reboot/shutdown from recovery, it shows the eee pad and nvidia logo on the bottom and then goes to recovery. I did what you said with the terminal window. I also typed in the code. and it says:
5+0 records in
5+0 records out
5 bytes (5B) copied,
0.006015 seconds, 831B/s
Afterwards, I rebooted normally and it still goes back to recovery. It doesn't even go to the 'ASUS' logo where there is a wheel on the bottom.
Click to expand...
Click to collapse
May need to do it from an ADB shell, but adb shell is blocked on TWRP 2.6.X.X for security reasons.
I would suggest flashing TWRP again using EasyFlasher. See my guide here: www.transformerforums.com/forum/asu...nt/31927-frederucos-guide-root-rom-tf101.html . Grab one of the repacked versions with TWRP 2.6 and you should be back in business in no time.
I did everything and it all seemed fine. Now I'm in a bootloop. I used the TWRP 2.6.3.0 EasyFlasher
Okay. I just tried other recoveries (CWM and Rogue) and they seemed to go well. I tried flashing, yet it still does the same thing as before where it goes to the logo and then to the recovery.
gigases said:
I did everything and it all seemed fine. Now I'm in a bootloop. I used the TWRP 2.6.3.0 EasyFlasher
Okay. I just tried other recoveries (CWM and Rogue) and they seemed to go well. I tried flashing, yet it still does the same thing as before where it goes to the logo and then to the recovery.
Click to expand...
Click to collapse
At this point, I would try restoring stock using EasyFlasher. Just download the asus firmware file and leave it as is (do not unzip) and put it in the asusupdate folder in EasyFlasher.
Once you flash back to stock and can boot, then flash TWRP with EasyFlasher and you should be good to go.
frederuco said:
At this point, I would try restoring stock using EasyFlasher. Just download the asus firmware file and leave it as is (do not unzip) and put it in the asusupdate folder in EasyFlasher.
Once you flash back to stock and can boot, then flash TWRP with EasyFlasher and you should be good to go.
Click to expand...
Click to collapse
That did it. I flashed back to stock and it can boot again. I'll flash TWRP again.:fingers-crossed: Thank You
Any time! I have a few EasyFlashers with newer versions of TWRP in the EasyFlasher thread. Start and the end and read backwards to find them.
Related
I sent my transformer in to Asus because the screen did not turn on anymore. I just received it back and am having an assortment of issues:
1. If I boot it up normally, it books straight into clockworkmod recovery. The only way to boot into the normal system is to go into Asus recovery and cancel wiping data.
2. If I try to flash a new rom in recovery, it just resets the aokp rom that I currently have on there. I also tried flashing new recoveries from Rom Manager, and it says they were successfully flashed, but it is always the same recovery when it restarts.
I have tried fixing permissions, doing a wipe in Asus recovery, doing a complete wipe in CWM recovery, putting the update.zip on the root of the SD card (it doesn't detect it)...I am really at a loss here. The tablet is definitely rooted and I confirmed busybox was installed. Any ideas?
if you can NVFlash something. And try using gnufabio's recovery installer instead of rom manager
mrevankyle said:
if you can NVFlash something. And try using gnufabio's recovery installer instead of rom manager
Click to expand...
Click to collapse
Good call, I am going to try the NVFlash method.
Hello Forum! I've come here for a little help! Here's My Story.
After running Cyanogen 10.1 Nightlies on 4.2.2 for quite some time, I decided to do a factory reset because my TF300T seemed to be running a little slugish. I DID NOT back it up (mistake #1), DID NOT have USB Debugging on (mistake #2), and, while CWM was wiping /data, I shut off the tablet (STRIKE THREE). Prior to my bonehead move, I had everything else squared away. The unit was fully functional. Now, I'm stuck in this infernal boot loop on the ASUS screen.
I can reboot into recovery, so CWM is not compromised. I have tried to push a new ZIP of the ROM via ADB (unsuccessful, thinking the drivers are nerfed) and through CWM (also unsuccessful).
If anyone has any ideas, please feel free to comment.
P.S. Please don't kill me Mods, I'll be good after this
Update:
After looking through the forums more I tried all of these:
Installed the Universal Naked Driver (Sorta Worked)
Reflashed the system blob from the most recent CyanogenMod Nightly (Says it wrote, I doubt it did)
Went into CWM, tried to Sideload the CM zip (Didn't work)
Then, I took my external SD, placed the CM zip onto it, rebooted the tablet w/ the SD in it, booted into CWM, TRIED a full system wipe (couldn't mount /data), and reflashed the ROM. That worked! ... sorta. Upon "successful install", I had CWM reboot the TF300T. It came to the ASUS Screen w/ a progress bar (went from 1% to 100% within a second). However, after that, it went back to the bootloop ASUS screen
I feel like I'm close on this one, any tips?
Kazman101 said:
Update:
After looking through the forums more I tried all of these:
Installed the Universal Naked Driver (Sorta Worked)
Reflashed the system blob from the most recent CyanogenMod Nightly (Says it wrote, I doubt it did)
Went into CWM, tried to Sideload the CM zip (Didn't work)
Then, I took my external SD, placed the CM zip onto it, rebooted the tablet w/ the SD in it, booted into CWM, TRIED a full system wipe (couldn't mount /data), and reflashed the ROM. That worked! ... sorta. Upon "successful install", I had CWM reboot the TF300T. It came to the ASUS Screen w/ a progress bar (went from 1% to 100% within a second). However, after that, it went back to the bootloop ASUS screen
I feel like I'm close on this one, any tips?
Click to expand...
Click to collapse
I would try to install TWRP recovery since CWM is sometimes a bit flaky, I would use TWRP 2.3.3.0 since I believe is the most stable but you can install the latest one 2.4.4.0, then flash the blob file via fastboot (instructions are at the twrp site) and repeat the same process as you did with CWM, wipe everything and then flash CM.zip from external SD and see if it works that way. If that does not work, try reflashing the stock system blob from Asus this time using fastboot and that will put you completely stock and then you can start over.
hope it helps.
Erik
ricco333 said:
I would try to install TWRP recovery since CWM is sometimes a bit flaky, I would use TWRP 2.3.3.0 since I believe is the most stable but you can install the latest one 2.4.4.0, then flash the blob file via fastboot (instructions are at the twrp site) and repeat the same process as you did with CWM, wipe everything and then flash CM.zip from external SD and see if it works that way. If that does not work, try reflashing the stock system blob from Asus this time using fastboot and that will put you completely stock and then you can start over.
hope it helps.
Erik
Click to expand...
Click to collapse
It Unbricked!
Step 1: Flashed TWRP 2.4.4.0 blob file to overwrite CWM (Check)
Step 2: Factory Reset and Wipe Entire Device (CHECK!?!?!)
Step 3: Flash CM.zip!?!?! (Not So Check ... PLAN B!)
Downloaded Chinese Stock system blob (don't ask, I know it was stupid, but go with me here)
Flashed the system blob (after 3 minutes ... SUCCESS!)
No more boot loop and back to stock ... now to root it again to get my sweet CyanogenMod back ...
Thank you Erik, your help was much appreciated!
I restored a Nandroid backup within TWRP and now the TF101 is in a TWRP recovery script bootloop.
When I start the I see after the standard ASUS screen the Teamwin screen and after that the text:
"Updating partition details...
Formating cache using make_ext4fs
Done.
Wiping data without wiping /data/media ...
Done."
And than it reboots instantly.
When hold volume down that I see before the Teamwin screen the text:
"Wiping user data and any indicator before cold booting Linux.
Please wait a few minutes ...
Booting recovery kernel image."
With volume up TF101 goes evently off.
When I connect the TF101 to my PC it is recognized, but connection is lost every time it boots.
How can I restore TWRP recovery image?
Possible that your Nandroid backup is corrupted, or maybe a problem with TWRP
Try flashing TWRP again with Easyflasher then try to restore your backup again
If it fails, try flashing a ROM and see if you can get it to boot, if you can, looks like a bad Nandroid backup
I tried both, and both failed. I need to know how to stop the TWRP script from running, because it is keeping wiping something.
If you have an SBK1 device (B6O or earlier, some B7O Serials) you could use a stock NVFlash ROM to wipe TWRP back to stock recovery, then use Easyflasher to get TWRP back again, then flash your backup again
Code:
http://www.xdafileserver.nl/Files/Asus/Asus%20Transformer%20(TF101)/STOCK%20ROMS/ICS%20.27/NVFLASH_ICS_9.2.1.27_US_NOROOT.7z
Extract > Put TF into APX Mode > Run Download.bat as Admin > Wait
*Detection* said:
If you have an SBK1 device (B6O or earlier, some B7O Serials) you could use a stock NVFlash ROM to wipe TWRP back to stock recovery, then use Easyflasher to get TWRP back again, then flash your backup again
Code:
http://www.xdafileserver.nl/Files/Asus/Asus%20Transformer%20(TF101)/STOCK%20ROMS/ICS%20.27/NVFLASH_ICS_9.2.1.27_US_NOROOT.7z
Extract > Put TF into APX Mode > Run Download.bat as Admin > Wait
Click to expand...
Click to collapse
It is a B70 SBK2.
Joh14vers6 said:
It is a B70 SBK2.
Click to expand...
Click to collapse
I was wrong.
First I was not putting the device really in APX-mode,. Another recent posting made me that clear. Seccond, although it a B70 it seems to be a SBK1.
Only problem now that is not loading the boatloader.bin completely. In succesive tries it random hangs at some point (6%, 27%, 48%, 90%). What can I do to solve this?
*Detection* said:
If you have an SBK1 device (B6O or earlier, some B7O Serials) you could use a stock NVFlash ROM to wipe TWRP back to stock recovery, then use Easyflasher to get TWRP back again, then flash your backup again
Code:
http://www.xdafileserver.nl/Files/Asus/Asus%20Transformer%20(TF101)/STOCK%20ROMS/ICS%20.27/NVFLASH_ICS_9.2.1.27_US_NOROOT.7z
Extract > Put TF into APX Mode > Run Download.bat as Admin > Wait
Click to expand...
Click to collapse
I changed to another computer and then the boatloader was loading, but flashing was afterwards still not succesfull. Then I tried to flash a stock ROM within Easyflasher (2x), but ended in a TF that always start in APX-mode.
Then I tried the link above, with the only diference that I changed US to WW and now my TF101 is revived.
Thank you very much!!!
Joh14vers6 said:
I changed to another computer and then the boatloader was loading, but flashing was afterwards still not succesfull. Then I tried to flash a stock ROM within Easyflasher (2x), but ended in a TF that always start in APX-mode.
Then I tried the link above, with the only diference that I changed US to WW and now my TF101 is revived.
Thank you very much!!!
Click to expand...
Click to collapse
Great!
First off, let me start out by saying that the Infinity is running on what is possibly the worst software ever designed. Props, Asus. You've made my life hell until the last second.
So, here's my problem. The tablet was working fine 24 hours ago. I turned it off last night, turned it on this morning, working great on CROMi-Xeno (which is awesome, it actually makes the tablet bearable.) and played on it for a while before turning off again. While playing it, I noticed it lag a little more than usual, so I decided to cold boot it. Booted bootloader, hit cold boot, and.... bootlooping. Awesome. No biggie, I'll just restore a backup. I waited for it to restore, and when it was finished, wiped cache and Dalvik, and.... bootlooping again. I tried wiping system and data. Still bootlooping. I downloaded Asus 's official firmware from their website, and flashed. Bootlooping. Someone help me fix this and get it back to stock firmware, so I can sell it and be done with it once and for all. I will never buy another Asus product again.
greydelta38 said:
First off, let me start out by saying that the Infinity is running on what is possibly the worst software ever designed. Props, Asus. You've made my life hell until the last second.
So, here's my problem. The tablet was working fine 24 hours ago. I turned it off last night, turned it on this morning, working great on CROMi-Xeno (which is awesome, it actually makes the tablet bearable.) and played on it for a while before turning off again. While playing it, I noticed it lag a little more than usual, so I decided to cold boot it. Booted bootloader, hit cold boot, and.... bootlooping. Awesome. No biggie, I'll just restore a backup. I waited for it to restore, and when it was finished, wiped cache and Dalvik, and.... bootlooping again. I tried wiping system and data. Still bootlooping. I downloaded Asus 's official firmware from their website, and flashed. Bootlooping. Someone help me fix this and get it back to stock firmware, so I can sell it and be done with it once and for all. I will never buy another Asus product again.
Click to expand...
Click to collapse
I'm wondering if my version of TWRP is too old or something. Can anyone explain in detail how to update to a newer version of TWRP or install CWM in order for flashing to fully work?
greydelta38 said:
I'm wondering if my version of TWRP is too old or something. Can anyone explain in detail how to update to a newer version of TWRP or install CWM in order for flashing to fully work?
Click to expand...
Click to collapse
what version do you currently have, just download the .blob from twrp's site boot into fastboot and run "fastboot flash recovery *name of blob*.blob"
JoinTheRealms said:
what version do you currently have, just download the .blob from twrp's site boot into fastboot and run "fastboot flash recovery *name of blob*.blob"
Click to expand...
Click to collapse
Yeah - I'm also wondering what bootloader you are running with it.
If you are not current on either flash the bootloader/TWRP package from CROMi-X OP, boot back into system, let it bootloop if it does, boot back into TWRP and reflash the rom.
That seems like it would be the only explanation, but now it won't even boot into recovery. I can get it into fastboot, but as soon as I select recovery image it shows the firmware upgrade symbol and then immediately shows the Android Error symbol, and sticks there until I hard power down. When I'm in fastboot, here's what I'm gonna do:
1. connect fastbooted Infinity to pc with all necessary drivers installed
2. download filename.blob from TWRP's website for the Infinity
3. on command console enter -fastboot flash recovery filename.blob- and it will push the recovery through fastboot hopefully
Is that correct? I'm under the impression that as long as I can get to the fastboot menu, ANYTHING is repairable.
greydelta38 said:
That seems like it would be the only explanation, but now it won't even boot into recovery. I can get it into fastboot, but as soon as I select recovery image it shows the firmware upgrade symbol and then immediately shows the Android Error symbol, and sticks there until I hard power down. When I'm in fastboot, here's what I'm gonna do:
1. connect fastbooted Infinity to pc with all necessary drivers installed
2. download filename.blob from TWRP's website for the Infinity
3. on command console enter -fastboot flash recovery filename.blob- and it will push the recovery through fastboot hopefully
Is that correct? I'm under the impression that as long as I can get to the fastboot menu, ANYTHING is repairable.
Click to expand...
Click to collapse
The command is
fastboot -i 0x0B05 flash recovery filename.blob
Since you can boot into the bootloader, check the version# and make sure you flash a compatible recovery.
Most of the time, as long as you can get into the BL, it's fixable. But to make it unbrickable you need nvFlash. And that's just become possible for or tablet on JB. May be a project for once you got this problem fixed: http://forum.xda-developers.com/showthread.php?t=2455925
I suspect you need to format data to fix the issues (you'll lose everything on the internal sd card) but before you do follow bernd's recommendation and get TWRP on there (you wiped it out when you flashed ASUS stock) and then use the file explorer in TWRP to copy anything important to an external SD and make sure the cromi-x rom is on sd too. Then format data from the wipe menu and reinstall. You'll be back to normal in no time. :good:
BTW You may have got some corruption from turning f-sync off.
berndblb said:
The command is
fastboot -i 0x0B05 flash recovery filename.blob
Since you can boot into the bootloader, check the version# and make sure you flash a compatible recovery.
Most of the time, as long as you can get into the BL, it's fixable. But to make it unbrickable you need nvFlash. And that's just become possible for or tablet on JB. May be a project for once you got this problem fixed: http://forum.xda-developers.com/showthread.php?t=2455925
Click to expand...
Click to collapse
sbdags said:
I suspect you need to format data to fix the issues (you'll lose everything on the internal sd card) but before you do follow bernd's recommendation and get TWRP on there (you wiped it out when you flashed ASUS stock) and then use the file explorer in TWRP to copy anything important to an external SD and make sure the cromi-x rom is on sd too. Then format data from the wipe menu and reinstall. You'll be back to normal in no time. :good:
BTW You may have got some corruption from turning f-sync off.
Click to expand...
Click to collapse
I tried wiping internal before recovery was lost and it didn't work. I suspected that some problems arose from turning fsync off too. I'm pushing TWRP 2.6 to the Infinity now, will try flashing your excellent rom again and see if it takes without bootlooping.
greydelta38 said:
I tried wiping internal before recovery was lost and it didn't work. I suspected that some problems arose from turning fsync off too. I'm pushing TWRP 2.6 to the Infinity now, will try flashing your excellent rom again and see if it takes without bootlooping.
Click to expand...
Click to collapse
You need to specifically format data in twrp not just wipe data. Only formatting will restore the device now once data corruption has occurred.
Hi,
I have TF101G (WW 9.2.2.6) with ICS 4.0.3 and wanted to upgrade to JB.
For that it has to be rooted.
I downloaded 1-Click Transformer Root (http://forum.xda-developers.com/showthread.php?t=1689193) and rooted it.
Then tried to install recovery: Rogue XM Recovery 1.5.0 (CWM-based Recovery v5.0.2.8).
It installed OK. Tried backup and restore and it worked OK.
Then I wanted to install NO-NAME 4.2 or KatKiss 4.2 and both recommend installing TWRP.
But when I install TWRP (tried with 2.6.3.0 and 2.3.2.3) - tried from XM "Install ZIP", tried dd if=??? of=???
and even went to modify 1-Click and put TWRP blob instead of XM blob.
(I have noticed that all tutorials say of=/dev/block/mmcblk0p4 but 1-Click uses of=/dev/block/mmcblk0p3!!!)
Only through 1-Click I can get to TWRP for the first time only. Any other attempt to go to TWRP finished with
TWRP load screen and some script loads saying something like: "Wiping cache" ... "Clearing data" and
it makes a full factory reset. Every time I try to go to TWRP.
I even restored to stock and tried again - same result.
This is not my first device on which I am installing CM - installed on
Samsung I900 and Tab 10.1, HTC Desire and SE Xperia X8.
What is the highest CM I can istnall from XM 1.5.0?
Can I install 4.2 with XM 1.5.0?
I am doing something wrong here, but what?
Has anyone installed TWRP 2.6.x.x from XM 1.5.0?
Thanks all,
--
Q
You CAN install 4.2 or 4.3 ROMs with XM.
The issue comes in when you go to flash and update, you will get your data that was in the /sdcard/ will appear in the /sdcard/0/ directory. This has to do with the new file structure for the multi users.
If you are already rooted, you can try the terminal method using twrp.blob.
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Reboot normally (not to recovery) to complete the install. Then reboot to recovery.
Also, does your tablet boot to recovery by default? If so, this can cause issues trying to flash a recovery update.
frederuco said:
You CAN install 4.2 or 4.3 ROMs with XM.
Click to expand...
Click to collapse
OK, I'll give it a try!
The issue comes in when you go to flash and update, you will get your data that was
in the /sdcard/ will appear in the /sdcard/0/ directory. This has to do with the new file structure for the multi users.
Click to expand...
Click to collapse
Data is not an issue. I can wipe every upgrade.
If you are already rooted, you can try the terminal method using twrp.blob.
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Reboot normally (not to recovery) to complete the install. Then reboot to recovery.
Click to expand...
Click to collapse
I have tried that. Rebooted several times to system, and even performed a cold boot.
Every time I try to boot to recovery - TWRP performs a factory restore.
One odd thing I have noticed: when I flashed stock or XM recovery after
reboot the blue line lasted a bit. But with TWRP it just flashed quickly,
like it just set some flag and it will do its doing some time later.
Also, does your tablet boot to recovery by default? If so, this can cause issues trying to flash a recovery update.
Click to expand...
Click to collapse
No, it behaves normally. Only XM recovery functions well, so I will stick with it while I can.
Thanks for tips. I will report back with 4.2 progress
LOL, don't upgrade recoveries and roms late at night.
All was OK all along. I was pressing wrong buttons:
VOL.DOWN+POWER - PAUSE - VOL.DOWN - VOL.UP - VOL.UP
instead of
VOL.DOWN+POWER - VOL.UP
I accused of TWRP performing factory resets and that is what it supposed to do.
XM recovery did not know how to do factory reset automatically - and that confused me.
Installed TWRP 2.6.3.0 again and KatKiss 4.2.2. I did not check 3G yet but
I have noticed some screen flickering.
Should I flash fsync_on.zip?
quazy99 said:
LOL, don't upgrade recoveries and roms late at night.
All was OK all along. I was pressing wrong buttons:
VOL.DOWN+POWER - PAUSE - VOL.DOWN - VOL.UP - VOL.UP
instead of
VOL.DOWN+POWER - VOL.UP
I accused of TWRP performing factory resets and that is what it supposed to do.
XM recovery did not know how to do factory reset automatically - and that confused me.
Installed TWRP 2.6.3.0 again and KatKiss 4.2.2. I did not check 3G yet but
I have noticed some screen flickering.
Should I flash fsync_on.zip?
Click to expand...
Click to collapse
Yes, flash fsync_on.zip if you want extra data security. No, if you want better performance with the risk of data corruption if you get random reboots or something.