Related
I've been running CM7 nightlies on my MT4G for a while now and have been quite happy with it. Unfortunately now I'm not able to boot it up. It's not a fully-fledged brick yet - I can still bot into recovery.
When I boot into CWR I get the following errors:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Click to expand...
Click to collapse
I followed the directions in this thread: forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/ , but running parted gives me the following error:
Error: /dev/block/mmcblk0: unrecognised disk label
Click to expand...
Click to collapse
Trying it again with /dev/block/mmcblk0p27 gives the same:
Error: /dev/block/mmcblk0p27: unrecognised disk label
Click to expand...
Click to collapse
I've posted recovery.log here: pastebin.com/N6EbBzJM
Note the following error:
/sbin/tune2fs: Attempt to read block from filesystem resulted in short read while trying to open /dev/block/mmcblk0p27
Click to expand...
Click to collapse
Running e2fsck from adb shell gives me a similar error:
e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/block/mmcblk0
Could this be a zero-length partition?
Click to expand...
Click to collapse
It sounds to me like I have some bad memory blocks, but I can't figure out how to fix them. I was hoping e2fsck would do the trick.
Any help would be appreciated.
might be fried SD?
Are you referring to the internal SD? The external SD is working just fine, and at least the recovery partition is working (although I am unable flash a recovery image to it using fastboot, for some reason).
It seems like I have some bad blocks on the internal memory, but I don't know how to confirm this. Any ideas, anyone?
mine always says that when I make first selection, cannot find, etc...
But then I have to confirm it on second screen and works fine.
I have never seen it make any menton of internal however, I always install or flash from external sd.
So you cannot restore to a previous restore that did work?
No, I can not restore any of my backups - any attempt to flash fails due to the failure to mount the cache partition.
The errors "Can't mount /cache..." occur in CW recovery, not the bootloader.
samhiatt said:
No, I can not restore any of my backups - any attempt to flash fails due to the failure to mount the cache partition.
The errors "Can't mount /cache..." occur in CW recovery, not the bootloader.
Click to expand...
Click to collapse
Have you tried to pd15img it back to stock yet? Link in my sig.
Yes, I have tried flashing the pd15img. The bootloader finds the image, asks if I want to install it, and then says "Fail_PU" after trying to install both the boot and recovery partitions, then freezes and eventually reboots while installing the radio image.
I've done a lot of searching around and wasn't able to find what the "Fail_PU" messages mean.
samhiatt said:
Yes, I have tried flashing the pd15img. The bootloader finds the image, asks if I want to install it, and then says "Fail_PU" after trying to install both the boot and recovery partitions, then freezes and eventually reboots while installing the radio image.
I've done a lot of searching around and wasn't able to find what the "Fail_PU" messages mean.
Click to expand...
Click to collapse
That doesn't bode well. I'd say it's time for warranty.
Sent from my HTC Glacier
I was afraid of that. ... It seems like there's gotta be a way to repair the disk and get it running again. But maybe it's not worth the time that would take.
... Has anyone had any experience making a warranty claim on a "rooted" phone with Tmobile?
samhiatt said:
I was afraid of that. ... It seems like there's gotta be a way to repair the disk and get it running again. But maybe it's not worth the time that would take.
... Has anyone had any experience making a warranty claim on a "rooted" phone with Tmobile?
Click to expand...
Click to collapse
I agree with you. It seems like a simple reformat should be all it would take.
How did this happen anyway?
Not sure what made it crash, but it seemed spontaneous. One morning I tried to open Messaging but it would immediately close (with no FC message). I think I tried a couple other apps, they wouldn't open so I tried a reboot. Froze during reboot, so I booted into recovery and tried wiping the cache. Since then I haven't been able to start android.
I had just flashed CM7 RC1 and then reverted back to a previous nightly the day before it crashed. I don't know if this could have anything to do with it, but it doesn't seem too likely.
Using CWR to try to reformat the cache throws this error: "Attempt to read block from filesystem resulted in short read while trying to open /dev/block/mmcblk0p27"
What can I do to confirm if this is a hardware failure?
try holding the up volume button and power, for stock boot,and reformat, use image you used for the first backup ever. See if that works
samhiatt said:
Not sure what made it crash, but it seemed spontaneous. One morning I tried to open Messaging but it would immediately close (with no FC message). I think I tried a couple other apps, they wouldn't open so I tried a reboot. Froze during reboot, so I booted into recovery and tried wiping the cache. Since then I haven't been able to start android.
I had just flashed CM7 RC1 and then reverted back to a previous nightly the day before it crashed. I don't know if this could have anything to do with it, but it doesn't seem too likely.
Using CWR to try to reformat the cache throws this error: "Attempt to read block from filesystem resulted in short read while trying to open /dev/block/mmcblk0p27"
What can I do to confirm if this is a hardware failure?
Click to expand...
Click to collapse
You said earlier that fastboot flash of recovery failed, correct? Which recovery are you using now and do you still have access to it? I assume you tried reflashing other roms as well?
That doesn't work. After holding vol up + power the phone vibrates 3 times, then the LED keeps flashing red with a blank screen.
I would try another SD card, if that doesn't work, Brick
Phateless said:
You said earlier that fastboot flash of recovery failed, correct? Which recovery are you using now and do you still have access to it? I assume you tried reflashing other roms as well?
Click to expand...
Click to collapse
Correct. Fastboot flash fails with the following:
writing 'recovery'... FAILED (remote: image update error)
Click to expand...
Click to collapse
Yes I am able to boot into the CW Recovery 3.0.0.5 on the phone. I am also able to do a fastboot boot into 3.0.0.6 over USB.
Attempting to flash any rom fails with:
Error while erasing boot image!
Click to expand...
Click to collapse
I just posted the output of dmesg at http://pastebin.com/4Ffj6sUx. Note all the errors with mmcblk0.
lion766 said:
I would try another SD card, if that doesn't work, Brick
Click to expand...
Click to collapse
The SD card is fine. Internal memory (mmcblk0) is the one with the errors. That's not replaceable, right?
It it is not retrieving good information from the SD card, you will get that error
That error looks more like a recovery image error, as opposed to a phone issue. Try and redownload and fastboot flash recovery again.
also, from fastboot try
Code:
fastboot erase system -w
option94 said:
That error looks more like a recovery image error, as opposed to a phone issue. Try and redownload and fastboot flash recovery again.
also, from fastboot try
Code:
fastboot erase system -w
Click to expand...
Click to collapse
Thanks option94. I've tried several recovery images and though I'm not able to flash them to my phone I can boot them from fastboot. I just tried booting up CWR 2.5.1.2 which worked, but I still got the "can't mount /cache..." errors. Dmesg after trying to format cache from CWR 2 shows a bunch of error messages like:
[ 67.592468] mmcblk0: error -110 requesting status
[ 67.592712] mmc_blk_issue_rq failed!!
[ 67.604736] mmcblk0: error -110 sending status comand
[ 67.604858] mmcblk0: error -110 sending read/write command, response 0x40ff8080, card status 0x40ff8080
Click to expand...
Click to collapse
I just tried
Code:
fastboot erase system -w
It's been stuck on "erasing 'system' ..." for at least the past ten minutes...
Hello there,
I updated my LG P700 to the v20c 4.1.2 JB version. After that, I couldn't find a wayu to root it, but found Framaroot app and succeeded with it. I got a little cocky how easy it was and downloaded ROM Manager. From it, I chose the CWM installation option and the window said it was a success. However, when I clicked to reboot into the recovery, only this little error appeared - "Secure Booting Error! Cause: Boot certification verify." in the left uper corner of the screen. Nothing worked, so I took out the battery and after turning the phone on, I noticed that all the internal memory got factory reseted or something like that and it is just a blank fresh android - all data was lost.
Long story short: flashing recovery from ROM Manager caused the wipe of the memory.
What happened?
[UPDATE] It could be caused by not unlocking the bootloader. I assumed that ROM Manager checks these things or flashes them with the recovery.
If that's the case (pls tell me) then I should unlock the bootloader. Maybe with this - http://forum.xda-developers.com/showthread.php?t=2197429 Does it work with v20c 4.1.2 android on my LG L7?
yes, the bootloader is locked, you need to unlock
Thanks, now I'm at least on to something. Does the method from the link works on v20c 4.1.2. version?
Sent from my LG-P700 using xda app-developers app
Macors said:
Thanks, now I'm at least on to something. Does the method from the link works on v20c 4.1.2. version?
Sent from my LG-P700 using xda app-developers app
Click to expand...
Click to collapse
it doesn`t matter if you have ICS or JB, it must work
I tried unlocking the bootloader with the Flash_Bootloader.bat file, but the error windows flashes only for a split second. I barely caught it and attached the screenshot of it saying "the system cannot find the path specified". What should I do now?
Phone connected in pc software mode, debuggin is on.
[Update] I moved the CWM folder directly to the local disk C and it worked, but didn't reboot the phone. I had to unplug it and then turn on. How to check if my bootloader is unlocked? I don't want any more fails with flashing the recovery ;/
Macors said:
I tried unlocking the bootloader with the Flash_Bootloader.bat file, but the error windows flashes only for a split second. I barely caught it and attached the screenshot of it saying "the system cannot find the path specified". What should I do now?
Phone connected in pc software mode, debuggin is on.
[Update] I moved the CWM folder directly to the local disk C and it worked, but didn't reboot the phone. I had to unplug it and then turn on. How to check if my bootloader is unlocked? I don't want any more fails with flashing the recovery ;/
Click to expand...
Click to collapse
you were needed to write adb reboot to rebbot your phone after, and the only way to chech the bootlaoder is to go on download mode or recovery
Everything is working, just rebooted into Recovery from the rom manager. By the way, how does this adb work? Do I have to run the .exe file after the .bin ?
Macors said:
Everything is working, just rebooted into Recovery from the rom manager. By the way, how does this adb work? Do I have to run the .exe file after the .bin ?
Click to expand...
Click to collapse
start - run cmd - cd %ADB% - and here you are
same here
Im using an lg lucid vs840 and is recently rooted, i downloaded rom manager and cyanogen mod 11, but when i try to install rom from sd card it reboots saying,
boot errer cause boot certification verify
Enter fast reboot...
Enter fast reboot...
Long time no see!
I can still use my phone but i cant install a new rom, any one help?
Thank you for reading.
lol nobody ever answers this same question many times on this site.... sorry first post but I get all my info from hereeeeee for a long time now
I flashed the new*B336 update for EMUI 5 and when i got into it i saw that there were not any system apps, i checked why and it appeared i had to install another*full_data file or smth, is there any way i can do it now ???
Btw when i try to boot into TWRP it says Your device is booting now... and does nothing
The situation is now even worst, why can`t nobody help?
Please someone help. i really need my phone back and i can`t take it for repairs.
When i try to install stock rom of EMUI 4 the install says error code - 7
failed to mount /vendor (invalid argument)
failed to mount /product (invalid argument)
I have no OS installed and i cant use HiSuite to recover using fastboot.
dload mode says the app update package does not exist when there is a corrent update.app in the dload folder on my SD card
and*i also am sure i*used the right OEMinfo file ;(
please respond someone.
TRY flash SYSTEM.IMG BOOT.IMG RECOVERY. IMG & CUSTS.IMG via ADB
Abdulla7 said:
TRY flash SYSTEM.IMG BOOT.IMG RECOVERY. IMG & CUSTS.IMG via ADB
Click to expand...
Click to collapse
Okay, i will try and see what happens and report back to you. Thanks for the response
Edit: When i try to use ADB to flash*the files to my device it says that the device is unauthorized
theAuxify said:
Edit: When i try to use ADB to flash*the files to my device it says that the device is unauthorized
Click to expand...
Click to collapse
Bootloader still unlocked?
If not, unlock it again with your code via fastboot.
Schlengge said:
Bootloader still unlocked?
If not, unlock it again with your code via fastboot.
Click to expand...
Click to collapse
Yea, the bootloader should be unlocked, when i boot up the device it says that it has been unlocked ;P
theAuxify said:
Yea, the bootloader should be unlocked, when i boot up the device it says that it has been unlocked ;P
Click to expand...
Click to collapse
Does it say "Unlocked" in bootloader mode?
On this screen I mean: Link
Schlengge said:
Does it say "Unlocked" in bootloader mode?
On this screen I mean: Link
Click to expand...
Click to collapse
Yea, says :
Phone unlocked
FRP Unlock
And if i use the command adb devices in fastboot mode no devices appear at all*D:
EDIT : I managed to flash boot.img and recovery.img without errors with the device not showing on the list of devices.
Says everything is okay
But when i try to flash system.img it shows this
C:\Users\Auxify\Desktop\Huawei\Huawei-P9-Lite>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (445202 KB)...
OKAY [ 14.775s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 14.828s
It sounds like your SD card is not working because of reasons...
Try flashing TWRP from this thread (http://forum.xda-developers.com/huawei-p9lite/how-to/guide-unlock-bootloader-twrp-root-t3405701) with fastboot. Take the recovery image out of the extracted SRKTool Huawei.
Name should be twrpp9mm.img
Report back if you are able to access recovery again. From there you should be able to recover.
Afaik it is not possible to just reflash EMUI 4 after having updated to the Beta of EMUI 5. Once you have a recovery going, try to follow the exact steps of downgrading that are here on the forums.
Schlengge said:
It sounds like your SD card is not working because of reasons...
Try flashing TWRP from this thread (http://forum.xda-developers.com/huawei-p9lite/how-to/guide-unlock-bootloader-twrp-root-t3405701) with fastboot. Take the recovery image out of the extracted SRKTool Huawei.
Name should be twrpp9mm.img
Report back if you are able to access recovery again. From there you should be able to recover.
Afaik it is not possible to just reflash EMUI 4 after having updated to the Beta of EMUI 5. Once you have a recovery going, try to follow the exact steps of downgrading that are here on the forums.
Click to expand...
Click to collapse
After installing this recovery the phone is stuck at Your device is booting now... screen when entering recovery mode D:
So no recovery is working?
Have you tried flashing Meticulus TWRP or the Nougat Revolution Recovery?
One of these has to work... It also helps you to find out where your phone is stuck. If only Nougat Recovery works, your rollback from N has not worked. That would explain why you cannot launch any Marshmellow based recoveries.
Schlengge said:
So no recovery is working?
Have you tried flashing Meticulus TWRP or the Nougat Revolution Recovery?
One of these has to work... It also helps you to find out where your phone is stuck. If only Nougat Recovery works, your rollback from N has not worked. That would explain why you cannot launch any Marshmellow based recoveries.
Click to expand...
Click to collapse
Yeah.*I can boot into recovery N B9 but when i try to flash/wipe/do anything it says cant mount /vendor /product /version
Hmm okay that's a problem...
I don't really see what to do next honestly. Somehow we need to get fastboot flash working.
Have you tried to get back to a working Nougat build?
So flash BadWolf's Revolution N ROM in TWRP or via fastboot (since TWRP does not seem to work).
Schlengge said:
Hmm okay that's a problem...
I don't really see what to do next honestly. Somehow we need to get fastboot flash working.
Have you tried to get back to a working Nougat build?
So flash BadWolf's Revolution N ROM in TWRP or via fastboot (since TWRP does not seem to work).
Click to expand...
Click to collapse
Can`t do anything,*even wipe.
After wipe says : Successful but in the log view it says
"Updating partition details...
Failed to mount '/product' (Invalid argument)
Failed to mount '/version'*(invalid argument)
Failed to mount '/vendor' (invalid argument)
...Done"
theAuxify said:
Can`t do anything,*even wipe.
After wipe says : Successful but in the log view it says
"Updating partition details...
Failed to mount '/product' (Invalid argument)
Failed to mount '/version'*(invalid argument)
Failed to mount '/vendor' (invalid argument)
...Done"
Click to expand...
Click to collapse
Have you tried this:
https://www.youtube.com/watch?v=VJRKuQf0puE
Schlengge said:
Have you tried this:
https://www.youtube.com/watch?v=VJRKuQf0puE
Click to expand...
Click to collapse
Yea, but thats not for /vendor /product /version*xD
P.s : Happy 2017 ;P
Hmm sorry but I ran out of ideas... Maybe somebody else can help you further. All the standard procedures are not working so without fully knowing what you did and not having your phone to test it is hard to say something.
Hope you will find a way to fix this.
Schlengge said:
Hmm sorry but I ran out of ideas... Maybe somebody else can help you further. All the standard procedures are not working so without fully knowing what you did and not having your phone to test it is hard to say something.
Hope you will find a way to fix this.
Click to expand...
Click to collapse
Meh, i guess ill just drive out and get it fixed xD Its a loooong way though DD
Thanks for all your help brother ;p
theAuxify said:
After installing this recovery the phone is stuck at Your device is booting now... screen when entering recovery mode D:
Click to expand...
Click to collapse
Hey try to download revolution recovery for nougat and flash it using fastboot it will work for recovery
But zip installation will fail due to ( faail to mount vendor, product and version), if anyone knows how ho fix this please help
jkmaziku said:
Hey try to download revolution recovery for nougat and flash it using fastboot it will work for recovery
But zip installation will fail due to ( faail to mount vendor, product and version), if anyone knows how ho fix this please help
Click to expand...
Click to collapse
The best, is to try to install twrpmeticulus, wipe all except external storage property, install oeminfo.zip badwolf, go back to reboot, shut down.
Restarts Dload bxxx.
I only see her.
Hi,
My ZE550KL was locked in boot with this message: "Security Error: This phone has been flashed with an unauthorized software & is locked", so i followed some tutorials and was able to install TWRP recovery (i had bootloader already unlocked). Then when trying to reinstall stock rom, i realized i had to reinstall the stock recovery. I did it and installed the stock rom with version matching with the stock recovery i installed(UL-Z00L-WW-1.17.40.1531-user). Everything was going ok, but when my newly installed stock rom was popping multiple apps stopped working an i was unable to basically do anything. So i tried reinstalling stock rom again, but this is when things collapsed. As i entered recovery to reinstall the rom, it has lots of errors from partition cache
Code:
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
. This same errors happens when i try to wipe it from the recovery, but when i erase the cache partition on fastboot it says "OK". I also tried to reinstall twrp, but apparently my bootloader was blocked again, and it says it is flashed when i try, but when rebooting it boots again on stock recovery.
So i tried just booting twrp, but then it says my bootloader is blocked and can't boot twrp. Also tried sideloading stock rom from adb, but it gets the same cache partition errors. I tried
Code:
fastboot -w
and it says OK but the cache partition errors are still there. I also tried
Code:
fastboot erase ASDF
and i get some errors.
TLDR; I'm stuck at a cycle where i have to remount cache and all other partitions via TWRP, but i can't install TWRP because my bootloader got locked again and i can't unlock it because i need to install some rom to do it, but since my cache partition is destroyed i can't install anything, neither via fastboot on pc nor from recovery on the phone.
Did you tried the unoffical unlock way? It can done via PC in fastboot mode. Also did you tried `fastboot format system` kind of commands?
TheImpulson said:
Did you tried the unoffical unlock way? It can done via PC in fastboot mode. Also did you tried `fastboot format system` kind of commands?
Click to expand...
Click to collapse
I didn't. Can you please explain how to do it? Thanks
VMokaccino said:
I didn't. Can you please explain how to do it? Thanks
Click to expand...
Click to collapse
Damn! I just noticed that you will need to be in system to gain root access. I guess then it won't work. I suggest to try `fastboot format system/userdata/cache` way as it fixed my issues with partitions multiple times.
Here you go for unoffical guide: https://forum.xda-developers.com/ze...de-unlock-bootloader-asus-unlock-app-t3405850
TheImpulson said:
Damn! I just noticed that you will need to be in system to gain root access. I guess then it won't work. I suggest to try `fastboot format system/userdata/cache` way as it fixed my issues with partitions multiple times.
Here you go for unoffical guide: https://forum.xda-developers.com/ze...de-unlock-bootloader-asus-unlock-app-t3405850
Click to expand...
Click to collapse
Well, i tried all these format commands, but nothing has changed
VMokaccino said:
Well, i tried all these format commands, but nothing has changed
Click to expand...
Click to collapse
Did you tried what this guide says: https://www.asus.com/zentalk/thread-116230-1-1.html
TheImpulson said:
Did you tried what this guide says: https://www.asus.com/zentalk/thread-116230-1-1.html
Click to expand...
Click to collapse
I tried this, but my phone is now stuck on Fastboot Mode. It doesn't matter if i press VOL + or VOL -, it always enters in Fastboot Mode
VMokaccino said:
I tried this, but my phone is now stuck on Fastboot Mode. It doesn't matter if i press VOL + or VOL -, it always enters in Fastboot Mode
Click to expand...
Click to collapse
It's because you don't have any recovery or ROM on your device. Try flashing stock recovery.
TheImpulson said:
Did you tried what this guide says: https://www.asus.com/zentalk/thread-116230-1-1.html
Click to expand...
Click to collapse
TheImpulson said:
It's because you don't have any recovery or ROM on your device. Try flashing stock recovery.
Click to expand...
Click to collapse
Well, i tried flashing all stock recovery versions i could find, but none of them worked. I guess my phone is dead.
VMokaccino said:
Well, i tried flashing all stock recovery versions i could find, but none of them worked. I guess my phone is dead.
Click to expand...
Click to collapse
Take your phone to service center I guess.
Hello guys, I ran into some trouble by trying to reset my phone to stock firmware. I followed this guide https://forum.xda-developers.com/showthread.php?t=2759495 but with the moto e4 firmware, now it bootloops to erasing and bad key. Please help, it doesnt let me boot into recovery
frederickrl said:
Hello guys, I ran into some trouble by trying to reset my phone to stock firmware. I followed this guide https://forum.xda-developers.com/showthread.php?t=2759495 but with the moto e4 firmware, now it bootloops to erasing and bad key. Please help, it doesnt let me boot into recovery
Click to expand...
Click to collapse
Update, I was able to boot into twrp, currently attemtping to flash a rom
similar problem: recovery loop
frederickrl said:
Update, I was able to boot into twrp, currently attemtping to flash a rom
Click to expand...
Click to collapse
Hello,
this is my situation:
- switchin-on my new moto e4 (XT1762)
- boot into recovery (TWRP)
- in TWRP, I am able to 'work', i.e. install LineageOS 15.1 (this is my main goal)
--- I WIPE
--- I INSTALL the lineage ZIP file (lineage 15.1 20180310 unofficial woods
--- I REBOOT
BUT, sadly, the reboot is done again into TWRP.
The installation of lineageos did not report any error.
How can I check, that what I've installed so far (TWRP and magisk) is correct and working?
Did I forget something? E.g. do I have to install GAPPS as well? Or Magisk? Or SUperSU?
Shall I try another custom ROM? Or another version of lineageOS? (Oh, yes, I tried Lineageos 15.0, but I got 'ZIP error'.
Thanks for your help!
Fussloseskriechtier said:
Hello,
this is my situation:
- switchin-on my new moto e4 (XT1762)
- boot into recovery (TWRP)
- in TWRP, I am able to 'work', i.e. install LineageOS 15.1 (this is my main goal)
--- I WIPE
--- I INSTALL the lineage ZIP file (lineage 15.1 20180310 unofficial woods
--- I REBOOT
BUT, sadly, the reboot is done again into TWRP.
The installation of lineageos did not report any error.
How can I check, that what I've installed so far (TWRP and magisk) is correct and working?
Did I forget something? E.g. do I have to install GAPPS as well? Or Magisk? Or SUperSU?
Shall I try another custom ROM? Or another version of lineageOS? (Oh, yes, I tried Lineageos 15.0, but I got 'ZIP error'.
Thanks for your help!
Click to expand...
Click to collapse
I imagine you are having the same problem that I was having. This is what I think happened, there is a particular partition which TWRP fails to erase, if this is the case I believe you are able to boot into the device by hitting start in the bootloader, hold volume down and power then select start. Tell me how it goes
TWRP loop
frederickrl said:
I imagine you are having the same problem that I was having. This is what I think happened, there is a particular partition which TWRP fails to erase, if this is the case I believe you are able to boot into the device by hitting start in the bootloader, hold volume down and power then select start. Tell me how it goes
Click to expand...
Click to collapse
Thanks for this hint, frederick.
Unfortunately, it did not work.
I rebooted to bootloader mode, then I pushed 'DOWN' and 'POWER' for several seconds - but I could not select anything - display was switched off and the device rebooted to TWRP again.
That's strange, because yesterday I've got this 'MENUE', when pushing 'DOWN'&'POWER' for selecting FACTORY, RECOVERY, ... but this does not appear now.
More facts (it might help):
- After switching on the the device, I get this 'Orange state' message.
Perhaps any other hints?
Fussloseskriechtier said:
Thanks for this hint, frederick.
Unfortunately, it did not work.
I rebooted to bootloader mode, then I pushed 'DOWN' and 'POWER' for several seconds - but I could not select anything - display was switched off and the device rebooted to TWRP again.
That's strange, because yesterday I've got this 'MENUE', when pushing 'DOWN'&'POWER' for selecting FACTORY, RECOVERY, ... but this does not appear now.
More facts (it might help):
- After switching on the the device, I get this 'Orange state' message.
Perhaps any other hints?
Click to expand...
Click to collapse
I have no other recommendations as to what to do. Just flash stock firmware with rsdlite and everything will be back to normal, if you have any data that you need to back up you can use TWRP to transfer the files to a PC
Fussloseskriechtier said:
Thanks for this hint, frederick.
Unfortunately, it did not work.
I rebooted to bootloader mode, then I pushed 'DOWN' and 'POWER' for several seconds - but I could not select anything - display was switched off and the device rebooted to TWRP again.
That's strange, because yesterday I've got this 'MENUE', when pushing 'DOWN'&'POWER' for selecting FACTORY, RECOVERY, ... but this does not appear now.
More facts (it might help):
- After switching on the the device, I get this 'Orange state' message.
Perhaps any other hints?
Click to expand...
Click to collapse
In twrp select reboot bootloader. In bootloader, tap volume until you see "start". Tap power. Do not try holding buttons together in bootloader. It doesn't do anything. Single taps.
madbat99 said:
In twrp select reboot bootloader. In bootloader, tap volume until you see "start". Tap power. Do not try holding buttons together in bootloader. It doesn't do anything. Single taps.
Click to expand...
Click to collapse
After "REBBOT BOOTLOADER" in TWRP, I get a black screen, where (on the very bottom) there are two lines: => FASTBOOT mode
=> device unlocked
Tapping or holding the volume&power buttons does not work in this state.
As mentioned before, by any reason I do not have this nice menue anymore, the one with RECOVERY, START, ...
So this could be the problem, right? Is my bootloader not working properly? Which part is telling the device to startup either in TWRP (=recovery) or into the Bootloader/System?
Mmmmh....
Fussloseskriechtier said:
After "REBBOT BOOTLOADER" in TWRP, I get a black screen, where (on the very bottom) there are two lines: => FASTBOOT mode
=> device unlocked
Tapping or holding the volume&power buttons does not work in this state.
As mentioned before, by any reason I do not have this nice menue anymore, the one with RECOVERY, START, ...
So this could be the problem, right? Is my bootloader not working properly? Which part is telling the device to startup either in TWRP (=recovery) or into the Bootloader/System?
Mmmmh....
Click to expand...
Click to collapse
Fastboot mode is bootloader. Why the options aren't there I couldn't tell you. I see you flashed a rom for woods. Do you have the mediatek version? Hopefully you didn't flash wood stuff on a Perry device. Bootloader may be different. I have Qualcomm. Was that option ever there in fastboot mode?
This is how to fix the recovery loop. And possibly boot you in to whatever is left of your os.
madbat99 said:
Fastboot mode is bootloader. Why the options aren't there I couldn't tell you. I see you flashed a rom for woods. Do you have the mediatek version? Hopefully you didn't flash wood stuff on a Perry device. Bootloader may be different. I have Qualcomm. Was that option ever there in fastboot mode?
This is how to fix the recovery loop. And possibly boot you in to whatever is left of your os.
Click to expand...
Click to collapse
Thanks again for your hints!
First of all, my device variant is XT1762, i.e. woods. I did not use PERRY software.
The bootloader options (RECOVERY MODE, FACTORY MODE, etc.) were there, but it seems I've somehow broken this peace of code... I believe this is the reason of my problems. Unfortunately I do not understand the Android boot sequence...
However, I tried >> fastboot erase misc << via terminal:
result:
erasing 'misc'...
FAILED (remote: partition table doesn't exist)
finished. total time 0.009s
I double checked it vie file manager in TWRP: there is no MISC folder.
It seems, my only option is to go back to stock ROM... :crying:
Fussloseskriechtier said:
Thanks again for your hints!
First of all, my device variant is XT1762, i.e. woods. I did not use PERRY software.
The bootloader options (RECOVERY MODE, FACTORY MODE, etc.) were there, but it seems I've somehow broken this peace of code... I believe this is the reason of my problems. Unfortunately I do not understand the Android boot sequence...
However, I tried >> fastboot erase misc << via terminal:
result:
erasing 'misc'...
FAILED (remote: partition table doesn't exist)
finished. total time 0.009s
I double checked it vie file manager in TWRP: there is no MISC folder.
It seems, my only option is to go back to stock ROM... :crying:
Click to expand...
Click to collapse
I think the partitions are different in mtk version. But I would try flashing stock.
I have exactly the same problem after trying to flash lineage 14.1 to my XT1762.
Unfortunately I have only a TWRP Backup of my stock system before the flash and recovering that didn't fix the problem.
Fussloseskriechtier said:
Perhaps any other hints?
Click to expand...
Click to collapse
MiGri said:
I have exactly the same problem after trying to flash lineage 14.1 to my XT1762.
Unfortunately I have only a TWRP Backup of my stock system before the flash and recovering that didn't fix the problem.
Click to expand...
Click to collapse
I know what a pain in the ass my Perry variant was just to get the root going, so I can just imagine your frustration.
Did you guys take the update they're pushing out on the phones? Check. Some of the updates might be forced or you may accidentally said Okay and didn't realize it- that could be the reason why you're having trouble. The significant other got an update on the E4, and now can't do root.
I was able to get my phone back to work using https://forum.xda-developers.com/moto-e4/development/rom-original-stock-firmware-woods-twrp-t3766902
Stock ROM used to repair bootloader
Articul8Madness said:
I know what a pain in the ass my Perry variant was just to get the root going, so I can just imagine your frustration.
Did you guys take the update they're pushing out on the phones? Check. Some of the updates might be forced or you may accidentally said Okay and didn't realize it- that could be the reason why you're having trouble. The significant other got an update on the E4, and now can't do root.
Click to expand...
Click to collapse
Hello!
In the meantime I actually deleted everything and flashed the Stock ROM on my XT1762.
After that, my Bootloader menue (RECOVERY MODE, FACTORY MODE, START, ...) appeared again...
I felt lucky and started the whole procedure again: use TWRP, backup, delete Cache, Flash custom ROM, delete Cache, restart... and finally, I got lineageOS 15.1 and CrDroid running on my phone.
Now I use CrDroid, because LineageOS 15.1 did not Support my SIM Card... ? However, I am happy with CrDroid: fast, slim, nice looking, ...
So in the end, it seems that I deleted a specific part in my Flash which caused the "boot Loop". But I could repair it by flashing the Stock ROM again.
Thanks guys, you're doing a good Job!
Buy!
Fussloseskriechtier said:
Hello!
In the meantime I actually deleted everything and flashed the Stock ROM on my XT1762.
After that, my Bootloader menue (RECOVERY MODE, FACTORY MODE, START, ...) appeared again...
I felt lucky and started the whole procedure again: use TWRP, backup, delete Cache, Flash custom ROM, delete Cache, restart... and finally, I got lineageOS 15.1 and CrDroid running on my phone.
Now I use CrDroid, because LineageOS 15.1 did not Support my SIM Card... ? However, I am happy with CrDroid: fast, slim, nice looking, ...
So in the end, it seems that I deleted a specific part in my Flash which caused the "boot Loop". But I could repair it by flashing the Stock ROM again.
Thanks guys, you're doing a good Job!
Buy!
Click to expand...
Click to collapse
I'm also stuck in boot loop... What directories/files did you delete? Have backup of stock rom, but restore fails:
This /data backup was made with f2fs file system! The backup may not boot unless you change back to f2fs
Failed to mount /data (Invalid argument)
TWRP says that file system of /data is ext4. Not possible to change or repair the file system in TWRP with Wipe / Advanced wipe / Repair or change file system. Result:
Error changing file system
or
/sbin/e2fsck -fp /dev/block/mmcblk0p27 process ended with error: 8
Phone is always starting in TWRP ending with:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
In terminal no problem to create (mkdir) and delete directories.
Flashing of lineage 14.1 or 15.1 for woods ends also with:
Failed to mount '/data' (Invalid argument)
This command in TWRP terminal didn't work:
fastboot erase misc
erasing 'misc'...
FAILED (remote: Partition table doesn't exist)
There is no misc folder.
Any ideas?
Thank you in advance!
pancobe said:
I'm also stuck in boot loop... What directories/files did you delete? Have backup of stock rom, but restore fails:
This /data backup was made with f2fs file system! The backup may not boot unless you change back to f2fs
Failed to mount /data (Invalid argument)
TWRP says that file system of /data is ext4. Not possible to change or repair the file system in TWRP with Wipe / Advanced wipe / Repair or change file system. Result:
Error changing file system
or
/sbin/e2fsck -fp /dev/block/mmcblk0p27 process ended with error: 8
Phone is always starting in TWRP ending with:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
In terminal no problem to create (mkdir) and delete directories.
Flashing of lineage 14.1 or 15.1 for woods ends also with:
Failed to mount '/data' (Invalid argument)
This command in TWRP terminal didn't work:
fastboot erase misc
erasing 'misc'...
FAILED (remote: Partition table doesn't exist)
There is no misc folder.
Any ideas?
Thank you in advance!
Click to expand...
Click to collapse
Just flash stock firmware with rsdlite, it's the simplest way to go. Then if you'd like flash your rom
frederickrl said:
Just flash stock firmware with rsdlite, it's the simplest way to go. Then if you'd like flash your rom
Click to expand...
Click to collapse
Thank you for the hint on rsdlite, didn't know the program! Unfortunately I have two problems, have only access to an old XP box (I'm normally on a mac), and rsdlite doesn't recognise the phone, driver problem presumably... And the program doesn't recognise the format of the backup I made with TWRP...
Is it possible to repair the file system on the phone via terminal? Or to delete parts of the system safely and reinstall the stock system? The other guy apparently did something like that. Or to unpack a custom rom and place the parts via terminal so it can install on next boot?
Thank you!
Did following check:
mount /data
mount: '/dev/block/mmcblk0p27'->'/data': Invalid argument
e2fsck -n /dev/block/mmcblk0p27
e2fsck 1.42.9 (28-Dec-2013)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p27
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Would it be safe to rmdir /data and mkdir /data ?
Thanks...
pancobe said:
Thank you for the hint on rsdlite, didn't know the program! Unfortunately I have two problems, have only access to an old XP box (I'm normally on a mac), and rsdlite doesn't recognise the phone, driver problem presumably... And the program doesn't recognise the format of the backup I made with TWRP...
Is it possible to repair the file system on the phone via terminal? Or to delete parts of the system safely and reinstall the stock system? The other guy apparently did something like that. Or to unpack a custom rom and place the parts via terminal so it can install on next boot?
Thank you!
Click to expand...
Click to collapse
Rsdlite is not meant to install your twrp backup. It's for installing the official firmware package. And you need to install moto drivers of course.