A week ago, more less, I installed KatKiss-5.0_TF300T_014b.zip on my Asus tf300t and everything was ok until today. When I have turned it on this morning I have noticed that it was staying in a reboot loop.
After that, I tried to reinstall this rom again through TWRP 2.8.0.0 but the reboot was there again. Then I tried to flash CM 11 snapshot m12, but the reboot was earlier. And now i don't know what I should do.
More info: when I flash superSU and gapps, the screen says "E: Unable to mount data" . Perhaps I should do a format data to fix it. What do you think?
Thanks for your answers
sergiolopezsan said:
A week ago, more less, I installed KatKiss-5.0_TF300T_014b.zip on my Asus tf300t and everything was ok until today. When I have turned it on this morning I have noticed that it was staying in a reboot loop.
After that, I tried to reinstall this rom again through TWRP 2.8.0.0 but the reboot was there again. Then I tried to flash CM 11 snapshot m12, but the reboot was earlier. And now i don't know what I should do.
More info: when I flash superSU and gapps, the screen says "E: Unable to mount data" . Perhaps I should do a format data to fix it. What do you think?
Thanks for your answers
Click to expand...
Click to collapse
I actually got the same problem with it when I flashed that. I did a factory reset from TWRP, then reflashed the ROM and Gapps to make the rebooting stop.
Format data??
cmendonc2 said:
I actually got the same problem with it when I flashed that. I did a factory reset from TWRP, then reflashed the ROM and Gapps to make the rebooting stop.
Click to expand...
Click to collapse
I have already tried it (factory reset) and the problem remains. What if i do a "format data"?
sergiolopezsan said:
I have already tried it (factory reset) and the problem remains. What if i do a "format data"?
Click to expand...
Click to collapse
The Format data within TWRP will delete all your apps and settings.
Now my tablet is ok after formatting data.
Related
Hi:
I am quite worried, because my Xoom is unable to boot normally. I have EOS Nightly 99 installed, and after many weeks of perfect bahaviour, it was giving some messages like "gapps has closed", so I restarted the tablet. To my surprise, I saw the Moto lgo, the Tam EOS animation, and the "wheel" that appears before booting completely... and that´s it. Stuck.
I tried wiping dalvik-cache and cache and restart. Same result.
I tried restoring a nandroid backup. And here's the strange thing, because it can't restore data. The error message reads:
Error removing /data/data/com.android.browser/databases/webview.db-wal!Error formatting /data!
I tried wiping userdata, same error message
I tried with another recovery, in case it mattered (cwm and rogue). Same error
EDIT (Update):
I tried accessing the Xoom through ADB, and try to delete manually the pesky file. I was succesful. When I tried another "wipe data" from the recovery, I got a similar error:
Error removing /data/data/com.android.browser/databases/autofill.db (another file)
When I tried to delete it, I got the following error message (through adb) [why did it work the first time and not now???]
rm: can't remove 'autofill.db': Read-only file system
Any help, please? I'm at a loss here...
I post some photos of the errors
iruiz2 said:
Hi:
I am quite worried, because my Xoom is unable to boot normally. I have EOS Nightly 99 installed, and after many weeks of perfect bahaviour, it was giving some messages like "gapps has closed", so I restarted the tablet. To my surprise, I saw the Moto lgo, the Tam EOS animation, and the "wheel" that appears before booting completely... and that´s it. Stuck.
I tried wiping dalvik-cache and cache and restart. Same result.
I tried restoring a nandroid backup. And here's the strange thing, because it can't restore data. The error message reads:
Error removing /data/data/com.android.browser/databases/webview.db-wal!Error formatting /data!
I tried wiping userdata, same error message
I tried with another recovery, in case it mattered (cwm and rogue). Same error
Any help, please? I'm at a loss here...
I post some photos of the errors
Click to expand...
Click to collapse
have you tried re-flashing the rom completely?
daley stephenson said:
have you tried re-flashing the rom completely?
Click to expand...
Click to collapse
Yes, I did try that as well. It flashes without problem (rom + gapps), but does not restart (same original problem). I flashed it after a cache and dalvik-cache wipe.
iruiz2 said:
Yes, I did try that as well. It flashes without problem (rom + gapps), but does not restart (same original problem). I flashed it after a cache and dalvik-cache wipe.
Click to expand...
Click to collapse
ok backup your recovery to your desktop just so it is safe
try this
wipe cache - wipe dalvik cache - wipe/reset factory data - flash rom only then reboot - if it bootloops again enter recovery and go to advanced settings and run fix permissions and reboot
daley stephenson said:
ok backup your recovery to your desktop just so it is safe
try this
wipe cache - wipe dalvik cache - wipe/reset factory data - flash rom only then reboot - if it bootloops again enter recovery and go to advanced settings and run fix permissions and reboot
Click to expand...
Click to collapse
Thanks for your reply.
The problem, in case I wasn't clear, is that I can not make a WIPE DATA (that's when I get the error). It doesn't help wiping cache and dalvik beforehand. So I am in the same bootloop situation. tried fixing permissions, but I continue in the same situation.
iruiz2 said:
Thanks for your reply.
The problem, in case I wasn't clear, is that I can not make a WIPE DATA (that's when I get the error). It doesn't help wiping cache and dalvik beforehand. So I am in the same bootloop situation. tried fixing permissions, but I continue in the same situation.
Click to expand...
Click to collapse
sorry i must of mis-read your op - all i can suggest then is returning to stock using adb guide here http://goo.gl/G09vP then flashing your rom again - just make sure you get the right image for your device
daley stephenson said:
sorry i must of mis-read your op - all i can suggest then is returning to stock using adb guide here http://goo.gl/G09vP then flashing your rom again - just make sure you get the right image for your device
Click to expand...
Click to collapse
I will try this, as a last resort. Now I am making a backup of my internal sd card, because this process will delete everything in it. In case somebody wonders how to do this (I didn't know it myself), I used adb. The exact command I used was:
adb pull /data/media .
It's taking ages to backup my internal sd files (at a rate of 7Gb/hour aprox).
Meanwhile, anybody knows what possibly is happening to my Xoom?
After wating several hours to back up my internal sd card, I have been able to wipe (format) /data from fastboot. In case somebody needs to do something similar:
Once in recovery, type in your computer:
adb reboot bootloader (wait for the xoom to reboot into fastboot)
fastboot erase userdata
I then rebooted into recovery, and restored a nandroid backup. This time, no problems.
Now I am in the (again) long process of copying the /data/media files back to my Xoom, but I was VERY relieved to see that it was booting normally after this...
glad you got it fixed dude
Hey guys, I recently preformed a factory reset in TWRP on my TF300T in preparation for a new rom install. The reset said it failed (odd) and is now showing 0mb of internal storage on my device. I'm stumped. TWRP now asks for a password and I'm not able to load a new rom or anything now. I've looked for a solution online but this issue is only showing results for the Nexus. If anyone can help. I would be in your debt. Thanks!
junglepoison said:
Hey guys, I recently preformed a factory reset in TWRP on my TF300T in preparation for a new rom install. The reset said it failed (odd) and is now showing 0mb of internal storage on my device. I'm stumped. TWRP now asks for a password and I'm not able to load a new rom or anything now. I've looked for a solution online but this issue is only showing results for the Nexus. If anyone can help. I would be in your debt. Thanks!
Click to expand...
Click to collapse
The password error usually occurs when you flash an incorect TWRP version on your tablet. Are you sure you didn't accidentally flash one?
cmendonc2 said:
The password error usually occurs when you flash an incorect TWRP version on your tablet. Are you sure you didn't accidentally flash one?
Click to expand...
Click to collapse
100 percent sure. It worked just fine till I did the last factory reset in preparation for a new rom.
Solved!
Had to individually wipe data, system, cache and so on, then did a full factory restore and reinstalled my rom.
Hello,
Serveral days ago i was trying to factory reset my phone (installing newer cyan rom) but then this happen:
1. factory reset directly from the system
youtube.com/watch?v=tW5oVY5Dw7g
operation stops on twrp logo, after turning off and on phone starts normally (nothing is erased).
2. factory from twrp
youtube.com/watch?v=24lbiXqqOag
same situation, phone reboots and nothing is changed.
I have falcon-12.1-20151008-NIGHTLY version and TWRP 2.8.6.0.
Thank you for any help
I had the exact same issue - tried TWRP 2.8.6 and 2.8.7 but nothing worked - finally installed philz_touch_6.58.7-falcon Recovery and it has been working perfectly.
Thanks Dude, Philz Recovery did the job!
But after factory reset i noticed that Google applications are still present. As i undersand to get rid of gapps i need to format /system partition also, right?
ssinghebay said:
I had the exact same issue - tried TWRP 2.8.6 and 2.8.7 but nothing worked - finally installed philz_touch_6.58.7-falcon Recovery and it has been working perfectly.
Click to expand...
Click to collapse
Thanks ssinghebay.
I was also having same issue and philz_touch_6.58.7 worked :good:
About two weeks ago just before CyanogenMod's announcement of its closure I updated my Moto G2015 (1GB) to the latest nightly, which was CM14.1 released on the 25th of December, with its corresponding GAPPS version also released on the 25th of December (ARM, android 7.1, Full)
Yesterday the 7th of January my Google Apps decided that they didn't want to open, at first I thought it was just updating and since my battery was low I plugged in my device, I later realised that my device randomly went to a boot loop and stayed there. I grew impatient so I restarted the phone and went to the Recovery Mode (To Re-Flash the ROM), but to my annoyance the recovery (TWRP) just stayed on the 'Teamwin' logo forever, it would randomly go black then return to that logo. infuriated I turned on my phone and went to backup/reset and clicked 'factory reset'. it annoyingly booted me into recovery to reset the device, which of course I couldn't do.
Now the simple answer would have been for me to go and wipe the cache and data from 'google play services' and or 'launcher3' but I did, either it always shows 'calculating' preventing me from clicking 'manage space' or clearing 'cache' or when it did finally show, after I did click the button for the cache and or data to be cleared it would say 'calculating', and a quick check would discover that nothing was actually cleared.
Kind Regards, and Thank You to any help recieved,
NotSoGreat
Boot TWRP or CWM Recovery (not sure if it's still called CWM Recovery now that LineageOS has replaced it) with the command 'fastboot boot recovery.img' but replace recovery.img with your actual recovery image filename. If TWRP won't boot wait, sometimes a theme or corruption in the TWRP directory on internal storage can pause the startup of TWRP by several minutes, if that still fails boot CWMR and remove the TWRP directory or wipe internal storage.
Once you can get TWRP to boot properly, backup everything (MPT works in TWRP) and wipe and reflash, should be good to go.
acejavelin said:
Boot TWRP or CWM Recovery (not sure if it's still called CWM Recovery now that LineageOS has replaced it) with the command 'fastboot boot recovery.img' but replace recovery.img with your actual recovery image filename. If TWRP won't boot wait, sometimes a theme or corruption in the TWRP directory on internal storage can pause the startup of TWRP by several minutes, if that still fails boot CWMR and remove the TWRP directory or wipe internal storage.
Once you can get TWRP to boot properly, backup everything (MPT works in TWRP) and wipe and reflash, should be good to go.
Click to expand...
Click to collapse
Thanks for the reply, what you're saying makes sense and would probably work, but I found a simpler work around. I'm actually annoyed I didn't do it earlier.
So simply put, I downloaded my stock recovery which worked and then I just factory reset my device from there, that reset the CM14.1 ROM and let my Google Apps work again. Now about the recovery, I'm a bit skeptical about Re Flashing it, but I think I'll try it next weekend and post the results.
NotSoGreat said:
Thanks for the reply, what you're saying makes sense and would probably work, but I found a simpler work around. I'm actually annoyed I didn't do it earlier.
So simply put, I downloaded my stock recovery which worked and then I just factory reset my device from there, that reset the CM14.1 ROM and let my Google Apps work again. Now about the recovery, I'm a bit skeptical about Re Flashing it, but I think I'll try it next weekend and post the results.
Click to expand...
Click to collapse
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
acejavelin said:
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
Click to expand...
Click to collapse
I'll try now.
acejavelin said:
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
Click to expand...
Click to collapse
Right, so I reinstalled and flashed the latest version TWRP, when I opened into it, it took about 1 minute before it opened up, it ran a quick operation that I just glimpsed, it looked like it was wiping cache and user data, my phone was rebooted and I was right, my phone had been reset for the second time today (I'm almost a pro at reinstalling all my apps). I rebooted into the recovery and Look and Behold, it was working.
Thanks slot for your help and time.
Hey guys,
I have a oneplus 6red rooted with magisk and twrp running oreo 5.1.11, today I decided to enter twrp and reset my phone by whiping dalvic, cache and data.
After reboot, phone screen is totall dark but the light indicator was flashing constantly, entering twrp is no succes, twrp screen is stuck like more then 10 mins. I believe that I cant enter twrp to do something about it. I have downloaded the stock 5.1.11 which is an oreo version
Did I do really something wrong ? if yes or no please let me know how to fix this.
abati said:
Hey guys,
I have a oneplus 6red rooted with magisk and twrp running oreo 5.1.11, today I decided to enter twrp and reset my phone by whiping dalvic, cache and data.
After reboot, phone screen is totall dark but the light indicator was flashing constantly, entering twrp is no succes, twrp screen is stuck like more then 10 mins. I believe that I cant enter twrp to do something about it. I have downloaded the stock 5.1.11 which is an oreo version
Did I do really something wrong ? if yes or no please let me know how to fix this.
Click to expand...
Click to collapse
Try bluespark TWRP and flash your OOS zip again and report back. Maybe a magisk flash will help too.
mikex8593 said:
Try bluespark TWRP and flash your OOS zip again and report back. Maybe a magisk flash will help too.
Click to expand...
Click to collapse
thnx, I entered into fastboot mode, then from my pc I when into the fastboot folder to open cmd and boot twrp from there on my device, from there I followed a tutorial how to adb sideload and flash a rom from your pc. Now its working
But I dont understand why a simpel factory whipe through twrp caused all of this, I only wiped dalvic, cache and data.
abati said:
thnx, I entered into fastboot mode, then from my pc I when into the fastboot folder to open cmd and boot twrp from there on my device, from there I followed a tutorial how to adb sideload and flash a rom from your pc. Now its working
But I dont understand why a simpel factory whipe through twrp caused all of this, I only wiped dalvic, cache and data.
Click to expand...
Click to collapse
This may be a side effect of A/B partitioning and no longer having a recovery partition. Remember TWRP is a part of the boot partition now
tabletalker7 said:
This may be a side effect of A/B partitioning and no longer having a recovery partition. Remember TWRP is a part of the boot partition now
Click to expand...
Click to collapse
what would be an alternative sollution to factory reset your phone without all the troubles i witnessed.
abati said:
after whiping data, phone is stuck and twrp does nothing
Click to expand...
Click to collapse
After a whipping I wouldn't be inclined to do much either!
croques said:
After a whipping I wouldn't be inclined to do much either!
Click to expand...
Click to collapse
what do you mean, could you be more clear and specifiek ?
abati said:
what would be an alternative sollution to factory reset your phone without all the troubles i witnessed.
Click to expand...
Click to collapse
Use a fastboot rom. That will wipe EVERYTHING - and guarantee that you have a usable phone afterwards
abati said:
thnx, I entered into fastboot mode, then from my pc I when into the fastboot folder to open cmd and boot twrp from there on my device, from there I followed a tutorial how to adb sideload and flash a rom from your pc. Now its working
But I dont understand why a simpel factory whipe through twrp caused all of this, I only wiped dalvic, cache and data.
Click to expand...
Click to collapse
You probably wiped system that's why you had nothing to boot into
yldlj said:
You probably wiped system that's why you had nothing to boot into
Click to expand...
Click to collapse
i am almost sure that it was data and dalvic cahce and not system, that is what i also explained in my first post.
But how are you sure that it was system wipe ? did you factory reset your op6 multiple times without issue through twrp ?
phone is fixed btw
abati said:
i am almost sure that it was data and dalvic cahce and not system, that is what i also explained in my first post.
But how are you sure that it was system wipe ? did you factory reset your op6 multiple times without issue through twrp ?
phone is fixed btw
Click to expand...
Click to collapse
Its the easy answer, say that you wiped system or such.
If you wiped Data with Magisk installed, without flashing the stock kernel, you won't be able to boot, since Magisk stores stuff necessary to boot on Data.
Usually, people is stuck on a infinite bucle on TWRP after this, you couldn't even enter TWRP? that's new. The issue you're telling sounds like you changed slot in TWRP somehow to an unused one or something like that, never heard of that.
abati said:
i am almost sure that it was data and dalvic cahce and not system, that is what i also explained in my first post.
But how are you sure that it was system wipe ? did you factory reset your op6 multiple times without issue through twrp ?
phone is fixed btw
Click to expand...
Click to collapse
Yeah I have wiped data in twrp with no issues. TBH it just sounds like there was no system to boot into. Wiping data is just that and shouldn't make the phone unbootable. Also you fixed the issue by flashing OOS which makes me believe this also. If you want to factory reset your phone the best way is to do it through settings.