My Huawei Ideos S7 is no longer booting normally.
Everytime I turn it on, it boots directly to the recovery partition. I had to use fastboot to overwrite my recovery partition with a working boot.img just to boot into my device.
My device doesn't have a misc partition. I don't know what can be causing this.
Since this is a QSD8250 device, I am thinking there might be something radio side causing this. Anyone can give me some hints as to what I can do?
I haven't done an md5 on the mtd yet, but I am guessing this is a result of something else.
Related
Hello, everyone.
So basically this is my issue. One day at work my Moto G restarted randomly and has been stuck in a bootloop ( boot animation cycles infinitely ).
I can access fastboot, booting to recovery freezes on TWRP logo.
My phone is rooted, unlocked and etc. I have tried flashing stock firmware, no changes, not even my custom boot logo and animation don't change.
I have tried using fastboot to erase everything and format but formatting fails saying this filesystem cannot be formatted.
I can access my files by booting into another recovery using fastboot boot recovery.img ( tried with PhilZ ) although it shows everything as it was before this all this ( all files gone, only directories left ).
I noticed that I could use ADB while stuck at TWRP logo. I tried pushing roms and using booted PhilZ to find them but they never appear, I can only push to /tmp, anything else doesn't exists although is shown through booted PhilZ.
I have tried using mkfs.ext4 to format my filesystem, everything went as it should but nothing changed.
TL;DR Bootloop, recovery does not open, fastboot flashing does nothing, adb push doesn't push anything
What the hell is going on with my phone? Any ideas people?
Somehow, your file system can't be accessed....was your phone encrypted?
itouchables said:
Somehow, your file system can't be accessed....was your phone encrypted?
Click to expand...
Click to collapse
It wasn't, I never encrypted it.
Also fastboot getvar all shows that my partition type is RAW.
Shouldn't it be F2FS or EXT4?
Maybe anyone has a proper partition mount point list for the Moto G?
I would try mkfs.ext4 formatting every possible mount point (cache,data,system and etc)
For example dev/block/mmcblk0p38
I found a Moto X mount point list but I have no clue if it's the same or not
Aequus.Mihi said:
Hello, everyone.
So basically this is my issue. One day at work my Moto G restarted randomly and has been stuck in a bootloop ( boot animation cycles infinitely ).
I can access fastboot, booting to recovery freezes on TWRP logo.
My phone is rooted, unlocked and etc. I have tried flashing stock firmware, no changes, not even my custom boot logo and animation don't change.
I have tried using fastboot to erase everything and format but formatting fails saying this filesystem cannot be formatted.
I can access my files by booting into another recovery using fastboot boot recovery.img ( tried with PhilZ ) although it shows everything as it was before this all this ( all files gone, only directories left ).
I noticed that I could use ADB while stuck at TWRP logo. I tried pushing roms and using booted PhilZ to find them but they never appear, I can only push to /tmp, anything else doesn't exists although is shown through booted PhilZ.
I have tried using mkfs.ext4 to format my filesystem, everything went as it should but nothing changed.
TL;DR Bootloop, recovery does not open, fastboot flashing does nothing, adb push doesn't push anything
What the hell is going on with my phone? Any ideas people?
Click to expand...
Click to collapse
Hi! did you find a solution?!
Oliverrlh said:
Hi! did you find a solution?!
Click to expand...
Click to collapse
No. Turns out my phone memory chip was corrupted due to flashing
Aequus.Mihi said:
No. Turns out my phone memory chip was corrupted due to flashing
Click to expand...
Click to collapse
I think I might have a similar situation. Can you give me an advice on how to confirm this?
The only difference in the circumstances is that my fiance's moto g has a custom recovery on it then she tired to install the 5.1 update. Then it would boot into the OS and after while would shut down then go to the recovery. I thought I had solved the issue by doing a factory reset. Everything was going fine until I turn it off. Now I get the boot animation and then a black screen. I can get the load screen on the custom recovery but that is it The computer can still recognize the phone.
Does this sound like your situation?
Icon000 said:
I think I might have a similar situation. Can you give me an advice on how to confirm this?
The only difference in the circumstances is that my fiance's moto g has a custom recovery on it then she tired to install the 5.1 update. Then it would boot into the OS and after while would shut down then go to the recovery. I thought I had solved the issue by doing a factory reset. Everything was going fine until I turn it off. Now I get the boot animation and then a black screen. I can get the load screen on the custom recovery but that is it The computer can still recognize the phone.
Does this sound like your situation?
Click to expand...
Click to collapse
That's the same situation I was in.
Even if you try to flash another ROM, it will never install.
You can't modify any files because the memory is ****ed.
I sold the phone for parts and bought a S4
Hi,
today, after performing a TWRP backup, something went wrong and since then I can't boot my phone.
It started with a bootloop. I can boot into bootloader, so I got that at the very least,
but I can't even boot into recovery, the phone will display TWRP logo briefly and then reboot.
I can sometimes boot into recovery - sometimes it works, I don't know why.
Phone: XT1023, used to have Lollipop 5.1.1 / CM 12.1
Bootloader 41.1A
What can I try? I tried reflashing recovery image and gtp.bin to no avail.
Okay, so I got it to work by going into recovery (when possible) and installing fresh CM image.
The recovery still behaves strangely, though, I tried restoring and older backup (which incldes system and data partition) and it randombly rebooting half way through the process. I also noticed some filesystem problems in dmesg earlier when the fresh CM boot up. Maybe there is a filesystem corruption either in the backup or on the device?
Recovery randomly rebooting on me is something I don't really like...
EDIT: this is what happend in recovery:
Code:
<3>[ 79.941057,0] F2FS-fs (mmcblk0p36): invalid segment number 7101692
<1>[ 79.941227,0] Unable to handle kernel paging request at virtual address f4482f80
What the hell is going on there?
Okay, so after doing some more testing, it seems that f2fs on my data partition gets randomly corrupted. I have no idea what's causing this. Might this be a hardware problem? I'm going to try ext4 instead...
The following fastboot command should resolve the issues: (Note that internal storage will be erased.)
fastboot erase userdata
lost101 said:
The following fastboot command should resolve the issues: (Note that internal storage will be erased.)
fastboot erase userdata
Click to expand...
Click to collapse
Thanks.
Weird thing is, F2FS errors continued even on a newly formated data partition. I used mkfs.f2fs to make a fresh filesystem, but when mounted or checked with fsck.f2fs, even such new filesystem contained errors. I'm sticking with ext4 for now, but I have a feeling there's something very wrong with my phone.
After flashing TWRP 3.1.0.0 from USB-OTG to my XT1039 the phone boots to TWRP and not into system.
The "funny" thing is that if i keep my USB-OTG stick connected after hitting reboot the system boots. It gets even funnier. If i disconnect the stick the phones goes blank (or powers off) immediately. I checked the stick, there are no partitions, besides the storage partition i created.
Does anyone have an idea what i did wrong to achieve this strange behaviour?
EDIT:
Looks like i flashed recovery.img to boot partition. After manually chosing to install boot.img to recovery partition the system boots, but setup assistant crashes. Seems i'm going to have a long night...
Looks like a complete reinstall is necessary, and if you have to use a flashable ZIP instead of just the recovery image to install the recovery, then do that. In the meantime, try installing the boot.img and recovery.img to the correct partitions.
Got it to work, but only after flashing boot.img to recovery partition and wipe all partitions. When i flash to boot.img, reboot takes me to recovery. When i flash to recovery, system boots, but to get to recovery again i have to flash recovery.img to boot via adb.
All in all very strange and i have no idea what i can do in order to make boot and recovery work side by side.
Hi,
this is my first post on this forum, so please let me know if you are missing any information …
My problem: I'm experiencing a boot loop with my Nexus 5 after having changed its damaged battery. I didn't use it for a long time because of this damage. Now, it does start the boot sequence again, but only to the "circle" animation which it keeps showing indefinitely.
The circumstances:
I never tried to root the phone
USB debugging is not (and cannot be) enabled
I'm completely sure the problem is not caused by the power button (seems to be a common cause)
stock recovery is reachable
an old version of ClockWorkMod Recovery (from this thread) is bootable
three tested versions of TWRP won't boot
What I tried:
I unlocked the bootloader. With both the stock recovery and CWM, I tried to
wipe the device / the cache partition
flash a stock image (directly downloaded from the Google developer page)
flash a ResurrectionRemix image
None of these worked. It seems that the recovery systems are not able to write on or even to mount the necessary partitions. As the stock recovery apparently needs access to /cache for adb sideload, any attempt to flash anything results in an error message. CWM is able to sideload the zip file, but writing the image fails.
I furthermore tried the "factory" (not OTA) image from Google with its flash-all.sh script which tries to also update boot loader and other things via fastboot – every single one of these update attempts failed as well.
So, my question is: Does anyone of you know of a way to get my phone working again?
Many thanks in advance, best regards
Hørk
Hørk said:
Hi,
this is my first post on this forum, so please let me know if you are missing any information …
My problem: I'm experiencing a boot loop with my Nexus 5 after having changed its damaged battery. I didn't use it for a long time because of this damage. Now, it does start the boot sequence again, but only to the "circle" animation which it keeps showing indefinitely.
The circumstances:
I never tried to root the phone
USB debugging is not (and cannot be) enabled
I'm completely sure the problem is not caused by the power button (seems to be a common cause)
stock recovery is reachable
an old version of ClockWorkMod Recovery (from this thread) is bootable
three tested versions of TWRP won't boot
What I tried:
I unlocked the bootloader. With both the stock recovery and CWM, I tried to
wipe the device / the cache partition
flash a stock image (directly downloaded from the Google developer page)
flash a ResurrectionRemix image
None of these worked. It seems that the recovery systems are not able to write on or even to mount the necessary partitions. As the stock recovery apparently needs access to /cache for adb sideload, any attempt to flash anything results in an error message. CWM is able to sideload the zip file, but writing the image fails.
I furthermore tried the "factory" (not OTA) image from Google with its flash-all.sh script which tries to also update boot loader and other things via fastboot – every single one of these update attempts failed as well.
So, my question is: Does anyone of you know of a way to get my phone working again?
Many thanks in advance, best regards
Hørk
Click to expand...
Click to collapse
Ever fix it?
Hello!
I wanted to update my oneplus 8 from 11.0.4.4 to newest version. OTA was not working idk why. I had magisk in place and I patched magisk to second partition or something like that [I dont remember how it was called] - I'm sure this is the reason of the problems. I turned off devices and wanted to boot into recovery, but suddenly it boot into Qualcomm crash dump mode with message: Attempted to kill init! exitcode: 0x00007f00 do_exit - that's all. I can't boot the system, I can;t boot into recover, I flashed patched boot, I flashed recovery - none of these works. Fastboot is present and recognized by PC.
First question can I do some backup through fastboot? To be honest I was not prepared for such problems. APKs are not even such a problem I care more about photos, documents and other data.
Can I flash some rom and restore phone back to life without wiping my personal data?
Please can you help me? I tried with some tutorials, but no success...
Maybe an idea would be to load TWRP recovery and then do backup, but how to boot into recovery when even after flashign recovery or booting via fastboot it enters in qualcoom crash dump mode. Something must be corrupted, but is it possible to fix some partition just in order to flash recovery to do backup of the files?
Okay I managed to get back to normal - since like I mentioned i patched the magisk into second slot, then probably this corrupted something. What has helped me is this: fastboot --set-active=b
It was not working via powershell I had to launch CMD and then it worked I switched slot to "b" and phone booted normally.
Hi, I'm facing the same problem but probably not for the same cause.
I'm right now on PE12 (with PE recovery) and wanna install TWRP recovery to then move on another A12 based ROM (Evox).
Basically my goal is to replace PE recovery with TWRP. So when trying to install twrp after downloading the ZIP file onto the phone, when I fastboot the img file, it sends me to the crash Dump mode.
How can I fix this? please note I have no issue booting to the main OS.