Recently, I found that when the kernel panic occur, Andorid will reboot itself.
This type of reboot will skip the T-Mobile screen and directly load into the OS.
It is extremely faster than the normal reboot option in most of the rom in the world.
Can anyone write a script that force the kernel panic occur and make the phone reboot?
Booker-T said:
Can anyone write a script that force the kernel panic occur and make the phone reboot?
Click to expand...
Click to collapse
That sounds just too awesome
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Man, you were always one of my favorite wrestlers.
Booker-T said:
Recently, I found that when the kernel panic occur, Andorid will reboot itself.
This type of reboot will skip the T-Mobile screen and directly load into the OS.
It is extremely faster than the normal reboot option in most of the rom in the world.
Can anyone write a script that force the kernel panic occur and make the phone reboot?
Click to expand...
Click to collapse
Why would you need to skip it when you're rooted?
why would you want to reboot in the first place?
Dunno if it will work with android, but use gscript to run (you can test it at a terminal first)
su
cat /dev/zero > /dev/mem
or
su
cat /dev/urandom > /dev/mem
use at your own risk, yadda ydaaa
makes the Kernel go into a panic, well it does on some distro's
domenukk said:
why would you want to reboot in the first place?
Click to expand...
Click to collapse
I don't know how you're phone operates but I know with mine, if I leave it on for a week, it's not as fast as it would be after a reboot. Then again, it could be JUST my phone that does that.
Ace42 said:
Why would you need to skip it when you're rooted?
Click to expand...
Click to collapse
Because my SD card is becoming bad, sometimes the EXT partition cannot be identified when I have normal reboot. This will make the apps corrupt and I have to nandroid restore to fix it.
However, the kernal panic reboot will skip the SD card scanning step that can prevent the SD card loading fail.
Related
after installing android on my orbit2 [polaris],according to this post : http://forum.xda-developers.com/showthread.php?t=1120923
recently my phone goes crazy and nothing work ! camera ,wifi, and calling , not work and today phone signal is cut ! first i install android on this phone, everything good but i don't know why it goes to this
0.recently i just see this error "the application google services framework (process com.google.process.gapps) has stopped unexpectedly. please try again - force close" and everything not WORK !!!! why ?
1.how can i reset phone or reinstall android or any possible way to fix this problem!?
2.how can i use new setup files?
3.why there is no "just one" guide to install android on orbit 2?
clean all file on SD Card and put androidinstall.tgz file in SD card "andboot" folder again, reboot and hold the "Volume up" key until it come a boot manual, then select run "7" "3" "1" to install again, and final select "10" boot up.
boot manual reference here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
thanks and just another question
raycho said:
clean all file on SD Card and put androidinstall.tgz file in SD card "andboot" folder again, reboot and hold the "Volume up" key until it come a boot manual, then select run "7" "3" "1" to install again, and final select "10" boot up.
boot manual reference here:
Click to expand...
Click to collapse
thanks alot raycho, it's worked. thanks
and now i want to use the newer version of android, because bluetooth and wifi in old version not worked. you think which version is better ?
read WIKI page > but nothing helped! many of links is broken or not found! how can i install android without haret.exe: because i don't have WM to run exe files !!
Successfully Done
✓ bootloader unlock
✓ TWRP Recovery twrp-merlin-2.8.7-r7.img
All most try all super user
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
but after flash super user zip phone stop work at bootloader warning
same thing happen to me too..plz someone answer.
Prior to flashing supersu.zip, open twrp>advanced>terminal and enter (without quotes) enter the command
Code:
"echo SYSTEMLESS=true>>/data/.supersu"
Now SuperSU would install in systemless mode. The latest betas automatically install in systemless mode (I am using 2.74). Check if now it works.
Broadcasted from Zeta Reticuli
@Gravemind2015 is correct, that is the command needed to make it work... note that since you already tried flashing several SuperSU versions the old way, if it continues to be a problem you may need to reflash the factory images and verify booting prior to trying the mentioned systemless method.
mindjek07 said:
...after flash super user zip phone stop work at bootloader warning
Click to expand...
Click to collapse
I had the exact same issue on my 16 GB xt1540, running stock, fresh 6.0. Trying to root with SuperSU's (over TWRP), several versions up to 2.74, earlier versions down to 2.4 ish... I'd freeze at boot logo every time, after what appeared to successful installs.
After reading somewhere about someone else's luck, I gave 2.65 a go, a version I must not have tried (and one I notice is not on your screen shot), and it worked. I certainly didn't expect it to, and obviously it could be completely coincidental. I'm pretty sure, however, that I did nothing differently on that install to what I had done other times.
HTH
Buena suerte
Love you!!!
You pacified my pain.
My phone battery went off I plugged the charger and it boots me to twrp even though I didn't wish to open it when I press to boot me to system I still end up in twrp window... I also get this noffication
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Au123456 said:
My phone battery went off I plugged the charger and it boots me to twrp even though I didn't wish to open it when I press to boot me to system I still end up in twrp window... I also get this noffication View attachment 5479285
Click to expand...
Click to collapse
Do you want to be able to modify your system partition(including rooting the device) at some point in the future? If so, check the box beside the "never show this screen during boot again" then just swipe the slider at the bottom to allow modifications in the future.
Or
If you do not plan to modify your system partition in any kind of way, tap the "keep read only" button.
This happened to me multiple times, for me it was an error with flashing Treble GSI from google, tho i fixed it by going in fastboot mode/bootloader and on my PC to flash boot, lk, lk2, recovery (official one) and then reboot my phone, but you will delete the TWRP Recovery just so you know.
_________________________________________________________________________________________________________________________
NOTE: I don't know if this will work for you and might brick your device if you don't use correct ROM files...
_________________________________________________________________________________________________________________________
Also if it then boots into Fastboot mode than you can try flashing all files (It will factory reset your phone)
You have to install adb and fastboot on your PC
Commands:
cd *the path to adb and fastboot*
fastboot devices
fastboot flash *what you wanna flash* *filename of the file that you wanna flash*
For Example if you wanna flash boot it will be like ( fastboot flash boot boot.img ) if the filename is with .bin wich most new devices use it will be fastboot flash boot boot.bin
Hope that this helps
A few weeks ago, my hidden Magisk Manager (hidden as "Settings") stopped working. When I try and launch the generic Settings app it sets up, I get the normal FC menu ("Settings keeps stopping") error. I also get it when I open up any app that I previously allowed root access to, but obviously I cannot add new apps superuser access. I also get the FC every time I reboot the phone.
I haven't updated my OnePlus 9 Pro since the ColorOS 12 update came out, as 1) was not a fan, and 2) everything I read said I'd need to wipe the phone to get root back. Needless to say, it's been a while. My phone is currently on the 11.2.10.10.LE15AA version.
This just started happening one day, but I have no idea why. I am not sure what version of Magisk I am on, because I can't open the app. I also tried downloading the latest and installing the APK, but when I launch it, it's says things need to be "fixed" and to reboot. I then get the choice the normal Magisk installer brings up. I tried doing a direct install, but it failed. I also tried to restore the boot image, but it said the backup wasn't found (never seen that either, as I restore images every time I do an OTA).
Not sure what to do at this point. I'm at a complete loss. I would appreciate any help you guys can provide!
Do a LOGCAT to get the very reason why Magisk is not working.
I tried to get it as quickly as possible to minimize clutter, but it's still pretty long. I believe I've found where in the log the FC I captured (by looking for "zygote", but not sure what to make of it. It sounds like a file or something is missing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Doesn't seem like the logcat file got attached.
Oh well, here's a link:
FilePost
filepost.io
Hi all, this is my first time trying to install a custom ROM to my Oneplus 6 phone and I'm stuck at this step:
Everything was fine until I choose "recovery mode" on my device after successfully run the recovery.img on my pc.
It brings me to a page to choose languages, then option of 1. wipe data and cache, 2. advanced, 3. exit.
I'm not sure which step I'd done wrong, I'm also following a video on YouTube:
It was all good but I do not see anything like in 02:50 of the video, my phone boot into this instead:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry I am really new in this, it would be great if I could get any help for what I'd done wrong or is it something different with my phone.
For extra information, my phone is updated to androind 11 firmware.
Thanks,
Phoebe
phoebegoh025 said:
Hi all, this is my first time trying to install a custom ROM to my Oneplus 6 phone and I'm stuck at this step:
Everything was fine until I choose "recovery mode" on my device after successfully run the recovery.img on my pc.
It brings me to a page to choose languages, then option of 1. wipe data and cache, 2. advanced, 3. exit.
I'm not sure which step I'd done wrong, I'm also following a video on YouTube:
It was all good but I do not see anything like in 02:50 of the video, my phone boot into this instead:
View attachment 5809533
Sorry I am really new in this, it would be great if I could get any help for what I'd done wrong or is it something different with my phone.
For extra information, my phone is updated to androind 11 firmware.
Thanks,
Phoebe
Click to expand...
Click to collapse
UPDATE: I solved it by using "fastboot flash boot lineage.....recovery.img" then power off my phone and turn it on, then it shows the lineage recovery page. Then continue to do the copy partition steps and so on.
It's all good now.