Hi,
I'm hoping that someone might be able to help me with my issue. I got my G5 H850 (european) today and got TWRP installed, installed SU and was in the process of installing a custom rom (this one https://forum.xda-developers.com/lg-g5/development/stock-h850-20a-eu-rom-flashable-zips-t3506514)
Was using the TWRP install method and using the LG-H85020A-Flashable.COMPLETE.zip
I suspect my issue occured when I performed a wipe and also completed the 'Format Data' option, where I had to type 'yes' to proceed.
I had installed the ROM and SU but now when rebooting system from within TWRP it just shows this orange warning https://support.google.com/nexus/an...4544340095349-2688197337&p=verified_boot&rd=1 and then boots back into TWRP.
I've tried the Terminal Emulator commands to get out of this and also tried the same thing from withing ADB on my computer.
I can still access TWRP and Bootloader, I can also still use ADB and Fastboot commands from my laptop, my phone is still detected. Because of this i'm sure it is still fixable but i'm at a bit of a loss for what to do as everything i'm trying seems to not be working.
Any help at all will be appreciated. My end goal is to have Stock Nougat installed with Root and TWRP
the orange warning comes from unlocking your device and is ok - because there is no other way for root;
try this: TWRP - Go to Wipe->Format Data. Don’t Swipe to Factory Reset
I had the same (loop), disabled the encryption for /data but didn't wipe it
If you have exsdcard, remove then boot without sdcard. Eventually format internall sdcard.
Related
Hi,
I'm currently trying to install CyanogenMod onto my HTC One X+, but keep running into problems.
I unlocked the bootloader, and installed TWRP v2.8.7.0.
I went into recovery fine, and used "adb push" to push cm-11-20150906-NIGHTLY-enrc2b.zip onto the device and install it through TWRP.
I then tap "reboot" but it always tells me that "No OS Installed", and rebooting into the bootloader to flash the boot.img and erase the cache doesn't seem to fix this issue.
I've tried a few different versions of recoveries, like CyanogenMod's recovery, but still can't seem to get it to install any OS. Always just get stuck on the HTC logo.
Am I missing an important step, or something? Thanks for your time.
hmm...sounds correct. just try it again.
1. boot into bootloader
2. flash the boot.img from the zip you want to install (for cm11 i recommend to flash nik3rs kernel http://forum.xda-developers.com/showthread.php?t=2012320)
3. reboot into recovery
4. select wipe from twrp menu
5. install the zip
6. reboot
why dont you try cm12? much better performance!
.
el-Loko said:
hmm...sounds correct. just try it again.
1. boot into bootloader
2. flash the boot.img from the zip you want to install (for cm11 i recommend to flash nik3rs kernel http://forum.xda-developers.com/showthread.php?t=2012320)
3. reboot into recovery
4. select wipe from twrp menu
5. install the zip
6. reboot
Click to expand...
Click to collapse
Ok, I tried again.
I went into the bootloader and flashed boot.img.
Then went into recovery, and did a factory reset via the wipe menu.
Then used "adb push" to push cm-11.zip to my /sdcard/.
Then I installed the zip without any issues.
But then when restarting, it still warned me no OS was installed.
Booting anyways just got me stuck at the HTC logo.
I then tried again, this time flashing the kernel with Nik3r's file.
And then doing all the same stuff as before, but still getting the no OS was installed message and stuck on the HTC logo.
Perhaps it's the ROM I'm using? I'm not sure why it's telling me "no OS is installed" right after installing one.
el-Loko said:
why dont you try cm12? much better performance!
Click to expand...
Click to collapse
I actually can't find a ROM for CM12. I just grabbed the latest from http://download.cyanogenmod.org/?device=enrc2b.
KindDino said:
Ok, I tried again.
I went into the bootloader and flashed boot.img.
Then went into recovery, and did a factory reset via the wipe menu.
Then used "adb push" to push cm-11.zip to my /sdcard/.
Then I installed the zip without any issues.
But then when restarting, it still warned me no OS was installed.
Booting anyways just got me stuck at the HTC logo.
Click to expand...
Click to collapse
I never used "adb push" to push the ROM installation .zip onto my phone.
If you've made a nandroid backup, then go back to stock and give it a try to transfer the .zip in normal USB/Phone mode.
Afterwards repeat the process as described above.
When I flashed my last CM11 ROM, I used CWM as recovery and I flashed the boot.img after full wipe and rom/gapps installation.
After flash process I restarted the phone into bootloader and flashed the boot.img via adb. Then first normal reboot of the phone.
Worked without any issues...
KindDino said:
I actually can't find a ROM for CM12. I just grabbed the latest from http://download.cyanogenmod.org/?device=enrc2b.
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc...ent/rom-cyanogenmod-12-international-t2948462
Njoatun said:
I never used "adb push" to push the ROM installation .zip onto my phone.
If you've made a nandroid backup, then go back to stock and give it a try to transfer the .zip in normal USB/Phone mode.
Afterwards repeat the process as described above.
Click to expand...
Click to collapse
Sadly, I didn't know to make a backup when I started, so I cannot go back to stock at this time.
Njoatun said:
When I flashed my last CM11 ROM, I used CWM as recovery and I flashed the boot.img after full wipe and rom/gapps installation.
After flash process I restarted the phone into bootloader and flashed the boot.img via adb. Then first normal reboot of the phone.
Worked without any issues...
http://forum.xda-developers.com/htc...ent/rom-cyanogenmod-12-international-t2948462
Click to expand...
Click to collapse
I tried with TWRP again and actually decided to write down the entire log for installing the zip, maybe that'll help. It does say some things about errors, unsure if they're actual bad, or not, as it does succeed.
Of course after installing the zip, I selected 'Reboot' then 'Reboot into Bootloader', then used 'fastboot flash' to flash the boot.img with the boot.img from within the cm-12.zip.
Code:
Installing '/sdcard/cm-12.zip'..
Check for MD5 file..
Skipping MD5 check: no MD5 file found
could not detect filesystem for /dev/block/platform/sdhci-tegra.3/by-name/APP, assuming ext4
mount: failed to mount /dev/block/platform/sdhci-tegra.3/by-name/APP at /system: Invalid argument
unmount of /system failed; no such volume
Patching system image unconditionally...
could not detect filesystem for /dev/block/platform/sdhci-tegra.3/by-name/APP, assuming ext4
mount: failed to mount /dev/block/platform/sdhci-tegra.3/by-name/APP at /system: Invalid argument
unmount of /system failed: no such volume
script succeeded: result was [0.200000]
Updating partition details...
E:unable to mount '/system'
E:unable to mount '/cache'
...done
I tried CWM a few days ago while attempting this ( as it's linked in the CyanogenMod wiki ), and I just attempted it again with it and still cannot get past the logo.
Here is the log from CWM.
Code:
-- Installing: /sdcard/cm-12.zip
Finding update package...
OPening update package...
Installing update...
detected filesysystem extr4 for /dev/block/platform/sdhci-tegra.3/by-name/APP
Patching system image unconditionally...
detected filesysystem extr4 for /dev/block/platform/sdhci-tegra.3/by-name/APP
script succeeded: result was [0.200000]
Install from sdcard complete.
When rebooting back into the bootloader, I got an error about lost root access. I selected yes.
Code:
Root access possibly lost. Fix? THIS CAN NOT BE UNDONE.
- No
- Yes - Fix root (/system/xbin/su)
Seems like you've wiped your internal SD card partition, if it's unable to detect the ext4 format.
It's mentioned under Post 2 http://forum.xda-developers.com/showthread.php?t=2066390
If so... Search the forum for a solution. Never had this issue. Good luck
Njoatun said:
Seems like you've wiped your internal SD card partition, if it's unable to detect the ext4 format.
It's mentioned under Post 2 http://forum.xda-developers.com/showthread.php?t=2066390
If so... Search the forum for a solution. Never had this issue. Good luck
Click to expand...
Click to collapse
I read the post, and maybe I did wipe my SD Card. I have no idea on how to fix that, and I'll have to research more.
I would like to just use Hasoon2000's toolkit but sadly can't find a working download for it.
Same problem here! Nothing is working. It is saying no OS. Always booting into fastboot mode. Someone help. I have a Moto G3 1540
---------- Post added at 11:27 AM ---------- Previous post was at 11:18 AM ----------
Follow these steps and recover your device.
1. Unlock your bootloader if you have it locked
2. Boot into TWRP
3. Go to Wipe
4. Go to Advanced
5. Select everything except USB - OTG and SD Card
6. Boot into fastboot
7. Download the stock image of your phone
8. Flash it to your phone ( Please find it online)
9. After flashing do not reboot!!!
10. Download Cyanogenmod recovery and flash it to your device.
11. Boot into the newly installed recovery.
12. Go into Apply Update
13. Go into Apply Update from ADB
14. Sideload the Cyanogenmod using the command adb sideload filename.zip ( Replace filename with the name of your zip)
15. After Sideloading, boot into fastboot mode.
16. In fastboot mode, Select BP Tools.
17. Boom! Your device will start booting
Hope this helps you:good::good:
I had the same issue - here's how I went about this...
KindDino said:
Hi,
I'm currently trying to install CyanogenMod onto my HTC One X+, but keep running into problems.
I unlocked the bootloader, and installed TWRP v2.8.7.0.
I went into recovery fine, and used "adb push" to push cm-11-20150906-NIGHTLY-enrc2b.zip onto the device and install it through TWRP.
I then tap "reboot" but it always tells me that "No OS Installed", and rebooting into the bootloader to flash the boot.img and erase the cache doesn't seem to fix this issue.
I've tried a few different versions of recoveries, like CyanogenMod's recovery, but still can't seem to get it to install any OS. Always just get stuck on the HTC logo.
Am I missing an important step, or something? Thanks for your time.
Click to expand...
Click to collapse
I have a Nexus 7 2013 that I commonly use as both my daily driver (tablet-only) and as my ROM-testing guinea-pig. I had AOSP Android 7 installed before I wiped everything, due to an issue with Google Play (which I just couldn't fix for the life of me). When I went to flash a new ROM (AOSP Android 7.1.1), TWRP claimed that there was 'No OS'. This would mean that you definitely wiped everything - possibly including the partitions. My guess is:
If there are no partitions (esp. System, Recovery, Boot, Cache, etc.), the data meant for them may still get written to the device's storage. But the bootloader/kernel won't recognize where to pass the torch to when it's time for the system/userspace to come in.
In order to get this back , you may need either:
A) a ROM that has images for at least the System, Cache, and Boot partitions (add your own recovery if need-be).
B) a Stock ROM from the manufacturer's website, which tends to come with all of these images ready in the .zip
Once you flash one of those, you should confirm that your bootloader is unlocked. Once that is done, flash the ROM of your dreams
I hope this helped...
TWRP bootloop
el-Loko said:
hmm...sounds correct. just try it again.
1. boot into bootloader
2. flash the boot.img from the zip you want to install (for cm11 i recommend to flash nik3rs kernel http://forum.xda-developers.com/showthread.php?t=2012320)
3. reboot into recovery
4. select wipe from twrp menu
5. install the zip
6. reboot
why dont you try cm12? much better performance!
.
Click to expand...
Click to collapse
I have quite same issue.
I have TWRP 3.0.3 (that's the only version that i found and works) on my Doogee X9 Pro (MTK chip inside).
But after flashing successfully a ROM it still reboots to the recovery. (I tried it with 3 different ROMs.)
Any idea what else should/could try?
Hi everyone,
I have a Wileyfox Swift 2 which came up with and update available. So I went ahead and installed the new update.
I hated it.
So I tried to install a ROM of the previous update using TWRP Recovery. Problem was I accidentally wiped the original OS the phone was running one without having the ROM I wanted to install on the phone (It was my first time doing something like this). I had no access to the phone apart from the fastboot and TWRP Recovery Screens. I emailed Wileyfox Tech Support and told them what happened. They sent me several versions of the stock OS (the new one I wanted to get rid of, but I would be glad to get it working at all at this point).
I ended up having to use ADB Sideload to get the ROM on the phone and I'm pretty sure it is installed properly. Problem is: when I boot it up these messages come up:'your device software can't be checked for corruption, please lock your bootloader' and then 'dm verity not started in enforcing mode' for 5 seconds, and then it just gets stuck on the white booting up screen until I turn it off or go into Recovery. I know how to fix the bootloader lock error but that erases all user data on the phone. I really need to sort this out so what should I do?
Would appreciate any help,
Thanks!
By the way I don't really care about any data on the device, everything is backed up elsewhere.
After flashing the rom you can use adb in twrp recovery with the following command: adb reboot "dm-verity enforcing"
This should remove the dm verity message and allow your phone to boot.
Thank You
But do you mean have TWRP Recovery open on the phone and have ADB command window open on the computer and type the command because I've done that and it comes up with 'error: device null not found'.
I'm completely new to this sort of thing so as much detail as possible would be appreciated.
Yes, you have to have twrp open and on your pc the adb windows. First type adb devices to see if windows recognizes your phone. Mine says 50580003 recovery, when I type the command. If you get an error, you'll probably need to install the driver in device manager.
Ok thanks for confirming that for me. The problem is that my phone doesn't even show up as being connected to my computer and I can't access the phone's OS to turn on USB Debugging, so when I type the command 'fastboot devices' nothing comes up. Is there a way to do this from TWRP Recovery?
Hmm.... You could try installing the old cyanogen of and use that to enable usb debugging. Alternatively you could try flashing Magisk https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 . I never tried it but it should work also.
BlueSheep274 said:
Ok thanks for confirming that for me. The problem is that my phone doesn't even show up as being connected to my computer and I can't access the phone's OS to turn on USB Debugging, so when I type the command 'fastboot devices' nothing comes up. Is there a way to do this from TWRP Recovery?
Click to expand...
Click to collapse
Reboot your phone to fastboot mode from TWRP (reboot>bootloader) or the wileyfox boot menu then flash this file
(https://drive.google.com/open?id=0B34ZucLt1HQ9YjFRQ0otbmFRc28)
from your computer with fastboot.
It will also overwrite your recovery, system, data and internal storage partitions.
Facing same/similar problem
boa05 said:
Reboot your phone to fastboot mode from TWRP (reboot>bootloader) or the wileyfox boot menu then flash this file...
(link removed to allow first-time post)
from your computer with fastboot.
It will also overwrite your recovery, system, data and internal storage partitions.
Click to expand...
Click to collapse
Unfortunately the download link you provided is no longer available, would you mind reposting please?
I got the link working. Thanks for sharing. Unfortunately, flashing them failed with the following:
"Updater process ended with ERROR: 7"
Googling the error code, I found this: //.lineageosdownloads(dot)com/fix-error-7-lineage-os/ but I'm still just going round in circles trying to get OTA updates, re-flashing, rebooting into dastboot, losing adb connections and on and on....
markusmunch said:
Unfortunately the download link you provided is no longer available, would you mind reposting please?
Click to expand...
Click to collapse
Sorry about it, here is a reuploaded version.
Exact same problem
Having made exactly the same mistake as the OP, I've managed to re-install the old version of CyanogenOS but I can't get updates OTA or get rid of this dm-verity enforcing error on boot up. Any help would be massively appreciated.
markusmunch said:
Having made exactly the same mistake as the OP, I've managed to re-install the old version of CyanogenOS but I can't get updates OTA or get rid of this dm-verity enforcing error on boot up. Any help would be massively appreciated.
Click to expand...
Click to collapse
Just download the nougat ROM from Wileyfox, they will send you a link if you ask them. Then you can flash boot and system (and if you like all other partitions and radios) and it will then be on nougat and working correctly.
Scott
Worked
RedNas74 said:
After flashing the rom you can use adb in twrp recovery with the following command: adb reboot "dm-verity enforcing"
This should remove the dm verity message and allow your phone to boot.
Click to expand...
Click to collapse
I have been living in dm-verity hell for the past 4 hours trying to fix my phone after a bad firmware flash (4.1.3 replacing a bad SuperSU uninstall), even trying various 4.0.2 firmwares and full packages, as well as a full-phone restore to a previous TWRP backup I had from a few days ago.
I have absolutely no idea why none of the other methods at all worked (such as the simple fastboot oem disable_dm_verity then re-enable command), but this one finally did it on 4.1.3 *fingers crossed it stays that way*
Hi.
I unlocked the phone correctly via CMD.
Then, I flashed recovery VIA cmd too.
After that, I booted to recovery and the screen showed vertically half blurred screen after it booted into TWRP.
Finally, tried to install the rom unsuccessfully as TWRP didn’t detect any file in the SDCARD path. Some issue "mount sd card failed" related.
Tried, sideloading another zip file just in case but it says something about "closed device".
Now I cannot flash anything and I cannot reboot normally as It seems to be everything erased.
I can access fastboot and TWRP (although I cannot flash or side load anything...)
What could I do?
Flash this twrp https://dl.twrp.me/x2/twrp-3.2.1-0-x2.img
Boot into twrp
Wipe data partition
Install any rom you want
Heyyo, unfortunately adb sideload is currently broken on x2 official builds.
I'd recommend using...
adb push NameOfROM.zip /sdcard
That will push the ROM to your Sdcard folder. Same can be repeated for Gapps
I've just had my Nexus 9 a couple of weeks ago, been running on stock OTA 7.1.1 from Google with FireIce kernel. While tweaking around using ElementalX's app on the Play Store, I happened to create a simple script to reboot into recovery (i.e.
Code:
reboot recovery
).
After I ran the script, the tablet turned itself off for about ~3 seconds before showing up the Google logo, but this time it went straight into the stock recovery. I tried powering off the device and power it back on, but it kept going into the stock recovery which I remembered having it replaced with TWRP a few days ago. Things went weirder as I attempted to boot into TWRP using HBOOT (fastboot boot TWRP.img) and do a factory reset, but halfway through the process, it froze with the error 'can't mount /data (invalid argument)'.
I tried a few solutions online, one of which involved the command
Code:
fastboot -w
. I was able to get into the OS, but as soon as the boot animation ends I was asked to enter my password. No matter what the password, what resulted in the end was the same: "Decryption Unsuccessful - Your data is corrupt" and an option to do a factory reset, but to no avail, since it showed error halfway as well.
I noticed that while trying to do
Code:
fastboot -w
, it gave me a warning "f2fs not supported", furthermore the device seemed to be encrypted right from the factory.
Can anyone tell me what exactly happened? How to decrypt my tablet? I've tried FED Patcher but wasn't able to understand the guide thoroughly.
UPDATE: I've managed to install the Lineage OS 15.1 unofficial ROM and so far it's running fine but still get the "encrypted" thing going on.
format data and flash magisk or fec patcher to remove force encryption
ChristopherXI said:
format data and flash magisk or fec patcher to remove force encryption
Click to expand...
Click to collapse
Did that, nothing worked :/
I am attempting to root a moto g6 following procedure described in a guide on howtogeek named "how-to-root-your-android-why-you-might-want-to".
I successfully unlocked the bootloader, rebooted, copied SuperSU zip file to the internal storage, reentered fastboot, flashed TWRP with the platform-tools command
>fastboot flash recovery twrp.img
and opened TWRP (by entering recovery mode). However, TWRP can't decrypt my phone data no matter how many times I enter my password. On the other hand, there is the following clue on TWRP webpage for moto g6:
>Notes: Currently only vold decryption is working. This image must be flashed to properly decrypt. If you format data (Not just factory reset) after decrypting you must reboot into recovery and format again.
How do I know which type of encryption my phone is using and how do I switch it to vold encryption (if that's what is going to fix the issue)? Alternatively, can I cancel mounting data and just install SuperSU?
@digofr
TWRP isn't needed at all to install SuperSU Zip, Stock Recovery and a working ADB connection is sufficient