I changed the Splash Screen via twrp wrongly, and the smartphone restarted in download mode with this message "Invalid boot image header can't get fdt download mode!!
I tried to solve the problem by reinstalling the original boot image. I installed the file (boot image) from an unofficial website, and the smartphone had other problems. (See attachments 1, 2, 3). So I downloaded the original rom from the sammobile site, extracted the boot image (attachment 4) and installed it via twrp. (see attachments 5, 6, 7, 8) Then the smartphone went into bootloop.
How to solve?
Sorry for translation errors, English is not my native language.
Re-flash STOCK ROM to get rid off of all mods you applied so far.
Related
Hi all,
Yesterday,I have tried with the help of internet to upgrade my oneplus X phone to CM 13. Below are the steps followed,
1. Downloaded TWRP image file,"UPDATE-SuperSU-v2.46","open_gapps-arm-5.1-stock- 20160108","cm-13.0-20160108-jgcaap-bacon" files from internet
2. Enabled Developer Option from settings
3. Rebooted with boot loader
4. Used " Fastboot boot twrp.img " command
5. Installed "UPDATE-SuperSU-v2.46" and "open_gapps-arm-5.1-stock- 20160108" files successfully.When am trying to install "cm-13.0-20160108-jgcaap-bacon",i got error message as ":Error executing updater binary in zip '/sdcard/cm--13.0-20160108-jgcaap-bacon'".
Later i tried again but no luck. I tried in internet and changed versions of CM 13,but still same issue exists.Then i thought of stopping this and rebooted to system.Then i got a notification as "NV partition is invalid".Later nothing is working in my mobile.Not able to open my gmail,playstore etc. I did factory reset then also same thing happens.
Please help me out.
devinaren said:
Hi all,
Yesterday,I have tried with the help of internet to upgrade my oneplus X phone to CM 13. Below are the steps followed,
1. Downloaded TWRP image file,"UPDATE-SuperSU-v2.46","open_gapps-arm-5.1-stock- 20160108","cm-13.0-20160108-jgcaap-bacon" files from internet
2. Enabled Developer Option from settings
3. Rebooted with boot loader
4. Used " Fastboot boot twrp.img " command
5. Installed "UPDATE-SuperSU-v2.46" and "open_gapps-arm-5.1-stock- 20160108" files successfully.When am trying to install "cm-13.0-20160108-jgcaap-bacon",i got error message as ":Error executing updater binary in zip '/sdcard/cm--13.0-20160108-jgcaap-bacon'".
Later i tried again but no luck. I tried in internet and changed versions of CM 13,but still same issue exists.Then i thought of stopping this and rebooted to system.Then i got a notification as "NV partition is invalid".Later nothing is working in my mobile.Not able to open my gmail,playstore etc. I did factory reset then also same thing happens.
Please help me out.
Click to expand...
Click to collapse
Hello,
You need to follow instructions and download the zip file from this thread. CM13 for OnePlus X
Also bacon is oneplus one, and oneplus x is onyx. So on the previous attempt, you downloaded a wrong file.
Good luck!
-Vatsal
i tried installing a theme pack from substatum . it got stuck in boot animation (not a boot loop). how to resolve the issue.
thank you
Flash the stock image with MiFlash. You can choose to keep user data. Instructions here:
http://en.miui.com/thread-807252-1-1.html
Note: I only got flashing to work by putting the extracted ROM folder on drive C.
Hi everyone,
I had a big iussue with my phone (Motorola X10T39).
I installed LineageOS 14.1, and I recently updated it at the version 14.1-20180908.
All worked fine, but after the update I lost root privilege.
After that, I updated my TWRP recovery from the version 3.1.0-0 to the version 3.2.3-0, flashing the image(.img) in recovery mode.
The file I flashed was correct, and the phone still boot properly.
But when I turn on the phone in fastboot mode and try to select recovery I get error:
"Invalid boot image size! failed to validate recovery image Boot failed"
What can I do to fix it?
Thanks
silencefalls said:
Hi everyone,
I had a big iussue with my phone (Motorola X10T39).
I installed LineageOS 14.1, and I recently updated it at the version 14.1-20180908.
All worked fine, but after the update I lost root privilege.
After that, I updated my TWRP recovery from the version 3.1.0-0 to the version 3.2.3-0, flashing the image(.img) in recovery mode.
The file I flashed was correct, and the phone still boot properly.
But when I turn on the phone in fastboot mode and try to select recovery I get error:
"Invalid boot image size! failed to validate recovery image Boot failed"
What can I do to fix it?
Thanks
Click to expand...
Click to collapse
Try these steps in order, stopping if a particular works.
- Ensure you installed the correct TWRP image for Peregrine, not for Falcon.
- Try entering fastboot mode manually, if you didn't already try to: Turn off the cell phone, then press and hold the Volume Down button for couple of seconds and while still holding Volume Down button press the Power button for a little bit and then release both buttons at the same time.
- If you updated TWRP with the Official TWRP app, try flashing it manually in fastboot mode: fastboot flash recovery TWRP image name, copied exactly. If you did flash it manually, try installing via the Official app.
- Make sure your downloads for both the Rom and TWRP image are not corrupted - re-download with md5 sum checks and re-flash with verification.
- Backup all your data (including on SD Card) and clean flash TWRP & the rom again (i.e., wipe System, cache, Dalvik cache and format/wipe Data - important).
- If issue persists, re-flash the previous version of the TWRP or rom, depending on which one is the culprit, and report to developer.
silencefalls said:
Hi everyone,
I had a big iussue with my phone (Motorola X10T39).
I installed LineageOS 14.1, and I recently updated it at the version 14.1-20180908.
All worked fine, but after the update I lost root privilege.
After that, I updated my TWRP recovery from the version 3.1.0-0 to the version 3.2.3-0, flashing the image(.img) in recovery mode.
The file I flashed was correct, and the phone still boot properly.
But when I turn on the phone in fastboot mode and try to select recovery I get error:
"Invalid boot image size! failed to validate recovery image Boot failed"
What can I do to fix it?
Thanks
Click to expand...
Click to collapse
This thread is quite old (around 2 years old). But nevertheless, I am sharing my experience so that it may help someone facing similar problem. I have a Moto G 1st Gen Falcon which was running Lineage OS 14.1 based on Android 7.1.2. I was planning to update it to Android 10 based Unofficial Lineage OS. I downloaded latest TWRP zip to update existing TWRP. I rebooted into TWRP and flashed the zip. It installed perfectly. Then to check it attempted to reboot into recovery. But it instead went to fastboot mode with the error "Invalid boot image size! failed to validate recovery image Boot failed". I tried botting into recovery but was not working. I tried flashing through adb a different file but it was not working. Then what worked was booting into recovery using the command Fastboot boot recovery recovery.img. After that I was able to flash Android 10 and now everything is working perfectly.
Hello,
I'm trying to install lineage-15.1-20180918 on my new (second hand) Google Pixel (sailfish). It came with Android 7.1.0 (NDE63H, Oct 2016) pre-installed.
No mater what I try to do, after installing Lineage zip file, I always get a warning saying that there is no OS. When I try to reboot to System, I am stuck in a boot loop between a screen saying that I should lock the bootloader and another one displaying the Google logo.
General information about device and softwares used
I run Debian on the PC that is used for the install, adb (v 1:7.0.0+r33-1) and fastboot (v 1:7.0.0+r33-1) are installed.
I got the Lineage zip from there (the shasum is good).
I got the TWRP image from there (v 3.2.3-1).
What I did
I followed the official howto there.
I have unlocked the bootloader, can boot into the TWRP recovery.
TWRP is launched via
Code:
fastboot boot twrp-3.2.3-1-sailfish.img
I did "Format Data", then "Advanced Wipe" (selected everything and wiped).
Then
Code:
adb push lineage-15.1-20180918-nightly-sailfish-signed.zip /sdcard/
(Note that I first tried to sideload both this zip and the suaddon one, given that it didn't seem to work, I wiped everything out again and went with the adb push method)
And, finally, went back to the "Install" menu, selected the zip and launched the install process (without checking the "Verify signature checkbox").
I managed to restore the initial backup created with TWRP, the system booted normally. I then tried a LOS install again and got stuck into a boot loop again.
Problem
At the end of this process, when offered with a swipe gesture to reboot, there is a warning saying that no OS is installed. Swiping to reboot leads to the reboot loop described above.
Any idea on what I can do to fix this issue?
Huge thank you in advance!
Have you tried installing the latest stock ROM first? There may be an incompatibility with other parts of the 7.1.0 ROM, like the modem, etc.
post-mortem said:
Have you tried installing the latest stock ROM first? There may be an incompatibility with other parts of the 7.1.0 ROM, like the modem, etc.
Click to expand...
Click to collapse
I did not. But there were other issues as well (I used outdated version of adb and fastboot), I followed the instructions there (due to the stupid rule for new users, I can't post a direct link to it) old.reddit.com/r/LineageOS/comments/9h0aqy/cant_install_lineage15120180918_on_a_google_pixel/e6nbqg6/ and it worked
Please Help- device stuck in bnoot
Current status:
Stuck in bootloop
Fastboot loads ok, can supposedly flash recovery_ramdisk & system
TWRP doesn't load after flashing recovery (or recovery_ramdisk with EMUI version) - I get "load failed" error screen
EMUI8 was probably not completely installed
Initial condition
Honor 6X w/ stock EMUI 5.1 (Nougat)
Traceback
Goal was to install LineageOS 15.01.
This is what I tried:
Unlocked bootloader (&wiped device)
EMUI8 was a pre-requisite, so followed this guide to upgrade
Ran script in guide, which loaded twrp followed by EMUI update screen (as expected)
EMUI update ran for a while, restarted (I think) at least once, but then showed failure screen
Tried rebooting- no system, stock recovery. (fastboot still loaded fine)
Couldn't install TWRP or use script anymore - after some research looked like this was because boot directories changed in Android 8 (recovery -> recovery_ramdisk)
Was able to install EMUI8 version of TWRP, but unable to flash rom or rerun update script (it used recovery2 partition, apparently changed to erecovery_ramdisk, which I couldn't flash to)
loading TWRP was unreliable, worked sometimes and didn't other times
Somewhere around here it seems like I deleted stock recovery (erecovery) while trying various workarounds
Tried installing ElementalOS
The included TWRP loaded, ROM Installation seemed to work but got error in the end (don't remember details)
rebooted device - can no longer boot to recovery ( Error screen: "Func no: 11 (recovery image) Error no: 2 (load failed!))
device stuck in bootloop and Flashing recovery_ramdisk/recovery has no effect!
can still enter fastboot without any problems
I'm hoping there's some way to recover to fix the recovery/system partitions so I can upgrade or at least revert to stock ROM!
Any help will be greatly appreciated
SuperSpasm said:
Please Help- device stuck in bnoot
Current status:
Stuck in bootloop
Fastboot loads ok, can supposedly flash recovery_ramdisk & system
TWRP doesn't load after flashing recovery (or recovery_ramdisk with EMUI version) - I get "load failed" error screen
EMUI8 was probably not completely installed
Initial condition
Honor 6X w/ stock EMUI 5.1 (Nougat)
Traceback
Goal was to install LineageOS 15.01.
This is what I tried:
Unlocked bootloader (&wiped device)
EMUI8 was a pre-requisite, so followed this guide to upgrade
Ran script in guide, which loaded twrp followed by EMUI update screen (as expected)
EMUI update ran for a while, restarted (I think) at least once, but then showed failure screen
Tried rebooting- no system, stock recovery. (fastboot still loaded fine)
Couldn't install TWRP or use script anymore - after some research looked like this was because boot directories changed in Android 8 (recovery -> recovery_ramdisk)
Was able to install EMUI8 version of TWRP, but unable to flash rom or rerun update script (it used recovery2 partition, apparently changed to erecovery_ramdisk, which I couldn't flash to)
loading TWRP was unreliable, worked sometimes and didn't other times
Somewhere around here it seems like I deleted stock recovery (erecovery) while trying various workarounds
Tried installing ElementalOS
The included TWRP loaded, ROM Installation seemed to work but got error in the end (don't remember details)
rebooted device - can no longer boot to recovery ( Error screen: "Func no: 11 (recovery image) Error no: 2 (load failed!))
device stuck in bootloop and Flashing recovery_ramdisk/recovery has no effect!
can still enter fastboot without any problems
I'm hoping there's some way to recover to fix the recovery/system partitions so I can upgrade or at least revert to stock ROM!
Any help will be greatly appreciated
Click to expand...
Click to collapse
Well when bricked the first thing you should try to do is flash TWRP. Which isn't working now? Can you somehow re flash and boot into TWRP? What TWRP are you using. Please try this one and let me know if it boots.
https://mega.nz/#!a81EDZAR!2-9yPFh3reghkGcfSl3nRIJhHGkP8fqDsgUG66ewjkk
Another thing you could try is Dload method. It requires an SD Card. Extract the Update.zip you downloaded on your PC and now create a Folder called Dload in your SD Card and copy the contents of the extracted zip into the folder. Put SD Card in phone and Hold all three buttons i.e. Power and Volume Up & Down at the same time. Firmware should start flashing. Once it finishes, while device is booting, press and Hold Power and Volume Up to boot into eRecovery and Perform a Wipe Data/Factory Reset. The Wipe Cache and reboot. If this works, then lemme know and then I'll help you flash a Custom ROM.
Mannan Qamar said:
Well when bricked the first thing you should try to do is flash TWRP. Which isn't working now? Can you somehow re flash and boot into TWRP? What TWRP are you using. Please try this one and let me know if it boots.
removed because I don't have link posting permission
Another thing you could try is Dload method. It requires an SD Card. Extract the Update.zip you downloaded on your PC and now create a Folder called Dload in your SD Card and copy the contents of the extracted zip into the folder. Put SD Card in phone and Hold all three buttons i.e. Power and Volume Up & Down at the same time. Firmware should start flashing. Once it finishes, while device is booting, press and Hold Power and Volume Up to boot into eRecovery and Perform a Wipe Data/Factory Reset. The Wipe Cache and reboot. If this works, then lemme know and then I'll help you flash a Custom ROM.
Click to expand...
Click to collapse
Thanks for the reply
Unfortunately TWRP doesnt boot (tried flashing the image you posted, same error screen- image below)
Dload method- I can't boot into erecovery atm- not sure if it's wiped or just can't be reached.
Also- the EMUI8 update I downloaded contained 3 zips- update.zip, update_all_hw.zip, and update_data_public.zip. do I only need the update.zip? (I can't boot into erecovery anyway, so it's a moot point until I do)
Image: (remove space, forum won't let me post images)
http s://i.imgur.com/tFUKDOC.jpg
SuperSpasm said:
Thanks for the reply
Unfortunately TWRP doesnt boot (tried flashing the image you posted, same error screen- image below)
Dload method- I can't boot into erecovery atm- not sure if it's wiped or just can't be reached.
Also- the EMUI8 update I downloaded contained 3 zips- update.zip, update_all_hw.zip, and update_data_public.zip. do I only need the update.zip? (I can't boot into erecovery anyway, so it's a moot point until I do)
Image: (remove space, forum won't let me post images)
http s://i.imgur.com/tFUKDOC.jpg
Click to expand...
Click to collapse
Ok the SW you downloaded is NOT a Dload rom, plus you do not enter eRecovery to flash it. Use the "force" method by pressing and holding all three buttons on power up.
Download a rom from here :-
https://androidhost.ru/
Also instructions are in the zip.
Sparkrite said:
Ok the SW you downloaded is NOT a Dload rom, plus you do not enter eRecovery to flash it. Use the "force" method by pressing and holding all three buttons on power up.
Download a rom from here :-
Also instructions are in the zip.
Click to expand...
Click to collapse
Tried downloading a rom from androidhost.ru- it had the update folder structure described,
and I put the unzipped dload folder into microSD root like the instructions said.
But pressing vol up+down+power doesn't load any update screen for me.
It just goes to bootloop again.
Is there anything else I can try?
Thanks