Title says it all
Considering the devices are similar hardware wise (and the US kernel boots properly on the European device) I guess (not validated so far) that the kernel crashes are caused by new kernel parameters that aren't passed by the "old" bootloader and not properly validated on the kernel itself when missing.
For example the Orange kernel has references to parameters which are not defined by the "old" bootloader
androidboot.cid
androidboot.keycaps (previously board_trout.keycaps)
In any case, be extra careful when swapping kernels and most importantly bootloaders between devices ...
Confirmed - hard patching the parameters in the Orange kernel allow it to boot properly on an "old" bootloader.
So be careful ... and I guess those modifications haven't been reviewed very throughfully (they should have been published, too)
{
"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"
}
Related
During device start this bug is visible.
The upper bar is imposed on welcomehead..
Device - polaris,niki.. Rom - oficial wm6.1
How to repair it?
thx
{
"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"
}
no it just does that sometimes
as far as i nkow it does ghamper the devices performance
It is corrected in many unoficial ROMs. Someone means knows
well yes probably but it s at best a minor affliction to winmo os and as it doesnt affect the use of the phone its probably best left alone
I edit ROM and I wish to correct it
then go for it.
You'll find even if you do replace that splash screen (you will find out how to do here even if you dont flash a new rom) that sometimes it will do this anyway.
As jayjay rightly says, its cosmetic and is a windows 6.1 issue. Both my prohpet and polaris do it sometimes, sometimes not.
Hello,
My tablet is very slow because of the lame version of android (4.2.2.). Maybe a new rom would have a positive effect on in. But sadly I didn´t found any custom rom support for that thing .
Maybe someone know more about it. Thats how it look like:
{
"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"
}
Yep - I installed Cyanogen 10 on it
Hi Alecander - I can tell you how I installed Cyanogenmod 10 on it.
Not much improvement, to be honest - but it is CM at least. I did have to go to crazy lengths to make wi-fi work, though (manually invoke wpa_supplicant, etc).
By the way, if you still have it - can you send me the /system/framework/framework.jar file from that tablet (email: [email protected])? In my tablet that file became corrupt, which stopped the stock image from working (that's why I moved to CM10).
Thanks!
I have pressed with this app (https://play.google.com/store/apps/details?id=com.kasitskyi.hiddensettings) Band USA on my Mi4c and now I have no signal in sim1. I live in Europe and don't know what to do. Is there any simple fix for that? I have found few but with other phones like Mi5 and so. Found this (http://forum.xda-developers.com/mi-5/development/xiaomi-mi5-qualcomm-diagnostic-drivers-t3336200)
but really don't know how to do it. I's mentioned lower :
(All you need to do is change the ban_pref* values back to the original, for the Sim-Card you changed it. Set the following values in your phone, for the Sim-Card you disabled em. (By Clicking band mode USA))
please help ...
I have try factory reset and other ROM's also now locked bootloader because of Chinese ROM but waiting for unlock. Is there anything somebody can help ???
Have found this but no luck: http://en.miui.com/thread-340101-1-1.html
{
"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"
}
So i know this will sound weired and unbelieveable but i managed with some exploits in iboot to boot twrp on the iphone 7plus dont be too happy i wont push the needed exploits or bl (i call it MAGDLDR_FOR_IPHONE) to my github soon because im afraid of apple patching it (when a jailbreak comes i will push it)
i will upload the pics to imgur and add the twrp device tree here
IT DOES NOTHING EXEPT BOOT AS SOON AS YOU TOUCH THE SCREEN THE KERNEL CRASHES AND IPHONE BECOMES UNRESPONSIBLE
NO THIS DOESNT MEAN YOU CAN BOOT ANDROID ON AN IPHONE THIS IS WAY MORE WORK AND I DONT KNOW IF I WILL TRY IT
github : https://github.com/J0SH1X/android_device_apple_iphone_7-1
This is opensource but if you like my work consider buying me a beer or two (paypal: [email protected])
{
"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"
}
https: //imgur.com/a/UYZYq
reserved
Lmao...[emoji23][emoji23]
Time to leave earth! ?
nice
As we all now Fortnite has finally come to the Android platform with an exclusive debut on Galaxy smartphones. I have one of the devices compatible with the game (Galaxy s7 edge) and was eager enough to get it. I was taken by suprise though when I ran into the error displayed below. I am running Sac 23's s9 port with a passing Safety Net and Magisk Hide active for Fortnite. After seeing the error, I turned off USB debugging but still ran into the same error.
I get that Epic Games just wants to keep the game free of cheaters, but checking for bootloader status seems taking it too far. Is there any way to hide the fact that I unlocked my bootloader?
{
"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"
}
Screenshot of the error code
https://imgur.com/a/qvTeqcM
Fortnite for Custom ROMs
I also am experiencing the same thing