After upgrading my Nexus 4 my phone wont boot up and stucks in bootloop
I've already tried to wipe data and cache but it didnt work. So I am all for a downgrading my phone to android 4.4..
My android system recovery is LRX21T. The only(software) way to communicate with my computer is using adb sideload(when I use the sideload option I get a verification error), nothing more
F****** Google
Any suggestions please?
Guys I need urgent Help
Recently I was running AOSP based ROM and tried to flash RR ROM based on Android 5.1.1.
I was not being flashed and was giving error so I dont remember which bootloader or file I flashed to make RR Rom flashing possible.
Then I flashed Gapps and wiped Cache and Delvik and restarted the cell.
After Restart, it was stuck on bootloop. One thing not to forget, It remains stuck on bootloop for several times and finally boots up, and the first screen comes is Android upgrade that works on 96 apps. As soon as upgrade completes, it reboots and remains stuck on bootloop.
If i try to enter into recovery, it takes me to fastboot mode where blackscreen with like commands stating fastboot is displayed.
If i press the volume button up and plug in the cable while connected to Laptop, Download mode starts but Laptop doesn't detect any device.
On the other hand, if started in fastboot mode, ADB device is detected.
I have tried to install LG Drivers, Verizon Drivers and also universal ADB drivers but nothing has worked so far.
The device is not detected at all.
I have windows 10, also tried on windows 8.1 but same issue.
Even tried disabling Driver Signature enforce or updating system but still same issue.
Anyone who could be able to help will highly be appreciated.
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.
Hi guys I manage to brick my shield (2017 16gb on latest Oreo 7.2.3) I unlock the bootloader, flash twrp and lineage os as well gapps but the rom doesn't boot as it should it keep boot looping (I forgot to do the wipe but the system was clean anyway becouse I unlock the bootloader 5 minutes before..) I was not able to launch the recovery too. So I try to flash the twrp again... the result was bad. Now restarts to the nvidia logo and boots again. I'm able to put it in fastboot (Using A+B on the joystick plug and unplug and plug power cable) but the pc no longer see shield. Adb device's doesn't show it. Device manager says only Android device - Android Fastboot. Any Ideas how to make the pc to see it again. I have installed all the drivers and everything. Any option I give from the recovery ceep restarting the device endless.. I download the official nvidia shield recovery rom for my device but without seeing it in adb is worthless. Any Ideas ?
Please read my problem:
1: I flashed using miflash oreo rom
2: Android 9 update comes to my mobile ,i did it
3. I flashed custom rom (derpfest pie version)
4: I wiped system, data, cache and flashed siberia os using twrp
5: Botloop on android one logo
6: Tried Power+Vol Down : No fastboot
7: Tried Power+Vol Up: No twrp. it show no comand screen
It just restarting continously after androidone logo. Meanwhile I getting VENDOR ERROR after mi flash.Before flashing sberia I was able to do fastboot and twrp. I even tried all three butoon press (VOl + - power). but same behaviour
Let me alive my device please
Thanks
Same happened here.plz help
Swaniya786 said:
Same happened here.plz help
Click to expand...
Click to collapse
I solved it
- exhaust mobile battery by doing bootloop without charging
- when battery is empty, connect usb cable with all drivers installed
- now try to bot in faastboot (power+vol Down)
i am sure after one or two attempt you will gee to fastboot
- now follow below guide:
c.mi.com/thread-2251485-1-0.html
in above URL i got error while restoring twrp backup.To resolve it first make backup of your corrupted rom device.Then using file explorer on PC remove all files.And replace all downloaded one.Delete all backedup files first.(Mind it)\\
Enjoy
If unable to get into fastboot, get battery zero and retry, Dont loose hope.Dont use any special method to zero battery.Simple let it restart