So, I first flashed Arrow OS and after a while I experienced sudden freezes followed by a reboot. I can't really tell where they are coming from, they seem completely random and not tied to the usage of a certain app. When flashing a custom ROM with Ofox I noticed it saying `Failed to mount /system_root Invalid argument`. Could that be the problem? Is my flashing procedure wrong? I am installing stock miui -> wipe cache/dalvik, cache, data, internal storage (I can't find system on Ofox) -> flash rom -> reboot. Those constant reboots make the device really frustrating to use to almost unusable, any idea where they are coming from and how to fix?
Can you run
Code:
adb logcat > file.txt
and stop that with Control+C after a reboot occurs?
Logcat might give some insights.
Related
Hi,
I am trying to update to 4.4 from 4.2 on my A700. I used the nightly and gapps files recommended in this thread [NIGHTLY][ROM][4.4] CyanogenMod 11.0 for Acer A700 here: http://forum.xda-developers.com/showthread.php?t=2563610
I booted into CWM Recovery v6.0.4.4 and installed both files. After that, I did a factory reset. I told it to reboot and now all I get is a boot loop of the Acer splash screen showing Bootloader Verion JB-653b3d3 (unlock mode) in the upper left. Then it vibrates once and reboots again. Can someone help me out?
btw, I have previously tried updating to a newer version of 4.2 and I was getting the same thing. At that point, I was able to flash my old files. Now I don't have the old files to flash. Also, I can't find a way to load files via usb. In CWM, it doesn't seem to want to mount so my XP machine can see it.
I am not too well versed in custom roms. I have looked over other threads in this forum but so far I don't see what I need. If my question has already been addressed (I wouldn't be surprised), I need some direction on this. I am stuck...
Thanks very much!
John
frankred said:
Hi,
I am trying to update to 4.4 from 4.2 on my A700. I used the nightly and gapps files recommended in this thread [NIGHTLY][ROM][4.4] CyanogenMod 11.0 for Acer A700 here: http://forum.xda-developers.com/showthread.php?t=2563610
I booted into CWM Recovery v6.0.4.4 and installed both files. After that, I did a factory reset. I told it to reboot and now all I get is a boot loop of the Acer splash screen showing Bootloader Verion JB-653b3d3 (unlock mode) in the upper left. Then it vibrates once and reboots again. Can someone help me out?
btw, I have previously tried updating to a newer version of 4.2 and I was getting the same thing. At that point, I was able to flash my old files. Now I don't have the old files to flash. Also, I can't find a way to load files via usb. In CWM, it doesn't seem to want to mount so my XP machine can see it.
I am not too well versed in custom roms. I have looked over other threads in this forum but so far I don't see what I need. If my question has already been addressed (I wouldn't be surprised), I need some direction on this. I am stuck...
Thanks very much!
John
Click to expand...
Click to collapse
Hey John.
What it sounds like, is that you didn't do your "wipes" before flashing the CM ROM. This is pretty much mandatory, and sounds like what happened.
I would boot back into CWM. These are what you need to wipe/format "before" flashing CWM.
1. Data/factory reset (this wipes your data partition)
2. System (this wipes pretty much all current system files)
3. Cache
4. Dalvak Cache (might need to look for this in "advanced", it depends on the recovery.)
5. Flexrom if it's an option. If not, don't worry about it, as it seldom causes issues.
Then, flash your CM. Now, for myself, I usually flash CM first, boot the system, bypass all the setup screens, then let it stabilize. Then I go back into CWM and flash the Gapps. That's just me though. Some folks flash CM, then Gapps in that order at the same time.
Good luck
MD
Thanks very much for the reply MD!
I tried the steps you suggested but I am still stuck in the same place. Let me explain.
When I select wipe data/factory reset, it processes for a second and then reboots. Is this normal behavior?
When I select Wipe Dalvik Cache, I get:
E:Unknown volume for path [/sd-ext]
Dalvik cache wiped.
I selected Show Log:
Block groups: 10
Reserved block group size: 79
Created filesystem with 11/78400 inodes and 10305/313344 blocks.
warning:wipe_block_device: wipe via secure discard suppressed due to bug in EMMC firmware
Cache wipe complete.
I:Ca't partition non mmcblk device: /decisces/platform/sdhci-tegra.0/mmc_host/mmc2
E:unknown volume for path [/sd-ext]
rm: can't remove '/data/dalvik-cache': no such file or directory
rm: can't remove '/cache/dalvik-cache': no such file or directory
rm: can't remove '/sd-ext/dalvik-cache': no such file or directory
Dalvik Cache wiped.I have my rom and gapps in /storage/sdcard1/cminstall/
cm-11-2014-111-NIGHTLY-a700.zip - not renamed cmupdate.zip
gapps-kk-20131209.zip
I feel like I have a larger issue here...
Well, it has been a while but I am still stuck in the same boat. I have since had the flu and I was out of town for work for 3 days then 5 days.
My rom and gapps files are currently on my external SD card. Should they be on the internal storage?
I have been trying to connect via usb to my xp laptop but I am not having any luck. The best I can get is an A700 in Device Manager with a yellow exclamation point. I have tried installing the Acer usb drivers but they won't take.
The closest I get to Windows finding the tablet with my laptop is when I let it attempt to boot. Windows finds the device for about 5 seconds before it reboots again.
Can anyone point me in the right direction?
Any help would be much appreciated.
John
This happens when you wipe the cache, but it does not mean anything is wrong with your phone.
E: Can't mount /cache/recovery/log and the other five errors are similar to this.
PERFORM A BACKUP PRIOR TO THIS
I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR PHONE.
Start by going into your recovery..
If you want to keep the ROM you have, then follow these directions. When flashing a new ROM follow the next set of directions.
KEEPING YOUR CURRENT ROM
1) Go into your recovery
2) Go to mounts and storage
3) Format /cache x3
4) Go to advanced in the main menu
5) Reboot recovery
If it is not working, repeat the steps.
FLASHING A NEW ROM
1) Go into your recovery
2) Format /system /data /cache x3 (Like any normal flashing of a ROM)
3) Install the ROM you want to use
4) Go to mounts and storage
5) Format /cache
6) Go to advanced in the main menu
7) Reboot recovery
8) Boot into your newly flashed ROM
I made this thread because some people still have this error show up even though it doesn't affect the way you flash a ROM.. It's just annoying to see that come up every time you hit the back button in CWM.
syedwaseem said:
This happens when you wipe the cache, but it does not mean anything is wrong with your phone.
E: Can't mount /cache/recovery/log and the other five errors are similar to this.
PERFORM A BACKUP PRIOR TO THIS
I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR PHONE.
Start by going into your recovery..
If you want to keep the ROM you have, then follow these directions. When flashing a new ROM follow the next set of directions.
KEEPING YOUR CURRENT ROM
1) Go into your recovery
2) Go to mounts and storage
3) Format /cache x3
4) Go to advanced in the main menu
5) Reboot recovery
If it is not working, repeat the steps.
FLASHING A NEW ROM
1) Go into your recovery
2) Format /system /data /cache x3 (Like any normal flashing of a ROM)
3) Install the ROM you want to use
4) Go to mounts and storage
5) Format /cache
6) Go to advanced in the main menu
7) Reboot recovery
8) Boot into your newly flashed ROM
I made this thread because some people still have this error show up even though it doesn't affect the way you flash a ROM.. It's just annoying to see that come up every time you hit the back button in CWM.
Click to expand...
Click to collapse
I have tried this but this does not work. I am Using PhilZ CWM 6.49.2. I cant even Flash A Custom ROM Because of this problem it would just show me these error messages and say "Installation Aborted" and restart phone.
I have also Flashed back the Stock ROM and repeated all of the procedures: 1.Framaroot 2:CWM
Still no success it just keeps giving me these stupid errors, Please Find a FIX.
THANKS
dima234 said:
I have tried this but this does not work. I am Using PhilZ CWM 6.49.2. I cant even Flash A Custom ROM Because of this problem it would just show me these error messages and say "Installation Aborted" and restart phone.
I have also Flashed back the Stock ROM and repeated all of the procedures: 1.Framaroot 2:CWM
Still no success it just keeps giving me these stupid errors, Please Find a FIX.
THANKS
Click to expand...
Click to collapse
I have the same problem.
I tried methods:
$ su
#dd if = / sdcard / recovery.img of = / dev / block / mmcblk0p13
It does not work.
I installed the stock rom and checked the partition mmcblk0p13 with "Partition Table" and the partition is not mounted.
Maybe this is the problem?
meriox said:
I have the same problem.
I tried methods:
$ su
#dd if = / sdcard / recovery.img of = / dev / block / mmcblk0p13
It does not work.
I installed the stock rom and checked the partition mmcblk0p13 with "Partition Table" and the partition is not mounted.
Maybe this is the problem?
Click to expand...
Click to collapse
Yea even i have tried the same but it does not work, guess we have to stick to the stock ROM till someone finds a fix.
dima234 said:
Yea even i have tried the same but it does not work, guess we have to stick to the stock ROM till someone finds a fix.
Click to expand...
Click to collapse
Do you think that someone will be looking to solve the problem?
It seems to me that the problem occurs only in the new models that have been bought recently.
I tried to install the older stock firmware but it did not help.
None of the methods that have been on the forum does not work.
The problem occurs only when WIPE DATA / FACTORY RESET.
meriox said:
Do you think that someone will be looking to solve the problem?
It seems to me that the problem occurs only in the new models that have been bought recently.
I tried to install the older stock firmware but it did not help.
None of the methods that have been on the forum does not work.
The problem occurs only when WIPE DATA / FACTORY RESET.
Click to expand...
Click to collapse
yea getting the same problem here.
cant mount system
cant mount cache
and most of all when install custom ROM. cannot continue since non of those partitions cannot mount properly.
and other errors are flooding the recovery, we have tried Philz, CWM, TWRP. same annoying problems.
Hello,
On another website I found this:
"All worked fine but that like of command in terminal you put there isn't right, i did this
$ su [and then enter]
# dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p32 [and then enter]
# reboot recovery [and then enter]
PS: the $ comes automatically when you start the terminal emulator app; the # comes automatically after you allow the super user [in $ su]
Do consider all the "Spaces" between symbols and paths!"
Has anyone used this method?
syedwaseem said:
This happens when you wipe the cache, but it does not mean anything is wrong with your phone.
E: Can't mount /cache/recovery/log and the other five errors are similar to this.
PERFORM A BACKUP PRIOR TO THIS
I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR PHONE.
Start by going into your recovery..
If you want to keep the ROM you have, then follow these directions. When flashing a new ROM follow the next set of directions.
KEEPING YOUR CURRENT ROM
1) Go into your recovery
2) Go to mounts and storage
3) Format /cache x3
4) Go to advanced in the main menu
5) Reboot recovery
If it is not working, repeat the steps.
FLASHING A NEW ROM
1) Go into your recovery
2) Format /system /data /cache x3 (Like any normal flashing of a ROM)
3) Install the ROM you want to use
4) Go to mounts and storage
5) Format /cache
6) Go to advanced in the main menu
7) Reboot recovery
8) Boot into your newly flashed ROM
I made this thread because some people still have this error show up even though it doesn't affect the way you flash a ROM.. It's just annoying to see that come up every time you hit the back button in CWM.
Click to expand...
Click to collapse
Thanks worked for me :good:
bricked
I've got these errors on my htc desire x, I made a backup, after that, I try to flash a new rom, with the steps written in the first post. The result was: after the htc logo, it showed a black screen! I try to restore the backup, but I cant restore!!!!! I've got soft brick, so I take it a service. I hope, they can fix it
Since lot of peoples are complaining about their phones going suddenly slow and lagging after some days of flashing a new ROM, so there is a guide how to fix this issue
Importants notes:
-This solution will provid you to format system partition , it means you will lost all custom mods you have installed on it (Xposed, Fonts), but don't worry you will be able to re-install them after.
-I suggest you to do a backup before anything.
-This fix only lags/slowness due to eMMCs, so if your phone still lagging after blame your ROM or the Kernel you use or maybe the 1000 apps you have installed on it.
What's eMMCs and why this lag is happening ?
I suggest to read full thread about it here : https://goo.gl/FchzSN (Thanks @doesntexits)
How to know if my device is affected by this issue?
Use this app https://goo.gl/gpY8tq
After install test your Internel Memory writing speed(Hold Internel Memory then select Quick), in the end it sould be at least 20mb/s.
If not so you have some lags on your phone.
How to fix it?
-Download and flash this version of TWRP: https://goo.gl/2znyCx (Flash it using your old TWRP )
-Reboot the phone to recovery again (You should see TWRP version is 3.0.1 now)
-Go to Settings , make sure (Use rm-rf instead of formatting) is unthicked
-Now go back and go to Wipe ,then Advanced Wipe, select only System and Swipe to Wipe
-Wait until it finishe , it could take lot of time (About 20 Minutes), have a cup of tea while you wait .
-Repeat the System Wipe for at least 20 times (More or less depend on users, but to be safe do it 20 or more ).
-Then It's done you can install any ROM you want, after installing the new ROM go check your Write Speed again with same app to see diffrences, if it still under 20mb/s do more System Wipes .
-After your lags are defently fixed you can Use rm-rf instead of formatting to flash ROMs or anything you like faster.
After this you should have your phone at good writing speed.
If you have any kind of question be free to ask me.
Credits:
- @doesntexits for original guide and solution.
- @Nikit for TWRP version.
- @mv2007 for advices and help.
Hope i didn't forget anyone.
Or you could just do 'fstrim -v /system' Optionally run the same command on /data and /cache. Works for me but YMMV. At least better than waiting six hours of repeated wiping arrrrgggggghhhhh.
my Galaxy core prime has the same problem. my phone now lagging stucking. how to fix this? will this mod help me?
rms112 said:
Or you could just do 'fstrim -v /system' Optionally run the same command on /data and /cache. Works for me but YMMV. At least better than waiting six hours of repeated wiping arrrrgggggghhhhh.
Click to expand...
Click to collapse
Sir can you explain this procedure step by step
Also is this helpful ???
---------- Post added at 01:33 PM ---------- Previous post was at 01:27 PM ----------
Sir I have one question what is the reason of using 3.0.1 version of TWRP when we have 3.0.0 version too?
Also are you or anyone else getting writing speed of 20 mbps or more......
Have anybody tried it?
I get 20 normally. Idk I haven't experienced lags so far. Screenshots show fstrim too.
rms112 said:
I get 20 normally. Idk I haven't experienced lags so far. Screenshots show fstrim too.
Click to expand...
Click to collapse
Followed your commands via TWRP recovery. Entered those commands successfully on system, data and cache.
Getting writing speed of 22.25 mbps on internal storage
It's really working for me!! i recommending
Everyone facing slow device problem, just follow these steps:
Make sure you're running @dreamstar's old TWRP version without formatting fixes (VERY IMPORTANT) (DOWNLOAD LINK BELOW)
Untick "Use rm -rf instead of formatting" in TWRP settings (again, VERY IMPORTANT)
Do a full wipe (format data, system, cache) (why don't we need to wipe data, dalvik cache in advanced wipe? because we have already done those steps when format data)
Reflash stock ROM (any versions)
And... enjoy flashing other ROMs
OLD TWRP LINK
Original Post
https://forum.xda-developers.com/showpost.php?p=67824939&postcount=383
iamkani said:
It's really working for me!! i recommending
Everyone facing slow device problem, just follow these steps:
Make sure you're running @dreamstar's old TWRP version without formatting fixes (VERY IMPORTANT) (DOWNLOAD LINK BELOW)
Untick "Use rm -rf instead of formatting" in TWRP settings (again, VERY IMPORTANT)
Do a full wipe (format data, system, cache) (why don't we need to wipe data, dalvik cache in advanced wipe? because we have already done those steps when format data)
Reflash stock ROM (any versions)
And... enjoy flashing other ROMs
OLD TWRP LINK
Original Post
https://forum.xda-developers.com/showpost.php?p=67824939&postcount=383
Click to expand...
Click to collapse
This guide is same as I wrote with just more details
:fingers-crossed:
rms112 said:
I get 20 normally. Idk I haven't experienced lags so far. Screenshots show fstrim too.
Click to expand...
Click to collapse
Me too. Havent expirienced it.
i did this command 'fstrim -v /system' alot of times and flashed stock system and i get write speed on internal 3.99 mbps
if i flashed custom rom like linage or python the system not boot up
i have lots o lags and slowness on stock
i formatted 22 times the system but still have slowness any idea? to fix my cp
muhammed Palestinian said:
i did this command 'fstrim -v /system' alot of times and flashed stock system and i get write speed on internal 3.99 mbps
if i flashed custom rom like linage or python the system not boot up
i have lots o lags and slowness on stock
i formatted 22 times the system but still have slowness any idea? to fix my cp
Click to expand...
Click to collapse
You can try this.
https://play.google.com/store/apps/details?id=com.paget96.lspeed&hl=en
Should I flash stock rom through odin? Or just flash the custom rom I was using?
QuinzyJb said:
Should I flash stock rom through odin? Or just flash the custom rom I was using?
Click to expand...
Click to collapse
Cause Im a little confused with the last part
Hello guys,
Today I wanted to update my Honor 8 (FDR-L09) because it was showing me, that there is a new update ready to install (FRD-L09C432B405) and I was on a very old firmware (something from mid 2017). So it was time for me to update.
I downloaded the latest update (FRD-L09C432B405) and tried to wipe the cache, dalvik, and Data, but for some reason it "couldn't mount /data" and the wipe failed.
After an advanced wipe it worked and I tried to flash the stock image (the update which was shown to me (FRD-L09C432B405) with TWRP (3.1.1.1.)).
Now my hassle starts:
1. The Rom couldn't get flashed because of "Error: 7" --> I fixed it with the common "Error 7 fix --> editing the update-script and removing the assert line. (And yes, I'm 100% sure that it was the right ROM.
2. Now TWRP seemingly starts to flash the rom but inbetween the lines there is "mountencrypt: failed to mount /data: no such file or directory and it ends with "unknown command [[]" and it takes just two seconds, so the flash obviously isn't succsessfull.
I tried the "failed to mount /data" fix, where I change the data system to ext3 and then back to f2fs and change it back, but it won't work.
In my frustration I did another pretty bad thing and made another advanced wipe and wiped the system too, so now I don't have an OS on my system.
Maybe it's also important to note that there was a window showing up for a very short amount of time, with something like "encryption/encrypted" showed up.
What should I do now? Is there a way to fix the "/data couldn't be mounted" problem? Or am I missing a vital step in flashing the stock rom?
Thanks for your kind help!
You can not flash an update with twrp unless you use hurupdater. You essentially bricked your phone. Look for hurupdater here on xda and follow the instructions and you'll be fine
I've been running ArrowOS - Arrow-v12.0-vayu-OFFICIAL-20211108-VANILLA - and pleased with it's stability, but decided it was time to update to the Arrow-v12.0-vayu-OFFICIAL-20211221-VANILLA version.
Recovery was TWRP-3.5.2-vayu-Nebrassy-2 so I used the TWRP app to update that to the official TWRP-3.6.0.
My phone is encrypted and without a password. TWRP-3.6.0 couldn't mount partitions or view files.
Data partition etc show 0 bytes' and adb sideload failed to connect - may have been an unreliable cable - so I added a 4-digit pin which worked in the system and rebooted to recovery. TWRP didn't ask for a password and showed the same encrypted and invisible partitions. Trying the 'Decrypt Data' option in TWRP 'Mount' menu, I got the errors 'Failed to decrypt data' 'Password failed'.
I tried using adb shell to decrypt:
vayu:/ # twrp decrypt 1234
Attempting to decrypt data partition or user data via command line.
Failed to decrypt data.
Click to expand...
Click to collapse
Then I tried adb sideload from TWRP which failed quickly with:
updater process ended with signal 7
Click to expand...
Click to collapse
And on my Ubuntu laptop:
$ adb sideload Arrow-v12.0-vayu-OFFICIAL-20211221-VANILLA.zip
serving: 'Arrow-v12.0-vayu-OFFICIAL-20211221-VANILLA.zip' (~7%) adb: failed to read command: Success
Click to expand...
Click to collapse
I rebooted into System, and got Fastboot instead. I can reboot into recovery.
Can anyone suggest how to repair the phone, and get TWRP to decrypt the filesystem?
TIA!
Giallograle said:
I've been running ArrowOS - Arrow-v12.0-vayu-OFFICIAL-20211108-VANILLA - and pleased with it's stability, but decided it was time to update to the Arrow-v12.0-vayu-OFFICIAL-20211221-VANILLA version.
Recovery was TWRP-3.5.2-vayu-Nebrassy-2 so I used the TWRP app to update that to the official TWRP-3.6.0.
My phone is encrypted and without a password. TWRP-3.6.0 couldn't mount partitions or view files.
Data partition etc show 0 bytes' and adb sideload failed to connect - may have been an unreliable cable - so I added a 4-digit pin which worked in the system and rebooted to recovery. TWRP didn't ask for a password and showed the same encrypted and invisible partitions. Trying the 'Decrypt Data' option in TWRP 'Mount' menu, I got the errors 'Failed to decrypt data' 'Password failed'.
I tried using adb shell to decrypt:
Then I tried adb sideload from TWRP which failed quickly with:
And on my Ubuntu laptop:
I rebooted into System, and got Fastboot instead. I can reboot into recovery.
Can anyone suggest how to repair the phone, and get TWRP to decrypt the filesystem?
TIA!
Click to expand...
Click to collapse
Any custom recovery at the moment cannot decrypt Android 12.
Try USB OTG or microSD card to flash in custom recovery.
Oic thanks!
Sounds like an easy fix. Before I do that, am I going to lose data, settings etc by flashing the update when the recovery can't access all the filesystem?
Giallograle said:
Oic thanks!
Sounds like an easy fix. Before I do that, am I going to lose data, settings etc by flashing the update when the recovery can't access all the filesystem?
Click to expand...
Click to collapse
Not sure if your previous actions messed up your data partition or not, so not sure if you will loose your data or not.
Recoveries cannot decrypt data partition, but the system file writing ability should be working.
If you still have the zip file of the old version 20211108, you can flash it and see if the system will boot and read your data correctly.
If it boots and your phone is like before update attempt, then you can try flash the update zip.
If it did not boot into the OS, chances are some of your earlier actions messed up data partition. In this case, format data is the way, which will loose your data.
If format data still doesn't help, you might need to go back to MIUI and start again.
That was a good suggestion. I reinstalled the Arrow-v12.0-vayu-OFFICIAL-20211108-VANILLA rom and the phone rebooted.
Only glitch is constant notifications that Google Play Services keeps stopping, and various other apps notifications to 'Get Google Play Services'.
I presume that Play Services may have been rolled back by the reinstallation, and I'm wondering whether to try to find a more recent copy to install and see if that fixes it, or just go directly to the Arrow-v12.0-vayu-OFFICIAL-20211221-VANILLA rom.
Giallograle said:
That was a good suggestion. I reinstalled the Arrow-v12.0-vayu-OFFICIAL-20211108-VANILLA rom and the phone rebooted.
Only glitch is constant notifications that Google Play Services keeps stopping, and various other apps notifications to 'Get Google Play Services'.
I presume that Play Services may have been rolled back by the reinstallation, and I'm wondering whether to try to find a more recent copy to install and see if that fixes it, or just go directly to the Arrow-v12.0-vayu-OFFICIAL-20211221-VANILLA rom.
Click to expand...
Click to collapse
Did you install GApps manually?
If you did not, but your system has Google Play Services, then you probably had installed GApps version of ArrowOS instead of Vanilla version.
Switching between Vanilla and GApps is probably not working well if you did not format data. Maybe from Vanilla to GApps version is possible, but from GApps version to Vanilla may cause some issues.
Make sure which version you had, GApps or Vanilla.
If you are not very sure, then backup all your personal data and apps and do a clean flash with format data.