adb reboot bootloader only boots to "fastboot mode..." - Upgrading, Modifying and Unlocking

I am following this guide
gearallnews.___/how-to-install-lineage-os-17-on-umidigi-a5-pro/ (sorry for the circumvent. felt it was important for the pros to check the source)
since I have a newer phone (at the time of this writing) Android 9.
but regardless of the above site or any instructions regarding "adb" and "fastboot" it always takes me to the black screen with tiny print at the bottom that says "fastboot mode.." and thats it. If I just do Vo+Pow it will take me to a menu from clearing cash to rebooting the system and factory reset. Can even boot to bootloader, but it gives me the same black screen with those tiny words at the lower left of the screen, everything else is blank.
I have to use the power button to shut off, then again to reboot to normal.
when I type fastboot devices, nothing,
adv devices (before the boot) will show the correct phone
All the other UMIDIGI AS5 PRO tutorials seem to work fine.
This is a dual sim, unlocked phone.
Any suggestions?

OK fixed all the issues (a5 pro driver missing, FIXED, mtk67xx installed)
(thought) I installed TWRP but when booting to bootloader, all it says is "fastboot mode..." and the screen in blank
So tried a different method, by rooting this from scratch, so first thing was to make a scatterfile.txt
Powered up the MTK DROID ROOT & TOOLS and got the following message (of course because of this, cannot use the ROOT button successfully)
Code:
--->>> Connect to device <<<---
--- ERROR : --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!
--- Unknown ROM structure, backup NOT possible!
ATTENTION! File /system/recovery-from-boot.p which restore factory recovery in case of phone switching on in a normal mode Is Found!
"/data/local/tmp/pwn": error: Android 5.0 and later only support position-independent executables (-fPIE).
ATTENTION! Requests for confirmation on the device screen are possible!
What to I have to fix/clean up?
Thanks for any suggestions
EDIT: Yes the phone is still working fine, (other than th emessage the phone is not safe because the booloader is not locked)

Related

[Q] attempted kitkat revert, almost completely unresponsive

