Database Info

Rom wont boot [S4][H2.15]

Hello,
I tried to install the rom : Candy5 v2.5.3 using TWRP 2.84 (Hboot 2.15, One S4)
The installation is a success but when I reboot the device, it load infinitely (black screen) and nothing happens
I also tried with the candy5 v4.1-skyrocket but the recovery cant extract the file (signature and MD5 off)
I did a full wipe (Dalvik Cache, Cache, System, Factory Data Reset)
To access the bootloader, I need to wait till the battery is empty and then charge the device and press Power+Down.
NB : I'm using the Venom Rom (android 4.1), working good and got a backup file of it. I need a Rom with android 5+ to run a specific application.
Any solution ? I'm kinda a 'newbie' on this and I'm unable to see what's wrong.
Thx
EDIT : I upgrade my TWRP into 3.0.2, same problem

I fixed the problem with :
- Flashing Gapps & SU (just add some apps, I dont think that was useful)
- Flashing boot.img (from candy5)
SColaux

Problem Flashing Omni Rom

Hello,
Since a few days I try to flash the actually Omni Rom on my Xperia XZ.
It didn´t work.
Actually FW: F8331_41.2.A.7.35 (Flash with flashtool)
My method:
- flash AndroPlus v26
- flash twrp
- flash supersu
- flash omni rom
I have the following problems and questions:
- When I use twrp 3.0.2.0 and flash omni rom I have bootloop at omni rom logo (wait>20 min) when I start twrp again it wants a decryption code at start
- When I use twrp 3.0.2.4 --> twrp wants a decryption code at start
- When I use twrp 3.1.0.0 --> twrp wants a decryption code at start
- When I use twrp 3.1.1.0 --> no descryption code is required but I can not wipe dalvik etc.
It is required to flash AndroPlus? It is required to root before flash?
I have no idea what method I have to use to flash omni rom successful.
Please can you help me.
THX

Now I try another Method:
I Flash Androplus kernel and Twrp 3.0.2.4
Than I Flash carbon Rom 5.1.
Flash and wipe success. At the First boot i have to enter a Pin Code for my device.
I didnt set any pin code. When i try a Pin randomly
It says that Pin is correct but dates are corrupted.
Then I Can make a reset but landing finally at the screen with pin Code.
Anyone any Ideas?

You have to wipe internal storage in twrp recovery. Wipe -> erase -> yes. Then flash rom again

[TWRP][BRICK] Motorola Moto G LTE 2013 Peregrine - Fail entering Recovery Mode

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.

[TWRP] [Port] L.R.-Team recovery OMFG-Mod-From Cactus -to -Umidigi-F1

First version shared was twrp 3.2
New version is 3.3.0
***ORIGINAL TWRP is not my work. Only the porting of it to this device. I take no credit for the source.
*** DISSCLAIMER ALLERT***
I started having issues with encryption coming back to enforcing when using the Ported Team LR TWRP 3.3
Did not have trouble yet with OMFG-Mod version.
Also @ghost45 has made a build of twrp 3.3.1 for F1. It works good as well
https://forum.xda-developers.com/showpost.php?p=79651368&postcount=49
--- all versions give trouble of loosing IMEI when using the remove force encryption patch I suggest below. Left logs with @Zackptg5 .
**May need more testing**
-decryption is broken
-MTP is working
-ADB is working
****--Advanced menu items are not correctly on 3.2 version.
-- Some of the advanced menu was fixed in 3.3.(install root is working)
- Advanced menu has extra features.(all from source twrp)
-- install magisk (currently has V17 on OMFG V19 on LR TEAM)
-- patch dm-verity and force encrypt remove.zip. ( personally I prefer the universal dm-removal patch from xda)
-- Remove system password, (from original dev, I have not tested)
--
--Install (basic directions only)--details may be added later if needed
Open zip and fastboot flash the recovery image if bootloader is unlocked.
or
Open zip , then open scatterfile (scatter file in test 1 has issue, updating it in next test )with sp-flashtool , select download
--First boot into TWRP will give errors for unable to mount /data. This is from the force-encryption.
- When boot into TWRP, select wipe -> format type 'yes' to format data
- When format is done, return to TWRP home page, select reboot -. recovery
--Now Patch device so no longer forces encryption
-- Use built in feature from 'Advanced Menu' or use the following directions--Fails to unpack boot. (current zip used is not compatible with system-as-root boot.img)
-To remove this I use 'Disable_Dm-Verity_ForceEncrypt' from
-- https://github.com/Zackptg5/Disable_Dm-Verity_ForceEncrypt -- currently based on magisk V19.2
-Download from the "Clone or Download" button on the above linked Github Page.
-Unzip the downloaded file. You will have a folder with same name as the zip package. Browse inside this folder, select all files and zip them.
-Put this new zip file onto your phone. ( Hay notice the MTP function on this TWRP works)
- in stall the zip like any normal twrp package.
--Next Install Magisk
--Use Built in Root Option from 'Advanced Menu' to use Magisk V19 or the following direction
- Goto the releases page of magisk github page. ==>LINK
- Download latest Magisk zip , Put file to phone, Install.
-- Download Folder For TWRP Ported from OMFG-Mod
https://www.androidfilehost.com/?w=files&flid=294886
-Screenshots.
- Ported OMFG-MOD gold Button TWRP V3.2
- Ported Team LR TWRP 3.3 standard Button
Attached Below
--Thanks --Mentions
recovery source from [LR TEAM] MIUI
http: //www.miui.com/forum.php?mod=viewthread&tid=19006123&page=1&mobile=2#pid257831639
link is newer version from ported recovery. They updated recently. Next port may use newer base as well.

