So mom dropped off her old Xperia Tablet Z SGP311 as a "gift". It did not work for her anymore, so if I wanted it and could fix it then I would have another tablet in the pile.
Her description of what did not work was what you would expect from a non-techie aka "some error turned up but I cannot remember what the screen said, so can you fix it?".
In the beginning I thought the problem was the common USB/charging problem, however I feel anything about this tablet seems different than other Android tablets, so after finally managing how volume buttons along with power buttons work, I could rule out it was a charging issue.
Getting the Tablet to boot it seemed that it had been updated and was booting into OS doing the "optimising applications 1 out of 258". However going to the step "starting applications", then tablet would just reboot a few times and then start over with optimising applications, starting applications, reboot and repeat all over. So some sort of bootloop.
I then used Sony's Xperia Companion to repair the tablet from fastboot (volume up + power) which succeded until it should reboot the tablet, then I was stuck in the same loop as above.
After a few tries I then managed to unlock bootloader and get TWRP 3.2.2 booted onto the tablet (booted NOT installed since I have no root).
With TWRP I tried deleting Dalvik cache etc., which did not help the situation, same bootloop.
With TWRP I then gave LineageOS a shot, but LineageOS experience kinda the same bootloop (both LineageOS 14.1 and 15.1).
LineageOS boots fine and proceeds with the fresh install questions (region, timezone, Internet access) but as soon as I hit next on the "Location Services" page the tablet will reboot.
Since this tablet has no value to me, I have tried deleting all data on all partitions from TWRP, I have checked the filesystem with e2fsck on the tablet which shows no errors, but in any attempts it simply reboots at the same stage every time.
So are we at the level where this might be some internal hardware failure (GPS/WiFi chip, NVRAM)? Or is there any suggestions of what else to try other than throwing this to recycle bin.
bjoeg said:
So are we at the level where this might be some internal hardware failure (GPS/WiFi chip, NVRAM)? Or is there any suggestions of what else to try other than throwing this to recycle bin.
Click to expand...
Click to collapse
probably memory problem either RAM or ROM.
Related
I have a problem with one of my Lenovo A830 phones.
I bought it from Etotalk, so it came rooted, and with their custom version of the Lenovo Stock ROM and their custom version of CWM 5.5 installed.
I tried formatting my SD card and then doing a factory data reset from within the operating system. (I was intending to install MIUI V5 after rebooting into recovery).
However, on rebooting, the device is now caught in an infinite boot loop, and I am not able to boot into recovery mode (by holding down power and both volume keys). It loads the initial splash screen, then shows a few seconds of the Android character and some whirring cogs before rebooting.
I am able to boot into Factory mode (power and volume up) or Meta mode (power and volume down). Factory mode has a number of options, but they are all in Chinese characters, which I am unfortunately not able to read.
I did notice that my SD card seemed to be write protected when I tried to format it in my computer and to copy on the new ROM - I solved this by putting it in a different phone and reformatting it. I wonder whether the factory reset process has write protected something it shouldn't have?
Does anyone know how I might best proceed? I've been digging around on the forums, and tried a few things, but there's nothing which seems to provide a coherent solution for this problem.
I've got the latest Android SDK Tools, MTK Droid Tools 2.4.8, SP Flash Tool 3.1312, some additional ADB drivers (120827 v3.7) that I'm not sure how to install, the latest MIUI V5 ROM (3.8.16), and the latest stock Lenovo ROM (S118 from Need A ROM, just in case I need it).
Maybe different SP Flash Tools version?
I had trouble using SP Flash Tools v3.1312 with A830. Once I switched to v3.1304.0.119 I was able to flash both the original ROM and the custom MIUI one without serious issues. I'm unable to post the download link but google it.
One other thing is that when connecting the phone, it usually loads the something something Preloader driver, which is no good (even if it gives you Download OK). When attempting to flash either ROM, try pressing both the power and volume up buttons while connecting the phone (after pressing Download), only way it worked for me.
Good luck!
I managed to sort this out quite simply in the end!
On the Lenovo A830 (and presumably other Lenovo Android phones?), you enter recovery by pressing power and then pressing volume up / down together after a short pause. The short 1 - 2 second pause is important, because if you try and press them at the same time or in quick succession it doesn't seem to work.
I then installed MIUI V5 from the SD card followed by Google Apps after a reboot. In order to get MIUI to install, I had to remove the assert check at the top of the update script, because this seems to erroneously check for the A820 (even though there isn't currently a port for this device?). It's working excellently with two exceptions - I am unable to select the SD card as a storage device, and Google Play store is not searchable (it causes a Force Close).
tominglis said:
I managed to sort this out quite simply in the end!
On the Lenovo A830 (and presumably other Lenovo Android phones?), you enter recovery by pressing power and then pressing volume up / down together after a short pause. The short 1 - 2 second pause is important, because if you try and press them at the same time or in quick succession it doesn't seem to work.
I then installed MIUI V5 from the SD card followed by Google Apps after a reboot. In order to get MIUI to install, I had to remove the assert check at the top of the update script, because this seems to erroneously check for the A820 (even though there isn't currently a port for this device?). It's working excellently with two exceptions - I am unable to select the SD card as a storage device, and Google Play store is not searchable (it causes a Force Close).
Click to expand...
Click to collapse
Hello,
How did you manage to fix the reboot loop?I have the same problem,after a factory reset the phone just reboot like you said in first post...please help me fix it...
claudiuionel said:
Hello,
How did you manage to fix the reboot loop?I have the same problem,after a factory reset the phone just reboot like you said in first post...please help me fix it...
Click to expand...
Click to collapse
Hi I had similar "reboot loop" problem this morning after a phone factory reset.
I have no idea how I solved that but the following was the steps I tried:
1. Install the MTK6589_PdaNET_ADB_VCOM_Drivers. Skip the USB connection during setup. Start the PdaNET after setup finished.
2. Insert battery inside the phone and connect the phone with the computer by USB
In my case, the phone reboot loop once, and the lenovo screen appeared in the second restart. The phone hanged. I unplugged the cable, took out the battery, insert the battery again and start the phone normally again and it is working now.
I recommend installing the recovery rom after you have fixed the phone.
Goodluck
Hi Im new to the forum but I am finding it to be a massive resource for all things technical android. I am also new to rooting android but am technically savvy, (10 years in IT will do that). Initially it went just fine, even if a speed bump here or there. I got my Sony Z2 (starting BL unlocked w most recent Sony stock .291 firmware) rooted and flashed with TWRP and SuperSU (UPDATE-SuperSU-v2.76-20160630161323.zip) using rocker00's guide. I was then able to successfully flash ParanoidAndroid's latest (pa_sirius-6.0.3-20160809-signed.zip) and Gapps (A-GAPPS+6.0.1_14.05.2016_v5.2.zip) using TWRP recovery. I got a minor bootloop trying to get PA running, but re-flashing seemed to clear it up. It seemed to work fine although I couldn't figure out how to get the pie controls or the halo notifications to work. Without those things i couldn't see the point, so I decided to try Cyanogen (cm-12.1-20161016-NIGHTLY-sirius.zip). Apparently this uses a different recovery (CWM), I was a little worried but went for it anyway. It seemed to be fine after the first reboot. I rooted fine (same SuperSU as before) and started installing apps via Google restore. But after the next reboot, it started bootlooping. First it would cycle between the Sony screen and a blank screen, But after trying a bunch of things (I'll detail below), it just hangs at the Sony screen indefinitely.
So, what I've tried till now to fix it is:
1) First I tried to reinstall TWRP using the tool from rocker00's post with the phone in fastboot mode. The flash went without error, but did not fix the problem. I have not been able to get into recovery since the bootloop. In the process I also did a fastboot -w, which also seemed to have relatively no effect, although I would get the android robot with the blue progress once before it reboot into the bootloop.
2) With the phone in flashmode I tried flashtooling the kernel again with the same from rocker00's post (D6503_23.5.A.0.575_kernel.ftf). No effect. I also tried flashing recovery a few more times using the script from his post to no effect (i think the phone needs to be booted for this tool to work).
3) I've tried all the relevant commands from this page and this page, hoping to eradicate whatever errant code is screwing with my phone. Since fastboot seems to be the only way to interact with my phone. I tried:
Code:
fastboot flash recovery /path/to/twrp-3.0.2-0-sirius.img
fastboot -w
fastboot update /path/to/pa_sirius-6.0.3-20160809-signed.zip
the attempt to flash PA through fastboot errored with a message about not having "android-info.txt".
I also desperately tried:
Code:
fastboot erase system
fastboot erase data
fastboot erase cache
the one about data errored. the others seemed fine, but didn't change the situation.
This guide was informative yet quite useless to me, since I definitely don't want to start scripting my phone 2 days after starting this stuff. I've also scoured this forum and others for similar situations, which I've found but they all seemed to get resolved by either doing stuff I've already tried or from having a completely irrelevant problem to my own..
I'm really scratching my head here because it is all stock TWRP and Android or should be by now. adb commands aren't connecting due to stock android not having USB debugging enabled, and without being able to boot into the settings I can do nothing to change that. So all I have is fastboot. I also have a TWRP backup image I made before installing PA but till now Ive seen no way to restore it without booting into recovery.
Any help please!!!! This can't be bricked!!
epeace said:
Hi Im new to the forum but I am finding it to be a massive resource for all things technical android. I am also new to rooting android but am technically savvy, (10 years in IT will do that). Initially it went just fine, even if a speed bump here or there. I got my Sony Z2 rooted and flashed with TWRP (twrp-3.0.2-0-sirius.img) and SuperSU (UPDATE-SuperSU-v2.76-20160630161323.zip) using this guide. I was then able to successfully flash ParanoidAndroid's latest (pa_sirius-6.0.3-20160809-signed.zip) using TWRP recovery. I got a minor bootloop trying to get PA running, but re-flashing seemed to clear it up. It seemed to work fine although I couldn't figure out how to get the pie controls or the halo notifications to work. Without those things i couldn't see the point, so I decided to try Cyanogen. Apparently this uses a different recovery (CWM), I was a little worried but went for it anyway. It seemed to be fine after the first reboot. I started installing apps, rooted fine. But after the next reboot, it started bootlooping. First it would cycle between the Sony screen and a blank screen, But after trying a bunch of things (I'll detail below), it just hangs at the Sony screen indefinitely.
So, what I've tried till now to fix it is:
1) First I tried to reinstall TWRP. The flash went without error, but did not fix the problem. I have not been able to get into recovery since the bootloop. In the process I also did a fastboot -w, which also seemed to have relatively no effect.
2) I tried flashtooling the kernel again with the same from rocker00's post (D6503_23.5.A.0.575_kernel.ftf). No effect. I also tried flashing recovery a few more times using the script from his post to no effect.
3) I've tried all the commands from this page and this page, hoping to eradicate whatever errant code is screwing with my phone. Since fastboot seems to be the only way to interact with my phone. I tried:
Code:
fastboot flash recovery /path/to/twrp-3.0.2-0-sirius.img
fastboot -w
fastboot update /path/to/pa_sirius-6.0.3-20160809-signed.zip
the attempt to flash PA through fastboot errored with a message about not having "android-info.txt".
I also desperately tried:
Code:
fastboot erase system
fastboot erase data
fastboot erase cache
the one about data errored. the others seemed fine, but didn't change the situation.
This guide was informative yet quite useless to me, since I definitely don't want to start scripting my phone 2 days after starting this stuff. I've also scoured this forum and others for similar situations, which I've found but they all seemed to get resolved by either doing stuff I've already tried or from having a completely irrelevant problem to my own..
I'm really scratching my head here because it is all stock TWRP and Android or should be by now. adb commands aren't connecting due to stock android not having USB debugging enabled, and without being able to boot into the settings I can do nothing to change that. So all I have is fastboot. I also have a TWRP backup image I made before installing PA but till now Ive seen no way to restore it without booting into recovery.
Any help please!!!! This can't be bricked!!
Click to expand...
Click to collapse
Welcome to XDA!
May I know what fw version did you initially start with? .575 or .291 or any others?
iXaidyiu said:
Welcome to XDA!
May I know what fw version did you initially start with? .575 or .291 or any others?
Click to expand...
Click to collapse
Hi iXaidyiu,
I started with .291. i stopped going back to it after the first time as I noticed that the custom recovery stopped working in .291. I have had it at .575 since then. And of course now that I can't get into recovery .291 is not an option unless I find an ftf of it for flashtool.
Another observation I forgot to mention is that I cannot turn the thing off. I have to force quit it (vol up + power) and after a second it boots up again to get stuck at Sony screen. I have noticed that if I do the flash boot buttons (vol down + power) I get a different Sony screen (without the xperia logo). But it sticks just the same. I don't even know if the phone is charging at this point, although it was on the Sony screen all night so there must be some charging happening. How could this have gotten so screwed up? It was working fine and I was doing benign activities at the time it choked
epeace said:
Hi iXaidyiu,
I started with .291. i stopped going back to it after the first time as I noticed that the custom recovery stopped working in .291. I have had it at .575 since then. And of course now that I can't get into recovery .291 is not an option unless I find an ftf of it for flashtool.
Another observation I forgot to mention is that I cannot turn the thing off. I have to force quit it (vol up + power) and after a second it boots up again to get stuck at Sony screen. I have noticed that if I do the flash boot buttons (vol down + power) I get a different Sony screen (without the xperia logo). But it sticks just the same. I don't even know if the phone is charging at this point, although it was on the Sony screen all night so there must be some charging happening. How could this have gotten so screwed up? It was working fine and I was doing benign activities at the time it choked
Click to expand...
Click to collapse
Well if so, let's just start from scratch, because you seems to have screwed quite badly and complicated.
Firstly, flash .291 firmware with the three boxes under "Wipes:" ALL CHECKED, check also "AUTO_BOOT" on the right column. These steps will return your device into factory state.
After the flashing process has finished, if your device turned on automatically, turn it off, then unplug the device and replug it when pressing vol+ key, this will enter fastboot mode, you can have two ways to follow now:
(1) Select "Flash", "Fastboot Mode", "Select kernel to flash", navigate to the directory that contain the kernel downloaded (I personally recommand Elite Kernel and extracted), then flash the .IMG file;
(2) Open a cmd using shift+R mouse on the blank space in the directory that stores your twrp.IMG (you can download it here), and type in:
Code:
fastboot flash recovery <filename>.img
and press Enter.
In both method, after you have pressed Enter and see there are two "Okay" printed in the CLI, unplug your device and boot it.
During boot, you will see yellow or green LED light blinked, press vol+ button once and hurray, you will be booted into TWRP recovery!
Now you can load your zip onto your SD card and start flashing! Happy flashing!
P's1 When you tried to boot up your device with the vol- button pressed together, you will be booted into SAFE_MODE, in this mode all 3rd party applications will be disabled.
P's2 I personally DO NOT recommend you to flash zip or erase anything using fastboot commands, use TWRP instead
Thank you iXaidyiu. Option 1, although it fails to boot normally, was successful in getting me back into recovery! Now that I'm in recovery, I first tried to restore my back up. But this failed with errors:
Code:
Failed to mount '/system' (Invalid Argument)
Failed to mount '/data' (Invalid Argument)
Failed to mount '/cache' (Invalid Argument)
So then I tried to flash PA again (since that was the only rom I had on my sd card right now) which also failed with the same errors plus new ones:
Code:
Failed to mount '/data' (Invalid Argument)
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/Download/pa_sirius-6.0.3-20160809-signed.zip'
It also said that "This package is for "sirius" devices; this is a "".". Apparently my Z2 is no longer identifying as 'sirius'. I checked the file system, and I can see that the /data, /cache, and /system folders are physically there. Why are they not mounting? Permissions? :s What to do from here?
UPDATE: This "Failed to mount /data error" seemed to be the root of all the problems till now. Others on the net with this error also see boot hanging at the mfr logo. However, I was able to solve it by formatting /data. I still couldn't flash PA due to the 'This package is for "sirius" devices' error, but I was able to restore my TWRP backup, which then solved the "sirius" ID issue, after which I could flash PA just fine! Thanks iXaidyiu for your help in getting me back into recovery! That was clutch to me finding the solution!
@epeace
If you ever face the device id issue again, unzip the ROM, navigate down /META-INF/com/Google/Android/updater-script and delete the following line:
Code:
getprop("ro.product.device") == "sirius" ||
abort("E3004: This package is for \"sirius\" devices; this is a \"" +
getprop("ro.product.device") + "\".");
(probably the first of the code till a semi-colon)
This disable the Device ID check when you flash the ROM.
P's May I know how's your phone charging status? I am curious cuz' I once tried flashing PA 6.0.3 and all working good EXCEPT the battery cannot be charged. It keeps draining itself even though it can sense the presence of the charger but it still cannot charge:crying:
Ok great tip, I'll make that edit for next time. Re: the charging, I think it's charging, but it's definitely charging very slow. But a number of things could be contributing to that, I'm constantly on it right now (setting it up), i'm charging off of my computer (usually slow to begin with), and this phone is a few years old so the battery is not what it used to be. I'll keep an eye on it the next days, and report back here and let you know what I've observed. Thanks again for your help!
iXaidyiu said:
@epeace
P's May I know how's your phone charging status? I am curious cuz' I once tried flashing PA 6.0.3 and all working good EXCEPT the battery cannot be charged. It keeps draining itself even though it can sense the presence of the charger but it still cannot charge:crying:
Click to expand...
Click to collapse
Hey @iXaidyiu,
I no longer have PA installed, but in the couple days with it I didn't notice any difference in battery performance compared to other ROMs. I think that shouldn't be a deterrent. At the moment I'm trying out GarvityBox on rcstar6696's vanilla MM/Nougat. So far it feels right, although rooting was a little tricky for some reason. We'll see how that goes!
Hello!
I'm one of the folks who did OTA update on my Motorola Moto E (1st gen) and after that the phone became unusable due to lacking internal space. After that my phone started to restart randomly on daily basis (according to other posts it was caused by almost no free internal memory).
I was so tired of not being able to install apps that I decided to root my phone, I've never done it before but somehow I managed to root it, unlock the bootloader, install twrp, su and then downgraded my phone to 4.4.4, I'm not sure but most likely from there:
https://forum.xda-developers.com/moto-e/general/video-tutorial-downgrade-moto-e-android-t3032738
Anyway it's been working perfectly fine but the phone was still reseting itself (which was odd, having over 500 MB of free internal memory). About 4 months passed by and I'm unable to turn on the phone, it's stuck on logo. Pressing power and volume down gives me access to factory and recovery options but factory worked only once and now doesn't work and when I try to do recovery I'm getting red triangle with Android robot on his back.
How do I fix that? Recovery is unusable. I've got https://dl.twrp.me/condor/twrp-2.7.1.0-condor.img, did
HTML:
fastboot boot recovery-twrp.img
but still recovery doesn't work.
Any hints?
[edit]
I managed to install twrp using "fastboot flash recovery recovery-twrp.img", installed latest Linage OS from official thread on our forums, did everything as in: https://www.youtube.com/watch?v=9esNxdH8-eA and I was stuck on loading screen (blue swiping dot along a curved line), but after like 10 minutes the OS finally booted. Not sure what caused my problems, but they seem to be resolved.
[edit 2]
The OS reseted itself right after booting. I guess I might have some hardware issue after all Can I somehow find out what's the state of my internal memory? I think it might be corrupted. Damn.
LG Volt Unresponsive Presses? Factory Reset Results In Talkback Screen & Long Reboots
I'm not even sure how to title this thread. It all got nasty.
The most I've done so far is root my LG Volt.
I was just recently pursuing building an AOSP ROM and even used "dd" to back up EVERY partition to my computer.
Then, I also had wiped the laf partition to get to fastboot rather than "recovery" (download mode (volume-up&power)). THEN, I fastboot restored the backed up laf partition.
This was all probably 2-3 weeks ago.
Now last night, my phone became more and more unresponsive, to where I just had to reboot and the unresponsiveness didn't get better AND the script used for mounts to my sdcard didn't work and when I even tried to "su" while in adb, I never was able to get root for some reason (which likely explains the permitted root apps to fail to run).
And it only gets worse. One of the times I rebooted, the keypad didn't come up to decrypt the drive. Eventually I gave it time and it came up. But even BEFORE decrypting, I'd get notices of apps failing like Settings (and I hadn't even booted yet).
At this point, I didn't have many (any?) options left. I can't adb/fastboot with Volume-Up/Down & Power (lg nerfed it?)
I mean, I can boot to those (screens?), but can't use the programs on my computer (no device is found in those modes, unlike when I could adb while fully into android).
So, I have been able to get to the fastboot screen and wipe cache and also factory reset (wipe data).
When I reboot from fastboot, boot takes about 6-7 minutes and android starts with the Talkback screen.
But again, the screen presses are nearly unresponsive. When pressing "Next" finally registers, my phone ends up rebooting and NEVER boots up.
It starts with the LG boot logo and the smooth "glimmer" animation. After maybe 15 minutes, it seems like it reboots again (or maybe a 2nd stage of boot or something?) and that "smooth" animation now becomes "jittery", like the cpu is really being taxed.
Again, I hadn't flashed any ROMs with this phone yet, so surely the factory reset would've brought it all back to a clean state.
Also, I DID remove my old swollen battery (gassed-up for maybe 2 years now (yes, I know I'm practically playing with fire)) too, and put it back in.
I would always have my phone plugged into my computer so it would always be charged.
What are my options at this point for my 3+ year old phone? Is there a way to get to adb/fastboot so I can restore what I backed up before? Can I sideload a ROM from my sdcard? ...?
What I'd like to do is fsck the data partition and maybe even run badblocks on it.
While typing all this out and reviewing it, that part of the boot with the jittery logo disappeared, so it may now be onto the stage of getting back into the main android start screen. Ouch, that boot audio really struggled, again like the cpu is really being hammered.
Nope, the logo is coming back up again and really struggling to even display the logo. The G and "Life's Good" is still fading in VERY slowly.
Well, luckily I was still able to use the old flash method https://androidforums.com/threads/guide-brick-recovery.893332/
Now I look to restore the partitions I had previously backed up with dd.
The problem is, I never backed up the decrypted dm-0, but rather the encrypted userdata mmcblk partition.
Does twrp or something have the ability to restore the encrypted mmcblk partition and what I guess is the small "encrypt" partition that I assume contains the encryption key?
My Nook HD+ bootloader won’t launch the installed OS, CM 13. The Nook screen appears, and then gives way to the Cyanogenmod Universal Bootloader. After a bit the blue android image appears. It pulses normally at first, then the pulsing pauses, and finally the process starts all over … and over, and over, and over!
At first I thought there was a problem with the OS, so I booted into recovery (TWRP 3.1.1-0) and tried to flash CM 13 for ovation. That didn’t work, so I tried flashing other ovation ROMs. None will install. They all report an ERROR 7. I’ve attempted to work around that error, but none of the methods I’ve found made any difference.
It seems that I may have to reinstall the factory/stock ROM, and I’m okay with that. But it seems I can’t do that either. The stock rom download is in a CWM backup format, and I have TWRP, not CWM. So I tried to flash CWM with TWRP, but in order to make that work one has to reboot into recovery via TWRP, The problem here is that the TWRP boot menu has just two options … System and Power Off. The Recovery option that is supposed to be there isn’t!
So I tried to replace TWRP with CWM via ADB. I can sideload a CWM zip without a problem. I then issue an ADB Reboot Recovery command. But, instead of rebooting into recovery, the bootloader launches instead. As a result, when I go into recovery it’s still TWRP. I’ve also tried powering on with the CWM bootable image file on an sd card, but no matter how many times I power off and back on, my tablet never recognizes that the file is there and my problem persists.
Is there a way to boot into CWM or swap CWM for TWRP in a situation like this? I’ve seen postings that suggest fastboot may the be solution, but that requires that debugging be enabled, and it was not enabled when my problems began. Apparently there is no way to enable debugging without launching the OS.
Help!
Update:
My Nook HD+ has not rewarded my attempts to bring it back to life Perhaps I’ve made things worse. I certainly haven’t made things better. Here’s the latest.
When booted up, little or nothing has changed. At bootup the Nook screen is followed by the Cyanoboot Universal Bootloader screen. Sometimes it gets no further, and reboots. More often the android image appears with a halo pulsing in the background. Sometimes the halo pulses a couple of times before the device reboots. Sometimes is pulses a bit longer before rebooting. Sometimes it never stops pulsing (until I press and hold the power button to shut the bloody thing down, that is).
Thinking the problem was related to the OS (I had been running android 7.1.1 (an unofficial HD+ release, but from a very reliable source), I've tried in vain to flash another OS. I've tried multiple android releases, from 7.1.1 down to 4.4.4. I've also tried flashing several versions of the HD+ factory stock OS. I’ve done all this using TWRP, and also by booting CWM from an sd card. No matter which recovery I've used or which OS I've attempted to install, the process always ended with an ERROR: 7.
So, I got my hands on a good Nook HD+ running android 5.1.1. I made unbundled TWRP backups of the System, Boot, and Apps partitions using release 3.1.1-0. The System and Boot partitions each restored without a problem. The Apps would not restore, ending with “extractTarFork() process ended in ERROR: 255." That error probably isn’t related to my problem, which is that I can’t get the system to boot up. More telling is the fact that after successfully restoring the System and Boot partitions using the backup from a good HD+, when I power up the device appears to be launching 7.1.1, not 5.1.1. The android image displays in portrait mode on the good HD+ running 5.1.1, but displays in landscape mode on my HD+ ... and the boot loop continues, of course.
At this point, at the $7.25/hour minimum wage rate I’ve spent enough time that I could have earned many times the original cost of the HD+. So, am I giving up? HELL NO! Now it’s personal!!
My HD+ boots into TWRP flawlessly, so I still have that going for me. My HD+ is not rooted and did not have USB Debugging enabled when it crashed, so any solution requiring SU or flashboot is a non-starter. Otherwise, I’m willing to give anything a try. Maybe I should be looking for an exorcist?
Thanks for reading this, and for your suggestions, words of encouragement, and expressions of sympathy.