[Q] Stuck on boot logo after flashing 4.2.2 Team Eos - Xoom Q&A, Help & Troubleshooting

Hello,
I am trying to upgrade my xoom. Its MZ601 3G EU. I have rooted it and flashed TeamWin TWRP v2.5.0.0 and it works ok .
I have tried to flash 4.2.2 JDQ39 AOSP] Eos 4.0 -- Umts_Everest and CM 10.1- 20130511 Nightly build Everest.
The problem is once its flashed and prompts to restart it hangs on the boot logo but I'm not sure what I have done wrong..
Thanks

I recommend you to flash your ROM again, just a few things to remember:
1 - Remember to factory reset if you're coming from another ROM (in your case DO a factory reset)
2 - Flash GAPPS right after flashing the ROM, it's important due to many libs located there
3 - Don't flash anything "weird" to the ROM at first, wait it boot then you can flash any mod or such
Good luck
~Lord
"This Story Ends Where It Began" - Octavarium (Dream Theater)

Thanks Lord,
Worked a treat, did as you said working perfect.

My Xoom went in bootloop after flashing atualization
Hey guys I have the same problem. However both my MAC and PC can't recognize the xoom. I am also trying to do factory reset but it is not working, going stucked in motorola logo as well. My Xoom is model MZ601 brazil. I am using TWRP v2.2.1. I need my tablet again, please if someone can helpe me? I already download motorola driver and andorid file transfer (in case of mac), typed ./adb device and couldnt see nothing. How could I do factory reset or flash new room, etc, without computer? To finalize I coudn't mount the sd card.

hbtwender said:
Hey guys I have the same problem. However both my MAC and PC can't recognize the xoom. I am also trying to do factory reset but it is not working, going stucked in motorola logo as well. My Xoom is model MZ601 brazil. I am using TWRP v2.2.1. I need my tablet again, please if someone can helpe me? I already download motorola driver and andorid file transfer (in case of mac), typed ./adb device and couldnt see nothing. How could I do factory reset or flash new room, etc, without computer? To finalize I coudn't mount the sd card.
Click to expand...
Click to collapse
Hi,
Can you boot in recovery? Try plugging your Xoom to your PC/MAC while the recovery is open. Also, you have to type "./adb devices" not device . You can factory reset from recovery! Try selecting to wipe data, if sdcard can't mount you can try formatting it too.
All the best,
~Lord
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD

XxLordxX said:
Hi,
Can you boot in recovery? Try plugging your Xoom to your PC/MAC while the recovery is open. Also, you have to type "./adb devices" not device . You can factory reset from recovery! Try selecting to wipe data, if sdcard can't mount you can try formatting it too.
All the best,
~Lord
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Yes,I can boot in recovery. Did all possible combinations wipe Cache/Dalvick Cash/Factory Reset and System but didn't work, when rebooting stayed the same ;(. When I formatted the External SD the TWRP could see it. Now I will try to install things by External SD and post what happened. Thanks for answering. It helped a lot. Now there is light in the end of the tunnel. I think the problem with sd card was win8, every time a use it the pendrive or card corromps!!!

Solved for me!!!!
Hey Lord, thank you for your support. I discovered that my first sdcard was broken. When I´ve tried a new one with ZIP files inside it works perfectcly and I could return to my old room doing flah in the recovery mode of TWRP2.2.
It is important to note that my Xoom did not find .IMG files inside the card but only ZIP ones. Any way it worked perfectly and I hope this solution will serve to other in solving his/her problems.
Many thanks

hbtwender said:
Hey Lord, thank you for your support. I discovered that my first sdcard was broken. When I´ve tried a new one with ZIP files inside it works perfectcly and I could return to my old room doing flah in the recovery mode of TWRP2.2.
It is important to note that my Xoom did not find .IMG files inside the card but only ZIP ones. Any way it worked perfectly and I hope this solution will serve to other in solving his/her problems.
Many thanks
Click to expand...
Click to collapse
Hi,
Glad to know it worked with you . The .img files are only recognized/used with fastboot the only way you can flash them in recovery is using a dd command, but that's a talk we can save for later, as I almost never use it except in some more extreme cases.
Nice work again .
~Lord
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Monster S4

Help needed
My xoom recently got stuck in a bootloop and i tried to reflash the rom. No luck, The bootloop is still there. i can get into recovery and rsd along with fastboot. i just don't know what to do. ideally i would get it back to stock.

uttt7 said:
My xoom recently got stuck in a bootloop and i tried to reflash the rom. No luck, The bootloop is still there. i can get into recovery and rsd along with fastboot. i just don't know what to do. ideally i would get it back to stock.
Click to expand...
Click to collapse
Hi,
Did you try factory resetting your device and wiping the system? Also try another zip, the problem may be a bad zip too...
Hope this helps,
~Lord
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Monster S4

Related