hello @ColtonDRG. Long time.
I see you posted in umidigi forum that bootloader is not checking signature. So you CAN flash images with flashtool without unlocking. Is that correct.?
I have based the above install guide on that fact that you CAN.
But the first twrp posted by "ghost45" says no it must be unlocked.
edit:
I should be able to verify later today or this weekend, when my order arrives.
OK, verified, when i used flash tool and put twrp on phone before unlocking bootloader, on reboot I was stuck in "RED" status for boot loader. So must unlock

Flash this zip to remove the AdupsFota app
this is the update app. You will not be able to install OTA when rooted and twrp anyway, And if an OTA comes you will get stuck in recovery bootloop. So this flash file will rename the 2 apk related to OTA download and Force reboot that supposed to install that update.

Reserved
Will keep this post for working on issues .
Right now , I discovered after playing with the built in dm verity patch and root install lead imei's getting erased.
Restored the full rom with flash tool fixed, will update process as necessary
Restarted from the top again.
--1 Full stock rom flashed with sp flash tool.
--2 Twrp flashed in flash tool
--3 format /data, reboot recovery
--4 use mtp to copy Disable_Dm-Verity_Forceencrypt to phone
--5 flash the decrypt zip. And at the end of flash the output log showed 'failed to mount /nvdata file not exist'
*** Waiting for input from the Patch dev. Others on his xda thread with MTK have had similar trouble***
--6 use mtp , put stock recovery file on phone. Image flash stock recovery, reboot recovery, do factory reset in stock recovery. This fixed the /nvdata error.
--7 sp flash twrp again, use built in 'install root' option from advanced menu.
Bam all done

New Umidigi f1 recovery 3.3.1 test2 is pubblished.
Test this one if all is corrected...
http://www.mediafire.com/file/1emy4tk1gvnkj96/recovery-twrp-3.3.1_Umidigi_F1_test_2.rar/file

ghost45 said:
New Umidigi f1 recovery 3.3.1 test2 is pubblished.
Test this one if all is corrected...
http://www.mediafire.com/file/1emy4tk1gvnkj96/recovery-twrp-3.3.1_Umidigi_F1_test_2.rar/file
Click to expand...
Click to collapse
Thank you, this one has no displayed errors.
I have question though.
Do you know how to make system be mounted as /system instead of /system/system ?

Hey, buddy. Good to see you on the forums again. When I picked up this device I wondered if anyone from the R1 HD days would also be on it. I seem to have misplaced mine but I'll find it eventually, send me a DM if you wanna talk about it. I'm not 100% sure about this, but the bootloader verifying signatures might have been patched in because I don't remember mine doing that when they first came out. Of course even if it does, SPFT is still useful for unbricking and downgrading, but I really doubt UMIDIGI will patch out the unlock option like BLU did.

