Hi guys, I need your help.
I've tried to update the rom with the latest beta Omnirom (30/06), directly from TWRP.
All the steps I followed, hoping it's usefull:
- removed the PIN from the system;
- made a full backup (from TWRP);
- installad latest vendor;
- installed latest Omnirom beta;
- wipe caches;
- reboot.
The phone is in bootloop; ufortunately, plus in TWRP the touchscreen is unresponsive and I have to reboot until it works.
I tried to flash just the rom beta or to restore the backup, without success.
EDIT: after flashing a older vendor and, again, Omnirom, the phone booted.
I don't know if it's related or not, but now, every app that I open, I see it in rotated horizontally, also if I have disinibited the rotation!
Any idea?
Thanks a lot,
Nic.
Sup3rN1c said:
Hi guys, I need your help.
I've tried to update the rom with the latest beta Omnirom (30/06), directly from TWRP.
All the steps I followed, hoping it's usefull:
- removed the PIN from the system;
- made a full backup (from TWRP);
- installad latest vendor;
- installed latest Omnirom beta;
- wipe caches;
- reboot.
The phone is in bootloop; ufortunately, plus in TWRP the touchscreen is unresponsive and I have to reboot until it works.
I tried to flash just the rom beta or to restore the backup, without success.
EDIT: after flashing a older vendor and, again, Omnirom, the phone booted.
I don't know if it's related or not, but now, every app that I open, I see it in rotated horizontally, also if I have disinibited the rotation!
Any idea?
Thanks a lot,
Nic.
Click to expand...
Click to collapse
I never recommend dirty flashes.
I would say that your problem is more than likely because you didn't wipe the system clean and start fresh.
Since you've already made backups of your data, I would suggest trying these steps:
Boot to TWRP
Format data, type yes to confirm
Go back to wipe / advanced
Select everything except USB and SD card.
Swipe to wipe.
Go back to the main menu.
Reboot to recovery.
Now flash the latest firmware, ROM, gapps
Also flash DFE if you want to disable the encryption.
Wipe cache when done.
Reboot.
Thank you BentMetal.
As you see from the EDIT, I solved the problem flashing a older vendor and the same updated rom.
For the other problem (screen rotation), solved by disabling display setting (auto rotate) and re-enabling again.
Now I just need to remove the touch screen freezing problem... very annoying.
It's a specific issue about a part of Pocophone who use a different touch screen.
Nic.
Related
Hi,
I was running BeanStalk-4.4.270 03/18/14 by zymphad. Im not sure what the kernel was.
I tried flashing the ROM by ronasimi in this thread.
The ROM that i picked was cm-11-20140817-UNOFFICIAL-geeb & the kernel was gbx-kernel-lights-CM11.0-CAF.zip. Apart from this i picked the Google Stock package of PA GApps from here.
For flashing i did the following :-
1. backed up all my apps using TB from BeanStalk.
2. loaded the ROM, the kernel & GApps zip files into a folder on my sdcard.
3. rebooted into recovery(TWRP 2.6.xx), backed up my original ROM and lined up all the three flashable zips and flashed them. (The flash was successful)
4. Then i rebooted into system. But after reaching the home screen, i was getting errors "Unfortunately, the process com.android.systemui has stopped" & "Unfortunately, the process com.android.phone has stopped". I remembered it might be because i forgot to wipe dalvik & cache.
5. I again rebooted into recovery, wiped dalvik & system cache and tried booting into system. It was still giving the same issues.
6. I tried restoring my old ROM's backup. Surprisingly even that wouldn't solve the issue.
7. So i again flashed the CM11 ROMs. But this time, the boot process is getting stuck at the boot animation.
My Qs are as follows:-
1. Did i miss anything or do something that is not recommended (or maybe even dangerous)?
2. What should be my next step in resolving this issue?
Any help appreciated.
gautam_k said:
Hi,
I was running BeanStalk-4.4.270 03/18/14 by zymphad. Im not sure what the kernel was.
I tried flashing the ROM by ronasimi in this thread.
The ROM that i picked was cm-11-20140817-UNOFFICIAL-geeb & the kernel was gbx-kernel-lights-CM11.0-CAF.zip. Apart from this i picked the Google Stock package of PA GApps from here.
For flashing i did the following :-
1. backed up all my apps using TB from BeanStalk.
2. loaded the ROM, the kernel & GApps zip files into a folder on my sdcard.
3. rebooted into recovery(TWRP 2.6.xx), backed up my original ROM and lined up all the three flashable zips and flashed them. (The flash was successful)
4. Then i rebooted into system. But after reaching the home screen, i was getting errors "Unfortunately, the process com.android.systemui has stopped" & "Unfortunately, the process com.android.phone has stopped". I remembered it might be because i forgot to wipe dalvik & cache.
5. I again rebooted into recovery, wiped dalvik & system cache and tried booting into system. It was still giving the same issues.
6. I tried restoring my old ROM's backup. Surprisingly even that wouldn't solve the issue.
7. So i again flashed the CM11 ROMs. But this time, the boot process is getting stuck at the boot animation.
My Qs are as follows:-
1. Did i miss anything or do something that is not recommended (or maybe even dangerous)?
2. What should be my next step in resolving this issue?
Any help appreciated.
Click to expand...
Click to collapse
Flash TWRP 2.7.1 or Philz's touch CWM
than do a clean install
Wipe data and Format system
Flash any ROM (here CM 11 ) and Gapps
Flash proper kernel ( for CM 11 old Gprij-X kernel or neighborhood kernel)
Wipe cache and delvick cache
reboot profit
For more info :
ShoaibAhmed said:
Flash TWRP 2.7.1 or Philz's touch CWM
than do a clean install
Wipe data and Format system
Flash any ROM (here CM 11 ) and Gapps
Flash proper kernel ( for CM 11 old Gprij-X kernel or neighborhood kernel)
Wipe cache and delvick cache
reboot profit
For more info :
Click to expand...
Click to collapse
I tried flashing using TWRP but the flash failed. then I saw the video and thought of giving philz touch cwm a try. it worked like a charm. Thanks a lot for the help. For kernel I flashed gprojx-kernel-lights-CM11.0-CAF-20140414.zip. Everything seems to be working now. Only thing is that I can't seem to turn off NFC. Every time I deselect the check box, go somewhere else and come back, the NFC check box is already checked.
Any tips on that? It's eating up my battery
gautam_k said:
I tried flashing using TWRP but the flash failed. then I saw the video and thought of giving philz touch cwm a try. it worked like a charm. Thanks a lot for the help. For kernel I flashed gprojx-kernel-lights-CM11.0-CAF-20140414.zip. Everything seems to be working now. Only thing is that I can't seem to turn off NFC. Every time I deselect the check box, go somewhere else and come back, the NFC check box is already checked.
Any tips on that? It's eating up my battery
Click to expand...
Click to collapse
Reboot once and then try to turn off NFC , it will work.
ShoaibAhmed said:
Reboot once and then try to turn off NFC , it will work.
Click to expand...
Click to collapse
Awesome! Thanks a lot man.
One last Q p)- I spent almost 30mins combing through settings but I couldn't find a 3G/2G switch. Is it hidden somewhere or it doesn't exist yet in CM11?
gautam_k said:
Awesome! Thanks a lot man.
One last Q p)- I spent almost 30mins combing through settings but I couldn't find a 3G/2G switch. Is it hidden somewhere or it doesn't exist yet in CM11?
Click to expand...
Click to collapse
Settings--->Mobile networks--->Prefered network type--> change it from "LTE" to 2G/3G
ShoaibAhmed said:
Settings--->Mobile networks--->Prefered network type--> change it from "LTE" to 2G/3G
Click to expand...
Click to collapse
i am actually looking for a shortcut for the same in notification draweer or quick settings pulldown...apologies for not making it clear before.
gautam_k said:
i am actually looking for a shortcut for the same in notification draweer or quick settings pulldown...apologies for not making it clear before.
Click to expand...
Click to collapse
Found the shortcut in Settings> Notification Drawer> Quick settings panel> Tiles & layout> Network mode
For some reason i was thinking that this will lead me to the GSM/WCDMA switch.
Hi;
So i recently installed CyanogenMod 13.0 on to my Samsung S4 GT-I9505 using the first download link on:
https://download.cyanogenmod.org/?device=jfltexx --> cm-13.0-20160102-NIGHTLY-jfltexx.zip
That all installed fine, but i wanted to get the Google apps installed aswell, which is where i am having some issues.
I have been trying to install the following package:
http://opengapps.org/?api=6.0&variant=nano
but have also tried to install quite a few others as well, and all have exactly the same issue. Basically after the apps have been installed and i boot the device up, i get various error messages like:
unfortunately, Setup Wizard has stopped
unfortunately, google play services has stopped
Any help on fixing this would be much appreciated, as nothing seems to download from the play store thats included in Cyanogen, they just say "your download will begin shortly" but never does.
Thanks in advance
I am a total noob, but I had exactly this problem. The issue appears to be that you have to flash gapps *before* rebooting after flashing CM. In my case since I had already flashed CM before I flashed gapps I had to put the gapps file on the phone (I did this by push with adb, you might find an easier way), re-flash CM, wipe cache/dalvik, flash gapps, wipe cache/dalvik, reboot. It worked.
The easiest guide I found was on androiding.how, called "how to install cm13 (cyanogenmod13)." (The forum won't let me post a link, just google it, it should come up).
Hope that helps. I'm on a galaxy s5 and used twrp recovery if that matters.
audacityandrouge said:
I am a total noob, but I had exactly this problem. The issue appears to be that you have to flash gapps *before* rebooting after flashing CM. In my case since I had already flashed CM before I flashed gapps I had to put the gapps file on the phone (I did this by push with adb, you might find an easier way), re-flash CM, wipe cache/dalvik, flash gapps, wipe cache/dalvik, reboot. It worked.
The easiest guide I found was on androiding.how, called "how to install cm13 (cyanogenmod13)." (The forum won't let me post a link, just google it, it should come up).
Hope that helps. I'm on a galaxy s5 and used twrp recovery if that matters.
Click to expand...
Click to collapse
Thanks for the reply, i gave that a try and it seems to be stuck on a loop now with "installing app # of 22" . it completes the installation and then reboots, after about 5 minutes on the Cyanogen boot screen, it goes back to installing apps again.
Hm, did you do a factory reset in your recovery before re-flashing CM and gapps? If not, that might be necessary.
audacityandrouge said:
Hm, did you do a factory reset in your recovery before re-flashing CM and gapps? If not, that might be necessary.
Click to expand...
Click to collapse
Yeah, i did. Tried it multiple times now
That's about the limit of my ability right there, hopefully someone with more experience than me can point you in the right direction. Good luck.
Boot to recovery (preferably TWRP)
Wipe cache / dalvik cache / data / system
Flash CM13 and the gapps you were trying first
Reboot
Profit!
Since you keep flashing different gapps on top of the system, this is probably causing some issues. Once you fully wipe and reflash everything, it should work.
es0tericcha0s said:
Boot to recovery (preferably TWRP)
Wipe cache / dalvik cache / data / system
Flash CM13 and the gapps you were trying first
Reboot
Profit!
Since you keep flashing different gapps on top of the system, this is probably causing some issues. Once you fully wipe and reflash everything, it should work.
Click to expand...
Click to collapse
Ive tried that multiple times using twrp (i always wipe everything before i flash CM13 and gapps), i still get the exact same issue. The second the phone boots, i get all these "unfortunately ******** has stopped".
Perhaps try installing 12.1 with gapps, get it all updated then upgrade to 13. I did the accidental upgrade to 13 but have had no issues whatsoever.
Hi all,
So I was happily running the 20190722 PE (Pixel Experience) on beryllium-V10.3.6.0.PEJMIXM-9.0-vendor-firmware with DFE and Magisk 19.3 flashed from TWRP 3.3.0. All files from official sources including the Official Telegram.
I come to discover I am 2 updates behind on PE so I created a NANDROID backup of the boot, system, and restore. I then cleared the dav and cache per usual and dirty flashed the ROM.
I then proceed to reboot the phone and it begins to encrypt itself. Given that I am a brilliant engineer, I proceed to interrupt it and restart the phone into TWRP. It loads and prompts a password. I have forgotten to DFE.
At this point I know that I have completely screwed up so, following the ongoing consensus on these forums, I format in TWRP, rebooting and clearing as instructed. I then go to restore the NANDROID. No go, boot loop.
After reading more, conclude that I need to flash the vendor FW and use it to reset/clear the phone and reinstall TWRP via FASTBOOT then flash the NANDROID. Nope, boot loop.
Going farther I discover that I need to flash the NAN on top of it’s working ROM/FW.
I go and flash the previously working ROM AND FW with dfe. To I double check I boot that and it boots properly to Android Setup.
Great! I use TWRP to flash the NANDROID. It boots to a lighted black screen. Pushing power I can get it to come up with a power/reboot/lock down menu that moves around the screen. This will actually restart or turn it off (didn’t touch the last).
I have tried this in various combinations with both my new NAN as well as a known working one.
Any ideas/thoughts/insults/ (I can take it)?
Try flashing 10.3.7.0 and then PE and immediately after DFE. However, I'm not sure it you won't lose everything. When doing your backup from TWRP, choose everything except System & Vendor. These 2 will be covered by System Image & Vendor Image.
HTH
Plz anybody help this out...
I unlocked bootloader, then immediately flashed Pitchblack recovery, then booted into recovery.
Initially console shows decrypted FBE device with default password. But Encryption status : Encryped
So I went into wipe & Formatted Data inorder to get rid of encryption. Then I rebooted recovery & it shows Unable to decrypt FBE device.
[UPDATE] (24/12/20) : The console output Unable to decrypt FBE device was nothing but to tell us that incompatible operating system flashed.
I flashed global version roms which are the main cause for bootloops. I flashed stock rom, then immediately worked out of the box.
1. Format data after going into twrp *It will wipe you device*
2. If you don't want to install a custom rom just mod MIUI, remove your lock screen password or flash orange fox and if it asks for password just put your lock screen password.
3. Else if you want to install a custom rom
Open recovery
Wipe data cache davilk
Flash rom
Format data
Reboot.
LoadOP2 said:
1. Format data after going into twrp *It will wipe you device*
2. If you don't want to install a custom rom just mod MIUI, remove your lock screen password or flash orange fox and if it asks for password just put your lock screen password.
3. Else if you want to install a custom rom
Open recovery
Wipe data cache davilk
Flash rom
Format data
Reboot.
Click to expand...
Click to collapse
Thnx for reply. I've tried Orange fox too. When I format data, internal storage doesn't decrypt. Also when I flash custom roms, they flash, but I'm gonna stuck in bootloop.
My main problem is that I can't decrypt storage. Phone boots only when I'm on MIUI stock. Am I missing something ?
That is odd but still flash fastboot rom and then flash twrp , flash a rom of your choice then format data . Maybe it will help . Btw which rom are you installing.
LoadOP2 said:
That is odd but still flash fastboot rom and then flash twrp , flash a rom of your choice then format data . Maybe it will help . Btw which rom are you installing.
Click to expand...
Click to collapse
Thnx for the reply. I'm trying to have lineage 17.1 & resurrection remix official build. I think rom's not the issue here. I need to know one thing.
To exactly say my issue, I can do flashing. But when I do & then reboot, Internal storage doesn't show the size & mtp doesn't work too, with bootloop issues along together.
There is no official LineageOS for the device.
kalehrl said:
There is no official LineageOS for the device.
Click to expand...
Click to collapse
Oh, I've mistaken, I was about to say resurrection remix official build & lineage unofficial one. Btw what do you think my device is going up to ? How can I decrypt & use internal storage successfully? I can't use internal storage when I flash a rom. Bcaz internal storage renders useless because of encryption.
Which recovery are you using?
Try flashing magisk 20 or 21.
Flash twrp by marounfurio( I am sorry if I slaughtered the name) which is available on xda.
And format data.
It's midnight here and I am going to sleep I will help to tommorow morning.
LoadOP2 said:
Which recovery are you using?
Try flashing magisk 20 or 21.
Click to expand...
Click to collapse
Right now I'm on Pitchblack beta latest build.
I tried magisk on MIUI stock through patched boot method, it worked, but no apps able to access root. I checked all magisk settings...
I think encrypted data partition is the whole culprit here. How can I decrypt it ?
MPK99 said:
Right now I'm on Pitchblack beta latest build.
I tried magisk on MIUI stock through patched boot method, it worked, but no apps able to access root. I checked all magisk settings...
Click to expand...
Click to collapse
And what about flashing magisk in twrp.
MPK99 said:
Right now I'm on Pitchblack beta latest build.
I tried magisk on MIUI stock through patched boot method, it worked, but no apps able to access root. I checked all magisk settings...
I think encrypted data partition is the whole culprit here. How can I decrypt it ?
Click to expand...
Click to collapse
Formatting data normally decrypts it . I don't know why something like this is happening here.
Follow my guide again maybe? Give it a shot step by step.
LoadOP2 said:
Formatting data normally decrypts it . I don't know why something like this is happening here.
Follow my guide again maybe? Give it a shot step by step.
Click to expand...
Click to collapse
Yah, I'm feeling weird too. Normally there are 3 ways to remove decryption...I tried all those.
1. Formatting Data by typing "yes"
2. Formatting data partition from f2fs to ext4
3. Installing Decrypt script v2 zip immediately after flashing stock rom.
I tried everything I could. I know all sorts of common flashing things. I caz I always used to try so many roms on my previous redmi's, but this one is special case.
I'd suggest you use LineageOS recovery. That's how I removed decryption.
kalehrl said:
I'd suggest you use LineageOS recovery. That's how I removed decryption.
Click to expand...
Click to collapse
Sure. Encryption is the whole culprit for me to say exactly. I'm trying to decrypt & flash builds. I'll notify if it works. Nice to get help from you guys.
Try this.
How to decrypt rom/storage so you can easily switch roms without format
First I would thankx to @sakhatlonda for koutiliy.zip
Steps to download file
1. Download koutility.zip from below.
2. Documentation related to koutility
Read from below link (recommended)
Just a utility zip which can be flashed on every rom flash, to do some pre-defined tasks.
Can be used either to copy everything you place in sdcard/sudeep/system_root to respective dirs or to set config and use that to do predefined tasks
This is how it works:
Flash in recovery, every option has Note with it
Available Configs:
brbootdtbo - auto backup/restore boot & dtbo, will do backup if no backup present and will do restore if backup is there
bbootonly - always backup boot
bdtboonly - always backup dtbo
resbootdtbo - always restore boot & dtbo (brbootdtbo won't work if this is enabled)
enalways - encrypt always (edauto won't work if this is enabled)
dealways - decrypt always (enalways & edauto won't work if this is enabled)
edauto - auto change encryption state on each flash
avb - removes avb flags (if decrypted)
quota - removes quota flag (if decrypted)
keep - doesn't over-writes boot/dtbo backups
debloat - removes bloats
rebloat - restore removed bloats
patchD - same as flash but set in config
productsize - makes a product image from your currently flashed rom to sdcard/sudeep and adds 600mb to it. So you can flash gapps etc. without error. (PC needed to flash product.img)
Steps to decrypt rom/storage
1. Flash roms
2. Flash koutility.zip tested on aosp only
3. Format data (required only first time after flashing koutility)
4. Reboot to recovery
5. Flash gapps (optional)
6. Boot into system
Congratulations your storage/rom is decrypted , you can switch roms without format
Next time when you want to switch roms
Steps
1. Wipe data,caches and dalvik caches
2. Flash rom
3. Flash koutility.zip
4. Reboot to recovery
5. Flash gapps (optional)
6. Boot into system
Notes
Remember you need to config koutility.zip in recovery
How to config koutility for decryption
Volume down (set config) > yes
After that "No" till 5th option
Then "yes" for 6th option
Rest "No" till 15th option
Last "yes" to flash
@LoadOP2 Thanx for providing KoUtil & its read me.
But I think we shouldn't reboot to recovery immediately after formatting the data. Because the stock rom will start it's initial encryption process by then & I won't get decrypted storage. Isn't it ?
I think this is the case that's happening to me. I always reboot recovery after formatting data, my storage will encrypt again because of stock rom's existence.
Yes you have to reboot to recovery. Otherwise you won't be able to use data partition.
LoadOP2 said:
Yes you have to reboot to recovery. Otherwise you won't be able to use data partition.
Click to expand...
Click to collapse
Yes, you're correct, we should do that. But can you read my 1st post in this thread. This is about that specific problem. I'm rebooting recovery after formatting data, then recovery shows Unable to decrypt FBE device
Send your recovery logs after formatting data.
LoadOP2 said:
Send your recovery logs after formatting data.
Click to expand...
Click to collapse
That would help. I'll attach screenshots too. Currently I'm on stock & being busy. I'll do this by today night & post logs & screenshots.
Hi there,
I've reinstalled my Lineage OS in May and have recently installed the latest upgrade. Today, I was using my phone just fine before a subway trip, then after it was stuck in a boot loop (lineage OS circles). My guess is that I accidentally restarted it.
What is the procedure to repair the phone without loosing the data?
I tried:
- Reinstalling recovery, lineage, MindTheGApps in that order
- Wiping the cache partition, wiping the dalvik cache
So far I have not seen any progress. Am I missing something?
I really want to avoid wiping my data as I just set the phone up two months ago.
Did you try dirty flashing the ROM zip by only Wiping the System partition but not Data? I use NikGApps and its not necessary to reflash it during a dirty flash but I flash the latest GApps build in any case. I pretty much use crDroid exclusively and dirty flashing works reliably. Not encrypted though.
Ok, so I did the following
Action -- What I think it does
Install TWRP recovery via fastboot -- to selectively wipe partitions
Wipe System -- to remove system files from the previous update
Wipe Cache & Dalvik cache -- to remove cache files that have previously been written on startup
Install lineage os -- to install a clean OS
Install MindTheGapps -- to install the Google subsystem
System reboot
Files used:
twrp-3.6.2_9-0-beryllium.img
lineage-19.1-20220618-nightly-beryllium-signed.zip
MindTheGapps-12.1.0-arm64-20220605_112439.zip
Again with:
lineage-19.1-20220716-recovery-beryllium.img
lineage-19.1-20220716-nightly-beryllium-signed.zip
MindTheGapps-12.1.0-arm64-20220605_112439.zip
Still caught in the boot loop.
I feel a bit lost here.
I did nothing special. Just installed the newest Lineage OS from the GUI and then apparently accidentally restarted it (or it crashed). This should be a common use case. I would expect there to be a guide or wiki that explains and solves this. But from my own Google searches I mostly see recommendations in the line of try wiping and reinstalling.
I am pretty sure, my data is encrypted. Does this mean I am screwed? (i.e., all not backup-ed data is lost?) Was flashing a new Lineage OS & GApps the step that doomed me?
Before the bootloop did you have TWRP installed instead of LOS recovery? Flashing the OTA update via TWRP can be problematic.
I had recovery installed. I reinstalled the Image from Lineage recovery. After this didn't work I tried it with TWRP.
Did you try flashing the build you were using before the bootloop occurred? No clue otherwise how to resolve this. Hopefully someone else can help you out.
Yes, first I tried installing only MindTheGapps, then lineageOS (last version I had) + MindTheGapps. And I tried a number of recent releases.
I also tried the most recent version and now I cannot install earlier versions anymore: "Current SPL: 2022-07-05 Target SPL: 2022-06-05 this is considered a downgrade".
I gave up. Reinstalled everything. Lost a ton of messages for which I did not have the right backup.
Depressing. Nothing I did was special. So I can expect this to happen anytime. I will improve my backup. But still, in the long term I need to find something that is reliable.
Thanks @amn1987 for the suggestions.
Use Swift Backup for backing up apps and their data, SMS, call logs etc. on a regular basis. Works very reliably. You can backup messages to Google Drive as well. Probably can schedule the backups.