My mother has a TF300T that, according to her, just stopped booting. It gets to the ASUS screen, and the little circle of dots just flashes forever. I've managed to get fastboot working, and tried flashing a couple of the firmwares they have on the official site, but no luck.
Is there anything I can do to recover this tablet if it was never rooted or equipped with a recovery system before? I'd like to do so while saving the files that were on it, but if that's impossible, I'll deal with it. Thanks!
HoratioGiovanni said:
My mother has a TF300T that, according to her, just stopped booting. It gets to the ASUS screen, and the little circle of dots just flashes forever. I've managed to get fastboot working, and tried flashing a couple of the firmwares they have on the official site, but no luck.
Is there anything I can do to recover this tablet if it was never rooted or equipped with a recovery system before? I'd like to do so while saving the files that were on it, but if that's impossible, I'll deal with it. Thanks!
Click to expand...
Click to collapse
Is the bootloader unlocked ?
What bootloader version is on the tablet ?
Thx Josh
lj50036 said:
Is the bootloader unlocked ?
What bootloader version is on the tablet ?
Thx Josh
Click to expand...
Click to collapse
Sort of new to this. How would I find out?
Actually, I'm just gonna wager it isn't unlocked since I didn't do anything to this tablet. It's completely stock. It just stopped booting one day.
HoratioGiovanni said:
Actually, I'm just gonna wager it isn't unlocked since I didn't do anything to this tablet. It's completely stock. It just stopped booting one day.
Click to expand...
Click to collapse
Ok lets boot into the bootloader, VOL DOWN & POWER .....
In the upper left the version will start with 'epad_'
Thx Josh
Awesome, thanks for your help, in advance.
Bootloader version is 10.6.1.6-20130225
HoratioGiovanni said:
Awesome, thanks for your help, in advance.
Bootloader version is 10.6.1.6-20130225
Click to expand...
Click to collapse
Can you check and make sure its not 10.6.1.8-20130225
That is a real old bootloader , Can you also get the SKU of the tab ...
It will be the 2 letters in front of the bootloader version ......
e.g. US_epad-10.6.1.6-20130225
In red is the SKU, I am doing a test on mine as its unbrickable, I will let you know what I find..... :good:
Thx Josh
Sorry, yup, it's 10.6.1.8-20130225, the 8 just really looks like a 6. The SKU is WW.
HoratioGiovanni said:
Sorry, yup, it's 10.6.1.8-20130225, the 8 just really looks like a 6. The SKU is WW.
Click to expand...
Click to collapse
Ok, you should be able to use the 'WIPE DATA' on the bootloader screen .....
Use 'vol down & power' to get into the bootloader , then 'vol down' to 'wipe data' 'vol up' on it ....
It will ask if you are sure you want to wipe ......
'vol up' to agree, let it do it thing and it will boot into android .....
This is going to wipe all the data from the device, but not much can be done about that.....
Thx Josh
Worked like a charm! Thanks!
HoratioGiovanni said:
Worked like a charm! Thanks!
Click to expand...
Click to collapse
Great, you got it up and running ....
Can you add 'SOLVED' to the thread title ....
Thx Josh
Just to clarify, for other users that may find this thread ......
THIS ONLY WORKS ON AN ALL STOCK TABLET
Related
:crying:
Hello there!
I have a really serious problem with my TF300T. I had the newest bootloader installed with 4.4 enabled TWRP recovery. I had the 2014.01.07. CM 11 nightly installed and was running fine. I have seen, that there are some never releases so decided to update. I downloaded the newest nightly yesterday and pressed power button. Selected reboot and then selected Recovery.
And here comes the problem!
The tablet bricked himself! It did restart but got into a bootloop I cannot get through the Asus splashscreen. I tried POWER+VOLD DOWN, I cannot get into fastboot or recovery. The tablet keep rebooting, no boot to android either. I tried power off, no success. I tried the reset button. I removed battery, still the same.
As I have never done anything to the bootloader, I did not consider making NVFLASH backup, as it is a risky operation. Shame on me...
How could it happen????? Does cyanogenmod alter Bootloader partition to reboot into recovery??? What the hell??
Please help me somehow! I dont know what to do, I tried all I could! Maybe APX? or only Asus RMA??
yours,
dpeti said:
:crying:
Hello there!
I have a really serious problem with my TF300T. I had the newest bootloader installed with 4.4 enabled TWRP recovery. I had the 2014.01.07. CM 11 nightly installed and was running fine. I have seen, that there are some never releases so decided to update. I downloaded the newest nightly yesterday and pressed power button. Selected reboot and then selected Recovery.
And here comes the problem!
The tablet bricked himself! It did restart but got into a bootloop I cannot get through the Asus splashscreen. I tried POWER+VOLD DOWN, I cannot get into fastboot or recovery. The tablet keep rebooting, no boot to android either. I tried power off, no success. I tried the reset button. I removed battery, still the same.
As I have never done anything to the bootloader, I did not consider making NVFLASH backup, as it is a risky operation. Shame on me...
How could it happen????? Does cyanogenmod alter Bootloader partition to reboot into recovery??? What the hell??
Please help me somehow! I dont know what to do, I tried all I could! Maybe APX? or only Asus RMA??
yours,
Click to expand...
Click to collapse
No, sorry, you won't be able to use APX mode without have making the NvFlash backups beforehand.
is this possible? I'm now afraid to update to newer cm11 versions...
aplopeanu said:
is this possible? I'm now afraid to update to newer cm11 versions...
Click to expand...
Click to collapse
Yeah, Ive seen it happen to multiple people across the forums idk what the actual bug is though.
cmendonc2 said:
Yeah, Ive seen it happen to multiple people across the forums idk what the actual bug is though.
Click to expand...
Click to collapse
so basically ... don't update CM11 until this is fixed right?
aplopeanu said:
so basically ... don't update CM11 until this is fixed right?
Click to expand...
Click to collapse
Im not sure It only happened to a few people in addition to OP of this thread. Im not upgrading to be safe, but maybe the dev should look into it.
cmendonc2 said:
Im not sure It only happened to a few people in addition to OP of this thread. Im not upgrading to be safe, but maybe the dev should look into it.
Click to expand...
Click to collapse
Yea I'm doing the same thing...btw if you birck it...changing the motherboard will unbrick it?
aplopeanu said:
Yea I'm doing the same thing...btw if you birck it...changing the motherboard will unbrick it?
Click to expand...
Click to collapse
In theory, yes. But many people consider it easier to RMA it.
cmendonc2 said:
In theory, yes. But many people consider it easier to RMA it.
Click to expand...
Click to collapse
RMA?
aplopeanu said:
RMA?
Click to expand...
Click to collapse
Send it back to Asus and pay the repair costs.
I flashed the newest version of TWRP and now I have a split screen with 2 menus and I cannot do anything in recovery now. I've been trying to find a solution but I can't find anything, has anyone else had this issue and fixed it?
MrKite4 said:
I flashed the newest version of TWRP and now I have a split screen with 2 menus and I cannot do anything in recovery now. I've been trying to find a solution but I can't find anything, has anyone else had this issue and fixed it?
Click to expand...
Click to collapse
On the bootlaoder screen where you enter the rck to get to TWRP, in the upper left
What is the bootlader version ?
e.g of the bootloader version is
epad_XX_xx.xx.xx.xx.xx
something like that...
Thx Josh
lj50036 said:
On the bootlaoder screen where you enter the rck to get to TWRP, in the upper left
What is the bootlader version ?
e.g of the bootloader version is
epad_XX_xx.xx.xx.xx.xx
something like that...
Thx Josh
Click to expand...
Click to collapse
WW_epad-10.6.1.8-20130225
MrKite4 said:
WW_epad-10.6.1.8-20130225
Click to expand...
Click to collapse
Yes, that is the issue ..
You need to be on a bootloader ending in 27.1 or 27.5
To use the newest version of twrp ....
If you need any help with upgrade
Let us know..
Thx Josh
lj50036 said:
Yes, that is the issue ..
You need to be on a bootloader ending in 27.1 or 27.5
To use the newest version of twrp ....
If you need any help with upgrade
Let us know..
Thx Josh
Click to expand...
Click to collapse
Yeah definitely, if its not too much to ask. Right now I have no SD card because of not removing it safely so it destroyed it going back and forth between my phone and tablet, but once I get another one I definitely wanna get the recovery fixed in my tablet.
MrKite4 said:
Yeah definitely, if its not too much to ask. Right now I have no SD card because of not removing it safely so it destroyed it going back and forth between my phone and tablet, but once I get another one I definitely wanna get the recovery fixed in my tablet.
Click to expand...
Click to collapse
PM me if you would like some help with the...
Thx Josh
Hey guys. I had flashed gpe edition on my XT1032 to get lollipop and everythign was fine. Yesterday I decided to get back to stock in order to wait for 5.1 but since then i have messed up everything in my phone. The point in wich i am now is that the phone wont boot and will be stuck in bootloader warning screen and when in fastboot adb wont recognize my phone which means i can do nothing to flash a new rom or anything. Guys please help i really am desperate and i have tried everything.
StanEzio said:
Hey guys. I had flashed gpe edition on my XT1032 to get lollipop and everythign was fine. Yesterday I decided to get back to stock in order to wait for 5.1 but since then i have messed up everything in my phone. The point in wich i am now is that the phone wont boot and will be stuck in bootloader warning screen and when in fastboot adb wont recognize my phone which means i can do nothing to flash a new rom or anything. Guys please help i really am desperate and i have tried everything.
Click to expand...
Click to collapse
If it says AP Fastboot Flash Mode at the very top, you need to work with fastboot tool, not adb. They're not the same.
riding1 said:
If it says AP Fastboot Flash Mode at the very top, you need to work with fastboot tool, not adb. They're not the same.
Click to expand...
Click to collapse
That's what it says but how do i work with fastboot? The sites and the guides i have searched nothing works. Could you explain to me what i have to do or refer me to another guide probably?
StanEzio said:
That's what it says but how do i work with fastboot? The sites and the guides i have searched nothing works. Could you explain to me what i have to do or refer me to another guide probably?
Click to expand...
Click to collapse
What OS are you on?
riding1 said:
What OS are you on?
Click to expand...
Click to collapse
8.1. So i tried what you said (kinda figured it out) and everything seems to be working out just fine. thanks a lot. The only thing i notice is something wrong with the screen, a line which goes from top to bottom of the screen every other second
StanEzio said:
8.1. So i tried what you said (kinda figured it out) and everything seems to be working out just fine. thanks a lot. The only thing i notice is something wrong with the screen, a line which goes from top to bottom of the screen every other second
Click to expand...
Click to collapse
Great. Can't help you with the lines - maybe look at other roms.
riding1 said:
Great. Can't help you with the lines - maybe look at other roms.
Click to expand...
Click to collapse
Thanks a lot.
StanEzio said:
8.1. So i tried what you said (kinda figured it out) and everything seems to be working out just fine. thanks a lot. The only thing i notice is something wrong with the screen, a line which goes from top to bottom of the screen every other second
Click to expand...
Click to collapse
The lines are due to the fact that you have a lollipop bootloader with a Kit Kat ROM. Upgrade to stock 5.02 or the latest CM12 and the lines will go away, except possibly in custom recovery. No lines if running stock recovery.
audit13 said:
The lines are due to the fact that you have a lollipop bootloader with a Kit Kat ROM. Upgrade to stock 5.02 or the latest CM12 and the lines will go away, except possibly in custom recovery. No lines if running stock recovery.
Click to expand...
Click to collapse
Thanks for the tip though it stoped on its own
StanEzio said:
Thanks for the tip though it stoped on its own
Click to expand...
Click to collapse
If you're running Kit Kat, it will stop if you lock and unlock the phone using the power button. If you restart the phone or your boot into recovery, the lines will reappear until your lock and re-lock again.
Hello, everybody!
My new tablet, it is not recall one, i received from nvidia because i have a recalled tablet, it is already killed.
But now, my new tablet also sticking in APX mode, i used a nvidia toolbox from a person to flash the first version about this tablet, when it finished, i rebooted my tablet, the screen became black, and never show anything, can't enter fastboot mode, my PC show APX!
What i can do now???:crying::crying::crying:
What toolbox and what firmware? What did you do, step by step, to get in this state?
lafester said:
What toolbox and what firmware? What did you do, step by step, to get in this state?
Click to expand...
Click to collapse
A Chinese man uploaded it on a website, he said this toolbox can flash the first version of this tablet, when i run the flash.bat, the cmd window showed many, system.img is 900+M but was separated as 90+m and flashed many times, also userdata.....
I want to show you a picture about the cmd window when i flash this img, but i don't know how to upload a picture.....sorry:crying::crying::crying:
nobody......
wyy1993 said:
nobody......
Click to expand...
Click to collapse
Have you tried forcing boot into fastboot with volume down?
Was the replacement a K1 and did you flash a ROM for the original?
Anything else you can tell us about this mysterious Chinese man's website? Maybe post a link.
Still got that pic of the console output or a text version?
Any other info that can help us to help you?
durgis said:
Have you tried forcing boot into fastboot with volume down?
Was the replacement a K1 and did you flash a ROM for the original?
Anything else you can tell us about this mysterious Chinese man's website? Maybe post a link.
Still got that pic of the console output or a text version?
Any other info that can help us to help you?
Click to expand...
Click to collapse
I can't forcing boot into fastboot, i tried power button and volume down, nothing happened, the screen always black...
I think the partition is broken, i don't know the replacement is or not K1, but i flashed the original version....
I used this toolbox: http://bbs.gfan.com/android-8245744-1-1.html V2.3
Thanks for your attention!
wyy1993 said:
I think the partition is broken, i don't know the replacement is or not K1, but i flashed the original version....
I used this toolbox: http://bbs.gfan.com/android-8245744-1-1.html V2.3
Click to expand...
Click to collapse
I think you might be right about the partitions being wrong. The easiest way to distinguish the tablet is that the original has a stylus and K1 does not.
I couldn't read much on that forum, but it specifically calls out "nv-recovery-image-shield-tablet-k1-factory0_0_0.zip". So you might have flashed a recovery/rom for the wrong device and bricked it.
durgis said:
I think you might be right about the partitions being wrong. The easiest way to distinguish the tablet is that the original has a stylus and K1 does not.
I couldn't read much on that forum, but it specifically calls out "nv-recovery-image-shield-tablet-k1-factory0_0_0.zip". So you might have flashed a recovery/rom for the wrong device and bricked it.
Click to expand...
Click to collapse
so, do you think my tablet is broken? Forever broken?
wyy1993 said:
so, do you think my tablet is broken? Forever broken?
Click to expand...
Click to collapse
Someone else may come along with a better idea, but I think it's is beyond my abilities.
durgis said:
Someone else may come along with a better idea, but I think it's is beyond my abilities.
Click to expand...
Click to collapse
Okay...anyway, thanks for your reply!
OnePlus 7 stuck in "Your device is corrupt it can't be trusted" after locking the boo
Help. I've made a big mistake. I can only access the Bootloader. Recovery mode is not accessible.
As with the 7 Pro, I didn't like the standard 7 and decided to return it. Thought it would be a good idea to lock the bootloader before doing so.
OnePlus support won't help me and they are telling me that I can't return the device anymore. "Repair is the only option now" even though I'm in the 30 days return window.
GoToNap said:
Help. I've made a big mistake. I can only access the Bootloader. Recovery mode is not accessible.
As with the 7 Pro, I didn't like the standard 7 and decided to return it. Thought it would be a good idea to lock the bootloader before doing so.
OnePlus support won't help me and they are telling me that I can't return the device anymore. "Repair is the only option now" even though I'm in the 30 days return window.
Click to expand...
Click to collapse
Try this one.
https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478
If thats not working because of locked bootloader, you can try the MSMTool.
https://forum.xda-developers.com/oneplus-7/how-to/unbrick-tool-oneplus-7-msmtool-hydrogen-t3953240
Note: Never lock the bootloader if system isn't Stock!
Kollachi said:
Try this one.
https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478
If thats not working because of locked bootloader, you can try the MSMTool.
https://forum.xda-developers.com/oneplus-7/how-to/unbrick-tool-oneplus-7-msmtool-hydrogen-t3953240
Note: Never lock the bootloader if system isn't Stock!
Click to expand...
Click to collapse
I keep trying the MSMTool method but nothing happens when I keep both volume buttons pressed...
GoToNap said:
I keep trying the MSMTool method but nothing happens when I keep both volume buttons pressed...
Click to expand...
Click to collapse
Be sure device is off and try to hold the buttons while connecting phone to your computer.
Kollachi said:
Be sure device is off and try to hold the buttons while connecting phone to your computer.
Click to expand...
Click to collapse
OMG it worked. Thank you so much. You saved my life man!
GoToNap said:
OMG it worked. Thank you so much. You saved my life man!
Click to expand...
Click to collapse
Np dude. Good to know if I could help you.
Kollachi said:
Np dude. Good to know if I could help you.
Click to expand...
Click to collapse
Sorry to be a pain in the ass, but I can't really figure out how to get back to OxygenOS now. Everything is in Chinese...
Also, will this procedure mess with anything on my device?
GoToNap said:
Sorry to be a pain in the ass, but I can't really figure out how to get back to OxygenOS now. Everything is in Chinese...
Also, will this procedure mess with anything on my device?
Click to expand...
Click to collapse
Read the unbrick thread. There is all you need.:good:
Kollachi said:
Read the unbrick thread. There is all you need.:good:
Click to expand...
Click to collapse
I've looked through it but couldn't find anything. Sorry, I am extremely stressed out as tomorrow I am supposed to return this phone and I want to make sure that it passes inspection.
So, I did the following:
- Used the unbrick tool which lead me to HydrogenOS
- Installed the latest OxygenOS version on top of it
- Did a factory reset, and so far everything looks to be in working order.
Am I missing anything here? Are there any possible changes done to the device so that it won't pass inspection?
Sorry again for being so annoying...
GoToNap said:
I've looked through it but couldn't find anything. Sorry, I am extremely stressed out as tomorrow I am supposed to return this phone and I want to make sure that it passes inspection.
So, I did the following:
- Used the unbrick tool which lead me to HydrogenOS
- Installed the latest OxygenOS version on top of it
- Did a factory reset, and so far everything looks to be in working order.
Am I missing anything here? Are there any possible changes done to the device so that it won't pass inspection?
Sorry again for being so annoying...
Click to expand...
Click to collapse
So if OxygenOS works and you also did a factory reset, your device should be fine. Check bootloader status. But it should be locked.
Kollachi said:
So if OxygenOS works and you also did a factory reset, your device should be fine. Check bootloader status. But it should be locked.
Click to expand...
Click to collapse
Yes, I'm on the latest OxygenOS version after a factory reset and the bootloader is locked.
Thank you so much man! You are my hero
GoToNap said:
Yes, I'm on the latest OxygenOS version after a factory reset and the bootloader is locked.
Thank you so much man! You are my hero
Click to expand...
Click to collapse
Great. you could report your experience at the other thread. Maybe it helps other people too.:good: