Database Users

[Q] Can't boot... have been meticulous... Help please?

This may "wreak of non-search" and I am sorry if it does. While I have searched, the overall panic that one experiences when you suspect a brick and cannot afford to have a brick.... (that, plus a friend purchased this Glacier for me to help me get back on my feet with respect to career/employment, etc., so a good amount of guilt is thrown into this mix)... all prevents me from rationally and methodically searching thread after thread to figure out why I am having the problem I am having.
I will be as precise as possible.
1. Back in Feb., I perm rooted with visionary... then about 2 weeks later, I read that this root was not true radio s=off perm root, so I used adb and the scripts to perm root again--using the wiki as a guide. Saved a copy of the partition 7 bin on my laptop as an added precaution. Also, BTW, I never flashed the engineering HBOOT. It didn't seem essential to do so... PLUS, in almost every guide it warned that this was the most likely chance for one to f*ck up and brick, so in the interest of erring on the side of caution, I skipped that.
2. I kept stock ROM for several weeks after that... just enjoying root and freezing bloatware with Ti, and doing other root-enabled mods... nothing too involved.
3. About 1 week ago, I finally decided to flash my ROM. I had Rom Manager (paid version), and had flashed ClockworkMod Recovery 3.0.0.5. Further, as an FYI, I had/have numerous nandroid backups on the SD, plus several Ti backups of apps/data... even sync'd this with dropbox, so I can access those now (which are not of any help obviously).
4. I first flashed a CM7 nightly build--wiped data and cache, and as far as I know followed the guides precisely. All was well...new ROM worked alright... some bugs, but it was nice to have the new features, etc.. And of course the mental gratification of having 2.3.3 (GB) instead of 2.2.1 (boring old froyo). I updated the nightly maybe 2 times... in each case, I simply flashed without backing up those ROMS or wiping data/cache as they didn't seem necessary, plus I still had all my stock rom nandroid backups on the SD.
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Since I cannot get into the phone... I am of course panicked... I have ADB on my laptop if needed, but I really am at a loss as to why this happened, and what I can do at this point....
Please, please advise. My utmost appreciation and sincerest gratitude in advance for any assistance.
Thank you!!!
syntropic

syntropic said:
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Click to expand...
Click to collapse
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
should come up to a white screen.

take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Sent from my HTC Glacier using XDA App

Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
Click to expand...
Click to collapse
No... that is what I meant when I said tried to "boot into recovery". And I got the 3 vibrate alerts and a blank screen, and nothing........

take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Click to expand...
Click to collapse
Will do... Thank you. DO you have any idea of where I f*cked up here??

Could be a number of things. Like wipe didn't go through completely , bad download, or just random crap out like a few others. Even flashing with the wrong cwr version can less to your issues. Lol like I said could be a number of things. Sorry I couldn't be more helpful.
Sent from my HTC Glacier using XDA App

OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....

I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Sent from my HTC Glacier using XDA App

syntropic said:
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
Click to expand...
Click to collapse
What recovery are you using? 3.0.0.5? and you're trying to flash a 2.2 ROM. Thats where the problem lies. See my post regarding this. It's in my signature, the green one.

I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Click to expand...
Click to collapse
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
EDIT: MUSTKll20... Well, you were right... This is not ROM specific. I tried Re-Flashing RC3, which previously worked fine. Now, since I have CWModRec 3.0.0.5, I need to use a 2.3 ROM.... So I thought I would start with this idea. So, I guess, I need to get whatever is corrupt deleted... So my only question thus remains: How do I wipe everything except the SD from within CWR?
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!

syntropic said:
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
Click to expand...
Click to collapse
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
and android phone have a method of using a section of the SD card for their memory banks. I'm not really sure how it works either, but it does. You can wipe the internal w/o wiping the SDcard.
Wiping the phone from with in the recovery image will not touch the SDcard, it will only wipe the internal. You can format the SD card from the Recovery Image, but i'll leave that dog sleep so we do not it accidentally.

last little clean-up question.
Sorry to bump this... last LAST question...
Mustkll20: I realized that you were correct to suggest to wipe everything except the SD... Something is corrupt.
But I am not real sure exactly how to wipe EVERYTHING except the SD, from within CW recovery... Since that is the only mode I have available to me. Once I wipe, I will reinstall CM RC3, then update Clockworkmod Recovery to 3.0.0.6, and then try and download RC4 again using another method, and re-flashing.
I would trial and error this, but do not want to wipe the SD.
Thanks guys... seriously.

