I installed twrp on A605 device by somehow(just ask me), but it looks drunk.
Terminal is not working, and i got "permission denied" on everything
i can't even access to my sdcard and internal storage!
and MTP is not working..
i used this recovery: https://gitlab.com/HosteBin/noobdev/raw/master/samsung/a6plte/TWRP_a6plte-140918.img
i hope i can fix this...
I've also tried that TWRP, but almost nothing works on it because of permission problems. We still have to wait
Related
I'm running Modaco's Froyo FRF91 on my Nexus one. The recovery is Amon-RA's v.1.7.0.1 - the latest.
I tried eViL D's latest Froyo ROM and it was awesome except I had no phone. Just data. Time to wipe and restore.
I did a full wipe, including ext + repair and when I tried to do a Nandroid restore, I got the "nandroid-mobile.sh" via ADB message.
For some reason ADB wouldn't see my phone.....I had updated the udev for the N1, restarted udev and no luck. Tried as root. No luck. Just "????????? No permissions"
OK....whatever.
So still in recovery, I moved the recovery log to my sdcard....to keep it....and tried the restore again - just for the hell of it - and it worked fine the second time. No error message.
I don't know if moving the recovery log to SD had anything to do with it....but that's the way it went for me today.
All good...but not knowing why.
After the re-boot into my restored system, ADB could see the phone just fine, listing it's device ID.
Again...no idea why.
I hate it when stuff works just after you needed it....and you don't know why.
Has anyone else seen this? Just try it again and it works?
try removing spaces from the directory name of the anndroid backup.
If you actually search the forum for that error message, you'll find plenty of info and reasons why it happens, The most common being your battery was too low when you tried to restore. Charged it up and then it works.
When I've gotten that error, running an error scan on the sd card fixed the issue.
Sent from my Nexus One using XDA App
Basically I reboot and install the .zip like normal...says it installs...but when I reboot they're not there. When I reboot and try to mount the file systems to check I get this error:
e:can't mount /dev/block/stl9
(file exists)
I get that trying to mount anything. That's about as much of an error message as I can come up with. Beyond it not working I'm not sure what else to do. I used titanium backup and tried to side-load some backups I had of Market and such and was just going to get the other apps like that but it comes up and flashes back to desktop real fast. I went Cognition>CM7...then when this happened I went back to stock, formatted my internal SD, then brought it back up to CM7 from stock...still no dice. Any help would be appreciated.
For some reason adb wouldn't work. I could adb before flashing to CM7 but afterward, it's like the driver no longer worked. I downloaded the latest SDK driver and pointed it over to that but it still wouldn't work. So I ended up enabling the wireless adb option and that worked like a charm. I pushed the files to /system/app wirelessly and rebooted. That let me setup my accounts and at least get to market but it caused the apps to hang. I redownloaded all the apps from market(probably unnecessary) and ran Fix Permissions from clockwork and I'm in business. I just wish I knew why I was having that mount issue. I think it may cause me problems in the future.
If you don't have nexus s drivers installed you wont be able to mount adb. Once you install those you should be good to go. I had the same problem.
I'm starting this thread to move the topic out of another forum.
I encountered the issue of TWRP not being able to write to the internal storage after downgrading to 4.4.4 and only flashing the boot, system & baseband images from the KXE package Motorola provides.
It gave the error message errno=13
It gave the same error on 4.4.4 & 5.0
I had double-checked all permissions & symlinks.
To fix the issue I had to re-flash the KXE recovery, reboot the bootloader & then reflash TWRP 2.8.6.0, then all was well with both 4.4.4 & 5.0
adm1jtg said:
Not sure if this solves the error 13 or not but I can confirm using your process exactly OTG is still broken on 2860 and still works in 2850 so separate issue I would guess but since I need OTG for my backups and restores I will keep using the modded 2850 for now. Can you confirm on your setup if OTG works or not from within twrp. On mine the drive light doesn't even come on, I cannot mount it it just vibrates and I cannot backup to it. All the correct options are there but it cant access the drive at all..
Click to expand...
Click to collapse
@adm1jtg Can you backup to the internal storage?
defcondev said:
@adm1jtg Can you backup to the internal storage?
Click to expand...
Click to collapse
I had other weird issues. Initially mine would backup internally just fine but those files could not be viewed from rom side aka root explorer and such couldn't see files. Only twrp could see the backup files. I then formatted the sdcard and got the error #13 error.
To be honest I FINALLY got my phone setup and backed up the way i want it. The newly re-released 2850 works in all aspects I have tested, aka no error 13, can see files backed up internally on rom side, can see and use otg thumb drive for both backups and restore. Since 2850 works for all I need I really am not overly motivated to test much with 2860 just to be honest with you.
Since I confirmed that OTG is still broken in 2860 that makes using 2860 a deal breaker for me.
adm1jtg said:
I had other weird issues. Initially mine would backup internally just fine but those files could not be viewed from rom side aka root explorer and such couldn't see files. Only twrp could see the backup files. I then formatted the sdcard and got the error #13 error.
To be honest I FINALLY got my phone setup and backed up the way i want it. The newly re-released 2850 works in all aspects I have tested, aka no error 13, can see files backed up internally on rom side, can see and use otg thumb drive for both backups and restore. Since 2850 works for all I need I really am not overly motivated to test much with 2860 just to be honest with you.
Since I confirmed that OTG is still broken in 2860 that makes using 2860 a deal breaker for me.
Click to expand...
Click to collapse
I had that issue as well (not being able to view the TWRP folder);
The folder wasn't showing up in storage/sdcard but was showing up in data/media/0
To fix this there are a couple things you need to do;
1. Using a terminal emulator, execute the following command
su
restorecon -FR /data/media/0/*
2. Using a root-enable file browser, go to /data/media/0/ and change both the Owner & Group of the TWRP folder to "media_rw" (without quotes) and make sure permissions are set to drwxrwxr-x
defcondev said:
I had that issue as well (not being able to view the TWRP folder);
The folder wasn't showing up in storage/sdcard but was showing up in data/media/0
To fix this there are a couple things you need to do;
1. Using a terminal emulator, execute the following command
su
restorecon -FR /data/media/0/*
2. Using a root-enable file browser, go to /data/media/0/ and change both the Owner & Group of the TWRP folder to "media_rw" (without quotes) and make sure permissions are set to drwxrwxr-x
Click to expand...
Click to collapse
Different scenario as i had that happen to me on my 2013 where it went into a 0 folder. This was not the case on the 2014 it LITERALLY didnt exist anywhere, the twrp folder existed with NOTHING under it. But in twrp all files and file structure were visible and working. Mass storage did show the space being taken up of course.
Just to clarify all this mess and all these issues are cause I was going back and forth between lp and kk. It was not REALLY an issue with twrp per say EXCEPT the otg not working... that IS specifically a twrp issue near as i can tell
Alright, maybe I did something stupid, but I don't think so...
I unlocked the bootloader, used the R2 version to remotely launch TWRP (can't get the phone to do it) and then rooted with Magisk. All as recommended.
Ad Away wouldn't work because the permissions weren't set right for system/etc/host directory. So, I used Solid Explorer to change the system directory permissions (rwxrwxrwx -R). Probably overkill, but just wanted to eliminate the issue of permissions.
Shortly after executing the command, I got an error "couldn't remount" and the phone rebooted into a bootloop, which leads to a recovery that won't launch (TWRP won't launch from the phone).
I can stop the bootloop and get into the bootloader, but can't "see" the phone in PC ADB.
Anyone have advice on how to proceed?
In bootloader or recovery it wont be ADB but Fastboot. Try "fastboot devices" and see if the pc sees it.
Also Magisk is a systemless root and they have in option in their main app to allow host file to be written to system/ect/host/.
Hi,
I am in a bit of trouble I have a Motorola Edge 20 (2022) and I was playing with De-Bloater under Magisk. It worked really fine until I pushed the limit of how many Motorola apps i can remove. The last one was the wrong one, I think it was Motorola settings storage (provider) or so. Now the phone won't boot anymore and I was stupid enough not to back up the photos I made in the last three days.
I don't have TWRP on the phone (it's not available yet), so the Android recovery has to do. I saw that I can mount /system, but I don't know how to modify or even read it after mounting it. The internet is full of instructions of how to mount it and always mentions that you can then modify anything on it, but nowhere does it explain exactly HOW to do that
adb shell/push/pull just says "unable to... : closed"
The second option seems to adb sideload some zip. But what zip would I have to flash to disable the De-Bloater without factory resetting everything?
thanks
whoohoo! I jst discovered Safe Mode. Immediate problem thereby solved However, I am still interested in the first part of my question: how to use the mounted /system in Recovery Mode?
michael-brade said:
whoohoo! I jst discovered Safe Mode. Immediate problem thereby solved However, I am still interested in the first part of my question: how to use the mounted /system in Recovery Mode?
Click to expand...
Click to collapse
with stock recovery, youre unlikely to win as /data is decrypted (usually) and /system is largely unmountable and writeable (at least easily)
the usual prescription if you cant get into safe mode is:
Code:
adb wait-for-device shell magisk --remove-modules
from the bible (read on for TWRP ways which are 100% easier):
Magisk - Installation and troubleshooting:Magisk and MagiskHide Installation and Troubleshooting guide
didgeridoohan.com
which obviously removes all modules, even us experienced folks fond ourselves using the magical key combo to get into safe mode on occasion because we flew too close to the sun doping something in magisk
ironically debloating wasnt one of those times for me, i gave a log of what i debloated to the author of one debloater modules recently when he released a new version of his module and he was like "and it still boots?"...the list of debloated packages was at 135, and i could remove even more...
Thanks, good to know. But even adb wasn't able to connect anymore, Android got stuck even earlier.
However, I don't really mind if /system is read-only, I am more interested in how to (even theoretically) use the stock recovery. There is no manual and nobody said anything so far. So once you clicked "mount /system", what to do?
Lenovo (owner of Moto) has a online 'rescue' site that u can go to with your phone connected to the PC and it'll flash your Moto back to stock...prolly won't retain ur data, but it saved my a$$ a few times with my old twrp-less A/B slotted Moto G7. Can't recall the exact url but am sure u can dig it up with google.
Zaxx32 said:
Lenovo (owner of Moto) has a online 'rescue' site that u can go to with your phone connected to the PC and it'll flash your Moto back to stock...prolly won't retain ur data, but it saved my a$$ a few times with my old twrp-less A/B slotted Moto G7. Can't recall the exact url but am sure u can dig it up with google.
Click to expand...
Click to collapse
Hmm... but I can already do that without their help using fastboot. No need for the Android recovery.
Isn't it strange that there is a function we don't know how to use or how it works?