Database Info

Wifi won't connect after clockwork 5.5.0.4 install

I have searched with what I can on a mobile device, but I haven't found an answer for my situation.
What happened was I installed AOKP and then installed the new recovery. Then halfway through the say I found my transformer boot looping so I flashed back android revolution on a data/cache/system wipe.
Unfortunately after booting up, the wifi did not work, and it now says turning on but it never does. Does anyone know of a similar problem or point me in the right direction?
Oh and I am also unable to reboot properly with this recovery, I have to hold down and power and then cold boot every time. :/ any help would be greatly appreciated.
Sent from my Galaxy Nexus using xda premium

Flash revolution Rom again without wipe, that should fix your wifi problem.
For your cwm recovery loop go here
http://forum.xda-developers.com/showthread.php?p=23256536

baseballfanz said:
Flash revolution Rom again without wipe, that should fix your wifi problem.
For your cwm recovery loop go here
http://forum.xda-developers.com/showthread.php?p=23256536
Click to expand...
Click to collapse
Thanks! I'll try and then report back!
Sent from my Galaxy Nexus using xda premium

had to nvflash back to prime 1.6.2 and start from scratch but the tf is alive again.

FaithCry said:
had to nvflash back to prime 1.6.2 and start from scratch but the tf is alive again.
Click to expand...
Click to collapse
LOL, you could have NVFLash the newer ICS ROM

kexec recovery questions?

Ok i am running beans rom and am new so bear with me. i understand kinda what kexec does. I have it working i think? It is however booting into recovery after its been shutdown and when i reboot it seems to loop 2 or three times before starting up?
What i did.
Root
installed CWR 6.0.1 (which i believe supports kexec)
Wiped and flashed Beans Rom
is this right? i see that there are recovery images on the kexec forum. should i use one of these instead? Also where is the custom boot.img ? on the sd card? will a nandroid backup from a stock root take me all the way back?
I really appreciate it
Paul

Kexec makes the phone reboot several times. It's just working it's magic. Small price to pay for a custom ROM.
Sent from my SCH-I535 using xda app-developers app

Vorfidus said:
Kexec makes the phone reboot several times. It's just working it's magic. Small price to pay for a custom ROM.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I love having it overclocked to 1.9GhZ .. WOW FAST! what about on a cold boot? do you boot into recovery? i can deal with the reboot but the whole turning the phone on thing sucks

You boot into recovery, hit reboot, and it does the same thing.
Sent from my SCH-I535 using xda app-developers app

Ok so it is normal for it to bootloop on a restart, and on a cold boot to go staright into recovery. So once your in recover from a cold boot just hit restart now and it will boot up.
Where is the custom kernel stored at? uis it booting it from the internel sd card? if so where would it be? What if i want to try a different kernel? All i did was flash bean Rom?
what does it do when you repack a recovery image with the custom kernel. kindof explained here
http://forum.xda-developers.com/showthread.php?t=1773514
Also i was doing some research and heard that it is possible ( or maybe being worked on) if you take some sort of image and put it in the /cache that it will not boot loop? by the way i may be wrong. Just interested?

[Q] S4 , cant access my recovery or boot normally!

i cannot boot phone into recovery nor can i boot phone normally... I had just installed Viper one S rom on my phone and rebooted into recovery because my wifi wasnt working , so i was just going to revert back to an old rom. After clicking reboot to recovery from Viper rom the screen just went white . I had to power it down manually, after powering it up it would stop at htc screen with the red development lines... tried to go into recovery and it will come up for a second then disapear then phone reboots.... any ideas? oh I also had installed Latest radio in CWM after installing rom.. I hear its buggy in CWM...

I had the same problem. Did you flash the boot.IMG in recovery or fastboot? If you flashed in recovery and its not supported by your hboot version. That could be the issue. Try re flashing the boot.IMG using fastboot. If you still cannot get it to work. I would try reinstalling a custom recovery manually and restarting the Rom flashing process. There are forums all over the place to help with that. Try twrp. Ps this is all assuming you are able to get into your boot loader.
Sent from my HTC One S using xda app-developers app