You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
Click to expand...
Click to collapse
I didn't see your reply... ummm. and I do need to wipe.. Because I have tried to re-flash both RC3 and RC4, and I get what must be a "bootloop": During the CM splash, it stops and then reboots---over and over. It never did that before.... so my problem is something else...
I don't know what else there is besides the SD and the ROM, but whatever it is, I need to delete it. So should I do a factory reset???

Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.

lowandbehold said:
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
Click to expand...
Click to collapse
Yep... I know the thread is not for thrillseekers (i.e., its boring), but I mention that I discovered this phenomenon... so I really wasn't in all that bad a spot to begin with.
I still need to figure out how to fix my current problem.... all CM RCs (I can only flash 2.3 ROMs because of CW 3.0.0.5) go into what I guess is a bootloop. In other words, they do not ever boot, just crash and restart. And the RC3 ROM I used worked fine before this... so something else is causing this problem. I need to wipe everything I guess, but I just don't know how... without touching the SD card and from within Clockwork Recovery.

Ok. Go into recovery.
1. Wipe data/factory reset
2. wipe cache partition
Both of these are on the main screen.
Go to advanced
3. Wipe Davlik Cache
Go back to main screen
Go into mounts and storage
4. format boot
5. format system
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.

lowandbehold said:
Ok. Go into recovery.
{...}
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
Click to expand...
Click to collapse
Thank you for the concise and thorough response!!!!!!! Id thank you, but have used up my allotment. get ya tommorow!!

And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?

syntropic said:
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
Click to expand...
Click to collapse
You can thank the Google c&d order for that. Go to cyanogenmod.com. there is a link there for the gapps zip.
Sent from my HTC Glacier using XDA App

OK... I thoght Gapps.zip was just Google Docs. Luckily, I had that on my SD card from one of my many ROM downloads. I see why they had to make it separate.
But I am installing it, and everything is great... And I learned a lot too... Which can only mean trouble.
Thanks!

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?

Vega screen is unresponsive when cold

Hi all, hope someone can help me.
I've recently bought a refurbished Advent Vega from Curry/PC World Ebay outlet. I've installed ICS Custom rom onto it but am having a problem with the screen being unresponsive when the tablet is cold.
I know its not an issue with the rom as the same issue occurs with other roms including the vega's stock rom.
I believe it is some sort of heat problem, that when the device is cold (when it has been off all night) the screen is really unresponsive, to the point that the unlock slider won't move without pressing extremely hard on the screen, this still doesn't unlock but it does move around a little.
After a while the screen will gradually become more reponsive but still a bit jittery and then after a bit longer once it has warmed up a bit the screem works perfectly. If I charge the tablet it seems to fix it quicker but I believe this is due to the heat again as the battery charging heats the tablet up quite quickly.
I've read a couple of other articles about squeezing the left hand or right hand side of the tablet and many people say that this works but it doesn't for me.
Does anyone else have any other suggestions on how this can be fixed.
Thanks for any help you can provide.

Try 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.

Thanks so much for your help. Works perfectly well now thanks even when it is cold.

Your welcome, glad it fixed it.
The next release of vegaice will include a improved touchscreen driver that will correctly calibrate the screen but if the problem returns again just redo the above fix.
Richard

