Related
Hello all....I was messing around with my X trying to switch over from DarkSlide 4.2 to GB. However, when I flashed GB in clockwork, it would not move past the boot screen and I couldn't recover into cwm recovery. I have soft bricked before, so I went and got the 2.2 SBF for .340 and loaded it back to stock ....problem is, I'm out of the country right now, so I can't exactly activate my phone. I was curious if there are any other Roms that have been converted to SBF so I can load them, or am I screwed until I get back to the States. Thanks in advance.
Dude to bad you didnt just do a data wipe/ factory reset before SBFing your phone, if you are on stock you dont have to activate your phone to flash a rom, hopefully you have z4root and dxbootstrap on your phones sd card, if so root your phone, boot into clockwork and flash a rom or nandroid. maybe you can access a pc with internet and download z4root and dxbootstrap if you dont have the apks stored on your sdcard
i already have z4 and bootstrap. rooting is not the issue. my issue is i can't activate it, so it won't let me past the setup screen from the stock rom. i have backups of all my apps, so i'm not worried about it...this is not the first time i've soft bricked a phone i know for the D1 (a different beast all together) you could flash some roms via rsd with an SBF. I'm just curious if there any for the X. Also, I did wipe data/cache
To my knowledge there is no other type of sbf besides stock for the dx. I believe this is because of the locked bootloader not allowing us to modify certain parts of our phone
I think if you are at the android screen you can start in the top right corner and make a swipe to all four corners to get into the phone without activating it. If I can find the link I will post it.
Update: start in the top left and swipe your finger in a clockwise motion touching each corner. That will get you past the activation part and allow you to use the phone like normal. Obviously you won't have a cellular connection, but wifi will work.
Sent from my DROIDX using XDA App
jgraham4598 said:
I think if you are at the android screen you can start in the top right corner and make a swipe to all four corners to get into the phone without activating it. If I can find the link I will post it.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Tap all four corners starting from the top left and going clockwise
So Top left, top right, bottom right, bottom left
Awesome...thanks guys.
I had my Iconia working well with OTA 3.1 unrooted and it all started when I decided to update it 3.2 and then root it but after updating i realised that there was no root for 3.2 so i searched for a way to do so and i found the "downgrade to 3.0.1(unstable) then root" way and followed it and got my Iconia with the 3.0.1(unstable) downgrade and rooted it with "gingerbreak" and downloaded "acer recovery installer" and got "virtuous galaxy 1.0.5" rom and that's when every thing went wrong after i flashed it with the recovery mode it booted but was unusable it kept on force closing and lagging and nothing worked it didn't even respond to my touches.
I reseted the device many times but in vain so i decided to reflash the downgrade file "3.0.1(unstable)" and remove the root and re-update to 3.2 as if nothing happened but just when i reflashed the downgrade it booted but didn't even give me the chance to do anything it became really "unstable" it kept on force closing the launcher as if i'm stuck in a loop and i don't know what to do as i don't have that much knowledge so i left it closed as it is (so as not to ruin it more ) and want anyone to PLZ HELP me to return back to stock 3.2 (totally stock as if i just bought it) with no roms or root .
Thanks in advance to anyone who did or didn't help
I solved it i managed to get to settings in the 1 second interval between the successive force closes and then pressed factory default and like magic every thing was good as new at last.
Thanks to everybody helped me ...... no one even replied
Well 46 minutes isn't that long in forum-reply terms
Anyways. Good you got it fixed. Did you install Clockworkmod from Acer Recovery Installer, a full wipe followed by a fresh ROM from here flashed using CWM would likely have fixed it.
i think your mistake is , you didnt wipe data before lashing virtuous galaxy
interqd said:
i think your mistake is , you didnt wipe data before lashing virtuous galaxy
Click to expand...
Click to collapse
Exactly but I learned the lesson and now I rooted and wiped and got everything right with virtuous galaxy rom flashed and working
Peter Baher said:
I solved it i managed to get to settings in the 1 second interval between the successive force closes and then pressed factory default and like magic every thing was good as new at last.
Thanks to everybody helped me ...... no one even replied
Click to expand...
Click to collapse
Next time, you can reset your tablet by going: power button + right volume button (when held landscape with power button on top left corner)
power button + left volume button boots to recovery.
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?
Ok, so everything was going fine and dandy so i decided to root my nexus 7. it was amazing, i was able to over/underclock. Then i remembered an app that i had called chainfire3d that allows you to force certain things on the gpu such as anti aliasing and full 32 bit color on some things. anyways after an install it needed to reboot. once rebooted, it just sits at the google screen with the little lock thats open at the bottom. going into bootloader by holding down all the buttons gets me to the screen but then it freezes. cant boot, cant get into bootloader. any help?
Thanks in advance.
jombo2323 said:
Ok, so everything was going fine and dandy so i decided to root my nexus 7. it was amazing, i was able to over/underclock. Then i remembered an app that i had called chainfire3d that allows you to force certain things on the gpu such as anti aliasing and full 32 bit color on some things. anyways after an install it needed to reboot. once rebooted, it just sits at the google screen with the little lock thats open at the bottom. going into bootloader by holding down all the buttons gets me to the screen but then it freezes. cant boot, cant get into bootloader. any help?
Thanks in advance.
Click to expand...
Click to collapse
sounds like you need to go to the android development list and look for the unbrick thread that has directions to put the original os back on. Then reflash your favorite recovery/rom..etc.
jinside said:
sounds like you need to go to the android development list and look for the unbrick thread that has directions to put the original os back on. Then reflash your favorite recovery/rom..etc.
Click to expand...
Click to collapse
ok, but. im no android fixing expert, but i know my way around it really well. anyways, cant you do nothing if you cant at least get to the recovery screen?!
i have no idea.\
*EDIT
Finally got recovery to work by lots of reboots and was able to reflash the whole thing. i guess let this be a lesson to people trying chainfire.
Hi everyone.
My father recently bought himself a Nook simple touch running 1.20 firmware on the promise that I would root it for him so he could borrow books from the local library using overdrive and also use Kindle. I have done similar with many devices in the past - installing custom firmware on Android tablets, jailbreaking iPHones (sorry to swear on here ) etc etc.
I read how easy it was to do and thought I would have no problems. Boy was I wrong!
I downloaded touchnooter 2.1.31 and wrote it to a micro sd card using a built in card reader on the PC and Win32 disc imager.
I put the card in the Nook and powered up. Everything happened as it should, the screen flashed to black etc etc. I took the card out and powered up. I got the "Your NOOK is starting up" message and then it just froze on that screen.
Holding the power and N button down reset it but it just went back to that screen. Eventually, though, for some reason on one of these cycles it reset itself.
So I set the machine up, and started again.
This time I restarted the whole process from scratch, put the card in the machine and powered up. This time, the screen never flashed to black at all, and I am not stuck at the "Your NOOK is starting up" screen. Trouble is, this time holding the power and n button down do nothing (they did a few times, but now nothing) and the machine seems completely dead.
My Dad aint going to be too happy if I've killed his Nook - so can anyone help me?
Or am I beyond help (don't answer that, )
Thanks in advance.
You neglect to mention taking a backup before your attempts at rooting; are we to imply that you don't have one you can restore from?
cowbutt said:
You neglect to mention taking a backup before your attempts at rooting; are we to imply that you don't have one you can restore from?
Click to expand...
Click to collapse
Thanks for the reply. Oh dear. I read three different guides and not one of them mentioned that you could back up (I presume the Nook firmware itself) first?
You could preform a factory reset using the 6 failed boots method, I cant post links yet but if you do a search for "nook simple touch factory reset" you should instructions at nookdevs.
The NST has a nice feature of keeping a factory recovery partition that stores a factory.zip and will restore the NST using the above method.
Sometimes it takes quite a few tries for this to work, the timing has to be right. It will wipe everything (except the factory partition of course) and restore the nook to the how it was out of the box.
@norwichred: you might want to consider using the Touch-Formatter recovery tool http://forum.xda-developers.com/showthread.php?t=1475613. I had used it successfully to recover from a failed attempt at routing my NST.
Brick
Try holding the left and right buttons down Bottom ones at the sides of the screen when booting.
This should put it into restore to defaults mode.
This helped when I tried flashing with touchnooter. Ended up going back to defaults and then rooted with Nook Manager which went faultless.
norwichred said:
Hi everyone.
My father recently bought himself a Nook simple touch running 1.20 firmware on the promise that I would root it for him so he could borrow books from the local library using overdrive and also use Kindle. I have done similar with many devices in the past - installing custom firmware on Android tablets, jailbreaking iPHones (sorry to swear on here ) etc etc.
I read how easy it was to do and thought I would have no problems. Boy was I wrong!
I downloaded touchnooter 2.1.31 and wrote it to a micro sd card using a built in card reader on the PC and Win32 disc imager.
I put the card in the Nook and powered up. Everything happened as it should, the screen flashed to black etc etc. I took the card out and powered up. I got the "Your NOOK is starting up" message and then it just froze on that screen.
Holding the power and N button down reset it but it just went back to that screen. Eventually, though, for some reason on one of these cycles it reset itself.
So I set the machine up, and started again.
This time I restarted the whole process from scratch, put the card in the machine and powered up. This time, the screen never flashed to black at all, and I am not stuck at the "Your NOOK is starting up" screen. Trouble is, this time holding the power and n button down do nothing (they did a few times, but now nothing) and the machine seems completely dead.
My Dad aint going to be too happy if I've killed his Nook - so can anyone help me?
Or am I beyond help (don't answer that, )
Thanks in advance.
Click to expand...
Click to collapse
Ok, firstly TouchNooter doesn't work with v1.20, you need to use GlowNooter. Don't worry, I found this out the hard way too. I actually found NookManager + GAPPSAttack gave the cleanest results.
Try holding down the power button for varying amounts of time, between 0 and 15 seconds, eventually you'll get it to reboot. You don't need to press the n button.
To get back to v1.21 do this - http://forum.xda-developers.com/showpost.php?p=41296148&postcount=2
noodles2k said:
Ok, firstly TouchNooter doesn't work with v1.20, you need to use GlowNooter. Don't worry, I found this out the hard way too. I actually found NookManager + GAPPSAttack gave the cleanest results.
Try holding down the power button for varying amounts of time, between 0 and 15 seconds, eventually you'll get it to reboot. You don't need to press the n button.
To get back to v1.21 do this - http://forum.xda-developers.com/showpost.php?p=41296148&postcount=2
Click to expand...
Click to collapse
Guys - thank you SO much for your replies so far.
I have managed to reset the nook using your methods above, and am about to try again. I'll look into nook manager and glownooter. Is there a general opinion on which is better?
now , download the package from BN website (1.2.1) and apply manual update then ur nook will be 1.2.1 version then take Back up and make sure about 1.9GB and save it in safe place , and then play with ur nook as much as u want
PS: if u want root 1.2.1 nook software then use Nook Manager also if upgrade steps u cant get , tell me and i will replay u shortly
TC about ur father's Nook
speedman2202 said:
now , download the package from BN website (1.2.1) and apply manual update then ur nook will be 1.2.1 version then take Back up and make sure about 1.9GB and save it in safe place , and then play with ur nook as much as u want
PS: if u want root 1.2.1 nook software then use Nook Manager also if upgrade steps u cant get , tell me and i will replay u shortly
TC about ur father's Nook
Click to expand...
Click to collapse
Ok so I have taken a backup and rooted using nook manager. I am waiting for his google password (he's changed it without telling me) so I can install GAPPSattack. Will this give me a nice desktop? At the moment I have a file explorer view and he won't understand that.
norwichred said:
Ok so I have taken a backup and rooted using nook manager. I am waiting for his google password (he's changed it without telling me) so I can install GAPPSattack. Will this give me a nice desktop? At the moment I have a file explorer view and he won't understand that.
Click to expand...
Click to collapse
Try ADW Launcher with this theme
or this theme depending on the background colour.
If you don't like the icons you can turn them off under Themes/Customize.
The other launcher worth a try is 7 Launcher.
I've attached black and white image you might find useful.
well, it's all rooted and working now I am very grateful to ALL who have contributed to help me out here. Few things I'm not overly happy with so want to try and sort this out for him before I give it to him - want an easy way for him to get to a list of apps or to the nook homescreen using buttons but apart from that it's great.
Thanks again!
norwichred said:
well, it's all rooted and working now I am very grateful to ALL who have contributed to help me out here. Few things I'm not overly happy with so want to try and sort this out for him before I give it to him - want an easy way for him to get to a list of apps or to the nook homescreen using buttons but apart from that it's great.
Thanks again!
Click to expand...
Click to collapse
for me
i had ADW launcher and Button savior that let me navigate to home screen in any time when i be on any app .... so try both and for ADW launcher home screen , easy to use and u can view all apps like u have android phone