Database Users

BATTERY

Ok, so I am running the newest ENERGY ROM, VBN RELOADED, and CORE CELL v4.1 and Im for android Im using hd 3.7, and when I first install the android I can get it to run 5-10mA or when I flash a new ROM, but once I restart android I can only get 50-60mA, i have pushed the back button when haret is running, it is so frustrating becuase I want to switch between android and winmo, and Im already using hastarin custom kernels and cant seem to get it to go less than 50-60mA unless I reflash or reformat and install over. Someone please tell me why the f8Ck this is happening, SO irritating. Ive tried to do some searching but all I have heard is that its from not lighting up my buttons. is there a certain time im supposed to light them up? Also, does having my charger plugged in help? Someone please help! Dont make a grown man cry.
Thanks in advance.
Matt

Just use Excellors' Multi boot app and set it to auto boot/3 secs when you want to boot Android and you should be good. If you run WM for a while reset your phone before going to Android and let it auto boot into Android. The battery drain in Android seems to be related to WM/Sense. By using the auto boot feature, WM/Sense is not allowed to fully boot. You should see significant improvement in battery performance in Android if you follow these simple steps. Cheers.

thanks mate
reocej said:
Just use Excellors' Multi boot app and set it to auto boot/3 secs when you want to boot Android and you should be good. If you run WM for a while reset your phone before going to Android and let it auto boot into Android. The battery drain in Android seems to be related to WM/Sense. By using the auto boot feature, WM/Sense is not allowed to fully boot. You should see significant improvement in battery performance in Android if you follow these simple steps. Cheers.
Click to expand...
Click to collapse
Thanks brodie, Imma give it a shot! let you know shortly

I solved this problem by renaming lights.htcleo.so included in the kernel

?
sykodelyk said:
I solved this problem by renaming lights.htcleo.so included in the kernel
Click to expand...
Click to collapse
Whaqt did you rename it to?

TheGeorgiaSwagger said:
Whaqt did you rename it to?
Click to expand...
Click to collapse
Im assuming hes talking about renaming it to lights.qsd8k.so?

How to install a Kernel.

Hey guys,
I know everyone is going to first think, What the hell, this is too easy what a noob.
Anyway, point is, ive been looking for a tutorial on this for ages and just can´t find one.
On all Android Roms they always just write things like "Also make sure to intall the kernel" and thats it or when you look through generall ROM tutorials for android you just see "Don´t forget to install the coresponding kernel"
Nothing on how to do it.
So I have the following questions please:
1. I want to install this ROM on my HTC HD2
http://forum.xda-developers.com/showthread.php?t=1316632
Click to expand...
Click to collapse
How do I install the kernel for it?
2. It tells me to partition the SD card, I really don´t get what they mean with all of those numbers?
Please send me to a tutorial where it is explained or explain it, it would really be a great great help. Thank you!

Well.
First thing - it depends on whether you want to flash the Magldr or cLK version.
I highly recommend cLK, with it you can use ClockworkMod Recovery, which will allow you to easily install pretty much everything that's in correct zip format.
So if you flash the cLK version, afterwards you just download the kernel (that's in the thread you provided) in the .zip format and save it on your sdcard. Then go into Clockworkmod Recovery (if you don't know what it is, search the net, and study) and flash zip from sdcard. That's it for the kernel.
If you want to use Magldr, I can't help with that, I'm using cLK.
About SD partitioning - there is a good guide here https://docs.google.com/document/d/1dhXJZPjZzBHcAtIE_jfEeuG988UDUaP7GfZk909nNCc/edit?hl=en&authkey=CLDJw80N&pli=1
It's a guide made especially for AmeriCan Android ROM, but the partitioning part is well written and it should work for all ROMs like that.
Just check it out, if you need anything more, let me know.