Hello again, all. I've been working on my UMIDIGI F1 again and after flashing the most recent firmware update using SPFT and trying to flash TWRP again I realized that something that changed in the latest firmware update has broken all of the existing TWRP images. Now the bootloader screen hangs for a while, sometimes a green bar appears at the top of the screen briefly, and then the phone reboots into Android. It is perhaps worth noting that when I tried to flash the upgrade in download only mode it just complained about the partition layout or something like that and then bailed, telling me to use the Format and Download option instead. I didn't do that because UMIDIGI told me not too and instead opted to try the Firmware Update option, which did work. I'm going to try to downgrade (hopefully I don't get bricked from downgrading preloader, efuses, etc) but I am a bit concerned about what has changed. Stock recovery still boots OK so it would seem to me that the bootloader isn't just completely borked, but either way it's a bit alarming that an OTA caused the custom recoveries we have to go kerplooie.

ColtonDRG said:
Hello again, all. I've been working on my UMIDIGI F1 again and after flashing the most recent firmware update using SPFT and trying to flash TWRP again I realized that something that changed in the latest firmware update has broken all of the existing TWRP images. Now the bootloader screen hangs for a while, sometimes a green bar appears at the top of the screen briefly, and then the phone reboots into Android. It is perhaps worth noting that when I tried to flash the upgrade in download only mode it just complained about the partition layout or something like that and then bailed, telling me to use the Format and Download option instead. I didn't do that because UMIDIGI told me not too and instead opted to try the Firmware Update option, which did work. I'm going to try to downgrade (hopefully I don't get bricked from downgrading preloader, efuses, etc) but I am a bit concerned about what has changed. Stock recovery still boots OK so it would seem to me that the bootloader isn't just completely borked, but either way it's a bit alarming that an OTA caused the custom recoveries we have to go kerplooie.
Click to expand...
Click to collapse
There is a newer twrp that has been released on 4pda.net that supposed to work on newest firmware release.
And downgrading with flashtool should work. Again need to use firmware upgrade option.

mrmazak said:
There is a newer twrp that has been released on 4pda.net that supposed to work on newest firmware release.
And downgrading with flashtool should work. Again need to use firmware upgrade option.
Click to expand...
Click to collapse
Downgrading worked. I couldn't find the newer TWRP version you were referring to and the website you mentioned redirects to a bunch of scammy crap.

ColtonDRG said:
Downgrading worked. I couldn't find the newer TWRP version you were referring to and the website you mentioned redirects to a bunch of scammy crap.
Click to expand...
Click to collapse
We have the twrp file copied to telegram group also. I'm stuck on mobile, or I would just copy the twrp here.
UMIDIGI
UMIDIGI unofficial TG group
https://t.me/UMIDIGI

Disable_Dm-Verity_ForceEncrypt failed
Hello, I'm trying to patch my F1 using the Disable_Dm-Verity_ForceEncrypt, but am stuck with an error "Dumping/splitting image failed. Aborting..." This occurs when I try using the Install from twrp. Has anyone encountered this issue before? I have done a wipe, and also tried installing Magisk (which installs fine).

Phone boots to CrashDump mode, cannot enter Fastboot Mode and stuck in TWRP splash

Hi guys,
I have made a bad decision in trying to clean install Lineage OS 17 and now my phone only goes to QUALCOMM CrashDump Mode or gets stuck in the TWRP splash screen.
I cannot even make it start in Fastboot mode.
What I did was:
- Install TWRP 3.3.1-4
- Wipe EVERYTHING from the advanced wipe option
- Sideload Lineage OS 17
- Reboot into recovery to discover that I had the OnePlus recovery back
- Install TWRP 3.3.1-4 again
- Reboot into recovery
- Install GApps
- Restart phone
- Get into infinite boot load of Lineage OS which after a couple of auto restart would take me to TWRP
- Panic
- Wipe EVERYTHING again
- By mistake sideload TWRP 3.3.1-4 instead of Lineage OS 17
- Reboot into recovery
- Get stuck in the splash screen of TWRP
- Reboot into Fastboot
- Get stuck in the OnePlus logo Fastboot Mode
- Somehow turned off the phone
Is there anyone that can help me please?

Flash fastboot stock ROMs
or
Use MSM Download Tool

