[Q] problem ics stuck at asus logo - Eee Pad Transformer Q&A, Help & Troubleshooting

I'm still stuck at the Asus eee pad screen and I didn't find a solution for it yet.
did the superwipe and I tried different roms,search in every topic.
I use the correct cwm 3.2.0.1
its driving me mad!Please help!!

How long are you waiting on booting?
Wipe everything, load rom, fix permissions and boot then give it 5 minutes...
Try gnufabios ics rom and watch the progress... does is say completed?

I did a superwipe and fixed permission,I have tryed the revolution rom and the standard with root.
after complete i did a reboot then you see the green bar then it reboots again and I wait for more then half a hour..
why is this happening to me things never go smooth ...

Perhaps try loading this one
http://uploading.com/files/1973838a/us-8.6.5.21-CWM-full-unrooted.zip/
Make sure the power is plugged in.
Hang in there champ, there's a solution somewhere.

thanks! I will try it later on.
hoop it works..
and if it don't do you have some other ideas? ?

I suppose more info would help.
What did you have before ? Revolver? Prime? Stock rooted rom?
If stock ROM, which version?
And which ROM did you try first when the problems started?
Ps: I'm no expert just read a lot of these threads and flashed a few Roms.

at first I had revolver 3.11 (hc) and the first ics rom I tried was the us stock rooted full (option b). I have tried different mirrors.

c-greg said:
I did a superwipe and fixed permission,I have tryed the revolution rom and the standard with root.
after complete i did a reboot then you see the green bar then it reboots again and I wait for more then half a hour..
why is this happening to me things never go smooth ...
Click to expand...
Click to collapse
same thing happened to me too,since the update two times surprisingly i noticed my screen stucked at the Asus logo,i dont know why its so,it looks some issue there in the stability,
but anyway i just did a cold reboot by holding down the volume down button and the power button simuteneously untill cwm options appears on the left corner as well two images on the center then release the buttons,after few seconds the system will reboot normally.
sorry for my poor english...

that sounds like a different problem because you passed the installation process and the system just reboots (there are other with the same problem)I on the other hand am still stuck before that

just try going back to recovery and manually wiping rather than using super wipe - reflash the rom and reboot - dont fix permissions either.

sorry did that already. then people said superwipe is the solution but that didn't work either ..maybe I'm the only one....

Had the same Problem Yesterday.. - with a Restore from a CWM Backup..
Always Stuck @ the EEE PAD Screen.. - Tried Permissions, Wipe Cache, Old Backups etc. but the PAD never Boot..
After this i Flashed "Revolution ICS" and the Problem was gone.. - donĀ“t know why. Maybe the Kernel?!

can you get back to another rom or base?
how much free disk space do you have?

Yes I can i'am now still on revolver 3.11 hc..
Tried the revolution HD rom didn't. Work either.
Very strange.......

try flashing the stock ww full rom with root first to give you an ics base.....
is it rogue recovery you have? if not flash it first and then try working from internal sd.
otherwise im not sure what else to suggest.

I don't know what roque recovery is...

I will try the roque method and some different roms will be back later on..
Sent from my Nexus One using XDA App

Is it normal that while flashing a rom in cwm the bar won't move?it just stays gray..and then complete....
Sent from my Nexus One using XDA App

Yes, thats normals.. Happens every Time here
I tried both Recoverys (Roque and Roach) was always the same ... - Hope Roque Recovery Helps you..
Flashed from External or Internal SD? Try Flashing from Internal so you know your External SD is not corrupt.. - You can flash from Internal only from Roque btw.

I'm getting sick and tired. Even roque won't work flashing it from internal..how long does it normally take to get past the eeepad logo??
Sent from my Nexus One using XDA App

Related

[Q] Boot loop or Brick? HELP?

