Allowed CM to update to latest snapshot, now stuck in bootloop - Nexus 4 Q&A, Help & Troubleshooting

My wife's N4 was on an April snapshot build of CM 13 and started behaving a bit weird (Trebuchet crashing). Factory reset fixed it but then it started happening again, so I decided to flash the latest (August) snapshot. Downloaded successfully through the built-in update option, but when I told it to install it tried to restart and then just got stuck with the screen flashing off and on.
It doesn't even get to the CM logo, just flashes screen off then on infinitely. I can reboot into bootloader but NOT into recovery because it does the same flashing screen thing.
I can't currently get ADB to recognise the phone when I'm in bootloader so I can't do anything at all right now. Scratching my head a bit as I've tried a couple of different drivers and still can't get ADB to see the phone.
Any ideas?

Install. Minimal adb and fast boot to your pc it will give you the appropriate drivers

Boot into fastboot mode then use volume buttons to choose recovery as the reboot option
Sent from my Nexus 4 using Tapatalk
---------- Post added at 06:11 AM ---------- Previous post was at 06:10 AM ----------
Sorry if you already tried this but it worked for me today when I bootlooped
Sent from my Nexus 4 using Tapatalk

Adb commands don't work in boot loader mode. Use fast boot commands to flash twrp, then use twrp to wipe cache. If it is still stuck, use twrp to wipe data too.

Related

Nexus 4 Stuck on Boot Animation

Hi, I just tried Modding on Android for the first time. I went about this using adb commands in Ubuntu Terminal. I unlocked my bootloader then (I think) I flashed twrp recovery onto my Nexus 4 (Build Number LMY470.) When I went to check if my flashing of twrp was successful, it brought me stock recovery. I saw online that someone was in the same situation and they used the
Code:
fastboot erase cache
so I tried the same. In the terminal it looked like it was successful but as soon as I went to recovery mode it brought me to stock recovery again. In the recovery menu it said something about failing unmount or something. After this I tried turning my phone on and it has been stuck in the boot animation for the past 50 minutes. What should I do? Thanks!
EDIT: I factory reset my device after an hour and a half of not knowing you could get out of the boot animation. Now my recovery works. No replies needed.

OP2 soft bricked, can't access recovery, not recognized by laptop