I have a bone stock 2013 Nexus 7 32 Gb Wifi, never had a problem with it. A few weeks ago, it notifies me of an update (Lollipop) so I apply it. Nothing but problems since then. It was very laggy and would glitch every few seconds while playing video (either local files or streamed over Plex, both had same issue). Sometimes when I'd wake it from sleep, the screen would look like an old CRT TV with static (except it wasn't moving, it was a fixed image). It would hang like this for seconds or sometimes minutes. Rebooting would usually resolve this for a while.
Tried a few 'lollipop tuning' tweaks, but when these failed to fix the video glitching and lagginess, I decided to revert to kitkat and followed an online tutorial (exactly like the one here except it had me install a standalone ADB/fastboot instead of full SDK) . No problem installing USB driver or setting nexus into USB mode. No problem getting it into fastboot mode and "fastboot devices" correctly listed the device, and "oem unlock" appeared to work fine as well. Running the flash-all batch file also seemed to go normally. But now my device is even worse than before:
- won't boot/run normally... no boot-up logo or video ever displays (or if it does, it's just a partial static image). Appears to get to a 'welcome' screen but the display is all messed (part of the screen is just repeated several times, so you can't see the entire screen). Unresponsive to touch, though it will make some sounds when you press in certain areas, but the display never changes. If I sleep it and wake it up, it shows the 'CRT static' mentioned above for many seconds before showing slowing showing the tiled/corrupted welcome screen. I can access the nexus' file system over USB on my PC even while it's in this borked state.
- display is now blank when getting into fastboot mode... i can time pushing the down-volume and power button so I know I am in fastboot mode ('fastboot devices' correctly lists the device) but the display is now completely black (not on, no backlight) in this mode.
I tried flashing to factory 4.4.4, 4.3, and 4.2 (always using 2013 wifi images) and it doesn't make a difference. Same results. Is there some bit of code that doesn't get reflashed during this reset that could explain why I'm having these issues? Any advice how to fix?
flyingsherpa said:
I have a bone stock 2013 Nexus 7 32 Gb Wifi, never had a problem with it. A few weeks ago, it notifies me of an update (Lollipop) so I apply it. Nothing but problems since then. It was very laggy and would glitch every few seconds while playing video (either local files or streamed over Plex, both had same issue). Sometimes when I'd wake it from sleep, the screen would look like an old CRT TV with static (except it wasn't moving, it was a fixed image). It would hang like this for seconds or sometimes minutes. Rebooting would usually resolve this for a while.
Tried a few 'lollipop tuning' tweaks, but when these failed to fix the video glitching and lagginess, I decided to revert to kitkat and followed an online tutorial (exactly like the one here except it had me install a standalone ADB/fastboot instead of full SDK) . No problem installing USB driver or setting nexus into USB mode. No problem getting it into fastboot mode and "fastboot devices" correctly listed the device, and "oem unlock" appeared to work fine as well. Running the flash-all batch file also seemed to go normally. But now my device is even worse than before:
- won't boot/run normally... no boot-up logo or video ever displays (or if it does, it's just a partial static image). Appears to get to a 'welcome' screen but the display is all messed (part of the screen is just repeated several times, so you can't see the entire screen). Unresponsive to touch, though it will make some sounds when you press in certain areas, but the display never changes. If I sleep it and wake it up, it shows the 'CRT static' mentioned above for many seconds before showing slowing showing the tiled/corrupted welcome screen. I can access the nexus' file system over USB on my PC even while it's in this borked state.
- display is now blank when getting into fastboot mode... i can time pushing the down-volume and power button so I know I am in fastboot mode ('fastboot devices' correctly lists the device) but the display is now completely black (not on, no backlight) in this mode.
I tried flashing to factory 4.4.4, 4.3, and 4.2 (always using 2013 wifi images) and it doesn't make a difference. Same results. Is there some bit of code that doesn't get reflashed during this reset that could explain why I'm having these issues? Any advice how to fix?
Click to expand...
Click to collapse
So your bootloader is blank right? I would flash a new bootloader asap! And see if that fixes anything
noahvt said:
So your bootloader is blank right? I would flash a new bootloader asap! And see if that fixes anything
Click to expand...
Click to collapse
I have to confess my ignorance here... I'm brand new to flashing android like this so I don't know the answer to your question. If part of tutorial I followed blanks out the bootloader (and doesn't write something in?)... then you're probably right. I shall look into this more tonight when I'm at home with the nexus. Thanks for at least giving me something to look into, that's exactly what I was hoping for!
This sounds more like a hardware issue than software to me. See if you can get a warranty repair or replacement.
From another thread by a user with a blank screen like yours:
Asus_USA said:
a7medmo7eb - We're very sorry to hear of this. Kindly email us at [email protected] with this copied problem description along with the serial number of your tablet and we will do our best to provide you with troubleshooting and servicing options.
If you have any further questions, comments or concerns please do not hesitate to let us know. We will be more than happy to assist you. Once again, thank you for choosing ASUS products and services.
Thank you.
-In Search of Incredible-
Technical Support Department
http://www.asus.com :: http://service.asus.com/
Click to expand...
Click to collapse
nhizzat said:
This sounds more like a hardware issue than software to me. See if you can get a warranty repair or replacement.
From another thread by a user with a blank screen like yours:
Click to expand...
Click to collapse
Thanks, you're probably right. I did read up to understand all this stuff a bit more, so I know it's not lack of a bootloader or anything. All img files install just fine, so my pc can talk to the nexus, just the screen is all wonky no matter what i do.
Unfortunately I bought this 1.5 years ago so I don't think it's under warranty anymore. Everything was fine until I updated to Lollipop! Seems a big coincidence that I had a hardware failure at the same time as that update... I feel like Google ruined my tablet...
There is a bug where sometimes when you unlock the bootloader it zeros out the data partition. This might be the cause of your problem. It happened to me when I unlocked mine and I got stuck in a bootloop where it kept booting into recovery then shutting off. I fixed the problem by using fastboot to format data. Also, the flashall script didnt work for me. I put all the .img files in the same folder as fastboot then used these commands.
fastboot format data
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
after this I booted into recovery and did a factory reset for good measure and the problem was fixed. This may solve your problem. It may also be possible that you got a bad download. I hope this helps you
Masterchief87 said:
There is a bug where sometimes when you unlock the bootloader it zeros out the data partition. This might be the cause of your problem. It happened to me when I unlocked mine and I got stuck in a bootloop where it kept booting into recovery then shutting off. I fixed the problem by using fastboot to format data. Also, the flashall script didnt work for me. I put all the .img files in the same folder as fastboot then used these commands.
fastboot format data
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
after this I booted into recovery and did a factory reset for good measure and the problem was fixed. This may solve your problem. It may also be possible that you got a bad download. I hope this helps you
Click to expand...
Click to collapse
Hmm, thanks for the idea, but fastboot wouldn't do "format data", giving me the error: Formatting is not supported for filesystem with type ' '
Googling that makes it not look good. Weird, thing is, it still technically boots up, just the screen is so wonky you can't see where you are or interact with it properly. Not sure what else to try (opening it up and re-seating touchscreen cables?).

Soft Bricked - Unable to Sideload OTA

Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked
SomewhatIrked said:
Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked
Click to expand...
Click to collapse
Did your phone just reboot in the middle of doing something innocuous then start bootlooping? Were/Are you on total stock with bootloader locked? If both yes, it is probably hardware issue you are encountering.
Regarding sideloading, did you place your Android recovery in sideload mode?
Did you verify adb can "see" your device using "adb devices"?
SomewhatIrked said:
Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked
Click to expand...
Click to collapse
Well luckily I made this post today.
The more this goes on, the more I believe it to be hardware ...
@sfhub - reasonably innocuous. Had just opened one or 2 apps that morning. Not sure what had updated overnight app/os wise. Not anything interesting as far as I can tell. Once I managed to get it into recovery "adb devices" was returning the phone.
@bardhi92 - I saw that once I got in. However, I couldn't get it to see my phone.
Updated things I have tried and why I've all but thrown in the towel:
After the OTA rescue sideload failed I started trying a few different things. It stopped taking me into recovery mode more frequently, at least it seemed that way - it would just keep bootlooping. My main issue is that I has a locked bootloader, which stopped me whacking TWRP on and loading on a custom rom - just to see if that worked.
I thought it might let me sideload on a factory default img file. Turns out nope.
However I used NRT to "Flash Stock + Unroot" (with "Soft Brick/Bootloop" checked) which for some reason, then allowed me to get back into recovery mode. I had also removed the sim card/tray at this point. May have been either or neither of those that allowed me to get into recovery mode. Can't say for certain.
I cleared /cache and /data and then attempted the OTA rescue update again. This time it failed at 45% (according to my cmd prmpt) with the error: "* failed to read command: No error". I'm not sure text was on the phone at the time. But it did manage to boot into Android. I quickly stepped through the various intro steps (putting in the sim, adding my mail google account details).
I went to get a beer. Only to find it boot looping again.
Not to be deterred, I vowed to try again. Same steps as before (remove sim, nrt voodoo). This time however the OTA rescue worked and fully completed. I went through the intro steps again. This time I quickly turned on dev options, enabled usb debugging and sorted out the OEM bootloader. I thought this would be smart, just in case it hapened again. Once I chose to unlock ("fastboot reboot", selected yes), it decided to start boot looping again.
The main annoyance is: I don't think I have any proof of purchase, even though it's in warranty. That, and I now live in Dubai - so shipping back to the UK where I brought it is going to be killer. But I think it's the path of least resistance at the moment.
SomewhatIrked said:
The more this goes on, the more I believe it to be hardware ...
@sfhub - reasonably innocuous. Had just opened one or 2 apps that morning. Not sure what had updated overnight app/os wise. Not anything interesting as far as I can tell. Once I managed to get it into recovery "adb devices" was returning the phone.
@bardhi92 - I saw that once I got in. However, I couldn't get it to see my phone.
Updated things I have tried and why I've all but thrown in the towel:
After the OTA rescue sideload failed I started trying a few different things. It stopped taking me into recovery mode more frequently, at least it seemed that way - it would just keep bootlooping. My main issue is that I has a locked bootloader, which stopped me whacking TWRP on and loading on a custom rom - just to see if that worked.
I thought it might let me sideload on a factory default img file. Turns out nope.
However I used NRT to "Flash Stock + Unroot" (with "Soft Brick/Bootloop" checked) which for some reason, then allowed me to get back into recovery mode. I had also removed the sim card/tray at this point. May have been either or neither of those that allowed me to get into recovery mode. Can't say for certain.
I cleared /cache and /data and then attempted the OTA rescue update again. This time it failed at 45% (according to my cmd prmpt) with the error: "* failed to read command: No error". I'm not sure text was on the phone at the time. But it did manage to boot into Android. I quickly stepped through the various intro steps (putting in the sim, adding my mail google account details).
I went to get a beer. Only to find it boot looping again.
Not to be deterred, I vowed to try again. Same steps as before (remove sim, nrt voodoo). This time however the OTA rescue worked and fully completed. I went through the intro steps again. This time I quickly turned on dev options, enabled usb debugging and sorted out the OEM bootloader. I thought this would be smart, just in case it hapened again. Once I chose to unlock ("fastboot reboot", selected yes), it decided to start boot looping again.
The main annoyance is: I don't think I have any proof of purchase, even though it's in warranty. That, and I now live in Dubai - so shipping back to the UK where I brought it is going to be killer. But I think it's the path of least resistance at the moment.
Click to expand...
Click to collapse
So, you flashed the .TOT file, sideloaded the given OTA within the stock recovery bootloader that comes with the .TOT file, and cleared cache/factory reset?
Please condense it. If you managed to start up the phone, that's a huge success for people who have not been able to yet.
bardhi92 said:
So, you flashed the .TOT file, sideloaded the given OTA within the stock recovery bootloader that comes with the .TOT file, and cleared cache/factory reset?
Please condense it. If you managed to start up the phone, that's a huge success for people who have not been able to yet.
Click to expand...
Click to collapse
In short:
OTA rescue failed during adb sideload,
Tried bullhead-nbd90w-factory-d2f11c5f.zip & removed sim tray - seemed to allow access to recovery mode,
OTA rescue claims to have failed at 47% during adb sideload- still booted into android. However briefly. Went back to bootloop,
Tried bullhead-nbd90w-factory-d2f11c5f.zip & removed sim tray - seemed to allow access to recovery mode,
OTA rescue completed via adb sideload,
Turned on dev options (usb debug, oem unlock),
Booted to fastboot - unlocked bootloader. Now back to bootlooping
@bardhi92 - I could not get the LG utility to detect my phone. Will attempt again tomorrow.
SomewhatIrked said:
@bardhi92 - I could not get the LG utility to detect my phone. Will attempt again tomorrow.
Click to expand...
Click to collapse
IMO you shouldn't flash the TOT file. If you end up bootlooping again, your phone will be stuck in bootloader locked mode with no ability to unlock it.
If you were able to get your phone to boot into android once, there is really nothing the TOT file will do for you that you can't do from TWRP or bootloader, whereas once it locks your bootloader, there are problems you can no longer fix like EFS corruption (which likely isn't your problem).
In the end, you probably do have eMMC that is slowly starting to fail. There is usually error correction on the eMMC that can lock out bad blocks but if it gets to serious, it'll fail. This is why reflashing stuff over and over sometimes works.

HTC DESIRE 820 (OPFJ400 D820N) - "Decrypt Storage" Problem

Hello fellow android lovers!
I need help with said Smartphone from everyone with a knowledge bigger than mine.
Ill start from the beggining:
Friend of mine had this phone for a really long time. The condition of said device is nearly new (Few minor scratches here and there).
He decided not so long ago, to change his phone to newer one, so that one went to the drawer where it was for like a year or so.
He came to me a week ago with this phone, because he wanted to give it to his child as a first smartphone.
On that HTC device, after booting the system, there is a notification "Decrypt Storage" where you need to enter password to decrypt ROM memory. He said he never used any password on his device and even on new smartphone, he did not put any lock kode or pattern.
After entering any password, even with one letter, the notification says: "The password is correct, but unfortunately your data is corrupt" then there is a "reset phone" whitch restores smartphone to factory state.
Sadly, this doesnt work. It shows the same notification after factory reset. More like a bootloop but with a note.
I tried to hard reset it, but after i choose in bootloader "Factory reset", it takes me to main menu of bootloader and it says "Failed"
I also tried to get to the phone via USB. I installed htc usb drivers, got the binares to unlock bootloader and the fastboot option works, adb isn't.
I tried to use Fastboot factory resset command, tried also flashing TWRP recovery and nothing.
The wierd thing is, that the bootloader unlock binaries is not working as i see on the device because after "Unlocking" Bootloader, i go to the Bootloader menu and it allways says:
*****LOCKED*****
*****SOFTWARE STATUS: MODIFIED*****
*****SECURITY WARNING*****
Click to expand...
Click to collapse
The wierd thing is, that software status was modified even when he gave me this phone to work with. He is not the type of android poweruser. I doubt that he will modify his software.
Can somone help me with some tips how to flash a new system or get this device to work? I am banging my head on the wall right now. I am out of options.

your device is corrupt. it can not be trusted and not boot

I'm sorry if the post is not in the right place.
I own a z2 force that turned itself off and the rear camera did not work.
Putting the "power low" message on the recovery screen, even when the full charge appeared, after a time off "power ok" was displayed.
One moment he did not call any more and I tried bootloader, but without being able to activate usb debugging (my fatal error!), Now the message "your device is corrupted. It can not be trusted and it does not boot" and I can not unlock bootloader nor flash a new rom to boot the device.
obs: camera and battery problems appeared after the upgrade via ota to 8.0 actions
Solved.
eriton carlos said:
I'm sorry if the post is not in the right place.
I own a z2 force that turned itself off and the rear camera did not work.
Putting the "power low" message on the recovery screen, even when the full charge appeared, after a time off "power ok" was displayed.
One moment he did not call any more and I tried bootloader, but without being able to activate usb debugging (my fatal error!), Now the message "your device is corrupted. It can not be trusted and it does not boot" and I can not unlock bootloader nor flash a new rom to boot the device.
obs: camera and battery problems appeared after the upgrade via ota to 8.0 actions
Click to expand...
Click to collapse
I was able to start the device after hours looking for a solution, now I'm flashing a new rom to try to fix the camera problem and automatic shutdown.
How do you solve it?
I usually buy second hand Motorola phones (also this ATT Z2F), but I've never met the problem on individual hardwares yet (like camera, fingerprint sensor). Almost errors can be solved via flashing a right firmware. I think you can now flash fw via Lenovo Moto Smart Assistant (LMSA). If you use flashall.bat method, just take a look at the xml file and compare it to the content of flashall.bat (two types can be opened by Notepad, Notepad++ is recommended). The xml one shows what will be flashed.
For example: in the xml one has oem.img_sparsechunk.0-1-2, but in flashall.bat only has: fastboot flash oem oem.img
If you continue, your phone won't boot.
You have to edit flashall.bat:
fastboot flash oem oem.im_sparsechunk.0
fastboot flash oem oem.im_sparsechunk.1
fastboot flash oem oem.im_sparsechunk.2
Save and continue your works.
The xml is the standard file for RSD Lite. But, RSD seems not to be supported on recent PC hardwares, so step-by-step fastboot or flashall.bat is recently used. Therefore, just take a look before flashsing (other preparations won't be mentioned here). You should flash the equal or higher version to your current fw version on your phone.
Hope this works for you all.
i'm facing same problem,
eriton carlos said:
I was able to start the device after hours looking for a solution, now I'm flashing a new rom to try to fix the camera problem and automatic shutdown.
Click to expand...
Click to collapse
how you get repaired your phone?

[SOLVED] Soft brick (?) on Z1C-based ZPG handheld

SOLVED: I figured out the issue. As mentioned in this thread, downgrading to an older version of flashtool successfully got me past the bundle mismatch error, allowing me to flash stock US firmware onto the device. Still not exactly sure why that's the case, but it worked for me.
Hey folks,
Hope you're all doing well! I have a bit of an odd situation. I recently picked up a Z-Pocket Game, a handheld built using the internals from a torn down Z1 Compact.
A few days ago, I decided to see if I could poke around and install a custom ROM onto the device, given how many are available for the source hardware (Z1C). The device already came pre-installed with XZDualRecovery and was running a custom ROM in Chinese built off Lollipop.
I'm a novice when it comes to flashing and custom ROMs, so I tried to learn more about the process before getting started. Evidently, however, I'm in over my head - fully my responsibility, of course, but over my head nonetheless.
Long story short, I tried to install Lineage OS 17.1 onto the device via the version of TWRP already installed on the device. As per the installation instructions detailed here, I did an advanced wipe before attempting the install, selecting "Dalvik," "System," "Cache," and "Data." When I actually attempted the process, however, it errored out almost immediately, leaving me with a wiped system and no ROM (TWRP warned me about this prior to rebooting).
When I now power on the device, it's stuck on the "Sony - XPERIA" screen, and the LEDs don't light up at all. I can't seem to access TWRP or Philz on the device with the normal key presses. I can force the device off by holding Power and Volume Up, and it also seems able to enter fastboot mode (with a solid blue LED) and flash mode (the LED flashes green, then turns off). I've tried a number of different things to try and fix it, but all of them haven't worked in one way or another. Providing a brief overview to the best of my recollection here, but happy to try again and give more detail if needed:
Using fastboot via the command line to flash a new recovery onto the device gives me an error indicating I can't write the file to the device, and things just end there.
Trying to flash a stock US ROM to the device via flashtool gives me an error indicating the device does not match the bundle, and things just end there.
Trying to restore the device using Xperia Companion first gives an error requesting permission to access the device, then when I select "My Device Cannot Be Detected or Started" and follow the instructions, it tells me that "an error occurred while repairing this device," and provides this small blurb of device info:
UEGetPhoneInfoMissingInfo
Z-POCKET GAME 3579 1279-6978 R2D 14.6.A.1.236
2.11.6.0 / Windows 10 64 bit / Win32 / US / /
So I'm a bit stumped. It seems as though enough of the device is working to get everything back into a workable state, but I'm not sure of how to go about that. Any thoughts or leads would be greatly appreciated!
edit_duplicate said:
SOLVED: I figured out the issue. As mentioned in this thread, downgrading to an older version of flashtool successfully got me past the bundle mismatch error, allowing me to flash stock US firmware onto the device. Still not exactly sure why that's the case, but it worked for me.
Hey folks,
Hope you're all doing well! I have a bit of an odd situation. I recently picked up a Z-Pocket Game, a handheld built using the internals from a torn down Z1 Compact.
A few days ago, I decided to see if I could poke around and install a custom ROM onto the device, given how many are available for the source hardware (Z1C). The device already came pre-installed with XZDualRecovery and was running a custom ROM in Chinese built off Lollipop.
I'm a novice when it comes to flashing and custom ROMs, so I tried to learn more about the process before getting started. Evidently, however, I'm in over my head - fully my responsibility, of course, but over my head nonetheless.
Long story short, I tried to install Lineage OS 17.1 onto the device via the version of TWRP already installed on the device. As per the installation instructions detailed here, I did an advanced wipe before attempting the install, selecting "Dalvik," "System," "Cache," and "Data." When I actually attempted the process, however, it errored out almost immediately, leaving me with a wiped system and no ROM (TWRP warned me about this prior to rebooting).
When I now power on the device, it's stuck on the "Sony - XPERIA" screen, and the LEDs don't light up at all. I can't seem to access TWRP or Philz on the device with the normal key presses. I can force the device off by holding Power and Volume Up, and it also seems able to enter fastboot mode (with a solid blue LED) and flash mode (the LED flashes green, then turns off). I've tried a number of different things to try and fix it, but all of them haven't worked in one way or another. Providing a brief overview to the best of my recollection here, but happy to try again and give more detail if needed:
Using fastboot via the command line to flash a new recovery onto the device gives me an error indicating I can't write the file to the device, and things just end there.
Trying to flash a stock US ROM to the device via flashtool gives me an error indicating the device does not match the bundle, and things just end there.
Trying to restore the device using Xperia Companion first gives an error requesting permission to access the device, then when I select "My Device Cannot Be Detected or Started" and follow the instructions, it tells me that "an error occurred while repairing this device," and provides this small blurb of device info:
UEGetPhoneInfoMissingInfo
Z-POCKET GAME 3579 1279-6978 R2D 14.6.A.1.236
2.11.6.0 / Windows 10 64 bit / Win32 / US / /
So I'm a bit stumped. It seems as though enough of the device is working to get everything back into a workable state, but I'm not sure of how to go about that. Any thoughts or leads would be greatly appreciated!
Click to expand...
Click to collapse
Glad that you find out yourself.
And thanks for sharing!

Categories

Resources