I have a Samsung J400M and since the 23rd of May I am trying to solve the error "Could not do normal boot. Invalid Kernel Length". The device was running Android 9 and this error appeared without any explanation.
{
"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"
}
I can only access the device's download mode.
OEM and FRP are locked and I cannot unlock and I cannot identify my binary number.
I tested firmwares and several versions (new and old) of Odin, but so far I have not achieved any positive results.
I tried to solve by FWRP, but I was also not successful, because I believe that with OEM blocked, I can't get anything. Right?
The image below is the Odin screen. That was as far as I could go so far.
Can anybody help me?
How can I unlock the OEM on this device without having access to Android? Any other solution?
hpernaf said:
I have a Samsung J400M and since the 23rd of May I am trying to solve the error "Could not do normal boot. Invalid Kernel Length". The device was running Android 9 and this error appeared without any explanation.
I can only access the device's download mode.
OEM and FRP are locked and I cannot unlock and I cannot identify my binary number.
I tested firmwares and several versions (new and old) of Odin, but so far I have not achieved any positive results.
I tried to solve by FWRP, but I was also not successful, because I believe that with OEM blocked, I can't get anything. Right?
The image below is the Odin screen. That was as far as I could go so far.
Can anybody help me?
How can I unlock the OEM on this device without having access to Android? Any other solution?
Click to expand...
Click to collapse
Unlock the boot loader with fast boot if possible with Samsung phones. If you can flash twrp which I presume you can't, flash RMM bypass zip and hope for the best. Good luck.
Related
Hi,
I never saw this problem
My phone is unlocked (since a year more or less) and I can't install TWRP nor CWM. I tried many tutorials such as all the root methods listed on XDA for this smartphone.
{
"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"
}
Any idea would be really appreciated!
Thanks
There might be a problem with your drivers. You can try uninstalling and reinstalling them. Also, try using fastboot commands manually
Sent from my Mate
unlock again
Thank you. I'd like not to have to relock it as it's already done and rooted. Could you please tell me what drivers to install? I tested many of them (https://i.imgur.com/wBgsezr.png) but it seems I don't have the right ones then.
I'm using Win7 64bits.
Thanks again!
Use adbdriveinstaler and when it's install you can push recovery to add folder and try this command
cd C:/adb
Fastboot flash recovery recovery.img
Change name your twrp or cwm to recovery
Send frome globe
Okay. Here we go
ADB driver installed (https://i.imgur.com/PWrZoHH.png)
Went to flash and... still not allowed.
And in fastboot/rescue mode on my phone it's written PHONE Unlocked.
WTF
BTW, is there any other way to upgrade the phone? Cause every time I go to the software update in the menu i'm told it's up-to-date, but it's not... Android 4.4.2 & EMUI 3.0.
I read about a "local update" but can't find out how to update from the SDcard, I only have OTA.
Bud64 said:
Okay. Here we go
ADB driver installed (https://i.imgur.com/PWrZoHH.png)
Went to flash and... still not allowed.
And in fastboot/rescue mode on my phone it's written PHONE Unlocked.
WTF
BTW, is there any other way to upgrade the phone? Cause every time I go to the software update in the menu i'm told it's up-to-date, but it's not... Android 4.4.2 & EMUI 3.0.
I read about a "local update" but can't find out how to update from the SDcard, I only have OTA.
Click to expand...
Click to collapse
In your screen you have locked bootloader. Unlock againg
Send frome globe
Okay, I sent an email to Huawei, I'll get back in a few days.
Here is the short story. I followed the unofficial method of unlocking bootloader. I did that and managed to install twrp then i flashed CM14. However, it proved to be not working (Stuck at CM Logo). I also noticed that in TWRP it has an error which is E: Failed to mount /persist. So yeah, i revert back to MIUI and relock it. I managed to reflash to 7.1.8.0 global beta but the problem is there are so many bugs like No wifi detected and no sim data making it unusable to do any internet plus brightness isn't working.
So, this is the true problem came. I followed Raaj52's instruction and want to flash the latest Fastboot rom Developer (which is 6.7.29 global) but i got stuck with Unspecified error when i follow Raaj's instruction. When i do miflash and flash in EDL mode, it got stuck with Not enough storage is available to continue. Please help me, i have redmi phone just and want to use it again.
In addition, can someone please explain to me about:
1. Why E: Failed to mount /persist in TWRP happens?
2. Why Wifi cant detect any hotspot and sim card has no service at all?
3. Why do i have Unspecified error when flashing in Fastboot mode?
4. Why do i have Not storage is available to continue error in EDL mode?
Thank you and hope someone can help me.
PS: I use Miflash 20151028, Anz Folder, Unlocked Bootloader folder and Fastboot_edl folder as well as fastboot ROM downloaded. I also post similar thread in http://en.miui.com/forum.php?mod=viewthread&tid=433772&page=1&extra=#pid8058468 in hoping that someone can help me.
P.S: The Device codename is Kenzo (Xiaomi Redmi Note 3 Pro Snapdragon Version) and here is the picture needed for you guys to help me figuring this out.
{
"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"
}
hey, i've been trying to root 920P (S6 Sprint) for whole week now, i've tried everything i found, tried to flash few versions of TWRP, failed at 99%, tried to root directly with CF-Auto root and it fails mid-flash, tried multiple versions of odin, still same results :|
{
"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"
}
it's really weird, I've succesfully flashed 920F (International) without any problem multiple times. I can flash stock rom so it's not hardware's fault. Am i missing some simple newbie step?
{FIXED}
i was missing newbie step like i suspected xDD i forgot to enable oem unlock
what is the solution ?
i have the same problem. what is the solution ?
aLwaYs7Online said:
{FIXED}
i was missing newbie step like i suspected xDD i forgot to enable oem unlock
Click to expand...
Click to collapse
my device is sm920A . it is at&t . i cannot find oem unlocker
Possible Solution to Odin "failed" messaged whilst flashing
Warm greetings to all.
I have previously encountered this problem before, ive tried clearing the cache and formatting with still no luck
Eventually I wanted to try something, I loaded my software I wanted to flash on a USB.
I then used an OTG adapter to connect the usb to my phone. I then booted into the recovery ( I have TWRP) and chose install from external storage. To my surprise it worked.
NOTE: I am not sure if this method will work on stock recoveries. Also if you have an external hard drive it works as well
Also note. My S6 is an international version i believe G925F
Wishing you all the best of luck if I was not able to help
sazid311 said:
my device is sm920A . it is at&t . i cannot find oem unlocker
Click to expand...
Click to collapse
did you enable developer settings?
Yes
A relative brought me his Moto G3 (XT1542) because it did not turn him on, he told me that the device was being updated and turned it off without knowing that something bad could happen, then he wanted to turn it on and send it to the following screen:
{
"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"
}
When "Start" was selected using the power button, the Motorola logo was displayed for a fraction of a second and the following screen appeared:
No matter which option is selected, "Bootloader Log" appears in all.
I have already tried to load the stock firmware but it does not take it, the same error continues.
I already thank you if you can help me solve this, it is already giving me headaches
Sorry for my bad English, I had to translate it because I don't speak that language.
As our phones are old this software may or may not work but give it a try,
https://support.lenovo.com/gb/en/downloads/ds101291
HTH
R1ffR4ff said:
As our phones are old this software may or may not work but give it a try,
hXXps://support.lenovo.com/gb/en/downloads/ds101291
HTH
Click to expand...
Click to collapse
did this work? I am stuck at the same problem
This error is indicative that either the ramdisk or kernel is corrupted. However, this is a soft brick and can be restored by using fastboot mode or RSD-Lite to flash an official firmware package to your device. Doing so will restore the device back to a factory stock state (but will not relock the bootloader if it has been unlocked. But, since relocking the bootloader carries no advantage except warranty related advantages, this is of little consequence). Official firmware packages for the Moto G 2015 can be found here https://mirrors.lolinet.com/firmware/moto/osprey/official/
Select the most current package for your variant. There are numerous guides here on XDA for restoring Moto devices using fastboot or RSD-Lite. The best fastboot guide I have seen is @lost101's tutorial & firmware repo here https://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
(Official firmware is available at either of the above links. Just choose a link and find the most current build for your device.) @R1ffR4ff's earlier post linking the Lenovo Motorola Smart Assistant should also fully restore your device, and is less complicated than manually flashing an official firmware package. As such, the methods outlined in my post should only be used if the Smart Assistant did not do the trick.
So I got the first step, flashing TWRP. But, there's only a version of TWRP for the a10, would this work?
you don't really need twrp for root, just follow this guide
Installation
The Magic Mask for Android
topjohnwu.github.io
imalreadycrying said:
you don't really need twrp for root, just follow this guide
Installation
The Magic Mask for Android
topjohnwu.github.io
Click to expand...
Click to collapse
my phone doesn't show an oem bootloader unlock option
is it grayed out or do you just not see it
imalreadycrying said:
is it grayed out or do you just not see it
Click to expand...
Click to collapse
doesn't exist.
do you have dev options?
imalreadycrying said:
do you have dev options?
Click to expand...
Click to collapse
yes
send me a screen recording if you can, dev options should look like this
{
"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"
}
I have previously tried Kingo/King Root which worked on my KitKat Nabi tablet, I tried that on my a10e it failed. Root checker says there is no root for andr 11 on the a10e
whatever you do, do NOT use kingoroot, it basically installs a outdated version of SuperSU (which isn't liked by the community anymore because the original developer sold it to some random company) and bloats ur system up.
Yep, no OEM bootloader unlock option in dev settings
it may be possibly locked to your carrier. again, you can send me a screen recording or get an unlocked phone
My phone appears to be unlocked already, there is no sign of Verizon still being on here. I have since upgraded phones and the SIM card isn't in anymore.
Do I have to factory reset to fully get rid of the OEM?
i found this youtube video with some quick searching. it's in hindi but you can get the gist of it.
I most certainly dont have to disable automatic time right?
i don't know, after you get the option maybe you can set it back
i followed and nothing happened
did you reboot your phone after the fact?
yep, nothing works