Trying to update while rooted... - Nexus 5X Q&A, Help & Troubleshooting

Hello,
today I accidentally tapped on "Update" (to 7.1.1) on my rooted Nexus 5X... Something you usually shouldn't do, but it was 2am and I was tired and.... Doesn't matter. After this my phone rebooted and almost instantly showed the dead android with the message "No command". And now I'm stuck there. After rebooting I still land there.
Since the error message almost instantly appeared and since I still can boot into TWRP (3.0.2-2), I think the update wasn't installed and I hope to find a way to avoid the factory reset of my phone. Do you have some tips or possible solutions what I should do in this case?
Thank you for your help.

Its odd this happened, when rooted and twrp installed. in my experience, the update will just simply fail and it will boot back up.... in your case, it sounds like something flashed but the phone didnt like it.... All I can think of is if you cant get into twrp, boot into fastboot and flash the factory image from google, you will loose all data though.....
EDIT, RE-READ you post, if you CAN get into TWRP, try flashing a backup... you should have a backup I hope, lol... First rule of root and flashing is make a backup asap....LOL

When I rooted my phone I did a backup. But the problem is, it was several months ago. So I tried the only method I could save all my data. It wasn't safe, I knew this, but no risk no fun.
My solution was: Download the ota update from Google and flash it with TWRP... Voila! My phone boots properly with the new update... But this method is like I mentioned before not safe and can probably cause a boot-loop with an overwritten recovery. I had to flash my recovery again, but everything works fine now.

Related

[Q] Help! Won't boot after software update.

Ok, so I did something really stupid this morning. I had a notification that a software update was available. I decided to ignore my better judgement and install it. After it downloaded, the phone rebooted and went into recovery. When I say recovery, I mean TWRP, since that's what I have installed. Now every time I reboot the phone, it just goes straight to TWRP! I tried wiping the phone (factory reset). I even tried installing a different ROM! It just keeps on booting straight to recovery.
Any suggestions? Please help. I'm dead in the water.
Download mode and Lg flashtool flash KDZ.
Whose a silly boy then.
Cant believe that people are still installing OTA updates even though they have TWRP.
Vivasanti said:
Whose a silly boy then.
Cant believe that people are still installing OTA updates even though they have TWRP.
Click to expand...
Click to collapse
You'll get no argument from me...

[Q] (Nearly?) Bricked M8 - Help