GOT IT FIXED
Thanks to fabricatedhero for the brain pulse to try and just root it!
First this isnt my G2X, I am trying to help a co-worker. She isnt Tech-savy by any means... lol... any way here is her story:
She got the OTA pop-up and thought it was a virus (yeah shes that smart) then she said she accepted the update as it kept asking. She started the update and it took hours over night and it never finished she said so she pulled the battery durring the s/w update screen. Then it started the boot loop.
Now my story:
The G2x is bone-stock
I did the NVflash successfully... Flashed the stock recovery via:http://forum.xda-developers.com/showthread.php?t=1056847 ... Still have the boot loop issue and wont boot into recovery. I searched and even Googled and everything is the same, and of which nothign is working for me.
I tried to maybe catch something from the boop loop and also from the S/W update screen... NOTHING... Clearly this is software issue; The only thing I have yet to confirm is if I place the stock update on sd card and see if itll pick that up.
The issue I see there is I cant google for the life of me what the "special" name of the update would be called. Nor do I have a clue what to really call it. I know for most phones its NOT "update.zip" more like "espring13" or somethign like that...
Can any Jedi MAster help me? Thanks!
ok found the file name:
LG-P999-V10f.zip
Still boot-looping and that didnt work...
resources
http://theunlockr.com/2011/05/23/how-to-unroot-the-t-mobile-g2x/
Use. The nvflasher to put Cwm on it and go under restore and re-format sd, cache, and etc
Then go and do gummans froyo 2.2 stock rooted rom
Also there's a post about how to do the GB update on here as well.
Sent from my LG-P999 using XDA Premium App
Did you try a simple factory reset? If you still have stock recovery and rom try holding volume up + power until the reset process begins.
G2X CM7
So I will have to root the device? I guess that makes sense...
Keep in mind I cant get into stock recovery period...
cwm worked! wipped everything, still nothing, gonna flash a new rom
update:
ok SDcard doesnt show have to mount internal storage to apply update... *crosses fingers*
**worked running newest nightly of CM7 with CWM recovery

CWM partially flashed/some glitches?

My brother got tired of all the bloatware on his G2x with 2.3.3 OTA, so I proceeded to try to flash a custom ROM. Did the process of NVFlash, but with some unexpected results:
1) As I'm lead to believe, I should see an orange "ANDROID" show up when holding volume down and power. But instead I get a green "ANDROID" with a bunch of Android icons like messaging.
2) When it gets past the screen I mentioned, it does go into CWM Recovery but as soon as I let go of a button to navigate, the phone shuts off. Sometimes it stays on if, while still holding down volume and power, I press volume up, release down, then release power. Even then, it sometimes still shuts off.
3) When trying to flash a rooted ROM (CyanogenMod 7.1, after doing a data wipe/factory reset), I get an error message and the installation aborts.
Was able to restore the 2.3.3. OTA because I had backed up, but any ideas?
I am no expert but I would start over from scrach. Rinse and Repeat. it sounds like it did not install right.
Are you sure you flashed the CWM for the G2X? If you flashed the wrong recovery all kinds of problems, such as you described, could occur. Good thing you had the backup.
mojorisin7178 said:
I am no expert but I would start over from scrach. Rinse and Repeat. it sounds like it did not install right.
Click to expand...
Click to collapse
Would you recommend I reflash CWM straight up, or the stock recovery through NVFlash before trying again? I'd assume I should follow all the same steps as if I was trying to flash CWM, but instead of clicking on CWM, click stock recovery instead.
jboxer said:
Are you sure you flashed the CWM for the G2X? If you flashed the wrong recovery all kinds of problems, such as you described, could occur. Good thing you had the backup.
Click to expand...
Click to collapse
Positive. I downloaded the necessary files and followed all the steps from here:
http://forum.xda-developers.com/showthread.php?t=1056847
Again I am no expert but that sounds like a good idea i would say you it cant hurt. I think you will have to reflash cwm but you have to do that anyway so I would say it is the best way to start clean.
Got CWM Recovery to work. It still shows the green ANDROID with the icons, but I no longer have to struggle to keep it from shutting off. I was able to flash xboarder's tweaked Gingerbread ROM, but still unable to flash CyanogenMod 7.1. I did a factory/wipe data, wiped cache, and dalvik cache. Still get an error message upon trying to install.
when i first did the nvflash my phone was getting shut off when it got to the recovery and then i let go of the power button. Until i realized that you are supposed to let go of the power/volume button when the word android appears and all those icons u mentioned, yeah i get the same screen. i had no problems flashing 3 builds of cm7 and xboarder's rom 2 times.
Not sure what's going on with the CM 7.1RC but I was able to flash the latest EaglesBlood ROM this mornibg and he's really enjoying it so far. Thanks for all the help!
Sent from my HTC Glacier using XDA App
The green android with the icons is just a different splash screen in the newer version of cwm.
lcambriz said:
Not sure what's going on with the CM 7.1RC but I was able to flash the latest EaglesBlood ROM this mornibg and he's really enjoying it so far. Thanks for all the help!
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Could've been a bad download. Sometimes you just gotta download the file again and it'll flash no issues.
But I'd go for the latest CM7 nightly. They are leaps and bounds ahead of where they were with RC1.
I figured that might be the problem. Eaglesbood seems to be working really well for him, so I think he'll just stick with that. My bro is more of the "If it isn't broken, don't fix it" type, whereas I'm more inclined to try the latest. I'm tempted to try the nightlies myself on my Glacier, if they really are better than RC1.
Sent from my HTC Glacier using XDA Premium