Problem fixed. Don't ask me how lol. All I did was relock boot loader and flash stock ROM. Stock ROM would not load so I just decided to unlocked boot loader and phone rebooted fine. Recover works to.. crazy.
Sent from my HTC One S using xda premium

That happened to me when I didn't fast boot flash the boot.IMG file, but only the latest Viper has given me grief with that.
Sent from my HTC One S using xda app-developers app

MrPickleFicker said:
That happened to me when I didn't fast boot flash the boot.IMG file, but only the latest Viper has given me grief with that.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Good to know so I won't make the same mistake twice.
Sent from my HTC One S using xda premium

Did Wipe Data in Bootloader break my tablet

Hello
So i decided that i was going to upgrade my bootloader from 4.1 to 4.2 so i could keep installing CM10.1 nightlies. I downloaded all the necessary files (Stock Asus, twrp2.5-42 and CM10.1 nightly), put them on my SD and rebooted into the bootloader. Here's where i think i screwed things up. While in the bootloader i accidently selected the Wipe Data option. It did completed teh wipe and booted into a fresh Andriod install. So i rebooted back into the bootloader and went into twrp and flashed the stock Asus update. After rebooting into hung (after 30 minutes) at the Asus screen with the spinning circle. I rebooted holding the power button and tried letting it load again and after another 30 min still "loading"
i can still get into the bootloader and twrp (fastbooted that back on) but i can't flash any ROM's successfully
My question is did i screw up the partition table or file system since i have read that this can happen. If so how can i verify this and can i fix it? IS there anyway to recover my tablet or am i going to have to pay Asus to fix it?
Thanks

No, no brick you have to flash stock Asus firmware blob via fastboot then flash latest twrp then flash Asus firmware in twrp
Sent from my sensational HTC Desire C

noahvt said:
No, no brick you have to flash stock Asus firmware blob via fastboot then flash latest twrp then flash Asus firmware in twrp
Sent from my sensational HTC Desire C
Click to expand...
Click to collapse
Tried that same result...see attached pic for my i think the partition might be screwed
Sent from my GT-I9000 using xda app-developers app

Why do you think it's screwed?
BTW if you used the correct version of twrp (-jb for 4.1 -4.2 for 4.2) it should have wiped them correctly!
Sent from my sensational HTC Desire C

noahvt said:
Why do you think it's screwed?
BTW if you used the correct version of twrp (-jb for 4.1 -4.2 for 4.2) it should have wiped them correctly!
Sent from my sensational HTC Desire C
Click to expand...
Click to collapse
Because it says tmpfs...which i think means temp file system
also i didn't do the wipe in twrp i did it in the bootloader

Yes, the bootloader contacts the recovery and the recovery peforms the wipe! If you have an older version of twrp: it doesn't know the partitions so it wipes Them wrong!
Sent from my Transformer Pad TF300T using xda app-developers app

Display went blank, sound still there, now stuck in bootanimation

I was running CleanROM Inheritance 3.4.something. I had just rebooted the tablet, battery was around 95%. I launched an app while reboot was still going on, as evidenced by the toasts that came up regarding superuser permissions.
And then it happened. The display went blank. I still had sound. Hardware buttons did nothing until I held the power button down. Device went into reboot and stalled at the bootanimation. More than 5 minutes went by so I rebooted into recovery.
While in recovery, I poked around for a backup to revert to. I have misplaced my recovery SD card...but no big deal. I was considering updating to CleanROM Inheritance 3.4.7. I downloaded that from the interwebs, copied it to an SD, then booted the device into recovery and flashed it. The flashing process had no issues and I rebooted the device.
Now the device is still doing the same thing. Still stuck at the bootanimation. Been another 5 minutes on this one too.
I compel thee to opine.

