Padfone S - can not load invalid boot image - help - Asus Padfone X and S

hello,
I downloaded Flashify and I install with it TWRP (image), but I think, I downloaded a bad version, because when I restart my phone, It can't load boot screen..
- in 4.4 android I get error message: "error: can not load invalid boot image"
- in 5.0 android I dont get any info, it stops in boot screen..
I tried to change ROM (with full wipe), but it doesn't works (5.0 --> 5.0 --> 4.4 --> 5.0, etc.)
So I cant use my phone... Have you any idea? How I solve this problem? :/
thanks!
(sorry for my bad english..)

When you get into recovery does it look stock with the android there or does it show twrp.
If its not twrp you could use fastboot to try flashing a new recovery and then boot recovery after.
Then you could just reflash the fw you have before.
That could mean that you might have flashed the recovery img under boot.
Because you only restarted your phone and it just came up like black screen.
But what confuses me is you have went to 5.0 to 4.4 somehow and the problem still exists. Im wondering how you did that exactly, is it from backups or fw files from Asus.
If its the asus fw and the problem persists It might be the recovery and you might want to flash a different one.
The 4.4fw to 5.0fw should have flashed stock recovery again and the problem would have been solved. Only if you have used the downgrade fw and bootloader gets relocked
Overall its a weird problem

You could also try to flash cm 12.1 or 13.0 using custom recovery too if the bootloader is unlocked. And it should work just fine then you could go back to stock. You just might want to back up the data partition on stock then restore it after you get back to stock

Related

not-flash-able P7510, help

hi,
i got a P7510 working fine, flashed to AOKP Milestone4 4.0.3 (or 404) ... today i was trying to revert back to stock 3.x, but ODIN couldn't flash all the way, it always stuck somewhere when flashing system.img
i tried many ways, with or without PIT file, no luck ... tried on many different version of stock rom, same problem
it can still go download mode, it can still be flashed to CWM recovery ... but when flash stock rom, it stops ... anyway to put custom rom to the internal memory to flash thrugh recovery?
by the way, if i go CWM recovery, i can mount every partitions except /data ... bcoz the partition is broken? how can i repartition it?
thanks in advanced.
thnx for watching, it is solved by just using another pc ...
weird, but yup, it flashed all the to the end, and phone just reboot itself into setup screen ...

Phone won't install a ROM.

Hi so after updating from the stock zv6 to lollipop update my phone won't install a custom ROM. Every time I try to turn it on it goes straight to TWRP and went I install a ROM or try to load a backup as soon as I hit reboot it goes back to the TWRP page. Amy ideas?
You must flash back, using Flashtool, to zv4, then reroot, then flash newest TWRP. OTA software not included, because they flash every partition of the phone, including the boot loader. Stock roms like zv6 and zv8(lollipop)or AOSP, must be flashed from xda from here on out, because they've been modified to work correctly on zv4 boot loader. TWRP and root access only work correctly with zv4 boot loader.
sent from my LG G3
It sounds like there is no OS installed or it is stuck a reboot-loop. Try pulling the battery out for 10 seconds and if it still goes into twrp you know that it isn't a reboot-loop. When you go to restore a rom and it has the bar that shows the amount of storage does it say "0 MB"? If it does it means that twrp can't mount the storage on the phone thus causing it to not install/reboot. Have you tried side loading a rom via adb? Are you trying to install a rom off of a sdcard? I have seen many issues in the past sdcard related.
If you can please answer the following:
1) What is the message you are getting from twrp (if there is any)?
2) Have you installed a custom kernel and if so witch one?
3) What twrp are you running (the bumped one from xda or from the official twrp site) and what version is it?
4) Have you tried adb and pulling the battery?
If you answer these questions they should be able to tell us all that we need to know in order to help you out.

[CM 13] Recovery didn't work, after trying to update phone too!

When I updated Cyanogenmod to CM13 my recovery stopped working (I turned on "update recovery with system"). I didn't can apply ANY updates from SD card and from PHONE STORAGE too.
To fix it I tried to update CM to 13 from 10-02-2016 to 13-02-2016. But... It didnt ANYTHING happened! It was only black screen. But now I can't turn on my phone! Recovery mode is not turning on too! I have only not working phone with not working recovery when it will turn on too!
I need my phone tomorrow, please, HELP ME! What can I do?!
Recovery: CM13 recovery.
It is not bootloop, I have:
BLACK SCREEN
After Samsung logo.
It is very important, does somebody know what to do?
I have new news:
After turning on I have samsung logo and for about one second Updating System message! Without loading bar . After it of course black screen!
I didn't do any backups of my phone, but I can wipe all data, but I NEED WORKING PHONE!
@tom790
Try flashing this kernel I attached with odin. Next try rebooting to recovery. If you get a working TWRP recovery, then flash the rom you want to use as normal. Please read this guide if you want to use CM13 and avoid common issues.
Same problem here after trying to update to the newest nightly (also with "update recovery with system" on in developer settings) I assume that this function isn't working correctly. The only alternative is as mentioned above - flash kernel+recovery with Odin and make changes afterwards.
I have same problem. I tried to install this kernel above with ODIN but no luck, after sucessful flash logo and black screen. Any other advice or tips? Is there any chance to recover some data from internal card?
And exactly the same issue here. Will try the workaround from the first answer by noppy22.
OK, succeeded. I used ODIN with the kernel tar file from noppy22, put the S2 into download mode (that was still possible, recovery mode couldn't be accessed), flashed the kernel. Phone rebooted automatically into recovery and started (continued?!) with the installation of CM 13.0. And here I realize the issue. The OTA was the nightly of CM 13.0 which I inadvertently chose to be flashed over the running CM 12.1. Bad idea!
Caveats: I see the yellow triangle now which didn't show up before. No problem for me - it's more than 4.5 years old. And there is still the error that "Google play service was terminated" which showed before I triggered the OTA update of CM 12.1.

Twrp bootloop

Hello, I have RR Android 7.1.1, and I want to flash new GlobeRom, but Ive noticed that my recovery dont work(not even show me a splash screen) or twrp load very long and rebooted.
What's the matter? How can I fix this?
did you try to flash recovery zip again?
@covecove1 yea, the old one, and the new, based on marshmallow. Same result ;d

Realme 7 Pro, I have TWRP but Can't Flash Anything

Recently I installed Project Elixir 1.9, for some reason I decided to go to stock rom again, but I couldnt, first my TWRP was reboting all the time, I managed to solve it by installed another version, the problem now is that I cant install any rom, I mean not stock not custom rom because it is stuck on patching system image unconditionally, no matter what ROM i try to pacth, it always get stuck there and reboots TWRP, I've tried with many TWRP, Orange fox and PBRP, different versions of android and I cant do anything...
I even tried to unbrick it with flash tool and with other tools with no luck, anyone has the same problem? Anyone knows how to solve it and get back to custom rom?
As I mention I have access to TWRP and to fastboot, my device is RMX2170
Thanks a lot.

Categories

Resources