HELP

installed a custom rom = ''http://forum.xda-developers.com/showthread.php?t=1198684''
works fine , then installed "LeeDroid 3.1.0 Kernel "
and all of a sudden my phone just stays on HTC white and green screeen :/
dont know what to do tried installing other kernels but all have the same effect stays on HTC screen for minutes
give it al least 10 to 15 mins, before u jump to conclusion, it always takes a while when you first flash!
Just give it time,
ok ok thanks i will
Its been about 30 mins and still just the HTC screen CAN ANYONE help me!
It has been 16 minutes, not 30.
Be patient. Try reflashing if you can get to recovery.
Sent from my GT-I9100 using XDA App
Warchief337 said:
Its been about 30 mins and still just the HTC screen CAN ANYONE help me!
Click to expand...
Click to collapse
It's a bad flash or won't work on your device. Flashing a kernel with a speed to high for your CPU can do that, for example. Do a restore via recovery or try and flash a different version of that kernel or a different kernel.
no its been 30 i let it stay on that screen for a whole game of dota lol i just had it on my laptop while i played and it stayed white and HTC the entire time
oh ok ill try that , im new to the rooted phone scene was just using revolution hd but i like the insertcoin version better ill try another kernel
Firstly custom kernals dont work with sense 3.5 roms, that could be your problem, wipe everything in recovery, data wipe, factory reset, go to advanced and wipe dalvik cache, then just install the rom and see what happens, or else restore (assuming you made a backup)
ok so i wiped and reloaded rom and we are in business thanks everyone for your help DDDDD hahaha im releived
Warchief337 said:
ok so i wiped and reloaded rom and we are in business thanks everyone for your help DDDDD hahaha im releived
Click to expand...
Click to collapse
You will most likely run into it again in your flashing future (the stuck boot screen). It doesn't always require a full wipe or restore to fix. You could have most likely fixed it by flashing the kernel that came with the ROM.
The easiest thing you can do for yourself is to always make a nandroid backup before flashing anything, even a theme. Just remember to delete old backups you know you won't use, they take up a lot of sdcard space.
digiholic said:
You will most likely run into it again in your flashing future (the stuck boot screen). It doesn't always require a full wipe or restore to fix. You could have most likely fixed it by flashing the kernel that came with the ROM.
The easiest thing you can do for yourself is to always make a nandroid backup before flashing anything, even a theme. Just remember to delete old backups you know you won't use, they take up a lot of sdcard space.
Click to expand...
Click to collapse
thaey sure do take a lot of space. when I do an nandroid backup it always saves the rom with the date. can i rename it so I can keep them all straight? THis is a very NOOB question

[Q]Stuck on "Android is Upgrading - Installing Applications" Screen. Any Ideas?

