Related
Guys, its my first time to try to do some modding on Android and unfortunately Im stuck with a problem.
I did a good install with drivers, unlocked it successfully then installed TWRP 2.5 mako. after installing TWRP, I locked my phone again. Then I went to TWRP recovery then made a backup. After backup was complete, I was to reboot but was prompted something like "my device seemed not to be rooted. Do you like to install SU?" But I choose "dot not install" instead. Then it rebooted. Then the Google logo showed up longer than usual, then the X logo and was stuck on it from there. I waited till morning thinkin the phone might be configuring itself for the first time after all the things I have done but to my surprise, when I got up this morning, still on the X logo! I then tried to reset by pressing the power button for some seconds. It rebooted but same thing happens, google logo showed up for a longer time than usual then stuck again on the X logo. Then I tried fastboot, it did went to fastboot. Tried to reset bootloader, tried using TWRP reset system and reboot but still no success.
What do you think happenede and what did I do wrong? What should I do now to fix this.
Im really nervous now thinking I might have bricked my phone. Im a newbie so I really have no idea..
Hope you guys could help. Thanks!
Try clearing cache in twrp if that doesn't work flash the stock recovery and clear cache from there.
Sent from my Xoom using Tapatalk 4 Beta
El Daddy said:
Try clearing cache in twrp if that doesn't work flash the stock recovery and clear cache from there.
Sent from my Xoom using Tapatalk 4 Beta
Click to expand...
Click to collapse
thanks for the reply. You mean using "Wipe" in twrp right? After choosing wipe, i was prompted with 2 button options and a swipe option. 1 button was "advance wipe", the other was "format data" and the swipe option was "swipe to factory reset" what should I use? It says "factory reset wipes data, cache and dalvik (not including internal storage). Most of the time this is the only wipe that you need." You mentioned to try to clear cache, do you mean to say the data and dalvic as well? If so then should I choose the swip option which is "factory reset"?
Thanks again..
Nope just the cache. This phone sometimes has issues when wiping data/cache from the bootloader. (Which is what happens when you unlock the bootloader) The way to fix the bootloop problem is to wipe cache using the stock recovery.
Sent from my Nexus 4 using Tapatalk 4 Beta
vinz_bangiz said:
thanks for the reply. You mean using "Wipe" in twrp right? After choosing wipe, i was prompted with 2 button options and a swipe option. 1 button was "advance wipe", the other was "format data" and the swipe option was "swipe to factory reset" what should I use? It says "factory reset wipes data, cache and dalvik (not including internal storage). Most of the time this is the only wipe that you need." You mentioned to try to clear cache, do you mean to say the data and dalvic as well? If so then should I choose the swip option which is "factory reset"?
Thanks again..
Click to expand...
Click to collapse
Try factory reset first if that doesn't work you may have to sideload a ROM onto it. The same thing happened to me a couple of times. Sometimes a factory reset worked but most of the time I ended up sideloading.
El Daddy said:
Nope just the cache. This phone sometimes has issues when wiping data/cache from the bootloader. (Which is what happens when you unlock the bootloader) The way to fix the bootloop problem is to wipe cache using the stock recovery.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
so just to clear, i would not try anymore to clear cache via twrp or should i try it first before flashing stock recovery and clearing it from there? To be honest, im quite careful now in every move ill make coz Im afraid i might make matters worst.
Pls advice. thanks for your patience.
by the way, in case I would really need to flash stock rom, how to do it and where to get right stock recovery?
Thanks again!
All the info to flash recovery and resources are here: http://forum.xda-developers.com/showthread.php?t=2010312
Basically, download the stock image. Extract the folder down til you see the recovery.img.
Then using fastboot type the command:
fastboot flash recovery recovery.img
Then boot into recovery and clear cache.
Sent from my Nexus 4 using Tapatalk 4 Beta
El Daddy said:
All the info to flash recovery and resources are here: http://forum.xda-developers.com/showthread.php?t=2010312
Basically, download the stock image. Extract the folder down til you see the recovery.img.
Then using fastboot type the command:
fastboot flash recovery recovery.img
Then boot into recovery and clear cache.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
oh ok. I understand now. Sorry, its my first time so im not that familiar yet on how things go. I did a lot of reading and browsing as well but xda sure is very overwhelming in information..
P41ll37 is suggesting sideload which I also am not yet familiar with. i tried to search it but most of it led to using a toolkit. I mentioned in another post that I made that I wanted to learn instead of jsut being able to fix my problems. Could you advice me as well or lead me to the right link to know how to do this.
Thanks!
Guys! before trying anything else, I tried to clear cache using TWRP and choosing advance then marked the delvic cache and cache then restarted system, was asked if I wanted to installed SU, this time I choose yes, it rebooted by itself, but still nothing happened. same stuck on X logo problem.
But then, I tried wipe again in TWRP this time choosing factory reset, then restarted system again, google logo did stay a longer but not as long as before, then X logo appeared and stayed there like forever but after a minute or so.. FINALLY! it went to the Welcome screen asking for what language I should use.
So i guess this means it is fixed already?
Also, since I choose to install SU a while ago, does this mean my phone is already rooted as well? How would I know? Well, maybe installing a root app like titanium backup should tell right?
If so, then looks like I have advanced already on my step by step learning to mod my phone. I was only in the unlocking and custom recovery part last night. Tonight was supposed to be rooting and putting custom rom but I was still trying to learn thru our forum guides.
I wana thank you guys for your time, kind help and suggestions. This was my first experience in modding and right away I was faced with a problem to be solved. This is good anyway as a learning experience.
One last thing, could you guys tell what really happend, how I went into this kind of problem or what caused it? As I mentioned, I was noping not only to mod or fix my phone but rather really learn on how to do or fix things. Like a difference between a toolkit and manually doing it. Right?
Thanks again guys!
vinz_bangiz said:
Guys! before trying anything else, I tried to clear cache using TWRP and choosing advance then marked the delvic cache and cache then restarted system, was asked if I wanted to installed SU, this time I choose yes, it rebooted by itself, but still nothing happened. same stuck on X logo problem.
But then, I tried wipe again in TWRP this time choosing factory reset, then restarted system again, google logo did stay a longer but not as long as before, then X logo appeared and stayed there like forever but after a minute or so.. FINALLY! it went to the Welcome screen asking for what language I should use.
So i guess this means it is fixed already?
Also, since I choose to install SU a while ago, does this mean my phone is already rooted as well? How would I know? Well, maybe installing a root app like titanium backup should tell right?
If so, then looks like I have advanced already on my step by step learning to mod my phone. I was only in the unlocking and custom recovery part last night. Tonight was supposed to be rooting and putting custom rom but I was still trying to learn thru our forum guides.
I wana thank you guys for your time, kind help and suggestions. This was my first experience in modding and right away I was faced with a problem to be solved. This is good anyway as a learning experience.
One last thing, could you guys tell what really happend, how I went into this kind of problem or what caused it? As I mentioned, I was noping not only to mod or fix my phone but rather really learn on how to do or fix things. Like a difference between a toolkit and manually doing it. Right?
Thanks again guys!
Click to expand...
Click to collapse
basically whenever you flash a factory image (and perhaps even some custom ROMS) you have to do a factory reset for really two reasons. The first reason is to get it out of bootloop. For some reason whenever the phone is flashed it will go on endless loop until you boot into recovery and factory reset. Also, you will need to check your storage after you flash. The phone has a tendency to lose half its memory after a flash. Check storage and if at half memory do another factory wipe and you should be good to go.
The easiest way I do it is to simply reboot the phone after flashing the files, I then allow the phone to reboot and get stuck on the bootloop. I then hard shut the phone off by holding down power. Once shut down boot into fastboot and then fastboot boot TWRP recovery where I then wipe the phone. After it reboots it will stick on the X logo for a few minutes and get to the welcome screen. From there log in and get it set up again.
Also, this is where you should check storage. I notice that more often than not mine still is only half storage (despite my TWRP wipe), so I use the phone to factory reset and then when it reboots the phone has full storage again.
Im sure there is probably someone out there with a better system but that is how I do it.
thos25 said:
basically whenever you flash a factory image (and perhaps even some custom ROMS) you have to do a factory reset for really two reasons. The first reason is to get it out of bootloop. For some reason whenever the phone is flashed it will go on endless loop until you boot into recovery and factory reset. Also, you will need to check your storage after you flash. The phone has a tendency to lose half its memory after a flash. Check storage and if at half memory do another factory wipe and you should be good to go.
The easiest way I do it is to simply reboot the phone after flashing the files, I then allow the phone to reboot and get stuck on the bootloop. I then hard shut the phone off by holding down power. Once shut down boot into fastboot and then fastboot boot TWRP recovery where I then wipe the phone. After it reboots it will stick on the X logo for a few minutes and get to the welcome screen. From there log in and get it set up again.
Also, this is where you should check storage. I notice that more often than not mine still is only half storage (despite my TWRP wipe), so I use the phone to factory reset and then when it reboots the phone has full storage again.
Im sure there is probably someone out there with a better system but that is how I do it.
Click to expand...
Click to collapse
Thanks for the reply. really very informative!
The easiest way I do it is to simply reboot the phone after flashing the files, I then allow the phone to reboot and get stuck on the bootloop. I then hard shut the phone off by holding down power. Once shut down boot into fastboot and then fastboot boot TWRP recovery where I then wipe the phone. After it reboots it will stick on the X logo for a few minutes and get to the welcome screen. From there log in and get it set up again.
Click to expand...
Click to collapse
Actually, this is exactly what I did and the one that solved my problem.
Also, this is where you should check storage. I notice that more often than not mine still is only half storage (despite my TWRP wipe), so I use the phone to factory reset and then when it reboots the phone has full storage again.
Click to expand...
Click to collapse
About this, are you referring to the remaining free storage or that actual usable storage of the phone. To my knowledge, a new 16gb nex4 would actually give you about 12+gb of free usuable space. Do you mean I should observe if this has dropped to about 6gb? or are you reffering to for example I have 5gb remaining free space before flashing and rebooting then after this I should observe if the "remaining free" space is now only around 2.5gb after rebooting it?
Looking forward to your clarification.. thanks again!
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Info
Xtra-arrow said:
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Click to expand...
Click to collapse
Wipe everything > Advance Wipe Phone in recovery
Reinstall CM13 through Recovery and don't flash another kernel
:good:
Geeks Empire said:
Wipe everything > Advance Wipe Phone in recovery
Reinstall CM13 through Recovery and don't flash another kernel
:good:
Click to expand...
Click to collapse
Whoa! Don't tell him to wipe everything in the advanced wipe menu, that'll wipe the internal storage too which is completely unnecessary.
Xtra-arrow said:
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Click to expand...
Click to collapse
Which partitions are you backing up when creating the nandroid with TWRP?
Heisenberg said:
Which partitions are you backing up when creating the nandroid with TWRP?
Click to expand...
Click to collapse
System, data, boot - Installing the kernel made no difference, the device still corrupted on reboot. and then sometimes at least twice it has soft-bricked
Geeks Empire said:
Wipe everything > Advance Wipe Phone in recovery
Reinstall CM13 through Recovery and don't flash another kernel
:good:
Click to expand...
Click to collapse
Already tried it mate, a number of times. no joy.
Xtra-arrow said:
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Click to expand...
Click to collapse
The bootloader message won't go away until you lock the bootloader. Its just there as a warning to you in case you did not unlock your phone. As for CM I'm sure there are still many bugs to be worked out. I know I'm going to wait before Flashing it until I see people enjoying it as a daily driver. There are some great devs here in the n6p forums though so I recommend checking out some other ROMs too.
XxMORPHEOUSxX said:
The bootloader message won't go away until you lock the bootloader. Its just there as a warning to you in case you did not unlock your phone. As for CM I'm sure there are still many bugs to be worked out. I know I'm going to wait before Flashing it until I see people enjoying it as a daily driver. There are some great devs here in the n6p forums though so I recommend checking out some other ROMs too.
Click to expand...
Click to collapse
i understand the boot message and CM - i have tried other roms too. i'm not the only one who is getting bootloops on every rom. not sure what to do mate. it says corrupted then boot loops upon restart
Xtra-arrow said:
i understand the boot message and CM - i have tried other roms too. i'm not the only one who is getting bootloops on every rom. not sure what to do mate. it says corrupted then boot loops upon restart
Click to expand...
Click to collapse
Maybe this will be helpful. I think you have the red level warning like this user. Seems like the exact same situation.
http://forum.xda-developers.com/showthread.php?p=64403982
Turns out it isn't bootlooping. Its taking at least 3 minutes to turn on. It looks like bootlooping. BUt if finally loaded. After doing my uninstalling of aomw system apps. Its rebooted and keeps optimising apps. 2-4 then restarts and does same
Info
Heisenberg said:
Whoa! Don't tell him to wipe everything in the advanced wipe menu, that'll wipe the internal storage too which is completely unnecessary.
Click to expand...
Click to collapse
It s necessary to Wipe everything when don't know which modification cause the problem.
+ Recovering the backup also not working for this situation.
@Xtra-arrow
Can u explain step-by-step what u did so far
more detail = better help
:good:
Geeks Empire said:
It s necessary to Wipe everything when don't know which modification cause the problem.
+ Recovering the backup also not working for this situation.
@Xtra-arrow
Can u explain step-by-step what u did so far
more detail = better help
:good:
Click to expand...
Click to collapse
No it isn't necessary to wipe the userdata partition. No modifications are stored in the userdata partition. It would only be necessary to wipe system, data, cache, and dalvik cache. And probably flash the vendor partition too. Not userdata though.
I had a similar problem when I botched a SU flash, same warning then it would take forever to boot, then the rom would degrade over the next several minutes. I know its not fun to start over, but it was the only thing that cleared all the problems. I didn't want to take more time finding another solution when going back to stock is so simple with this device. Follow the instructions in step #11 of Heisenberg's guide (great guide, I link it to friends a lot). Then start again, I know, not what you wanted to hear. Hope this helps!
I am also in agreement with Heisenberg in regards to the userdata partition.
Geeks Empire said:
It s necessary to Wipe everything when don't know which modification cause the problem.
+ Recovering the backup also not working for this situation.
@Xtra-arrow
Can u explain step-by-step what u did so far
more detail = better help
:good:
Click to expand...
Click to collapse
Thank you very much for replying. I have found the root of the cause but no solution. Uninstalling or disabling system apps will cause my phone to go into a "optimising apps" boot loop on the next restart. What do you think? ++ every restore I make on twrp either soft bricks or bootloops. Crazy!
Info
Xtra-arrow said:
Thank you very much for replying. I have found the root of the cause but no solution. Uninstalling or disabling system apps will cause my phone to go into a "optimising apps" boot loop on the next restart. What do you think? ++ every restore I make on twrp either soft bricks or bootloops. Crazy!
Click to expand...
Click to collapse
If you are sure about reason Forget ur Backups.
you should completely install Stock Kernel, Rom, Boot.img >> Back to Stock
But If I remember correctly u did this before...
I just have to say Retry Also Install and use Nexus Root Toolkit
:good:
I have reinstalled original stock files from google. I've wiped everything numerous times. Installed ROMs just after. It took me a while but I think it comes down to the system apps. I'm running a custom ROM, cm13 and my phone is running fine. I know if I was to delete all the unwanted apps off my phone, on next reboot it will try and optimise apps, finish. Says starting apps... Then reboots. Follows the same process.
Xtra-arrow said:
I have reinstalled original stock files from google. I've wiped everything numerous times. Installed ROMs just after. It took me a while but I think it comes down to the system apps. I'm running a custom ROM, cm13 and my phone is running fine. I know if I was to delete all the unwanted apps off my phone, on next reboot it will try and optimise apps, finish. Says starting apps... Then reboots. Follows the same process.
Click to expand...
Click to collapse
Can I ask what gapps are you using? Are you using your google account to recover your apps, or are starting fresh each time?
Sent from my Nexus 6P using Tapatalk
Thanks for your reply. I've actually now narrowed itnright down to a few apps, maybe gapps. Sound recorder, voice recorder app and the google app. Either one or more of these cause my optimising apps bootloop.
So i was going to downgrade from android 7.0 (DigitalHigh6P rom). I flashed the newest 6.0.1 factory images, but no matter what i do, it still bootloops. I have tried sideloading an ota file, wiped everything several times. My bootloader is unlocked (of course).
I never get to the android boot animation.
what do?
I had the same issue upon installing N with complete stock. My bootloader was unlocked. I had to boot into recovery, wipe everything (I did it multiple times to be sure) and then in recovery I powered off the device. With N still installed I setup the phone WITHOUT restoring ANYTHING from Google. Upon the initial setup menu I started like it was a brand new phone and I had no Google account. Set that all up later. That ended my bootloop problem.
Unfortunately Wi-Fi password backup was huge for me and now it's gone. Everything else while a hassle was manageable, I'm hoping when the factory image is released I can start over and sign into my account and have that data restored.
318sugarhill said:
I had the same issue upon installing N with complete stock. My bootloader was unlocked. I had to boot into recovery, wipe everything (I did it multiple times to be sure) and then in recovery I powered off the device. With N still installed I setup the phone WITHOUT restoring ANYTHING from Google. Upon the initial setup menu I started like it was a brand new phone and I had no Google account. Set that all up later. That ended my bootloop problem.
Unfortunately Wi-Fi password backup was huge for me and now it's gone. Everything else while a hassle was manageable, I'm hoping when the factory image is released I can start over and sign into my account and have that data restored.
Click to expand...
Click to collapse
what did you use to update to N?
I was on the beta. I never flashed anything else. Like a dummy I had my adb commands backwards (was using adb instead of fastboot). Otherwise I would have reflashed MM.
Some other person had the exact same issue when going from 7.0 to 6.0.1
I will have to get a replacement. :/
same here.... guess this is the first brickable nexus device... the only thing that gets me to boot is if I flash N then flash the MM F vendor image, but it does not detect the sim card and camera don't work.
Mgrev said:
Some other person had the exact same issue when going from 7.0 to 6.0.1
I will have to get a replacement. :/
Click to expand...
Click to collapse
Look in the other post about botched nougat install , some of us got phone working
yeah some but like most people say they got no backup available so it doesnt help @rbouza1
minidude2012 said:
yeah some but like most people say they got no backup available so it doesnt help @rbouza1
Click to expand...
Click to collapse
I have a twrp backup, but it doesn't help at all.
Mgrev said:
I have a twrp backup, but it doesn't help at all.
Click to expand...
Click to collapse
From that thread, my solution.
FragmentsOfLife said:
Okay, this is the method I used to fix my phone. The issue was the phone constantly alternating between the "Your device cannot be checked for corruption" screen and the white Google screen with the lock.
1. Flash a stock image (I used the August stock image MTC20F)
2. Fastboot flash TWRP 3.0.2-0
3. Boot into TWRP
4. Select Wipe -> Advanced Wipe -> Select and repair each partition individually (some won't be able to, and that's fine, just move on to the next one)
5. Restore a full nandroid backup (make sure everything is selected) and reboot
6. You should now be free of the never ending boots, and if your device is bootlooped at this point (stuck at the boot animation), you can just flash stock again.
Click to expand...
Click to collapse
Mgrev said:
So i was going to downgrade from android 7.0 (DigitalHigh6P rom). I flashed the newest 6.0.1 factory images, but no matter what i do, it still bootloops. I have tried sideloading an ota file, wiped everything several times. My bootloader is unlocked (of course).
I never get to the android boot animation.
what do?
Click to expand...
Click to collapse
Please join this thread to help troubleshoot.
Hoping to find the answer for you!
Mgrev said:
So i was going to downgrade from android 7.0 (DigitalHigh6P rom). I flashed the newest 6.0.1 factory images, but no matter what i do, it still bootloops. I have tried sideloading an ota file, wiped everything several times. My bootloader is unlocked (of course).
I never get to the android boot animation.
what do?
Click to expand...
Click to collapse
Ur getting bootloops bcuz u didn't had cleared the dalvik and sys cache. try doing a sys format (along cleaning those ) and then do a fresh flash of android 6.0.1 then it'll definitely work. (Y)
-anidaniel
anidaniel said:
Ur getting bootloops bcuz u didn't had cleared the dalvik and sys cache. try doing a sys format (along cleaning those ) and then do a fresh flash of android 6.0.1 then it'll definitely work. (Y)
-anidaniel
Click to expand...
Click to collapse
I have already done that, and it does not work.
I have already contacted my retailer about getting a replacement.
I have system-less root on my Huawei Ascend XT and also system-less Xposed installed and working. See https://forum.xda-developers.com/showpost.php?p=70512435&postcount=3 for Xposed installation instructions I used.
Let's discuss anything regarding Xposed and modules in this thread .
Thanks, divineBliss
EDIT: WARNING: NOTE: CAUTION:
Please be aware that if you install Xposed framework on your XT, at times the phone won't boot correctly as evidenced by the fact that if you try to go to bring up the phone settings window/app, the screen will just flicker and the settings screen won't open. The simple solution is to just reboot the phone. Sometimes it takes multiple reboots before the phone successfully reboots/settings app can be successfully opened. This issue has been experienced by me and several others who installed Xposed framework on the XT.
For me personally, the advantages of using Xposed modules far outweigh this minor inconvenience which only happens after a phone reboot.
Not running xposed yet but have there been any issues or maybe a list of what works and doesn't? I'd like to know what others are getting from xposed.
Sent from my H1611 using Tapatalk
I got Xposed modules that let me listen to YouTube with app YouTube app minimized and even screen off.
And another module to adjust YouTube volume/scroll video by swiping on video screen.
See
http://www.howtogeek.com/263663/how...k-for-frustration-free-android-customization/
I used Magisk to install Xposed framework.
Also see: https://forum.xda-developers.com/showpost.php?p=70472229&postcount=488
Some how Xposed didn't install right, It wasn't working so I uninstalled it. My phone started to boot to recovery mode. Couldn't get passed it. I went into TWPR and recovered the Boot backup that TWRP installs to your internal. It "worked" but whenever it booted back to the home screen I got a black screen with nothing but for my notification bar and soft keys.
I tried to use my Backup from whenever I rooted but they are not showing up. I backed them up onto my computer so I put them onto my SD card and they are still not showing up in TWRP
1. After you installed Xposed with Magisk and rebooted the phone, what happened?
2. Did you wait about 30 minutes if the screen was dark or on the boot logo?
3. Go into TWRP and make sure you selected external SD for source. Use the TWRP file manager to make sure you it can access external SD - specifically the folder where you put the TWRP backup.
dabadguycr said:
Some how Xposed didn't install right, It wasn't working so I uninstalled it. My phone started to boot to recovery mode. Couldn't get passed it. I went into TWPR and recovered the Boot backup that TWRP installs to your internal. It "worked" but whenever it booted back to the home screen I got a black screen with nothing but for my notification bar and soft keys.
I tried to use my Backup from whenever I rooted but they are not showing up. I backed them up onto my computer so I put them onto my SD card and they are still not showing up in TWRP
Click to expand...
Click to collapse
divineBliss said:
1. After you installed Xposed with Magisk and rebooted the phone, what happened?
2. Did you wait about 30 minutes if the screen was dark or on the boot logo?
3. Go into TWRP and make sure you selected external SD for source. Use the TWRP file manager to make sure you it can access external SD - specifically the folder where you put the TWRP backup.
Click to expand...
Click to collapse
1. It was working great for about 20mins than everything started to freeze up and crash. Everything before was working great.
2. Yes, it only took around 10mins to boot back up.
3. I did that and my SD card is showing up. What file should the backups be in? I'm thinking I should make another backup than place the ones I have into that file.
I'm wondering if it is something with my launcher. I get Notification bar with everything and Soft key but nothing else.
1. After it booted up fine for 20 minutes, what did you do during that 20 minutes before it crapped out?
2 . So after you installed Xposed Framework with Magisk, the phone booted up fine within 10 minutes?
3. Yes, go back into TWRP and backup just the recovery so you see what directory it creates, then put your original TWRP backup into a similar parallel directory and see what happens.
What launcher are you using?
dabadguycr said:
1. It was working great for about 20mins than everything started to freeze up and crash. Everything before was working great.
2. Yes, it only took around 10mins to boot back up.
3. I did that and my SD card is showing up. What file should the backups be in? I'm thinking I should make another backup than place the ones I have into that file.
I'm wondering if it is something with my launcher. I get Notification bar with everything and Soft key but nothing else.
Click to expand...
Click to collapse
divineBliss said:
1. After it booted up fine for 20 minutes, what did you do during that 20 minutes before it crapped out?
2 . So after you installed Xposed Framework with Magisk, the phone booted up fine within 10 minutes?
3. Yes, go back into TWRP and backup just the recovery so you see what directory it creates, then put your original TWRP backup into a similar parallel directory and see what happens.
What launcher are you using?
Click to expand...
Click to collapse
I did 3. Took about 5mins to reboot. No launcher but luckily I had a pop up for updates so I was able to get into store to download a launcher.
imma try to download one.
It just says Download Pending nothing else.
Did you just restore a TWRP backup? Rooted backup or before root backup? Why was there no launcher in this backup?
dabadguycr said:
I did 3. Took about 5mins to reboot. No launcher but luckily I had a pop up for updates so I was able to get into store to download a launcher.
imma try to download one.
Click to expand...
Click to collapse
divineBliss said:
Did you just restore a TWRP backup? Rooted backup or before root backup? Why was there no launcher in this backup?
Click to expand...
Click to collapse
I thought I froze the stock launcher I think I may have deleted it. The stock launcher is found in the System files since it's read only I can not restore the system.
I thought I placed the stock recovery on my phone but I guess not. I still have super user and root.
I just checked my root with rootchecker and its working perfectly.
You can check or uncheck the box when TWRP starts to make System writable and you need to do that now to restore your System backup from TWRP. If you made a backup after rooting, you could try to restore that.
dabadguycr said:
I thought I froze the stock launcher I think I may have deleted it. The stock launcher is found in the System files since it's read only I can not restore the system.
I thought I was using a stock back up but I still have root.
Click to expand...
Click to collapse
Is your phone working now? What was the lesson learned out of all this? Got some notes/bullets to share for others?
dabadguycr said:
I thought I froze the stock launcher I think I may have deleted it. The stock launcher is found in the System files since it's read only I can not restore the system.
I thought I placed the stock recovery on my phone but I guess not. I still have super user and root.
I just checked my root with rootchecker and its working perfectly.
Click to expand...
Click to collapse
divineBliss said:
Is your phone working now? What was the lesson learned out of all this? Got some notes/bullets to share for others?
Click to expand...
Click to collapse
Yes, it's working again!!
I learned be very very careful removing Xposed and do not remove or freeze the stock launcher.
If you are restoring from a older backup and it doesn't show up. Make a new backup (I did cache only back up so I could tell the difference easier) on your SD Card. It should create a folders called
TWRP/BACKUP/(folder with 8 different letters and numbers) / (Then your new backup file)
Place your old backup folder under the new one. It will now show up in TWRP.
It's safe to restore a backup with root and super user. Takes around 10mins first boot.
Now that you have mastered restoring in 10 minutes, try Xposed again. I got it installed first try with Magisk. .
Every time I boot, I click the settings icon to make sure it works. Sometimes the screen just flashes and no settings screen comes up, so I just reboot. I'm not sure if that's caused by Xposed or what at this point, but it's not worth uninstalling Xposed for me to find out at this point.
dabadguycr said:
Yes, it's working again!!
I learned be very very careful removing Xposed and do not remove or freeze the stock launcher.
If you are restoring from a older backup and it doesn't show up. Make a new backup (I did cache only back up so I could tell the difference easier) on your SD Card. It should create a folders called
TWRP/BACKUP/(folder with 8 different letters and numbers) / (Then your new backup file)
Place your old backup folder under the new one. It will now show up in TWRP.
It's safe to restore a backup with root and super user. Takes around 10mins first boot.
Click to expand...
Click to collapse
divineBliss said:
Now that you have mastered restoring in 10 minutes, try Xposed again. I got it installed first try with Magisk. .
Every time I boot, I click the settings icon to make sure it works. Sometimes the screen just flashes and no settings screen comes up, so I just reboot. I'm not sure if that's caused by Xposed or what at this point, but it's not worth uninstalling Xposed for me to find out at this point.
Click to expand...
Click to collapse
I honestly think Magisk uninstall was what crashed my phone. I think I may have uninstalled it wrong. From the guide I read it said download the uninstall go into custom recovery and open the zip. I just thought it was Xposed because that's when my system started freezing.
divineBliss said:
Thanks, these details are important. So make a backup of Boot, System, and Data (and be sure you already have a good backup of Cust somewhere) if you want to try installing Xposed again. Depending on what else you do, you should only need to restore System if things get messed up trying to install Xposed again. And again, I have it installed with Xposed modules working, so it's possible.
Click to expand...
Click to collapse
Does installing Xposed even touch the system? It looked like it modifies the boot but doesn't touch the system.
The Xposed install is supposed to be system-less, and you get did things working by only restoring Boot, that's why I said probably just Boot needs to be restored. If things didn't work after that, I'd restore System, and then if still not working, restore Data after that.
If you do try and reinstall Xposed, can you take notes on where it takes a long wait before something happens ........ I forgot to do that and don't remember now. It's not fun when the screen goes dark and you don't expect it ....... actually I seem to remember that happening for like 30 minutes ??? when I install Magisk/Xposed ........ the screen wasn't even on.
dabadguycr said:
Also
Does installing Xposed even touch the system? It looked like it modifies the boot but doesn't touch the system.
Click to expand...
Click to collapse
divineBliss said:
The Xposed install is supposed to be system-less, and you did things working by only restoring Boot, that's why I said probably just Boot needs to be restored. If things didn't work after that, I'd restore System, and then if still not working, restore Data after that.
If you do try and reinstall Xposed, can you take notes on where it takes a long wait before something happens ........ I forgot to do that and don't remember now. It's not fun when the screen goes dark and you don't expect it ....... actually I seem to remember that happening for like 30 minutes ??? when I install Magisk/Xposed ........ the screen wasn't even on.
Click to expand...
Click to collapse
I'm going to install it manually. I think Magisk was what missed up my phone last time so I rather go that path then taking the chance at missing something up again.
I'm going to install sdk23 should I install arm arm64 or x86.
I don't believe our phone is a 32bit system so x86 is out. I think arm64? Correct?
Yes, arm64. Take notes and good luck . Do you have a link on how to install it manually?
dabadguycr said:
I'm going to install it manually. I think Magisk was what missed up my phone last time so I rather go that path then taking the chance at missing something up again.
I'm going to install sdk23 should I install arm arm64 or x86.
I don't believe our phone is a 32bit system so x86 is out. I think arm64? Correct?
Click to expand...
Click to collapse
divineBliss said:
Yes, arm64. Take notes and good luck . Do you have a link on how to install it manually?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=3034811
I'm using this link.
Believe I just download the zip to SD card
Go into TWRP
Click install
Find the zip
Swipe to install
Click Wipe
Wipe cache and dalvik
I did a stupid thing. I got away with it. Pure Nexus running normally now. Questions remain that boil down to this: why wasn't this a much bigger ordeal than it turns out to have been? I'd like to at least learn something when I do a bone headed thing. Here's the sequence of events.
1) 6p, pure nexus 7.1.2, latest vendor etc with twrp 2.8, rooted and running like a champ.
2) fooling around with different apps and so forth, took a look at a couple of dialers that I didn't much like, took them back off. After one of these the stock pure nexus phone app (I think this is just google dialer) started crashing constantly. Restoring titanium backups didn't stop it. Restoring a month old nandroid backup didn't stop it.
3) getting super annoyed (a poor time to start ripping stuff out), I wiped every partition on the phone in twrp except the SD card where all my recovery images and things like SuperSU.zip and some ROMs are stored. Wiped system, data, cache, boot, & dalvik cache.
4) restored a backup image and rebooted. Twrp gave me the no OS warning but I was on automatic pilot, swiped to reboot, and then I was like "what?! No OS! Wtf?" But I had already done the deed. Nothing to do now but wait to see what would happen. I was expecting moderately bad news - like I would end up monkeying with fastboot or adb if I couldn't boot back to twrp and flash the pure nexus image I was pretty sure I still had in storage.
5) result: pretty quickly I was watching the Pure Nexus boot animation so I knew that I was booting Pure Nexus. And this was the case. It took an extra long time like it does on the first boot but then there is was. Welcome. Let's get started. I set the phone back up and replaced most apps from backups and no harm, no foul. Also, the phone app stopped crashing. Bonus.
Now, I have no idea why I got the no OS warning from twrp. I'm sure that if I'd read it before I swiped to reboot and not after, like a bonehead, I would have done something like trying to flash the backup again or even the ROM I have on the SD card. Anything but reboot with the no OS warning on the screen. But the result was the same as if I'd flashed the ROM without, as I think of it now, flashing gapps or SuperSU. I had to go back and flash SuperSU but I put the apps back with titanium backup.
If anyone would like to take a shot at telling me how I got this result I think it might light up a dark area in my just-enough-experience-to-be-dangerous brain. Thanks in advance.
Truechunks said:
I did a stupid thing. I got away with it. Pure Nexus running normally now. Questions remain that boil down to this: why wasn't this a much bigger ordeal than it turns out to have been? I'd like to at least learn something when I do a bone headed thing. Here's the sequence of events.
1) 6p, pure nexus 7.1.2, latest vendor etc with twrp 2.8, rooted and running like a champ.
2) fooling around with different apps and so forth, took a look at a couple of dialers that I didn't much like, took them back off. After one of these the stock pure nexus phone app (I think this is just google dialer) started crashing constantly. Restoring titanium backups didn't stop it. Restoring a month old nandroid backup didn't stop it.
3) getting super annoyed (a poor time to start ripping stuff out), I wiped every partition on the phone in twrp except the SD card where all my recovery images and things like SuperSU.zip and some ROMs are stored. Wiped system, data, cache, boot, & dalvik cache.
4) restored a backup image and rebooted. Twrp gave me the no OS warning but I was on automatic pilot, swiped to reboot, and then I was like "what?! No OS! Wtf?" But I had already done the deed. Nothing to do now but wait to see what would happen. I was expecting moderately bad news - like I would end up monkeying with fastboot or adb if I couldn't boot back to twrp and flash the pure nexus image I was pretty sure I still had in storage.
5) result: pretty quickly I was watching the Pure Nexus boot animation so I knew that I was booting Pure Nexus. And this was the case. It took an extra long time like it does on the first boot but then there is was. Welcome. Let's get started. I set the phone back up and replaced most apps from backups and no harm, no foul. Also, the phone app stopped crashing. Bonus.
Now, I have no idea why I got the no OS warning from twrp. I'm sure that if I'd read it before I swiped to reboot and not after, like a bonehead, I would have done something like trying to flash the backup again or even the ROM I have on the SD card. Anything but reboot with the no OS warning on the screen. But the result was the same as if I'd flashed the ROM without, as I think of it now, flashing gapps or SuperSU. I had to go back and flash SuperSU but I put the apps back with titanium backup.
If anyone would like to take a shot at telling me how I got this result I think it might light up a dark area in my just-enough-experience-to-be-dangerous brain. Thanks in advance.
Click to expand...
Click to collapse
Why are you still using TWRP 2.8? 3.11 is the latest version now. Not sure if it's related or not though.
My bad. That's the SuperSU version. TWRP is the latest. 3.1.1
Moderator Information,
Thread closed at OP's request.