So this started by me trying to remove the stock camera app on a custom ROM. The app caused similar problems in the past, but I forgot about it. In the past, when I tried using that app, the OS died and I had to flash it again. This time the same thing happened except I can't flash anything because TWRP crashes. Tried regular wiping and formatting data, it didn't work. The regular wipe said it's done, but the formatting said it can't remove encryption.
Sorry for bad english.
My device is the Xiaomi redmi note 7
Update to Orange fox, last version.
Related
Hello, I have a problem with my Nexus 4.
Everything was working fine (Even the SIM card) under a MIUI ROM, obtained from the MIUI port team of XDA. I wanted to install Ubuntu Phone, so I wiped everything.
When I say everything, is everything: Cache, Data, Dalvik... And I formated everything too: System, Data, Sdcard... So the problems started. I wasn't able to flash the phone to go back to stock, with the Nexus Rootkit. I installed the 1.6.6, the last version, and after many attemps I have now a fully customizable phone again, which is able to go back to stock or to a custom ROM, if I want.
The problem is that the SIM is not working. I'm trying to flash to 4.2.2 Stock again (because I've tried it two times) to see if it fixes the problem, but I guess that again, it won't.
So, any ideas?
Thank you very much indeed.
EDIT: The 4.3 update arrived and it fixed the problem automatically.
Hi All,
I've searched across forum to find also similar cases, but no results so far.
I have a N4 with TWRP and CM (previously running 10.1.2)
Today I decided to install the new 10.2.
Installation went fine but after the restart I've noticed some strange behaviour with some applications (missing from phone, but installed for my play store account)
I've decided to reboot again the phone, and since that time I'm stuck with the black start up Google screen (the one with the lock at the bottom).
Entered recovery mode, I've wiped Dalvik, Cache and System, but no results, rebooting is always stuck on Google screen (I've also left it there for 15+ minutes, no changes)
I've tried to install a previous ROM (zip available on phone storage) but no result even in this case.
Any help or suggestion would be much appreciated, even a link pointing to similar case happened in the past.
Let me know if any further detail may be needed to better understand the situation
Thanks!
mh a wipe/factory reset should be working...
Try pushing a different rom with ADB to your device, then flash it.
Sent from my Nexus 4 with Tapatalk 4
This is usually happening when you don't flash something right. I'd go back, flash it all again with wiping everything and flashing it by the right order and stuff. If it doesn't work, as written above, flash other ROM through ADB or something similar.
Besides, you could always restore your nandroid backup, and if you don't have one, learn from your mistake
Good luck
Sent from my Nexus 4 using xda app-developers app
To be honest, I've already tried to revert back to previous CM and even to the factory image from Google, but it always hang on the google screen.
I've not yet Format/completely wiped the phone, and that's my last option.
Once I'm done with the manual backup I'm doing via adb shell, I will try again to flash a new ROM, and see what happen.
Definitely I'm learning from my mistakes
Need some expert assistance. The problem is my phone keeps crashing with systemui errors when using custom roms. It always happens after a reboot and usually within 1-3 days, depends on WHEN I reboot the phone. Let me give you a little backstory.
A little over a month ago, I was running AICP on my phone, but decided to try SimpleAOSP and Hells doctor.. So I created a backup in TWRP, then flashed SimpleAOSP and HD. The next day day I started getting the errors. At the time, I thought it was the kernel or a Titanium Backup glitch.
So I wiped and reflashed SimpleAOSP without HD and without restoring from TB. But the next day, systemui failed to start. I thought it might be a rom issue so I restored AICP from my TWRP backup. And I couldn't believe it when the same systemui errors happened. So I restored the backup again. Again it was okay for a few days, then error.
After that I copied everything from my phone to the PC and wiped internal storage. Then installed the same rom version from AICP that I had been using for weeks prior to all this. Same error after a few days.
So next I tried wiping internal storage again and flashing stock 4.4.4. I used that for over a week with no system errors. So I did a TWRP backup of Google stock rom, Then installed AICP again but this time without modifying any systemui type settings, I left the rom as stock as it could come. Didn't even restore apps or anything. I then the rebooted the phone a couple of times to test and the error came back. This was the same day I installed it.
So I restored the stock backup and have been running fine all week. I want to get back on a custom rom though. Any suggestions?
Am I getting no replies because I'm missing something really obvious?
Or can no one think of anything that I haven't already tried?
By the way, right after posting the OP I installed the L preview and it's been working fine so far. I figured if I had to run stock android it may as well be the latest thing.
Sent from my Nexus 4 using Tapatalk
I don't have any answer to your question but I was wondering if this happens without installing a custom kernel on CM11 and AOSP custom ROMs.
Thanks for replying.
When I tried SimpleAOSP, it was with and then without an additional kernel. I saw no difference as far as the error is concerned. I have not tried a CM11 based ROM since this all started.
Maybe I should try a custom rom that doesn't have heavy modifications like AICP has.
Sent from my Nexus 4 using Tapatalk
Are you flashing a Gapps package? A couple weeks ago when I was trying different ROMs I was getting system crashes after flashing PA Gapps and they updated. I never narrowed it down, but after uninstalling a bunch of them (News/Weather, Talkback, Keep, Newsstand, some others) so they wouldn't update, I stopped getting system crashes.
Idk why I have the feeling your theme/icon pack has something to do with it. I run pa and whenever I try to use click ui icon pack it happens to me but if I just run veu I don't have a problem. Try not using themes for a bit to see what happens
Sorry, I missed your responses, I had kinda given up on the whole thing. Android L is running good for an unfinished product.
Getting back to the original issue, no theme or icon pack was installed.
Yes, I was using PA gapps mini from 9-23. Maybe that was it.
But that would be weird because I don't remember my first ROM running PA gapps, not 100% sure... that was a month ago.
I'll try to install without any gapps package and report back. Thanks.
Sent from my Nexus 4 using Tapatalk
from my past history, I'm facing issues when I did 3 things :
1. if I just dirty flash or factory reset only before flashing new rom.
2. Did restore backup from TB (which from your explanation above, you don't have any problem TB)
Nowdays I always use wipe dalvik, system, data, cache. Because someone once told me if you changing roms, if not it's possible that the system setting from old rom will crash with the new ones. and for the wipe system part (some roms included that command in their roms zip file and some didn't).
Good morning.
After almost 3 years with no problems with a XT907, I have again an issue with it (this time, my father's one). Again, I come to you requesting help.
It all started with all apps crashing over and over. With an old XT907 I have for emergencies, the common fix method is flashing VZW_XT907_4.4.2-KDA20.62-15.1_1FF.xml.zip with RSD Lite v6.1.5 and all solved.
I tried that method with my father unit, and when it started again, all process were still crashing. I thought it was still nothing (just a harder issue), and tried flashing VZW_XT907_4.4.2-KDA20.62-15.1_CFC_1FF_SVC.xml.zip, just deleting all his data, to fix it.
When the process ended, it turned on and it had still the same problem. In this point, I got worried the /system and /data partitions got locked
I re-started, went to stock Recovery, and wiped system and cache. Then, went to Fastboot a third time and tried again flashing VZW_XT907_4.4.2-KDA20.62-15.1_CFC_1FF_SVC.xml.zip. Guess what? Still the same problem
The phone turns on, but ALL apps keep crashing over and over. I can't even take an screenshot, as it immediately reboots.
Someone know what happened with it? And... how to fix this issue?
To make things worse
Fastbook Locked
No Root
Last 4.4.2 stock ROM
by twrp try make Wipe Data Or Repair File System, if not done mybe your internal memory Currpted
I haven't followed development of the 6T since November so please forgive me if this has been answered 100 times.
The steps to flashing custom non-OOS ROM's is to; flash ROM/flash TWRP installer/reboot recovery/flash gapps/flash magisk
The weird issue for me is when I reboot recovery after flashing the ROM and TWRP when I go to install gapps all my files are encrypted. My way around this was to sideload gapps and magisk and everything booted up fine. When I go back to recovery after the first boot all the files are normal again.
This has happened both times I've flashed a ROM.
I'm sure this has an easy answer and it's most likely due to a step I didn't execute properly -- or at all. I did a lot of reading and making sure I understood the process before rooting my device but as far as flashing ROM's I was noticing a lot of conflicting info which I've never seen before on any other device. Anyway, other than this I haven't had any issue.
Thanks for any feedback.
Security issue. Best way around it is to either format data before flashing and/or remove your lockscreen security pin before flashing.
Deleted
ogkillergreen said:
Security issue. Best way around it is to either format data before flashing and/or remove your lockscreen security pin before flashing.
Click to expand...
Click to collapse
I never use any lock. Always just use Swype to unlock. I'm aware of the issue with using a lock though. I read that people had problems. I just haven't seen where any one brought up my exact issue. It doesn't seem to effect anything so I'm not stressing it too bad. Eventually I'll get around to troubleshooting it.
I've flashed almost every ROM for 6T till now and every time I flash a ROM I'm having exactly the same issue as you. I've also tried formatting data several times, but the issue with unreadable data in TWRP after flashing a ROM returns every single time. I've tried multiple combinations of flashing, wiping etc. and it's always the same. However, what I'm doing in such case is flashing gapps + magisk from USB-C pendrive, no need to sideload, just mount USB and flash files from that as usual. After doing that I can boot to ROM and the data is readable again. I just need to remember to have this pendrive close to me when I'm flashing a new ROM.
BreathingWounds said:
I've flashed almost every ROM for 6T till now and every time I flash a ROM I'm having exactly the same issue as you. I've also tried formatting data several times, but the issue with unreadable data in TWRP after flashing a ROM returns every single time. I've tried multiple combinations of flashing, wiping etc. and it's always the same. However, what I'm doing in such case is flashing gapps + magisk from USB-C pendrive, no need to sideload, just mount USB and flash files from that as usual. After doing that I can boot to ROM and the data is readable again. I just need to remember to have this pendrive close to me when I'm flashing a new ROM.
Click to expand...
Click to collapse
Thanks for the tip and info. I don't mind sideloading because it's fast and anytime I mess with my phone it's when I'm at my PC. I've been using adb for so many years it's my go-to whenever my phone is acting stupid.
The second time I flashed a ROM I didn't even worry about flashing gapps, just magisk. And I stacked them. So ROM, TWRP, Magisk. Then rebooted system. I actually prefer this anyway because then you boot straight to the launcher with no setup process. Then I go back and flash GAPPS. I actually have used this flashing process for years because I hate the setup after a first time boot.