I have verizon nokia 822 that has been bricked after update. The boot partition seems to be messed up as i get error message no bootable option found. I read that nokia care could restore boot but I get fpu error. I guess jtaging it is the only option to fix it ? Or maybe there is an option that will bypass verification
Related
Hi, I need help with my huawei p9, when I power up and the system start, a screen says Encryption Unsuccessful, and that I should do a factory reset for resume using the phone. I do the cleaning in TWRP and I install fRomFuture - NewWorld V4.1, the installation is performed without errors, but the message remains.
How could resolve this situation?
PS: sorry for my English
I have similar problem
Hi, I have the same thing here, but it has stock recovery, which I can't boot into. I can get to Encryption unsuccessful screen and to fastboot. It is customers phone, he was messing around with SW, and I think he didn't allow oem unlocking, debbugging is disabled aswell I think. I can't flash anything to it, whatever I try I get 'FAILED (remote: command not allowed). Tried force-flashing it via SD card, it gets stuck at Huawei logo. Any thoughts? Or to tell him to use it for smashing nuts?
Motorola Moto X2 USB does not define all that in the loader in the system, TWRP gone, instead there was an inscription:
Invalid boot image size!
failed to validate recovery image
Fastboot Reason: Fall-through from recovery boot mode.
It was established Lineage OS, correctly and properly, Ruth rights absent
I look for the cause in the expanses of the Internet - really nothing.
Who can faced with similar?
bump
have same problem here
and can't install last nightly, says "cant install on top of incompatible data"
drico_649 said:
bump
have same problem here
and can't install last nightly, says "cant install on top of incompatible data"
Click to expand...
Click to collapse
I have a suspicion that the system itself can not enable debugging on USB, but it is impossible to return to the factory settings - no TWRP. ROOT not set there for a new opportunity - a vicious circle..
the root is separated from the rom itself, it's a zip that u flash on top of ROM. but the update doesn't install on top of the same system is weird, since it's the same code.
I had to wipe data, update and then, re-setup my phone. this is boring, since I have almost 200 apps...
One thing i noticed is, on recently versions of Lineage for xt1097 (br variant of xt1095), there is an option under development settings called "update recovery when update system". On cyanogenmod, this installed a recovery made by CM itself, in lineage it does nothing. and since I turned on this option, when I try to go to recovery gave me this same error of yours. when I turn option off, recovery works again.
I think that this option enables some sort of check of recovery partition to update system and/or recovery itself, but since there isn't any recovery in OS package, it can't be installed, neither the recovery nor the rom itself (choosing to install update through system just boots up twrp, and nothing happens, I had to find zip package myself and install, then find the "error 7".)
Continued: set up your smartphone no drivers to devices. Today died system interface - just a black screen, there are sounds, the phone works, but there is no image. Tried other cable, assorted devices to get in close connection - the connection is OK. The problem with the loader has not been solved, everything develops in a poor way.
And so, I have - Smartphone. without bootloader without Root rights, the operating system crashes. The smartphone can be considered a brick! While the solution to the problems found.
Invalid boot image size!
Bush_Jr said:
Motorola Moto X2 USB does not define all that in the loader in the system, TWRP gone, instead there was an inscription:
Invalid boot image size!
failed to validate recovery image
Fastboot Reason: Fall-through from recovery boot mode.
It was established Lineage OS, correctly and properly, Ruth rights absent
I look for the cause in the expanses of the Internet - really nothing.
Who can faced with similar?
Click to expand...
Click to collapse
I also have the same problem but TWRP 3.0.0.0 condor image is only working for my moto e runninig with lineage 14.1.
Soft bricked my Razer 2 getting "fastboot: error: cannot get partition size"
Ok here is my problem, I was trying to root my phone, didnt want a custom rom just root access so I could reenable NFC login. First i think the problem was the cord I was using, the flash would just hang, it would send to the phone but not write to the partition. The only way to stop it was to restart the bootloader but I dont know if I corupted something. Now when I try to flash anything patched image or vanilla it wont work the patched version gives me the error above, and the vanilla install from the manufacturer just hangs when it tries to check the version.
Hi guys,
I have a Microsoft Lumia 820 where the display is broken. That was the reason why I tried to backup my phone - especially the several hundred of contacts. I used for this the WPinternals tool (version 2.9.2) to switch to mass storage mode and save the whole system. Unfortunately something must going wrong, because now the phone is in flash mode and no matter what I`m doing the red screen (flash mode) (photo 1) is always there. If I try a soft reset the same issue occur. I tried also to boot to normal mode, but it doesn`t work. WPinternals shows me the message: "Error: Phone is in an unexpected mode." (photo 2). The same occur when I try to unlock or restore the bootloader. I don`t want to flash the phone because of the contacts on the phone which I really need. Is there anybody out there which can help me in that case?
I`ve tried also the thor2 tool from the Windows Device Recovery Tool to change the state to normal boot via emergency mode, but the same issue occur. As you can see on the attached photo (photo 3) it is "not possible to boot to emergency mode with this version of phone SW." Are there other commands or tools where I can bring my phone back?
Thank you for your help! For me it is really necessary to get all the data from the phone, so every hint is welcome! If you need further information on this case please let me know!
Fred
Hello XDA Community,
I recently purchased a Motorola Edge 20 for just 150€, which seems like a great deal. However, there's a catch: the display shows "Motorola confidential property, not for sale." The device had developer mode on and an open bootloader by default, and some features were still buggy. Since all the hardware components matched the retail version, I decided to try and flash the retail OS to get a more stable system.
I first tried to flash the system via a ZIP file, but I encountered a signature issue, which I now realize was due to my limited knowledge and inexperience in flashing ROMs. Next, I attempted to flash a recovery file that I found online by running the command "fastboot flash recovery recovery.img." The process seemed successful, but it resulted in my device getting stuck in a boot loop.
After more research and troubleshooting, I found a script on XDA forums that I ran with firmware that was supposed to be original, and that got my device back into a boot loop. The recovery.img is not present in that firmware. When I try to boot the phone now, it displays "booting into recovery mode" at the top and then reboots (possibly because the recovery file is broken). I tried other firmware files such as LineageOS and PixelExperience recovery, but I always encountered errors while attempting to upload the recovery file.
While attempting to flash the PixelExperience recovery, I encountered the following error message:
Code:
C:\Users\marti\platform-tools>fastboot.exe flash recovery PixelExperience_Plus_berlin-13.0-20230112-1838-OFFICIAL.img
Warning: skip copying recovery image avb footer (recovery partition size: 0, recovery image size: 100663296).
Sending 'recovery' (98304 KB) OKAY [ 2.377s]
Writing 'recovery' (bootloader) Invalid partition name recovery
FAILED (remote: '')
fastboot: error: Command failed
It appears that the bootloader reports an "Invalid partition name recovery" error. I suspect this might be related to the device being a "confidential property" version of the Motorola Edge 20, which might have a different partition layout or naming convention. The bootloader is still unlocked.
With all this information, I hope that someone can help me understand what went wrong and how to fix this issue. I would appreciate any guidance on flashing the retail OS to my Motorola Edge 20 without causing further problems or finding a compatible recovery file that will allow me to boot the device successfully.
Thank you in advance!
Hi, this problem was because there is no sector named "recovery" in Edge 20. I followed the LintageOS instructions again and got the phone into LintageOS recovery. However, after installing and updating the phone via ADB, I got the phone hard-bricked. Honestly, I don't know why, but I might have broken something much earlier in the process. Tip for future me: prepare in advance.
Sounds like you got your hands on a dev device of some sort. Try making your own update script, follow these instructions (you will need to add a few more script lines depending on your system version):
If for some reason you cannot boot into recovery mode at all, there is a Qualcomm recover tool that I found out about the hard way after bricking my device too. If you plug your phone into your computer and the computer makes a sound that it recognizes a new device then you can probably recover it. I don't remember where to find it since I too found it by chance after desperately searching the internet, so you're on your own for that.
I forgot to mention you can get ROMs on sites like lolinet but I can't guarantee integrity. Also, if it is a dev device then the IMEI might not be valid, so it might be illegal to use or it might not be functional with any SIM card, so careful what you do with it. I don't know how to check for IMEI. Maybe try the RSA tool and input your IMEI there and see if it gives you a software to download (the IMEI can be found on the inside of your SIM tray).