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?
Related
Hey guys,
I got a moto g here which has a bootloop (cyanogenmod is installed).
I tried to boot TWRP but it also doesnt boot up fully - only showing the TWRP splash screen.
So I went and got the factory image and flashed that with fastboot - but even though there were no error messages it seems that nothing actually sticked on the phone.
When I try to boot it still booting CM and when I try to enter stock recovery its still the TWRP?!
Tried flashing CWM but its still TWRP..
Any ideas on how to fix it, or is this problem "known" or smth?
Seems like this is a hardware failure - like internal memory broken.
zroice said:
Hey guys,
I got a moto g here which has a bootloop (cyanogenmod is installed).
I tried to boot TWRP but it also doesnt boot up fully - only showing the TWRP splash screen.
So I went and got the factory image and flashed that with fastboot - but even though there were no error messages it seems that nothing actually sticked on the phone.
When I try to boot it still booting CM and when I try to enter stock recovery its still the TWRP?!
Tried flashing CWM but its still TWRP..
Any ideas on how to fix it, or is this problem "known" or smth?
Seems like this is a hardware failure - like internal memory broken.
Click to expand...
Click to collapse
Try using the mfastboot package, install the Motorola USB drivers if you haven't done so and flash the ROM, as per the instructions here:
https://forum.xda-developers.com/showpost.php?p=71328823&postcount=915
Seeing as I assume your phone responds to key presses, you can ignore the dismantling part of the instructions provided.
aha360 said:
Try using the mfastboot package, install the Motorola USB drivers if you haven't done so and flash the ROM, as per the instructions here:
https://forum.xda-developers.com/showpost.php?p=71328823&postcount=915
Seeing as I assume your phone responds to key presses, you can ignore the dismantling part of the instructions provided.
Click to expand...
Click to collapse
thanks for your reply!
unfortunately I already tried to install the stock rom with fastboot and mfastboot - every step would be processed, but in the end the phone was just in the same state - with twrp and cyanogenmod on it - both not booting,
Funny thing is that when i boot to twrp i can actually adb to the phone while it bootloops twrp - I tried placing and removing files in data but they would just disappear or reapper aka the device was still just as before.
Whats weird though is that I never get a single error message - it just takes all commands and stuff but they dont stick?! never had a phone like that. Usually the flashes fail or smth if the memory is broken,
zroice said:
thanks for your reply!
unfortunately I already tried to install the stock rom with fastboot and mfastboot - every step would be processed, but in the end the phone was just in the same state - with twrp and cyanogenmod on it - both not booting,
Funny thing is that when i boot to twrp i can actually adb to the phone while it bootloops twrp - I tried placing and removing files in data but they would just disappear or reapper aka the device was still just as before.
Whats weird though is that I never get a single error message - it just takes all commands and stuff but they dont stick?! never had a phone like that. Usually the flashes fail or smth if the memory is broken,
Click to expand...
Click to collapse
That's massively odd - have you tried unbricking the device by forcefully bricking it then unbricking it here:
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
https://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788
If you have tried everything, then I cannot help you any further sadly.
@zroice
try
Code:
fastboot boot TWRP.img
maybe flashed TWRP can't mount /data or other partition
Hey,
Quick rundown: Stuck in a bootloop to some sort of empty bootloader screen which has the readout:
"Start/Restart Bootloader/Recovery Mode/Power Off"
"Press volume key to select, and press power key to select"[Regarding above options]
"FastBoot Mode
PRODUCT_NAME - sdm845
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - [Gonna leave this out for now]
SECURE BOOT - yes
DEVICE STATE - unlocked" [this line is in red]
Every choice besides Power Off returns me to the same window. What can I do to recover from this?
Background:
So I was trying to update my OP6 to the current OxygenOS while keeping my root using TWRP and Magisk, which I've done in the past without any issue(i.e. go in recovery flash OS, flash current TWRP, reboot back to recovery, flash current Magisk as I understand it). However this time I was running into an issue flashing the Oxygen update getting an error that said it "failed to map file" for the zip. My first instinct was to update TWRP to see if the newest version didn't run into this issue so I flashed that followed by the current Magisk(no reboot in between). After booting back to standard operations everything seemed fine. I went back into recovery and tried the OS update again, but hit the same issue.
I couldn't find anything specific to OP6 with this issue, but similar questions with other devices suggested clearing the dalvik cache, which I tried to no useful effect. Then I came across this thread (forums.oneplus.com/threads/oxygen-os3-i-have-a-problem-please-help.440587/page-2 too new to hyperlink) and did what I think really messed me up which was boldly follow this guy's advice to do an advanced wipe of everything but internal storage(I also left USB storage intact) from TWRP. This failed to fix the issue with the file mapping error when I subsequently tried to flash the update, though I was able to flash TWRP and Magisk successfully again before rebooting and ending up in this loop.
Any assistance in fixing this or general tips on how to not be foolish when messing around with this stuff is greatly appreciated.
Update:
So I followed the advice gleaned from the resourceful person here(https://forum.xda-developers.com/oneplus-6t/help/bootloader-baseband-versions-blank-t3927565) to try working with the device from my computer with fastboot. At first it would recognize the device as "Android" but be unable to find a driver for it and adb/fastboot both failed to recognize it as a device. After installing MiniTool(more as a way to backup what was on the SD card) the proper device driver also got installed and I was able to access it with fastboot; I ran into similar issues as the linked thread above, solved it by switching to b(still failed) then back to a.
Currently I've got it booted into TWRP and I'm working on getting the current Oxygen .zip copied onto the phone storage but the transfer keeps failing after moving a negligible amount.
Update 2:
Via TWRP was able to sideload the current up-to-date standard OS onto it, however my Google backup seems to have decided to disappear on me and the only OP backup I have is ages old. Anyone have recommendations on data recovery tools?
next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.
NickTheHuy said:
next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.
Click to expand...
Click to collapse
Good to know, thanks for the info!
I assume that happened when I messed around with advanced wipe, do you know which of the folders I selected that would have been under? And just for future awareness, would that have not occurred had I just used TWRP's standard wipe instead?
You can run a program that will install 9.0.6 from scratch, running a batch file...
Save my life before yesterday....
Your device is bricked
If able to access the TWRP recovery then boot into twrp and try to get all the data stored in your computer.
Then use the Qualcomm flash tool to completely recover from your hard bricked OP6.
from here https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
Then its easy, again unlock boot-loader flash TWRP and magisk.
Hello. I'm having trouble installing TWRP on my Pixel (sailfish) phone. Here's a detailed rundown to where I'm now.
I messed up by flashing the .zip file instead of booting from the .img. I restored the factory image following the instructions on the Factory Images page on Google Developers. Following that, I retried by closely following the instructions (booting into system, setting up PIN, enable debugging, rebooting into bootloader, etc.) Upon trying to install the .zip from the temporary TWRP boot, I get the errors
Code:
Failed to mount /system_data
Failed to mount /vendor
After this I'm unable to boot into recovery. Phone will get to Google screen, then shutdown and boot into system. I've tried a couple of things I've found online:
tried installing Verified Boot Signer with same errors
tried different versions of TWRP
tried factory resetting then wiping data from temporary TWRP boot
tried mounting partitions manually from menu; can only get vendor to mount
At this point I'm not sure what I might be missing. My goal is to install LineageOS + microG and rooting the device.
(Originally I tried using the Lineage Recovery for this following instructions unsuccessfully, so I'm trying TWRP instead. I'm including this in case it might have any relevance.)
Thanks in advance.
I dont have pixel,if pixel have 2 slots,u can try this way
Android = Fastboot mode.
PC to android = Fastboot boot twrp.img for temporary twrp.
Android = will display twrp,click install,pick twrp.img in android,click install ram disk,reboot system
Done
Try to reboot into recovery...it should be twrp recovery in permanently
Hello,I came to the same problom today,I tried to flash a LineageOS following this,and then install TWRP successfuly,It seemed that the latest google factory image was incompatitive with TWRP,that two partitions seem are new things that cannot be recognized by TWRP.Sorry for my poor English.
edit:It turns out no use,the TWRP app would crash and Recovery was the same.
edit again: I tried one older version of TWRP which is twrp-3.1.1-1,and It worked!
Hello everyone,
The starting situation is the Google Pixel of my mother was stuck on android 8.0. While showing there was an update available, the update would always fail to install after the reboot in the process. I found advice to factory reset the phone and then update, but this didn't help.
So my first thought was, if the update won't install the normal way I will do it manually. Google OTA installation guide says, get file (latest), reboot to recovery, plug in to USB, choose apply update by adb.
At this point the guide loses me, because the recovery screen I get to only lists reboot, reboot bootloader, simlock tool and device info tool (see picture). The device info will only tell "failed to update device info". The simlock tool just says "failed to enable simlock". Further while on this screen the phone isn't visible as an ADB device any more.
Next thing to try cause this didn't work was getting the image file (latest) from Google and flashing it through fastboot flash all, which led to a boot loop and the phone not starting at all. So I went and flashed back to the android 8 that was on it before and the phone booted again, but I'm still not any step further.
Next idea was maybe the recovery is broken somehow, so I went to install TWRP. Following the instructions I copied the latest version zip onto the phone and booted the img through fastboot. So far everything is fine, but when I install the zip I will get several errors about "can't mount /persist". And the installation won't work.
At this point I am out of ideas, so maybe someone here can tell me if and how this can be fixed? I wasn't able to find any information on this issue, aside from some xiaomi phones can show similar errors with the /persist partition and TWRP.
Any help would be welcome.
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.