Related
I just updated my LTE to the official Bell Mobility ICS software, I rooted it and was in the process of deleting bloatware and i accidentally deleted SystemUI.apk. Thus leading to a crash and now my phone is stuck on the LG screen with security error underneath. Can someone please help me get my phone working again.
Thanks.
You're going to have to go through the unbricking guide since you definitely just bricked your phone.
You can try doing a factory reset if it lets you. Not sure if it lets you in that situation though.
When device is completely off, hold power button and volume down button for 5-10 seconds. Then press power button twice to confirm.
He deleted SystemUI.apk. Even if that didn't trigger LG's secure boot error, it would be in an endless bootloop that only *might* be recoverable if adb still managed to function and he had root permissions. His only option is to unbrick, which is fortuitous in a way because it will allow him to install a proper recovery that can prevent this from happening in the future.
I just did the same thing, only I deleted Google Play Books. Holy **** is this ROM ever loaded with useless crap.
Press Volume Up + insert USB cable to access download mode. You should be able to unbrick using this.
Instead of using titanium backup to uninstall the bloatware... you need to freeze it (requires titanium backup pro)
Malnilion said:
He deleted SystemUI.apk. Even if that didn't trigger LG's secure boot error, it would be in an endless bootloop that only *might* be recoverable if adb still managed to function and he had root permissions. His only option is to unbrick, which is fortuitous in a way because it will allow him to install a proper recovery that can prevent this from happening in the future.
Click to expand...
Click to collapse
Yeah I misread what he said. I thought he meant he only "disabled" it.
Warrimonk said:
I just did the same thing, only I deleted Google Play Books. Holy **** is this ROM ever loaded with useless crap.
Press Volume Up + insert USB cable to access download mode. You should be able to unbrick using this.
Instead of using titanium backup to uninstall the bloatware... you need to freeze it (requires titanium backup pro)
Click to expand...
Click to collapse
Can't you just disable all the bloatware applications using Google's built-in method? You don't even need root to do that. And it's safer than using apps like Titanium Backup which will actually modify the system partition.
This is assuming LG hasn't removed the ability to disable apps.
Then again, I'm not sure what Google's method does. I assume it doesn't modify the system partition directly but I am not sure.
drumist said:
Can't you just disable all the bloatware applications using Google's built-in method? You don't even need root to do that. And it's safer than using apps like Titanium Backup which will actually modify the system partition.
This is assuming LG hasn't removed the ability to disable apps.
Then again, I'm not sure what Google's method does. I assume it doesn't modify the system partition directly but I am not sure.
Click to expand...
Click to collapse
What method are you talking about? Hiding an app in the app tray? It does not exist in this version... and the built in lg "App manager" only lets you remove a single app... leaves a lot more junk untouched.
Warrimonk said:
What method are you talking about? Hiding an app in the app tray? It does not exist in this version... and the built in lg "App manager" only lets you remove a single app... leaves a lot more junk untouched.
Click to expand...
Click to collapse
I'm talking about going to System settings > Apps > Select a preloaded app > click Disable. If the app has been updated, you have to do "Uninstall updates" first for it to show up.
I don't know if LG has changed how this all works though.
I was worried i was going to have to do that. I have no idea what i am supposed to do. That whole process has me lost. Do you think it is possible to bring it in to a local repair shop and maybe they can do it? I just don't want to mess it up anymore then it is.
Ethanp said:
I was worried i was going to have to do that. I have no idea what i am supposed to do. That whole process has me lost. Do you think it is possible to bring it in to a local repair shop and maybe they can do it? I just don't want to mess it up anymore then it is.
Click to expand...
Click to collapse
I just unbricked it following this guide http://forum.xda-developers.com/showthread.php?t=1784709
Just follow the steps carefully.
Have you tried running the Bell ICS installer again while the phone is in download mode? (To get to download mode, turn phone completely off, then hold down volume up button while inserting the USB cable. Don't press power button; phone should turn itself on.)
I think that's all you need to do to get it back up and working.
drumist said:
Have you tried running the Bell ICS installer again while the phone is in download mode? (To get to download mode, turn phone completely off, then hold down volume up button while inserting the USB cable. Don't press power button; phone should turn itself on.)
I think that's all you need to do to get it back up and working.
Click to expand...
Click to collapse
Are you talking about installing the .kdz file through LG tools? I have downloaded the official Bell ICS release from HO!NO!'s thread but don't know how to install it. I try updating through LG tools but it says i am already up to date. Is there a way i can force an update?
Ethanp said:
Are you talking about installing the .kdz file through LG tools? I have downloaded the official Bell ICS release from HO!NO!'s thread but don't know how to install it. I try updating through LG tools but it says i am already up to date. Is there a way i can force an update?
Click to expand...
Click to collapse
Ah, I figured I was forgetting something. LG's tools are frustrating. I don't really see the point in preventing you from reflashing a ROM.
Yes, you can force it -- that's actually what the unbricking guide does, basically. So I guess you will have to follow the unbricking guide process, except use the Bell ICS KDZ file when doing it (and stop after you finish flashing the KDZ). The KDZ can be downloaded here: http://forum.xda-developers.com/showpost.php?p=30177420&postcount=1
drumist said:
Ah, I figured I was forgetting something. LG's tools are frustrating. I don't really see the point in preventing you from reflashing a ROM.
Yes, you can force it -- that's actually what the unbricking guide does, basically. So I guess you will have to follow the unbricking guide process, except use the Bell ICS KDZ file when doing it (and stop after you finish flashing the KDZ). The KDZ can be downloaded here: http://forum.xda-developers.com/showpost.php?p=30177420&postcount=1
Click to expand...
Click to collapse
Alright so i attempted the unbricking process, something strange happened. My phone left download mode the home back and menu buttons flashed my computer recognized it and then it shut off. Now it won't turn on or go into download mode or recognize I'm charging it. Noting just a black screen.
Ethanp said:
Alright so i attempted the unbricking process, something strange happened. My phone left download mode the home back and menu buttons flashed my computer recognized it and then it shut off. Now it won't turn on or go into download mode or recognize I'm charging it. Noting just a black screen.
Click to expand...
Click to collapse
Pull the battery out, plug it back in, and see if you can get to download mode again.
drumist said:
Pull the battery out, plug it back in, and see if you can get to download mode again.
Click to expand...
Click to collapse
Tried that and nothing happened. I'm just assuming that the battery is dead because normally (correct me if I'm wrong) when the three buttons flash it means your battery is dead. And I have been doing some research and it seems that the phone will not charge in download mode. So I have it plugged into the wall to see if it powers up (taking an awful long time though).
Warrimonk said:
I just did the same thing, only I deleted Google Play Books. Holy **** is this ROM ever loaded with useless crap.
Press Volume Up + insert USB cable to access download mode. You should be able to unbrick using this.
Instead of using titanium backup to uninstall the bloatware... you need to freeze it (requires titanium backup pro)
Click to expand...
Click to collapse
I agree the ROM is filled with tons of bloatware. What a frustrating process. Waited so long for the update and not even 24 hours with it and this happens lol.
Ethanp said:
Tried that and nothing happened. I'm just assuming that the battery is dead because normally (correct me if I'm wrong) when the three buttons flash it means your battery is dead. And I have been doing some research and it seems that the phone will not charge in download mode. So I have it plugged into the wall to see if it powers up (taking an awful long time though).
Click to expand...
Click to collapse
Yeah, I've never let my phone get that low, but supposedly it takes a while for it to get high enough to stop doing that. I'd let it charge for a few hours to make sure it's high enough to not die on you again.
I just upgraded to Bell ICS ,but when the upgrade finished, my phone displayed the LG logo (like it would when you turn on the phone) for an hour......
not sure what to do as i have left the phone for a long time and nothing has happened, any suggestions??
Thanks for all the solutions from everyone. After many hours i have successfully "unbricked" my Optimus. My phone would not charge for 3+ hours and eventually got completely stuck in download mode. But I ran windows enabler and small server and after 50 or so tries the kdz update tool finally took my phone and updated it to the point prior to bricking.
I saw a couple people had the same issue that im now having but none of there solutions solved my problem
i wiped my GS3 for ATT tried to go back to a stock with root rom and when it rebooted it now just hangs at the samsung logo at boot tried re-flashing via odin with no luck also tried flashing a CWM.tar since i cant get into stock or CWM recovery to flash from there is there something im missing i know its late and maybe my brain isnt working like it should
Solved the problem myself.....and rather then just say i figured it out ill share how i did this since i watched countless videos and read endless amounts of threads and since none of them helped mem
First also try t put your phone into stock recovery mode and wipe your phone then flash this should take care of things if it doesnt try what i tried below
and i hope this can help someone else out there who has the same problem that i had all you have to do is the following i did this with obviously an AT&T model should work with others but as always try at your own risk.....
First make sure your battery has a charge even if its stuck on the boot screen its still charging....
then download KIES from samsung update it and make sure you have the latest version.
Next plug in your phone if your stuck at the samsung screen your computer will recognize your phone still at least it did with mine.
Once your done with the above open up KIES goto the top and then TOOLS and Firmware upgrade click on that enter your phone model (ATT SGH-I747) i dont get this part but next it will ask you for your SN and for some reason it doesnt recognize the SN use your IMEI
Now it should ask you a couple questions tell you its wiping your device and you will lose everything etc.....but then it will download the latest FW and begin to install everything and in about 20-25 mins everything will be back to stock
Nvm.. misread.
I'm stuck too...and Kies can't find the phone. Anyone have any other ideas? I can't even get into recovery...only download mode.
dbdynsty25 said:
I'm stuck too...and Kies can't find the phone. Anyone have any other ideas? I can't even get into recovery...only download mode.
Click to expand...
Click to collapse
your computer is not seeing your phone when you plug it in or its just KIES that doesnt see it??
also im guessing you have all the correct drivers installed??
yearziro said:
your computer is not seeing your phone when you plug it in or its just KIES that doesnt see it??
also im guessing you have all the correct drivers installed??
Click to expand...
Click to collapse
Yes, all drivers are installed because that's how I ODIN flashed it in the first place! Just stuck on the damn Samsung screen and I can't get Kies to connect to the phone. Not in Download Mode or when it's just stuck on that screen.
you can just hold VOL UP, HOME , POWER same time enter stock samsung recovery mode and scroll down select wipe data and cache and reboot u should good to go....
whit3gh0szt said:
you can just hold VOL UP, HOME , POWER same time enter stock samsung recovery mode and scroll down select wipe data and cache and reboot u should good to go....
Click to expand...
Click to collapse
Worked, thanks! I appreciate it.
it doesnt work on mine
dbdynsty25 said:
Worked, thanks! I appreciate it.
Click to expand...
Click to collapse
my cellphone reboots by itself on the samsun screen and i cant get on the recovery mode! any ideas!"
me neither
mkstf said:
my cellphone reboots by itself on the samsun screen and i cant get on the recovery mode! any ideas!"
Click to expand...
Click to collapse
Yeah I can't get into recovery either, and its getting really annoying.
indieslap said:
Yeah I can't get into recovery either, and its getting really annoying.
Click to expand...
Click to collapse
With the phone off, hold down VOL UP + HOME + POWER until the phone vibrates. Then let go of the power button. When you see the blue text in the top left corner of the samsung boot screen, let go of the other 2 buttons
xBeerdroiDx said:
With the phone off, hold down VOL UP + HOME + POWER until the phone vibrates. Then let go of the power button. When you see the blue text in the top left corner of the samsung boot screen, let go of the other 2 buttons
Click to expand...
Click to collapse
Okay, this brought the menu up for me, but I removed the data,cache, and reset the phone and it is still not working. Also, my phone just goes black after the Galaxy Samsung S3 logo, but the blue light in the top left is still on. Can anyone help me out?
P.S. Sorry for reviving this thread if it is too old.
Edit: I should also mention that I can still hear the sound of the phone booting up (the sound that typically occurs when the phone is on the white loading screen). However, the screen is black at this point.
cabato said:
Okay, this brought the menu up for me, but I removed the data,cache, and reset the phone and it is still not working. Also, my phone just goes black after the Galaxy Samsung S3 logo, but the blue light in the top left is still on. Can anyone help me out?
P.S. Sorry for reviving this thread if it is too old.
Edit: I should also mention that I can still hear the sound of the phone booting up (the sound that typically occurs when the phone is on the white loading screen). However, the screen is black at this point.
Click to expand...
Click to collapse
You're going to have to tell us what you did (changed, flashed, etc) before all this so that we can help you
xBeerdroiDx said:
You're going to have to tell us what you did (changed, flashed, etc) before all this so that we can help you
Click to expand...
Click to collapse
Ah, sorry about not providing enough information. Please keep in mind that I am very inexperienced and I may get some things incorrect just due to that. To my understanding, I went to try and root my phone, but beforehand I used the guides below to get my phone ready for the root (yes I do realize at this point that using these outdated guides was a clear mistake and I should have come to XDA instead). I flashed my phone to the stock kernel using the file that site provided, and then encountered the problem above. In my panic I have tried to restore the phone through several methods, but every time I try to load anything onto it with Odin, it doesn't complete until my phone restarts (and my phone won't boot up completely) so I can't get the pass message. Interestingly enough I did manage to get clockwork mod installed as that is what shows up when I try a secure boot using the methods that you described.
Ah, I am unfortunately not allowed to post links. The guides were off of Android Authority.
If there is any other information needed to help me please let me know and I will do my best to obtain it.
cabato said:
Ah, sorry about not providing enough information. Please keep in mind that I am very inexperienced and I may get some things incorrect just due to that. To my understanding, I went to try and root my phone, but beforehand I used the guides below to get my phone ready for the root (yes I do realize at this point that using these outdated guides was a clear mistake and I should have come to XDA instead). I flashed my phone to the stock kernel using the file that site provided, and then encountered the problem above. In my panic I have tried to restore the phone through several methods, but every time I try to load anything onto it with Odin, it doesn't complete until my phone restarts (and my phone won't boot up completely) so I can't get the pass message. Interestingly enough I did manage to get clockwork mod installed as that is what shows up when I try a secure boot using the methods that you described.
Ah, I am unfortunately not allowed to post links. The guides were off of Android Authority.
If there is any other information needed to help me please let me know and I will do my best to obtain it.
Click to expand...
Click to collapse
Sounds like you need to clear your cache partition and clear your dalvik cache. There are several guides on this site to help you. Choose the one that is most appropriate to what you are trying to do and follow it EXACTLY. There is one to start. Follow it from the beginning.
http://forum.xda-developers.com/showthread.php?t=2042775
When nothing else works start over from search. You cab use download mode? First make sure you got right drivers as that can mess up Odin. Use one in my Sig if you want. Then flag stock recovery with root someone nice will part a link to it I'm on my phone can't do it. Well fix your phone
Sent from my SGH-I747 using xda premium
allow rldcess
Okay now I am running into another problem. I have tried downloading the drivers from many different places and they always seem to be correctly downloaded. That being said, I can't install the drivers after I plug my phone into the computer (after downloading and installing Samsung USB drivers). Therefore, I cannot access my phone storage to put the root zip file on it. I was still able to download the custom recovery.
Now I have gone to a different computer, and the drivers seem to install correctly, but the phone still does not appear under my computer.
Edit: I do already have a root zip file on my phone from my earlier attempt, but I install it and my phone still doesn't load up. Also, Odin still recognizes the phone.
Edit 2: Windows says that the drivers cannot recognize the device. Edit 3: "Hardware ID Missing"
Bump
Sorry, I really need help for this. I can't install the MTP drivers even through using some of the tips on this site. That seems to be the problem with me accessing the phones storage from my computer. Does anyone have an ideas for what else I could do? Should I just take it to the store and hope they can fix it?
cabato said:
Okay now I am running into another problem. I have tried downloading the drivers from many different places and they always seem to be correctly downloaded. That being said, I can't install the drivers after I plug my phone into the computer (after downloading and installing Samsung USB drivers). Therefore, I cannot access my phone storage to put the root zip file on it. I was still able to download the custom recovery.
Now I have gone to a different computer, and the drivers seem to install correctly, but the phone still does not appear under my computer.
Edit: I do already have a root zip file on my phone from my earlier attempt, but I install it and my phone still doesn't load up. Also, Odin still recognizes the phone.
Edit 2: Windows says that the drivers cannot recognize the device. Edit 3: "Hardware ID Missing"
Click to expand...
Click to collapse
go to your device manager on your computer, locate samsung drivers for your device, uninstall them
restart your computer
then plug in the phone and lets it reinstall by itself
Use my drivers in my signature
They are last good damaging drivers. Don't update them but install them and plug phone in with no internet. after install plug internet in. There good stable drivers
Sent from my SAMSUNG-SGH-I747 using xda premium
Howdy folks, a couple questions. I had 4.1.2 on my 1st gen KF for a while now and just upgraded to 4.3. In doing so I lost the option to boot into Recovery (I used to be given the option when I held the power button). Now I am not sure how to get to TWRP.
Also, and more frustrating, I noticed several of the apps I had working before, won't work. Flickr, for example, will download and install, but when I try to launch it, I just get an error saying "Unfortunately, Flickr, has stopped "
Any ideas?
(Sorry if this has been discussed, I searched all night, but didn't find anything.)
DaveInPhilly said:
Howdy folks, a couple questions. I had 4.1.2 on my 1st gen KF for a while now and just upgraded to 4.3. In doing so I lost the option to boot into Recovery (I used to be given the option when I held the power button). Now I am not sure how to get to TWRP.
Also, and more frustrating, I noticed several of the apps I had working before, won't work. Flickr, for example, will download and install, but when I try to launch it, I just get an error saying "Unfortunately, Flickr, has stopped "
Any ideas?
(Sorry if this has been discussed, I searched all night, but didn't find anything.)
Click to expand...
Click to collapse
Open GooManager and reboot recovery from there.
https://play.google.com/store/apps/details?id=com.s0up.goomanager&hl=en
DaveInPhilly said:
Howdy folks, a couple questions. I had 4.1.2 on my 1st gen KF for a while now and just upgraded to 4.3. In doing so I lost the option to boot into Recovery (I used to be given the option when I held the power button). Now I am not sure how to get to TWRP.
Also, and more frustrating, I noticed several of the apps I had working before, won't work. Flickr, for example, will download and install, but when I try to launch it, I just get an error saying "Unfortunately, Flickr, has stopped "
Any ideas?
(Sorry if this has been discussed, I searched all night, but didn't find anything.)
Click to expand...
Click to collapse
amandadam said:
Open GooManager and reboot recovery from there.
https://play.google.com/store/apps/details?id=com.s0up.goomanager&hl=en
Click to expand...
Click to collapse
Sooooo.....why do you think we install FireFireFire?
soupmagnet said:
Sooooo.....why do you think we install FireFireFire?
Click to expand...
Click to collapse
Huh
amandadam said:
Huh
Click to expand...
Click to collapse
FireFireFire comes with an option to use the power button upon startup to access a boot menu, which will give you to access custom recovery. AOSP doesn't have the option to reboot into recovery or GooManager, so you'll just reboot and use the FireFireFire boot menu upon startup. If one doesn't have FireFireFire installed, it should be installed immediately because it will be invaluable in case something goes wrong...and it usually does.
so,i have the ze551ml,and right now, i can boot it up,but it gets stuck at the asus logo,and the spinning circle below it. i see lots of people clearing cache,going into safe mode,or simply reinstalling the firmware.
first method doesn't work,i don't know how to clear device cache without actually being inside,i.e. actually have android properly loaded up
second method,just seems to get me nowhere.
third method,i tried power,then up rocker,then the recovery tab,just gives me the dead android thing with error written below.
help,this is my daily driver,so everything's on it!
also,forgot to mention,so this is a quick edit,i have adb installed(i think) on my pc,but whenever it launches,it justs has text running quickly,too fast for me to read,then self exits.
i also have to disconnect it from my pc or else it would not reboot.
umm..quick update,the recovery function now somewhat works, i managed to get the firmware from asus's webpage,put it in a ,microsd card,renamed it MOFD_SDUPDATE.zip. it seems to recognize it,at least no dead android with error sign,but after the install,it just does nothing.
it also never seems to actually finish the update,as it just gets about one third of the way,then vibrates twice,and reboots.
i did somehow manage to get it to boot up to the lock screen yesterday before i went to sleep,but then,after i woke up,it just seemed to have rebooted itself,and is stuck on the asus logo with the spinning wheel below again.
if u facing the continuously rotating circle problem in boot screen, then there is very easy solution. it is a very common problem happens for mainly low memory ,sometimes other.. it happens very often to me..
1.first clear user data then clear cache from recovery. u can also use adb from pc.
2. just restart.
[if you dont know how to open recovery, thenopen fastboot & select recovery as u mentioned in ur question, next when the dead android logo appears, dont worry. Then PRESS & HOLD VOL UP+POWER for 3 sec. it ll take few trying as it needs perfect timing to press those keys at a same time. from there you can clear data and cache.]
#PRESS THANKS IF IT HELPS YOU.
sounak1 said:
if u facing the continuously rotating circle problem in boot screen, then there is very easy solution. it is a very common problem happens for mainly low memory ,sometimes other.. it happens very often to me..
1.first clear user data then clear cache from recovery. u can also use adb from pc.
2. just restart.
if there is important data in internal memory,then try with flash the firmware. dont know if it ll solve or not as i always do the above steps and it becomes OK.
#PRESS THANKS IF IT HELPS YOU.
Click to expand...
Click to collapse
i'll try the first method,but i just tried the third,and that did nothing.
i also tried the second method,multiple times,nothing.
also,how could it have low memory? it's not even booted up,technically.
Jasper1224 said:
i'll try the first method,but i just tried the third,and that did nothing.
i also tried the second method,multiple times,nothing.
also,how could it have low memory? it's not even booted up,technically.
Click to expand...
Click to collapse
Try to install custom ROM, like SuperZen. I think the is when you update your ROM and it doesn't finish due to a bad download.
24imelqui said:
Try to install custom ROM, like SuperZen. I think the is when you update your ROM and it doesn't finish due to a bad download.
Click to expand...
Click to collapse
But you have to unlock bootloader for that. Not everyone wants to do that...
Perhaps it's better to install Asus Flash Tool on your computer and flash raw firmware. You could even try without clearing user data.
Jasper1224 said:
i'll try the first method,but i just tried the third,and that did nothing.
i also tried the second method,multiple times,nothing.
also,how could it have low memory? it's not even booted up,technically.
Click to expand...
Click to collapse
just delete the internal memory..then clear cache..then restart
nothing else
sorry,done that after a bit of reserach,didn't type it in...everything's fine.
but can i just clear cache next time?
sorry,done that after a bit of reserach,didn't type it in...everything's fine.
but can i just clear cache next time?
Jasper1224 said:
sorry,done that after a bit of reserach,didn't type it in...everything's fine.
but can i just clear cache next time?
Click to expand...
Click to collapse
sir can you help me with this please? i have the same problem right now with my asus zenfone 2 z00ad. im stuck on the asus logo with this circle. please help me.
Well I recently bootlooped my OnePlus 8 Pro installing a module that I totally forgot is build specific..
What a dummy?...
Well Safe mode is certainly the easiest and simplest way to get you back up and running...
All you do is 1. Enter fastboot mode and select power off.
2. Start phone as soon as you see that OnePlus logo press and hold the Volume + and Volume - buttons till it boots into your system in safe mode...
3. Go into phone settings, then to Apps and notification.
Finally, go into all apps. Scroll down to Magisk Manager and clear all data from the app. Then you can restart phone enable modules restart phone again and back to normal....
For me it's a piece of mind now that we have no Custom Recovery...
This is exactly how I have done it twice now and worked both times perfectly...
Actually found this out a while back..I think it's a feature of magisk to do this when you boot to safe mode to remove faulty modules.
There is no need to clear data or go to the fastboot mode btw.
1. Hold power until it's off.
2. Boot and wait for the bootloader warning.
3. Hold vol up and down until boot animation.
4. Once it's booted just reboot again and you're done.
Now on boot all magisk modules are disabled.
Remove what failed and re-enable everything else.
:good:
I too discovered this the hard way (and for the same reasons)... Works well!
Sent from my IN2025 using Tapatalk
TENlll423 said:
Well I recently bootlooped my OnePlus 8 Pro installing a module that I totally forgot is build specific..
What a dummy...
Well Safe mode is certainly the easiest and simplest way to get you back up and running...
All you do is 1. Enter fastboot mode and select power off.
2. Start phone as soon as you see that OnePlus logo press and hold the Volume + button till it boots into your system in safe mode...
3. Go into phone settings, then to Apps and notification.
Finally, go into all apps. Scroll down to Magisk Manager and clear all data from the app. Then you can restart phone enable modules restart phone again and back to normal....
For me it's a piece of mind now that we have no Custom Recovery...
This is exactly how I have done it twice now and worked both times perfectly...
Click to expand...
Click to collapse
We do have a custom recovery for A 10
dladz said:
Actually found this out a while back..I think it's a feature of magisk to do this when you boot to safe mode to remove faulty modules.
There is no need to clear data or go to the fastboot mode btw.
1. Hold power until it's off.
2. Boot and wait for the bootloader warning.
3. Hold vol up and down until boot animation.
4. Once it's booted just reboot again and you're done.
Now on boot all magisk modules are disabled.
Remove what failed and re-enable everything else.
:good:
Click to expand...
Click to collapse
I shared something that works for me.. I did forget to put volume - so thanks for that...
There is plenty of people that might benefit from this...
I know I would have in the past..
Good to know this available option! cheers
TENlll423 said:
I shared something that works for me.. I did forget to put volume - so thanks for that...
There is plenty of people that might benefit from this...
I know I would have in the past..
Click to expand...
Click to collapse
Nah you miss my point, i think it's a good thing you put it up, I clicked thanks.
And I agree people will definitely benefit from it, maybe change the name of the thread to magisk module failure recovery or something so people know what it is..safe mode doesn't really describe it, just a thought.
Just helping you on a couple of things that's all, didn't want you wiping data for no reason and I wasn't sure about the vol up and down, it's just what worked for me.
The more info and guides there is on here the better..less questions asked.
:good:
jamescable said:
We do have a custom recovery for A 10
Click to expand...
Click to collapse
Yeah I do know A10 has twrp.
I think A11 has a bootable chinese recovery or something in that area.
I personally am not worried about twrp anymore..
Really have no need for it...
why would this not be working for me? i'm on newest magisk on oneplus 8 pro....android 11 (11.0.2.2.IN11AA)
i loaded a magisk module that is not cooperating so the system UI never starts. i've also tried the "adb wait-for-device shell magisk --remove-modules". still no luck. would love some help. thanks
glhelinski said:
why would this not be working for me? i'm on newest magisk on oneplus 8 pro....android 11 (11.0.2.2.IN11AA)
i loaded a magisk module that is not cooperating so the system UI never starts. i've also tried the "adb wait-for-device shell magisk --remove-modules". still no luck. would love some help. thanks
Click to expand...
Click to collapse
Might try by stating what you installed, kernel etc.
Force your phone off and hold vol +/- when you see the bootloader sign.
Just wait for it to load then reboot
dladz said:
Might try by stating what you installed, kernel etc.
Force your phone off and hold vol +/- when you see the bootloader sign.
Just wait for it to load then reboot
Click to expand...
Click to collapse
I have tried the above (boot to safe mode) but nothing happens but system ui crash on start
I'm on stock oneplus 8 pro with 11.0.2.2.IN11AA. Rooted with newest magisk. Stock kernel. Had viper4android working stable.
I installed renovate ice in magisk. It installed ok but lost mobile data. So i uninstalled renovate ice. .. Rebooted. Then installed renovate ice again. Now all i get on boot is system UI error and cant access anything on the phone. I've also tried flashing the original boot.img to try to disable magisk but that results in same system ui crash/black screen
glhelinski said:
I have tried the above (boot to safe mode) but nothing happens but system ui crash on start
I'm on stock oneplus 8 pro with 11.0.2.2.IN11AA. Rooted with newest magisk. Stock kernel. Had viper4android working stable.
I installed renovate ice in magisk. It installed ok but lost mobile data. So i uninstalled renovate ice. .. Rebooted. Then installed renovate ice again. Now all i get on boot is system UI error and cant access anything on the phone. I've also tried flashing the original boot.img to try to disable magisk but that results in same system ui crash/black screen
Click to expand...
Click to collapse
Ok so you may want to contact rice as they have components in their ROM that can affect system and as such it isn't just so simple as reliving a magisk module.
Furthermore they don't have a full roll back feature when removing the module so changes can remain, one of the reasons I wouldn't use rice, cyberpunk theme if you don't revert back to stock theme before removal for example will cause your stock theme to be lost forever.
Forcing you to reset system via recovery.
The very fact that you can't boot into safe mode suggests to me that there is a deeper issue, it's possible viper has something to do with this but I would guess it's rice.
If it were me I'd wipe system only in recovery and set up your phone again..
If you've tried to boot to safer mode and you've done it right and it's still not working then I'd say start with system, your boot IMG isn't the problem
dladz said:
Ok so you may want to contact rice as they have components in their ROM that can affect system and as such it isn't just so simple as reliving a magisk module.
Furthermore they don't have a full roll back feature when removing the module so changes can remain, one of the reasons I wouldn't use rice, cyberpunk theme if you don't revert back to stock theme before removal for example will cause your stock theme to be lost forever.
Forcing you to reset system via recovery.
The very fact that you can't boot into safe mode suggests to me that there is a deeper issue, it's possible viper has something to do with this but I would guess it's rice.
If it were me I'd wipe system only in recovery and set up your phone again..
If you've tried to boot to safer mode and you've done it right and it's still not working then I'd say start with system, your boot IMG isn't the problem
Click to expand...
Click to collapse
Thank you. I reported my troubles in the rice thread a couple days ago but no responses yet.
I've been doing custom roms for years but this phone is very new to me. I think i can find how to wipe system in stock recovery but after that... How would i proceed to set up my phone again (with no system from the wipe)?
Do you mean i should do "reset system setting" in stock recovery?
... Much appreciated
glhelinski said:
Thank you. I reported my troubles in the rice thread a couple days ago but no responses yet.
I've been doing custom roms for years but this phone is very new to me. I think i can find how to wipe system in stock recovery but after that... How would i proceed to set up my phone again (with no system from the wipe)?
Do you mean i should do "reset system setting" in stock recovery?
... Much appreciated
Click to expand...
Click to collapse
Back up using Google drive or other playstore backup tools (apps)..
glhelinski said:
Thank you. I reported my troubles in the rice thread a couple days ago but no responses yet.
I've been doing custom roms for years but this phone is very new to me. I think i can find how to wipe system in stock recovery but after that... How would i proceed to set up my phone again (with no system from the wipe)?
Do you mean i should do "reset system setting" in stock recovery?
... Much appreciated
Click to expand...
Click to collapse
Yep that's the one then just boot it'll be like a fresh phone
dladz said:
Might try by stating what you installed, kernel etc.
Force your phone off and hold vol +/- when you see the bootloader sign.
Just wait for it to load then reboot
Click to expand...
Click to collapse
Hello sir, when trying that, my phone is still in bootloop...
Rindmann said:
Hello sir, when trying that, my phone is still in bootloop...
Click to expand...
Click to collapse
What module are you having a problem with? If it's rice then it may not work
dladz said:
What module are you having a problem with? If it's rice then it may not work
Click to expand...
Click to collapse
I hope he/she didn't enable cyberpunk theme and then uninstall it. I heard you need to go back to stock theme in settings / customizations enable default theme and then uninstall rice..
TENlll423 said:
I hope he/she didn't enable cyberpunk theme and then uninstall it. I heard you need to go back to stock theme in settings / customizations enable default theme and then uninstall rice..
Click to expand...
Click to collapse
Same thing happened to me.
Maybe they've fixed it now