Thanks man.
This is great.
Did it with cLK and it was really easy.
Thanks!
Edit.
I need some help on this ROM. I tried to post this question in the ROM thread but it wont let me so im hoping someone can help me here.
My phone won´t boot anymore. It just gets stuck at the HTC logo with this ROM installed.
What I did was:
1. Wiped data and cleared cache
2. Installed kernel via CWM (from SD)
3. Installed ROM via CWM (from SD)
4. After succesful install (with out errors at least) i press reboot now.
And from then on its just suck at the HTC logo.
Ive left it for over an hour now just to be sure but nothing.
Can someone tell me what is wrong with it?
Thanks!

Cheesus182 said:
Thanks man.
This is great.
Did it with cLK and it was really easy.
Thanks!
Click to expand...
Click to collapse
No problem mate, if anything more, just ask - here or PM.
Edit:
P.S. if you wanna confirm that you have the new kernel installed, just go to settings, about phone and there you see the kernel info.

I'm going to jump this existing thread as I also have a beginners question on the same subject...
I already installed a ROM (NexusHD2) and having huge battery drain problems (drains from 100% to dead in aprox. 15 hours on 100% standby with no applications running), but having less than 10 posts on this forum, I can't ask in the thread for the particular ROM. But I see a lot running this ROM with a tytung_r14 kernel, so I figured that I probably had to install this as well and I'm going to try it, but one question though...
Was I supposed to install the kernel BEFORE installing the ROM? Or can I just go and install the kernel now and all will be dandy?
Thanks.

Just flash Rom again in Recovery mod then flash kernel later on. It's gonna be fine, I believe.
Sent from my Desire HD using xda premium

Why should I do a recovery flash of my ROM and then flash kernel afterwards instead of just flashing the kernel right now if that is possible?
The ROM was flashed friday afternoon, so it's a pretty clean ROM.

You can flash kernel at anytime, you don't have to reflash anything.
Also, it might not be the kernel, which is responsible for your battery life.
Search for thread called something like ultimate battery guide for android and there are all things you can do to check what's wrong and make your battery life great. I did that, and am very satisfied.

DaneX said:
I'm going to jump this existing thread as I also have a beginners question on the same subject...
I already installed a ROM (NexusHD2) and having huge battery drain problems (drains from 100% to dead in aprox. 15 hours on 100% standby with no applications running), but having less than 10 posts on this forum, I can't ask in the thread for the particular ROM. But I see a lot running this ROM with a tytung_r14 kernel, so I figured that I probably had to install this as well and I'm going to try it, but one question though...
Was I supposed to install the kernel BEFORE installing the ROM? Or can I just go and install the kernel now and all will be dandy?
Thanks.
Click to expand...
Click to collapse
I'm currently running the existing ROM on my SD card, and I'm not experiencing any battery drain what so ever...
I've also installed the ROM in NAND previously and didn't experience any heavy battery drain as well.
But to answer your question, no you weren't suppose to install the kernel before installing the ROM; The ROM (in SD or NAND format) already comes with a compiled kernel (It's a file called zImage).
You can install the kernel and you should just be dandy. Just remember that your battery life is heavily influenced by your cell reception and by the synching that occurs in the background.
To give you a reference, my phone is at 89% has been on standby for 13.5 hours with WIFI ON and data ON, but with data synching turned OFF for facebook and gmail. I'm also currently running it through the SD card with kernel r13. You should get similar results with the newer or existing kernel.

g.s said:
To give you a reference, my phone is at 89% has been on standby for 13.5 hours with WIFI ON and data ON, but with data synching turned OFF for facebook and gmail. I'm also currently running it through the SD card with kernel r13. You should get similar results with the newer or existing kernel.
Click to expand...
Click to collapse
Is this with the NexusHD2 ROM?
When my phone is "sleeping" with screen/WiFi/Sync/Bluetooth OFF my phone is using 55-60 mA.
With the screen on and lowest standard brightness setting it is at 115-125 mA