Hi Richard - I registered with XDA (after months of lurking) just so I could thank you for this same advice when you gave it to mmace. I now gather I can't thank anyone till I've posted at least once, so this is it - if I now can I'll thank you on both threads, FWIW.
Anyhoos, to make this more than just a "thank you note" I'll explain - I bought a Vega with an "unresponsive screen" very cheaply on eBay hoping I could at least make a cheap netbook of it with a keyboard/mouse - my Tosh Folio100 permits this more easily than the Vega, it transpires, as it defaults to USB host status. When it arrived I found an otherwise tidy tablet stuck in language selection and tried various roms in the hope that the USB could be enabled. ICS b1, unlike the others, showed some vestigial responsiveness on the screen itself so I started looking for a way to calibrate it - I didn't find Alex's posting on Modaco but when I found mmace's here I followed your instructions (resisting the temptation to just stick with Alex's rom once it fixed the screen completely!) and now (fingers crossed) have a fully working Vega for peanuts....
Please let me stress - when it arrived this Vega's touch screen was totally non-functioning, no amount of pressure or flexing of the case made any difference. In ICS the language selection would scroll but not select. After running Alex's rom the problem disappeared completely.
Two questions now occur to me -
1. Why the load/clear/reload/load regime? I followed it religiously but can't help wondering whether I couldn't have just skipped the clear and reload.
2. Why isn't it possible to run a standalone version of the recalibrator on an adhoc basis when required? - If the touch screen fails again once the tablet's been in use for a while this procedure will be far more of a nuisance.
Anyway, Richard, I thank you for the sage advice and my wife thanks you for her now having a tablet instead of a netbook. Only thing is, I was going to buy a new touch screen for my Tosh (which is 'starred') but since it would cost more than this now-perfect Vega I can no longer justify it.....

Thank you indeed.
My Vega has suffered from random screen badness since I first went to vegacomb.
I had to live with it by treating it like it was a baby not to be upset!! Otherwise the screen and the dummy went outta the pram.
Could anyone provide some more download links? as Richards dropbox is creating too much traffic and has been disabled for a while.
Sent from my Advent Vega with a screen like a slapped ass!

recovery boot problem with this method
hello
i have exactly the same issue as cboard with a vega probably bought at the same time!
i have followed richardmlea's post but seem to be having trouble with the vega recovery boot. I have installed it into the test rom with the file manager but when i run it it boots to recovery (android man with the orange arrow) but hangs here, if i eventually then press the power button it shows the vega recovery options but none of them work and just send me back to the android/orange arrow recovery screen. in the bottom of the recovery page it says something like
formatting: ... misc
i'm sure this will also solve my 'cold' vega problem so would be grateful of any help
thanks
keith

kiffmoore said:
hello
i have exactly the same issue as cboard with a vega probably bought at the same time!
i have followed richardmlea's post but seem to be having trouble with the vega recovery boot. I have installed it into the test rom with the file manager but when i run it it boots to recovery (android man with the orange arrow) but hangs here, if i eventually then press the power button it shows the vega recovery options but none of them work and just send me back to the android/orange arrow recovery screen. in the bottom of the recovery page it says something like
formatting: ... misc
i'm sure this will also solve my 'cold' vega problem so would be grateful of any help
thanks
keith
Click to expand...
Click to collapse
Same issue here,
Also, tried to install CWM from Rom Manager but unable to gain root access?
Any suggestions to install CWM rather than the stock vega recovery?

Bad nand blocks
Glad it helped you all.
More Vega’s saved from the scrap heap; I can feel the ozone layer growing back as I type. I think I may burn a tree to celebrate.
x5starguerillaa said:
Same issue here,
Also, tried to install CWM from Rom Manager but unable to gain root access?
Any suggestions to install CWM rather than the stock vega recovery?
Click to expand...
Click to collapse
This Issue is caused by block in the bad nand ram. The bad blocks you have are in the boot partition so recovery is not flashing correctly to the ram. If the bad nand where elsewhere (everyone has them to some degree) they would be causing a different problem.
The solution is to install a rom that re-partitions the nand differently (effectively moving the physical locations of the recovery and other partitions on the nand)
This was the reason 2 versions of Moddedstock were created. Moddedstock re-partitions Nand to make more space for larger versions of android (originally Vegacomb). Newbe5 discovered that altering the location and size of the boot and recovery partition fixed the problem for some but created the same problems for others. He created Moddedstock version 2 so there was a second version so people could have a second roll of the dice, so to speak.
All versions of VegaICS have the same partition layout as moddedstock version 2 (I think) but of regardless which is one now being used, there is only one base. This is why some people get stuck at the boot logo after installing Vegaics and others cant boot recovery.
Ideally we need 2 partition layouts again.
The solution for both of you above is not to install or boot CWM recovery after calibration on the factory test rom. Instead turn it off, put it in nvflash mode (back/power button thing) flash moddedstock and when booted select boot to recovery. If this fails any point (installing, booting or recovery) get the other version of moddedstock and try that one, one of them should work for you.
Good luck
Richard

I tried the shuttle test rom in my viewpad 10s with totally unresponsive touchscreen, but it didn't work. After hitting "back" button to start screen calibration, it jumped to setup screen and the touchscreen is still not working at all. Already tried to reflash the shuttle rom few times.
Any idea how to fix it? Thanks.

Answered on modaco thread
http://android.modaco.com/topic/352220-how-to-fix-touch-problemadvent-vega-p10-10s/
rchoi999 said:
I tried the shuttle test rom in my viewpad 10s with totally unresponsive touchscreen, but it didn't work. After hitting "back" button to start screen calibration, it jumped to setup screen and the touchscreen is still not working at all. Already tried to reflash the shuttle rom few times.
Any idea how to fix it? Thanks.
Click to expand...
Click to collapse

Is it possible to restore a cwm backup after doing this or will that simply undo what this process fixes?
Edit: I'm running VegaICS Beta1 btw
Sent from my Vega using XDA

Thanks for advice on bad nand blocks Richard. I will give that a whirl later this evening.
Sent from my HTC One X using XDA

fubofo said:
Is it possible to restore a cwm backup after doing this or will that simply undo what this process fixes?
Edit: I'm running VegaICS Beta1 btw
Sent from my Vega using XDA
Click to expand...
Click to collapse
It depends on what you are referring to.
Restoring the CWM will not undo the touchscreen fix. However, most roms that are not android 2.2 (everything useful except corvus5) will fail to calibrate the screen properly*, so over time heat (and probably other things) cause the calibration to go off. Using the shuttle tools calibration app wont work properly.
Eduardo's new touchscreen driver fixes this problem so the calibration works correctly. Unfortunately this driver was made after Vegacomb beta 1 was released. There are a couple of updates that I know of (*one by Scanno one by Areo) that include the new touchscreen driver.
If your CWM backup contained this new Touchscreen driver, after you restore your backup you shouldn't have any further problems. You may occasionally loose calibration but the screen calibration app (in shuttle tools) will work correctly and the touchscreen will work again after calibration (so no need flash another rom).
If it’s the partition layout and the nand issue you are referring to.
A cwm backup won’t change the partition layout but will restore the contents of the recovery and boot partitions. The bad nand will still be there but in a different place (relative to the old partition layout). If the errors are somewhere critical the tablet may not boot after restoring the backup or boot to recovery may not work. If the errors are somewhere less critical it may not affect you at all. The bad blocks are common to all nand, as long as there are not too many they won’t cause any problems.

Thanks for getting back richard.
I do have the latest VegaICS beta1 installed along with the UpdatedApps patch and Kernel supplied by scanno. No my concern was not about the recovery partition issue, it was reference a full system backup from CWM.
So just to confirm:
I should be able to create a complete system backup (nandroid) then apply this fix? A nandroid restore should not undo the fix so long as I have the latest kernel installed (I believe I do), would that sound about right?
Sent from my Vega using XDA

Exactly right.
Fingers crossed anyway.
I only had to do the fix once, a few days later the new driver was released and I used it immediately. The only touchscreen related issue I have had since was a slight loss of calibration after I had been playing a game for about 4 hours. The screen had got very hot and started to loose accuracy. The screen calibration in shuttle tools restored normality in seconds and it hasn't happened since.
I have since put a sheet of Mylar between the LCD and the motherboard to deflect heat away from the touchscreen. This may have helped, its defiantly cooler.
http://forum.xda-developers.com/showthread.php?t=1585071

Great, thanks for that. I'll have a go and get back with any success. My screen has random sensitivity issues and regularly hits keys multiple times, gets a bit annoying after a while lol.
I take it the Vega tools you refer to is the shuttle tools app?
Sent from my Vega using XDA

fubofo said:
I take it the Vega tools you refer to is the shuttle tools app?
Sent from my Vega using XDA
Click to expand...
Click to collapse
Doh!
Yes, do. I will change it to avoid confusion for anyone else.

richard's advice if you can't boot to recovery
hi richard
thanks for your further advice on bad nand blocks and booting into recovery, followed you further method and at present (touch wood!) the unresponsive 'cold' screen issue has been solved
appreciate your help saves me sending it back to currys ebay!
keith

Ive got a problem where after installing the P10_image_20110411_v1.10.4_std_dev rom, and rebooting into recovery. Im presented with this screen:
Code:
Android system recovery <3e>
Android system recovery utility
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
_______________________________________________________
Formatting MISC.....
Now im able to highlight the options using the up/down volume keys but i cant select anything. The power button just hides all the options and the back button seems to do nothing.
Has anyone else come across this or got a resolution?

[Q] camera shows up as a black screen

So I know a lot of people have actually had this issue, but I am not entirely sure that it's a hardware failure in my case.
Recently, I flashed ONLY the .15p radio without the .621 using Goose306's .605 AIO Updater which works great to take you from Froyo to GB and updates the radio to the .15p which to my understanding is only flashable on a froyo kernel.
Now after SBFing to the 340, then flashing the 15p radio, and finally going back to CM9 4/24/12 rc2, I noticed my camera no longer worked. I figured being that it's an ICS build, it may have just been something they rebroke. I rebooted into CWM, wiped data, cache, and dalvik, and following someone's advice, formatted system, data, and cache seperately. Then I flashed Liberty 3 2.0 Gold. While doing so, I decided to mount the /pds partition. HOWEVER I DID NOT FORMAT THIS PARTITION. I was nervous about it in the first place and did some reading only to see if I format this partition, I would lose wifi, radio, BT, and possibly more. My wifi works great still. radio is still 15p, and I never try BT as I have nothing to test it with. Even after using the RSD Lite method to go back to the .340, .596, .602, .605 I still have no camera. The camera app does not fc at all but it also doesn't take pictures. Shutter sound is enabled, but when I try to take a picture, the sound doesn't play. I did SBF assuming like the rookie I am that it would fix it. No dice.
Now I would like to troubleshoot my phone to see if it's possible I have corrupted a file that is fixable.
Where would be the best place to start?
What software or apps should I use?
If it is truly a software issue, how would I go about fixing it? (I know it would be dependant on what is really wrong in this case).
Basically I don't want to buy a replacement camera module just to figure out that it really is a software problem.
Thanks XDA for the time and keep doing what you're doing. We're counting on you!

Newbie Need Help..got my TF101 rooted..now what?

Hello, Im new to this and was able to root my TF101 build .27 with oneclickrecovery V0.4, which installed SUPERUSER v3.0.7
Wanted to install the EOS 4 JB because I read this is very Fast and Stable. This is what is important to me, hence the root.
Now how do I use this and install the ROM?
Is there a youtube or link that someone can direct me to?

Have a look here:
http://www.transformerforums.com/forum/showthread.php?t=33773
You will need to update to TWRP 2.3.2.3 (highly recommended) via GooManager

THank you for the link. I tried to install easyflasher but I think when I installed oneclickrecovery, it installed Rogue XM Team which I think is my flasher (instead of easyflasher)..when I rebooted with VOL_DN & PWR, then VOL-UP, it went to Rogue XM Team instead of easyflasher.
So can I just download the ROM into my SD Card and use the menu from the Rogue "install from .zip file"?
Is this the method?
I know Im half way there but need guidence for finish the rest. thanks for your help.

hipertec said:
THank you for the link. I tried to install easyflasher but I think when I installed oneclickrecovery, it installed Rogue XM Team which I think is my flasher (instead of easyflasher)..when I rebooted with VOL_DN & PWR, then VOL-UP, it went to Rogue XM Team instead of easyflasher.
So can I just download the ROM into my SD Card and use the menu from the Rogue "install from .zip file"?
Is this the method?
I know Im half way there but need guidence for finish the rest. thanks for your help.
Click to expand...
Click to collapse
I'll alleviate some of your confusion lol, Rouge XM etc are recoveries (that are accessed via holding vol down and power) Easyflasher is a program that runs off your pc and allows you to install a recovery (like Rouge, TWRP or CWM). Easyflasher also works as an unbrick tool (if you do something wrong and mess up your tf101 easyflasher will restore it back to stock)
When using a recovery you need to place the rom on your sd card (some recoveries will only allow flashing from internal or external sd card's not both, but in the case of rouge it access both) then wipe the device (this will get rid of data etc, so if your going to make a back up this is the time) and then wipe everything except for battery stats (it isnt necessary to wipe everything but im not using the same recovery so i cant remember what the options say on rouge so just wipe everything for now) then flash the rom with "install for .zip"(and anything that goes with it i.e gapps or another kernel----- depends on the rom your using) and then just to be safe wipe the devlik cache again and reboot.

hipertec said:
THank you for the link. I tried to install easyflasher but I think when I installed oneclickrecovery, it installed Rogue XM Team which I think is my flasher (instead of easyflasher)..when I rebooted with VOL_DN & PWR, then VOL-UP, it went to Rogue XM Team instead of easyflasher.
So can I just download the ROM into my SD Card and use the menu from the Rogue "install from .zip file"?
Is this the method?
I know Im half way there but need guidence for finish the rest. thanks for your help.
Click to expand...
Click to collapse
I would STRONGLY suggest switching to TWRP. Rogue will work for now, but if you flash updates to this ROM, the new file structure for 4.2 will cause your /sdcard/ to end up in the /sdcard/0/ directory, and after another flash it will be /sdcard/0/0/. You can move the files, but IMO TWRP is much better anyway (it can flash from internal and external storage).
You can install GooManager and choose to install open recoveryscript from the menu, or you can use the dd command and a terminal emulator to install TWRP:
First, download the twrp blob from here: http://techerrata.com/browse/twrp2/tf101
Rename the 2.3.2.3 blob to TWRP.blob
Method 1
Open a terminal emulator.
Code:
$ [B]su[/B]
# [B]dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4[/B]
# [B]reboot[/B]
It is important to just do a reboot, if you reboot to recovery immediately it WILL NOT update the recovery. Upon reboot, you should see a progress indicator at the Eee Pad screen. Feel free to reboot to recovery after this (even before it boots).​

I strongly recommend reading the post by Fredurco in the link he provided. As a matter of fact, read the first three posts. These are the most detailed instructions for any ROM I've ever seen and believe me, I've seen more than a few. Take your time and just follow those directions to the letter and you will be fine.

frederuco said:
IMO TWRP is much better anyway (it can flash from internal and external storage).
Click to expand...
Click to collapse
I agree, rogue can also flash from internal and external, but twrp is the best, I need to update PERI to include it...

Thing O Doom said:
I agree, rogue can also flash from internal and external, but twrp is the best, I need to update PERI to include it...
Click to expand...
Click to collapse
Yeah, get crackin!

Thanks everyone for your help. Got it updated to eos4. Is there another ROM that is fast and stable?
Sent from my Transformer TF101 using xda app-developers app

hipertec said:
Thanks everyone for your help. Got it updated to eos4. Is there another ROM that is fast and stable?
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
Nothing as fast, eos3 in my opinion is the stablest custom ROM I've used but I can't move away from eos4, plus when timduru release the cornerstone build my tablet is gonna get some major use.

hipertec said:
Thanks everyone for your help. Got it updated to eos4. Is there another ROM that is fast and stable?
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
JoinTheRealms said:
Nothing as fast, eos3 in my opinion is the stablest custom ROM I've used but I can't move away from eos4, plus when timduru release the cornerstone build my tablet is gonna get some major use.
Click to expand...
Click to collapse
I agree! EOS 4 IMO is the most usable and stable 4.2 build. My biggest complaint with the CM10.1 build was the touchpad disable was not working. It is still a great ROM otherwise and pretty stable.
As far as 4.1 ROMs, EOS 3 is solid, and so is the CM10/PananoidAndroid hybrid.
I am definitely itching for some cornerstone love!

I use liquidsmooth currently, and it's my new favorite, since everything works. I haven't found or noticed any bugs, which is rare.
EOS4 is also good, but I just don't like the feel of it oddly. Very well built and worth a shot though.

Hi Fred! Dug my TF101 out of moth balls and put on EOS4.
Had some trouble with the drivers, So I ended up using 1 from column A, 2 from column B:silly:
end result, got my drivers, APX mode going, (cross between oneclickrecovery, easyflash, nvFlash, Universal Naked Drivers),
Finally got twrp on and flashed superuser
got twrp-goo manager to update it, Flashed EOS4- saw updated recovery did not stick, finished the flash, updated twrp again, reflashed eos4- saw twrp update did stick this time, and now get to play with the TF 101 all over again!
Everything old is new again!
Thanks Fred! Your post on the TF forum was great, and XDA supplemented what wasn't working for me!! Great teamwork:victory:

Thanks to Fred's excellent tuts, I was able to easily get TWRP installed and rooted (although it did kill my WiFi somehow, which I'm hoping will be solved with a different ROM), but have a dilemma:
Not to hijack (didn't see the point of starting a new thread about the same thing, but I will if you guys want me to) but which ROM will give the best video performance? I'm not trying to do 1080 stuff or anything naive like that, but I would at least like to be able to watch some of the lower quality 720p stuff (NPW's releases are very good) without stuttering or syncing issues.
Note: I'm not trying to do everything with this tablet and overall I'm VERY satisfied with the overall performance and wouldn't even be tinkering with it at all (I've had it for over a year on stock ICS) if I didn't travel a lot and use it to watch movies on the go. I only use this tablet for gaming, surfing, movies and lots of document viewing (PDF, MSOffice, etc). I don't care about GPS or the camera. I have a phone for that. However, I don't have the time or means to be constantly reflashing this thing because WiFi drops out every 30 minutes or something like that.
Basically, I'm looking for the ROM with the best combo of:
- Stability
- Respectable HD-ish video playback
I'm not a total Android noob. I spent many hours tinkering with my old Nook Color back in the day, so no worries there. I'm just looking for reliable video playback on the go. I've been looking at Android Revolution HD to preserve the ASUS File Manager and things like that, but really haven't seen anything definitive about video playback improvements. I'm open to moving up to JB, but its not a burning desire or anything.
Thanks!

LongbowFoSho said:
Thanks to Fred's excellent tuts, I was able to easily get TWRP installed and rooted (although it did kill my WiFi somehow, which I'm hoping will be solved with a different ROM), but have a dilemma:
Not to hijack (didn't see the point of starting a new thread about the same thing, but I will if you guys want me to) but which ROM will give the best video performance? I'm not trying to do 1080 stuff or anything naive like that, but I would at least like to be able to watch some of the lower quality 720p stuff (NPW's releases are very good) without stuttering or syncing issues.
Note: I'm not trying to do everything with this tablet and overall I'm VERY satisfied with the overall performance and wouldn't even be tinkering with it at all (I've had it for over a year on stock ICS) if I didn't travel a lot and use it to watch movies on the go. I only use this tablet for gaming, surfing, movies and lots of document viewing (PDF, MSOffice, etc). I don't care about GPS or the camera. I have a phone for that. However, I don't have the time or means to be constantly reflashing this thing because WiFi drops out every 30 minutes or something like that.
Basically, I'm looking for the ROM with the best combo of:
- Stability
- Respectable HD-ish video playback
I'm not a total Android noob. I spent many hours tinkering with my old Nook Color back in the day, so no worries there. I'm just looking for reliable video playback on the go. I've been looking at Android Revolution HD to preserve the ASUS File Manager and things like that, but really haven't seen anything definitive about video playback improvements. I'm open to moving up to JB, but its not a burning desire or anything.
Thanks!
Click to expand...
Click to collapse
I guess I am not sure what is causing your WiFi stability issues. I have no problems with the EOS 4 ROM and WiFi. It never drops out on me. It is perfectly stable, and I can play 720p H264 23.94 FPS mkv files with no issues using MX player.
Before I ran EOS 4, I was running the ParanoidAndroid/CM10 Hybrid ROM and it was just as stable and fast.
If you are having WiFi issues, did you do all the wipes (Cache, Davlik, System, Factory Reset) before flashing the ROM? If not, then that is probably where the WiFi issue is (settings from your previous ICS ROM still present on the data partition).

Disregard the bit about the WiFi. I disconnected and reconnected to my network and all is well.
It sounds like EOS4 is the only ROM that is still consistently updated. I'll give it a shot and see how it goes.
Thanks!

LongbowFoSho said:
Disregard the bit about the WiFi. I disconnected and reconnected to my network and all is well.
It sounds like EOS4 is the only ROM that is still consistently updated. I'll give it a shot and see how it goes.
Thanks!
Click to expand...
Click to collapse
EOS4 and the CM10.1 No-Name are the only ones getting regular updates.

Thanks for the quick responses. EOS 4 is installed and process of redownloading all my apps. Now I just need to test out some video. I'm testing it without the OC kernel first, just for fun.

If you wanna see more in-depth which rom is better, I recommend a little app called Antutu benchmark, it'll give your current setup a score depending on how fast it does things like 3d renderind, sd card reading and battery performance

I might be in the minority with this opinion, but after some tinkering I'm not all that convinced that EOS is any faster than the stock ROM from a general usability standpoint (even with the latest KAT kernel), but the video is definitely improved, so I'll keep it as my "daily driver".
Thanks for the help, guys!