I trashed my rooted Lollipop ROM by renaming a system file & now it gets stuck in a bootloop. I was hoping to restore the old filename using adb. I can boot into stock recovery adb but it's stuck at sideload. Is there a way to change it to adb shell? Will renaming the system files back to their original names trip Knox?
EDIT - never mind, I just went for a reinstall
Related
I tried to prevent my phone from updating to 6.2.1 by changing /system/etc/otacerts.zip to /system/etc/otacerts.zip.bak. When I did this it rebooted into CWM and looks for update.zip (i renamed it b/c i didn't need it). now it loops because I can't choose to anything other than install update.zip
ADB won't find the device so I can't rename the file or push a new one. I built a factory cable which appears to work but I still can't see my KF. When I run lsusb it shows 1949:0006 Lab126 as the device.
Any ideas?
using Ubuntu 10.10
<update>
I can adb shell now. however, no adb functions seem to work. Anyone know how I can keep cwm from hi-jacking my boot? I would gladly go stock to get going again.
I tried to follow this thread: http://forum.xda-developers.com/showthread.php?t=1356257
But I am getting the errors: adb: not found -or- adb permission is denied. how can I solve this? I have the original framework-res.apk. However, I screwed up with the one on my kindle and now it is bricked at the logo screen.
HELP?
i was having the same problem - where i was going wrong was not remounting the kindle device via adb
once i ran adb remount i was able to get the file back in place.
Sorry, but I really can't mount ADB Remount.
No adb commands will work for me. I either get:
-exec '/system/bin/sh' failed; No such file or directory (2)
-or-
adb: permission denied
-or-
the other error listed above.
My question; can someone walk me through step by step what to do if I bricked by messing up the framework-res.apk? Please?
Do you have TWRP? Did you take a backup first? You shouldn't be messing with system files that are required for booting without doing this first. The procedure for recovering should just be booting into TWRP and restoring your backup. Backups backups backups.
If you don't have a backup, but do have TWRP, does adb work in TWRP so you could try it there? (I'm at work so I can't double check that)
If none of these work, you might be able to get the system to boot into fastboot and get TWRP on there, Vashypooh or one of the TWRP guys would be more helpful than I would be for that. The only other option is a factory cable (there's at least one thread on here for that).
For anyone who has rooted without also installing the custom recovery, my advice is to install it right away, especially if you plan to do any modding.
I messed up my KF editing settings.db file. Somehow I changed the ownership and permissions. After that, wouldn't boot, just kept boot looping. In the boot loop mode, I could talk to it with an adb shell, but couldn't acquire root permissions to fix it.
So I booted into recovery, used the graphical menus to mount the drive, then while at the recovery screen, used adb to get a shell, get root, and then fix the files. Worked perfectly.
Seems from looking for posts to resolve this that lots of people end up messing up the settings.db file. Careful of the permissions and ownerships. If you push a file back from your PC, they might change on the linux side.
It was a lifesaver.
Thanks devs.
Hey guys. just wanted to share how I got access to all files (no sms/mms though) on a screen locked, non-rooted, stock rom Samsung S5 (in this case also with a black and broken screen with no touch).
First of all, thanks to FuzzyMeep Two and his post -> http://forum.xda-developers.com/showthread.php?t=2339530
The trick is to access the phone with ADB commands and copy the files that way. The problem is that stock recovery doesn't support adb commands, so first off we must flash a custom recovery. This has to be a terrible security breach on Samsungs part, as flashing a custom recovery won't wipe the phone.
What I did was download Odin (Samsung flash tool) and a CWM custom recovery. Then I entered download mode on the samsung and flashed the recovery no problems. Then I rebooted the phone in recovery mode.
From here on I used the above mentioned post, with the custom recovery I could find the phone with ADB devices command and thereafter run the program ADB data recovery which pulls all the files from the phone and puts it on you'r harddrive.
Hope this post will help someone, and thanks to XDA for all the help I have gotten on this site.
So it had been a while since I had tried getting into recovery twrp but I figured I could remember how so I did
fastboot flash boot twrp etc.img
This was a mistake according to the site here > https://twrp.me/nokia/nokia6_1.html
WARNING: If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
Click to expand...
Click to collapse
Which is exactly what I did
So now my phone is either stuck on the Nokia logo, or I can load twrp.
They provide some info on fixing it but I'm not sure I understand what they are saying. Can anyone help with this?
The phone was running Oreo (not sure which version unfortunately) and it was fully rooted and running magisk/xposed/su just fine before my mistake.
I don't have access to fastboot. Only Twrp and adb commands.
Edit, I can get to fastboot/download mode through the twrp terminal.
[SOLVED]
So I was able to use twrp to copy all of my internal files onto an sd card.
Then I set about getting this tool here > https://github.com/RaghuVarma331/Nokia-Tool the firmware specific to my phone, and modifying the bat file found here > https://github.com/RaghuVarma331/Nokia-Tool/blob/master/batscripts/Nokia-Tool-DRG-B2N-PL2-CTL.bat (because windows for some reason gave me a 16 bit application warning when I tried to use the tool exe)
My phone flashed a bunch of time and I was able to load up an almost entirely stock android 10, still capable of using magisk, edxposed, etc.
And now all there is to do is to get everything back onto it and set up which is at this point, the best case scenario.