duckredbeard said:
I was running CleanROM Inheritance 3.4.something. I had just rebooted the tablet, battery was around 95%. I launched an app while reboot was still going on, as evidenced by the toasts that came up regarding superuser permissions.
And then it happened. The display went blank. I still had sound. Hardware buttons did nothing until I held the power button down. Device went into reboot and stalled at the bootanimation. More than 5 minutes went by so I rebooted into recovery.
While in recovery, I poked around for a backup to revert to. I have misplaced my recovery SD card...but no big deal. I was considering updating to CleanROM Inheritance 3.4.7. I downloaded that from the interwebs, copied it to an SD, then booted the device into recovery and flashed it. The flashing process had no issues and I rebooted the device.
Now the device is still doing the same thing. Still stuck at the bootanimation. Been another 5 minutes on this one too.
I compel thee to opine.
Click to expand...
Click to collapse
Sounds like something got corrupted. Might be worth doing a factory reset and reflash the rom to see if it boots?

Factory reset from recovery. Reflashed 3.4.7. Rebooted to clean install. Joy.
Ty sdbags...you rock. Now that I'm at square one again I should go with a 4.2.2 ROM.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

duckredbeard said:
Factory reset from recovery. Reflashed 3.4.7. Rebooted to clean install. Joy.
Ty sdbags...you rock. Now that I'm at square one again I should go with a 4.2.2 ROM.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I reckon so

I shall get everything to an SD card and do it at work tonight. Is everything done from flashing or do I need a PC interface ?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

duckredbeard said:
I shall get everything to an SD card and do it at work tonight. Is everything done from flashing or do I need a PC interface ?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Yeah you need to flash twrp with fastboot, download stock firmware from asus unzip it and flash it with twrp then re-flash twrp again with fastboot (the asus firmware zip will wipe twrp) then install CROMi-X

JoinTheRealms said:
Yeah you need to flash twrp with fastboot, download stock firmware from asus unzip it and flash it with twrp then re-flash twrp again with fastboot (the asus firmware zip will wipe twrp) then install CROMi-X
Click to expand...
Click to collapse
Δεν είμαι σίγουρος αν κατάλαβα καλά όλα αυτά.
Yeah means I need a PC or just do it all from TWRP recovery (I think I have 2.3.1). I was looking at the CROMi-X thread and didn't see any need for a PC if I am already running a custom recovery and ROM. I might just stick with what I have for now...don't want to get in too deep. Been a while since I've done anything with the TF700 anyway, barely even used it last month.
If I can't do it all from flashing from recovery, I need to do more thinking and reading before I do anything else.
Thanks again for your support.

duckredbeard said:
Δεν είμαι σίγουρος αν κατάλαβα καλά όλα αυτά.
Yeah means I need a PC or just do it all from TWRP recovery (I think I have 2.3.1). I was looking at the CROMi-X thread and didn't see any need for a PC if I am already running a custom recovery and ROM. I might just stick with what I have for now...don't want to get in too deep. Been a while since I've done anything with the TF700 anyway, barely even used it last month.
If I can't do it all from flashing from recovery, I need to do more thinking and reading before I do anything else.
Thanks again for your support.
Click to expand...
Click to collapse
Oh I actually didnt see The bootloader package on the Cromi-x thread, that should work fine. I tried this method long ago, but my bootloader package didn't have a custom recovery included so i still needed to use a pc to fastboot one on. The cromi one should be fine

Yes I prepared the recovery and bootloader as one so as long as you have any custom recovery installed you can use my package to get to the right supported versions. Twrp 2.6 still has issues hence why I haven't upgraded yet.

I have done all the flashing. All is good. I am happy with the update but I need to thin out my apps. I am curious why there isn't an advanced power menu (shutdown, reboot, recovery, hot boot).
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

duckredbeard said:
I have done all the flashing. All is good. I am happy with the update but I need to thin out my apps. I am curious why there isn't an advanced power menu (shutdown, reboot, recovery, hot boot).
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
You on Cromi yet? 4.7 certanly does, power menu looks like this
power off
restart
-reboot
-hot boot
-bootloader
-recovery
airplane mode