[Q] My Nexus S won't boot at all... Help, please

Hi
I'm facing a problem with my Nexus S, before it was working... but, unfourtunatlly i just make some modification in the system file and now my phone not working and stuck at the google logo black screen... exactly, i think the problem in the java runtime.jar file that was in the system folder, i replace it with another file and all that done since i want to add another language to the system so that it can understand it. but, the device now is not working....
I tried to enter the recovery mode and wipe all data, but nothing change. its keep the same. so i tried also to format the system (from the recovery) since, the modification done in that folder... also, its not working....
So, I think the best way right now is to return it to the default rom(official one from google) , i download it, and tried to flash it using the "fastboot" command but it keep give me error when writing for system.img file....
What can I do right know ??? I can't use my device at all...
Help me Guys, please.....
For future reference Factory wipe doesn't touch /system...just /data.
If you formatted your /system, and it actually formatted, all you can do now is restore a working system.
If you didn't make your own nandroid backup of the system (and you ALWAYS should in the future before messing with system level modifications) to have a known working configuration, then your best bet in my opinion is to go to this thread: http://forum.xda-developers.com/showthread.php?t=884093
Download the nandroid image from there and flash it to your phone using Clockwork Recovery.
Good luck.
distortedloop said:
For future reference Factory wipe doesn't touch /system...just /data.
If you formatted your /system, and it actually formatted, all you can do now is restore a working system.
If you didn't make your own nandroid backup of the system (and you ALWAYS should in the future before messing with system level modifications) to have a known working configuration, then your best bet in my opinion is to go to this thread: http://forum.xda-developers.com/showthread.php?t=884093
Download the nandroid image from there and flash it to your phone using Clockwork Recovery.
Good luck.
Click to expand...
Click to collapse
But, The question here is.... how can i flash it when i can't get access to the memory(since the Nexus S doesn't have sd memory slot) and to the system ??
when i enter the recovery, all i can do is use the fastboot command.... can i use it here ??
Thanks alot .....
If you boot into Clockwork, you should be able to use it's mounts menu to mount the sdcard...then use adb to push the files to your sdcard. adb should be active and working in clockwork.
If that doesn't work out for you, you could also try the Odin and "download mode" approach from this thread: http://forum.xda-developers.com/showthread.php?t=947950
distortedloop said:
If you boot into Clockwork, you should be able to use it's mounts menu to mount the sdcard...then use adb to push the files to your sdcard. adb should be active and working in clockwork.
If that doesn't work out for you, you could also try the Odin and "download mode" approach from this thread: http://forum.xda-developers.com/showthread.php?t=947950
Click to expand...
Click to collapse
Thank you sooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo much distortedloop....
as what u said.... the mount already available in the clockwork.. but i didn't see it before.....
Now i got my Nexus S back to me again.....
Thank u soooooooooooooo much Man... I appreciate it
abd640 said:
Thank you sooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo much distortedloop....
as what u said.... the mount already available in the clockwork.. but i didn't see it before.....
Now i got my Nexus S back to me again.....
Thank u soooooooooooooo much Man... I appreciate it
Click to expand...
Click to collapse
Glad you're up and running again.
Hello guys
I have the same problem, but i guess for different reasons.
I applyed the superboot from the modaco´s forum on my nexus s, but I guess I did it with the wrong version (i had got the 2.3.4 ota before doing so and used a 2.3.3 version) and now my phone won´t boot. My rom was stock. Now, it remains on that google initial screen. I can´t get to upload anything for the device since I guess the usb debug mode is off, although when I connect the device to the computer, the system shows the usb driver. I guess my device is GT90 something, can´t say for sure. Have to check at the box.
That said, I´d like some help on what to do about it.
I´ll be forever grateful!
ectole said:
Hello guys
I have the same problem, but i guess for different reasons.
I applyed the superboot from the modaco´s forum on my nexus s, but I guess I did it with the wrong version (i had got the 2.3.4 ota before doing so and used a 2.3.3 version) and now my phone won´t boot. My rom was stock. Now, it remains on that google initial screen. I can´t get to upload anything for the device since I guess the usb debug mode is off, although when I connect the device to the computer, the system shows the usb driver. I guess my device is GT90 something, can´t say for sure. Have to check at the box.
That said, I´d like some help on what to do about it.
I´ll be forever grateful!
Click to expand...
Click to collapse
try to boot into bootloader. root the phone n install a recovery.img, then reinstall a custom rom or the stock rom.
deeren said:
try to boot into bootloader. root the phone n install a recovery.img, then reinstall a custom rom or the stock rom.
Click to expand...
Click to collapse
The thing is that i already have clockworkmode installed and i can access it through bootload, in fact is the only thing i can do. My problem is that i just can´t send the recovery.img from the pc to the phone. And I also think that the usb debug mode is unavailabe, so I can´t activate it.
I´m new to this thing so the only way I could move files into the phone was through windows explorer drag and drop. Honestly I´m lost without it.
Is there a different way to push it to the phone ?
I understand this forum is intended to more experienced users, and for that I apologise.
Guys I found a solution by enabling USB from clockwork! Thanks! Keep the good work!
Sent from my Nexus S using XDA Premium App
Hello "ectole", could you let me know how you get out of it. I am in the same problem. I followed this guide http://forum.xda-developers.com/showthread.php?p=13800735#post13800735 to root my phone, now I always boot into clockwork. I can I boot into Nexux again?
Hi guys,
I'm in a similar situation. I tried to install CyanogenMod 7 to my Nexus S (ATT), got stuck at the skating dude.
Booted back into Clockwork, and tried to flash back to the stock firmware, but I think I accidentally flashed the wrong one (for the 9020T instead of 9020A) build. Now I can't get into ClockworkMod or anything on the screen whatsoever.
Does anyone have any tips at all? I'm really screwed here, would appreciate it a lot...
J
Hey bante just go to clockwork then to mount/dismount menu and the last option should be mount USB storage. Mount it and stay there and your PC should see the sd card. Then upload what you want.
Sent from my Nexus S using XDA Premium App
HELP!!! Odin bricked my Nexus S i9020a
I attempted to use odin to restore my phone. Could not get past bootloading screen. Put phone in recovery mode and used odin and grh78 firmware.
Odin went thru the whole process and said success, then my phone shut off, and will not power back on. Any ideas?
OkNewMedia said:
I attempted to use odin to restore my phone. Could not get past bootloading screen. Put phone in recovery mode and used odin and grh78 firmware.
Odin went thru the whole process and said success, then my phone shut off, and will not power back on. Any ideas?
Click to expand...
Click to collapse
Which phone version you got?
Sent from my Nexus S using XDA App
OkNewMedia said:
I attempted to use odin to restore my phone. Could not get past bootloading screen. Put phone in recovery mode and used odin and grh78 firmware.
Odin went thru the whole process and said success, then my phone shut off, and will not power back on. Any ideas?
Click to expand...
Click to collapse
By 'recovery mode', do you mean download mode? (you hold both vol up and vol down then plug in USB)
My Nexus s not boot at all
Hi
I'm facing a problem with my Nexus S, before it was working... but, unfourtunatlly i just make some modification in the system file and now my phone not working and stuck at the google logo black screen...
it doesn't entering the recovery mode. it only stucks at the google black logo screen
What can I do right know ??? I can't use my device at all...
Help me Guys, please.....
shavinder said:
Hi
I'm facing a problem with my Nexus S, before it was working... but, unfourtunatlly i just make some modification in the system file and now my phone not working and stuck at the google logo black screen...
it doesn't entering the recovery mode. it only stucks at the google black logo screen
What can I do right know ??? I can't use my device at all...
Help me Guys, please.....
Click to expand...
Click to collapse
flash either clockwork or twrp recovery via fastboot.
but how can i do this thing
jstennis1591 said:
Hi guys,
I'm in a similar situation. I tried to install CyanogenMod 7 to my Nexus S (ATT), got stuck at the skating dude.
Booted back into Clockwork, and tried to flash back to the stock firmware, but I think I accidentally flashed the wrong one (for the 9020T instead of 9020A) build. Now I can't get into ClockworkMod or anything on the screen whatsoever.
Does anyone have any tips at all? I'm really screwed here, would appreciate it a lot...
J
Click to expand...
Click to collapse
Sounds like you flashed i9023 software. You could try Odin. Does your computer recognize the phone?
Sent from my Nexus S 4G using xda premium

