Prior Info: Phone is rooted with magisk and bootloader is unlocked. Stock Pie Rom with pixelify Magisk Module and a couple of other modules installed.
Have been using AdAway for some time. Disabled it recently to watch some ads for games. Today switched it back on again. Clicked on Reboot after the prompt, and since then it is stuck in boot 'Android one' animation screen. It has been a few hours.
Is there any way i can get it working without loss of data? Tried booting into recovery (no TWRP, stock recovery only), there was no option to wipe cache, only factory reset.
Please help.
(ps. the phone memory was almost full, don't know if that info helps.)
Thank you all in advance.
Related
Hi folks,
I recently rooted by N4. It was running Android 5.0.
I also have MultiROM installed, with CyanogenMod installed as a secondary ROM.
I didn't realise I couldn't apply the OTA updates to the stock Android system (my oversight), and I allowed the device to download and (attempt an) the recent 5.0.1 update from Google.
When the update attempted to reboot the device, I could see in the terminal data that popped up, that it failed.
After that device now gets stuck in the booting stage with the little coloured balls drifting around.
I continued to use my phone with the secondary ROM (Cyanogen) for some days until I had time to sort this out.
MY ATTEMPTED RECOVERY
I read that ordinarily on a rooted device one would manually apply the various image files from the full 5.0.1 package.
So, following instructions found here: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Using method two (long method).
... In fastboot mode I flashed the system, boot, recovery, cache (after clearing cache), radio images from the 5.0.1 stock image.
At first I didn't flash the bootloader (as I wanted to maintain the multiboot loader I had installed) nor the user.img (I don't want to lose my user data). I read this should work. But it didn't.
When it came to booting into recovery mode to finish the process, an android icon with a ! warning on it would appear, and I could not do the recovery.
So, I have since flashed the bootloader also. That didn't change much, except that my dual-boot boot loader is now gone, and the device is still not recoverable.
Is there something I am not doing correctly? How can I recover this device so that it has 5.0.1, my existing user data, and my existing dual boot bootloader?
Cheers,...
May have solved it...
I'll post another update in a moment. Posting this just in case someone starts responding to my question in the interim.
After further fiddling around, I may have resolved this issue. I've managed to get it into recovery menu, rebooted from there, and device is now in "Android is updating" mode. Looking good.
Will post new message soon as to whether this was successful or not.
Issues continue
So, after the device booted a screen appeared for a fraction of a second, that appeared to be the screen for selecting system language (as per what happens when a device is first run after a clean install). But the screen almost instantly goes black except for the little network icon and battery icon and time in the top right of the screen.
If I use the power button to lock the screen and again to activate it, the screen very briefly flashed up the language selector, then goes blank again.
So... it seems something odd is happening after applying the 5.0.1 file.
Any suggestions?
Flash the 5.0.1 factory image with fastboot
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Flash the 5.0.1 factory image with fastboot
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Well, this is what I resorted to doing. And it worked. Phone started and was as new. Of course, I lost my user data which is a ****. I did pull the SDCARD content over ADB, but am not sure how I'd go about pushing it all back on, into right locations, etc.
BUT—and it's a BIG BUT—when I re-rooted it and applied SuperSu, it couldn't be put into recovery mode any more. It would keep running through the SuperSu install process each time I'd attempt to go into Recovery.
I ended up ignoring this, and installing Busybox (with Play) and SuperSu.apk (via Play). But the SuperSU apk would keep saying its files needed to be installed/updated.
I forget the exact mess that unfolded, but eventually (after installing MultiROM) I could boot the phone as it would ALWAYS go into (custom) recovery.
So I starter the whole process again, with another clean install of 5.0.1, and yet now it is stuck at the bootloader (the little swirling balls screen).
AndroidWelcome said:
Well, this is what I resorted to doing. And it worked. Phone started and was as new. Of course, I lost my user data which is a ****. I did pull the SDCARD content over ADB, but am not sure how I'd go about pushing it all back on, into right locations, etc.
BUT—and it's a BIG BUT—when I re-rooted it and applied SuperSu, it couldn't be put into recovery mode any more. It would keep running through the SuperSu install process each time I'd attempt to go into Recovery.
I ended up ignoring this, and installing Busybox (with Play) and SuperSu.apk (via Play). But the SuperSU apk would keep saying its files needed to be installed/updated.
I forget the exact mess that unfolded, but eventually (after installing MultiROM) I could boot the phone as it would ALWAYS go into (custom) recovery.
So I starter the whole process again, with another clean install of 5.0.1, and yet now it is stuck at the bootloader (the little swirling balls screen).
Click to expand...
Click to collapse
Try a full wipe from Factory Recovery, and see if it will fix the bootloop.
Bootloop no more...
ariesgodofwar said:
Try a full wipe from Factory Recovery, and see if it will fix the bootloop.
Click to expand...
Click to collapse
(wiping the sweat from his brow...)
After many tedious hours of messing around with this beast... there is life beyond the bootloop.
Back to a stock install.
So, now I am wondering why the SuperSu/Root process didn't work on my last round on this.
The SuperSu installer would kick in EVERY time I went into Recovery mode, and would then reboot the phone. This made it impossible to do things with ADP because I essentially couldn't get into recovery mode. I wanted to push through some of the stuff I pulled using ADP before I wiped the phone previously.
I installed MultiROM (which includes TWRP [is that what it's called] recovery system. BUT then go stuck in a Recovery loop.
Not wishing to repeat that fiasco... does anyone more knowledgeable than I (not a difficult status to achieve) have any suggestions to what might have caused those issues?
My device is (or: was) running Google Lollipop, but with added root access. Tonight su told me that it needs an update, so it rebooted to TWRP, installed something, rebooted again, trying to load the OS, but got stuck in the boot animation. Now the only way to switch it off is via the boot loader.
Is there a way to regain control over the device, or should I just flash some custom Marshmallow instead? I already wiped the cache partitions, but with no avail. And I am not really satisfied with Lollipop, because very often it's acting like paralysed.
self comment: solution
I went to the SuperSU thread in this forum and found out that I am not the only one with this problem. A solution was to boot to TWRP, enter the ReadyToSomething folder and (re-)install some old version 2.46 of SuperSU which I found there.
System is running normal again, but SuperSU is constantly begging for a "binary update".
I had Magisk 16.0, but Magisk Hide didn't work very well. I wanted to see if it would work with Magisk 14. Not it's stuck in a boot loop. It shows the "Samsung Galaxy S8 powered by android" for a few seconds then reboots. I can still boot into TWRP recovery and access the storage. Download mode works too. I tried uninstalling Magisk and flashing the stock boot image. Neither worked. Is there anhthing I can do to make my phone work again without losing my data?
Update: if I have to flash the stock ROM, I'm planning to do the next thing: back up my data partition to an external hard drive with TWRP. After I flash the ROM and wipe everything, I want to reinstall TWRP and restore that backup. Would this cause any issues?
vladone97 said:
I had Magisk 16.0, but Magisk Hide didn't work very well. I wanted to see if it would work with Magisk 14. Not it's stuck in a boot loop. It shows the "Samsung Galaxy S8 powered by android" for a few seconds then reboots. I can still boot into TWRP recovery and access the storage. Download mode works too. I tried uninstalling Magisk and flashing the stock boot image. Neither worked. Is there anhthing I can do to make my phone work again without losing my data?
Click to expand...
Click to collapse
I think you cant, since your phone is bootlooped there is no way to get your data back ..
You should backup your data even before root your phone ..
Just flash latest TWRP img.tar from odin, disable auto reboot from the options on odin , after the success flash you need to press the buttons to enter recovery mode .
https://android.gadgethacks.com/how...-s8-into-recovery-mode-download-mode-0177223/
StonebridgeGr said:
I think you cant, since your phone is bootlooped there is no way to get your data back ..
You should backup your data even before root your phone ..
Just flash latest TWRP img.tar from odin, disable auto reboot from the options on odin , after the success flash you need to press the buttons to enter recovery mode .
https://android.gadgethacks.com/how...-s8-into-recovery-mode-download-mode-0177223/
Click to expand...
Click to collapse
I already have TWRP.
I am having issues installing the xposed framework. I have rooted with Magisk successfully and I'm on the ElementalX kernel. When I try to install the xposed framework via TWRP, when I reboot back into the OS, it gets stuck in a hello moto bootloop. I can boot into the OS without issue by clearing the dalvik cache and the normal cache after installation, but when I get into the Xposed installer app, it says it's installed but not running. There is no log, so I assume it is because the Xposed folder doesn't have permissions. I give it permissions and reboot by pressing restart in the power menu, but when I do that, it gets in the bootloop again.
I would appreciate any help on this.
MineMasterHD said:
I am having issues installing the xposed framework. I have rooted with Magisk successfully and I'm on the ElementalX kernel. When I try to install the xposed framework via TWRP, when I reboot back into the OS, it gets stuck in a hello moto bootloop. I can boot into the OS without issue by clearing the dalvik cache and the normal cache after installation, but when I get into the Xposed installer app, it says it's installed but not running. There is no log, so I assume it is because the Xposed folder doesn't have permissions. I give it permissions and reboot by pressing restart in the power menu, but when I do that, it gets in the bootloop again.
I would appreciate any help on this.
Click to expand...
Click to collapse
I had this problem also, I would typically just long press the power button and let it complete a second normal boot, and then xposed would work after the second boot completed. (The second boot after initial bootloop would load up just fine.) However, after a few reboots, my phone became unstable and I had to reflash the stock ROM. I'm not sure how stable OREO xposed is on this device yet. It may have just been my modules. (GravityBox, Flat Color Keyboard, Bars, and Status Icons)
Drkmatr1984 said:
I had this problem also, I would typically just long press the power button and let it complete a second normal boot, and then xposed would work after the second boot completed. (The second boot after initial bootloop would load up just fine.) However, after a few reboots, my phone became unstable and I had to reflash the stock ROM. I'm not sure how stable OREO xposed is on this device yet. It may have just been my modules. (GravityBox, Flat Color Keyboard, Bars, and Status Icons)
Click to expand...
Click to collapse
I also have a Moto G5 plus and when I tried to reboot it a second time it was still stuck in its boot loop so I had to enter TWRP to flash the uninstall and if I try to install Xposed via Magisk I have to factory reset, I don't think it's me ROM because it's the same as a stock ROM (had to install the ROM because the one it came with got corrupted or something when I tried to install Xposed where I still had the boot loop problem). I am running 8.1.0 Oreo.
I think a lot of my problem was i was using a sprint variant also. I think a lot of other users are using the verizon/t-mobile variants. I never really did get xposed to work properly on oreo on the sprint variant of this phone no matter what i tried.
Any news on this issue?
I just updated to 8.1 and would like to get xposed up and running like I had it on Nougat. Has there been any fixes yet to this. Thanks to anyone for a reply.
I get bootloop when I install magisk & xposed.
I am using Xposed since months
Working fine
One thing you is that we've to do soft reboot instead of regular reboot
A little background first, I have had my galaxy (sm-g975F exynos) rooted for some time now with magisk. I wanted to update the firmware, reroot and install TWRP in the process. Took me a few hours and only one mistake but at the end I was successful. This was 2 days ago and Ive been working on customizing ever since.
Now onto the problem, I noticed the camera app didn't work any more when I boot into magisk mode. When I boot in standard mode the camera works fine. I tried force quitting, rebooting, reverting to original settings, etc... and no change. I started reinstalling system apps I removed with debloat thinking I may have removed a system app that had an effect but again no change. I read somewhere that clearing/wiping cache may help so I booted into TWRP, went into advanced wipe and only wiped "cache". Now when I reboot into standard mode the phone works fine, but if I boot into magisk mode I cant get past the lock screen. Basically magisk mode boots fine but when I enter my pin it just goes back to lock screen. So I rebooted into standard mode and made it so there was no lock screen(no pin, no fingerprints, etc...) then I tried rebooting in magisk mode to see if this will get me past the lock screen and now it just bootloops in magisk mode only.
So my first problem is getting my phone back into magisk mode, my second problem is the camera. is there a safe way to reflash with TWRP or am I going to have to redo the whole process with odin?
Thank you in advance for any help, I have searched online but haven't found anyone that has had issues wiping cache with TWRP
update, tried downloading magisk zip from magisk manager, rebooted into TWRP and tried installing the zip, no change. wiped dalvik cache for kicks, no change.
update #2, also tried uninstalling or disabling root privilege apps such as novalauncher, liveboot and buttonmapper but I was only able to do this in non-magisk mode, again no change.
Update #... what # am I on?
So I started fresh, reinstalled stock firmware, reinstalled magisk and reinstalled TWRP. Phone is working fine except for the fact the camera doesnt work in magisk mode. I am now 100% positive this is due to magisk or TWRP. I will try and install another camera app to see if it works, but would still like to figure out how to get samsungs camera app to work in magisk mode.
So I decided to enter into safe mode which ultimately broke my magisk install. Same scenario as before, I can boot into non-magisk mode now but if I try and boot into magisk mode I cant get past lock screen. However while in safe mode and now non-magisk mode, the camera actually does work. So as it stands I can either have my phone rooted and not be able to use the camera or not have it rooted and be able to use the camera. If anyone has any suggested work arounds, please feel free to chime in. In the mean time I will start over again.
another update.
I reflashed stock firmware along with magisk. I now have root as well as a working camera, and yes the camera works in magisk mode and non-magisk mode. I am now looking to blame TWRP or multidisabler in breaking the camera. I know that having TWRP on a galaxy S10+ is fairly new to the market but I am surprised that I cannot find a single other report of someone elses camera not working after installing TWRP. I feel like I should keep trying things but I also have reflashed firmware, magisk, TWRP 3 times in the past 5 days and I just want a working phone with root. The only other ideas I had was to either give the camera root access or make the camera a system app. I dont see why I would/should need to do that though.
Moderator can you please change the title of this thread to "Camera not working after installing TWRP" please and thank you if it is possible.