My device is rooted, S-off, debloated 4.3 senseless. I have spent days trying to push a new boot and up animation to said device with no luck. and now I am turning to the crew here in an effort to solve this since I am missing something obvious. RW permissions have been changed for system, customize, resource. What am I missing?
Really, no thoughts, or flashes of brilliance? I'm still stumped!
Related
Wondering if any of you guys could help me out here?
By the way, if this is the wrong section for this, apologies and feel free to move?
Nexus 7, 16gb, rooted with stock 4.1.2. I have not edited the build.prop, still using the 4.1.2 Keyboard, Gmail etc.
So, nothing changed other than unlocked/rooted.
I have superSU pro and have 'Survival Mode' enabled, which is basically and OTA Rootkeeper (I am sure you already know this...)
When we got the OTA to 4.1.2, it worked no problem, survival mode worked and I kept root and custom recovery.
So this morning I get a notification to upgrade to 4.2, which I done. It restarted, and installed with no errors etc, then comes the Google screen with the unlocked padlock... and it stayed this way for an hour, so I am assuming it is borked?
I restarted it, same again, so rebooted into the bootlaoder menu. Going into recovery shows the android dude on his back, red triangle ! etc, so I gather my custom recovery is gone.
So the question is, where to go from here, and is there a walkthrough I can use to resuce this (I am techy enough minded, but given the state it is in, loathed to make it worse down to sheer stupidity)?
Any help would be much appreciated guys.
BTW - I used Wugs Toolkit to root, so that is all set up with drivers etc, can that be used now to recover?
No ideas?
Good morning droids,
I was looking around for info on the "phone storage encryption" option which requires a PIN when the phone is first powered on. This sounds nice conseridering the amount of information contained on our devices these days.
I think this is a stock HTC feature but I wasn't finding much in other forums. I'm currently running viper rom which has me wondering a few things:
Where in the boot process does it prompt for decrypt? Would you still be able to mount images from storage-- like does it prompt before the bootloader starts? would you still be able to use/nandroid/mount roms in a custom bootloader? Are there any recovery options? if it all goes to hell would I still beable to flash back to stock? Can encryption be undone after? My main concern has to do with when in the boot the storage is decrypted and how it affects the use/flashing of roms.
With all these questions I think the resounding common sense answer is "its just not worth the potential fallout." but I'll ask anyway...
Thoughts?
CarbolDroid said:
Good morning droids,
I was looking around for info on the "phone storage encryption" option which requires a PIN when the phone is first powered on. This sounds nice conseridering the amount of information contained on our devices these days.
I think this is a stock HTC feature but I wasn't finding much in other forums. I'm currently running viper rom which has me wondering a few things:
Where in the boot process does it prompt for decrypt? Would you still be able to mount images from storage-- like does it prompt before the bootloader starts? would you still be able to use/nandroid/mount roms in a custom bootloader? Are there any recovery options? if it all goes to hell would I still beable to flash back to stock? Can encryption be undone after? My main concern has to do with when in the boot the storage is decrypted and how it affects the use/flashing of roms.
With all these questions I think the resounding common sense answer is "its just not worth the potential fallout." but I'll ask anyway...
Thoughts?
Click to expand...
Click to collapse
I don't believe that recoveries are able to update a phone with an encrypted data partition unless you're using stock. I do believe you can flash back to stock if something goes wrong, although you would certainly have to format /data to get back into it. However, the actual login process (if I remember correctly, it's been a while) is that the bootloader starts you in a "dummy" environment of sorts that just asks you for your password. If it checks out, the system reboots, passing that key on to the "real" operating system which decrypts the data volume.
I'd echo though that it's really not something you should fool around with.
I have googled this but all the solution I find are either to factory reset or re-flash your firmware. I'd really like to avoid that.
I have a Z3 compact, rooted and then flashed with the latest firmware I think its the .77 at the end.
Xposed framework with a few mods running beautifully on it.
The last 3 changes I did before the phone got stuck in the boot loop:
- updated minmin xposed module from 1.8.1 to 1.9
- updated another module but forgot its name
- fiddled with the settings of this app: https://play.google.com/store/apps/details?id=org.namelessrom.devicecontrol
I'm pretty sure its the latter as it sets certain kernel parameters at reboot.
Can anyone give me instructions on how to disable this app from booting or how/where to find it and delete it?
Where can I find logs of this boot loop?
I really want to avoid re-flashing, re-rooting, re-flashing and restoring my backup again as that will take half a day.
I've just brought back mine from bootlooping after I've installed several extensions (just discovered that the culprit was DonkeyGuard) and I'm about to do it for the second time, by flashing a Xposed-Disabler-Recovery.zip file that's stored either in the root of your phone or at
/storage/emulated/0/Android/data/de.robv.android.xposed.installer/files/Xposed-Disabler-Recovery.zip
But that would only work in case you messed it up with Xposed.
Thanks, I'll keep that in mind if I encounter this problem again.
Still finding it hard to believe there's no other reply to a seemingly common problem / question, does everyone just pack up and factory reset when boot looping?
Well, it's as common as people repeating to make a nandroid backup, you know
Btw, before I will flash yesterday a black theme (modded system files), I made the backup, so when my Z3C got stuck in a bootloop for the third time, I had nandroid ready. Such a shame, I really liked that mod.
If the kernel is problem, how about just reflashing your kernel?
Believe it or not, I started looking into nandroid backups today already made my first tests.
Until now I relied on titanium backups but that still makes me do a factory restore before I can restore stuff from those backups.
But the issue is, I am not looking for better "protection" I'm trying to find out how I can fix something minor like this i.e. via adb and command line...
Talking about a custom kernel, is there one? I have a rooted xperia z3 compact and wouldn't mind checking out a different kernel but I held back unlocking my bootloader until there is a custom ROM available that can fully replace my rooted stock ROM.
If love to get PAC man ROM for my phone.
I had the same issue, but by using 3C toolbox (similar to the app you've mentioned).
In my case putting back the original build.prop into /system via ADB fixed the bootloop.
As for custom kernel, you can try AndroPlus kernel HERE
@ovizii as @davebugyi said, you could always put some files back via ADB, but you need to have a file that you want to put back, like in davebugyi's case an original file. In your case you don't have it, so unless you know what value you changed, there is nothing much that you could really do with ADB access.
-V-O-Y-A-G-E-R- said:
@ovizii as @davebugyi said, you could always put some files back via ADB, but you need to have a file that you want to put back, like in davebugyi's case an original file. In your case you don't have it, so unless you know what value you changed, there is nothing much that you could really do with ADB access.
Click to expand...
Click to collapse
Hm, I was thinking along the lines of accessing log files, like a system log file, check what went wrong, i.e. auto start of a certain app, or setting of kernel parameters at boot time, then remove the offending apps/entries?
Just not sure if that's possible, hence this question here
Checking out the suggested ap and the kernel! Thanks!
So, today I upgraded to 6.0 and had a hell of a time (took me 7 hours) and the problem was that when I installed su from twrp it'd soft brick my phone, anyway, that's not the problem, the problem is everything is saving to /storage/emulated and I can't access it without root. I noticed this when I was on OGInsta and I wanted to download a picture, it gave me an error code about how it couldn't find the directory, so I went to my file manager, everything was fine but I accidentally hit up instead of home and it brought me to an empty page. I started messing with the settings of my file manager assuming something went wrong with it, new version etc, and I found it had a root option. I clicked it and gave it root access and went back and I could see the files where I was previously. To make sure I tried to save something on kik, didn't work. I tried accessing my storage from the rar app and it wouldn't. I don't know what's going on or how it even got this way.
How did you install 6.0, what version of su did you install, and how did you fix the soft brick?
Sounds like you have very little idea what your doing and running a ton of random stuff. Probably best to do a system restore, take a step back learn what your doing and do it again properly... but if you can recount the steps you have done it may be fixable.
I like to think I have decent knowledge on what I am doing, I've been rooting phone's and made xposed apps (for myself) since kitkat. I've never had so much trouble with something. And to answer your questions, I figured using nexus root toolkit would he fine, as it always has worked before but I couldn't get it to root my phone. It would soft Brick it for an unknown reason, I left it on for about an hour at one point to make sure it was bootlooping. So then I used adb, flashed boot.img and then recovery. Went into recover and flashed SU 2.52 beta. (this is also how I solved the soft Brick the nexus toolkit was giving me)
scryan said:
How did you install 6.0, what version of su did you install, and how did you fix the soft brick?
Sounds like you have very little idea what your doing and running a ton of random stuff. Probably best to do a system restore, take a step back learn what your doing and do it again properly... but if you can recount the steps you have done it may be fixable.
Click to expand...
Click to collapse
Also, to clearly, I have 2 storage paths. One is "sdcard/" and the other is "storage/emulated/0" I'm not sure if the "storage" folder is new in 6.0, I know 4.+ and 5.+ used "sdcard/". Too see "storage/emulated/0" I need to grant root access to the file manager. And any app the does not have root, cannot access that directory.
YoureVexing said:
I like to think I have decent knowledge on what I am doing, I've been rooting phone's and made xposed apps (for myself) since kitkat. I've never had so much trouble with something. And to answer your questions, I figured using nexus root toolkit would he fine, as it always has worked before but I couldn't get it to root my phone. It would soft Brick it for an unknown reason, I left it on for about an hour at one point to make sure it was bootlooping. So then I used adb, flashed boot.img and then recovery. Went into recover and flashed SU 2.52 beta. (this is also how I solved the soft Brick the nexus toolkit was giving me)
Click to expand...
Click to collapse
you might have knowledge in making apps, but you are missing lots of knowledge when modding your phone. you are going to have to use an app like root explorer, and find where your storage was placed, then move it to the right location. or you can reflash the factory image. ive always just moved my storage back when its happened to me. anyways, flash the factory image the right way, not through a toolkit. then flash any custom kernel(if flashing marshmallow), and supersu.
YoureVexing said:
I like to think I have decent knowledge on what I am doing, I've been rooting phone's and made xposed apps (for myself) since kitkat.
Click to expand...
Click to collapse
Why are comments like this always made by people who take 7 hours to flash a factory image, and make statements like
YoureVexing said:
So then I used adb, flashed boot.img and then recovery.
Click to expand...
Click to collapse
ADB cannot flash factory images.
I didn't need your resume... Just answers to the questions I asked....
Do as simms said and flash factory image with fastboot to fix whatever you did, then a kernel and the lastest supersu.
The emulated storage folder has been there at least since kit kat. My S4 and Moto X, neither of which saw LP both had it.
scryan said:
Why are comments like this always made by people who take 7 hours to flash a factory image, and make statements like
ADB cannot flash factory images.
I didn't need your resume... Just answers to the questions I asked....
Do as simms said and flash factory image with fastboot to fix whatever you did, then a kernel and the lastest supersu.
The emulated storage folder has been there at least since kit kat. My S4 and Moto X, neither of which saw LP both had it.
Click to expand...
Click to collapse
It took me 7 hours because I could figure out what was wrong with it and why twrp kept soft bricking my device. And I'm not worried about emulated. I know that has been there. I'm saying there is 2 folders, /sdcard and /storage. Every app is trying to use the path "/storage/emulated/0/*insert app folder here" and it cannot do that without root. I'm confused as too why all the apps are trying to do that for a default location instead of /sdcard. I've already tried to reflash everything. I even looked up like 5 tutorials to make sure I was doing it right and I was.
Can't really help you with your current situation (other than to advise you to flash a factory image and start over), but if it confirms your sanity the exact same thing happened to me using the rootkit to root my Nexus 6. I should've known better than to use rootkit, but I'm not really used to fastboot having been on Samsung devices and using Odin for everything. I corrected it by flashing a factory image, flashing the modified boot image, flashing TWRP, and then SuperSU. But the whole process was quite a fiasco from what I'm used to and for what I expected from a Nexus phone.
YoureVexing said:
It took me 7 hours because I could figure out what was wrong with it and why twrp kept soft bricking my device. And I'm not worried about emulated. I know that has been there. I'm saying there is 2 folders, /sdcard and /storage. Every app is trying to use the path "/storage/emulated/0/*insert app folder here" and it cannot do that without root. I'm confused as too why all the apps are trying to do that for a default location instead of /sdcard. I've already tried to reflash everything. I even looked up like 5 tutorials to make sure I was doing it right and I was.
Click to expand...
Click to collapse
/sdcard is a simlink, its the same folder.
internetpilot said:
Can't really help you with your current situation (other than to advise you to flash a factory image and start over), but if it confirms your sanity the exact same thing happened to me using the rootkit to root my Nexus 6. I should've known better than to use rootkit, but I'm not really used to fastboot having been on Samsung devices and using Odin for everything. I corrected it by flashing a factory image, flashing the modified boot image, flashing TWRP, and then SuperSU. But the whole process was quite a fiasco from what I'm used to and for what I expected from a Nexus phone.
Click to expand...
Click to collapse
The rootkit wasn't working for me, it's been a charm for my nexus 5 and from 4.+ and nexus 6 on 5.+, on 6.0 it wasn't working so I tried to flash it on fastboot and I still got the same thing. I'll try it once more I suppose, thank you.
Hello all. I Recently attempted rooting my phone, running on 5.0.2, and it seemed to have worked. But then after attempting to use SuperSU to add root permissions to an app, my screen went black, and the only thing visible was the top status bar, which had some animations still running (Like the battery icon filling up or the signal bars changing), but thats it. It wasn't responsive to any of my button presses, and then it shut off. It keeps doing this over and over, and i cant keep the phone on for more than 5 mins maybe 10. How would I fix this? I used this "tutorial". - andromods .com/news-root/lg-g3-g-flex-2-g2-lollipop-one-click.html - (Stupid thing wont let me post links)
I would like to solve this without factory resetting, as I have apps that have data on them that needs to be transferred from one phone to another, and i dont have a second phone to transfer to at the moment.
Thanks in advance.
As far as I know, flashing kdz with LG Flash Tool following the tutorial to "unroot" won't delete your data, but you will lose root, of course. If you don't have custom recovery nor root, there is little else you can do. Do you have adb root (shell)? If yes you can try re-flashing system partition...
lfom said:
As far as I know, flashing kdz with LG Flash Tool following the tutorial to "unroot" won't delete your data, but you will lose root, of course. If you don't have custom recovery nor root, there is little else you can do. Do you have adb root (shell)? If yes you can try re-flashing system partition...
Click to expand...
Click to collapse
I'm very new to this, and probably shouldnt have attempted this without knowing more, so I have no idea what you are asking me. What is ADB root (shell)? I probably dont have it. And I didnt do any sort of custom recovery. But it seems that me messing around with SuperSU (clicking the uninstall root/turning of superuser once or twice) seems to have stopped the crashing all together. Ive been using my phone since and it hasnt crashed. Whether or not that's fixed the real issue, I don't know. And I'm not sure I want to mess with it further. :crying: