EDIT
I woke up and did exact the same thing as I was doing yesterday. It worked. I don't know how or why, but it worked.
Now I'm stuck on "Android initializing apps" screen. Maybe soon I'll get it to work xD
---------------------------------------------------------------
EDIT 2
All was needed to do, was boot the phone without charge cable pluged-in.
It's aaaaaallll fine now รต/
---------------------------------------------------------------
So... As the title says. By mistake, I wiped everything: Dalvik Cache, System, Data, Internal Storage, Cache, Micro SD.
Yea, everything. Total newbie.
My device is an Moto E XT1025
I'm trying to fix it for couple of hours now. But simply can't.
I have an .zip with ROM in the SD, tried to install/flash and give me this errors (in sequence):
- no MD5 file found;
- could not detect filesystem~;
- failed to mount~;
- patching system image unconditional;
- failed to update system image;
- error executing updater binary in zip;
Then I tried to adb sideload, so I have this error:
- no MD5 file found.
And it stops here.
The ROM I tried was: https://forum.xda-developers.com/devdb/project/dl/?id=14329
Now all my phone can do is: stuck at bootloader screen and enter in recovery/twrp mode.
I don't know what I can do now
Brother
Everything is possible in fastboot...
https://forum.xda-developers.com/moto-e/development/downgrade-5-0-x-to-4-4-4-stock-firmware-t3031073
U can this just use xt1025 firmware replace with xt1022
Related
I've tried to flash my rom to CM7 but something went wrong with the procedure because I am stuck on the android boot screen (Android logo lightning, it gets stuck for a while and then the letters continue flashing, cycling).
I followed the normal procedure: root, installed custom recovery, I made a backup with nandroid (normal one, which I copied to my computer), wiped data+cache (both caches) and I tried to flash from SD. Update went as normal but I got stuck in this boot screen.
After trying 2 or 3 times this same procedure and being unable to move on, I tried to recover my backup using nandroid: it said it was unable to recover and to do it from adb; adb says that it's unable to mount my sdcard.
From what I've read, I would need to repartition my card.. I chose that option in the recovery; still unable to recover my backup.
I figured that it would not be too bad if I lost my data, so after giving up on CM7 I gave up on recovering my data as well.. the problem is that even after wiping data and cache I'm still stuck in this same boot screen.
Any idea?
I can access recovery and adb so this has to have a solution..
I managed to boot after formatting /system.
Good evening,
I have a problem something like this ... the problem is in their own recovery.
I installed recovery, and supposedly installed everything OK.
the worst and go into the recovery agr (Betelgeuse v0.3), the file update meth-cm-9.0.0-RC0-folio100-KANG-r3.zip-signed for the card, already moved to update.zip and recovery not read the file.
He always says "no such file or directory" ... to help, I was "stuck" in the boot CyanogenMod 7.1.0 Android 2.3. the doll is always blue ... never goes away ... not enough to pass the animated image ... I've basically wipe data / factory reset, wipe Dalvik cache and everything .. and is always caught in the same place.
I try to install any rom and I can not install none (cant install oder recovery). what can I do? any ideas?
greetings
Hello,
I have a Kobo 10HD and rooted and installed CWM v6.0.5.1. I made a backup before and then installed Titanium Backup update.zip. Installation of that zip caused a bootloop (back to CWM). No problem, I thought, I can just restore the backup I made. No dice. I tried to restore the backup and still bootlooping. I even tried to installed the stock ROM ZIP and it fails with the message: (from recovery.log):
nv_copy_blob_file: couldn't get the device path
script aborted (no error message)
script aborted (no error message)I:Legacy property environment disabled.
E:Error in /data/media/0/macallan-ota-932.zip
(Status 7)
Installation aborted.
I have read that some people have had success installing this zip using stock recovery, but I have no idea how to get stock recovery.
Also, I noticed using adb shell that CWM does actually put all the files back into system and other areas during the restore. Upon reboot, and subsequent bootloop, the system files are gone. It must have something to do with an automatic script that is running after restore.
SOLVED!
zhzhou said:
Hello,
I have a Kobo 10HD and rooted and installed CWM v6.0.5.1. I made a backup before and then installed Titanium Backup update.zip. Installation of that zip caused a bootloop (back to CWM). No problem, I thought, I can just restore the backup I made. No dice. I tried to restore the backup and still bootlooping. I even tried to installed the stock ROM ZIP and it fails with the message: (from recovery.log):
nv_copy_blob_file: couldn't get the device path
script aborted (no error message)
script aborted (no error message)I:Legacy property environment disabled.
E:Error in /data/media/0/macallan-ota-932.zip
(Status 7)
Installation aborted.
I have read that some people have had success installing this zip using stock recovery, but I have no idea how to get stock recovery.
Also, I noticed using adb shell that CWM does actually put all the files back into system and other areas during the restore. Upon reboot, and subsequent bootloop, the system files are gone. It must have something to do with an automatic script that is running after restore.
Click to expand...
Click to collapse
After a few more hours of fiddling, I was able to get the device back up. I wiped absolutely everything manually with CWM (format /X) instead of Wipe/Factory Reset. The factory reset was not clearing the SD card, but format/data and /data/media cleared it. I then applied the stock zip that is available via adb sideload. Installation failed with the same error, but I rebooted with the adb reboot command. The device booted back into Kobo stock requiring several updates. It actually got stuck repeating one update several times until I booted back into stock recovery and cleared data and did a factory reset. The update applied correctly and then another upgrade came (a total of three upgrades). I rooted again and we are back in business.
For some reason, I think the key step was manually wiping /data/media. I'm not exactly sure why this would cause a bootloop for CWM restore. Anyway, I hope this helps someone else who may run into a similar issue.
Hi zhzhou!
Just a quick question:
do you happen to remember if stock recovery for Kobo was CWM? I'm in process of restoring stock ROM +recovery and little bet surprised to see CWM after flashing stock recovery
Thanks a lot!
zhzhou said:
After a few more hours of fiddling, I was able to get the device back up. I wiped absolutely everything manually with CWM (format /X) instead of Wipe/Factory Reset. The factory reset was not clearing the SD card, but format/data and /data/media cleared it. I then applied the stock zip that is available via adb sideload. Installation failed with the same error, but I rebooted with the adb reboot command. The device booted back into Kobo stock requiring several updates. It actually got stuck repeating one update several times until I booted back into stock recovery and cleared data and did a factory reset. The update applied correctly and then another upgrade came (a total of three upgrades). I rooted again and we are back in business.
For some reason, I think the key step was manually wiping /data/media. I'm not exactly sure why this would cause a bootloop for CWM restore. Anyway, I hope this helps someone else who may run into a similar issue.
Click to expand...
Click to collapse
Stock was definitely not CWM. It was a long time ago and I no longer have the device, but I think CWM was still present after restoring stock. I think you'll need fastboot if you want to flash the stock recovery image back on. But why do that? TWRP is now available for the device.
Thanks for quick reply! I had CM on it but had some artifact issues so wanted to revert to full stock, even recovery
zhzhou said:
Stock was definitely not CWM. It was a long time ago and I no longer have the device, but I think CWM was still present after restoring stock. I think you'll need fastboot if you want to flash the stock recovery image back on. But why do that? TWRP is now available for the device.
Click to expand...
Click to collapse
Hi all,
I have Samsung A5 2016 and I tried to update my phone through latest Naugat official firmware using by Odin however it turned out something wrong. My first problem is when I enter the boot screen, ''installing update'' screen pops up and then ''no comment screen'' afterward. Second problem is that boot screen shows an error says E: failed to find /misc partition. I've read tons of post however I couldn't figure this out.
I would greatly appreciate it if you could help me.
Thank you & Best!
Hi
My message has been moved here
https://forum.xda-developers.com/samsung-a-series/help/sm-a510f-rom-stock-entering-mode-t3653121
Thanks
Anybody know how to deal with the E: failed to find /misc partition? I saw this come up on my SM-J700T after I tried to flash TWRP. The flash passed but TWRP was not successfully installed. Probably because I did not prevent reboot and reboot in a proper way . But now I have been all around the barn trying to recover and eventually get twrp and root. I flashed several stock roms with lots of errors and finally got the phone running with Nougat 7.1.1 but the E: failed to find /misc partition error remained on the phone all the while. I was unable to use Odin to re-partition due to errors and have been trying to figure out how to use adb, also with errors (yesterday I launch "abd devices" and get a listing for my device (I think- it is not properly identified) and it lists the device properly, today it lists the same device as unauthorized. So what I really would like to do is completely wipe the phone and start fresh but I only have access to the stock bootloader which allows cache wipe and data wipe- factory reset, which does not wipe the Missing partition. So 1)completely wipe phone 2)install twrp 3)root
hey guys just looking for some help. ive been modding and flashing phones from 2014, but its always gone really smoothly, so my diagnostic ability is lacking.
it started with flashing twrp. my bootloader is unlocked, usb debugging on, device is showing in adb and fastboot, and i can flash twrp without any issues. hoowever when i go to boot twrp, only the stock recovery boots. i tried to flash twrp using the XiaoMiTool v2, but the same thing happened. i eventually got around this by just booting twrp instead of trying to flash it. so i got in, took a full back-up and started installing a custom rom.
the first one i tried was ParanoidAndroid Quartz. i wiped cache, dalvik and storage then transferred it to my phone, tried to flash and got "zip verification failed". so i turn off zip verification and tried again. it flashed perfectly with zero errors. however, when i reboot the phone it would only boot to stock recovery and not twrp (expected) or the new rom. i tried that a few times, then tried LineageOS, and MSM Xtended 10. all of them had the same issue, the flashed without a hitch, then wouldnt boot.
i also tried flashing a new fw-vendor and it just straight up failed. Then i decided to cut my losses and restore my twrp backup, and that came back with the error, "extractTarFork() process ended with error: 255"
Software before i began these attempts was completely stock, so i dont know what is going wrong, but as of now, my phone is bricked, i cant install a new rom or restore my back-up.
any help is appreciated guys. thanks
You can figure out this problem with
1 Copy backup folder to computer
2- Format Data - Yes , Wipe Everything
3- Install ROM that you have installed before and boot
4- Go to TWRP, format data yes reboot recovery
5- Paste backup folder to internal storage and restore