DaneX said:
When my phone is "sleeping" with screen/WiFi/Sync/Bluetooth OFF my phone is using 55-60 mA.
Click to expand...
Click to collapse
That means that you have a lurking app that keeps your phome from going into standby,so called partial wake.
Go into you app Spare Parts, click on battery history, choose other usage, since last boot or unplugged.
The screen on and running percentages tell you about the wake lock.
If it is nearly the same, that means you have almost no partial wakes.
If running is much higher, than screen on, that means you have some app that keeps phone awake.
Now choose partial wake usage in Spare Parts and it'll show you the apps.
And now you either uninstall them or change settings.
I'm on AmeriCan Android rom, getting 1-4mAh consumption in standby.

DaneX said:
Is this with the NexusHD2 ROM?
When my phone is "sleeping" with screen/WiFi/Sync/Bluetooth OFF my phone is using 55-60 mA.
With the screen on and lowest standard brightness setting it is at 115-125 mA
Click to expand...
Click to collapse
Yep, this is with the NexusHD2 ROM. My phone during standby, only draws about 2-4mA.
55-60mA during sleep/standby is not normal. Are you in an area with bad cell reception?

Gen1 to Gen2 TPT Upgrade

Sorry for the new thread, but I can't post in the dev section yet - this is really a follow up to http://forum.xda-developers.com/showthread.php?t=1258855 - maybe someone can move it?
I just used the following zip file and it worked well:
CM Nightly 257 Version (Upgrades from Gen1 to Gen2 & installs latest CyanogenMod nightly build - all in one)
Download: cm7-n257-blade-gen1-to-gen2-tpt.zip mirror
Download size: 107.8 MB
MD5: 813ba810ca0a596da4eb6ea7e47205a1
SHA1: 11030dff7b48c79463185b25fc848d488fe77768
A couple of things that weren't clear from the Instructions section (which presumably apply rather to the non all-in-one versions - haven't tried personally) were
a) Does not "reboot into ClockworkMod recovery", rather direct into CM Nightly 257, and
b) Wipes data - presumably must have done because the boot into CM was successful.
This is all very good and nicely automated; could just amend the instructions to be something like:
It should take a few seconds to flash the new Gen2 firmware (you should see some green text), then it should either reboot into ClockworkMod recovery, use that to wipe data & then install your Gen2 rom (for the custom and stock versions), or reboot into CM Nightly 257, no need to wipe or install the CM rom oneself (for the all-in-one).
All in all a great piece of work.

New here and also wish i could post on that thread as i found it extremely useful and it persuaded me to make the jump and finally upgrade my San Francisco.
It honestly feels like a new phone now, after running stock orange 2.1 since i got it about 10months back with some tweaks to launcher etc. I wish id done this a lot sooner. I also used the nightly 257 rom.
I was also (initially alarmed!) a little confused about the points a) and b) you raised above as mine also seemed to skip those steps and just launch straight into the mod. All well and good though this has now left me wondering if the step b was vital. Prior to this on a fresh start and after using Advanced Task Killer to kill all the crap id be looking at around 300mb free memory. Since the new ROM i now have 173mb free in Advanced Task Killer. Odd since i dont have a fraction of the amount of stuff on the phone considering all the stuff that came preloaded with Orange etc.
I dare say the new OS may have a larger footprint. Though my main concern is that as I somehow skipped the part where it says
"then it should reboot into ClockworkMod recovery, use that to wipe data & then install your Gen2 rom." I wonder if this means not all the old ROM has been erased and results in my limited memory.
If i check under Settings > Storage it gives me 294 Total with 203 free under internal storage. Wish id thought to check this value prior to install...
That aside it all works great and im delighted with it.