Look here!
https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109

What do you think about starting with reading the flashing instructions before you attempt flashing ROM's. That would've prevented all the troubles you are experiencing.

Mr.FREE_Bird said:
What do you think about starting with reading the flashing instructions before you attempt flashing ROM's. That would've prevented all the troubles you are experiencing.
Click to expand...
Click to collapse
I managed to reset the device following the guide linked above but I am not able to have a Custom ROM yet.
It doesn't look like there is any "official" guide as I've seen many and each of them gives different instructions!
Ultimately what I found (and tried with no success) is:
- Have the phone automatically update to stock (Oxygen OS 9.0.9) after the reset mentioned above
- Boot into TWRP 3.3.1-14
- Wipe => Format Data: "yes"
- Reboot into TWRP 3.3.1-14
- Flash Stock ROM Oxygen 22 OTA 040 (android 10)
- Flash TWRP 3.3.1-14 installer
- Reboot to recovery
- Flash Stock ROM Oxygen 22 OTA 040 (android 10)
- Flash TWRP 3.3.1-14 installer
- Wipe => Advanced Wipe => Data and Dalvik/ART Cache
- Flash TWRP 3.3.1-14 installer
- Reboot to recovery
- Flash OpenGApps arm64 10
- Reboot to system
After this the phone automatically boots into Fastboot Mode, there is no way to make it try and load the OS.
If you have any better guide, can you please tell me where I can find it?
Thanks

NamingIT said:
I managed to reset the device following the guide linked above but I am not able to have a Custom ROM yet.
It doesn't look like there is any "official" guide as I've seen many and each of them gives different instructions!
Ultimately what I found (and tried with no success) is:
- Have the phone automatically update to stock (Oxygen OS 9.0.9) after the reset mentioned above
- Boot into TWRP 3.3.1-14
- Wipe => Format Data: "yes"
- Reboot into TWRP 3.3.1-14
- Flash Stock ROM Oxygen 22 OTA 040 (android 10)
- Flash TWRP 3.3.1-14 installer
- Reboot to recovery
- Flash Stock ROM Oxygen 22 OTA 040 (android 10)
- Flash TWRP 3.3.1-14 installer
- Wipe => Advanced Wipe => Data and Dalvik/ART Cache
- Flash TWRP 3.3.1-14 installer
- Reboot to recovery
- Flash OpenGApps arm64 10
- Reboot to system
After this the phone automatically boots into Fastboot Mode, there is no way to make it try and load the OS.
If you have any better guide, can you please tell me where I can find it?
Thanks
Click to expand...
Click to collapse
Hold on, what exactly do you want to achieve?
You want to flash LineageOS 17.0 right? I see, just like your first attempt, a couple of things going wrong.
This should work.
● Backup all your data.
● Make sure you have the latest OOS Pie Stable installed on both A and B slots.
● Download the latest LineageOS 17.0 build and Gapps for Android 10.
● Boot to TWRP.
● Wipe data and dalvik cache.
● Flash the ROM zip followed by the TWRP installer zip.
● Reboot to recovery.
● Flash Gapps (if you need Google Services etc).
● Reboot to system.
● Go trough the setup and after that you can reboot to TWRP again to flash Magisk if you need root.
This should work. :good:

Mr.FREE_Bird said:
Hold on, what exactly do you want to achieve?
You want to flash LineageOS 17.0 right? I see, just like your first attempt, a couple of things going wrong.
This should work.
● Backup all your data.
● Make sure you have the latest OOS Pie Stable installed on both A and B slots.
● Download the latest LineageOS 17.0 build and Gapps for Android 10.
● Boot to TWRP.
● Wipe data and dalvik cache.
● Flash the ROM zip followed by the TWRP installer zip.
● Reboot to recovery.
● Flash Gapps (if you need Google Services etc).
● Reboot to system.
● Go trough the setup and after that you can reboot to TWRP again to flash Magisk if you need root.
This should work. :good:
Click to expand...
Click to collapse
I have done exactly what you said. This time I was able to make the Lineage OS load but shortly after it gave me an error saying that "Android Setup keeps stopping" without that the wizard even starts.
I read online that in some cases you need to do a minimal setup before installing the GApps so I will try like that.
Definitely I got 1 step further though, thanks!