[Q] Trouble whilst trying to sell device!

Hi all,
I have recently sold my g tab on ebay.
I tried to clear my own personal data of the tablet. I am running vegan ginger edition and went to privacy and then clicked on reset (including delete data off sd card). Bloody stupid thing to do I now realise.
When the tablet rebooted, it got stuck in a boot loot on the vegan tab screen. I obv cant restore a nandroid backup or reinstall the rom because I deleted.
Any ideas on how i might be able to fix this would be really appreciated.
Many thanks in advance.
Harry
gifton1 said:
Hi all,
I have recently sold my g tab on ebay.
I tried to clear my own personal data of the tablet. I am running vegan ginger edition and went to privacy and then clicked on reset (including delete data off sd card). Bloody stupid thing to do I now realise.
When the tablet rebooted, it got stuck in a boot loot on the vegan tab screen. I obv cant restore a nandroid backup or reinstall the rom because I deleted.
Any ideas on how i might be able to fix this would be really appreciated.
Many thanks in advance.
Harry
Click to expand...
Click to collapse
Easy, use "nvflash recovery kit" to recovery your table via USB cable, go back into the recovery mode, have the then cwmod_internal installed if you not already done so with the nvflash, use Calkulin's_FORMAT_ALL.zip to format your gtab and then go back into recovery mode and mount it as usb and transfer the ROM that you want and then flash it ....
search in the DEV section to have more details
y2k-inc said:
Easy, use "nvflash recovery kit" to recovery your table via USB cable, go back into the recovery mode, have the then cwmod_internal installed if you not already done so with the nvflash, use Calkulin's_FORMAT_ALL.zip to format your gtab and then go back into recovery mode and mount it as usb and transfer the ROM that you want and then flash it ....
search in the DEV section to have more details
Click to expand...
Click to collapse
Thankyou so much for your reply, I will try that now
I ran the nv flash and that all went fine. however, when the tablet rebooted, it is now just doing a boot loop between the gtablet logo and the viewsonic birds, continuously. I think i need to repartition the sd card? any ideas if this and how i might go about doing that?
Thank you
Problem solved - loaded CWM using the following instructions http://guide-to-installing-clockworkmod.com/ then i was able to repartition SD card. Then performed another NV flash and good to go!
thanks y2k-inc
gifton1 said:
Problem solved - loaded CWM using the following instructions http://guide-to-installing-clockworkmod.com/ then i was able to repartition SD card. Then performed another NV flash and good to go!
thanks y2k-inc
Click to expand...
Click to collapse
NP, this way you will be sure, that your personal information is wiped out
Use NVFlash to start over from scratch would probably be the best bet.

