[Q] (Nearly?) Bricked M8 - Help - One (M8) Q&A, Help & Troubleshooting

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...

Related

HELP PLEASE - EVO 3D Stuck in Bootloop!

Hello All,
I recently rooted my EVO3D using the HTCDEV method because the bootloader was version 1.5.
Here are the steps I followed to root (sorry for the copy and past but I want to be as detailed as possible)
Files Used
su 2.3.6.3
TWRP Recovery
Steps Taken:
1)Take both the su.zip and recovery.img files and put them in your sdk tools folder.
2)Now do the following in ur command prompt, hitting enter after each command.
3)Code:adb push recovery.img /sdcard/And,
4)Code:adb push su-2.3.6.3.zip /sdcard/Then,
5)Code:adb reboot bootloaderUr phone will go to fastboot and should look like the after picture above. Now you can flash the twrp recovery, so do,
6)Code:fastboot flash recovery recovery.imgIt will ouput something like this,
7)Code:sending 'recovery' <5068 KB>... OKAY////writing 'recovery'... OKAY///finished. total time: 11.355sNow you have twrp recovery, so you can navigate to it. On ur phone, use the power button to pick bootloader, then scroll down to recovery and pick that. You will then be booted into recovery.
8)Here you can pick "install zip" and then pick the "su-2.3.6.3.zip"
It will flash, the you can pick "back to main menu", then "reboot system now"
9)You will boot back up and have working Superuser. I have had no trouble with Titanium Backup, Root Explorer, Quick Boot or any other app that requires root. Before you do too much, it would be good to go back to recovery and do a Nandroid backup. Always best to get one ready before you start modding anything.
All of this worked fine, and the phone was "unlocked."
Then, I flashed the most recent version of CleanRom (2.7)
Again, the phone worked fine, battery life was a little crappy.
I decided to flash Ziggy's kernel.I flashed the kernel simply by putting on the SD card, and then rebooting into recovery. This worked fine as well, but I noticed some of the buttons for example the menu popups displayed volume where it should have said more, or bluetooth options where it should have said preferences. so this is where the trouble started, I downloaded kernel manager, and flashed silverneedle through that program. Now, I am stuck at the White HTC Splash screen bootloop. The phone turns on and after 15 seconds reboots, and reboots, and reboots.
What Ive attempted:
I have done countless wipes and clears of the dalvik cache and cache
ive formatted the system and the date sections (advanced menu in twrp)
ive reflashed the rom after wiping countless times
ive tried flashing different kernels in recovery to no avail
factory reset and wipe havent helped
im not concerned losing the contents of the SD card
I need help because I already had two phone claims in the past 11 months, and if I claim another lost phone I will lose insurance for life with Asurion (sprint)
anytips or help would be greatly appreciated
i can provide any additional info
Similar situation, Not sure if you've already solved the problem but I'm going to copy paste my solution from another thread...
Hi, I'm not sure if this is the right place to ask but this is a preety derp question. I've gone across the internet and tried a lot of reflashing to repair my sort of "bricked" evo. What happened, was that I had a evo 3d s-on htc bootloader unlocked, with custom recovery -clockwork..anyways I had flashed the leedroid 3d 4.0 rom and It worked the only problem was my wifi, so i attempted to flash another kernel onto it, but I had accidently flashed "Rcmix" kernel which I later found out was cdma =.=. so now my phone keeps rebooting at the htc screen, it would just load up with the green htc letters, then after 10 seconds or so it'd reboot, and then begin the process again. I can boot into bootloader and recovery but whatever I flash doesn't seem to work including restoring my backups...and then the battery died so i couldn't even charge it or go in. But i managed to work out I could load into bootloader from the CMD and the furthest i've gotten to is to have the bootloader show FASTBOOT USB. SO I must be getting somewhere...? I did read that i had to load from the cmd and not just from power+vol down..but I'd appreciate any help towards restoring my phone to the way it is or at least before i flashed the rcmix.
Just a note tho I've tried factory resetting but all i get is that it loads into recovery at the bootloader options i dont get "clear storage" as an option and "restore to factory settings" and what not just boots me into recovery agian.
EDIT:
I Managed to fix the phoneeee!!!..just for future preferences and anyone else who has this problem...
I followed bits and piece of IL DUCE's advice to izzy spun, the important part was booting the recovery from cmd. I wasn't able to "erase recovery" But I tried just booting it,
First I would remove the battery,
Put it back in,
Plug the usb cable in
1. Type command, from your Adb/fasboot folder, "adb reboot-bootloader"
2. After that I made sure my bootloader said "Fastboot USB", and then I issued the command, "fastboot boot cwm-4.0.1.4-shooteru.img" or with whatever recovery you had..
3. From there I restored from my backups my original rom. Rebooting, and fixed.
--- and It worked. At the time I was on clock work recovery, i only had the Revolutionary recovery img. Cwm-4.0.14.-shooteru.img to be exact,
after going in there I just cleared the cache and davlik and then, proceeded to restore my backups (I'm not sure if it would've worked if I had re-flashed the leedroid or a custom rom)
and then I simply rebooted the phone, and it got back into my phones original state before leedroid (as I had Only backedup before then)....
Apologies for the lengthly post, but I guess reading does help, but I've been going nuts before I managed to fix this. Just thought I'd leave this post incase someone were to need this.
Same problem
Hi there. I just recently joined so excuse my noobness but i have a similar problem. I recently just rooted my evo 3d sprint with the the boot 1.5 and everything went well. I decided i wanted to overclock my phone so i followed zeemaxs way. Before going into the overclock procedure i decided to do the the RCMIX Evo 3d kernel v. 2.2.3 first so i would have better results when done with the overclock procedure.I bootup the kernel through the recovery mode on the phone butit failed to load so i just reeboted. After that my wifi and 4g stopped working. So i downloaded an app on the market called "flash image GUI" which lets me flash the kernels through the app. I flashed the RCMIX kernel and rebooted and now im stuck ima boot loop. I COULD just go back and back up to my old rom and settings etc...........but the problem is i dintmake any kind of back up or recovery i think. I know i know im stupid and an idiot but i just sort of panicked n ended up with this. If anyone can help please tell me.I do not want to pay for a new phone at full price. PLEASE HELP THIS POOR NOOB!!!!! X(
awsomepanda20 said:
Hi there. I just recently joined so excuse my noobness but i have a similar problem. I recently just rooted my evo 3d sprint with the the boot 1.5 and everything went well. I decided i wanted to overclock my phone so i followed zeemaxs way. Before going into the overclock procedure i decided to do the the RCMIX Evo 3d kernel v. 2.2.3 first so i would have better results when done with the overclock procedure.I bootup the kernel through the recovery mode on the phone butit failed to load so i just reeboted. After that my wifi and 4g stopped working. So i downloaded an app on the market called "flash image GUI" which lets me flash the kernels through the app. I flashed the RCMIX kernel and rebooted and now im stuck ima boot loop. I COULD just go back and back up to my old rom and settings etc...........but the problem is i dintmake any kind of back up or recovery i think. I know i know im stupid and an idiot but i just sort of panicked n ended up with this. If anyone can help please tell me.I do not want to pay for a new phone at full price. PLEASE HELP THIS POOR NOOB!!!!! X(
Click to expand...
Click to collapse
What your going to have to do is flash the original kernel you started with. thats why your in a bootloop
Similar problem
Hi everyone!
I have a kind of similar problem, so I won't post it in a new thread.
Yesterday I rooted my phone following this guide: androidforums.com/evo-3d-all-things-root/494212-complete-newbies-guide-rooting-flashing-evo-3d-roms-kernels-using-fastboot . html (i am not allowed to post links to prevent spam).
I unlocked it with htcdev and installed a custom ROM without getting any errors. After restarting the phone, it got into a boot loop; it showed the starting animations of htc and the ROM and then shut down again.
Here some more information:
-Evo 3d Europe gsm
-hboot 1.5
-s-on
-image version 3.28.401
-installed ROMs using clockworkrecoverymod (as proposed in guide)
I have tried these ROMs (all leading to boot loop):
ICS NonSense
Cyanogen Mod 10 – DisarmedToaster (v. 1.4 and 1.5)
Jelly Bean 3d (by Ubuntuz)
SAD 2.1 DEsenseX
I installed the ROMs by doing:
Connect device via usb > flash boot.img via fastboot (from pc) > clear Cashe/UserData/DalvikVM > install rom.zip from sdcard > reboot
I really don't know what to try
Any ideas how I could install a running Android OS are highly appreciated.
Thx for any help
Problem solved!
Ok, I solved the problem by simply relocking the phone and installing the stock ROM with the RUU.exe
RUU.exe
I'm glad someone else mentioned Relocking before running the RUU. I've read several posts be others that have actually stated that Relocking wasn't necessary but in order for the RUU to take you have to Relock. IF you get a chance check out CoolICS Rom and MeanRom both are pretty good.
Thanks all for the help, had to revisit this issue today.

[Q] continuous boot loop TWRP

First of i'd like to thank the community! I've ran in to numerous issues and have been graciously saved several times.
I'll start of by providing some context in to the issue.
original configuration:
Unlocked - T-Mobile US SIM
AT&T LG E980 factory tot 4.1.2 - flashed using LG Flashing Tool
Root - E980 Universal Root
Unlocked Bootloader - Freegee [Android Marketplace]
Installed Recovery TWRP v2.6 - Freegee [Android Marketplace]
Removed bloatware - AT&T Applications
So from this point the phone was working as expected. I spent hours configuring to my liking and decided to call it a night. Before I called it quits I decided to make a backup using TWRP. Backup took a really long time but it said successful. I left handset plugged in to charger overnight, roughly 6 hours of continuous charging. When I woke up I noticed the phone was in recovery mode. Touchscreen was also unresponsive. I held the power button to allow it to reboot and it rebooted me back to recovery. At this point I knew something was wrong. I attempted to re-install backup files made from previous night, this failed. The phone booted back to recovery. I then installing some zip files I had pre-loaded on to the external SD card, this was CM10.1 and gapps files for E980. I tried this out a few days ago and it was working fine. I decided lets try installing this and see what happens. Install was successful and rebooted. The phone boots back in to recovery. At this point I'm really frustrated. I checked the memory card by running through the TWRP menu. I noticed the file sizes were unchanged but the files were not displayed on both in/ext memory. I decided to finally restore again by using LG Flashing Tool. This by the way has saved my a$$ numerous times. So the one thing I would note, at the 85% when the phone reboots I noticed there was an error, an error I've never seen before. It was a picture of sync icon (large) and android man on top of it and text that said "error 0x123456" I didn't note the exact string. I let it go and monitored the flashing tool, somewhere around 93-95% it rebooted again in to the normal boot sequence. Viola my phone is back to where I started.
So here's some of the questions I had:
How did I end up in the TWRP Recovery boot loop?
Why could I not see the files to install once in TWRP?
Why did TWRP continuously boot back in to recovery mode after successful install of restore?
Why did TWRP continuously boot back in to recovery mode after successful install of CM10.1/gapps zip?
Has anyone seen the LG Flashing Tool error I described above and does anyone have an explanation as to what happened?
Here's my theory on what happened...
My phone was on 4.1.2 as mentioned. I noticed a few times that there was a notification stating the phone had a OTA software update available. The first time I tried to update (already rooted and unlocked) the phone failed to update. The error cited that my phone was believed to be rooted. I paid no attention to this and decided to continue using. Later in the day I noticed the notification again, I opted to try again. The phone updated, or at least tried to. It kept booting in to TWRP Recovery. Nothing I could do could restore it, except flashing using the LG Tool. After experiencing this I knew to leave the OTA alone. I don't know if this is possible but somehow I think the OTA was pushed and forced through while I was sleeping allowing the phone to charge. This is the only time I've seen that behavior. Is that even possible???
Where am I now...?
Phone is restored, I opted to upgrade using the OTA before I start tinkering again. Maybe I won't mess with it at all and leave it alone at this point.

[HELP] I think I screwed up, factory image/bootloader help

EDIT: SOLVED. After some hours at work I was able to boot back to the bootloader and flash the images individually.
TL;DR at the bottom.
Hi, I've been rooting and ROMming for a while now, and last night I made a mistake that set forth a chain of depressing events. I have a N7 2013 LTE, and was running AOKP up until last night. I wanted to flash the 9001 L preview, despite having no access to data. Simple right? Wrong, you forget to realize I'm a tired idiot last night. I downloaded the zip no problem, rebooted to TWRP and commenced my advanced wipe. Some how, I mistakenly checked off "wipe internal storage" during the process. So I go back to the Install screen, and my heart sinks. F***. At this point I decide to let it lie in recovery until tomorrow (today) and keep it charged.
Fast forward to this morning, I'm at the office. My device is charged and waiting in recovery. I decide I'm just going to flash the factory image to stock 4.4 and start with a clean slate, wiping all (even though it's wiped). Reason for factory image and not just adb push the ROM is that I'm having a seemingly-unsolvable issue of incorrect storage. It tells me my 32gb device only has 11.6 gb total storage. This has persisted through multiple clean-wiped installs of various ROMs, but I don't know if it started out like that when I bought it, since I didn't think to check before unlocking and putting a ROM on it.
So I get the SDK and images on my work PC, and commence flash-all.bat. Working great until it gets to system.img, then it fails. Try again twice, same thing. Open the image zip and extract the files, then try to flash one by one, now it's saying the commands are invalid (fastboot flash system system.img, etc). So I wonder, because sometimes these devices are wonky in ADB, maybe it installed and just said it failed? F*** it, I'll try to boot. Google logo for an hour. Ok, cool, I'll go back to the bootloader. NOPE. The device either won't power on at all, or it will get stuck at the splash screen and hang there. Any idea where to begin to fix this?
TL;DR: No OS on phone, failed flashing system.img in flash-all.bat, now device won't boot to bootloader or (missing) OS. Any ideas?

Trying to update while rooted...

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.

Stuck on google logo boot screen after twrp recovery & then factory reset

Hi guys, bit of a saga here so bear with me...and also it should be mentioned I have little experience/understanding of tech stuff, so that isn't helpful either lol
I've had a Nexus 5x running 7.1.2 for not quite a week; it came with an unlocked bootloader (strangely). Tried to do the usual install twrp & root as I've done with previous phones (all pre-nougat) but all attempts failed. Couldn't boot into stock recovery from the bootloader at all, it would just boot into the system. OK, next thought was that an OTA upgrade to Oreo might work to restore a recovery - but got the BLOD (naturally lol). I found a fix in a modded 4-core Twrp 3.2.1 -0 fbe img + workaround injector zip from osm0sis & XCnathan32 which by some miracle worked.
So far, so good. Ffwd a few days and google play store keeps crashing on opening; I had the feeling that some glitch happened while it was updating, so I tried all the usual fixes like app cache/data wipes and uninstall updates/renistall google play, delete google account etc which failed. Next I tried a cache & data device wipe through twrp - also unsuccessful. Finally, I thought the only thing left to try would be to restore a backup I made on twrp - this led to the current issue of not booting, stuck on the google logo screen. I even thought what the hell! and attempted a factory reset with twrp - same result, where I am now. Google logo screen, however I still have an unlocked bootloader.
Would anyone be able to suggest where I might go from here? I'm pretty sure the version is N2G48C, if that helps.
Any suggestions very much appreciated...wouldn't mind getting to the 1 week mark with a functioning phone lol
Saga #2
Still no idea what's going on. I realised that I'd backed up and recovered the system and vendor .img files, which according to this thread would be a cause of the issue https://forum.xda-developers.com/nexus-6p/help/stuck-google-logo-twrp-backup-restore-t3320840/page3
So I made another backup without those images, did a full wipe and restored it - still does not boot, still only sitting on the google logo. Tried next to open a cmd terminal to see if I could reflash a stock image, but adb could not connect (maybe because the phone would have been on charging and not file transfer mode?)
Last resort as I saw it was to try the NRT, and see if it would flash stock via the bootloop/softbrick option. Process seemed to be OK, judging by the log - but it did not reboot to the system. Now there is a looping bootloop between the google logo and the unlocked bootloader warning.
Following wugfresh's instructions to factory reset from the recovery (the phone won't turn off via the power button so I just booted straight into the bootloader) Looked for the recovery option, selected....and nothing!!
So there isn't a stock recovery??? How does that work?
And what hope is there for this phone now? (I can't think of anything else )
Anyone have an idea? I've never heard of this before tbh!
Well, my problem has been sorted. In the absence of knowing what the hell I should do lol I managed to get a refund for the phone even though it was a refurb to begin with (something to be said for an honest seller who provides a 3 month warranty!) and I picked up a brand new N5x, which was unboxed on Tuesday. Not even 6 hours into setting it up, the phone started to get progressively hotter and then went into bootloop. Got into the bootloader and tried a factory reset - all seemed OK but halfway through the setup process it bootlooped again. Fortunately it was still within the 2 year warranty, and LG didn't argue about authorising a repair for a phone which didn't get even half a day's use on it lol
Authorised Wednesday, walked into the service centre Thursday and a 1 hour wait later had phone in hand with the PCB/motherboard replaced. Has been working fine (and cool!) ever since. Definitely feel lucky to have hopefully dodged a bullet on this one.
Bonus that they upgraded from 6.0 to 7.2.1 while they were at it; apparently LG considers nougat the "latest" stable version for the 5x.

Categories

Resources