Hello community,
Earlier I was messing with the voltages on setcpu, and I guess I ticked the box "set on boot" and now my phone wont boot pass the lockscreen. I don't want to wipe my phone if i don't need to.
I tried removing it via adb shell with these instructions i found:
1) Boot into recovery
2) Connect USB
3) open ADB shell - 'adb shell'
4) mount the Data folder - 'mount /data'
5) navigate to the Data folder - 'cd /data/data'
6) Remove the config file - 'rm -r com.mhuang.overclocking'
7) exit and reboot phone
but i can't mount data. any help would be great. Thank you
Hello,
The SetCPU program can generate a "safe mode" script in case that happens.
It puts it into the root directory of the sdcard.
You have to generate it from within the program, it does not do it automatically.
I have attached the file I generated on my phone, I hope it can help you.
I think the instructions will be to boot in "red recovery" then flash the safe mode file to remove the "set on boot" flag.
Do not set on boot until you are sure the OC/UV settings do not crash your phone.
Good luck!
jayson94538 said:
Hello community,
Earlier I was messing with the voltages on setcpu, and I guess I ticked the box "set on boot" and now my phone wont boot pass the lockscreen. I don't want to wipe my phone if i don't need to.
I tried removing it via adb shell with these instructions i found:
1) Boot into recovery
2) Connect USB
3) open ADB shell - 'adb shell'
4) mount the Data folder - 'mount /data'
5) navigate to the Data folder - 'cd /data/data'
6) Remove the config file - 'rm -r com.mhuang.overclocking'
7) exit and reboot phone
but i can't mount data. any help would be great. Thank you
Click to expand...
Click to collapse
A lot of the time the recovery isn't setup to properly use adb but maybe you just need to try a different command.
First see what is mounted and
ih what mount options by simply typing 'mount' in adb shell
Normally about halfway down you will see /dev/block/mmcblk0p2 /data make sure it is there and mounted read write. If it's not mounted try mounting it with 'mount -o rw /dev/block/mmcblk0p2 /data'
Or if it is mounted read only (which would be weird) try mount -o remount rw /dev/block/mmcblk0p2 /data
If that doesn't help you might need to do a nand droid backup, wipe data, reboot, create a safemode script like mentioned above, restore the nand backup and run the script in recovery.
Thank you very much for your replies. Helped me a ton. I got it fixed thanks to you guys.
Sent from my SAMSUNG-SGH-I997
Hey guys,
I just can't figure this one on my own. My phone is bricked, so I'm trying to use ADB in Recovery mode to fix it. The problem is, that 'su' always returns 'permission denied', so I can't mount system rw and that's where I'm stuck.
Phone is fully rooted - that's how I was able to brick it in the first place.
'/system/xbin/su' is also present (checked via Aroma).
Is there any way to "fix" this?
in the recovery go to mount and storage then mount /system.It will be mounted as RW.
I have the e3 stock recovery, so there are only these options:
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
use aroma file manager it have terminal.You can use it in recovery.
or try adb remount
Yes, I know about the aroma terminal and I also tried some commands in it, but without a positive result. But just to be sure, what command(s) did you have in mind?
And 'adb remount' returns:
remount failed: Operation not permitted
if you have e3 recovery that means you havent rooted your phone which means su wont work first root your phone
also it would be great if you could explain a little more as to what you want to accomplish
Oh.. That doesn't sound very good..
I need to modify some files in the system/framework folder.
Anyway, it should be rooted, because I already replaced a system file.
I just found out on the web that in the system settings on CM10 -> Developer settings -> you can set root access also for ADB.
Maybe it helps?
Symptoms:
Phone stucks at boot animation screen (4 color balls rolling)
adb devices command shows device is represent.
adb logcat shows no fatal error, no obvious cause
kernel message shows no fatal error
Cause:
Content inside /data/system/sync is corrupted(?)
Fix:
Rename or remove folder /data/system/sync
Below is the full story and how I figure it out:
3 days ago when I woke up, i find that my phone was rebooting and the screen showing boot animation. After waiting a long time, I find that the phone was stuck on boot animation. I can use adb shell to connect the phone and adb logcat to retrieve the log. The log shows nothing special or fatal, just some minor errors.
My phone is rooted, unlooked and relocked bootloader, CWM Recovery 6.0.4.4
The apps I installed that have root access included, but not limited to:
Xposed FrameworkAndroid Tuner aka 3C ToolboxGravityBoxiFontXprivacyGreenifyAFWall+BusyBoxSuperSucom.avast.android.mobilesecuritycom.avast.android.antitheft (Root install)
After Googled a few hours, 99.9% of the result tell you factory reset your phone is the fix, and i am not satisfied with that. So I used CWM recovery to made a complete backup, and tinkering with the files and system.
At first I cleared cache and dalvik-cache in recovery as this is easiest, but no luck.
Then I suspect this might be a flash memory chip problem , so I boot into recovery, use adb shell to connect console, however, adb shows that device unauthorized, so I do a factory reset and reboot recovery, then adb shell again and success, and in recovery, restore /data backup. Then I use command
Code:
%path to android platform tools folder%> adb push adbkey.pub /data/misc adb/adb_keys
, then adb is authorized after reboots.
To check if the flash memory is okay, i used the command:
Code:
e2fsck -fv /dev/block/platform/msm_sdcc.1/by-name/persist
e2fsck -fv /dev/block/platform/msm_sdcc.1/by-name/cache
e2fsck -fv /dev/block/platform/msm_sdcc.1/by-name/userdata
e2fsck -fv /dev/block/platform/msm_sdcc.1/by-name/system
The result seems fine, and no signs of hardware failure.
After reading logcat, the system seems nearly finished the booting process, and stucked at end of System service, and never signal Boot_Completed. Using Android Device Monitor, system_process main thread is still running and doing something unknown.
At this point, i think kernel and /system should be normal.
Then I suspect that the apps i installed might be the cause, I renamed the folders like:
Code:
mv /data/data /data/data.old
mv /sdcard/Android /sdcard/Android.old
mv /data/app /data/app.old
to see if the OS can boot normally, but no luck.
I also renamed many other app folders and reboot, but none of this can solve the bootloop problem.
Then I renamed /data/system and reboot, from the logcat, i can see the system is regenerating the content inside the system, and I waited for a moment, the OS booted successfully with many "xxx process stopped" error message on the screen. So at this moment I realized that content in /data/system might be the root of all evil. As Home screen is not usable with a lot of process stopped messages, I used this command to start the apps i want.
Code:
adb shell monkey -p com.yourpackage.name -c android.intent.category.LAUNCHER 1
(Need to use some game points )
Next I used command
Code:
find /data/system -mtime -3
to find out which files were altered within last 3 days. I get a list of files and folder and then I rename the folders one by one and reboot. Finally, /data/system/sync folder is confirmed as the cause of the problem.
I restored the full backup in recovery, and renamed the /data/system/sync folder to /data/system/sync.old and reboot. Phone boots normally, everything seems fine.
I don't know what, why, how exactly causing the boot problem, but the problem is solved anyway. Hope this information can help someone.
I used 40+ hrs to figure it out, and another 2+ hrs to summarize and write this.
fxxk.
Nice work!
Sent from my Nexus 5 using Tapatalk
Sir my Samsung J2 Core is stuck on BootAnimation, because of the new System Webview that i installed on Magisk, what should I do for this, Thank you in advance for your Help.
Sir my Samsung J2 Core is stuck on BootAnimation, because of the new System Webview that i installed on Magisk, then im trying to open bootloader but it is not responding. what should I do for this, Thank you in advance for your Help
TUPANGPUTi23 said:
Sir my Samsung J2 Core is stuck on BootAnimation, because of the new System Webview that i installed on Magisk, then im trying to open bootloader but it is not responding. what should I do for this, Thank you in advance for your Help
Click to expand...
Click to collapse
Probably best to ask in your devices forums. This is for the Nexus 5, not the Samsun J2 Core.
Hi,
Since a few days I'm unable to see any data in my phone via gallery or file manager or any application, and I'm unable to save any data to internal storage. (example: I'm able to use whatsapp for texting, but I can't receive/send any audio/picture and I can't access the old ones).
And I keep getting this error message:"com.android.providers.media.MediaApplication keeps stopping."
I don't know if that's what causing it or if that's just a consequence of not being able to access internal storage.
I can still see all the used storage from settings though.
Phone has unlocked bootloader, but no root/custom rom/recovery.
I saw other Oneplus users started getting the same error these days... (I have a Oneplus 6, but others have different models like Oneplus Nord).
Someone resolved by wiping system and they were able to retrieve storage content and functionality, but they lost apps data, I'm trying to find another way since I have an unlocked bootloader.
An user on stackoverflow suggested I should clean the com.android.providers.media.MediaApplication app data to regenerate the database, but I couldn't figure out how to do it
I tried cleaning media and media.module packages (not media.MediaApplication) from adb but no luck even if successful.
I tried removing "com.android.providers.media" (not media.MediaApplication, I couldn't find that one) folder from data/data with twrp file manager but no luck...
Is there a way to specifically clean "com.android.providers.media.MediaApplication"?
If anyone has any other suggestion on things to try, post it here please.
Thank you in advance
you wrote you already did successfully - obviously that is not the cause. my suspect is broken encryption (you will figure out from recovery.log)
encrypted files look like this +NiZZaTrs3RFzYegpkEk if encryption is not the reason, it could be symlinks messed up. in android enable usb-debugging and check from adb shell.
(repeat this for each result)
Code:
readlink /sdcard
readlink ...
in TWRP recovery check for files like /data/system/uiderrors.txt
/data/log
(don't know exact names) you can adb pull files to PC and inspect with wordpad or Notepad++
last but no least you can capture logcat during boot for further analysis
Code:
adb logcat > logcat.txt
if you're going to factory reset device, install Magisk from TWRP and backup apps to usb flash drive with Migrate-NG beforehand. copy all your pictures + backups to PC
Code:
adb pull -a /sdcard
if you can't install Migrate or can't get usb-otg to work, get a backup to PC at least, I can tell you how to restore single apps from it later (ignore the confirmation request "WARNING adb backup is deprecated... Now Unlock your device and confirm...")
Code:
adb backup --twrp --compress data
alecxs said:
encrypted files look like this +NiZZaTrs3RFzYegpkEk if encryption is not the reason, it could be symlinks messed up. in android enable usb-debugging and check from adb shell.
(repeat this for each result)
Code:
readlink /sdcard
readlink ...
in TWRP recovery check for files like /data/system/uiderrors.txt
/data/log
(don't know exact names) you can adb pull files to PC and inspect with wordpad or Notepad++
last but no least you can capture logcat during boot for further analysis
Code:
adb logcat > logcat.txt
if you're going to factory reset device, install Magisk from TWRP and backup apps to usb flash drive with Migrate-NG beforehand. copy all your pictures + backups to PC
Code:
adb pull -a /sdcard
if you can't install Migrate or can't get usb-otg to work, get a backup to PC at least, I can tell you how to restore single apps from it later (ignore the confirmation request "WARNING adb backup is deprecated... Now Unlock your device and confirm...")
Code:
adb backup --twrp --compress data
Click to expand...
Click to collapse
Hi @alecxs , I really hope you are still active on this forum...
Probably you won't remember this discussion from back in the days (This was the previous part of our exchange if you would like to refresh your memory).
In the end I ended up using my phone in that state for more than one year with the plan of changing phone soon and not have to deal with the wipe and restoration on the same device (if that's not procrastination.... ).
Well, last week I dropped the phone and the screen died. I bought a pixel 7 as a replacement but now I would like to try to save the data of just a few apps. Most important one being Whatsapp, I don't really care about the rest...
So basically:
-the screen is dead but touch is still working and I was able to get scrcpy to work so I can still use it as a "normal' phone from my computer, so that shouldn't be an impediment.
-as previously stated the phone is not able to access internal storage, but I'm able to access it in recovery mode through adb so pulling files should not be an issue.
-I'm able to install and update apks through adb install.
-whatsapp was not able to execute backups during this year since it could not access internal storage, so I have only old ones.
-bootloader is unlocked, I have twrp but no root.
I still need to try your suggestion above, but wanted to ask this before cause maybe you have a different suggestion to extract a single app. Also, I don't really know how migrate works but if it saves the backup on the internal storage I think that's not gonna work cause every app that needs to save something (that isn't data) doesn't work.
Isn't there a way to just copy the data folder of the app on the new phone to transfer data (like what happens for mac apps)?
Thank you in advance
0xCuter said:
-as previously stated the phone is not able to access internal storage, but I'm able to access it in recovery mode through adb so pulling files should not be an issue.
Click to expand...
Click to collapse
yes, if that is true all fine, you can run the Migrate_EMERGENCY_FLASHABLE.zip from recovery and restore app data on other device with Migrate
alecxs said:
yes, if that is true all fine, you can run the Migrate_EMERGENCY_FLASHABLE.zip from recovery and restore app data on other device with Migrate
Click to expand...
Click to collapse
Hey, it's me again... So, I rooted my new phone and I found the emergency_flashable.zip in the migrate thread, now I just need to flash it, but I cannot use scrcpy in recovery mode to see the screen. I guess there is a way to flash the zip from adb without the need to use the screen, but better to ask since I don't want to do stupid stuff...
yes, you can do it from adb. best is MicroSD Card as target directory. copy the zip into the target directory, mount data system vendor product, then install zip. on the first trial it will fail because packages.list needed. but it will create one you can edit. delete unwanted packages before second trial. you can repeat as often you want, existing backups won't created twice.
Code:
adb push Migrate_EMERGENCY_FLASHABLE.zip /sdcard
adb shell
# mount /system_root
# mount /system
# mount /vendor
# mount /product
# mount /external_sd
# mkdir /external_sd/Migrate
# cd /external_sd/Migrate
# mv /sdcard/Migrate_EMERGENCY_FLASHABLE.zip .
# twrp install ./Migrate_EMERGENCY_FLASHABLE.zip
# exit
adb pull /external_sd/Migrate/packages.list
edit the file with editor and push it back
https://twrp.me/faq/openrecoveryscript.html
alecxs said:
yes, you can do it from adb. best is MicroSD Card as target directory. copy the zip into the target directory, mount data system vendor product, then install zip. on the first trial it will fail because packages.list needed. but it will create one you can edit. delete unwanted packages before second trial. you can repeat as often you want, existing backups won't created twice.
Code:
adb push Migrate_EMERGENCY_FLASHABLE.zip /sdcard
adb shell
# mount /system_root
# mount /system
# mount /vendor
# mount /product
# mount /external_sd
# mkdir /external_sd/Migrate
# cd /external_sd/Migrate
# mv /sdcard/Migrate_EMERGENCY_FLASHABLE.zip .
# twrp install ./Migrate_EMERGENCY_FLASHABLE.zip
# exit
adb pull /external_sd/Migrate/packages.list
edit the file with editor and push it back
https://twrp.me/faq/openrecoveryscript.html
Click to expand...
Click to collapse
One thing I forgot to ask: do I need to root my old phone as well or is twrp sufficient?
And to root I would just need to flash Magisk the same way I would flash the emergency flashable.zip right? Or can I just "twrp install [magisk_package]" without going into the shell?
No need to root old phone, TWRP already provides root access for backup purposes. the new phone should be rooted by flashing magisk patched boot.img because the TWRP install method is deprecated. I know I gave only short hints, so don't hesitate to ask for more detailed instructions in case you don't know what to do for some specific step...
alecxs said:
No need to root old phone, TWRP already provides root access for backup purposes. the new phone should be rooted by flashing magisk patched boot.img because the TWRP install method is deprecated. I know I gave only short hints, so don't hesitate to ask for more detailed instructions in case you don't know what to do for some specific step...
Click to expand...
Click to collapse
Thank You... Yes, the new phone is rooted.
One thing that's not needed for the process but I wanted to understand is: Is there a specific reason why we "twrp install" from shell or could in theory be possible to flash the zip file directly from pc storage?
0xCuter said:
or could in theory be possible to flash the zip file directly from pc storage?
Click to expand...
Click to collapse
the reason is, the backup is created locally in the same directory where the zip file is. never tried sideload but I guess it would try to store in /tmp which is RAM.
alecxs said:
yes, you can do it from adb. best is MicroSD Card as target directory. copy the zip into the target directory, mount data system vendor product, then install zip. on the first trial it will fail because packages.list needed. but it will create one you can edit. delete unwanted packages before second trial. you can repeat as often you want, existing backups won't created twice.
Code:
adb push Migrate_EMERGENCY_FLASHABLE.zip /sdcard
adb shell
# mount /system_root
# mount /system
# mount /vendor
# mount /product
# mount /external_sd
# mkdir /external_sd/Migrate
# cd /external_sd/Migrate
# mv /sdcard/Migrate_EMERGENCY_FLASHABLE.zip .
# twrp install ./Migrate_EMERGENCY_FLASHABLE.zip
# exit
adb pull /external_sd/Migrate/packages.list
edit the file with editor and push it back
https://twrp.me/faq/openrecoveryscript.html
Click to expand...
Click to collapse
I'm trying and when I do "mount /system" from the shell I get this:
mount: '/system' not in fstab
Click to expand...
Click to collapse
Is it normal?
it's either /system_root or /system so one of it will fail. I just listed both.
alecxs said:
it's either /system_root or /system so one of it will fail. I just listed both.
Click to expand...
Click to collapse
I suspected that... is it the same for product and external_sd?
Only system_root and vendor went through
/external_sd is the mount point for MicroSD Card, it may have a different name like /sdcard1 or something. if you have enough disk space on /data, no need for external SD.
/product is maybe not needed, just running with /system_root + /vendor is fine.
alecxs said:
/external_sd is the mount point for MicroSD Card, it may have a different name like /sdcard1 or something. if you have enough disk space on /data, no need for external SD.
/product is maybe not needed, just running with /system_root + /vendor is fine.
Click to expand...
Click to collapse
There is no external MicroSD on Oneplus 6... can I put the migrate folder in /sdcard?
Also, I think I should delete some stuff from storage to make space, since I already pulled it on the pc
/sdcard = /data/media can be used. you can split the packages.list file into few parts so it fits in remaining disk space.
alecxs said:
/sdcard = /data/media can be used. you can split the packages.list file into few parts so it fits in remaining disk space.
Click to expand...
Click to collapse
I tried the install and I get this, even though the zip file is in the same folder I'm in (it even autocompletes from terminal)
OnePlus6:/sdcard/Migrate # ls
Migrate_EMERGENCY_FLASHABLE.zip
OnePlus6:/sdcard/Migrate # twrp install Migrate_EMERGENCY_FLASHABLE.zip
Unable to locate zip file 'Migrate_EMERGENCY_FLASHABLE.zip'.
Installing zip file 'Migrate_EMERGENCY_FLASHABLE.zip'
Error installing zip file 'Migrate_EMERGENCY_FLASHABLE.zip'
Done processing script file
Click to expand...
Click to collapse
make sure you give a path to zip file on install, like ./ or full path. it will fail on first execution. check if packages.list was created successfully.
alecxs said:
on the first trial it will fail because packages.list needed. but it will create one you can edit.
Click to expand...
Click to collapse
you can always pull recovery.log afterwards to see what's going on.
Code:
adb pull /tmp/recovery.log
alecxs said:
make sure you give a path to zip file on install, like ./ or full path. it will fail on first execution. check if packages.list was created successfully.
you can always pull recovery.log afterwards to see what's going on.
Code:
adb pull /tmp/recovery.log
[/cod
[/QUOTE]
Click to expand...
Click to collapse
It launched with the full path. I didn't edit the package.list file and I launched it again.
I got a lot of "migrate.sh: failed:..." and just a few "migrate.sh: finish:..." mostly for system apps, but honestly I really only need to backup whatsapp...
...
Click to expand...
Click to collapse
migrate.sh: failed: com.intsig.lic.camscanner
migrate.sh: failed: com.android.theme.icon_pack.ci
migrate.sh: failed: com.google.android.apps.restor
migrate.sh: 397x packages failed / 0x already exist
# MIGRATE_STATUS: backup finished (27/424)
# DONE.
#
# exiting script
#
# # # # # # # # # # # # # # # # # # # # # # # # # #
Updater process ended with ERROR: 1
I:Install took 69 second(s).
Error installing zip file 'sdcard/Migrate/Migrate_EMERGENCY_FLASHABLE.zip'
Done processing script file
Click to expand...
Click to collapse
These are the things that have been backed up:
OnePlus6:/sdcard/Migrate # ls
Backup_android Backup_com.google.android.networkstack
Backup_com.android.bluetooth Backup_com.google.android.packageinstaller
Backup_com.android.cellbroadcastreceiver Backup_com.oneplus.screenshot
Backup_com.android.emergency Backup_com.qualcomm.qti.cne
Backup_com.android.inputdevices Backup_com.qualcomm.qti.poweroffalarm
Backup_com.android.location.fused Backup_com.qualcomm.qti.smq
Backup_com.android.phone Backup_com.qualcomm.qti.uceShimService
Backup_com.android.providers.blockednumber Backup_org.ifaa.aidl.manager
Backup_com.android.providers.settings Backup_se.dirac.acs
Backup_com.android.providers.telephony Backup_vendor.qti.hardware.cacert.server
Backup_com.android.proxyhandler Migrate_EMERGENCY_FLASHABLE.zip
Backup_com.android.server.telecom backup_app_and_data.sh
Backup_com.android.settings busybox
Backup_com.android.shell migrate.log
Backup_com.android.stk migrate.sh
Backup_com.android.systemui packages.list
Backup_com.google.android.ext.shared readme.txt
Click to expand...
Click to collapse