OK, what do you want free memory for? You should realise that is memory that you have paid for which isn't in use - wasted memory in other words. Android 2.3 uses more ram, when nothing else wants to use it, in order to make your phone run faster, that is a good thing. If you want to use an app which requires a lot of memory then android will free it automatically.
Don't use task killers, they harm system performance by working against Android's own memory & task management system (which is better than any task killer), reduce battery life, cause bugs & you wont get any support at all from anybody involved with Cyanogenmod if you use one.
The all in one version that includes a rom starts straight into that rom, that should be pretty obvious.
It will wipe your data, if you're updating from Android 2.1 then it'll wipe everything. Otherwise it'll miss any apps on your sd card, that's the only reason i say to wipe data - if you're coming from stock Android 2.1 then you can't have any apps on your sd card, so it makes no difference.
Stock Android 2.1 phones have 207mb internal storage ( /data) in total, you gain almost 90mb. The stock Orange bloat apps use up more room (dalvik cache) too, so you end up with much more room to install your own apps & games.

Unable to convert Gen1 -> Gen2 via TPT
Hi all,
I didn't want to start new thread, so I'll post here. In short - I'm unable to convert my Gen1 Blade to Gen2 using wbaw's TPT method.
I followed instructions carefully, tried 2 different zips (Gen1-to-Gen2-TPT-v10-custom, cm7-n257-blade-gen1-to-gen2), used 3 different microSD cards (1GB, 2GB, 8 GB class 4) and still nothing.
Image folder is on the card, all MD5s do match, I turn off the phone, wait few sec (I even took the battery out few times), press and hold menu&vol+ and then power, red power led is on, then green robot shows up, and... nothing, no green text on the screen, just few seconds later my Gen1 ROM is booting.
Any ideas?

make sure that you keep holding menu & vol+ when you press power. that's the only thing i can think of, unless your phone is already gen2. a few sd cards dont work with it, but it shouldn't be that hard to find one that does.

Thanks for the answer, wbaw.
I am holding both - menu (the one in the middle, between home and back) & Vol+ - then I press and hold power, after few seconds I let the power go but keep holding the other two. After few another seconds (while green robot is visible) a regular boot animation shows up.
My phone is definitely Gen1, as I recently installed G1 ROM (mmhmp) and previously used Mr. Pigfish, both report Gen1.
I just reformatted my stock Transcend 2GB card in CWM, put only 'image' folder with all files (MD5s are ok) and still no go. What the hell?....
Btw. I'm using 3.0.2.8 CWM. Does it make any difference? I'm running out of ideas.. what else can I check?

No idea then, sounds like you're doing everything right. The flashing should happen before the green robot shows up, if the robot comes up straight away then it's already failed to flash anything & you have to try again. It's a zte flashing program, built into one of the first bootloaders (the green robot is displayed by a later bootloader), you need to be holding vol+ & menu when you turn it on & for about a second after that, then you can let go. You should see some green text, or maybe just a black screen, then after a minute or two a big version of the green robot & clockworkmod 5.
Clockworkmod is irrelevant, it's a different zte flashing process.
Only thing I can suggest is try another sdcard. I know a few people have reported it didn't work with their sdcard, but it was only a few people & it worked with the 2nd or 3rd sdcard they tried. I got a verbatim 2gb with my phone, that works, sandisk 8gb class 2 works too & so does my new 16gb class 10 verbatim.
If everything fails & you must update to gen2, then there are some windows software phone update packages that let you update your phone using your windows pc. Those packages & instructions are in the zte blade section at modaco.com. It's a bit harder, slightly riskier, but hopefully it'll work.

