Probably soft-bricked my N4 - Nexus 4 Q&A, Help & Troubleshooting

Hi folks,
It appears that I managed to soft-brick my device, while trying to revert everything back to stock.
To make a long story short, I'm working by efrant's guide, but once I try to flash the radio, it takes ages and doesn't really go anywhere, i'm waiting more than 20 minutes now.
In addition to the bootloader (which is unlocked and the computer recognizes), I can also access the recovery (TWRP) - BUT, when I tried to wipe all the data, it wiped stuff and then claimed that there's no OS installed. when I rebooted my device, it got stuck on google's logo and I had to force reboot into bootloader again.
Luckily, the bootloader is the only thing that currently works in this phone, whilst the recovery keeps "claiming" that there is no OS installed and i can't really do something with it.
so i try to flash the bootloader, it works. once i try to flash the radio, it gets stuck. i try to flash system.img, the same.
What do I do?
A lot of thanks in advance!
*update* - I managed to flash it back to stock, eventually. yey.

just flash any ROM and Gapps and It should work.

Related

Boots back to TWRP after flashing a rom

So I am going to trade in my phone soon and as part of it I need to go back to stock. I was on a stock rooted ROM for today and when I got home I saw it had a software update. I figured Id just install it but then after clicking on it remembered that I would lose root in the upgrade and didnt want to deal with that. It had booted me into TWRP as soon as I clicked on the update and so I just turned the phone off and then on cause I figured nothing tried to actually install so it would be fine. Instead of booting the OS, it booted straight into TWRP. So I figured it had set a flag and wouldnt boot unless the update finished installing, so I would just wipe everything and re-flash a new ROM again. Did that, but I still boot straight into TWRP. Can anyone help me get back to a bootable OS state where I can use the phone again? I know it is kinda retarded to click on a software update on a rooted device, but I never thought it would completely break my ability to boot and still wouldnt even work if I wiped everything and re-installed the ROM or tried a different ROM.
My guess is that as soon as I clicked on the update it set a flag in the bootloader itself, because this issue persists even after wiping and flashing. And if I try to boot into the bootloader it actually boots me into TWRP. Should I try to use ADB in recovery and push a flashable bootloader onto the device and then try re-flashing the bootloader?

Flashing another ROM turned into some bigger problem

Hi guys, the times has come for me to open up my own account - I screwed up. I hope this is the right sub forum and apologize if it is not.
LG G2 Germany, formerly: TWRP recovery, Paranoid Android 5.1.1
Loved the rom but there were some issues like the screen turning off and on randomly, wouldn't accept pin right away, so I decided to go for CM 12.1.
Booted into recovery, factory wiped, tried to flash the .zip, but neither the rom nor the gapps would even begin to flash. It just said error.
Went crazy, tried some other CM versions, none of them worked. I've never had this issue before, when I flashed PA it all went just peachy.
Went even crazier and I can't really remember what I did in my panic spiral, but I somehow ended up with a soft-bricked phone. Managed to re-install the LG firmware .kdz, however, only the 4.2 one worked (4.4 gave me a bootloop.)
Now, getting this bad boy rooted and ready to flash custom roms is somewhat of a problem. I managed to get it into recovery though (after some issues with the recovery image), but flashing CM still won't work. Same error as before. I think there may be something wrong with the recovery image. I still had the image .apk from the first time I rooted my phone (also with 4.2) and it worked just fine so I figured I'd just use it again and do it like I did it last time. However, I am able to get into recovery mode. I've tried ClockworkMod and TWRP, but as a result of my panicking, it's just really a big ol' mess right now. I hope I've included all the info needed.
Please help, I'm actually lost.
Are you flashing the latest TWRP which is 2.8.7.1?
http://blastagator.ddns.net/twrp.html
Hey, thanks for replying. At the moment it only boots into recovery, unfortunately. ADB does not work, even after re-installing the usb drivers. My computer recognizes the device now though, but I can't get any files onto that thing at the moment.
Edit: It's not the latest TWRP
If you install the latest TWRP, you may be able to boot into TWRP and copy over a ROM to flash.

Need Help Please Probably Soft Brick

