Hi people. Today I needed to install a file inside system/etc/permissions to enable OTG Host. Since I couldn't create a file there, I had the stupid idea of changing the permissions of the system folder. I changed it with root browser, to Owner: read/write/execute (the other stuff was unchecked). My phone turned off instantly, and now it wont turn on at all. Seems like I'm in big trouble. Still, I want to ask if something like that is recoverable somehow, and if anyone can point me in the right direction.
Phone: Samsuing A5
OS: Android 6.0.1
Root: Yes (systemless, with Odin)
Custom Recovery: No
Edit: I just connected the phone to my PC, and it detected a USB device called SAMSUNG_Android. It's weird, the phone seems to be off. Kinda gives me a bit of hope, but I'm a noob with these things.
Edit2: I waited a few minutes and tried to turn it on again. It worked! But now it boots to recovery, so it seems to be a soft brick. Factory Reset doesn't seem to do anything, I guess I'll have to flash a ROM. But I have no idea how to do that. Any help?
Edit3: With the help of a friend, I installed TWRP custom recovery, and used it to flash a Resurrection Remix ROM and GApps. However, I cannot make it reboot into system. It always goes to recovery. When booting, it shows the message "Recovery is not Seandroid Enforcing", and then opens TWRP recovery. I can see my device has a system folder with stuff in it, but I can't make it boot properly. Any suggestions?
Related
If I am unable to enable USB debugging, am I pretty well S-O-L? I can get my phone to boot to android recovery utility, but because I did a factory reset, usb debugging is disabled. I cannot seem to get a custom recovery installed. My friend said that I should be able to download a custom recovery and install it from a zip from the recovery menu; is this possible? I am getting really frustrated because I cannot get my phone up and running again, any help would be greatly appreciated.
Backstory:
I rooted my phone with no problems, started messing around with my build.prop to try to run a gameloft game. I made a back up of my original build.prop and stored it on my sd card. I replaced my entire build.prop with one from another phone and rebooted but my phone shows lg logo(at the suggestion of the same friend who has been trying to help), I hear the tracfone sound as if it is booting up, but my screen just remains backlit with no images. I am able to get into android recovery utility as well as the so-called emergency mode. However I cannot get the phone up and running again.
Hi All.
So I'm not new to rooting / ROMs (nor am I an expert, as you'll see), but somehow have totally screwed up my tab. I've now honestly done so many things to try to recover, that I couldn't begin to summarize how I got into this mess, but I'll try.
Model is GT-P5113. Most recent working ROM was SlimLP 5.1
I went to flash CM12.1 (using CWM) and God only knows what happened. After it flashed, I tried to reboot and it would only go to CWM recovery. If I chose to reboot device, it would only shutdown, not reboot (This was actually one of the issues I was having with SlimLP as well, so I don't think the flashing had anything to do with that???)
After many attempts at reinstalling CM and SlimLP (I used the same Zip that had worked previously with SlimLP, and the flashing would say installed) it would still only boot to recovery. I finally said, screw it, I'll just start completely over
So attempted to go back to stock 4.2.2 using Odin3.09. Got the stock ROM off SamMobile site. ODIN seemed to flash,but again when it would go to reboot, it would just power down and a charging battery would show up. So I would unplug from the computer, push power button. When it powered up, it would say Installing system update, then after the status bar moved a bit, it would say Error and shut down. When I restart, it very briefly says installing system update, then show the dead android with a red triangle and No Command, and it would boot to the stock android system recovery (I assume CWM was taken off in the process). In yellow, under the stock recovery it says
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : XAR
Successfully applied multi-CSC.
I've tried installing the other ROMs again, this time with TWRP, but only for it to boot to recovery after the Samsung Tab 10. 1 logo.
I have no clue where to go from here. No clue if I'm still rooted (doubt it). At this point I don't care. I just want a functioning tab. I've spent hours searching, but nothing works. I'm open to any / all ideas.
Thanks
Aw, show me a little love, bros. Someone' gotta know something. I'm not above begging / pleading.
I can give more info, less info, post somewere else. Just let me know,and help me resuscitate my tab.
thanks again!
Hello all.
I'm new to modifying my android (Galaxy S7 G930A) and could use some help. I have successfully rooted my phone, but have had some issues trying to flash a custom recovery. I was trying to flash TWRP but for some reason it didn't work, and I would always boot into the stock recovery.
Today, I screwed something up while trying to figure out my host of issues (I was also trying to figure out why I kept getting a "dm-verity verification failed" notice when flashing). Using the TWRP Manager app, I tried to install the recovery that way and it kept giving me an error that it was either already installed or encountered an issue of some kind. Knowing it wasn't installed, I looked for a different route. Long story short, I downloaded Flashify and then manually downloaded and flashed the TWRP recovery img and a "no-verity-opt-encrypt" file - which I read would fix the dm-verity error I was receiving.
I believe that's all I did before this recovery boot issue starting occurring.
Now, when attempting to boot into recovery (no matter what way, through an app, manually, etc) the blue text "Recovery Booting..." appears for half a second and then disappears. If I'm holding down the buttons it will flash again and disappear again, over and over. If I don't hold down the buttons, when it disappears the phone boots up as normal. So now I can't seem to access recovery at all. I wanted to try going the hard/factory reset route, but obviously can't because I can't access recovery.
Also, I don't know if this is related or not, but now my laptop will not recognize my phone at all. Doesn't give me any options - it will charge, but no connection. I was hoping to load it into Odin and do a stock reset to start from scratch before flashing a custom ROM.
Edit: I tested and connected to a different computer just fine, so there's obviously some miscommunication going on between my phone and laptop.
Can anyone help me out here? Sorry for the long post, I'm just really frustrated. :crying:
hello, recently i bought myself a new op6, as it was good for modding and such. unlocked the bootloader, flashed twrp, and rooted it the day after, used it for a couple of days, before I installed elementalX. was happy with that for some days. then I decided I wanted to try out lineageOS, in order to de-google my self, in my quest for privacy.
TL;TR:
mtp is not working after flashing, neither is twrp, cant even access it through fastboot with booting the .img file.
does this have something to do with the a/b partition thing on these phones, perhaps?
I would guess that I flashed lineageOS the wrong way, and that is the issue, but since I cant access twrp, I cant restore and reflash the correct way.
more detailes below
--------------------------------------
backed up before installing elementalX, to have something to go back to, in case of failure
rebooted into twrp, and wiped everything, exept internal storage (i looked this up several places, prior to flashing, that this was the way to do it, so assumed this was the correct way)
flashed lineageOS 15.1
wiped dalvik and rebooted
took ages to boot, so figured id reboot again a couple of times, with no succsess
tried to boot to twrp, to restore back state prior to flashing, but ended up in lineageOS' own recovery.
tried to boot from fastboot, and reflash twrp
goes out of bootloader and screen turns black, led turns on, and nothing. tried waiting for a bit, but nothing seems to happen
have to manually turn of phone, and reboot. tried this several times, but same result.
after reboot i turned to the recovery to look after any solutions there, but nothing
started adb, just to check, and it says "device unauthorized"
sortof gave up, so figured I could atleast get going installing apks, but after downloading f-droid, I couldnt get it to install
found out this was some sort of permission issue, so had to move it to internal storage to get it to install
after installing some apks, I was going to transfer my contacts from my pc, but cant get mtp working..
if someone know a soulution to this, I would be really greatfull, as Im at a loss. cant seem to find anyone who has had a simillar issue..
You can always use EDL and MsmDownloadTool. Check that thread
thanks, will definetly check that out.
now it apears that I have another issue, the key for adb is no longer valid. i did get the prompt when I connected the usb, but that didnt appear to do anything. have tried to revoke it, reanable, reboot both phone and pc, also delete the keys on my pc. I have no root access anymore, so cant really enter the root on my phone, to pull out the keys there, neither can i push my own keys, as it seems atleast. I may be doing it wrong too, for all i know..
If you can enable debugging and see your phone with adb devices, you can adb push /sdcard/<romfile>.zip
I am able to enable debugging mode, yes. Will this enable me to push my own key, or any other existing key for that matter, to remove the unauthorized label?
Id also like to at that i done goofed when flashing lineageOS. Ive come to and understanding that I have to flash OOS 1.5.1 (i think that was it) on both slots, before then flashing the custom rom onto the device, and reflashing twrp after that. Which i did not do. I also were running pie at that time, so theres another mistake I made to begin with. Neither was I really aware of the concept of a/b partition system at hand..
Can i switch slots in fastboot, and then boot inton twrp, and reflash back to OOS 1.5.1, on both slots, and then reflash LOS 15.1? And ofcource reflash twrp and root afterwards, which totally slipped my mind..
Hello everyone,
This is my first post on this forum, sorry in advance if the format is not correct.
Here's my problem: I was given a SM-J710FN that displayed an overheating problem on the screen while the phone was not heating at all, as well as buttons at the bottom of the phone were not working anymore.
I reset the device to factory default, erased the data from the recovery mode and flashed the 8.1 Oreo version with a ROM STOCK J710FXXU6CSK1
After all these manipulations, the buttons still did not work and the overheating message still appeared, preventing the phone from being charged even when it was switched off.
So I thought of programmed obsolescence, and thought it was worth trying to downgrade the phone to 7.0 from version 8.1.
Could you help me on this subject and tell me what you think?
Sorry for the up
try flash a custom rom, it does not need buttons, like this https://www.google.com/url?sa=t&source=web&rct=j&url=https://m.youtube.com/watch?v=veWLleEULe4&ved=2ahUKEwigx7TjmoTvAhVUIIgKHWbJCjIQ28sGMAJ6BAgFEBc&usg=AOvVaw3xJ6phS4kotjx4fk6Ypfuq
home button work or not
Thank you for the answer, I really appreciate it
Here is the update since I followed the Youtube link you sent me:
I have transferred the Custom ROM (Pixel-AB-11-20200909-ErfanGSI.img-0125.7z) as well as H-VENDOR_V1.0.zip to the mobile phone via a USB cable plugged to my PC in the root of the phone in order to proceed to its installation.
I then used Odin to flash Orange Fox (also TWRP on other attempts) with AP, but when I get to the Orange Fox recovery screen, the .zip files do not appear in the files. When searching on the Internet, it is advisable to flash via Fastboot, but despite several attempts, I cannot detect the phone with Fastboot, but only ADB. Even the manipulation saying to install the drivers manually from the device manager doesn't work because a message saying that the file to be used doesn't contain a driver is displayed. (android_winusb.inf)
And I also notice that after having flash TWRP or Orange Fox, the phone can no longer boot on the system.
Have you got any advices?
I continued my tests on my side, I was able to better understand how TWRP and Orange Fox work, in fact to make it usable, you first have to FORMAT the /data (not swipe), so, make TWRP / Orange Fox operational.
I was then blocked during the installation of the personalized ROM with the error of the /vendor, following my research, it would be necessary to install a .zip dedicated to that (Mokee from what I saw)
But I did something I shouldn't have done, and I flashed the zip "twrp-3.2.1-0-20180414-codeworkx-dumpling" from the Orange Fox recovery, and since then, the phone is stuck at startup, and when I try to access Download Mode, I get stuck at the Warning Message because my volume buttons don't react.
Is it possible to do something about it or the phone will be forever bricked?
up