Database Users

A501 Tablet Stuck At Boot Screen with "Reboot the device!"

I have an Acer A501 which had Android 3.2.1 on it and recently decided to provide to my parents as a tv guide device so they could sit and research on it. They didn't need the 3G component.
I performed a factory reset and we were unable to use the Market/Play Store to load any of my parents apps. I returned home with the device so decided to try and upgrade to 4.0+
Upon doing lots of reading I started loading an ICS bootloader (a500_a501_bootloaders_apx_ics_v9) with the A500APX Flash.exe I found.
Since doing this my device sits at "Reboot the device!" in big red letters and the Acer logo has turned yellow. When I try a Power+LeftVolume reset it tries to read from SD card but fails. My Micro-SD is 64GB, whats the max size and is there anything special I need to do to try and ressurrect the device?
Can anyone help me with my problem?

When I boot with Power + Volume Up I get shown the following:
Erasing Cache before SD update...
SD update cmd:recovery
--update_package=SDCARD:update.zip

Same issue
dkingsho said:
I have an Acer A501 which had Android 3.2.1 on it and recently decided to provide to my parents as a tv guide device so they could sit and research on it. They didn't need the 3G component.
I performed a factory reset and we were unable to use the Market/Play Store to load any of my parents apps. I returned home with the device so decided to try and upgrade to 4.0+
Upon doing lots of reading I started loading an ICS bootloader (a500_a501_bootloaders_apx_ics_v9) with the A500APX Flash.exe I found.
Since doing this my device sits at "Reboot the device!" in big red letters and the Acer logo has turned yellow. When I try a Power+LeftVolume reset it tries to read from SD card but fails. My Micro-SD is 64GB, whats the max size and is there anything special I need to do to try and ressurrect the device?
Can anyone help me with my problem?
Click to expand...
Click to collapse
Hi
I got a friends A501 tablet and he asked me to upgrade the os. so I flashed the bootloader with the same bootloader as you and got stuck with the same problem. Yellow Acer and reboot the tablet in red. Did you ever find a solution?

Hi! I have exactly the same issue! did any one knows what the steps to fixe it? I tried to follow the unbrick solutions and nothins because I don't even get connection to the computer. The only way to listen the USB connection is with a paper clip press reset and power for 3 seconds (or more) and I will ear the sound of a USB device being connected to the computer, but then I try to write adb usb or adb shell and nothing... and with AfterOTA tool appears in the USB section: ERROR - connect usb cable and enable usb debugging (in dhe Driver section is OK).

Probable brickage of TN7

Hi folks,
So, after little usage due to instability caused by the Lollipop upgrade I hadn't used the TN7 in a while. Yesterday I thought I'd have a go at reconditioning it.
Background: The bootloader has been unlocked, recovery was TWRP, I'd flashed and reflashed stock ROMs of KitKat and Lollipop several times previously. The main problem in Lollipop was that whilst the SD card files were showing up fine in FS Explorer, I couldn't see any of my files or folders when looking at local storage. Also, Google Play Services refused to update (or install using an APK).
Yesterday I grabbed the factory ROM from the nVidia site to do a full factory install and reset. I followed the instructions, flashing the recovery, boot, system, userdata, staging blob and dtb in that order. I then rebooted and...nothing. No power (or so it appears), no boot screen, no ability to get back into the bootloader, nada, zilch. When I read back through the flash commands I noticed that the final part of flashing the system image failed, which could well be the cause - I should have paid more attention.
I've searched all over and tried multiple options to get the TN7 to boot or show some signs of life. I don't even get an LED showing when plugged into a wall socket to charge.
The device doesn't show in fastboot or adb on the Mac. I did however get a small sign of life from Windows. If I hold down the power button for around 10 secs and let go, I can hear the Windows chime of a device connecting, immediately followed by a disconnect sound, the Device Manager updates but shows nothing new.
So my question is: have I completely screwed the pooch, or is there something that can be done to resurrect it?
Cheers for reading,
Gray