Hey,
Very strange query but here goes. Rooted phone a while back and installed CM13 along with recovery. Was trying to update TWRP{ by downloading .img from their website, went to flashing, selected the file and hit recovery. Said it was succesful so attempted to reboot. Plugged in to charge and was charging but when I tried to switch it on, it was stuck in Cyanogen Bootloop (blue alien stayed on the screen for 10+ minutes). Tried rebooting to recovery by hitting power + volume down and instead of booting to TWRP, it takes me to a Cyanogen recovery screen where I see the following options:
Cyanogen Recovery.
- Reboot system now
- Apply update
- - -apply from ADB
- - -choose from emulated
- Factory reset
- - -system reset
- - -full factory reset
- - -wipe cache
- Advanced
- - -reboot recovery
- - -reboot to bootloader
- - -Wipe system partition
- - -view recovery logs
Here's what I tried as troubleshooting. Tried to do a system reset, factory reset and wiped cache and tried to restart my phone but no luck. Still stuck in boot loop with CM logo. Tried to reboot to bootloader but the screen is stuck with the 1+ logo for about 5 mins so gave up on that.
Basically, right now I can't access anything on the phone, can't find any way to reinstall a ROM and when I plug it into my Macbook, it is not recognised. So I'm screwed sideways. I had TWRP recovery set up so I have no clue how this happened but can anyone please help me with this.
If data isn't at risk try the Qualcomm recovery tool one the oneplus forum it's by nammand bhal (definitely butchered the name) but all data is lost and resets the phone to out of box conditions locked bootloader and Oos 2.2.1 so this is often a last measure (tool is Windows but may have Mac variant and the file is quite big)
My suggestion is to try to boot to bootloader again and flash TWRP
hmm mac book I don't have much experience with those
If you have a Windows pc you can use adb or on Mac if it has it. Also when it come to being found by a computer in recovery it should but again don't have a mac
CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.
AJay27 said:
CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.
Click to expand...
Click to collapse
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.
justicesourglide said:
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.
Click to expand...
Click to collapse
Actually I don't think the issue was with the Macbook since I have unlocked, flashed custom recoveries and sideloaded ROMs on several devices including OP2, OP3, Nexus 5, etc on mine. It might have been some accidental flashing error, which unfortunately ended up bricking your device.

Help Needed: Phone stuck on Motorola's warning screen.

Ok so recently I was backing up and wiping my phone as a procedure I do every couple of months to make sure everything's up-to-date.
But when I tried to boot into it this time, it got stuck on Motorola's unlocked bootloader screen and won't boot into recovery mode or turn off.
Everytime I try to turn it off, it reboots to said screen and gets stuck. My previous root was phh's Superuser, and I was upgrading it to Magisk's root.
I was also upgrading twrp 3.0.0 athene to twrp 3.1.1.
Currently I have the stock firmware downloaded from AndroidSages and the OTA Update pulled from my phone, as well as all the files stated above.
All I'm trying to do is boot into recovery mode, as I can make my way from there. Any help would be greatly appreciated.
AiAlpha said:
Ok so recently I was backing up and wiping my phone as a procedure I do every couple of months to make sure everything's up-to-date.
But when I tried to boot into it this time, it got stuck on Motorola's unlocked bootloader screen and won't boot into recovery mode or turn off.
Everytime I try to turn it off, it reboots to said screen and gets stuck. My previous root was phh's Superuser, and I was upgrading it to Magisk's root.
I was also upgrading twrp 3.0.0 athene to twrp 3.1.1.
Currently I have the stock firmware downloaded from AndroidSages and the OTA Update pulled from my phone, as well as all the files stated above.
All I'm trying to do is boot into recovery mode, as I can make my way from there. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Hold power and volume down for 2-5mins it will boot into bootloader from there you can boot into recovery or flash the stock rom
ADB will not work unless you are booted into bootloader or the os
Sent from my Moto G4 Plus using Tapatalk
BlackBeats said:
Hold power and volume down for 2-5mins it will boot into bootloader from there you can boot into recovery or flash the stock rom
ADB will not work unless you are booted into bootloader or the os
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
That's the issue, it's not booting into recovery mode. If I could boot into TWRP I could push the stock firmware to the phone and I think I'd be all well and good.
What seems to be happening is that because the warning message comes before the phone can boot into recovery mode I can't boot into recovery mode.
That advice would be more helpful for someone with a different issue.
AiAlpha said:
That's the issue, it's not booting into recovery mode. If I could boot into TWRP I could push the stock firmware to the phone and I think I'd be all well and good.
What seems to be happening is that because the warning message comes before the phone can boot into recovery mode I can't boot into recovery mode.
That advice would be more helpful for someone with a different issue.
Click to expand...
Click to collapse
So you saying you can boot into bootloader
If yes then try reflashing the twrp
Or just boot recovery using fast boot
fastboot boot recovery twrp.img
Try the older version
Sent from my Moto G4 Plus using Tapatalk
BlackBeats said:
So you saying you can boot into bootloader
If yes then try reflashing the twrp
Or just boot recovery using fast boot
fastboot boot recovery twrp.img
Try the older version
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Maybe I wasn't being clear the first time but here's a vidual interpretation. The issue I'm having is that I can't boot into the bootloader, if I could I'd do what you said.
A Proper Load: Device Powers On > Motorola Boot Warning > Bootloader/Recovery/Normal Boot
My Issue: Device Powers On > Motorola Boot Warning [Freeze]
Somehow it fixed itself. All I did was reinstall Android Studio and the Android SDK and it work.
ADB wasn't showing any devices before the install, but now it is.
In case this happens in the future, can someone figure out what the hell happened?
Now that issue is solved, my wifi seems to not be working. From the moment I booted into the stock rom I haven't been able to connect/view any wifi networks.

[help] my phone is hard bricked !!!

I was running B618 on my phone (rooted and tweaked a little bit), A few days ago I realized that I am running an outdated version so I decided to update to B630. I downloaded the update extracted it with HUAWEI UPDATE EXTRACTOR and while extracting I saw there was an option to make flashable zip so I decided to try to flash it through TWRP (my biggest mistake). I restarted phone into recovery mode, wiped everything and flashed the zip and restarted the phone, at restarting TWRP warned me about NO OS INSTALLED but I ignored and restarted and boom.... I was holding a bricked phone, Nothing on screen not a single sign of phone being alive, just notification light blinking red and green when power button is pressed. Googled it on internet and found that it can be fixed through jtag box.
I took my phone to a repairer and he promised me that he can take my phone to fastboot mode by JTAG BOX and further software flashing I will do it myself. After 2 days he called me that your phone is successfully in fastboot mode you can take it. I took the phone from him paid him his fee and came back home, Now my phone was running a very basic version of EMUI 2.0 which was looking like EMUI 3.1 with no apps in it just some testing apps shortcuts and gallery and other basic apps. In about phone section it was showing android version 4.3 and EMUI 2.0 and internal storage was just 450mb.
I restarted into fastboot mode flashed the boot, cust, recovery, system and rebooted the phone and boom..... Once again a bricked phone with just total red screen. I googled and again found nothing, then I saw fastboot log on cmd and the issue was that the phone's eMMC is partitioned at just 450mbs and the 2.26GB system.img file is not able be saved into phone.
Is there a way I can fix this now, Its also not booting into recovery I've tried all the commands, and when I try to format through fastboot it gives an error saying that formatting is not allowed on file system type 0.5
PLEASE IF THERE'S ANY WAY TO FIX THIS PLEASE TELL ME
I WILL BE VERY THANKFUL TO YOU GUYS.
hbilalshah said:
I was running B618 on my phone (rooted and tweaked a little bit), A few days ago I realized that I am running an outdated version so I decided to update to B630. I downloaded the update extracted it with HUAWEI UPDATE EXTRACTOR and while extracting I saw there was an option to make flashable zip so I decided to try to flash it through TWRP (my biggest mistake). I restarted phone into recovery mode, wiped everything and flashed the zip and restarted the phone, at restarting TWRP warned me about NO OS INSTALLED but I ignored and restarted and boom.... I was holding a bricked phone, Nothing on screen not a single sign of phone being alive, just notification light blinking red and green when power button is pressed. Googled it on internet and found that it can be fixed through jtag box.
I took my phone to a repairer and he promised me that he can take my phone to fastboot mode by JTAG BOX and further software flashing I will do it myself. After 2 days he called me that your phone is successfully in fastboot mode you can take it. I took the phone from him paid him his fee and came back home, Now my phone was running a very basic version of EMUI 2.0 which was looking like EMUI 3.1 with no apps in it just some testing apps shortcuts and gallery and other basic apps. In about phone section it was showing android version 4.3 and EMUI 2.0 and internal storage was just 450mb.
I restarted into fastboot mode flashed the boot, cust, recovery, system and rebooted the phone and boom..... Once again a bricked phone with just total red screen. I googled and again found nothing, then I saw fastboot log on cmd and the issue was that the phone's eMMC is partitioned at just 450mbs and the 2.26GB system.img file is not able be saved into phone.
Is there a way I can fix this now, Its also not booting into recovery I've tried all the commands, and when I try to format through fastboot it gives an error saying that formatting is not allowed on file system type 0.5
PLEASE IF THERE'S ANY WAY TO FIX THIS PLEASE TELL ME
I WILL BE VERY THANKFUL TO YOU GUYS.
Click to expand...
Click to collapse
Did you try twrp and flashable b630 rom from hicloud?
same here need the dump file to try to unbrick my phone
Adi5 said:
Did you try twrp and flashable b630 rom from hicloud?
Click to expand...
Click to collapse
TWRP isn't booting up (TRIED EVERY METHOD)
hbilalshah said:
I was running B618 on my phone (rooted and tweaked a little bit), A few days ago I realized that I am running an outdated version so I decided to update to B630. I downloaded the update extracted it with HUAWEI UPDATE EXTRACTOR and while extracting I saw there was an option to make flashable zip so I decided to try to flash it through TWRP (my biggest mistake). I restarted phone into recovery mode, wiped everything and flashed the zip and restarted the phone, at restarting TWRP warned me about NO OS INSTALLED but I ignored and restarted and boom.... I was holding a bricked phone, Nothing on screen not a single sign of phone being alive, just notification light blinking red and green when power button is pressed. Googled it on internet and found that it can be fixed through jtag box.
I took my phone to a repairer and he promised me that he can take my phone to fastboot mode by JTAG BOX and further software flashing I will do it myself. After 2 days he called me that your phone is successfully in fastboot mode you can take it. I took the phone from him paid him his fee and came back home, Now my phone was running a very basic version of EMUI 2.0 which was looking like EMUI 3.1 with no apps in it just some testing apps shortcuts and gallery and other basic apps. In about phone section it was showing android version 4.3 and EMUI 2.0 and internal storage was just 450mb.
I restarted into fastboot mode flashed the boot, cust, recovery, system and rebooted the phone and boom..... Once again a bricked phone with just total red screen. I googled and again found nothing, then I saw fastboot log on cmd and the issue was that the phone's eMMC is partitioned at just 450mbs and the 2.26GB system.img file is not able be saved into phone.
Is there a way I can fix this now, Its also not booting into recovery I've tried all the commands, and when I try to format through fastboot it gives an error saying that formatting is not allowed on file system type 0.5
PLEASE IF THERE'S ANY WAY TO FIX THIS PLEASE TELL ME
I WILL BE VERY THANKFUL TO YOU GUYS.
Click to expand...
Click to collapse
If You are able to get TWRP or stock recovery WIPE ALL DATA FAST I had same problem, and after that it solves your issue! If not Open fastboot and Flash Userdata.img then boot, go in recovery and Wipe all data again! Keep me updated!
---------- Post added at 12:53 PM ---------- Previous post was at 12:51 PM ----------
Mehdi008 said:
same here need the dump file to try to unbrick my phone
Click to expand...
Click to collapse
For Your issue, I recommend dc phoenix tool! It is ULTIMATE TOOL! BEWARE OF MEGA BRICK! If You will do all right. Your phone if boot in no time! Keep me updated!
RootingPro-18 said:
If You are able to get TWRP or stock recovery WIPE ALL DATA FAST I had same problem, and after that it solves your issue! If not Open fastboot and Flash Userdata.img then boot, go in recovery and Wipe all data again! Keep me updated!
---------- Post added at 12:53 PM ---------- Previous post was at 12:51 PM ----------
For Your issue, I recommend dc phoenix tool! It is ULTIMATE TOOL! BEWARE OF MEGA BRICK! If You will do all right. Your phone if boot in no time! Keep me updated!
Click to expand...
Click to collapse
WHERE DO I GET USERDATA.img ???
hbilalshah said:
WHERE DO I GET USERDATA.img ???
Click to expand...
Click to collapse
From update.app extract and flash

Huawei Y5 MYA-L22, NO ROOM, NO STOCK RECOVERY, FRP LOCKED

So I tried to unlock the bootloader of this phone and installed TWRP recovery and I did but then when I opened the phone I found no IMEI for the both SIM cards, anyway I thought it's a simple Rom reinstall problem, so at first it would sometimes boot into Stock recovery and sometime TWRP recovery, when it booted into TWRP Recovery I wiped everything accidentally and now the phone is Romless with a TWRP recovery only. I tried to flash Many custom roms and after flashing it just says no OS and boots into recovery again. the phone is like a rock
In Conclusion:
1. There's no OS
2. Only TWRP recovery
3. I can't flash stock recovery because OEM unlock is not enabled and in order to enable it I have to go to Developer options which I don't even have an OS to do this
4. I need stock Recovery to apply the update.app method
I need anyhelp to get the OS or Rom installed again even if it's custom ROM! I just want it to boot up!
UPDATE: I broke the TWRP recovery too! now it just boots on the Huawei logo for like 0.1 second and restarts and Huawei logo again and it keeps doing this, I can't acess anyhting
Mohamed Darwesh said:
So I tried to unlock the bootloader of this phone and installed TWRP recovery and I did but then when I opened the phone I found no IMEI for the both SIM cards, anyway I thought it's a simple Rom reinstall problem, so at first it would sometimes boot into Stock recovery and sometime TWRP recovery, when it booted into TWRP Recovery I wiped everything accidentally and now the phone is Romless with a TWRP recovery only. I tried to flash Many custom roms and after flashing it just says no OS and boots into recovery again. the phone is like a rock
In Conclusion:
1. There's no OS
2. Only TWRP recovery
3. I can't flash stock recovery because OEM unlock is not enabled and in order to enable it I have to go to Developer options which I don't even have an OS to do this
4. I need stock Recovery to apply the update.app method
I need anyhelp to get the OS or Rom installed again even if it's custom ROM! I just want it to boot up!
Click to expand...
Click to collapse
Update: Now I fuc*** up the recovery and it only shows the Huawei logo for 0.1 second and then starts again, I feel like there's no hope anymore/
Hello,
Sorry for your phone,
You should use SP flash tool to recover it, you need to download a full ROM for this phone and then flash it to the phone,
You should find the tools via google easily!
Good luck
I think the imei problem will still exist, when you recover the phone, then I may guide you to overcome the imei problem..
---------- Post added at 05:58 PM ---------- Previous post was at 05:56 PM ----------
BTW if you plug the USB you will get into default emergency recovery,, else you will get into TWRP
salembream said:
Hello,
Sorry for your phone,
You should use SP flash tool to recover it, you need to download a full ROM for this phone and then flash it to the phone,
You should find the tools via google easily!
Good luck
I think the imei problem will still exist, when you recover the phone, then I may guide you to overcome the imei problem..
---------- Post added at 05:58 PM ---------- Previous post was at 05:56 PM ----------
BTW if you plug the USB you will get into default emergency recovery,, else you will get into TWRP
Click to expand...
Click to collapse
I broke the TWRP recovery too! now it just boots on the Huawei logo for like 0.1 second and restarts and Huawei logo again and it keeps doing this, I can't acess anyhting. I don't think SP flash too can fix this? also I went to the store he said that the motherboard is dead and needs a new one. I don't know what to do
Mohamed Darwesh said:
I broke the TWRP recovery too! now it just boots on the Huawei logo for like 0.1 second and restarts and Huawei logo again and it keeps doing this, I can't acess anyhting. I don't think SP flash too can fix this? also I went to the store he said that the motherboard is dead and needs a new one. I don't know what to do
Click to expand...
Click to collapse
SP tool will work for sure , just do it. It doesn't need twrp or any thing
Did you solve it? I got a Y5 on the same condition

Categories

Resources