Dear members, I've experienced bootloop, details as below.
Device: Moto E4
SKU: XT1760
Steps leading towards bootloop
1. intention: to install recovery and custom rom
2. unlock bootloader using adb
3. used the following to install twrp, Moto E4 Guide To Rooting Mediatek Variant SKU XT1760
TWRP was taken from Ported TWRP Recovery For Moto E4 Mediatek Variant SKU XT1760
4. twrp installed successfully
5. trying to backup stock rom, encounter error, couldn't mount /data
6. trying to flash custom rom, encounter error, couldn't mount /data
7. changing ext4 to ext2 back to ext4, encounter error, couldn't mount /data
8. changing ext4 to fat back to ext4, success
9. backing stockrom, success
10. wiping data, system, cache, dalvik, success
11. flashing Resurrection Remix N v5.8.5, success
12. reboot
13. bootloop recovery
14. retry
15. bootloop recovery
16. attempted to enter fastboot, black screen with small words at the bottom right, no options available
17. reboot, resulting in bootloop moto logo
18. pulling battery, inserting back, attempted to enter recovery(vol down + power button), fail
19. bootloop moto logo
I am open to suggestions. I've googled for solutions but to no avail. Your help would be appreciated. Thank you.
Hi #Fear,
I'm not sure but iykeDROID™ stated:
ROM Firmware Required: Must be on Nougat[SKU: XT1762]
Perhaps you've to use RR ROM - Resurrection Remix 5.8.5-20180122 by iykeDROID for Moto e4 Mediatek "Woods"
Do not forget to install no-verity-opt-encrypt zip file after flashing.
Hi, just to update you guys, i am now running on Resurrection Remix N v5.8.5.
For future XT1760 variant users.
This guide works to install TWRP. *don't forget to thank OP.
However, if you encounter "unable to mount /data", you will need to change the tick 'data' and select "file system" 'ext2' then back to 'ext4', I was on a first recovery that doesn't allow me to do so, so I flashed another recovery which it was able to.
Once that is done you will be able to flash the 'no-verity-opt-encrypt zip file' without any error, but if you still encounter the 'unable to mount /data', then maybe you will need to try another recovery.
Then I flash the custom rom with gapps and it booted b-e-a-utifully.
On another matter, if you encounter bootloop on the moto logo, and you are unable to enter recovery/fastboot/adb command, this is for you.
Google for SP flash tool. Make sure you have all the drivers installed. Get the stock Moto e4 file.
*WARNING* THIS WILL CLEAN YOUR PHONE OF ALL DATA
You can restore your device to stock using the program. There is multiple guides on youtube and a simple search can lead you to the said files.
Related
Hi all,
I am stuck at stock recovery. Can anybody help me to restore stock ROM?
Here is the story:
After I root GTAB manually according to that thread http://forum.xda-developers.com/showthread.php?t=859712, I tried to apply the GPS trick explained @ http://forum.xda-developers.com/showthread.php?t=922692
Actually instead of using root explorer to place the files, I tried to replace files in zip file manually(via adb). It looks like something was wrong and device doesn't boot normally anymore. It just reboots to recovery instead. In addition, adb still founds device during recovery but "adb shell" gives an error saying link error. I assume "sh" binary was depending on one of the files I modified.
So, is there an instruction to restore stock ROM on the device.
My current recovery screen says:
Android System Recovery 3e
Samsung Recovery Utils
for BML
- Reboot System
- apply sdcard: update.zip
- wipe data /factory ...
- wipe cache
...
Installing Multi-CSC
All information related to flashing/recovering a device at recovery can be found at
http://www.thegalaxytabforum.com/in...flashing-euro-firmware-on-samsung-galaxy-tab/
I also had to use trick mentioned at that thread to get rid of blank screen after first boot:
http://forum.xda-developers.com/showthread.php?t=899196
Thanks everybody!
Hi , newbie help needed here!
have tried to root my moto and installed twrp properly. everything stopped working fine after i tried to install supersu. i tried to reflash stock image however for some reason twrp stopped working and I cannot run cwm either. the errors from cwm read:
"unable to load kernel"
while on twrp the system kept looping while attempting to install - i got errors such as "cannot find e: data" or "cannot mount e:" etc.
Has anyone come across this situation? Thanks in advance.
How did you get cwm recovery when it's still not available for mxp?...
Download stock firmware and RSD lite and flash it. RSD lite only works on windows 7.. otherwise you have to flash firmware manually.
derheckler said:
Hi , newbie help needed here!
have tried to root my moto and installed twrp properly. everything stopped working fine after i tried to install supersu. i tried to reflash stock image however for some reason twrp stopped working and I cannot run cwm either. the errors from cwm read:
"unable to load kernel"
while on twrp the system kept looping while attempting to install - i got errors such as "cannot find e: data" or "cannot mount e:" etc.
Has anyone come across this situation? Thanks in advance.
Click to expand...
Click to collapse
Follow the instructions from here
http://forum.xda-developers.com/moto-x-play/general/how-to-flash-stock-marshmallow-firmware-t3277657
Download & install minimal adb and fastboot.Extract the firmware to that folder and then enter the fastboot commands
http://forum.xda-developers.com/showthread.php?t=2317790
Hello Friends, I just upgraded my Zenfone 3 ze520kl to Nougat, but i prefer Marshmallow i try from recovery mode to flash Marshmallow, it shows error and the installation aborted. Can any one help . Thanks.
What error does it show?
Error with some numbers follows by 'install aborted'. I unable remember the error numbers. I did three times all the time with same remark.Thanks.
That's not very helpful. Can you try it again and tell us exactly what it says?
Hi,
I downgraded a few days ago, here's an overview of the steps.
WARNING, this requires a factory reset so you will lose the data on the phone, so make sure you have backups before you proceed. You do this at your own risk and I am not responsible for any damages.
I assume you have adb / drivers all configured and know to how use them.
1) download firmware file http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE520KL/UL-ASUS_Z017D_1-WW-13.20.10.152-user.zip and save to SD card / insert card in phone.
2) download recovery and boot img files for Z017D_WW_13.20.10.152
- https://mega.nz/#F!ok0V0RIA!5WKtHe98opzjVI3NPbM7Ww
- under the folder Z017D_WW_13.20.10.152
3) Go to fastboot mode (power + vol up)
- flash recovery.img (command: fastboot flash recovery recovery.img)
- flash boot.img (command: fastboot flash boot boot.img)
4) reboot to recovery (power + vol down)
5) install update form micro sd card.
set the file UL-ASUS_Z017D_1-WW-13.20.10.152-user.zip that you saved earlier
6) wipe cache
7) factory reset
If you don't do a factory reset and reboot, Android pretty much crashes on multiple processes on start up, it is unusable.
Regards,
TK
Credit goes to https://forum.xda-developers.com/zenfone-3/help/guide-how-to-root-zenfone-3-ze552kl-t3471524 for laying the foundation.
Warning- No file-contexts. This package is for "ww-phone" devices, this is a E:error in /side load/ package.zip (status 7) Installation aborted.
Same thing happened to me as well. I just went ahead to flash the RAW file (http://www.asus-zenfone.com/2016/12/asus-zenfone-3-raw-firmware-and-asus.html) and updated the software to the latest marshmallow update, followed by a factory reset.
If we Downgrade
Then we get update in future yes or no??
Sorry for bad English??
Yes.
Hi, thanks for the help. Please answer this:
Do I need to use Recovery and Boot.img the same version of ROM? Why?
Why do I need to install Boot.img?
Hello GUYS.. So I was on the latest nougat update and I wanted to try CM13 on my P9 Lite VNS-L31 but someone told me that I need to downgrade to 6.0 before I install CM13 So I downloaded oeminfo and 6.0 rom from update finder.. and first I wiped system, data, cache and dalvik cache..okay so now I have no os installed.. Then I tried to install oeminfo with TWRP.. But it can't mount product/vendor/version (invalid argument) And I was like wtf does this mean? so I flashed stock rom image with fastboot again.. it said it's installed but twrp says no os is installed.. ugh I just tried everything to fix that..I tried to extract vendor.img and product.img and flashed them from fastboot.. But it said command not allowed and still twrp gives me the same errors when i try to wipe data or install system.. I asked people on another site and they told me I should install stock boot and recovery images from twrp and install system with 3 buttons method.. So I did but it said failed.. And when I wanted to flash twrp again the bootloader was locked wtf? so then I tried to unlock it again it asked me if i really wanna unlock it and I choose yes..the phone rebooted and I got this
Error Mode
Attention
Please update system again
(Android Logo)
Error!
Func NO: 11 (recovery image)
Error NO: 2 (load failed)
now I can't boot into recovery or fastboot it just stays in this screen
I tried to install system with the 3 button method but it just won't boot to anything.. I also tried to connect the cable and boot to fastboot..But it. just shows the huawei logo and then goes back to error mode.. please tell me what I should I do now?
hi, did you solve this issue?
You should've just downloaded the rollback package and stock mm rom. Flash the roll back package and then the mm rom in eRecovery. Btw if you are going for meticulus Cm13 rom then ot has been removed from his website and in the beanstalk rom of meticulus when you call someone or someone calls you then the UI restarts. Thats a major bug
Ok, so I’m trying to fix this phone my friend messed up like a year ago and then gave up on..
Huawei P10 Lite
Build No: WAS-LX1C432B183
Bootloader: unlock
FRP: unlock
Rooted (or used to be I guess)
These are his notes from back then:
Flashed an unstable Lineage build and provided the wrong vendor.img –
tried to flash stock Nandroid backup through TWRP, which failed, phone was still running Lineage. Bugs got worse every reboot, finally stuck in bootloop on Lineage booting screen. Then did a full wipe and flashed stock ROM again - update_data_full_public.zip worked, update_full_WAS-L01_hw_eu.zip failed ("error:9")
finally flashed vendor.img the same way as with the wrong file in the beginning dd if=/external_sd/vendor.img of=/dev/block/bootdevice/by-name/vendor
now device can't mount /vendor anymore and bootlooping on the “ur device can’t be trusted” screen
Ok, so now I honestly don’t know what the last command actually does or if he got it wrong, he can't remember where he got it from and so far I didn't really find anything on it either..
I can now
• boot into erecovery, which starts but fails every time ("file does not exist"),
• do 3 button method, which gets to 5% then stuck again and returns to bootloop
• fastboot flash just about anything successfully according to logs – still bootloop
• use Unbrick option in the Multi Tool (which does the same as far as I can tell), again successful according to logs but still bootloop
• get into TWRP, flash stuff from there (stock, Lineage), also success but no change
I keep getting “failed to mount /vendor” in the logs though, and still can’t mount /vendor from TWRP and it says it’s 0MB.. I honestly don’t dare messing with partitions on my own as I’m not sure what the exact problem is..
Can someone please help?
Thanks already (and sorry this is so long..)