Evil Penguin said:
Hi folks,
So, after little usage due to instability caused by the Lollipop upgrade I hadn't used the TN7 in a while. Yesterday I thought I'd have a go at reconditioning it.
Background: The bootloader has been unlocked, recovery was TWRP, I'd flashed and reflashed stock ROMs of KitKat and Lollipop several times previously. The main problem in Lollipop was that whilst the SD card files were showing up fine in FS Explorer, I couldn't see any of my files or folders when looking at local storage. Also, Google Play Services refused to update (or install using an APK).
Yesterday I grabbed the factory ROM from the nVidia site to do a full factory install and reset. I followed the instructions, flashing the recovery, boot, system, userdata, staging blob and dtb in that order. I then rebooted and...nothing. No power (or so it appears), no boot screen, no ability to get back into the bootloader, nada, zilch. When I read back through the flash commands I noticed that the final part of flashing the system image failed, which could well be the cause - I should have paid more attention.
I've searched all over and tried multiple options to get the TN7 to boot or show some signs of life. I don't even get an LED showing when plugged into a wall socket to charge.
The device doesn't show in fastboot or adb on the Mac. I did however get a small sign of life from Windows. If I hold down the power button for around 10 secs and let go, I can hear the Windows chime of a device connecting, immediately followed by a disconnect sound, the Device Manager updates but shows nothing new.
So my question is: have I completely screwed the pooch, or is there something that can be done to resurrect it?
Cheers for reading,
Gray
Click to expand...
Click to collapse
Hi,
It can be fixed via apx mode.
Download drivers and switch to apx mode.
Follow instructions http://mobileviandroid.blogspot.in/2015/07/nvidia-tegra-note-7-apx-images.html?m=1
Remember to change your device serial number as mentioned in instructions.
I also faced the same problem as you are facing now. It fixed. If you need any help further just post. God bless. Hope it helps

DJDON1302 said:
Hi,
It can be fixed via apx mode.
Download drivers and switch to apx mode.
Follow instructions http://mobileviandroid.blogspot.in/2015/07/nvidia-tegra-note-7-apx-images.html?m=1
Remember to change your device serial number as mentioned in instructions.
I also faced the same problem as you are facing now. It fixed. If you need any help further just post. God bless. Hope it helps
Click to expand...
Click to collapse
Lol that site ripped my Tutorial! how nice of them, You should of linked the person to https://forum.xda-developers.com/nvidia-tegra-note-7/general/nvidia-tegra-note-7-apx-images-t3149839

Deleted Os in TWRP

Im an Idiot. I went to twrp recovery and wiped everything, since I wanted to install a higher version of the Samsung tab e, and even when twrp told me that there was no OS installed, I rebooted anyways. I was new to this all thing, and had no idea what exactly that meant and thought, 'What could go wrong?' . . . I just wanted a higher device model, man.
Ugh. Now im stuck in the 'Powered by Android' logo screen, and cant boot into recovery or Download mode.
- What's even worse was that I didn't even enable USB Debugging so Adb is out.
- However, it is Rooted, if that even helps.
- Trying to use the Samsung 300k tool to force enter download mode ends up with 'Write file function failed (error 995)'
- My sibling has the same device model as me, but using T Flash via Odin and my 32GB micro SD card doesn't have a reaction to my device. (Or maybe im doing it wrong, since I don't see anything in the sd card when I plug it to the computer)
- Tablet gets recognized via Odin and Computer, but only as 'MTP USB Device', and in Devices, it is in Unspecified as 'Samsung Android'
- Only good thing that came out of this was the info that I had obtained over the past few days that has shocked my siblings as to why I have this much knowledge over Samsung devices and its functions (AKA I feel cool)
But honestly, at this point I am at a loss of what to do, and will not be surprised if I have to get a USB jig to force it to download mode (my only other option left), or take it to a service center to get it fixed. (the other option I have)
But if there is something you guys are aware of, that I had not tried yet, Please guide me.

Anybody?