[HELP] MY TF101 won't wake up (no matter which ROM)

Hi, I've been experiencing this problem for a while now. Once the screen comes off, the tablet will never wake up. I've clean flashed, with/without gapps, and even right after flashing (EOS, CM, RaymanFX's & Gierdo's, ARHD...) once I turn the screen off (with either the lockpad button in the keyboard, the button on the screen, or after a display timeout) it will never light up again.
I also have trouble switching off the tablet, i.e. I hit shut down and it will never do (I had to go into recovery by power vol-) and hit shut down from there.
Buttons work, so I am thinking it might be firmware problem? Since all roms and different recoveries dont make a difference... I am currently downloading the latest ASUS official firmware from their website, but it'll take some hours since my internet connection here is rubbish.
thanks for any advice and help!
When you flash the different ROMs, are you wiping all the following:
Cache
Davlik Cache
System
Factory Reset (from recovery)
If you are skipping any of these, it can cause issues. The most important one is the Factory Reset to erase the system settings and can cause huge issues when jumping from one ROM to another ROM.
Yes thanks, of course I am. Full wipes between flashes, cache and dalvik, when changing kernel, etc.
TWRP recovery doesn't install (nor with EasyFlash or GooManager) I currently have CM recovery flashable with EasyFlash. Twrp stalls on a splashscreen and nothing else...
TheKaser said:
Yes thanks, of course I am. Full wipes between flashes, cache and dalvik, when changing kernel, etc.
TWRP recovery doesn't install (nor with EasyFlash or GooManager) I currently have CM recovery flashable with EasyFlash. Twrp stalls on a splashscreen and nothing else...
Click to expand...
Click to collapse
If you can boot and want to try TWRP, here is another way to install it so long as you are rooted:
Download the 2.3.2.3 blob from HERE
Place the recovery blob in the /sdcard/ directory. We are going to pretend the downloaded file is called TWRP.blob
Open a terminal window and enter these commands
Code:
su
cd /sdcard/
ls
dd if=TWRP.blob of=/dev/block/mmcblk0p4
reboot
the ls will tell you if the blob is indead where it is supposed to be, if it can be seen, you should be good to go on to the dd command, if you don't see the file, do not procede.
Make sure to change TWRP.blob to the actual name and location of the file you downloaded
Let me know how it goes
thanks for your help, it still didn't work. It stays stuck in the recovery splash screen and it won't even boot into the rom. I have to fix it using EasyFlasher.
I am thinking that all my problems are due to a corrupt firmware or something like that. The tablet never reboots by software or shuts down, with no matter which ROM.
I will perform an internal storage backup and use EasyFlasher to install the official Asus firmware. Hopefully that will make the trick.
TheKaser said:
thanks for your help, it still didn't work. It stays stuck in the recovery splash screen and it won't even boot into the rom. I have to fix it using EasyFlasher.
I am thinking that all my problems are due to a corrupt firmware or something like that. The tablet never reboots by software or shuts down, with no matter which ROM.
I will perform an internal storage backup and use EasyFlasher to install the official Asus firmware. Hopefully that will make the trick.
Click to expand...
Click to collapse
I found a little mixup with my code, it should be just a REBOOT command at the end and not a REBOOT RECOVERY.
If you do the reboot recovery, it does not complete the flash of the firmware on boot.
Give that a shot and see if it works if you want.
frederuco said:
I found a little mixup with my code, it should be just a REBOOT command at the end and not a REBOOT RECOVERY.
If you do the reboot recovery, it does not complete the flash of the firmware on boot.
Give that a shot and see if it works if you want.
Click to expand...
Click to collapse
Nothing worked. I indeed followed the insturctions you gave me but reading them in the TWRP site so I did it correctly. Still didn't work. I flashed using EasyFlasher the official ASUS firmware, and the tablet still behaves in the same way: Will never shutdown or reboot by software command, will not wake up when screen is switched off... this is frustrating, but it needs to be software, right? It can't be hardware, since the power button does work...
I dont know what else to do... I wiped my tablet clean and flashed the official firmware and the issue is still present...
the thing is that the tablet is working (PC reacts to usb) and it makes noises when I plug the keyboard dock... but the power button will just not turn the screen on...
Hi, a little bump just to see if someone could help me out. I flashed the latest Team EOS nightly 4.2.2, and it runs like a charm, but as soon as I turn off the screen, it wont come back. I need to do a reboot by holding the power button to be able to use it again. Could it be hardware?
It happens likewise with all roms...
Sent from my Transformer TF101 using Tapatalk 4 Beta
TheKaser said:
Hi, a little bump just to see if someone could help me out. I flashed the latest Team EOS nightly 4.2.2, and it runs like a charm, but as soon as I turn off the screen, it wont come back. I need to do a reboot by holding the power button to be able to use it again. Could it be hardware?
It happens likewise with all roms...
Sent from my Transformer TF101 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Go to the android development tab of this forum and use the katkernel. Works with EOS roms. I still had a screen freeze but better than the stock kernel. This may help you. Follow the flashing instructions.
Sent from my SGH-T999 using Tapatalk 2
Thanks Tom, I have already tried katkernel in the past, with the same result.
the tablet cant power off either, it stays with the powering down box for ever. I need to hard reboot it into the recovery and power it down from there...
It's all very strange, it happens like that with every rom i've tried, from 4.0 to 4.2.2, and every kernel.
Sent from my Transformer TF101 using Tapatalk 4 Beta
I have followed all the threads I have seen, flashed from roaches Prime 3.0 rom, to EOS 4.2.2, stock Asus/unbrick with easyflash, and using tubuntu installer.
I always find the same issue, cant reboot (it stays stuck), cant tunr screen on after turning it off, and TWRP recovery doesn't work (only the two others provided by easy flasher).
Might it be there is something partially bricked?
I once bricked my USB in my old nexus. I am desperate, the tablet works fine when turned on but can't reboot, power down, or turn the screen back on... it has to be some kind of bricking...
ps: from here: http://forum.xda-developers.com/showthread.php?p=42046184#post42046184
TomTcom said:
It's probable my commands aren't correct. Hopefully you can see from the idea of how I started the commands and try to figure it out with some google searches. I don't know for sure if that config file is in the correct format for nvflash either. I used it from the Tubuntu application but the Tubuntu application doesn't have a "format all" and recreate everything option.
I believe your partitions are either not set correctly or the partition table is corrupt or non-existent.
I don't think you have faulty hardware at this point because you can execute wheelie and nvflash without problems so as long as you can do that you still have a fighting chance to recover the tablet.
I searched a lot on these commands but you'll need to do some more. I don't know yet what else I can provide. Good luck!
Click to expand...
Click to collapse
I can corroborate that your commands work.
TomTcom said:
Type this and hit enter: wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
Type this and hit enter: nvflash -r --format_partition 2 --bl bootloader.bin (If successful you will know it will say this: Formatting partition 2 please wait.. done!)
Type this and hit enter: nvflash -r --go
Let me know what happens.
Click to expand...
Click to collapse
Is there a way that some part of the hardware is bricked?
That's always possible it's bricked but I wouldn't give up. Dig deep into wheelie and nvflash and how they work. I'm sure you can get it running right again.
Wish I knew more, sorry!
Sent from my SGH-T999 using Tapatalk 2
TomTcom said:
That's always possible it's bricked but I wouldn't give up. Dig deep into wheelie and nvflash and how they work. I'm sure you can get it running right again.
Wish I knew more, sorry!
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
no worries, thanks for your effort. Is there a way to completely start from scratch? like format and wipe everything, install fresh bootloader, firmware, etc? like wipe everything wipeable and installable in the hardware?
TheKaser said:
no worries, thanks for your effort. Is there a way to completely start from scratch? like format and wipe everything, install fresh bootloader, firmware, etc? like wipe everything wipeable and installable in the hardware?
Click to expand...
Click to collapse
My commands from the previous postings were to do just that. Format_all and use the configuration file to load from but I could've edited it wrong.
You can try manually pulling all the files from fresh stock software. I don't use any of the tools out there so it's back to research on it.
Sent from my SGH-T999 using Tapatalk 2
once I do a format all, do you know what will I end up with? no OS, no SDCard files, no internal memory, but also no recovery? If so, I guess I have to do flash recovery via Easy Flasher on APX mode.
edit 1:
i couldnt make the --format_partition --format_all work, it gave an error on partition 0.
So, I run --format_partition 1 and its taking too long it seems, cant tell if it's hung up or what...
edit2.
from the config file you provided in the other thread, I can see the partitions are named 3-16. I manually formatted them with your androidpartition.cfg file. I will proceed to installing the stuff and report back. Thanks!
I DID IT!!!
I formatted each partition separately with the configuration file.
Once that was done, there was no OS, no recovery, nothing.
In APX mode, flashed the official firmware using EasyFlasher and booted.
There, the screen can be switched on and off and it works!!!! I also could power it down normally.
Back to APX mode, flashed Team Rogue's recovery (TWRP still didn't work), and flashed EOS latest nightly. It all works like it should, I am very very happy.
Thank you sir TomTcom, you are the man!
edit. Also, I removed a dead SD card, that might have helped to not reboot the tablet, since it might have waited for ever to securely stop it while it was dead and non-responsive. I dont want to verify what happens if I plug it back in, I am happy with my brand new TF101, which didnt work properly since December
TheKaser said:
I DID IT!!!
I formatted each partition separately with the configuration file.
Once that was done, there was no OS, no recovery, nothing.
In APX mode, flashed the official firmware using EasyFlasher and booted.
There, the screen can be switched on and off and it works!!!! I also could power it down normally.
Back to APX mode, flashed Team Rogue's recovery (TWRP still didn't work), and flashed EOS latest nightly. It all works like it should, I am very very happy.
Thank you sir TomTcom, you are the man!
edit. Also, I removed a dead SD card, that might have helped to not reboot the tablet, since it might have waited for ever to securely stop it while it was dead and non-responsive. I dont want to verify what happens if I plug it back in, I am happy with my brand new TF101, which didnt work properly since December
Click to expand...
Click to collapse
Good for you! Glad you got it!
Sent from my SGH-T999 using Tapatalk 2
TheKaser said:
I DID IT!!!
I formatted each partition separately with the configuration file.
Once that was done, there was no OS, no recovery, nothing.
In APX mode, flashed the official firmware using EasyFlasher and booted.
There, the screen can be switched on and off and it works!!!! I also could power it down normally.
Back to APX mode, flashed Team Rogue's recovery (TWRP still didn't work), and flashed EOS latest nightly. It all works like it should, I am very very happy.
Thank you sir TomTcom, you are the man!
edit. Also, I removed a dead SD card, that might have helped to not reboot the tablet, since it might have waited for ever to securely stop it while it was dead and non-responsive. I dont want to verify what happens if I plug it back in, I am happy with my brand new TF101, which didnt work properly since December
Click to expand...
Click to collapse
Hi!
I have similar problem to you.
My tablet is not booting corectly. Stuck on the logo (look at the picture).
I have tried: Easy flash (a few soft), and when i click on the "unbric" my tablet is disconecting from PC.
I can't go into TWRP. I only boot into APX mode.
I can turn on my tablet by recovery mode, and chose there "android" option, but this is annoying.
I dont konw what to do ;(

[Q] Bricked TF300TG

Hello all,
I seem to have really soft bricked my TF300TG. I've now run out of ideas and maybe someone in here can help.
The following happend: I wanted to update my rooted TF300TG from running JB (CleanRom 3.0.4) with Bootloader ww_epad_10.4.3.9 to the current stock Rom from ASUS ( V10.6.2.6 ). I did unzip the zip from ASUS once and used the resulting zip for the flash.
I attemted this via Method 3: TWRP v. 2.5.0.0, following this guide (http://forum.xda-developers.com/showthread.php?t=2187982), guess I should have read the whole thread, not just the first 20 pages.
What happend was, that during the flash in TWRP I got an error with no error message. I tried to flash again for three times with the "same" error. Thats when I panicked and rebooted the device.
Since then its sitting here, just showing the ASUS logo and doing nothing. I think I understand why its doing nothing since I have still the old bootloader v 10.4.3.9 but a new 4.2 Stock ROM (albeit maybe damaged).
Sadly I have also had no success communicating with the device via ADB or Fastboot.
I still can access the bootloader menue which shows 4 icons: RCK, Android, USB and Wipe. But: the volume up key is not working (did work in Android though) and the volume down key traverses the item entries. So I have no way to select USB which should put me into fastboot mode.
Does anyone have any idea? Otherwise I'm declaring this my last Android tablet (loved it but it didn't quite live up to expectations, Tegra 3 just sucks) and move on.
Thanks for reading!
jak4kaj said:
Hello all,
I seem to have really soft bricked my TF300TG. I've now run out of ideas and maybe someone in here can help.
The following happend: I wanted to update my rooted TF300TG from running JB (CleanRom 3.0.4) with Bootloader ww_epad_10.4.3.9 to the current stock Rom from ASUS ( V10.6.2.6 ). I did unzip the zip from ASUS once and used the resulting zip for the flash.
I attemted this via Method 3: TWRP v. 2.5.0.0, following this guide (http://forum.xda-developers.com/showthread.php?t=2187982), guess I should have read the whole thread, not just the first 20 pages.
What happend was, that during the flash in TWRP I got an error with no error message. I tried to flash again for three times with the "same" error. Thats when I panicked and rebooted the device.
Since then its sitting here, just showing the ASUS logo and doing nothing. I think I understand why its doing nothing since I have still the old bootloader v 10.4.3.9 but a new 4.2 Stock ROM (albeit maybe damaged).
Sadly I have also had no success communicating with the device via ADB or Fastboot.
I still can access the bootloader menue which shows 4 icons: RCK, Android, USB and Wipe. But: the volume up key is not working (did work in Android though) and the volume down key traverses the item entries. So I have no way to select USB which should put me into fastboot mode.
Does anyone have any idea? Otherwise I'm declaring this my last Android tablet (loved it but it didn't quite live up to expectations, Tegra 3 just sucks) and move on.
Thanks for reading!
Click to expand...
Click to collapse
Try resetting the device (the little hole beneath the volume rocker and try to get to fastboot. there is no real reason other than broken PITs or trashfiles in /misc that should prevent you form getting fastboot.
also read my post here (or better the threat)
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
gl
buster
Buster99 said:
Try resetting the device (the little hole beneath the volume rocker and try to get to fastboot. there is no real reason other than broken PITs or trashfiles in /misc that should prevent you form getting fastboot.
also read my post here (or better the threat)
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
gl
buster
Click to expand...
Click to collapse
Hi buster,
thanks for the reply. Sadly I can't seem to enter fastboot since "fastboot erase system" stays at "waiting for device" when I reset the device with a paper clip and press the volume down button.
I'm trying this on linux but that should be a plus versus using windows.
Thanks again
jak4
jak4kaj said:
Hi buster,
thanks for the reply. Sadly I can't seem to enter fastboot since "fastboot erase system" stays at "waiting for device" when I reset the device with a paper clip and press the volume down button.
I'm trying this on linux but that should be a plus versus using windows.
Thanks again
jak4
Click to expand...
Click to collapse
yeah - linux sometimes is less of a nightmare when it comes to fastboot commands - but remember to install adb and fastboot
gl
Buster
Buster99 said:
yeah - linux sometimes is less of a nightmare when it comes to fastboot commands - but remember to install adb and fastboot
gl
Buster
Click to expand...
Click to collapse
Yes I have fastboot and adb installed. They come with the Android SDK which I need for work.
jak4
I have the same problem. Difference is that I did a reset after a failed install of CM11. Stuck at ASUS splash. Cannot access recovery or any other option that was previously available. Nothing is detecting the device as it sits...Tried Ubuntu, Win 7, Win 8.1. I have tried installing all drivers I could find, even tried installing as legacy device, but all drivers give an error that device cannot start. Did A LOT of searching around, and it seems to come down to the tablet not being detected by PC in the state it's in. Seems like there is a lot of help out there for folks that can get their computers to at least see the device.
Would die for some help!
coppervines said:
I have the same problem. Difference is that I did a reset after a failed install of CM11. Stuck at ASUS splash. Cannot access recovery or any other option that was previously available. Nothing is detecting the device as it sits...Tried Ubuntu, Win 7, Win 8.1. I have tried installing all drivers I could find, even tried installing as legacy device, but all drivers give an error that device cannot start. Did A LOT of searching around, and it seems to come down to the tablet not being detected by PC in the state it's in. Seems like there is a lot of help out there for folks that can get their computers to at least see the device.
Would die for some help!
Click to expand...
Click to collapse
what recovery did you use for installing cm11?
Buster99 said:
what recovery did you use for installing cm11?
Click to expand...
Click to collapse
CWM from probably close to a year ago. I attempted to use Rom Manager to flash a newer recovery that would work with CM11, and got stuck in a bootloop. Then I stupidly did a factory reset from boot menu . Wish there was a way around this...and I think I could work some magic if I could get a computer to detect the brick.
coppervines said:
CWM from probably close to a year ago. I attempted to use Rom Manager to flash a newer recovery that would work with CM11, and got stuck in a bootloop. Then I stupidly did a factory reset from boot menu . Wish there was a way around this...and I think I could work some magic if I could get a computer to detect the brick.
Click to expand...
Click to collapse
yeah well with an old recovery kitkat gets you a brick - try to get it somehow to fastboot and you should be able to get it working again
gl
buster
Buster99 said:
yeah well with an old recovery kitkat gets you a brick - try to get it somehow to fastboot and you should be able to get it working again
gl
buster
Click to expand...
Click to collapse
I would hate to think that my USB cable could be bad...it's been a LONG time since its done anything other than charge. Just need the pc to see the damn thing. ANY insight would be helpful.
APX
I was able to get to APX mode with the universal drivers (Vol +reset)...looking around to see if anyone else has had success. I never installed Nvflash...
in the other threat a guy just needed a working cable to get it to work. it's a pain with asus and the cable
gl
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
Buster99 said:
in the other threat a guy just needed a working cable to get it to work. it's a pain with asus and the cable
gl
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What thread? Not sure I understand what you mean...
http://forum.xda-developers.com/showthread.php?t=2179759
Sent from my TF300T using XDA Premium 4 mobile app
Buster99 said:
http://forum.xda-developers.com/showthread.php?t=2179759
Sent from my TF300T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Since i have apx access, i'm assuming the data side of the cable is working...plus, without being able to get into adb/fastboot on the tablet a new cable would be useless. Thinking about getting a mobo on ebay...one for 50 and one for 75$ i think. will have to get wife's approval first
coppervines said:
Since i have apx access, i'm assuming the data side of the cable is working...plus, without being able to get into adb/fastboot on the tablet a new cable would be useless. Thinking about getting a mobo on ebay...one for 50 and one for 75$ i think. will have to get wife's approval first
Click to expand...
Click to collapse
So I'm assuming there is no solution to this problem without sending it to ASUS or getting a new Motherboard?
I'm in the exact same position...
coppervines said:
CWM from probably close to a year ago. I attempted to use Rom Manager to flash a newer recovery that would work with CM11, and got stuck in a bootloop. Then I stupidly did a factory reset from boot menu . Wish there was a way around this...and I think I could work some magic if I could get a computer to detect the brick.
Click to expand...
Click to collapse
Wipe data from the bootloader erases everything, if you don't have nvflash blobs I think you're done for.
ebildude123 said:
Wipe data from the bootloader erases everything, if you don't have nvflash blobs I think you're done for.
Click to expand...
Click to collapse
"bootloader wipe data" soft brinks your tab.
always use custom recovery or fastboot to wipe the tf300t.
otherwise you need to erase all partitions and reflash recovery and start from scratch. assuming that fastboot still works.
cheers
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
Buster99 said:
"bootloader wipe data" soft brinks your tab.
always use custom recovery or fastboot to wipe the tf300t.
otherwise you need to erase all partitions and reflash recovery and start from scratch. assuming that fastboot still works.
cheers
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Boot loader wipe is a hard(ish) brick unless you have nvflash blobs since all you have access to is apx mode, no boot loader, no recovery, etc.
Sent from my TF300T on OmniROM (4.4.2) using Tapatalk 4
not necessarily, I did it for cm10.1 (drunken flashing not advised ) and i don't have an NV backup.
and i had fastboot to work with.
but things may have changed since then.
cheers
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app

TF300T Stuck in a Infinite Loop (HELP)

hello everyone im having a issue with my ASUS Tablet...
I got it off some guy from Kijiji for $100 It was working fine untill i noticed that the dock was not charging... So i did some reading online and people said that a Hard reset made it work for them and to do a cold boot.... So i did all that Via TWRP.... I did a full wipe of everything it could not even find the Partitions anymore... But all partitions are back and now its stuck in a Boot Loop... I can Access TWRP Just fine ( Power/Volume down ) all that works...
I tryed to Downlode a few Roms i tred all US Factory roms but they all Instantly Fail...
I downloaded KatKiss for the TF300T and it Would flash for about 5-10min then fail... This is the farthest one i have had flash... all others are instant fail...
I put the ROM on my SD Card and go to install on TWRP and select the rom and hit Flash...
Nothing is working....
What do i do... it was working fine.... all i did was a Wipe But i think i wiped to much lol....
Any advice on what to do ? Im not to sure what Version its on or anything...
stupid me i dint do any research lol... Using TWRP to reset is vary bad... Please can anyone help me...
I live in edmonton ,AB so if there are any pro ASUS Firmware people that would like to help me that would be great
also it says THIS DEVICE IS UNLOCKED on the top left
is this what i did ????? hears a Post from XpLoDWilD
- I wiped everything but didn't put a ROM on my sdcard, what to do?!
Calm down, you're not bricked, you're just a bit dumb. Go in "Install zip from sdcard" until you reach list files, so the sdcard is mounted. Then, open a command prompt, and do "adb push c:\path\to\the\rom.zip /sdcard/". Wait, and once done your rom.zip will appear in the files list when you go back and forth in files list.
found out all i need is a rom now.... i had time to do some research and i installed TWRP/Fastboot/ADB And im just trying to find a rom that will work
FIXED The Issue PLEASE REMOVE ADD....
Figured all of this out on my own....

Categories

Resources