Hello there good folks of XDA,
I'm at work right now and my phone is at home but here is the story of what went down last night.
I tried to root my phone, after installing TWRP and superuser I ran a root-check app and it said that I was not rooted, so not thinking I tried the 'fix permissions' function of TWRP and then everything went haywire.
It's an international version M8 that I've had rooted before but reverted back to stock to get the lollipop OTA update​By haywire I mean the phone booted up but no widgets displayed and most of the apps still appeared in the app drawer but nothing would open.
Instead of seeking help at this point I went to town on trying various things :silly:
The last of which was try and flash a boot image to it, but I think I must've used the wrong one as after doing that it's now stuck in a boot into TWRP loop.
From when I had previously rooted the phone I had a boot image (I think) 2.22.401, it matched version on the recovery file I used when reverting to stock in the past so I thought it would be fine​
I've still got a terminal open at home with all the results of the fastboot getvar all command but from memory my CID was HTC_044
Can someone help outline the process and possibly even the files I need to reflash my phone into a working order. (it doesn't need to be 'stock' but that would be best)
I use a mac by default but I do have a windows machine at the ready I can use so feel free to base any tips on doing it from either platform​
Post the getvar all output, minus IMEI and serial number, and we'll go from there
Thanks for coming to my assistance but in the end (after a few more slight failures) I managed solve the problems myself.
I believe that my first problem was using a not up-to-date version of TWRP (2.7) with Lollipop; the first symptom was my attempt at rooting my phone, the process appeared to go well but just wasn't working properly.
My second problem was 'fixing permissions'; after doing that my phone went totally haywire and while it would boot into android nothing would work properly
After going to a previously used stock recovery and getting nowhere I went back to the same TWRP I started this with and still had fixed nothing.
at this point I did a factory reset from the recovery mode and while that got me booting back into android I was being swamped with error messages and couldn't get past setup wizard crashing.
At this point I flashed the wrong boot image and had a nearly impossible time getting to the system boot menu instead of TWRP being what it always went to. Eventually I must've got the timing right with the buttons or something because I got back into the system boot menu and could access fastboot.
Once in fastboot I downloaded a full nandroid backup and restored it, my phone was working again... or so I thought, it was still suffering from permissions problems
at this point I re-rooted it with the latest TWRP, got SuperSU working properly, did the 'restorecon' command with a terminal app and now the app crashes I was getting have stopped and I can see and write to the phone memory.
After trying to test everything I could think of on my phone today I think it's finally fixed.
I tried to do a partial/selective app+data restore from a nandroid backup I took of my own phone just after the 'fix permissions' event but it didn't work properly so in the end I manually re-setup my phone. I do run an sms backup app so overall I only lost time...

V410 7.0 LTE bricked

Ok guys I am pretty sure I fubar'd my tablet.
I am stuck in a recovery loop. When I start the tablet it just goes back into recovery. Which if I still had TWRP I think I could still do something, but I flashed cyanogen recovery trying to flash cm13 since I cold not get anything else to work. I cannot boot into download/firmware update screen. The screen just flickers a little and goes dark.
A little background:
Started when tablet forced install of 5.0 update and I was in a recovery loop. I flashed 410 test build, rooted, flashed twrp, installed stock rooted ROM. Everything was fine. Then tablet did it again, this time I just flashed rooted ROM and factory reset. Even took the steps to fix the white lines and storage issues. Was working fine. Got home a few days ago and I was in a recovery loop again. But now I don't have the bootloader screen/download mode/firmware update screen (whatever you want to call it) so last night i tried to download cm13, Gapps and cyanogen recovery with no avail.
I can access adb on my PC while in recovery, but when I try to access ADB shell I get unauthorized something or other. Because I cannot authorize USB debugging, because ROM won't boot. I tried to flash stock rooted ROM from cyanogen recovery and it says not signed or something like that.
Does anyone have any ideas? I really think I have screwed the pooch here.
sent from a device using an app
title
if you have a stock recovery image flashing it is easy, i had a LOT of troubles with my v410 and still am working with it. i have mine rooted, just with TWRP though, i cant use xposed framework, which negates why i rooted this in the first place. anyway, through much grit and determination flash your stock image after wiping what needs to be wiped and doing all other necessary things. Then, you must download kingo root, supersu, superuser. flashify would help with the flashing i hear, but it has troubles with the v410. kingo root was an apk i managed to find buried under a million viruses on the 34th page of google..or something. rooted mine in one click, from stock to reboot to twrp root.. many glitches.
I need help myself, deleted my "Phone" system app, causing me to lose connectivity with my data plan. cant seem to restore it, and flashify nor twrp has been able to flash a custom recovery, or a backup, im at a loss.
Help? We seek the same thing.
Ok but how do I flash the stock recovery image. I can't use fastboot. ADB says I am unauthorized.
sent from a device using an app
Anyone have any other ideas?
I am at a complete loss. I am by no means a developer, but I do know my way around. I really think I have FUBAR'd this one.
Kind of stinks, I give up. Anyone want a bricked v410?
Sent from my Galaxy Tab 2 using Tapatalk

bootloop issue?

Hi,
I think I have the bootloop issue. I was running purenexus marshamellow.
At first, I couldn't get past boot after many attempts,phone kept going dark. I wasn't even able to boot into bootloader. So, I removed the sim card to put in a backup phone. The next day I went to work on the phone to see what was wrong with it. Amazingly it booted up. So I connected to adb and downloaded all my personal media (adb pull). At that point I have never read about the bootloop issue, phone has been solid for a while and I don't keep up with the news. So then I decided to do a clean flash of purenexus. I noticed Nougate is available and decided to go with that.
For the most part, I can boot into bootloader without any problems now. So I flashed, the bootloader, the vendor image and radio. I went to reboot into TWRP and I got the bootloop issue. So I decided to flash the latest TWRP. Then I was able to boot into TWRP. I was able to wipe the cache/data. However, when I went to install purenexus, it would freeze and reboot. At that point I realized something is wrong and I came here. I read about the bootloop issue. So now I am wondering if I have that issue? I'm pretty certain I do, except that I can reliably boot into the bootloader. TWRP and android itself will cause reboots, but not the bootloader.
So should I send in the phone to get replaced? Or is there anything else I should try?
Also, I am halfway done towards installing purenexus, is there a way for me install in the bootloader without having to go into twrp?

I have hit a wall

Hello everyone, Merry Christmas!
Although I say that, I bring not so merry news. My OnePlus 7T is bricked and after trying everything I don't know where to go from here. Currently I am stuck at the:
The current image (boot/recovery) has been destroyed​phase of things and all I can do is boot into fastboot, that is it.
How did this all start? All I did was just update the phone to Android 12 with the official OTA update from OnePlus, big mistake. Worst update ever; my adaptive brightness went haywire, the brightness gets stuck at max, I couldn't receive calls, data was completely unresponsive, and the list goes on. So before the obvious downgrade method, I try a few things first:
Cycle airplane mode on/off
Reset network settings
Reset ANR
These worked for a minute on my data then right back to the same issue.
Wipe cache partition... Oh wait I had to find out the hard way Android 12 removed this option....
Wipe the phone
That fixed nothing.
Ok time to downgrade, but this is where things got tricky and I realized that maybe all my issues stemmed from me getting the wrong update from OnePlus? Although I found this out too late.
See my phone model is HD1907 which I already knew at the back of my head, but when it mattered to remember the most, I didn't catch what happened. After my update to A12, my model number changed to HD1901 which is the Indian version, and when I saw it didn't think anything of it at the time but then after all my problems it came back to me, my phone has always HD1907 so maybe this is a compatibility issue.
Anyway since I was going to downgrade anyway I thought to myself, 'since I already wiped everything, maybe I can use this opportunity to try out a ROM for A12 and see if it is just this ****ty OOS causing all these issues,' and so I did. First thing I did was unlock the bootloader, and try get TWRP on my phone. That all went fine, I booted into TWRP, flashed my zip for TWRP, then proceeded to try to boot into the OS... and the rest is history because that is as far as I got. Apparently my boot.img is destroyed and I can't boot back into TWRP anymore either, all I can do is get to fastboot.
So then I tried MSM, it won't detect my phone.... So then I tried flashing my Stock ROM through fastboot, apparently I'm missing a partition and it won't write to a critical partition either....
So where do I go from here...?
Hello I was in the exact same boat as you today same phone, same update issues, same no recovery mode, no os to boot into only greeted with fastboot mode. I have resolved it and I'm back on oos 11 good as new. I did use the msm tool it is tricky for sure at first. A critical step is installing the qualcomm drivers and then rebooting your pc. Get them here
https://androiddatahost.com/nbyn6. Be sure to reboot. It's late and I just got this thing back into working shape so I don't want to write a lot a right now. It's been a few days since this post so... If you are still stuck I will be glad to help out let me know. There is hope!
Canbeit said:
Hello I was in the exact same boat as you today same phone, same update issues, same no recovery mode, no os to boot into only greeted with fastboot mode. I have resolved it and I'm back on oos 11 good as new. I did use the msm tool it is tricky for sure at first. A critical step is installing the qualcomm drivers and then rebooting your pc. Get them here
https://androiddatahost.com/nbyn6. Be sure to reboot. It's late and I just got this thing back into working shape so I don't want to write a lot a right now. It's been a few days since this post so... If you are still stuck I will be glad to help out let me know. There is hope!
Click to expand...
Click to collapse
I too had all the symptoms after an update to OOS12, including progressively losing any semblance of booting. not even recovery and the drivers found elsewhere didn't work, and had a different name when installed and would never get detected in the MsmDownloadTool. After installing this one and rebooting, it finally detects it and installs the image of EDL mode.

Categories

Resources