hello, I rooted my asus padfone x with towelroot v1 a few days back, everything went fine. Earlier today I installed a a program ( I cant remember the name of it but will post as soon as I remember) and changed my boot logo successfully twice. When I wasn't satisfied with the boot logo I changed it again and reset to see it in action. So when I powered the device on it shows the asus pre-boot logo, then shows the boot logo I chose briefly then plays the at&t startup sound, but then just sits at a black screen. iv tried going into recovery mode and resetting back to factory defaults then reset but nothing but the same problem as before. I did make a backup with nandroid (I think its called) that I have stored on my asus pc running windows 8. Im not sure what to do, and now I feel like a dumb ass for not taking better precautions.. Any help would be greatly appreciated!! Thanks again,
Best regards,
Mike
Muzzler said:
hello, I rooted my asus padfone x with towelroot v1 a few days back, everything went fine. Earlier today I installed a a program ( I cant remember the name of it but will post as soon as I remember) and changed my boot logo successfully twice. When I wasn't satisfied with the boot logo I changed it again and reset to see it in action. So when I powered the device on it shows the asus pre-boot logo, then shows the boot logo I chose briefly then plays the at&t startup sound, but then just sits at a black screen. iv tried going into recovery mode and resetting back to factory defaults then reset but nothing but the same problem as before. I did make a backup with nandroid (I think its called) that I have stored on my asus pc running windows 8. Im not sure what to do, and now I feel like a dumb ass for not taking better precautions.. Any help would be greatly appreciated!! Thanks again,
Best regards,
Mike
Click to expand...
Click to collapse
Hello Mike,
I have a few suggestions that may help. If the program you are using does not require your Padfone X to be completely powered on, I would recommend changing your boot logo back to a previous version. If that does not work, I would proceed to enter recovery and restore your backup. Some recoveries allow you to restore from the SDcard, so I recommend placing the nandroid from your computer onto the SDcard. If you need further support please feel free to email me at [email protected]. Include case number N140731704 in the subject line.
Warm regards,
Scott
ASUS Customer Loyalty
[SOLVED]
[email protected] said:
Hello Mike,
I have a few suggestions that may help. If the program you are using does not require your Padfone X to be completely powered on, I would recommend changing your boot logo back to a previous version. If that does not work, I would proceed to enter recovery and restore your backup. Some recoveries allow you to restore from the SDcard, so I recommend placing the nandroid from your computer onto the SDcard. If you need further support please feel free to email me at [email protected]. Include case number N140731704 in the subject line.
Warm regards,
Scott
ASUS Customer Loyalty
Click to expand...
Click to collapse
hi scott, thanks for the reply. So last night before bed I looked at my phone pissed off and wasn't going to throw it on the charger. So before bed I plugged it into the tablet to charge, and that's were things got interesting.... so apparently the tablet portion has its own chip set that remembers things like boot logo. What I did was plug it into the tablet, then it displayed a battery logo to show that it was charging. So I held dow the power button until the phone tablet combo turned on, and to my surprise the original boot logo from at&t was shown and let me back into my phone. So from there I went back into my boot logo changer and changed it back to one that I know works. So now my phone is back to were it was thank god!!
Muzzler said:
hi scott, thanks for the reply. So last night before bed I looked at my phone pissed off and wasn't going to throw it on the charger. So before bed I plugged it into the tablet to charge, and that's were things got interesting.... so apparently the tablet portion has its own chip set that remembers things like boot logo. What I did was plug it into the tablet, then it displayed a battery logo to show that it was charging. So I held dow the power button until the phone tablet combo turned on, and to my surprise the original boot logo from at&t was shown and let me back into my phone. So from there I went back into my boot logo changer and changed it back to one that I know works. So now my phone is back to were it was thank god!!
Click to expand...
Click to collapse
I am happy to hear you were able to get back up and running.
Regards,
Scott
ASUS Customer Loyalty
Related
I've tried to look for this problem and haven't found anything similar. If it's already been addressed please direct me to the previous thread, if this is in the wrong place please move it.
I rooted my Galaxy S II a while ago and it's been working great. I wanted to try Cyanogen mod 7 and so I followed the instructions on their website. Trying to use ROM manager gave me a weird error message telling me that there was an invalid signature or something, despite toggling everything and wiping the cache to turn it off. So I followed the "method via recovery" instructions. I did everything exactly as it is there, including the Google apps stuff, and it all seemed to work perfectly. Then I rebooted it hoping for it to boot into CM7, and instead, when it turns on it goes to the screen saying Samsung Galaxy S II with the yellow triangle underneath, and stays there. Every time it turn it on it goes to that screen and doesn't change. It's now been like that for half an hour. I can start it up into download mode, and I've tried flashing zImage to it again, but no change.
I have a NANDroid backup (it's backed up with CWM anyway), and I've copied the backup to my computer, but I have no idea how to apply it when the bloody thing won't turn on.
I'm using Linux with Heimdall (the cross-platform Odin clone).
Please help me. Unfortunately I have no internet in my flat so I won't be able to see any advice until tomorrow unless it;s given in the next ten minutes. God I really hope the thing's ok.
Hi
Do you have jigg? ( if you don't have it buy it from ebay or ask some friend of you )
With jigg you can enter download mode and then flash the stock rom.
Pull battery, wait 10s, then boot while holding power+vol-up+home. This should get you in recovery. Then restore nandroid.
Sent from my Transformer TF101 using xda premium
TheGhost1233 said:
Pull battery, wait 10s, then boot while holding power+vol-up+home. This should get you in recovery. Then restore nandroid.
Click to expand...
Click to collapse
I can't believe it was this simple, I knew power+vol-down+home got tme to downloading but I didn't know that got me into recovery. Everything's recovered now.
Thank you Dutch people!
I received a G Tablet which had been used for development work for a few months. The person giving it to me (not the dev who has left) said the tablet was working fine, but had just become frozen at a reboot after he had tried to erase personal data from the tablet. I asked him if he had erased the sd card and he said "maybe" but that he couldn't remember. I powered the tablet on and sure enough it displayed two lines on a black background, one of which said something like loading kernel.
Now, these tablets were all rooted, and had Android 2.3 on them, via one of the ROMs discussed here. I don't know which one however.
So, I tried using NVflash to flash the tablet back to a stock ROM. Tablet then got stuck in a boot loop; I would see the Viewsonic logo, then the G Tablet logo, and then this would go on forever.
So I shut it down and tried again. This time Nvflash failed almost at the last step after having written most of the image.
And so here I am now, with a totally dead tablet. I cannot power it on. No combination of power or volume up/down buttons work. The only sign of life is when I plug it into its charger, and see the charging light come on.
I confirmed again with the person who gave me the tablet that the device was working just fine before it froze at a reboot after his erasing attempts.
Is there a way out of this? I hope so. Please help!
Thanks very much
Paul
texnote said:
I received a G Tablet which had been used for development work for a few months. The person giving it to me (not the dev who has left) said the tablet was working fine, but had just become frozen at a reboot after he had tried to erase personal data from the tablet. I asked him if he had erased the sd card and he said "maybe" but that he couldn't remember. I powered the tablet on and sure enough it displayed two lines on a black background, one of which said something like loading kernel.
Now, these tablets were all rooted, and had Android 2.3 on them, via one of the ROMs discussed here. I don't know which one however.
So, I tried using NVflash to flash the tablet back to a stock ROM. Tablet then got stuck in a boot loop; I would see the Viewsonic logo, then the G Tablet logo, and then this would go on forever.
So I shut it down and tried again. This time Nvflash failed almost at the last step after having written most of the image.
And so here I am now, with a totally dead tablet. I cannot power it on. No combination of power or volume up/down buttons work. The only sign of life is when I plug it into its charger, and see the charging light come on.
I confirmed again with the person who gave me the tablet that the device was working just fine before it froze at a reboot after his erasing attempts.
Is there a way out of this? I hope so. Please help!
Thanks very much
Paul
Click to expand...
Click to collapse
I would try popping it open and unplugging the internal battery then plugging it back in. Also hit the internal reset button while you're in there. It's pretty hard to actually kill one of these tablets. PM me if you need any other help.
help
Started my own thread, didnt mean to hijack. =)
Thanks, I will try removing the battery and let you know.
As for NVflash, I believe the latest version is here:
http://www.slatedroid.com/topic/171...-using-either-11-or-12-based-images-g-tablet/
However in my case I have no idea whether I have 1.1 or 1.2 and there is no way to determine this. Which one should I choose?
Paul
Doesn't matter for NVFlash, just download all of the flash files again because it might be that you have a bad download. Also make sure you have the right drivers installed since the drivers that automatically install when you plug it in sometimes don't work.
I'm pretty sure that if it boots past the birds, the hardware is working okay, so you should run the FORMAT version for NVFlash and then I'd run just a CWM flash setup and see if you can get into CWM and delete the partitions from within that.
The best thing to flash as far as ROMs would be Bekit's 1105 which is stock OTB with a few key changes. If you can't get the 1105 to play nice, you might really have some hardware problems.
I would go with the 1.2 BL, it will give you access to the newer roms as it appears that dev for the 1.1 BL seems to be dwindeling. I upgraded mine to 1.2 the other day and it worked great.
I have little hope for this, but thought I'd post it up anyway before buying a new phone. I have been using the JellyBomb ROM for about two weeks now, and until today it was working fine. Then (seemingly) randomly, while I was browsing a webpage in Firefox, the phone locked up.
"Okay, I'll just force a hard reboot." So I held down the power button and it turned off. When I turned it back on, it got stuck at the HTC screen (I let it sit for about 15 minutes). So I did another hard reboot and booted into bootloader (power + vol down), which came up fine. I went into recovery (TWRP 2.3), which took about 5-10 minutes to move past the TEAMWIN splash screen into the menu.
Once in the menu, I went to reflash the ROM, but no files showed up in either the internal or external storage which I found strange. I then went to reboot from the menu, at which point TWRP informed me that I had no OS installed. At that point, TWRP froze up, so I did a hard power off again and tried to boot it back into recovery but nothing happened. The soft buttons didn't even flash like usual.
Once I had access to my computer, I plugged it in, hoping that something would change with it connected to a PC. At that point, the Windows driver manager reported failure at installing a driver. I checked device manager to see that I had a QHUSB-DLOAD device connected. After some Googling, I attempted Unlimited.IO's fix tool (using a Linux live CD, obviously). I had little hope, however, because my device was S-ON. And sure enough, although the tool reported completion there was no change to the phone.
So, now that that long-winded (and hopefully sufficiently detailed) story is complete, does anyone have any suggestions/advice/instructions for me?
Thanks!
elead1 said:
I have little hope for this, but thought I'd post it up anyway before buying a new phone. I have been using the JellyBomb ROM for about two weeks now, and until today it was working fine. Then (seemingly) randomly, while I was browsing a webpage in Firefox, the phone locked up.
"Okay, I'll just force a hard reboot." So I held down the power button and it turned off. When I turned it back on, it got stuck at the HTC screen (I let it sit for about 15 minutes). So I did another hard reboot and booted into bootloader (power + vol down), which came up fine. I went into recovery (TWRP 2.3), which took about 5-10 minutes to move past the TEAMWIN splash screen into the menu.
Once in the menu, I went to reflash the ROM, but no files showed up in either the internal or external storage which I found strange. I then went to reboot from the menu, at which point TWRP informed me that I had no OS installed. At that point, TWRP froze up, so I did a hard power off again and tried to boot it back into recovery but nothing happened. The soft buttons didn't even flash like usual.
Once I had access to my computer, I plugged it in, hoping that something would change with it connected to a PC. At that point, the Windows driver manager reported failure at installing a driver. I checked device manager to see that I had a QHUSB-DLOAD device connected. After some Googling, I attempted Unlimited.IO's fix tool (using a Linux live CD, obviously). I had little hope, however, because my device was S-ON. And sure enough, although the tool reported completion there was no change to the phone.
So, now that that long-winded (and hopefully sufficiently detailed) story is complete, does anyone have any suggestions/advice/instructions for me?
Thanks!
Click to expand...
Click to collapse
Hey elead got your pm and I'm sorry this has occurred to you. I'm not familiar with the unlimited IO. But I will suggest that you allow your phone to charge tonight while its off... The reason for this is I believe the battery has fallen to a level such that will not allow the boot process to work... Having said that allow it to charge the night... Then see if it will boot into bootloader in the morning. If it does this you should be able to flash an ruu. I realize this is a stressful time, I've been in your shoes before and actually bricked. BUT, I believe your phone is salvalgeable and with a proper charge you be able to fix the issue... Please report back in the morning and let me know... Ok??
VeNuM said:
Hey elead got your pm and I'm sorry this has occurred to you. I'm not familiar with the unlimited IO. But I will suggest that you allow your phone to charge tonight while its off... The reason for this is I believe the battery has fallen to a level such that will not allow the boot process to work... Having said that allow it to charge the night... Then see if it will boot into bootloader in the morning. If it does this you should be able to flash an ruu. I realize this is a stressful time, I've been in your shoes before and actually bricked. BUT, I believe your phone is salvalgeable and with a proper charge you be able to fix the issue... Please report back in the morning and let me know... Ok??
Click to expand...
Click to collapse
I will post back with results. Not like I've got much else to do with it right now, eh? :laugh:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
elead1 said:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
Click to expand...
Click to collapse
Damn. Well I've been there done that too...
send it to htc.
elead1 said:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
Click to expand...
Click to collapse
i had the same problem but my situation was that i downgraded the radio while s-on. I was in the same situation that you are right now. i did everything i could but nothing worked so my last hope was sending it to HTC and say that i lefted updating the software while sleeping and when i woke up it was like that. i sended they didnt even ask, i got it back like new . :laugh:
I got my TF201 back yesterday from Asus after 1-2 months after I sent it in to see if anything can be done about the cracked screen issue... nothing.
The first thing I did when I got it back was update apps, backup apps, and then I decided to install 'AndroWook Prime Hairy Bean', so I downloaded it onto my Prime, went into ROM Manager, found an update for ClockworkMod, which I installed. I then proceeded to select the ROM to be installed, ticked back up current rom (Cyanogenmod 10 Unofficial), and wipe data, and clicked enter.
When I opened up recovery, it came up with TWRP, and did nothing, so I went to backup my ROM but didn't have enough data.
I tried to re-install an older ClockworkMod as I prefer it, and tried to connect with fastboot, and then followed instructions, but got a bit lost... (I'm 13..) Tried again, failed..
This bit is a bit of a blur, but I believe I tried to open up Recovery again, didn't work so I loaded up an app (Transformer reboot to Recovery), which hung on loading up recovery, did Vol-Down and rebooted..
I think it was then that it displayed the Splash Screen and hung, with 'The Device is UnLocked.' in the top left corner, ASUS logo in centre and NVidia Tegra bottom right..
Researched online and found no results.. I don't have NVFlash, but I'm curious as to whether this will work: androidroot .mobi/2012/05/27/introducing-wheelie-nvflash-for-asus-transformer-tf101-b70 as my laptop displays APX.
I appreciate any responses, this is all so daunting for me and I don't know what to do..
Xayko said:
I got my TF201 back yesterday from Asus after 1-2 months after I sent it in to see if anything can be done about the cracked screen issue... nothing.
The first thing I did when I got it back was update apps, backup apps, and then I decided to install 'AndroWook Prime Hairy Bean', so I downloaded it onto my Prime, went into ROM Manager, found an update for ClockworkMod, which I installed. I then proceeded to select the ROM to be installed, ticked back up current rom (Cyanogenmod 10 Unofficial), and wipe data, and clicked enter.
When I opened up recovery, it came up with TWRP, and did nothing, so I went to backup my ROM but didn't have enough data.
I tried to re-install an older ClockworkMod as I prefer it, and tried to connect with fastboot, and then followed instructions, but got a bit lost... (I'm 13..) Tried again, failed..
This bit is a bit of a blur, but I believe I tried to open up Recovery again, didn't work so I loaded up an app (Transformer reboot to Recovery), which hung on loading up recovery, did Vol-Down and rebooted..
I think it was then that it displayed the Splash Screen and hung, with 'The Device is UnLocked.' in the top left corner, ASUS logo in centre and NVidia Tegra bottom right..
Researched online and found no results.. I don't have NVFlash, but I'm curious as to whether this will work: androidroot .mobi/2012/05/27/introducing-wheelie-nvflash-for-asus-transformer-tf101-b70 as my laptop displays APX.
I appreciate any responses, this is all so daunting for me and I don't know what to do..
Click to expand...
Click to collapse
I don't like the sound of this. If you flashed an ICS recovery on there (which I think you have with clockworkmod) after having the jellybean bootloader on there (which I think you do because nVidia logo is bottom right) then you might be hard bricked.
Hold down power and volume down for 10 seconds when off. If you do not get to the screen with icons on like usb icon and wipe icon and you cannot enter recovery then I'm afraid you are hard bricked.
Thanks... *curls up into a ball and cries to death* What can I do now? Anywhere I can sell it or what..?
Did you have any luck getting to fastboot? If you failed flashing clockworkmod you might still have a chance.
Not that I know of.. just recognises APX on laptop..
Looks like you are hard bricked. As you said you don't have NVFlash so APX mode is unusable for you (you have to have files generated just for your device to be able to use APX).
If you could get into fastboot, you could have change of fixing it.
You can send it to Asus to have it fixed and pay for it ~260$ I think - look somewhere on Q&A forum, or sell it as bricked to someone who has broken his screen on ebay (or other site). Or you can have it as pretty expensive paper weight, sorry.
I did the exact same thing you did man. Was looking for an answer when I saw this thread...lol
EDIT: Also what is APX? Just got my Prime last week haha
I really hate to hear that this happened to you guys. FYI: a bricked Prime usually goes for between 150 and 200 bucks on eBay, depending on its condition.
I know that's not fantastic news, but at least you could put that towards a new tablet.
Or you could naturally pay Asus to repair it.
Sent from my Galaxy Note 2
Same thing happened to me yesterday..I have switched from custom rom to stock JB .17 then I decided to move to new Androwook Prime 1.51
I did
1. Prime Full wipe
2. Installed Androwook hairy Bean 1.51
FYI - I can still access both TWRP and Fastboot..Im on JB bootloader
When I rebooted Im Stuck at Splash Screen Any Ideas?? Thanks In Advance
Here is my log
http://tny.cz/2d399fb7
mercydia said:
Same thing happened to me yesterday..I have switched from custom rom to stock JB .17 then I decided to move to new Androwook Prime 1.51
I did
1. Prime Full wipe
2. Installed Androwook hairy Bean 1.51
FYI - I can still access both TWRP and Fastboot..Im on JB bootloader
When I rebooted Im Stuck at Splash Screen Any Ideas?? Thanks In Advance
Here is my log
http://tny.cz/2d399fb7
Click to expand...
Click to collapse
Just try installing it again straight over the top.
flumpster said:
Just try installing it again straight over the top.
Click to expand...
Click to collapse
I just unlocked and installed Androwook1.51 last night. No problems once I realized I had to wipe data since my prime had been encrypted under stock 4.1.1 But I figured that as long as I could get into TWRP I was probably OK, right?
Dai323 said:
I really hate to hear that this happened to you guys. FYI: a bricked Prime usually goes for between 150 and 200 bucks on eBay, depending on its condition.
I know that's not fantastic news, but at least you could put that towards a new tablet.
Or you could naturally pay Asus to repair it.
Click to expand...
Click to collapse
Oh.. It has suffered from the cracked screen issue and I've broken the Micro HDMI slot by tripping over the wire :L
How much would it cost for those two to be fixed, along with the splash screen issue?
I'm new to the andriod side of things but am very computer savy. Can someone please help? My son has this nextbook tablet and today when he turned it on, it hangs up on the second boot image. I went into recovery but didn't want to restore to factory just yet if i didn't have too. I've read so much i am confused. We have four boys, so that means we have four of these tablet, since Christmass. This is the only one not booting for whateer reason now. What can I do? Can i pull image from one of the others and install n this one, or just certan boot files? Please help and thank you for any reply.
Grwx4dad said:
I'm new to the andriod side of things but am very computer savy. Can someone please help? My son has this nextbook tablet and today when he turned it on, it hangs up on the second boot image. I went into recovery but didn't want to restore to factory just yet if i didn't have too. I've read so much i am confused. We have four boys, so that means we have four of these tablet, since Christmass. This is the only one not booting for whateer reason now. What can I do? Can i pull image from one of the others and install n this one, or just certan boot files? Please help and thank you for any reply.
Click to expand...
Click to collapse
I had the same problem with my next 7 premium se 8gig.
Pop your sd card in.
Boot into recovery mode by pressing the power button and the volume down button at the same time.
When recovery comes up, delete the media partition, clear your cache and restore to factory settings.
Choose the option to restart the tablet.
Once it boots it should be back to life though you will lose everything on it.
Beats having a useless tablet though.
It took me only a few hours to reload all my apps and she's been running fine since.
Good Luck.
I got it to go to recover but once at recovery it says upgrading please wait and sits their.
Exact same issue...
Any luck in resolving this yet? I have google for 16 hrs so far, and tried countless methods of restoring my tablet to it's previous glory...
Any help is much appreciated. :fingers-crossed:
sd card
you mention an sd card,where do i get such an sd card?
scarsfromknives said:
I had the same problem with my next 7 premium se 8gig.
Pop your sd card in.
Boot into recovery mode by pressing the power button and the volume down button at the same time.
When recovery comes up, delete the media partition, clear your cache and restore to factory settings.
Choose the option to restart the tablet.
Once it boots it should be back to life though you will lose everything on it.
Beats having a useless tablet though.
It took me only a few hours to reload all my apps and she's been running fine since.
Good Luck.
Click to expand...
Click to collapse