I was running the stock Nougat on this device, and booted into TWRP to wipe cache, I wasn't paying attention (was having a conversation with my wife) and accidentally did a factory reset. Now I am trying to re-flash the stock rom, or even a custom one. Every time I flash it goes through fine, but on reboot it just boots back into TWRP. There are no files on the internal SD, other than TWRP, which tells me it didn't actually flash... not sure what I can do
When it automatically reboots back to TWRP did you try to use the TWRP reboot menu to reboot to system?
Also try to purposely reboot to recovery and see if that sends you to an installed OS. I had that issue back on a Galaxy Tab 2 tablet once. The recovery and system partitions were internally labeled wrong somehow so booting normally sent me to recovery and booting to recovery sent me to the OS. That was an error in TWRP that was quickly fixed with an update. I doubt that is what's happened here, but it's worth trying since it will only take you a second to test it.
---------- Post added at 11:04 AM ---------- Previous post was at 10:59 AM ----------
Also if you did a factory reset that would wipe all the files on the internal SD. So that's not unusual.
It's odd that a factory reset would wipe out the whole ROM though. All that should do it wipe the data partition and cache of the internal storage, leaving the OS in tact. It sounds like you wiped the system partition.
What you'd need to do to fix is to rewipe everything. System, Data, and cache, THEN try to install a flashable ROM.
Also, have you previously been able to flash a custom ROM via TWRP on this phone? If yes, then its' probably not the TWRP recovery that's flawed. If you haven't previously done that, TWRP could have an issue and might need to be reinstalled.
More information on EXACTLY what you did and EXACTLY the steps you're taking to fix it would be helpful. if the above 2 options I gave you don't work.
Captn01 said:
I was running the stock Nougat on this device, and booted into TWRP to wipe cache, I wasn't paying attention (was having a conversation with my wife) and accidentally did a factory reset. Now I am trying to re-flash the stock rom, or even a custom one. Every time I flash it goes through fine, but on reboot it just boots back into TWRP. There are no files on the internal SD, other than TWRP, which tells me it didn't actually flash... not sure what I can do
Click to expand...
Click to collapse
Easy Fix read the whole post the end is what most need.
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
https://forum.xda-developers.com/lg-g5/how-to/android-booting-twrp-recovery-t3572200
wolfu11 said:
Easy Fix read the whole post the end is what most need.
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
https://forum.xda-developers.com/lg-g5/how-to/android-booting-twrp-recovery-t3572200
Click to expand...
Click to collapse
Sorry I am so late replying to this. It has been quite a hectic time. But thank you VERY much. This worked!
Is there a permanent fix though? I have to do this after every update...
Related
Long time visitor, first time poster.
Upgraded rom today when I found of there was an official 4.3 upgrade for the Verizon GS3. Looked around and found this one: http://forum.xda-developers.com/showthread.php?t=2600305 Before that, I was on the last official stock, flashed deodexed rom.
Installed rom zip via CWM, rebooted. After loading screen, it starts upgrading apps. It got stuck on 82 of 601. After 15 minutes, I booted into recovery and wiped cache (failed to do this during initial install, it never was a problem before). Reboot, gets stuck on 93 of 465. Hard reboot, total number keeps going down, but keeps sticking.
After several hard reboots (pulling the battery), I got it down to 1 of 1, but it won't go any further. It's been about an hour.
What do I do next?
While waiting for ideas, I'll hard reset, boot into recovery, wipe cache again, and see what happens.
Edit: Wiped cache partition from CWM, rebooted, still stuck at 1 of 1.
CaffeinatedGuy said:
Long time visitor, first time poster.
Upgraded rom today when I found of there was an official 4.3 upgrade for the Verizon GS3. Looked around and found this one: http://forum.xda-developers.com/showthread.php?t=2600305 Before that, I was on the last official stock, flashed deodexed rom.
Installed rom zip via CWM, rebooted. After loading screen, it starts upgrading apps. It got stuck on 82 of 601. After 15 minutes, I booted into recovery and wiped cache (failed to do this during initial install, it never was a problem before). Reboot, gets stuck on 93 of 465. Hard reboot, total number keeps going down, but keeps sticking.
After several hard reboots (pulling the battery), I got it down to 1 of 1, but it won't go any further. It's been about an hour.
What do I do next?
While waiting for ideas, I'll hard reset, boot into recovery, wipe cache again, and see what happens.
Edit: Wiped cache partition from CWM, rebooted, still stuck at 1 of 1.
Click to expand...
Click to collapse
I believe you may need to use ODIN to manualy re-flash the 4.3 update. NOTE: This will lock your bootloader, but seeing as how you have already upgraded it already is.
Mtsprite said:
I believe you may need to use ODIN to manualy re-flash the 4.3 update. NOTE: This will lock your bootloader, but seeing as how you have already upgraded it already is.
Click to expand...
Click to collapse
Do I specifically need to find a rom that is Odin flashable, or should I try another zipped package flashed through recovery?
CaffeinatedGuy said:
Do I specifically need to find a rom that is Odin flashable, or should I try another zipped package flashed through recovery?
Click to expand...
Click to collapse
Don't use Odin to flash the official tar file, you'll lock your bootloader and you'll be stuck.
Wiping dalvik cache should work, but if it doesn't then do this.
In recovery factory reset, wipe cache, wipe dalvik cache, format system, then format internal sd card (this will erase everything on your phone). Then reflash the rom again.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 01:55 PM ---------- Previous post was at 01:53 PM ----------
Mtsprite said:
I believe you may need to use ODIN to manualy re-flash the 4.3 update. NOTE: This will lock your bootloader, but seeing as how you have already upgraded it already is.
Click to expand...
Click to collapse
His bootloader is not locked, he never upgraded to the official 4.3 ota.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Don't use Odin to flash the official tar file, you'll lock your bootloader and you'll be stuck.
Wiping dalvik cache should work, but if it doesn't then do this.
In recovery factory reset, wipe cache, wipe dalvik cache, format system, then format internal sd card (this will erase everything on your phone). Then reflash the rom again.
Click to expand...
Click to collapse
I wanted to try something else before formatting the card and having to deal with that, so I downloaded the zipped rom here http://forum.xda-developers.com/showthread.php?t=2591895
From CWM I wiped cache (again), wiped dalvik (again), and installed rom. On reboot, went through app optimization without any problems.
I'm not sure what the problem was, but I fixed it by using a different rom.
Thank you for the help.
Hi!
I'm experiencing an annoying problem while updating my XOOM (MZ605) with the latest KitKat ROM.
I followed the instructions to repartition my device, and I tried using both Omnirom and Cyanogenmod roms, but I get the same error everytime.
In the step of wiping everything (but the SD card), I get a couple of messages saying that it was unable to mount cache to E: drive. TWRP recovery system says that the wipe process failed. Anyway, I went further in the steps, and I was able to flash the room and the gapps (it passes the BigPart partition check), but when I boot into system, my xoom stays stuck at the splash screen; it is not booting.
I tried both Omnirom and Cyanogenmod, and I get stuck in the same place. I thought I messed some part, so undone the BigPart, installed stock rom from motorola, and started over. But got the same problem.
I would liek to know if anyone know whats going on with the partiitoning, and if I can get rid of the mounting errors.
Thank you!
toiel said:
Hi!
I'm experiencing an annoying problem while updating my XOOM (MZ605) with the latest KitKat ROM.
I followed the instructions to repartition my device, and I tried using both Omnirom and Cyanogenmod roms, but I get the same error everytime.
In the step of wiping everything (but the SD card), I get a couple of messages saying that it was unable to mount cache to E: drive. TWRP recovery system says that the wipe process failed. Anyway, I went further in the steps, and I was able to flash the room and the gapps (it passes the BigPart partition check), but when I boot into system, my xoom stays stuck at the splash screen; it is not booting.
I tried both Omnirom and Cyanogenmod, and I get stuck in the same place. I thought I messed some part, so undone the BigPart, installed stock rom from motorola, and started over. But got the same problem.
I would liek to know if anyone know whats going on with the partiitoning, and if I can get rid of the mounting errors.
Thank you!
Click to expand...
Click to collapse
In your process of wiping...did you try to wipe just the cache by itself. When I got that error message i would go back to the main menu in recovery and just wipe the cache (or whatever giving me an error message) by itself.
Same problem here
gooniegoogoo2 said:
In your process of wiping...did you try to wipe just the cache by itself. When I got that error message i would go back to the main menu in recovery and just wipe the cache (or whatever giving me an error message) by itself.
Click to expand...
Click to collapse
Same problem here... I can't properly do some of the advanced wipes in the process of trying to install omni.
I did as you suggested and tried wiping them individually but to no success.
I am definitely not as fluent in this stuff as a lot of you on here are, but I am competent/confident enough to follow good instructions.
Somebody help please!
Cant install KitKat Roms
I am having the same issue and have done the same thing. Tried installing both CM and OMNI with no success. the recovery is telling me the came thing that it cannot mount E:\ 'cache' and other files i need to wipe.
Some one please help.
i was wondering...
i was wondering if the fact that i used to have a custom rom and then reverted back to stock (relocked the bootloader and unrooted successfully) last year before i attempted the omni install could be a factor?
But it worked before
ohDevious said:
i was wondering if the fact that i used to have a custom rom and then reverted back to stock (relocked the bootloader and unrooted successfully) last year before i attempted the omni install could be a factor?
Click to expand...
Click to collapse
I'm getting the same "can't mount cache" error when converting to Big Part - I had previously been running several Big Part roms, and had no problem with the conversion at that time - I then reverted back to stock (using VZW OTA's) for awhile, but want to give the Big Part roms another shot - I've tried several methods of reverting to stock, then coming back to install a 10.1 ROM, which is successful, but when I flash the Big Part TWRP and try the conversion, I get the cache mount error every time - I can revert to the "normal" TWRP, reformat, and re-install non-big part roms without a problem - help us Obi Wan! WTF?
I was getting the same thing as you guys. Stuck on splash screen. What I did to fix mine was under TWRP go to wipe, did factory reset wipe, then data wipe. Then mine worked for me. Takes about 3-5 minutes to boot on 1st start after wiping. Hope this helps.
---------- Post added at 08:25 PM ---------- Previous post was at 07:50 PM ----------
lightnuup said:
I was getting the same thing as you guys. Stuck on splash screen. What I did to fix mine was under TWRP go to wipe, did factory reset wipe, then data wipe. Then mine worked for me. Takes about 3-5 minutes to boot on 1st start after wiping. Hope this helps.
Click to expand...
Click to collapse
I forgot to mention click the format data tab under wipe and type yes.
I just had this same experience. I think the directions are somehow missing a step or we're misreading it.
lightnuup said:
I was getting the same thing as you guys. Stuck on splash screen. What I did to fix mine was under TWRP go to wipe, did factory reset wipe, then data wipe. Then mine worked for me. Takes about 3-5 minutes to boot on 1st start after wiping. Hope this helps.
---------- Post added at 08:25 PM ---------- Previous post was at 07:50 PM ----------
I forgot to mention click the format data tab under wipe and type yes.
Click to expand...
Click to collapse
A day not spent well
I am having the same issue all of you guys are having. I had 10.1 stingray (4.2.2) running well and thought it was time to try Kit Kat. Both the ROMs wind up the same way, a loooong running splash screen (over an hour before I manually rebooted). Over and over no mater how many ways I tried to wipe the XOOM I kept getting the Can't mount the cache message. I was able to revert back to 10.1 but I can't figure why others can make the install and we cannot. I have asked others on the forum but no one can answer the question?
Anyone? Thanks! Paddy
I was finally able to figure this out last night. I was looking at my cache and data formats and both were formatted as f2fs. I believe it's under wipe in the latest TWRP (2.7.1.0), there's an option on the left that shows you the format type of your drives. On non BigPart TWRP I changed the cache and data to ext4. Rebooted back into recovery, and followed the guide posted here to apply BigPart to my Xoom: http://forum.xda-developers.com/showthread.php?t=2506997 :: Then I was able to load Omni BigPart edition with no issues at all. I'd be happy to give more details if anyone wants. I'm in the office now, otherwise I'd post some snap shots. I'll update this when I get home.
has anyone recovered from the "unable to mount cache" error? I have followed all the information in this thread, checked out the relevant links all to no avail.
The only additional data I can provide is that when I go into the wipe menu (TWRP 2.7.1) / advanced / select cache / and "repair or change" I have all 0's for the cache size MBs. Repairing the cache or changing file system claims to be successful, but it's always 0 MBs. For grins I tried all of the above with TWRP 2.6.3 and had no better results.
Thanks in advance.
What is the expert method to deep clean, wipe every thing my OPO and than flash a ROM?
Hoping to hear from you experts.
Thanks.
Mike2040 said:
What is the expert method to deep clean, wipe every thing my OPO and than flash a ROM?
Hoping to hear from you experts.
Thanks.
Click to expand...
Click to collapse
You can flash the stock images via fastboot, that will erase everthing and get you back to stock. You can then install a custom recovery and flash roms again.
gsmyth said:
You can flash the stock images via fastboot, that will erase everthing and get you back to stock. You can then install a custom recovery and flash roms again.
Click to expand...
Click to collapse
No need to prior Wipe data, Factory reset, Wipe all storage etc?
Thanks.
Mike2040 said:
No need to prior Wipe data, Factory reset, Wipe all storage etc?
Thanks.
Click to expand...
Click to collapse
There is a command to wipe user data, see the below guide.
http://forum.xda-developers.com/showthread.php?t=2839471
Reason!
Thanks for your expert replies.
The reason for asking was and is for you to know in depth what happened.
My OPOs BL is unlocked and rooted.......at times try other ROMs like Hydrogen, RR, etc.
I was surprised to see and empty Baidu folder size 80 bytes shown by ES File manger, after I flashed back COS 12.
The way I flash is firstly reboot to TWRP, Format > type yes, than Factory reset, than Advanced Wipe ALL except OTG, power off the OPO.
Power on in fastboot mode, connect to pc and flash COS ROM using those commands.
All is good, except the empty Baidu Folder, fail to understand how did it persist.
Other thing is when I later flash TWRP over stock, and than when I perform a factory reset before flashing another ROM, see red SD card errors? ........have to keep rebooting to TWRP.
The way I flash is TWRP > Format type yes > Factory reset > Wipe all except OTG > Mount OTG-USB containing the zip, install zip swipe flash > once done > Reboot. (before reboot don't clear dalvik and cache).
If I take screen capture of TWRP they wont be saved in Gallery.
TWRP 2.7.8.0 when flashed on start up showed this.........
"TWRP has detected an unmodified partition. TWRP can leave your partition unmodified to make it easier for you to take official updates. TWRP will be unable to prevent the stock ROM from replacing from replacing TWRP and will not offer to root your device. installing zips or performing adb operations may still modify the system partition.
Never show this screen during boot again."
To sum up my queries are:
1. How can I perform a deep clean of OPO, and than flash COS 12 using fastboot, so I don't see any Baidu etc empty folders.
2. Than flash TWRP and and if needed can take it's screen captures.
3. Later if required can flash new custom ROM with out issues.
Bottom line to clean my OPOs Storage that includes SD card.
Btw my OPO isn't giving any issues or bugs and working great, no EFS issues etc.........
After reading all care to edit/correct what am I doing incorrect?
Thanks again.
Add
Is this the command to format user data?
Code:
fastboot format cache
Mike2040 said:
Thanks for your expert replies.
The reason for asking was and is for you to know in depth what happened.
My OPOs BL is unlocked and rooted........
Click to expand...
Click to collapse
I have seen people querying the Baidu folder before (i have it myself), it seems to be a folder left by ES file explorer, have you ever installed that? It doesnt seem to be anything malicious, although a lot people were spooked, thinking it was spyware of some sort.
https://forums.oneplus.net/threads/baidu-in-es-file-explorer-manager.303595/page-2
---------- Post added at 03:08 PM ---------- Previous post was at 02:58 PM ----------
Mike2040 said:
Is this the command to format user data?
Code:
fastboot format cache
Click to expand...
Click to collapse
Below is the command for flashing the userdata file via fastboot. If you have downloaded the fastboot image files, I think it basically pushes a blank file to overwrite/format the user data space/parition.
Code:
fastboot flash userdata userdata_64G.img
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.