I tried to update my device with the newest ROM (Dirty Unicorns) and somehow bricked it. ...
The device just stuck in the flashing process for over 10 hours. After TWRP and Fastboot were still working, I tried a lot of things to revive the system, but everything I tried went wrong.
First I tried to flash the factory image. The strange thing: that seamed to work well (with Wugfresh toolkit), but the device still stuck in a bootloop.
Everything I try in the recovery mode ends by TWRP with "E: Unable to mount '/system'" (in red letters). So I tried to flash the factory image again and wiped the device in the newly flashed Revovery completely.
No change: "Updating partition details... E: Unable to mount '/system'".
- ABD sideload doesn't work. I tried to flash system.img. No success.
- Bootloader is unlocked. V3.44.1.0123
- Newest TWRP (twrp-2.8.7.0-flounder.img)
Here are the best Android-experts worldwide! So can someone please help me?
Thanks in advance!!
Regards,
Frank
Gleichzwei said:
I tried to update my device with the newest ROM (Dirty Unicorns) and somehow bricked it. ...
The device just stuck in the flashing process for over 10 hours. After TWRP and Fastboot were still working, I tried a lot of things to revive the system, but everything I tried went wrong.
First I tried to flash the factory image. The strange thing: that seamed to work well (with Wugfresh toolkit), but the device still stuck in a bootloop.
Everything I try in the recovery mode ends by TWRP with "E: Unable to mount '/system'" (in red letters). So I tried to flash the factory image again and wiped the device in the newly flashed Revovery completely.
No change: "Updating partition details... E: Unable to mount '/system'".
- ABD sideload doesn't work. I tried to flash system.img. No success.
- Bootloader is unlocked. V3.44.1.0123
- Newest TWRP (twrp-2.8.7.0-flounder.img)
Here are the best Android-experts worldwide! So can someone please help me?
Thanks in advance!!
Regards,
Frank
Click to expand...
Click to collapse
Boot to bootloader, and enter the following commands:
fastboot format cache
fastboot format userdata (NOTE THAT THIS WILL WIPE THE CONTENTS OF YOUR SDCARD)
fastboot reboot
Related
I've a rooted ZTE V972M. I tried to increase internal storage following instructions in
"Re-Partition any MTK6589 Phone, Without A PC! (More /Data Storage!)"
When I reboot my phone, it stucks at logo screen.
What I've done trying to fix it:
1. Enter the recovery mode; it's a stock recovery (Android system recovery <3e>); wipe data/factory reset, wipe cache partition.
Result: still stuck at logo when rebooting.
2. Flash a stock ROM in recovery mode.
Result: Update aborted. In the log file, it says "failed to mount /cache (No such file or directory)" detailed in attached file. The stock rom I used is for ZTE LEO S1, while my phone is DTAC LION HD which is a house brand of my phone carrier. So, there may be a problem of ROM signing.
3. I installed "Minimal ADB and Fastboot" and "ZTE_Android_Driver", and run "adb devices" command.
Result: There is nothing under " List of devices attached", so I assume adb cannot see my phone. In Windows' Device Manager, it shows "Portable Devices" and lists drive I:\ and K:\ under it.
In summary, My phone is rooted. I might have damaged partition /data and /cache which causes the bootloop. I can still enter stock recovery mode. I have a stock ROM, but may not be properly signed.
Please suggest me on what I can do next.
Thanks.
sasawatd said:
I've a rooted ZTE V972M. I tried to increase internal storage following instructions in
"Re-Partition any MTK6589 Phone, Without A PC! (More /Data Storage!)"
When I reboot my phone, it stucks at logo screen.
What I've done trying to fix it:
1. Enter the recovery mode; it's a stock recovery (Android system recovery <3e>); wipe data/factory reset, wipe cache partition.
Result: still stuck at logo when rebooting.
2. Flash a stock ROM in recovery mode.
Result: Update aborted. In the log file, it says "failed to mount /cache (No such file or directory)" detailed in attached file. The stock rom I used is for ZTE LEO S1, while my phone is DTAC LION HD which is a house brand of my phone carrier. So, there may be a problem of ROM signing.
3. I installed "Minimal ADB and Fastboot" and "ZTE_Android_Driver", and run "adb devices" command.
Result: There is nothing under " List of devices attached", so I assume adb cannot see my phone. In Windows' Device Manager, it shows "Portable Devices" and lists drive I:\ and K:\ under it.
In summary, My phone is rooted. I might have damaged partition /data and /cache which causes the bootloop. I can still enter stock recovery mode. I have a stock ROM, but may not be properly signed.
Please suggest me on what I can do next.
Thanks.
Click to expand...
Click to collapse
can you return to stock using the mediatek flash tool and your stock firmware?(I'm not knowledgeable with MTK)
Lgrootnoob said:
can you return to stock using the mediatek flash tool and your stock firmware?(I'm not knowledgeable with MTK)
Click to expand...
Click to collapse
mediatek flash tool cannot see the phone either.
May be, if I can install CWM or TWRP, I might be able to update the stock rom with it. I've read elsewhere that If a phone can enter recovery mode, we can use fastboot in download mode. But I don't know how to install CWM or TWRP with fastboot.
sasawatd said:
mediatek flash tool cannot see the phone either.
May be, if I can install CWM or TWRP, I might be able to update the stock rom with it. I've read elsewhere that If a phone can enter recovery mode, we can use fastboot in download mode. But I don't know how to install CWM or TWRP with fastboot.
Click to expand...
Click to collapse
Driver issue?
Syntax for fastboot stuffz
try flashing:
Code:
fastboot flash recovery recovery.img
If flashing isn't working then try booting it directly
Code:
fastboot boot recovery.img
I have an M7 that gets stuck on the HTC boot screen. I can flash recovery, view files view file manager while in recovery TWRP. However trying to wipe cache/dalvik etc. I get an 'unable to mount /*' error. I have tried the RUU process which was successful but the issue remained unresolved. I have tried the mkfs.ext4 to try and unblock the blocks with issues without success.
I have bootloader unlocked, I tried flashing the SuperUser but it failed due to the mount issue. So I have S-ON and yes... my phone has 30%+ power.
Any help ?
dakimMastamynd said:
I have an M7 that gets stuck on the HTC boot screen. I can flash recovery, view files view file manager while in recovery TWRP. However trying to wipe cache/dalvik etc. I get an 'unable to mount /*' error. I have tried the RUU process which was successful but the issue remained unresolved. I have tried the mkfs.ext4 to try and unblock the blocks with issues without success.
I have bootloader unlocked, I tried flashing the SuperUser but it failed due to the mount issue. So I have S-ON and yes... my phone has 30%+ power.
Any help ?
Click to expand...
Click to collapse
When you flashed recovery did you fastboot erase cache after you flash it and before you rebooted? If not, you need to do that to clear out any thing left from the last recovery.
Which custom recovery are you using with the version number?
What was the RUU version and where did you get it?
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?
Good night,
I have an ASUS Z010D device that entered a loop, when entering the recovery mode it throws a message E: / I Can't Mount / Cache also when applying any option in the menu it throws a mount error in the E: drive and several directories.
I have tried various commands in adb and fastboot but have not been successful.
Important: the bootloader locked and I have not managed to unlock it since the computer does not start the operating system.
Thanks for the support you can give me!
@jesusz24
Seems to be a TWRP related problem. Or partition /cache doesn't exist.
answer
jwoegerbauer said:
@jesusz24
Seems to be a TWRP related problem. Or partition /cache doesn't exist.
Click to expand...
Click to collapse
hi jwoegerbauer,
if apparently it is a recovery problem.
The cache partition allows me to format it without any problem through fastboot, which seems strange to me.
The problem really is that I can't root the computer or unlock the bootloader before it loops.
at the moment it does not let me install the twrp to try to distribute.
Do you have any procedure to unlock the bootloader?
thanks for him
@jesusz24
Never have installed TWRP or any other custom recovery on the mobile devices I have and/or I had, hence can't help you with your TWRP problem.
Twrp updated from 3.5 to 3.6. I'm on A19. Rooted with Magisk 24.3. I flashed TWRP 3.6.img with Twrp 3.5. Flash OK, reboot in recovery mode OK. System reboot OK. Reboot in recovery mode to test Ok. Reboot system and there bootlooped with red point and white point turning.
I can reboot in TWRP. Il fastboot boo.img, vbmeta.img. Same pb Bootlooped.
I have a nandroid backup (data/boot/cache/DTBO/NVCFG/NVDATA/NVRAM/Persist/Persist Image/Protect F/protect S/Recovery/VBMeta).
I tried ti restore these partitions without erasing partitions. Restore OK but noway to boot. Bootlooped
I wipe all partitions. Restore without Data partition (with data, I have an error). Same bootlooped
I am trying to restore the data partition only. I have this error "Failed to mount '/data' (Invalid argument)
I have no more idea, I'm a little desperate. No solution ? Return the smartphone for repair?
1) flash stock recovery and stock boot via fastboot
2) flash patched vbmeta via fastboot with fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
2) format data via stock recovey
3) let it reboot to system
4) flash twrp via fastboot
5) restore only /data via twrp
6) reboot to system
7) UI will be broken, reboot again to fix it
8) remove any pin / password / pattern form the settings, and redo it.
9) Re flash twrp and magisk to root.
Thank you very much for this procedure Raygen. I was indeed able to recover my phone and restart it but it is very unstable. I had bootloopers again after reinstalling TWRP and Magisk. Now I have a problem with my security code or my fingerprints. Looks like they don't take them into account when I want to hand over a security code. Another problem is the camera no longer works. The app does not start. I tried to install the oneplus camera app loaded on Telegram v 3.422.2 but the installation failed.
A proposal to solve these problems ? Reinstall a partition other than Data that I backed up by Nandroid or is it back to OnePlus?
Try to restore the /persist partition from the twrp backup.
take a read here: https://forum.xda-developers.com/t/...rprint-to-become-completely-disabled.4363067/
Thanks very much. By restoring the "persist" partition, I recovered the camera and the fingerprints function. I hope the bootloops will stop there. Thank you very much, you are my saviour.
My OnePlus Nord 2 Indian version got hard bricked and I can't go in recovery or fastboot mode it is in a bootloop on OnePlus logo .
Any help???