[Q]Stuck on "Android is Upgrading - Installing Applications" Screen. Any Ideas?
Hi all.
Since 3 days I can't use my Transformer, and everytime I think I fixed an issue, there's another appearing.
At the beginning I was on Mike 1986's AR HD 3.0.1 Rom. Everything went well for like a week. And a morning pressed on the power button, as usual, and tried to slide the lock circle to the small lock icon. Nothing moved. Then I thougt "Perhaps my fingers are cold" I heated them, and nothing changed. I connected my Tab to the dock, and I could mysteriously still use the trackpad.
I rebooted it, still the same problem.
Wiped it and reinstalled ARHD, still the same problem.
Then I tried the NVFlashable stock ICS Rom, and there appeared the problem : The Asus loading screen appeared and stayed... For hours...
Then I re-rooted my tablet, wiped it, and installed the CWM- Flashable ICS. Oh my god! I went further than before! First the asus loading screen : Passed ; Then the "Android is Upgrading - Applying updates" screen - passed; Now I'm stuck on the "Android is Upgrading - Installing Applications" screen.
I'm getting mad!!!
Could someone help me? Is there a solution? Is my TF101 hard bricked? Could I mask the root and so on to send it on RMA ( Final Solution!) ?
Please help me... I read on the prime's forum that flashing a stock Rom after having a custom Kernel wasn't good... The blobs aren't up to date then...
DerSandmann said:
Please help me... I read on the prime's forum that flashing a stock Rom after having a custom Kernel wasn't good... The blobs aren't up to date then...
Click to expand...
Click to collapse
There's no "custom" kernel right now with ICS. Not sure what to tell you, usually an NVFLash would wipe everything and have a "clean" install.
baseballfanz said:
There's no "custom" kernel right now with ICS. Not sure what to tell you, usually an NVFLash would wipe everything and have a "clean" install.
Click to expand...
Click to collapse
+1. You could try doing a restore to true stock by going here
http://forum.xda-developers.com/showthread.php?t=1154947
But usually nvflash or return to true stock fixes most things. If you are still having troubles, bite the bullet and do a RMA.
There's no "custom" kernel right now with ICS. Not sure what to tell you, usually an NVFLash would wipe everything and have a "clean" install.
Click to expand...
Click to collapse
Yeah sorry, I didn't know how to say this, that I read on a Prime thread :
Brick 3: (After messing around with your Prime in recovery it won't boot any ROM anymore, you can however still access fastboot and the recovery)
Update: This particular brick happens due to a bad kernel flash. If you are flashing kernels via the ASUS /staging method, make sure /staging is unmounted before flashing stuff to it, otherwise it WILL faill and brick.
->Please go to Option 3
Click to expand...
Click to collapse
I tried your method, it worked! Thanks! But still no touch input. I'm putting it fully back to stock.. But nothing happens!
RMA'd it. They changed the MB + the Screen...

[Q] Problems with most Roms

I am unlocked and have the recovery of twrp 2.3.3.0. I'm having problems with about every single rom I flash. I wipe everything as you are suppose to and the flash appears to go well but usually right away after the rom boots up the system becomes unresponsive. I have to hold my finger over a button for a couple seconds for it to acknowledge a touch and things just don"t run right.
Its like either the system is almost locked up or the touchscreen just hardly works.... one of the two. I made a backup of my original asus setup and if I restore it the tablet works just fine. I've tried hydro, cm 10.1, blackbean 7, and one or two I'm forgetting. AOKP RC1 is the only custom rom that gives me no problems at all in this regard, unfortunately its an unfinished rom, no camera and my battery dies like crazy with it...
The 2nd best running rom that I really like from what I have seen is blackbean 7. Runs great for first few minutes but after playing a game for a bit or doing some other things and having it run just great all the sudden the dreaded problem occurs and the only fix is a reboot for it to work for a while longer. So frustrated at this point as I have flashed so many roms and resetup so many things just to find myself doing it again trying to fix this and find a rom that works for me.
Any ideas at all on what could do this? Is the difference in the kernels the reason why AOKP RC1 and Asus original work but none of the others? Or does it have to do with my recovery? Fairly certain I have the correct most recommended one with twrp 2.3.3.0 and the process went fine. Any ideas greatly appreciated. I really just want to be able to run blackbean. And knowing that most all roms will not work for me is rather disturbing in regards to the future. Really wanting to like my new tf300t but its making it hard:silly:
Try to downgrade your recovery.
Use this : openrecovery-twrp-2.3.1.0-tf300t-JB.blob
and take a feedback after, thanks
I really appreciate that you took the time to give me something to try but I'm afraid it didn't work. Process went fine I'm on 2.3.1.0 twrp but same problem. First rom I've tried instant non-responsive. Any other ideas?
I've been using ClockWorkMod Recovery on my TF300T, and it's been great. (Used it to upgrade my ROM to CM 10.1.) No issues at all.
If you need instructions for getting it installed on a TF300T, check out my second-to-last post on thoughtsontechnology.com. (NONE of the work is mine, I just compiled the instructions and links in one spot for easier access. Most of the work came from XDA contributors, they've been really great.)
Most roms need 5 to 10 mins to stabilize after a new install, usually as they are building media storage files, etc. Are you giving them enough time?
Failing that I can only think your microsd has something corrupt on it. Boot with it out.
Well I tried cwm again flashed it no problem installed rom no problem but no fix. So guess we have established it definitely isn't the recovery at this point...
Yes I've given roms several reboots and lots of suffering them working for 10min to only fail again for another reboot... So its not that. Still the only Rom that will work is my backup of the original asus and the AOKP RC1. Trying it without the external sdcard right now.
Well no joy on the removal of the external sdcard
Have you tried a full wipe before installing? You must have some thing on the data partition causing this. I
sbdags said:
Have you tried a full wipe before installing? You must have some thing on the data partition causing this. I
Click to expand...
Click to collapse
Not sure what a full wipe is? I wipe cache/dalvik system format data and have even tried formatting the sdcard once several roms ago. One thing I have noticed since I am trying so many roms all the time is the sdcard file structure seems odd as I have at the root of the sdcard a 0 directory that continues to be added to. Currently it goes sdcard/0/0/0/0 to actually get to where I have things stored like music, downloads. Is this normal? Its strangely repetitive.
Personally I think you should stop using TWRP if you're having all these issues. Just flash CWM and have fun
touchscreen
This thread is a couple months old, but i am having the same problem. After installing a lot of different roms, both stock based and cm/AOKP. I let the rom stabilize and after a few hours or even minutes the touch screen has a mind of its own. It lags, double touches or fails to respond at all. I m on twrp 2.4.1.0. Was this issue ever resolved? Should I try old version recovery or cwm? I restored rooted stock us10.4.2.20 and the issue is gone. Is it possible that installing a rom changed the touch screen firmware? I am open to suggestions as I have spent alot of time on this with no luck. Thanks!
What version CWM would u suggest as this is probably my next move?
Showme1 said:
This thread is a couple months old, but i am having the same problem. After installing a lot of different roms, both stock based and cm/AOKP. I let the rom stabilize and after a few hours or even minutes the touch screen has a mind of its own. It lags, double touches or fails to respond at all. I m on twrp 2.4.1.0. Was this issue ever resolved? Should I try old version recovery or cwm? I restored rooted stock us10.4.2.20 and the issue is gone. Is it possible that installing a rom changed the touch screen firmware? I am open to suggestions as I have spent alot of time on this with no luck. Thanks!
What version CWM would u suggest as this is probably my next move?
Click to expand...
Click to collapse
Sounds like you have a hardware fault if the issue persists across multiple firmwares.
Also, OP said his SD card directory structure was strange. I'd format both internal and external SD in recovery (in addition to wiping and factory reset) before you flash.
Thanks! Wiping internal has seemed to do the job. Still would like to know what the issue was. I was thinking it was the touch panel firmware, but thought that would be in /system
Sent from my SGH-I747 using xda app-developers app

Categories

Resources