I tried to use an app called Second Screen from Play Store to change my screen resolution as i was trying to cast the screen to my laptop which was resulting in black bars due to different resolution and aspect ratio. As soon as i applied the settings in the app, my screen turned black and then crashed after waiting for a few seconds. Tried the following:-
1. dirty flash the rom, uninstalled magisk.
2. Wipe /system and flashed rom.
From the above it looks like the resolution and/or DPI change has nothing to do with /system.
I really really dont want to reset the phone as there are tons of apps installed and i have a lot of media on it as well.
I have TWRP installed and is working fine and also the phone boots but ends up in a black screen and i can see the power menu if I long press the power button but it appears in landscape (nothing else appears). If i boot the phone and keep it for a minute or so, it ends up crashing.
Please help. I seem to have reached my limits.
Edit:
I made a nandroid backup and wiped everything except internal storage and the phone boots and works fine but as soon as i restore /data of the old rom backup, the problem comes back.
Edit 2: Tried safe mode but the again to no avail. I can get the phone back if i wipe everything /data / system EXCEPT storage but don't want to loose my apps and settings. Believe me there's tons of apps installed on my phone. Tried to enable adb via editing props but it ends in a bootloop. Editing adb settings in the global_settings file in /data/system/users/0 doesn't stick.
if anyone knows where the display size and density settings reside in the form of a file so that i can replace them with the correct one , please reply.
Any kind of help is greatly appreciated. :crying: :crying:
Edit 3: I don't know what I did but I somehow made it work. I was about to give up when I accidentally restored back the nandroid backup and I thought "I might as well give it a last shot now thay the old /data is restored". I did a lot of things including copying some of the props and XML files and many more things and it booted without any problems except that it wasn't accepting my lockscreen password which is quite easy to fix. Thanks to everyone for bearing this with me.
Google, the answer to this, that and many other things.
Try: adb shell wm density 392
guhvanoh said:
Google, the answer to this, that and many other things.
Try: adb shell wm density 392
Click to expand...
Click to collapse
Stupid me hadn't enabled USB debugging. I tried to enable it by editing build.prop and default.prop but the phone just bootloops.
MasterFURQAN said:
Stupid me hadn't enabled USB debugging. I tried to enable it by editing build.prop and default.prop but the phone just bootloops.
Click to expand...
Click to collapse
I'm not sure though, but I think flashing Vendor+Firmware will do the trick..
And if it didn't work, what you need to do is flash stock fastboot rom... then install twrp again and flash a custom rom (if that's what you're using)
MasterFURQAN said:
Stupid me hadn't enabled USB debugging. I tried to enable it by editing build.prop and default.prop but the phone just bootloops.
Click to expand...
Click to collapse
TWRP has a terminal shell. Try it there.
wm density
And
wm size
I forgot the full commands but you'll find them. I thing wm density reset is an option and so is wm size reset
srahman53171618 said:
TWRP has a terminal shell. Try it there.
wm density
And
wm size
I forgot the full commands but you'll find them. I thing wm density reset is an option and so is wm size reset
Click to expand...
Click to collapse
Already tried it but i get an error :
cabt find service: window
efakkawy98 said:
I'm not sure though, but I think flashing Vendor+Firmware will do the trick..
And if it didn't work, what you need to do is flash stock fastboot rom... then install twrp again and flash a custom rom (if that's what you're using)
Click to expand...
Click to collapse
Tried to flash the vendor to no avail. I can get the phone back if i wipe everything /system /data everything EXCEPT storage but i have tons of apps installed and lots of custom settings and i dont want o lose them.. :crying::crying::crying:
[OP UPDATED]
Been there. The only solution was restoring 1 day old backup. It's in /data partition for sure.
If your concern is the apps. Try move folder data/app and data/data to internal storage. Reset and move back the folders before booting up.
You can also try renaming Shell.apk to Shell.apk.bak and see if it solves your problem without factory reset.
Also try renaming WMService inside /system/app.
MasterFURQAN said:
Tried to flash the vendor to no avail. I can get the phone back if i wipe everything /system /data everything EXCEPT storage but i have tons of apps installed and lots of custom settings and i dont want o lose them.. :crying::crying::crying:
[OP UPDATED]
Click to expand...
Click to collapse
Which ROM are you on?
efakkawy98 said:
Which ROM are you on?
Click to expand...
Click to collapse
I solved it somehow. I'm on MIUI EU 9.6.27. I'll update the op.
Is there a way to stock flash rom without unlocked bootloader and usb debugging enabled? I encountered the same DPI bootloop, but still stuck here.
I read somewhere I can flash without unlocking bootloader as long as it is stock rom? but how?
I tried:
adb sideload stockrom.zip
but it only returned
* cannot read stockrom.zip' *
Is there still a way to flash? It is alright for me even to wipe data.
*edit: I did not enable USB debugging, but adb devices reads the data when in "Recovery > Connect to MIAssistant"
fastboot devices also reads my phone, but i'm nowhere near being able to do any useful commands
Hi Guys. I had my solution to this for Pocophone F1. Same DPI bootloop. This solution works for locked bootloader and USB debugging OFF.
https://forum.xda-developers.com/poco-f1/help/pocophone-f1-flash-stock-rom-locked-t4084949
Related
so, I editied my build.prop on simple streak, something I have done numerous time on many roms. I changfe some ro.ril, network setting for speed. didnt work so I reverted back, deleted current build.prop, and renamed the build.prop.bak in root explorer to build.prop and reboot. now it doesnt boot up, shows dell logo then blank screen.
Im thinking either build.prop is bad or permissions not set correct, tried clearing cache dalvik and fixing permissions from streakmod recovery, no help.
my next step I think is flash clock work, mount /system, then adb shell in and check it out. Any thoughts/help for this route???
I dont have nandroid of my current rom( I know, dumb.) I have nandroid of previous roms though.
thanks guys, If I have time later I will try IRC,
if nothing in a few hours will be forced to nandroid to old build.
The clockwork route should work fine - just flash it on from fastboot and adb shell into it as you suggest.
As an alternative to nandroiding back down though, you should just be able to reinstall the current rom straight over the top of what you have - don't wipe anything, just flash it straight on. That will replace the build.prop for you, though it will also undo any other mods you've made on the system partition. Though at least it will keep your settings and data intact.
Good luck
will this keep my apps too??, probably better than factory reset huh?? thanks for the help..
Yep, it won't erase any of your apps or settings from your phone at all.
And, while I'm sure you already plan to.... as soon as you get a working phone back, Nandroid it
yeah, just bit the bullet and did it after research and found nothing..
this was a big help,
thanks so much
You're welcome - glad it got you sorted out
and nandroided...
good to go.
READ AT THE END OF THIS POST FOR THE SOLUTION
I accidentally used Titanium Backup's widget to frost all system and user apps, leaving mi phone in a infinite boot animation loop. I dont have aNandroid Backup and I would really love to solve this issue without flashing.
I found at Titanium Backup's troubleshooting webpage that I could use this command with adb to solve my issue:
Code:
Type the following command (replace with /dbdata/system/packages.xml if you have a Samsung phone):
busybox sed -n 's/<package name="\([^"]\+\)".*enabled="false".*/\1/p' /data/system/packages.xml | while read PKG; do pm enable "$PKG"; done
but it just says: No such file or directory (yes, I changed /data to /dbdata as stated in the webpage)
Any idea on how to solve this issue?
Thank you!
**EDIT:
This is the way I managed to get my phone working again without having to flash or wipe:
1. Boot in recovery mode and used adb pull command to extract "packages.xml" and "packages-more-backup.xml" from /data/system/
2. Open both files with Wordpad and replaced all protection="2" or "3" lines to protection="1".
3. Also, and very important, replaced all enabled="false" lines to enabled="true"
4. Boot in recovery again and used adb to delete old "packages.xml" and "packages-more-backup.xml" files and push the new ones.
5. Reboot and Voila!
6. Boot once again in recovery mode and fix permissions to avoid any problem.
Hope that this could be usefull to someone else having this horrible problem.
Thank you all!
Checked for that file on my phone, it doesn't exist in /dbdata/system/, but it does in /data/system/
It's probably fixable from the command line with Linux but that is over my head, one option would be to Odin or heimdel back to stock, and start from scratch. You might need a jig to get into dlmode.
Sent from my SAMSUNG-SGH-I777 using xda premium
nitox.n2o said:
Checked for that file on my phone, it doesn't exist in /dbdata/system/, but it does in /data/system/
Click to expand...
Click to collapse
I tried with /data too but same result.
shadow65781 said:
It's probably fixable from the command line with Linux but that is over my head, one option would be to Odin or heimdel back to stock, and start from scratch. You might need a jig to get into dlmode.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
I know I could do that but I would really like to restore my system as it was
Help please
I wonder what would happen if you removed the app (its apk) via adb from /data/app. Would it retain the freeze settings? Something to consider trying.
This happened to me. I reflashed the ROM without wiping and all was back to normal
Sent from my FrankenTAB using Tapatalk
Simba501 said:
I wonder what would happen if you removed the app (its apk) via adb from /data/app. Would it retain the freeze settings? Something to consider trying.
Click to expand...
Click to collapse
Pretty sure that's not gonna work because the frozen apps settings are at packages.xml file, but I can't access it I don't know why
jhermit said:
This happened to me. I reflashed the ROM without wiping and all was back to normal
Sent from my FrankenTAB using Tapatalk
Click to expand...
Click to collapse
I tried doing that right now but it didn't worked
I got a little too punchy with titanium on my 3 year old original Galaxy tab 7 and froze a samsung system app. Got irreversibly stuck is soft brickland - Tried various methods before giving up and hitting the wipe and reset to factory restore in the system recovery mode. Everything was backed up except recent photos, so it was more annoying than the end of the world.
Odd thing was when it reset to factory, it appeared to do just that, yet when I plugged it into PC and mounted it - the memory was full and all my files and app data files were there - untouched. The apps themselves have gone except one - Superuser is still there, Does Superuser somehow override being reset? and act as a guardian of your data in the event of reset?
Odd. I was expecting to run some file recovery software to a salvage what i could, but viola - it was all there.
shokuchi said:
I got a little too punchy with titanium on my 3 year old original Galaxy tab 7 and froze a samsung system app. Got irreversibly stuck is soft brickland - Tried various methods before giving up and hitting the wipe and reset to factory restore in the system recovery mode. Everything was backed up except recent photos, so it was more annoying than the end of the world.
Odd thing was when it reset to factory, it appeared to do just that, yet when I plugged it into PC and mounted it - the memory was full and all my files and app data files were there - untouched. The apps themselves have gone except one - Superuser is still there, Does Superuser somehow override being reset? and act as a guardian of your data in the event of reset?
Odd. I was expecting to run some file recovery software to a salvage what i could, but viola - it was all there.
Click to expand...
Click to collapse
Wrong forum dude
Sent from my Zanpakuto using Getsuga Tensho!
<deleted>
ZIP for unfreezing apps
For those, who accidentally frozen important system app: here quick solution without factory reset, reflashing and ADB
It automatically edits files as described in first post.
You should have unlocked bootloader. If no, ZIP useless because unlocking wipes all data.
Download both ZIP's and just flash them via custom recovery (TWRP / CWM)
If first throws error try second and vice versa. 2nd with mark "New" contains newer updater-binary that must be compatible with recent TWRP.
Then all apps will be unfrozen, so phone will boot.
Fix compatible with all Android versions.
Note: also you can somehow (ADB or filemanager in TWRP) delete file /data/system/0/package-restrictions.xml
More correct to edit that file which ZIP actually do, but deleting not harmful too.
tags: unfroze apps, auto-unfroze, defrost apps, unfreeze apps, 5596
Bonoboo said:
For those, who accidentally frozen system app there is quicker solution without factory reset and ADB.
It automatically edits files as described in first post.
Just flash this ZIP through recovery and all apps will be unfrozen.
Compatible with all Android versions.
Click to expand...
Click to collapse
THANKS MAN!! i just signed up to say thanks! you just saved my life :highfive:
Bonoboo said:
For those, who accidentally frozen system app here quicker solution without factory reset and ADB
It automatically edits files as described in first post.
Just flash this ZIP through recovery and all apps will be unfrozen, so phone will boot.
Compatible with all Android versions.
tags: unfroze apps, auto-unfroze
Click to expand...
Click to collapse
Thanks very much for the zip. It worked great
Same Problem
Does anyone have an updated version of that zip? I also froze an app linked to the device and it won't boot, even after factory resetting it. Tried running the zip on my t-mobile GS4 (probably newer than that zip) from the SD card in recovery mode, however it didn't unfreeze it.
Any help greatly appreciated!
pianoplayer55 said:
Does anyone have an updated version of that zip?
I also froze an app linked to the device and it won't boot, even after factory resetting it.
Click to expand...
Click to collapse
1. To flash that ZIP you need have custom recovery (CWM or TWRP), not stock.
No update needed, it still works in this case.
2. That strange. Maybe you not really performed reset?
Double check all and try again.
Bonoboo said:
1. To flash that ZIP you need have custom recovery (CWM or TWRP), not stock.
No update needed, it still works in this case.
2. That strange. Maybe you not really performed reset?
Double check all and try again.
Click to expand...
Click to collapse
Yup, unfortunately I did select wipe data on the recovery screen. I am also stuck in an infinite boot up loop and cannot access the phone to install any apps. How can I use a custom recovery to run the zip file if i cannot access the phone? Instructions much appreciated. Thanks again.
pianoplayer55 said:
How can I use a custom recovery to run the zip file if i cannot access the phone?
Click to expand...
Click to collapse
ZIP – it's not app.
Again, you need to install custom recovery.
Here link to TWRP and how install it via Odin on PC.
You need place that ZIP on sdcard.
Enter in recovery (don't know how on your model), select Install > find ZIP > confirm > reboot,
Bonoboo said:
ZIP – it's not app.
Again, you need to install custom recovery.
You need place that ZIP on sdcard.
Enter in recovery (don't know how on your model), select Install > find ZIP > confirm > reboot,
Click to expand...
Click to collapse
Downloaded TWRP with Odin and ran custom recovery without a change after the zip (this must have been a deeper-rooted problem in the OS itself), however in the meantime I formatted the system partition, removing the operating system. Installed Kies and ran the update. It reinstalled the OS and I'm good now. Most stuff was backed up anyways. Thanks guys for your time :good::good:
Which apk is the culprit?
Man, I wish I'd found this thread before restoring my phones internal ROM. Had it rooted and set up in every way I like except removing bloatware.
Using TB, I froze a system apk that shut down my System UI and sent the phone bootlooping. What I'm trying to determine is WHICH apk(s) I froze that caused this. I thought I had researched each one that didn't seem obvious, but I musta missed one or one of the 'obvious' ones wasn't so obvious.
I have a silly problem, I had freshly installed the unofficial CM14.x and between all the new settings forgot the Lockscreen pattern. Since i didn't want to try factory reset and other solutions without data loss didn't wird, I searched a bit and erasted the /data/system/gatekeeper.pattern.key via ADB ! It actually helped passing through lockscreen, but now I can't set any new lock (none of the options tough) / I can't go to the option… I get dropped out with an error…
What can I do??
roshak said:
What can I do??
Click to expand...
Click to collapse
Open thread in right section.
CheckYourScreen said:
Open thread in right section.
Click to expand...
Click to collapse
Well, I guessed that users in the Q&A/Troubleshoot section wouldn't have much clue about manipulating Android's /data/system/. . . files and apparently I was true! No reply since 3-4 days
roshak said:
Well, I guessed that users in the Q&A/Troubleshoot section wouldn't have much clue about manipulating Android's /data/system/. . . files and apparently I was true! No reply since 3-4 days
Click to expand...
Click to collapse
Chill.
You able to access your files and data?
Just open settings and change the screen lock to "none" or "swipe", then select pin/password and set your own.
It should fix it.
If it doesnt then make a backup of your data and clean flash stock rom by wiping system,cache and data (not internal sd).
CheckYourScreen said:
Chill.
You able to access your files and data?
Just open settings and change the screen lock to "none" or "swipe", then select pin/password and set your own.
It should fix it.
If it doesnt then make a backup of your data and clean flash stock rom by wiping system,cache and data (not internal sd).
Click to expand...
Click to collapse
Says right in the in original post that he can't set any new lock with any of the options, it just crashes. I think he's got not choice but a re-flash.
As @Tanner1294 noticed. I can't change the locksreen options anymore and that's the problem (I can't use the device without lock! But I wouldn't)
backing up data may work or maybe not, because the missing files could be under data… But I'll give it a try.
I don't know why I couldn't replace the screen password via Google Device Manager… The device was recognised and the pass and message has been sent to it, but i couldn't interact with it at all! only "emergency call" was touchable If it's an issue in Android 7.x or CM14.x dunnow
Maybe dirty flashing the ROM again will help
mcmarius said:
Maybe dirty flashing the ROM again will help
Click to expand...
Click to collapse
didn't work!
roshak said:
As @Tanner1294 noticed. I can't change the locksreen options anymore and that's the problem (I can't use the device without lock! But I wouldn't)
backing up data may work or maybe not, because the missing files could be under data… But I'll give it a try.
I don't know why I couldn't replace the screen password via Google Device Manager… The device was recognised and the pass and message has been sent to it, but i couldn't interact with it at all! only "emergency call" was touchable If it's an issue in Android 7.x or CM14.x dunnow
Click to expand...
Click to collapse
Make a backup of contacts,sms, apps(or just download from playstore) or use titanium backup if you want app data also.
And clean flash rom.
Forget everything and clean flash after making backup.
That file is related to system and has to be present in /data/system/ so will remain excluded from backups you make.
Make sure you clean flash rom.
CheckYourScreen said:
Make a backup of contacts,sms, apps(or just download from playstore) or use titanium backup if you want app data also.
And clean flash rom. . .
Click to expand...
Click to collapse
If I only knew how I can re-install my selection of apps straightforward, I wouldn't hesitate about clean flash; I don't worry about my files, contacts etc.
I'll try to figure out, how Titanium Backup works… Thanks for advice
The problem is now solved without reflashing etc.
I just had to know which other files need to be removed in addition to /data/system/gatekeeper.pattern.key
they were locksettings.db locksettings.db-wal locksettings.db-shm from the same directory!
So i removed them, whatever they may contain
then rebooted to system and everything was on the rail, i could pick a lockscreen method again.
PS: I haven't imagined that havong debugging mode enabled could make an Android system so unsecure though!
roshak said:
If I only knew how I can re-install my selection of apps straightforward, I wouldn't hesitate about clean flash; I don't worry about my files, contacts etc.
I'll try to figure out, how Titanium Backup works… Thanks for advice
Click to expand...
Click to collapse
Titanium backup is godly makes transitioning between ROMs a breeze like you never left your setup. In TB app top right corner is a blank page with check mark on it. In there you can backup/restore large chunks of apps and data. After a fresh install rooted first thing install is TB and got to that section restore and choose what you want from backup. System apps can be backup also but will find some won't work on other ROMs. Regular apps will have no such issues. There is also TB sms backup. To use that you must set TB as default sms app. Restore sms then revert back to regular sms app and open. There all your messages will be restored.
roshak said:
The problem is now solved without reflashing etc.
I just had to know which other files need to be removed in addition to /data/system/gatekeeper.pattern.key
they were locksettings.db locksettings.db-wal locksettings.db-shm from the same directory!
So i removed them, whatever they may contain
then rebooted to system and everything was on the rail, i could pick a lockscreen method again.
PS: I haven't imagined that havong debugging mode enabled could make an Android system so unsecure though!
Click to expand...
Click to collapse
You shouldn't delete " /data/system/gatekeeper.pattern.key" as "locksettings.db locksettings.db-wal locksettings.db-shm" contain your lock screen pattern. So to remove pattern just delete these files. Android device manager won't work if it reads that your device has already a pattern/PIN enabled. I guess it worked a while ago on password protected devices as well but not anymore.
I got my F1 this morning and followed everything in the pixel edition guide. After first booting my phone I saw that I lost access to my PC connection (thought the drivers went bad but that wasn't the case) and my storge seem to be completely inacccessable from TWRP (but SD card was recognized). On the device itself I can't access the zip files that I had on preboot or anything the camera shoots. I did flash the Disable forced encryption and the Magisk Zips so I'm not sure why my device got encrypted anyway!
Where do I go from here to get back my file access and (presumably) dycript the device? My theory is that I should place all the files I need to do a clean install on the SD and wipe everything. But I'm not sure if that'll prevent encryption because it didn't the first time. Also, I'd be thankful if you pointed me to which zip files combination is the most functional since there's just so many different versions of everything!
Try format data then mount your local storage from twrp (you should see your storage pop on Windows) put your rom inside and flash it again
Format data not in advance wipe and then flash dfe.
SamyakJ said:
Format data not in advance wipe and then flash dfe.
Click to expand...
Click to collapse
I've don't that, now how do I know that I got access to my files? Can't test on the what I had before since they all got wiped and The device is definitely not encrypted now but when I take photos they still don't show up anywhere. This could be a bug in the pixel camera and not file access but IDK. Is there a way to check
Abd121 said:
I've don't that, now how do I know that I got access to my files? Can't test on the what I had before since they all got wiped and The device is definitely not encrypted now but when I take photos they still don't show up anywhere. This could be a bug in the pixel camera and not file access but IDK. Is there a way to check
Click to expand...
Click to collapse
In twrp you can't see anything except zip files but I think can see in file manager of twrp(haven't tested this)
After the latest magisk update 20.0, twrp (3.3.1-0) asks to Swipe to allow modification or keep read only. I always choose swipe to allow modification as that's what you primarily install twrp for, but even after doing so twrp fails to read my internal memory. Before this magisk update it didn't ever ask me this, except for the first time i installed twrp. Just shows 0MB and fails to mount storage for backing up or repair (Repair file system gives an error code 8).
Now the thing is that everything was working perfectly fine until this latest magisk update. Rom works fine (Havoc OS v2. 5), magisk works fine, root works fine, phone is encrypted just as it was before, everything is fine except twrp and i really need twrp to keep working as it was before.
Now yes, I have removed pin/password and tried to make twrp work, switched from pattern to pin as some solutions out there say that twrp will ask for the pin on boot up and on entering the correct pin it will decrypt the internal storage and all will be fine. But no, it didn't work.
Whatever it is am damn sure its magisk. Rom is the same, kernel is what came with the rom, no magisk modules installed, infact I run magisk in core mode only (yes I have disabled core mode only to see if it fixes the problem). I have attached a screen shot of magisk home screen and you can see that under the advanced settings Force encryption is enabled (just like it was enabled while installing magisk for the first time, I have never messed with those settings) and the other two are disabled. Do i need to check that recovery mode? Whatever the solution is, it is preferable that I don't loose my rom and data. But if there's a 100% working solution which involves wiping everything then please mention that too.
Also some solutions need you to change the file format of the internal storage, and I am a little afraid to try that.
Sorry for the extra long post, Thanks in advance.
ronish.x said:
After the latest magisk update 20.0, twrp (3.3.1-0) asks to Swipe to allow modification or keep read only. I always choose swipe to allow modification as that's what you primarily install twrp for, but even after doing so twrp fails to read my internal memory. Before this magisk update it didn't ever ask me this, except for the first time i installed twrp. Just shows 0MB and fails to mount storage for backing up or repair (Repair file system gives an error code 8)....
Click to expand...
Click to collapse
Check your TWRP logs. They will contain clues as to what might be the problem. Then post the logs in your TWRP forum. You can get the logs via adb
Code:
adb pull /tmp/recovery.log
adb pull /tmp/dmesg.log
Did you try changing the storage type? That helped me once. Also what helped was using the latest or an older version of twrp, you can also try doing this. Let me know what happens.
Soojikahalwa said:
Did you try changing the storage type? That helped me once. Also what helped was using the latest or an older version of twrp, you can also try doing this. Let me know what happens.
Click to expand...
Click to collapse
Changing the storage type would be safer or flashing the same version of twrp on top of it (as I have the latest one) or an older version would be better? I will use the official twrp app for the later.
ronish.x said:
Changing the storage type would be safer or flashing the same version of twrp on top of it (as I have the latest one) or an older version would be better? I will use the official twrp app for the later.
Click to expand...
Click to collapse
Try using an older version of twrp first. Changing storage type for system or data might lead to data lose. Make a backup in any case.