I just tried another card, some noname 512MB from my old Nokia (I didn't even realized I have so many microSD cards...) and unfortunately this one is also no good. Damn....
So, TPT is built-in and should work with all Gen1 ZTE's no matter what ROM or CWM I'm using, right? Is there any possibility I accidentally removed/erased or destroyed part of it?
I didn't even flash that much, from stock Blade (well, I removed simlock), I installed CWM and went to Swedish Spring (half a year ago). Now I've decided to move forward, installed Gen1 MMHMP, but decided to give CM a try. As you can see not much of a history, therefore I'm even more surprised TPT is not working in my case...
Is there a way to tell this flasher actually works? Something other than just putting gen-to-gen converter image? Any troubleshooting you may think of?
Edit: Tried another card (that's already 5th card!!), 8GB class 4 - no go... I don't think it's a problem with microSD card anymore... it has to be something else.

It turns out TPT is not available on my Blade (some European versions lacking TPT were reported). Anyway, I have successfully converted to Gen 2 using Windows/FTM method. I didn't find it hard, it's just a bit more hassle with repeated flashing. All went good, no need to fear.
Thanks!

Hi, sorry to thread hijack the thread hijack, but I too have a question about this process and can't post in the dev forum.
I just followed the all-in-one process on my girlfriend's brand new stock Orange San Francisco, and it worked flawlessly. I'm now wanting to do the same to mine, but it isn't stock; it has ClockwordMod (3.x, I think) and a FlibbleSan ROM from Modaco installed (Gen1).
What (if any) different steps do I have to take to get everything rolling on my own device? Apologies if it's a stupid question, I was just spooked by the parts about not using it on operator upgraded 2.2 devices and wondered if the same disclaimer applied to user updated phones.
(Merry Christmas )

Never mind, I took the plunge and everything works fine.

Random Reboots after Upgrade
Can't post in Dev forum either so posting here.
I had updated my blade last year from Orange stock to JJF, still GEN1.
I followed the all-in-one process to get to GEN2 CM7 build 257 and all has worked well.
The only issue I am seeing now is random reboots every day or so.
Any ideas? Known issue or fix?

eddiem74 said:
Can't post in Dev forum either so posting here.
I had updated my blade last year from Orange stock to JJF, still GEN1.
I followed the all-in-one process to get to GEN2 CM7 build 257 and all has worked well.
The only issue I am seeing now is random reboots every day or so.
Any ideas? Known issue or fix?
Click to expand...
Click to collapse
Have you changed anything under performance tab in CM settings?
Sent from my Blade using XDA app

karthiknr said:
Have you changed anything under performance tab in CM settings?
Sent from my Blade using XDA app
Click to expand...
Click to collapse
No, just done the update?
Sent from my Nexus S using XDA App

eddiem74 said:
No, just done the update?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
You did a wipe before flashing right?
Sent from my Blade using XDA app

karthiknr said:
You did a wipe before flashing right?
Sent from my Blade using XDA app
Click to expand...
Click to collapse
There was no option to wipe, it just updated from gen1 to gen2 and booted up after restart from what I can recall.
Sent from my Nexus S using XDA App

eddiem74 said:
There was no option to wipe, it just updated from gen1 to gen2 and booted up after restart from what I can recall.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Ok so I used ROM Manager and installed CyanogenMod 7 V7.1.0 as that is meant to be stable, wiped data/cache/etc via the process.
All was well until I needed to make a call, screen keeps going black and I need to remove battery to resolve?
Any ideas?

eddiem74 said:
Ok so I used ROM Manager and installed CyanogenMod 7 V7.1.0 as that is meant to be stable, wiped data/cache/etc via the process.
All was well until I needed to make a call, screen keeps going black and I need to remove battery to resolve?
Any ideas?
Click to expand...
Click to collapse
Sounds like you need to calibrate the proximity sensor. I think there should be a ZTE Blade settings app that you use to do it.
Probably better to flash one of the latest self-compiled versions of CM7. Its been a while since nightlies were made, but lots of new stuff has been added/fixed since 7.1.0 RCs/stable.

eddiem74 said:
Ok so I used ROM Manager and installed CyanogenMod 7 V7.1.0 as that is meant to be stable, wiped data/cache/etc via the process.
All was well until I needed to make a call, screen keeps going black and I need to remove battery to resolve?
Any ideas?
Click to expand...
Click to collapse
Like Amphoras says calibrate your proximity sensor in the ZTE Blade Settings app. That should do. If you still have a problem,flash the 257 nightly or any other ROM if you don't like CM.
Sent from my Blade using XDA app

this might be a bit offtopic but is there a way to tell from the packaging if the phone has amoled or tft? I suppose tft is best?

Vegacomb - drawing is useless

Not sure if this is hardware or software, if it's software, is there a way to fix this?
when I draw anything on the Vega (Vegacomb latest version) in DrawSomething or any drawing app (big canvas), my lines look like I'm on a vibrating plate, it's completely unusable, occasionally vertical lines look OK, but anything else is unrecognisable
any ideas?

Its probably the touchscreen causing the problem as most roms fail to calibrate the screen correctly because of a flaw in the it7620 driver.
Try installing this shuttle test rom.
http://dl.dropbox.com/u/37483979/P10_image_20110411_v1.10.4_std_dev.exe
It was posted over on modaco by a guy called alex zhou.
Install the test rom with NVflash, it will calibrate the screen correctly on first boot (press the back button).
Then install recovery boot
http://dl.dropbox.com/u/37483979/com.modaco.vegarecoveryboot_c2.apk
and boot to CWM recovery.
format data, cache, boot and system then turn off.
Now NVflash the test rom again, run it and calibrate the screen again.
Now install what ever rom you want and your problem should be gone
Good luck
Thanks to Ged over on modaco for the dropbox upload for the files.
The next release of vegaics should contain an improved driver that will enable proper calibration. The same driver can be used for vegacomb but would require someone building a rom with the driver included. As far as I know no one has done this yet and I dont think anyone is working on Vegacomb (I may be wrong) as ICS is getting all the love.

richardmlea said:
Its probably the touchscreen causing the problem as most roms fail to calibrate the screen correctly because of a flaw in the it7620 driver.
Try installing this shuttle test rom.
http://dl.dropbox.com/u/37483979/P10_image_20110411_v1.10.4_std_dev.exe
It was posted over on modaco by a guy called alex zhou.
Install the test rom with NVflash, it will calibrate the screen correctly on first boot (press the back button).
Then install recovery boot
http://dl.dropbox.com/u/37483979/com.modaco.vegarecoveryboot_c2.apk
and boot to CWM recovery.
format data, cache, boot and system then turn off.
Now NVflash the test rom again, run it and calibrate the screen again.
Now install what ever rom you want and your problem should be gone
Good luck
Thanks to Ged over on modaco for the dropbox upload for the files.
The next release of vegaics should contain an improved driver that will enable proper calibration. The same driver can be used for vegacomb but would require someone building a rom with the driver included. As far as I know no one has done this yet and I dont think anyone is working on Vegacomb (I may be wrong) as ICS is getting all the love.
Click to expand...
Click to collapse
tried VegaICS, got the same, run calibrate in shuttle tools, got the same, did as you suggested above, installed the ROM, calibrated, formatted etc, installed ROM again, calibrated, then installed VegaICS again, got the same, rant calibrate in shuttle tools, got the same
it's not just me either, a work colleague has the same issue

Most stable ROM for WiFi TF101

Title says it all guys blowing of the dust of this thing can anyone point me to the most stable ROMs out there CM10 prefer
Sent from my HTC6435LVW using Tapatalk 2

I'd like to know this too. I often have to turn wifi off then on to reconnect.

Team EOS4 & KatKernel are by far the most stable ROM and Kernel combination available from my experience, also it is JB 4.2.2, the latest Android available atm
No wifi issues at all, wifi works after sleep, never disconnects during use for me, and works first time after a full boot, just remember to set the correct wifi location in settings

Team EOS 4, Katkernel here too, make sure you reboot a few times after installing it. follow the guide in this forum, install it like it directs you to.
FULL wipe(cache, dalvik, factory, system), install ROM, cache/dalvik wipe, install gapps, cache/dalvik wipe, install Kernel, cache/dalvik wipe, reboot.
Get Kat apk to boost volume and GPS fix.
I was having systemUI issues, reinstalled everything a few times and now it's running great. Keep it under 1400mhz, 1200mhz seems to work well for me. Nightly 109 was eating up my battery too quickly, 111 is doing better, I hope they can improve more if possible, great ROM either way, I'm very grateful.
Sent from my Transformer TF101 using xda app-developers app

I cant write to developer threads (including TeamEos ROM) since I didn't write 10 post yet, but...
I love TeamEOS. One and half year I've used 4.1 compilation and now I use 4.2 #112 build....
What can I say? Stable WIFI, fast GPS as hell, marvelous performance.... Try it!
And big thanks for Developers of TeamEos and KAT Kernel. You should be owners of ASUS! or companies like this.

Astania said:
I cant write to developer threads (including TeamEos ROM) since I didn't write 10 post yet, but...
I love TeamEOS. One and half year I've used 4.1 compilation and now I use 4.2 #112 build....
What can I say? Stable WIFI, fast GPS as hell, marvelous performance.... Try it!
And big thanks for Developers of TeamEos and KAT Kernel. You should be owners of ASUS! or companies like this.
Click to expand...
Click to collapse
Just reply to a few other threads, XDA has thousands

+1 for EOS4/KAT kernel. No-name is pretty good as well if you like CM 10.1.

EOS is amazing running 4.2.2 with my cpu overclocked to 1400 is amazing

+1
talman26 said:
EOS is amazing running 4.2.2 with my cpu overclocked to 1400 is amazing
Click to expand...
Click to collapse
Aye...EOS 4.2.2 (v109) + 1400, very stable, no big issues, suitable for daily drive tab

+1
Team EOS4, Been using it for months and not a WiFi hicup.

*Detection* said:
Team EOS4 & KatKernel are by far the most stable ROM and Kernel combination available from my experience, also it is JB 4.2.2, the latest Android available atm
No wifi issues at all, wifi works after sleep, never disconnects during use for me, and works first time after a full boot, just remember to set the correct wifi location in settings
Click to expand...
Click to collapse
Dude, I did that update and crashed! I was using Stock ICS4.0 ASUS version and using [recovery-clockwork-touch-5.8.1.8-tf101-repack]. Happens that ended Succesfully, but it did not REBOOT. Bricked at the ASUS logo screen...I don´t know what to do, nothing works. Tried to unBrick from APX mode but can´t run into it. :crying:

danilimpsy said:
Dude, I did that update and crashed! I was using Stock ICS4.0 ASUS version and using [recovery-clockwork-touch-5.8.1.8-tf101-repack]. Happens that ended Succesfully, but it did not REBOOT. Bricked at the ASUS logo screen...I don´t know what to do, nothing works. Tried to unBrick from APX mode but can´t run into it. :crying:
Click to expand...
Click to collapse
Can you still get into recovery? If so, can you flash from the microSD?

danilimpsy said:
Dude, I did that update and crashed! I was using Stock ICS4.0 ASUS version and using [recovery-clockwork-touch-5.8.1.8-tf101-repack]. Happens that ended Succesfully, but it did not REBOOT. Bricked at the ASUS logo screen...I don´t know what to do, nothing works. Tried to unBrick from APX mode but can´t run into it. :crying:
Click to expand...
Click to collapse
That's because your running CWM recovery, I know its not easy to read every thread going, but if I had £1 for every person I've said the same thing to over the past 2 weeks I'd easily have £7.39 by now
Use Easyflasher to unbrick and flash TWRP recovery, then you can flash Jellybean ROMs without bricking
http://forum.xda-developers.com/showthread.php?t=1688012
APX Mode will not show anything on the TF screen, just plug the TF into the PC USB, then turn off the TF, then hold power and volume up until you hear the USB connect sound, that tells you that it is in APX mode, then you can run Easyflasher to unbrick
There should really be a sticky made about CWM, it doesn't play nice with JB ROMs

Team EOS 4 + Kat Kernel = FAST and STABLE :victory:
PS: If you wish to use Phablet UI i suggest you use Trebuchet from CM 10.1

*Detection* said:
That's because your running CWM recovery, I know its not easy to read every thread going, but if I had £1 for every person I've said the same thing to over the past 2 weeks I'd easily have £7.39 by now
Use Easyflasher to unbrick and flash TWRP recovery, then you can flash Jellybean ROMs without bricking
http://forum.xda-developers.com/showthread.php?t=1688012
APX Mode will not show anything on the TF screen, just plug the TF into the PC USB, then turn off the TF, then hold power and volume up until you hear the USB connect sound, that tells you that it is in APX mode, then you can run Easyflasher to unbrick
There should really be a sticky made about CWM, it doesn't play nice with JB ROMs
Click to expand...
Click to collapse
Ok, but to use Easyflasher I have to go into APX and I CAN´T (maybe driver issue, but I reinstlaled and nothing!
I DO can go into TWRP Recovery (to be straight it´s the only thing that workED) but flashing ROMs FAILED over 5 times. So, to get a lil worse, I was clearing cache and Dalvik and suddenly I miss-touched SYSTEM...and now I think that I did MESS with it. I reboot and I get nothing but [Eee Pad ASUS] screen...not even get to loading dots!!
Last try was LINUX Coldboot...nothing succesfull at all!
I gonna kill myself....BRB!

danilimpsy said:
Ok, but to use Easyflasher I have to go into APX and I CAN´T (maybe driver issue, but I reinstlaled and nothing!
I DO can go into TWRP Recovery (to be straight it´s the only thing that workED) but flashing ROMs FAILED over 5 times. So, to get a lil worse, I was clearing cache and Dalvik and suddenly I miss-touched SYSTEM...and now I think that I did MESS with it. I reboot and I get nothing but [Eee Pad ASUS] screen...not even get to loading dots!!
Last try was LINUX Coldboot...nothing succesfull at all!
I gonna kill myself....BRB!
Click to expand...
Click to collapse
Of course it won't boot; wiping system means deleting the ROM. Just re-flash the ROM now and see if that works. You are supposed to wipe system before flashing a new ROM anyway (to clear out remnants of the old ROM), so it's no big deal.
Sent from my Transformer TF101

zAlbee said:
Of course it won't boot; wiping system means deleting the ROM. Just re-flash the ROM now and see if that works. You are supposed to wipe system before flashing a new ROM anyway (to clear out remnants of the old ROM), so it's no big deal.
Click to expand...
Click to collapse
As I already said...flashing ROM FAILED over 5 to 7 times...and I CAN´T get to APX...i´m stucked at NO SYSTEM...just can get to Recovery, but NO flashing!

Try a different PC, or reinstall APX drivers
99% that APX mode does work, either you are doing something wrong, or your PC is struggling with the APX drivers
APX mode is volume up & power from powered off state while already plugged into PC, the only notification for entering APX mode is USB connect sound, nothing will appear on TF screen

I tried EOS4 recently and although the release looks good I experienced so many crash/reboots/freeze that it would make the worst build of the stock ROM look fantastic.
There are lots of update but nothing about fixing the important stuff like reboots, freeze no return from sleep
I would strongly advise on staying with stock ROM at the moment

hulk69 said:
I tried EOS4 recently and although the release looks good I experienced so many crash/reboots/freeze that it would make the worst build of the stock ROM look fantastic.
There are lots of update but nothing about fixing the important stuff like reboots, freeze no return from sleep
I would strongly advise on staying with stock ROM at the moment
Click to expand...
Click to collapse
Have to ask, what recovery did you use and did you do a full wipe before installing?
I find EOS 4 to be MUCH more stable on WiFi than any ICS ROM (including Stock and stock based ROMs)