Tablet stuck on bootloader

[runandhide05]

here is step by step with files
first get and make sure your android sdk are installed and up to date
Android SDK | Android Developers
then download this launcher2.zip - File Shared from Box - Free Online File Storage
and unzip to platfom-tools
if you installed them to your c: do this
open start and type cmd
in command prompt type
cd C:\android-sdk\platform-tools
boot device up and let it get to the bootloop (should be showing the droid animaiotn)
then type
adb devices
if your deivce shows we are good from here
type
adb push C:\android-sdk\platform-tools\Launcher2.apk /sdcard
adb push C:\android-sdk\platform-tools\Launcher2.odex /sdcard
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mmcblk1p17 system
cp /sdcard/Launcher2.apk /system/app/
cp /sdcard/Launcher2.odex /system/app/
chmod 644 /system/app/Launcher2.apk

after that the tab should boot now, give it a few seconds and watch to see if the animation loops, if it does just reboot


that launcher2 apk and odex is from my 8.2, if everything pushed properly with no errors and still does not boot ask/look around for ones specific to the xoom2 althought they should be the same

[Ads]

[Arestas]

likesaya little higher,my tabletdo not want tostartnow!awhite LEDappearswhen charging.and the LEDblinksred3 timeswhile trying tostart

[runandhide05]

likesaya little higher,my tabletdo not want tostartnow!awhite LEDappearswhen charging.and the LEDblinksred3 timeswhile trying tostart

From power off, push and hold all three power volume up and down, do u get this option

Sent from my Galaxy Nexus using Tapatalk

[HussX]

If your tablet won't start, it's probably too dead. They won't boot before about 15%, so plug it in and let it sit a bit. Zwei stuenden spaeter.... Press and hold power and volume up for about 20 seconds and see where that gets you.


Sent from my XB10.1

[Arestas]

adb does not find my tablet, even if it is connected

edit:
leaving the rest whole day, the tablet is lit again!

@runandhide05: I managed togo tothe page by "From power off, push and hold all three power volume up and down"

[fish1552]

Perfect example everyone that we shouldn't overlook the obvious reason someone can't see something.

Very first post: "but it only turn off"

Suggest FIRST, leave it on the charger for at least 6 hours before trying again.

[ggrant3876]

It would surprise most members what a full charge and a soft reboot will fix.

[runandhide05]

It would surprise most members what a full charge and a soft reboot will fix.

Well he said he pulled or removed his launcher... so my steps was going off that...

Sent from my Galaxy Nexus using Tapatalk

[HussX]

I had the blank screen problem when i first got mine.


Sent from my XB10.1

[nchantmnt]

I managed to "softbrick" my xoom2 and recovered from it. maybe this will help others with simmilar problems.

what happened before:
I removed some bloatware and appended execution of overclock.sh to recovery-install.sh which is automatically loaded by init.rc on startup.
This setup has worked for me for several days without errors.
The other day i put some media on my device and downloaded some random stuff until i got an error that there was no space left on my device.
My tab got quite unresponsive so i wanted to reboot and then delete some unused stuff but the device went directly into bootloop.

What I tried:
restart the tab via key-combo -> still bootloop
let the battery drain, fully charge over night and try to boot -> still bootloop
connect to device via adb -> not found neither during bootloop nor during recovery screen (no menu availlable)

What helped:
entering fastboot and erasing user-data & cache