norakana said:
Anybody?
Click to expand...
Click to collapse
The simplest way to get an operating system again is to put the ZIP file on a working MicroSD card and put it in your tablet, Then boot into the boot loader and choose to install the file by choosing the external micro sd card.
If you're stuck on a boot screen or download, get out of it by holding the power key + volume down, until the tablet resets.
Note for the future:
always backup your device to an external MicroSD card before deleting your existing operating system, or installing a new one.

[Urgent help] Xiaomi Mi A1 Unlock bootloader

Hi All,
I'm new to this as I'm not an Android developer but a good Android user. Requesting moderator to update anything required.
I've Xiaomi mi A1 and it was working for the last 3 years. Last Sunday, it just got hanged while kids were playing with it(maybe multiple apps/videos/some ad clicked) and it got hanged.
I restarted and it stuck on "Android One" screen till now even after multiple attempts.
What I tried:
1. I tried to wipe/factory reset from the Android recovery option(power off + volume up) then it stuck there saying "Formatting data" and I've restarted it to come back to Android One screen after hours.
2. I tried using MiFlash tool and it continues throwing the error "remote device is locked. cannot erase".
Then I got to know bootloader must be unlocked. and for that:
1. I tried fast boot oem unlock but it just says OK and device reboots. When I check status back, it's again locked .
2.I tried to unlock it using MiFlashUnlock tool but it says not able to find account details as I may have logged in once but probably I may not have used Xiaomi as cloud instead I prefer Google cloud.
You can assume I'v already searched possibly all threads on the internet and added here all possible information.
Attached getvar-all.txt output

Is there anyone on the platform who knows on this issue?
Or it's just a platform of Ads?

oooooof, sounds like a harsh brick from some sort of malware downloaded into the device or your kids diddled with some kernel settings somehow
is your device running on qualcomm snapdragon? i have the fix for it in this site
but first try the update option on the recovery, might fix something

arshad4u said:
Hi All,
I'm new to this as I'm not an Android developer but a good Android user. Requesting moderator to update anything required.
I've Xiaomi mi A1 and it was working for the last 3 years. Last Sunday, it just got hanged while kids were playing with it(maybe multiple apps/videos/some ad clicked) and it got hanged.
I restarted and it stuck on "Android One" screen till now even after multiple attempts.
What I tried:
1. I tried to wipe/factory reset from the Android recovery option(power off + volume up) then it stuck there saying "Formatting data" and I've restarted it to come back to Android One screen after hours.
2. I tried using MiFlash tool and it continues throwing the error "remote device is locked. cannot erase".
Then I got to know bootloader must be unlocked. and for that:
1. I tried fast boot oem unlock but it just says OK and device reboots. When I check status back, it's again locked .
2.I tried to unlock it using MiFlashUnlock tool but it says not able to find account details as I may have logged in once but probably I may not have used Xiaomi as cloud instead I prefer Google cloud.
You can assume I'v already searched possibly all threads on the internet and added here all possible information.
Attached getvar-all.txt output
Click to expand...
Click to collapse
found some fix on a russian website, gonna translate it:
im gonna make a warning there off-script of the russian website, this is NOT guaranteed to work. if it doesnt, send it off for repairs.
what do you need to do this:
1 - fully charge the phone
2 - a working usb cable
3 - a computer with wifi on it (i can tell you have it since you likely posted it on the computer)
4 -you should have Mi flash pro
5 - a recovery image on chinese (WARNING: 1.9 GB, BE PATIENT)
6 - actually working braincells and hands ( you guaranteedly have em)
THE STEPS:
1 - Load in mi flash pro and register in it under your name (not always under your name)
2 - press recovery
3 - you should see a lightning bolt icon along with the IMEI of your device
4 - type in the path of the firmware
even if your device shows your system has been destroyed you can still boot into recovery.
5 - in your device boot into recovery
6 - you see connect with mi assistant? choose that option and confirm it
your device should direct you to connect the usb from your computer to your device
7 - After you setup everything you should see your device, if not, press refresh device, then you should see the flash button, press it
8 - and there begins the magic - wait 5-10 mins for the firmware to initialise, DO NOT DISCONNECT THE USB FROM YOUR DEVICE AT THIS POINT, IF YOU DO, YOU WILL SCREW IT UP AND HAVE TO DO IT ALL OVER AGAIN!
if you dont screw up and your device actually boots congratualtions! the power of xi jing ping has restored your phone to normal with a small drawback - its all in chinese
worry not, it doesnt end here:
9 - Unlock the bootloader AKA Unlock OEM (This is important, because otherwise you will brick yourself again and will have to do it all over again)
10 - boot your device into fast boot and flash the global firmware onto your device (the global firmware can be found on the same xiaomiui website you got the chinese firmware from)
i hope this lengthy guide helps

arshad4u said:
Hi All,
I'm new to this as I'm not an Android developer but a good Android user. Requesting moderator to update anything required.
I've Xiaomi mi A1 and it was working for the last 3 years. Last Sunday, it just got hanged while kids were playing with it(maybe multiple apps/videos/some ad clicked) and it got hanged.
I restarted and it stuck on "Android One" screen till now even after multiple attempts.
What I tried:
1. I tried to wipe/factory reset from the Android recovery option(power off + volume up) then it stuck there saying "Formatting data" and I've restarted it to come back to Android One screen after hours.
2. I tried using MiFlash tool and it continues throwing the error "remote device is locked. cannot erase".
Then I got to know bootloader must be unlocked. and for that:
1. I tried fast boot oem unlock but it just says OK and device reboots. When I check status back, it's again locked .
2.I tried to unlock it using MiFlashUnlock tool but it says not able to find account details as I may have logged in once but probably I may not have used Xiaomi as cloud instead I prefer Google cloud.
You can assume I'v already searched possibly all threads on the internet and added here all possible information.
Attached getvar-all.txt output
Click to expand...
Click to collapse
crud, i forgot the critical part:
it doesnt boot you to the average xiaomi screen, its the A1 model
at this point you need to use the ADB to flash the chinese firmware and unlock the bootloader on the chinese firmware, then flash the global one
though you can still use the same method i typed above

How's the progress so far?

Lamntox said:
oooooof, sounds like a harsh brick from some sort of malware downloaded into the device or your kids diddled with some kernel settings somehow
is your device running on qualcomm snapdragon? i have the fix for it in this site
but first try the update option on the recovery, might fix something
Click to expand...
Click to collapse
I tried recovery also try to format the disc with recovery mode(power on + Volume up ) but then it stuck on the formatting disc... line

arshad4u said:
I tried recovery also try to format the disc with recovery mode(power on + Volume up ) but then it stuck on the formatting disc... line
Click to expand...
Click to collapse
Yup, the device is probs bricked
Have you tried the other methods i described?

arshad4u said:
Hi All,
I'm new to this as I'm not an Android developer but a good Android user. Requesting moderator to update anything required.
I've Xiaomi mi A1 and it was working for the last 3 years. Last Sunday, it just got hanged while kids were playing with it(maybe multiple apps/videos/some ad clicked) and it got hanged.
I restarted and it stuck on "Android One" screen till now even after multiple attempts.
What I tried:
1. I tried to wipe/factory reset from the Android recovery option(power off + volume up) then it stuck there saying "Formatting data" and I've restarted it to come back to Android One screen after hours.
2. I tried using MiFlash tool and it continues throwing the error "remote device is locked. cannot erase".
Then I got to know bootloader must be unlocked. and for that:
1. I tried fast boot oem unlock but it just says OK and device reboots. When I check status back, it's again locked .
2.I tried to unlock it using MiFlashUnlock tool but it says not able to find account details as I may have logged in once but probably I may not have used Xiaomi as cloud instead I prefer Google cloud.
You can assume I'v already searched possibly all threads on the internet and added here all possible information.
Attached getvar-all.txt output
Click to expand...
Click to collapse
Hi i dont have that kind of a problem!
my problem is when i try to do oem unlock it says error 0x1002 and idk what to do (i have same phone btw) i tried anything but nothing works!

"SECURE CHECK FAIL" on T295

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