This device was updated to 3.2, used very little and then battery died after 2-3 days (never rebooted since update)... forgot to plug up and when I did it's giving me "Unrecoverable bootloader error"
It's not rooted so I'm not quite sure what I can do to it... any ideas?
Only one thing you can do is call tech support at Toshiba and that is it, with 3.2 rooting is not a option because Toshiba has removed fastboot, so about all you can do is contact them and send it in for a reflash!!!
Related
I picked up a tablet off eBay for 80 bucks that was listed for parts/not working simply because they couldn't get it past the setup screen. Otherwise it's in mint condition. My goal when buying it was to use the screen to replace my cracked one so the only thing that popped in my mind was "WE KNOW THE SCREEN WORKS!". I also figured it may just be a software issue that could easily be fixed then I'd just transfer my nandroids over to the new tablet and forget about repairing my old one.
I got it home and realized the part that they couldn't get past was the WiFi connect (no skip option). The screen said "Turning WiFi on" and was hung. I unlocked the bootloader and used Wug's toolkit to boot into TWRP then hacked the build.prop to get past the setup process. It was after I got into the OS that I realized it was already rooted and running LeanKernel and Debugging was already enabled so that further reinforced my thoughts of a software issue. I figured someone messed with rooting and flashing ROMs then fudged it up, factory reset it, then relocked the bootloader to make it look factory.
I had to connect it as a camera for it to show up in Windows (it was also then that the RSA key message appeared) then transferred an AOKP zip over and flashed it via TWRP. Rebooted and still had the WiFi issue. Last night I downloaded factory images and flashed them via fastboot and still the issue persists so I'm figuring now it's a hardware problem. What debugging steps can I go through to confirm whether it's software or hardware-related?
EDIT: I know a way of getting out of the bootloader but it requires me to unlock it (even though I left it unlocked after initially doing it). Unfortunately, though, I think I'm left with a £150 paperweight since I need an OS on the device to enable OEM unlocking and the device literally has no OS or recovery after the hard brick. Motorola have been very "supportive" about my situation even after sending them a 10 paragraph email explaining everything which obviously, they didn't read because I wrote on the first line that the device has been rooted so they knew beforehand. I wrote 10 paragraphs, they replied with six lines, so... Yeah.
I installed LineageOS 14 on my Moto G4 months ago with TWRP and I've never had any issues until today. Literally, just updated to a new nightly build for LineageOS and my phone screen went black and didn't turn back on. I plugged it into my computer and it showed up as QHSUSB_BULK. Obviously, at this point, my device was hard bricked but I found a way online of using Qualcomm's recovery thing they have to get my phone working again, which I did. But now, I've sorta ended up soft bricking the device now.
The device boots up into the bootloader (or what I think is the bootloader). What comes up is just white text at the bottom which basically just tells me information about my phone (product/variant, serial number, CPU, eMMC, DRAM etc.) The menu for the bootloader is just one string of text that only reads 'Start' and when I press the volume buttons, it will show up with more options but they're all highlighted in red and they all lead to the same error message, as follows:
Bootloader logs
Start Up Failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer
to repair your device.
Connect your device to your computer to get
the Software Repair Assistant.
I've looked around Google for the Software Repair Assistant and it appears to only be for Verizon Wireless and since I'm in the United Kingdom, Verizon Wireless doesn't even exist over here, nor do I even have them as my phone carrier. I'm with O2.
Also, I've tried a few things with Minimal ADB and Fastboot but every time I enter a command, it fails and say's 'FAILED (remote failure). My phone is detected in Fastboot, but not in ADB.
Hopefully, I can get this fixed.
Thanks,
Gabriel.
Guys, i am having the same issue too. I am getting the same issue. Since verizon is not available in india, unable to repair the phone since soft bricked. Kindly help.
did you try to enter fastboot>recovery and get the robot? if you can get that try holding the the power key and tap the up volume. that should give you a drop list with a factory reset option. click it and see what happens?
same problem here.
my phone is rescued.
llaalways said:
same problem here.
Click to expand...
Click to collapse
Hello developers,
A friend of mine was using a Huawei P10 Lite (WAS-LX1A). After an OTA Update errer, the phone was running quit ****. It was laggy af, Battery was nearly empty after a view hours and much more other bugs. I flashed my Huawei P7 multiple times (30-40 flashes) and my Galaxy SIII with LionageOS was also still working untill hardware crash becouse i dropped the Phone on the street. After installing ADB and Fastboot, i wrote down the Speccs of this phone to get an unlock code from tech support. Bootloader was successfully opend, and now, im lost. Huawei eRecovery show up "Download latest version and recovery". Using this method shows up an error "Unable to recieve Device information" or something like this. it seems i lost my ADB Access, "ADB Devices" seems empty and windows is playing a sound when Plugin/out the phone from USB. Currently im unable to handle this problem, i dont know where the problem is, it seems there is no system/OS running on the device. The phone is booting endless in two screens. The 1st one is the "Your phone can not be trusted" screen wich is the result of unlocked the boot loader. The 2nd screen is Huawei eRecovery what is useless, i only can reboot and shutdown. Recovering doesnt work.
What u also need to know: I lost the unlock code, speccs and other informations abbout this phone so bootloader is unlocked, hopefully this is no major problem.
This of has NO ROOT. Only opend bootloader and a bricked OS. There is no TWRP or other stuff installed!
Hopefully there is a way to install TWRP and a OS or maybe back to stock rom. I dont care wich one if the phone works again.
BlitzlichtHD said:
Hello developers,
A friend of mine was using a Huawei P10 Lite (WAS-LX1A). After an OTA Update errer, the phone was running quit ****. It was laggy af, Battery was nearly empty after a view hours and much more other bugs. I flashed my Huawei P7 multiple times (30-40 flashes) and my Galaxy SIII with LionageOS was also still working untill hardware crash becouse i dropped the Phone on the street. After installing ADB and Fastboot, i wrote down the Speccs of this phone to get an unlock code from tech support. Bootloader was successfully opend, and now, im lost. Huawei eRecovery show up "Download latest version and recovery". Using this method shows up an error "Unable to recieve Device information" or something like this. it seems i lost my ADB Access, "ADB Devices" seems empty and windows is playing a sound when Plugin/out the phone from USB. Currently im unable to handle this problem, i dont know where the problem is, it seems there is no system/OS running on the device. The phone is booting endless in two screens. The 1st one is the "Your phone can not be trusted" screen wich is the result of unlocked the boot loader. The 2nd screen is Huawei eRecovery what is useless, i only can reboot and shutdown. Recovering doesnt work.
What u also need to know: I lost the unlock code, speccs and other informations abbout this phone so bootloader is unlocked, hopefully this is no major problem.
This of has NO ROOT. Only opend bootloader and a bricked OS. There is no TWRP or other stuff installed!
Hopefully there is a way to install TWRP and a OS or maybe back to stock rom. I dont care wich one if the phone works again.
Click to expand...
Click to collapse
https://forum.xda-developers.com/p10-lite/development/service-rom-b362-c432-upgrade-o-o-n-o-t3813946 this method will lock your bootloader...
Ty so much, this solved my problem. phone is nearly new now.
Howdy,
I've used the Tab A for a couple of months now as literally a daily driver, since I modified it to fit into the multimedia slot in my car. It was rooted, had TWRP and even Viper4Android on it.
Long story short:
Since it's laggy I thought to test project Treble on it, since it's supported.
I wiped the tablet with TWRP and installed arm64 A/B (since it's Android 10) and it wouldn't boot anymore. It showed "Samsung Galaxy Tab A", shut off, vibrated and repeat. Also tried "Only A". Same result.
I thought to install it via fastboot. Since TWRP effectively replaced Fastbook afaik, I tried to flash the original "BL" downloaded form sammobile for this exact model. Flashed it, it succeeded and then...
It turns on with a blue screen that essentially says "This phone has been modified and is locked" with red letters on top stating "SECURE CHECK FAIL: recovery.img"
I can't get into download, it always jumps to this message. I tried all possible combinations, plugged the tablet into my pc while holding down buttons - nothing.
If I hold the pwr+down for circa 10-15 seconds while in this screen, it reboots and goes to a slightly different message stating: "SECURE CHECK FAIL: boot.img"
My PC doesn't recognize any USB devices, not even in the device manager.
What should I do? Any help would be greatly appreciated.
(I guess no music on the daily commute tomorrow lol)
Tried a Samsung JIG adapter. Still no success
Finally good news!
I tried it again with new combinations.
Turns out, if you hold all three buttons (pwr, down and up) eventually DOWNLOAD mode appears.
Worked here and am flashing stock now.
For rooting on latest bootloader (Rev:4, U4) which is the one you've installed already, you must purchase a subscription on this page and download that file for root:
https://support.halabtech.com/index.php?a=downloads&b=file&id=452768
As you described, it seem that you updated the bootloader and there's no way to get back at Rev:3 U3 bootloader, having the same trouble in rooting terms, I just hope a developer or an advance user that have a subscription in such page can help us and share the file that is on that page
Mafworld said:
For rooting on latest bootloader (Rev:4, U4) which is the one you've installed already, you must purchase a subscription on this page and download that file for root:
https://support.halabtech.com/index.php?a=downloads&b=file&id=452768
As you described, it seem that you updated the bootloader and there's no way to get back at Rev:3 U3 bootloader, having the same trouble in rooting terms, I just hope a developer or an advance user that have a subscription in such page can help us and share the file that is on that page
Click to expand...
Click to collapse
No it wont work i have tried it. It gets secure check fail boot.img
Basically what the title says, Back in September 12, 2021, at 4 AM I had woken up out of nowhere and I thought I'd wanted to give that engineering firmware of my lavender a try, but then I did something bad, after digging in what the issue was and why my phone wasn't booting and was stuck in the splash screen (fastboot wasn't working either), I found out that there was a firmware OEM security certificate mismatch between the UEFI Bootloader (XBL.ELF) and the "Application Bootloader" which in android's case is "Kernel Flinger" (abl.elf), the mismatch between the certificates causes the phone to not load abl.elf and it ends up getting stuck at the splash screen and does nothing.
TL;DR my phone's hard bricked and won't boot up, fastboot won't work either.
I tried to unbrick it through the "Emergency Download Mode", also known as EDL Mode, but to no avail, I keep getting the exact same error I did before the battery this phone originally came from had died.
The error is "TARGET SAID: ERROR: Only nop and sig tag can be received before authentication."
I believe I'm getting stuck at xiaomi's authentication thing but I've tried everything, flashing stock ROM, flashing engineering ROM, trying the patched firehose that was available since a long time, trying the patched firehose that was in xiaomiengs, nothing.
Before the battery had died though, if I remember correctly, when I hadn't connected the battery to the phone and turned in on in a long time, after replugging everything and turning it on, the phone would power on it's battery LED and after getting it in EDL, instead of getting an EDL Authentication error, I was getting some weird write error and it would stop, after resetting the phone back, I'd get the same write error, I'm going to retest the thing where it'd get a write error and get past the EDL auth, but I'll have to wait.
I hope you all can give me some tips on how I can unbrick it and hopefully salvage this phone, then I can have it next to my Poco X3 NFC which I got 1 month ago and 23 days ago.
Oh and also if you were wondering why I was trying to flash the engineering firmware again through EDL even though it supposedly hard bricked my phone, that's not the case at all, what actually hard bricked it was that I had flashed MIUI 10's abl.elf (Application Bootloader/Kernel Flinger) and after rebooting, it didn't boot.
I'll admit that it was very dumb of me to flash just one firmware image out of all of them, but I should mention that I did it out of being afraid over the fact that flashing the engineering firmware might've caused my device to be stuck with it until I flashed the stock/production firmware through EDL Mode, now, I know I could've flashed it through fastboot but there was another problem with fastboot and it was that it would not flash anything due to a "image size mismatch error".
What were my findings after all? Well, Lavender (AKA Redmi Note 7) seems to have encryption stuff built right into it's bootloader which was what forced me to factory reset the device (Wipe out the data partition or "userdata"), I forgot to test whether disabling encryption wouldn't cause the entire encryption to not work (It does the same in stock/production firmware).
Another thing I also found out was that the UEFI Bootloader of the engineering firmware build is that it seemed to not have OEM certificates setup properly so it allowed the booting of MIUI 12.5's Kernel Flinger binary (abl.elf), one thing that confuses me is the fact that it wouldn't boot MIUI 10's Kernel Flinger binary (abl.elf).
Okay, update here, I've been messing around, getting help from some people in Telegram and I've managed to get past EDL Auth, unfortunately for me, it says "Failed to open the SDCC Device slot 0 partition" when attempting to flash.
I tried through Qualcomm's Product Configuration Assistant Tool and I got that error, I tried through QFIL, same error, I tried through Mi Flash and various different versions, still same error.
Does anyone have any idea what the error could mean? I hope it doesn't mean that my phone's eMMC isn't dead, because from what I remember it isn't.