Related
Guys,
As using LG's software to update, my phone restarted itself after downloading then it went to S/W upgrade screen then the program says remove the battery bla bla and restart after I did that program never recognized my phone again and everytime I power on my phone it goes to S/W upgrade. Then I go into clockwork recovery and re install CM7 but still can't pass the S/W upgrade screen any ideas?
Ps. I know there is a topic like this but after they go into recovery mode, it somehow went back to normal but mine didn't.
I was on stock, never rooted before, when I tried updating. I'm now stuck on that same S/W upgrade screen. I've been trying many things, but I do believe I may have a brick. The LG software is giving me this error now.
CaliLove310 said:
I was on stock, never rooted before, when I tried updating. I'm now stuck on that same S/W upgrade screen. I've been trying many things, but I do believe I may have a brick. The LG software is giving me this error now.
Click to expand...
Click to collapse
I was rooted and running Light&Sinister.
I'm stuck on S/W update. I was rooted stock. I don't know what to do.
Going to be a bunch of bricks if this isn't figured out. I am in same boat. All stock.
If any of you guys figure this out, let us know.
Having this same issue...seems as if the SPL was half written and it screwed everything up..
i have the samee isssue and mine wasnt rooted someone help please
I also tried .kdz flasher but didn't help either but at least we know that phone is not bricked
How do we use the kdz flasher I downloaded the kdz version of the rom but don't know what I have to do to flash using the kdz
Sent from a guy living in a van down by the river
raar said:
I also tried .kdz flasher but didn't help either but at least we know that phone is not bricked
Click to expand...
Click to collapse
Excuse me, but how did you get the software to show the log on the bottom of the jpg that you attached?
I was stuck at 4% for a while, so I clicked the update tab that was flashing and all of a sudden it started up again.
It all looked good, I have Gingerbread, but for Baseband version is says "Unkown" and I can't choose a network under Network Operators. Nothing shows up under search. When I go to Access Point Names, I do see T-Mobile US and everything looks to be the same as before, but I only have WiFi access.
Use [RECOVERY][APP]Update 6-16: One-Click ClockworkMod 4.0.0.2 NvFlasher
Flash CWM follow instructions
Boot into recovery
Wipe
Restore backup (I used stock rooted)
Remove Batt
Reinstall Batt and boot into recovery
Start LG Update
Now should see the phone and you can update
Mine is still updating will see if it finishes
Failed sent me to support
Links to the app your talking about and what all your talking about. Everything you said is foreign to me.
For those stuck try booting into bootloader volume plus power button. The hit reset froM there see if that works
Sent from a guy living in a van down by the river
jriv said:
For those stuck try booting into bootloader volume plus power button. The hit reset froM there see if that works
Sent from a guy living in a van down by the river
Click to expand...
Click to collapse
Volume Down? Doesn't that just boot into recovery? Where does it say reset? I'm confused.
It doesn't
My will show the box and the little android and then boot to the S/W update screen
chrisdepew said:
My will show the box and the little android and then boot to the S/W update screen
Click to expand...
Click to collapse
Same here, that's the stock recovery screen. I can flash either stock or clockworkmod from the apx loader by holding volume up and down, then plugging in the phone without the battery and using the nvflasher to flash whatever recovery I want. Other than getting into the recovery...I can't do anything without the S/W Upgrade screen coming up..damn you LG, damn you to hell.
Volume up plus power not volume down my mistake
Sent from a guy living in a van down by the river
Hello. I tried using the search button, but couldnt find anything. Sorry if I didnt look far enough into this before posting.
I have an Inspire 4g, and 2 days ago I rooted it, so that I may instal the sound mod. Im still running the stock rom. Well tonight, I tried to do a factory update, and now my phone is frozen. On the screen is a white triangle, with a yellow exclamation point in the middle and the droid robot below it. How do I fix this? Im trying to not freak out, as this is my first "smart phone".
Please help!
Thanks Chris
What do you exactly mean with "factory update". Do you mean OTA update or did you flash RUU?
Phone is just propably in recovery mode. If it has been there for long time, pull battery out and reinsert it and try to boot.
clark_farms said:
Hello. I tried using the search button, but couldnt find anything. Sorry if I didnt look far enough into this before posting.
I have an Inspire 4g, and 2 days ago I rooted it, so that I may instal the sound mod. Im still running the stock rom. Well tonight, I tried to do a factory update, and now my phone is frozen. On the screen is a white triangle, with a yellow exclamation point in the middle and the droid robot below it. How do I fix this? Im trying to not freak out, as this is my first "smart phone".
Please help!
Thanks Chris
Click to expand...
Click to collapse
If I recall correctly when your rooted you are NOT suppose to OTA update from carrier. You suppose to wait for the rooted version from XDA Devs and flash it.
Sent from my Inspire 4G using xda premium
Yeah, you're never supposed to update OTA from AT&T if you're rooted. Unfortunately you learned this the hard way . I'm not 100% sure of the fix, but the go to move always is try to get into HBOOT. Do this by turning of the phone and then press the vol. down rocker button and the power button at the same time. If you can get into HBOOT then you'll be able to get into recovery to flash a new ROM or restore a back-up.
clark_farms said:
Hello. I tried using the search button, but couldnt find anything. Sorry if I didnt look far enough into this before posting.
I have an Inspire 4g, and 2 days ago I rooted it, so that I may instal the sound mod. Im still running the stock rom. Well tonight, I tried to do a factory update, and now my phone is frozen. On the screen is a white triangle, with a yellow exclamation point in the middle and the droid robot below it. How do I fix this? Im trying to not freak out, as this is my first "smart phone".
Please help!
Thanks Chris
Click to expand...
Click to collapse
Chris, do as Bacon told you...try booting into hboot (Power + volume down) and check if you are still S-OFF (on the left corner you will see ACE PVT S-OFF or S-ON) if you are still S-OFF then you will have to try to flash a recovery image...
Chris,
I had the same issue when I first rooted. The process discussed above should fix it if you have a rom to flash on your sdcard, if you don't have a flashable rom, or can't access your sdcard through usb storage in your phone, pull your sdcard and put it into a reader to load a rom, then flash the rom using the instructions found in any number of threads about flashing custom roms. I am using IceColdSandwich v 4.2 and like it very much. Good luck.
Hey,
My Asus Tf300t has been working perfectly until I wanted to get into recovery mode (RCK) yesterday. It got stuck there and
I tried it another time and it didn't work. After that I let it go and just booted normally, but then it stayed at the "ASUS Inspiring inno.... etc." screen.
Now I can shut my device down by holding the power button, but I cant get it to cold boot or get into recovery options again, it just boots endlessly.
My device has been unlocked and working fine for months.
What can I do?
regards,
Pmobilee
make sure that you are hold the "volume down" button, and hope it puts you back to where you can boot into recovery. Does that tablet boot at all, or just a "bootloop"
Did you have a working recovery before this? Like have you booted your recovery before and know that it was working?
Sent from my Nexus 7 using xda app-developers app
tazzz013 said:
make sure that you are hold the "volume down" button, and hope it puts you back to where you can boot into recovery. Does that tablet boot at all, or just a "bootloop"
Click to expand...
Click to collapse
Yes, I have been into the recovery and know the procedure. And im afraid the boot goes as far as the asus logo.
markymark567 said:
Did you have a working recovery before this? Like have you booted your recovery before and know that it was working?
Yes, recovery booted before. But this all started when I tried to boot recovery again, and it got stuck. Then this infitite boot occurred.
Click to expand...
Click to collapse
and when you tried to boot recovery again what method did you use? did you use the "reboot recovery" option in your recovery or ROM power menu?or did you do it manually?(hold vol- and power then press vol+)?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Hi all. I'm in the exact same situation. Didn't want to make a new thread though.
I rooted my TF300T a few months ago (Oct 2013), and it has been running fine on CyanogenMod 10.2. So I ran the CyanogenMod Update app (Settings > About Tablet > CyanogenMod Updates), then downloaded the LATEST nightly (dated yesterday: Dec 14, so 10.2...141213). I don't know if this is a factor, but I usually pull down the notification bar and tap the "Reboot and Install" option, but I accidentally cleared my notifications, so I went back into CyanogenMod Updates, tapped the installed button for the latest nightly, and tablet started rebooting.
However I cannot get past the boot screen. So recovery is not loading. I used TWRP last time I did this. I Can't turn the tablet off either, at least not until I plugged the USB from my PC to the tablet then tried long pressing the Power button and holding Volume Down. Before plugging USB in it would simply restart and sit on the boot screen again.
I have to leave the house for now, but will attempt to get into Recovery later tonight with same methods as above. Fingers crossed!
EDIT: I remembered, it was 10.2, not 10.1 I was running. So I shouldn't have had any issues going from 10.2 to a newer 10.2.
I'm back home now. I've tried again to get into Recovery, but cannot. I've got the tablet plugged into the PC with the USB, I'm holding Power and Volume Down, but nothing. Instead it seemly turns off, but comes back on and stays on the same boot screen (Asus. Inspiring Innovation, etc...).
And I can't figure out how I was able to turn the damn thing off before either. So I have to leave it on until the power drains. So that sucks!
Is it bricked?
Let's do this together. I recently tried to upgrade to 4.4 from 4.3 and I accidently erased my tablet by manually booting into twrp 2.5 and selecting the 3rd option which is wipe data...so we are in the same boat.
Has your battery drained yet?
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Ideas4ya said:
Let's do this together. I recently tried to upgrade to 4.4 from 4.3 and I accidently erased my tablet by manually booting into twrp 2.5 and selecting the 3rd option which is wipe data...so we are in the same boat.
Has your battery drained yet?
Click to expand...
Click to collapse
Damn, that sucks! Yes, battery has now drained, and yes, let's work this out together. What ROM were you using? Android 4.4 is not out on CyanogenMod for the TF300T, and I will probably stick to CM. But if I have to use something else to get this fixed, I'll do it.
Was any fix found for this? I am now experiencing the same problem after trying to reboot into recovery to upgrade Cyanogen. Any help would be appreciated.
fdbryant3 said:
Was any fix found for this? I am now experiencing the same problem after trying to reboot into recovery to upgrade Cyanogen. Any help would be appreciated.
Click to expand...
Click to collapse
Nope, and after a lot of support and help from the good guys on the Transformer Forums, I've declared this unfixable. If you had a NVIDIA backup, you'd be fine, but without that you're pretty much screwed, sorry to say.
Can you get into bootloader? If so you can do this:
http://forum.xda-developers.com/showthread.php?t=2425581
And it should resolve ANY bad flash/wrong flash issues.
Hi. I hope this is the correct forum. My Samsung Galaxy Tab 2 (10.1) won't shut down after the latest firmware update. I believe I had 4.2.1 and now I have 4.2.2. My device name is is GT-P5113. I plugged the Tab into my computer and Kies opened automatically. It said there was an update for my device so I updated.
All seems to be ok, but now when I choose to "shut down" the tablet shuts down and then cycles back on as if I had just pressed the power button to turn it back on.
I guess it could be worse - it could be refusing to turn on.
Is there a fix for this? Anybody else had this problem?
It is not rooted and I don't really want to do so.
Thanks in advance for any help!
I think u could wipe cache in stock recovery I would do that and see if that fixes it. Hold down vol up and power at the same time till the device reboots into recovery. Dunno how it is on the bigger ones but on the 7" I have to keeo holding the buttons for a second longer after the samsung gtab2 logo comes on to boot in to recovery.
Remember u dont want to factory reset just wipe cache
Sent from my GT-P3113 using xda app-developers app
wipe cache
Thank you for the reply. I tried that and got an "error". I was able to get to recovery mode and choose "wipe cache". It begins and I get an error message.
mymeatb18 said:
I think u could wipe cache in stock recovery I would do that and see if that fixes it. Hold down vol up and power at the same time till the device reboots into recovery. Dunno how it is on the bigger ones but on the 7" I have to keeo holding the buttons for a second longer after the samsung gtab2 logo comes on to boot in to recovery.
Remember u dont want to factory reset just wipe cache
Sent from my GT-P3113 using xda app-developers app
Click to expand...
Click to collapse
beezerhale said:
Thank you for the reply. I tried that and got an "error". I was able to get to recovery mode and choose "wipe cache". It begins and I get an error message.
Click to expand...
Click to collapse
What type of error?? :cyclops:
error
It just read "error" and a image of the little android on it's back.
mythi said:
What type of error?? :cyclops:
Click to expand...
Click to collapse
beezerhale said:
It just read "error" and a image of the little android on it's back.
Click to expand...
Click to collapse
can you take a picture of it ??
mythi said:
What type of error?? :cyclops:
Click to expand...
Click to collapse
mythi said:
can you take a picture of it ??
Click to expand...
Click to collapse
I just uploaded 4 pics to a section of a website that I already have running.
Here is the link:
http://6thgraderocks.wix.com/galazyerror
The images show the end process of updating through Kies (I screen captured), the current tab info, the recovery screen and the error I get when I try to erase cache. Keep in mind, I am able to reboot and my tablet comes on like normal - no issues except when I try to turn it off - it comes right back on.
beezerhale said:
I just uploaded 4 pics to a section of a website that I already have running.
Here is the link:
http://6thgraderocks.wix.com/galazyerror
The images show the end process of updating through Kies (I screen captured), the current tab info, the recovery screen and the error I get when I try to erase cache. Keep in mind, I am able to reboot and my tablet comes on like normal - no issues except when I try to turn it off - it comes right back on.
Click to expand...
Click to collapse
Did you try flashing pit?? did you flash jb bootloader ?? did your device be rooted before flash ?? were you on cm/aokp/pac/slim/etc ??? if yes whic h build did you flash black hawk next kernel ?? <--- may be it what caused it ---> did you try to downgrade to 4.0.3/4.0.4/4.1.2 if yes what happened what did you flash before going to stock rom like mod and etc ???? hope you answer these questions !!
also try this
enable usb debugging
turn off your tab fully
connect tab to pc pull a logcat dsmg ksmg and post them as txt or pastbin
does your tab stuck in recovery loop like rebooting always to recovery sometimes until you compeletly shut down the tab?
if it is under warranty return it to SAMMY TO FIX IT IT IS THEIR FAULT !!
i think it is not hard ware related don't worry !!
This tab is not rooted or tampered with at all. I have no desire to do so.
mythi said:
Did you try flashing pit?? did you flash jb bootloader ?? did your device be rooted before flash ?? were you on cm/aokp/pac/slim/etc ??? if yes whic h build did you flash black hawk next kernel ?? <--- may be it what caused it ---> did you try to downgrade to 4.0.3/4.0.4/4.1.2 if yes what happened what did you flash before going to stock rom like mod and etc ???? hope you answer these questions !!
also try this
enable usb debugging
turn off your tab fully
connect tab to pc pull a logcat dsmg ksmg and post them as txt or pastbin
does your tab stuck in recovery loop like rebooting always to recovery sometimes until you compeletly shut down the tab?
if it is under warranty return it to SAMMY TO FIX IT IT IS THEIR FAULT !!
i think it is not hard ware related don't worry !!
Click to expand...
Click to collapse
I have the exact same problem with BOTH my Galaxy Tab 2 10.1 (Wi-Fi only) It's a software problem for sure...
Also flashing back to 4.1.1 or lower will eliminate the problem
Sent from my GT-P5113 using xda app-developers app
I know I could probably do that (flash back) myself, but I just don't want to. I have bricked a Kindle Fire before while trying to make it do what I wanted it to. I don't want to mess with this Galaxy - it does exactly what I want it to --- surf the web, Netflix/Hulu, and comic books - I'm not too complicated!
I spoke with Samsung yesterday and they said to try a hard reset. That did not work. I spoke with another rep this morning and they are going to repair or replace it for me. He sent a shipping label to my email. This was a gift and I have no receipt. I am VERY pleased with the service from Samsung.
SebasC said:
Also flashing back to 4.1.1 or lower will eliminate the problem
Sent from my GT-P5113 using xda app-developers app
Click to expand...
Click to collapse
So you're going to replace a perfectly good product with a software mistake? I've two tablets, unrooted, 4.2.2 with the same problem... Your better off waiting for a fix..
Why shoukd he feel burdened for something he had no control over. Samsung sent the update, iys not his fault its not doing what it should. If he wants to return it cuz it doesnt turn off as it should he has every right to do so. At least he didnt brick it and is expecting samsung to pay for it.
Sent from my GT-P3113 using xda app-developers app
I had the same problem
Hello,
I registered here to just answer your question since I've been searching around on the internet as well for this problem. I have a Samsung Galaxy Tab 2 10.1 with version 4.2.1. I updated to version 4.2.2 and all hell broke loose. Before I get into it, I had a perfectly working tablet that never had any problems. I installed all updates through OTA or Samsung Kies. It's not rooted.
Anyway, after the update to 4.2.2 my tablet wouldn't turn on. I had to plug it into the wall outlet and then it finally turned on. After playing around with it, some of the widgets didn't work so I thought maybe I should turn it off and reboot it. When I chose "power off" it wouldn't turn off. Instead it would automatically restart. After trying several attempts it still wouldn't turn off so I contacted Samsung. They made me clear the cache and then wipe out the whole system and install a fresh copy of the software. The tablet then went black and now all that was shown on the screen was the little android bot with the error message like how yours is now. It wouldn't boot up to the main screen anymore.
So I had to return the tablet back to Samsung yesterday and they are going to attempt to fix it. It's still under warranty but I'll be pissed if I won't be able to install the new software on my tablet since I like the new updates they did for it.
Anyway, sorry for my long response but I hope this helps you out even though nothing was resolved. I'll post what happens once I get back my tablet.
Similar "Reboot after turn off" issue
I have the same "can't turn off" issue on my stock Tab 2 10.1 updated to 4.2.2 via Kies. After turning off and confirming on the screen, the tablet simply turns back on. This typically happens several times in a row before something happens and it stays off. I emailed Samsung to request support.
d86 said:
Hello,
I registered here to just answer your question since I've been searching around on the internet as well for this problem. I have a Samsung Galaxy Tab 2 10.1 with version 4.2.1. I updated to version 4.2.2 and all hell broke loose. Before I get into it, I had a perfectly working tablet that never had any problems. I installed all updates through OTA or Samsung Kies. It's not rooted.
Anyway, after the update to 4.2.2 my tablet wouldn't turn on. I had to plug it into the wall outlet and then it finally turned on. After playing around with it, some of the widgets didn't work so I thought maybe I should turn it off and reboot it. When I chose "power off" it wouldn't turn off. Instead it would automatically restart. After trying several attempts it still wouldn't turn off so I contacted Samsung. They made me clear the cache and then wipe out the whole system and install a fresh copy of the software. The tablet then went black and now all that was shown on the screen was the little android bot with the error message like how yours is now. It wouldn't boot up to the main screen anymore.
So I had to return the tablet back to Samsung yesterday and they are going to attempt to fix it. It's still under warranty but I'll be pissed if I won't be able to install the new software on my tablet since I like the new updates they did for it.
Anyway, sorry for my long response but I hope this helps you out even though nothing was resolved. I'll post what happens once I get back my tablet.
Click to expand...
Click to collapse
Reboot issues
avm1 said:
I have the same "can't turn off" issue on my stock Tab 2 10.1 updated to 4.2.2 via Kies. After turning off and confirming on the screen, the tablet simply turns back on. This typically happens several times in a row before something happens and it stays off. I emailed Samsung to request support.
Click to expand...
Click to collapse
I had a live chat with Samsung just now. It is interesting that the tech I communicated with did not know of any issue with the rebooting and there was no mention in their system that a problem even existed (so I sent a link to this page to him).
Anyway, the end result was that it I wanted to fix the problem, I would have to restore Android through KIES:
samsung.com/us/support/faq/FAQ00052690/61266/GT-P3113GRSXAR
This will delete all data and get back to Android 4.2.1
Since I have already have seen issues with KIES, I wonder if it wouldn't be easier to just use ODIN? Any suggestions from those who might have tried both?
update #1
Just wanted to give an update. Samsung sent me an email yesterday stating they "fixed" my tablet. I should be getting back my tablet by the end of this week or early next week. The receipt said that it was a "software problem" and they reinstalled new software with the latest update. I'm just wondering if it's 4.1.2(that worked fine with my tablet) or 4.2.2(which messed up my tablet)
I'll give another update once I get it in my possession.
---------- Post added at 05:33 PM ---------- Previous post was at 05:28 PM ----------
SamsungTab2User said:
I had a live chat with Samsung just now. It is interesting that the tech I communicated with did not know of any issue with the rebooting and there was no mention in their system that a problem even existed (so I sent a link to this page to him).
Anyway, the end result was that it I wanted to fix the problem, I would have to restore Android through KIES:
samsung.com/us/support/faq/FAQ00052690/61266/GT-P3113GRSXAR
This will delete all data and get back to Android 4.2.1
Since I have already have seen issues with KIES, I wonder if it wouldn't be easier to just use ODIN? Any suggestions from those who might have tried both?
Click to expand...
Click to collapse
I tried this when I chatted with Samsung and it messed up my tablet completely where as when I rebooted my tablet it would show an android robot with "error"
Plus, I don't know about you but I don't want to have 4.2.1. I want to have the 4.2.2 update on my tablet. It's a much more sleeker interface. Just the only problem is that it wouldn't shut off. I will see what happens once I have it. If 4.2.1 is on my tablet I will try again updating the software to 4.2.2.
There are some problems like boot fail or can't poweroff I've seen at some posts, they do the same things:
1.flash a 4.2.2 stock rom
2.have some problems: boot fail or can't poweroff eg..
3.boot to recovery and want to wipe the cache
4.get a error with the robot logo lie down
I found a post mentions that he've fixed this problem by using odin 3.07 flash the 4.2.2 stock rom with a matched kernel boot file.
The post is here, it's in chinese:
http://b.it168.com/thread-4690107-1-1.html
His solution is get to this site to find the 4.2.2 stock rom and matched kernel file of your device and use odin 3.07 flash them:
http://samsung-updates.com/
do it at your own risk maybe solve your problem.
Update #2
So I got my tablet today and I turned it on to see that it had android software 4.1.1. Then the software update icon popped up and I updated to 4.2.2. Then the same problem happened again like the last time. The tablet wouldn't turn off and it would automatically restart. I contacted Samsung Support again and they had me do a factory reset which then fried my tablet again. It doesn't turn on. So now I have to send it back again for a 2nd time. This time they said they may have to replace the tablet either with the same tablet or a different model tablet. But I stressed to them to make sure to update the tablet this time to 4.2.2 so they can see the problem I'm facing. We shall see next week I guess what happens.
Good evening all?
Ive unlocked my TF300T a year back and had been running Cyogenmod 10.1 on it for months, all worked fine.
As a recovery i had CWM installed and it worked like a charm as well.
A week ago i saw Cyogenmod 10.2 was out there and i wanted to switch the recovery to TWRP (i installed ver 2.6.x.x) and tried the new Cyogenmod.
It sisnt work so i wanted to switch back to 10.1 and CWM.
I dont exactly know what i did but in the end even the vol down and power button menu doesnt work anymore.
The tab turn on now and shows the Asus start screen but doesnt boot up.
Also when i press vol down and the power button it doesnt load the boot menu where i can install a new recovery and install the old Cyogenmod.
When its powered on i cant even turn of the tab, it keeps turning on for a few minutes in the Asus logo screen and than turn off and on again... till the battery is empty.
Did i brick my tablet ?
Are there any ways i can try to get the original software back?
Any help would be greatly appreciated.
Cheers !
Marty
Same situation with me....i think u have Hard Bricked your Tablet. The only option is Change the motherboard. So u need to send it to Asus..
Sent from my iris504Q using XDA Premium 4 mobile app
Did you update your bootloader to the JB one?
It IS Lupus said:
Did you update your bootloader to the JB one?
Click to expand...
Click to collapse
I think i didn't...
At first i just unlocked the device, installed recovery CWM and after a version (januari 2013) of Cyogenmod 10.1 wich was Android 4.2.2 and kept the Cyogenmod 10.1 up to date every few weeks... Thats all i did till i wanted to install Cyogenmod 10.2 (Android 4.3)
I can't recall updating the bootloader myself, could have been with an Asus update or something but i think i din't do it myself.
CM changed to the updated PITs when Asus updated first.
best solution would be to flash latest stock, boot into it once, flash twrp2 (2.6.0.0 works for me atm) then flash cm10.2
here is my summary
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
hope it helps
and no, i don't think you need to send it in for repair - it sounds more like broken PIT's so mount and boot points are not being recognized anymore.
gl
-Buster
Buster99 said:
CM changed to the updated PITs when Asus updated first.
best solution would be to flash latest stock, boot into it once, flash twrp2 (2.6.0.0 works for me atm) then flash cm10.2
here is my summary
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
hope it helps
and no, i don't think you need to send it in for repair - it sounds more like broken PIT's so mount and boot points are not being recognized anymore.
gl
-Buster
Click to expand...
Click to collapse
Thanks for your reply, how do i get to give fastboot commands when starting with volume down + power doesn't work anymore.
The only thing i have left is volume up + power to boor into APX mode and i cant seem to get the right usb driver for the TF300T
Cheers !
Tablet gets stuck on boot animation
I have a rooted asus tf300t and it will turn on but not get past the boot animation. I have tried to reset it using the bootloader but it will still not work. if anyone has any suggestions, i would like to hear them. i am a complete noob so please try to keep it simple. thanks
Tablet gets stuck on boot animation
I have a rooted asus tf300t and it will turn on but not get past the boot animation. I have tried to reset it using the bootloader but it will still not work. if anyone has any suggestions, i would like to hear them. i am a complete noob so please try to keep it simple. thanks
geronphillips said:
I have a rooted asus tf300t and it will turn on but not get past the boot animation. I have tried to reset it using the bootloader but it will still not work. if anyone has any suggestions, i would like to hear them. i am a complete noob so please try to keep it simple. thanks
Click to expand...
Click to collapse
More details will be needed before someone can help. What had you done right before it acted up? What rom do you have in there ATM? Can you post a picture or tell what's on the initial screen (the one before the boot animation)? Did you try volume down + power? If you did, what did the screen show?
graphdarnell said:
More details will be needed before someone can help. What had you done right before it acted up? What rom do you have in there ATM? Can you post a picture or tell what's on the initial screen (the one before the boot animation)? Did you try volume down + power? If you did, what did the screen show?
Click to expand...
Click to collapse
I rooted my device using the method shown on this page
http://forum.xda-developers.com/showthread.php?t=2228613I
, the ROM is stock and the screen before the animation is normal (white Asus text). I have tried volume down and power and from that screen, I reset my tablet. This didn't solve the issue, before this started, I changed the boot animation and changed fonts. I think it was while restarting after the font change that it stopped booting properly.
geronphillips said:
I rooted my device using the method shown on this page
http://forum.xda-developers.com/showthread.php?t=2228613I
, the ROM is stock and the screen before the animation is normal (white Asus text). I have tried volume down and power and from that screen, I reset my tablet. This didn't solve the issue, before this started, I changed the boot animation and changed fonts. I think it was while restarting after the font change that it stopped booting properly.
Click to expand...
Click to collapse
I gather by "reset my tablet", you meant you cold booted it by selecting the android icon. This being the case, you can always reflash the stock ROM with fastboot. Depending on whether you had 4.1 or 4.2 bootloader - 4.1 has 4 icons including a USB icon which if clicked, will make the tab enter fastboot/download mode; 4.2 will enter that mode automatically as you press volume down+power - you need to choose the right ROM you want to install. The initial screen should tell you which bootloader on the top left corner. 4.1 matches stock Roms commencing with 10.4.x.xx; 4.2 is Roms with 10.6.x.xx
I've flashed a 4.1 ROM (104220) on a tab with 4.2 bootloader by means of an external SD card without problems. However, to be safe, you should flash whatever version you'd had before the incident. If you already have data on the tab that you care to keep, you shouldn't touch the wipe date icon. If you need a link as to what to do, read this one. Good luck.