Was on 6.0. Took the OTA no problem . Was running fine. Tried to put new TWRP on and sine then can't boot up. I can get into bootloader. I can get in stock recovery (no command). I tried to use back to stock and start over from LP. Probably not best option. Now gets to the screen saying that boot loader is unlocked and nothing happens. Was able to use fast boot and get into TWRP, but no where to go from there. If I try and use a flashable zip for 6.0 it just keeps rebooting TWRP. Any ideas? Help? Figure since I can still get into fastboot I have a chance, but not sure where to go with it?
SOLVED FOR NOW. Just keep going back and forth with wiping and trying to reset everything. Finally kicked in and back to LP.. been going back and forth for 3 hours.. no clue waht kicked it in, but using the restore tool.. then manually flashed twrp and wiped in twrp then rebooted and worked .. idk.. mods feel free to delete

[Q] Failed flash, stuck...

I was running xXx 4.5, and decided to "upgrade" to 5.0.
I did the usual, wiped data/system, then flashed.
I got stuck in a bootloop, and found I had to double back and wipe /data.
I did that, got stuck at the boot animation.
If I go back to recovery, all the data is jumbled, I assume encrypted? I flashed a different twrp for 8.0 compatibility, no change.
I can't push/sideload anything (roms, recovery zips sideload fine), it fails.
So I flashed the stock recovery in fastboot, rebooted there, and tried to sideload via adb the stock 8.0 flash files.
Now it works at it for a few minutes and just comes back as "Installation Failed".
Where do I go next? All i can get to is recovery, fastboot, bootloader.
I've already factory reset/wiped everything, so don't care if I lose anything anymore.
Help?
Thanks.
It appears I found a solution, just a few posts below my own! I hate it when that happens.
Anyways ,
https://forum.xda-developers.com/showpost.php?p=75364805&postcount=7
seems to have got the ball rolling, I was able to copy files to my phone while in twrp, which I couldn't do before, and currently have xXx installing. The first time it installed it didn't ask about encrypted/decrypted and didn't give me any warnings, this time it did.
xXx still won't boot after flashing, trying stock full flash file..
edit 2: Was able to flash full oneplus update file and boot. had to do a factory reset after rebooting as it was crashing a ton and wouldn't get through setup. It's been running fine since though. Now I'm a little skittish to try again, there are some root features I'd really like to still have.
I have a OnePlus 5 phone stuck in the Fastboot mode, been contacting them for days now but I still keep hearing the same excuses that the matter has been escalated to their tier 2 tech support team Nd would be contacted. Please is there a way to copy files off the phone in this state before it's flashed?

Sm-T510 Stuck in Bootloop

Hey, I'm new here when it comes to writing forum posts, so bare with me.
I've had this tablet for a few years now and I had flashed it with one of Magendanz roms (Nexus Stock) and I wanted to change to the LineageOS rom he had. I downloaded the .zip file and copied it to my sdcard and tried to get into TWRP to flash it. I did restart to recovery in the OS and once it restarted, it's been doing a boot loop ever since. I have tried using Odin to flash the rom that way, but for some reason it'll keep doing a boot loop after it's done flashing and restart. I can try going back to the stock firmware if it's a final option to get this tablet working again, but I would love to see if I can get LineageOS to work.
DengekiMatsuko said:
I did restart to recovery in the OS and once it restarted, it's been doing a boot loop ever since.
Click to expand...
Click to collapse
I had a similar issue once. It turned out that after flashing, not all the partitions mounted properly.
Are you still using TWRP? Boot to recovery, and go into "Mount". Make sure the system and other partitions are actually ticked. That solved the problem for me, and I was able to successfully boot to the system.
Hopefully your issue is that simple!
I managed to brick my Tab A 10.1 (2019) last year by dirty flashing ROMs I shouldn't have. I properly munted it, I couldn't even get into recovery. But I could still get into download mode with a USB cable plugged in to my laptop (it needed to be plugged in for download mode to come up). I flashed the stock ROM, which made it bootable again, which then allowed me to re-flash TWRP and then Magendanz' LOS18.1 ROM.
If you completely break your tablet, reflashing the latest stock ROM for your region is a great way to get back to a familiar starting point. You can then follow people's guides online to get where you want to be.

Categories

Resources