Related
VEGAn RC1 Ginger Edition was loaded and working fine for almost two weeks.
Then I powered up and it would get stuck on the G-TABDEVs splash screen.....
Here is what I can do:
I can power up and the tab will go past the viewsonic birds screen to the next splash screen (G-TABDEVS) and will stay there indefinately.
I can power up into Clockworkmod 2.5.1.1. 0.8 (all soft buttons work and I can scroll through the choices with the vol switch just fine)
I can wipe cache partition
I can apply sd card:update.zip (only because I still have VEGAn RC1 GE .zip on my device)
I can mount the USB drive (drive is recognised on my computer running win XP)
I can apply NVflash to the device (did this to get access to CWM by changing part #9)
What I can't do:
I can not transfer large files files from my computer to the tablet (I can make a directory and transfer small files only maybe 100 kb or less) Any time I try to transfer a larger file (a ROM or other) I get an I/O error.
I can not partition the SD card (internal storage),
Wide data/factory reset,
Wipe Delvik cache,
it just hangs indefinately with each of the above.
I have spent counless hours searching through all the great information on XDA and can not find any instance like mine.
I don't think it has been bricked because of what I still can access, although there still seems to be something "limiting" my actions.
Has anyone experienced this? and more importantly.... Can anyone HELP????
you can boot into clockwork but cant use the factory reset option there? if its hanging how long did you let it wait? id try a reset and let it sit for 5-10 mins to see if its really doing something or just mucking around.
you make a restore file (backup of your previously installed rom on your tablet)?
if the rom is still on your tablet try reinstalling it. then after installing try factory reset before rebooting. if you cant reset try reboot then reset.
the G-Tabdevs screen staying there indefinitely is because it needs to be reset. so you just have to figure out how to reset it.
Great! I totally did not realize that it took that long to reset. I will try that later tonight and post my results.
OK, I tried using "wipe data/factory reset" and it just hung. I let it sit for 20 minutes (just in case).
Then tried "partition SD card (2048,0) and let it run, again for 20 minutes and it just hung.
Still very frustrated.
What are my options at this point?
I need to follow this thread b/c I have the same problem. Last night shut down fine and this morning went to power back on and I get the birds and then it gets stuck in the next load screen. I reinstalled update.zip but no dice. Any ideas?
Make sure all the partition are active, wipe dalvik, try reflashing the same rom over and fix permission
For such strange issue you can alway use the nvflash format utility but not before having performed an nvflash backup then use bekit images to bring back the tablet to life. You can also make a clockwork backup
Backup http://forum.xda-developers.com/showthread.php?t=1010659 (if something goes really wrong it can help, the .bct is what you want to keep at least)
Be warned that backup may have issue if you got flash bad block, this is not a critical issue
Format http://forum.xda-developers.com/showthread.php?t=974422
Restore http://forum.xda-developers.com/showthread.php?t=861950
make sure you follow instruction
This thread has link to everything!
http://forum.xda-developers.com/showthread.php?t=1026660
Keep in mind that NVFLASH only restore or erase about 300MB of the 2GB out of the 16GB you can write to.
This is in no way a FULL tablet reset. It is however a dangerous tool above application are tested and proven, some older thread may have nvflash command that can be dangerous.
That is great information.
I have used the format flash, then Nvflash.
flashes work fine, but same issue. Stuck at G-tablet splash screen.
I still can not load update.zip because I can not transfer any large files to the tab when it is mounted.
Any time I try and transfer a file greater than about 100k I get an error that states "can not copy file due to an I/O error"
Really disheartening........
I have a problem. After finally talkling myself into rooting my phone I was able to pull it off sucessfully, almost. See I havent had service on my phone for 3 months. In that time I have enjoyed using it for wifi, e-mail etc. The phone always kept saying not provisioned a bunch of times but always kept functioning.
I installed cyanogen 7.0.3 (Ithink) last night and after it booted up I said "great I didnt break it" but right in the beginng when I tried to sign into my gmail (at the time already logged into my dads wifi) It wouldnt recognize that I am signed into a wifi. it just kept asking about a data plan. I dont get it.
1 year old Aria
Try going to Settings > Wireless & network settings > Mobile networks, and unchecking "Data enabled".
That was one of the first things I check. I got no idea why it won’t let me jump on internet or market even though I will see on my phone that I am connected to a strong wifi source. Then I'll use rom manager to restore back to 2.1 and my wifi will suddenly work again. It’s driving me nuts because I am having fun with cyanogen mod but the I’ll revert back to 2.1 because I have no internet
Try bypassing ROM Manager. In general there are all sorts of issues that can occur if you use ROM Manager to get to Clockworkmod on S-ON devices like the Aria. I'm not saying this is the actual cause of your problem, but it's one thing you can try.
Shut the phone off completely then do volume down + power button to get into Clockworkmod and try installing CM7 again.
Also, make sure you are doing a full wipe when you upgrade to CM7.0.3. You can't retain any settings from previous versions.
1) Boot into Clockworkmod
2) Wipe data/factory reset
3) Wipe cache partition
4) Advanced > Wipe dalvik cache
5) Partitions menu > format system
6) Install Cyanogenmod zip from sdcard
7) Install Google Apps zip from sdcard
8) Reboot
Parden my newb status for asking I'm learning quick. but after I go ahead with wiping all my data etc. do I keep super user status or do I have to download various boot drivers and root my phone again?
I also just noticed that as my phone was booting up from clockwork recovery it said at the end
"no sd-ext found. skipping backup of sd-ext" Maybe that could have been the prob?
Last question is I just bought a 8 GB sd a couple days ago, should I partition it while I am doing all this? Thanks alot for the help
BeanTown_HTC said:
Parden my newb status for asking I'm learning quick. but after I go ahead with wiping all my data etc. do I keep super user status or do I have to download various boot drivers and root my phone again?
Click to expand...
Click to collapse
Yes you will still be rooted. Clockworkmod will still be installed on your phone (which is what you use to install ROMs), and the ROMs that are available on this site (including CM7.0.3) are already pre-rooted. You shouldn't ever have to use Unrevoked again.
I also just noticed that as my phone was booting up from clockwork recovery it said at the end
"no sd-ext found. skipping backup of sd-ext" Maybe that could have been the prob?
Last question is I just bought a 8 GB sd a couple days ago, should I partition it while I am doing all this? Thanks alot for the help
Click to expand...
Click to collapse
That just means you don't have an ext partition on the SD card. It's normal.
If you partition your SD card and dedicate a portion of it to an ext partition, you can use it for additional app installation space. The Aria's internal memory is somewhat limited so this can be helpful if you like to use a lot of different apps. You don't have to partition the SD card before installing the ROM, although doing it before installing a clean ROM might save you some trouble of having to back up anything from the SD card.
You don't HAVE to partition the card if you don't want to. It's only if you want some extra app space or not.
Great it worked. My WIFI agnolidges me. That was wierd.
Thanks alot for the help.
Hello people. I have a 32 GB Wi-Fi only Tab, running seraphimserapis' CM9 preview kang.
I'll dive right into things here. Earlier today, I flashed the above ROM, everything went perfectly, booted up just fine, and got all my apps back up and running. I was using my tab fine for the entire day with no problems to speak of. Later in the day, I began transferring some misc. files (documents, music, etc) to my internal SD card via MTP USB transfer. After the transfer was complete, I unplugged my tab, and went on my merry way. The next time I booted up, everything began FCing on me, and nearly every app I tried to open immediately FCed. Thinking it was a temporary bug, I rebooted my tab, but the same problem persisted, multiple different processes fced upon boot, and almost all my apps would fc as soon as I opened them. After trying a few more times, I gave up, and booted back into CWM (which I can do perfectly fine), cleared cahce and delvik cache, and did a factory reset. This however,seemed to only augment the problem. Upon booting up (after doing that initial tab setup), trebuchet FCes (in a "FC loop", as it continually tries to open), and the tablet is completely unusable. I have tried wiping cache, reformatting and rebooting several times, each time with the same result
I am able to get into settings however, by plugging in the tab, and clicking USB debugging (for whatever reason, settings does not FC), and am able to connect to my internal memory via MTP. When the tab pops up in my computer, it says I have 25 GB out of 28 available GB, but when I click on the folder, it is completely empty. If i try to move files over to my tab, or even create a new folder, I get an error message saying "the device has stopped responding or has been removed". (Pictures below)
http://img141.imageshack.us/img141/9855/75464072.jpg
http://img190.imageshack.us/img190/3395/61277691.jpg
I do not believe this is a problem with the rom for two reasons. (1) no one else has had this problem (to my knowledge), and (2) it was working fine the whole day, until i did that file transfer (that being said, this is my own amateur opinion, which you may choose to completely disregard it in your diagnosis). I am 99% sure I didn't unplug the tab while files were still transferring, but I did not unmount the storage or eject it or anything fancy of that nature before I unplugged it.
My question is, is there any way I can somehow reformat the internal memory of my tab? Otherwise, is there some other possible fix you experts may possibly have? Or am I screwed?
I apologize in advance if you ask me to try something and I cant respond promptly. Its 3AM here and i need to wake up early tomorrow. Thank you in advance
Edit:
I am quite convinced there is some kind of internal memory corruption problem here, but I really am not an expert enough to know for certain. The tablet still boots up fine, but is completely unusable as trebuchet fc loops 90% of the time i reboot the tab. Obviously, the entire thing isnt trashed as it appears to boot and get into the system fine, but I it's still completely unusable from that point on.
I have tried formatting the /data and /cache partitions of the internal memory to no avail. I would try formatting /system, but from my understanding, thats only advisable if you are able to flash a new rom after formatting, but if i cannot write into my internal memory, then there's no way i can flash a new rom. Conveniently enough, I deleted the .zip file for the rom off my internal sd, and i cannot access my clockworkmod recovery from CWM (gives an error, I don't think that would have worked anyway) since the internal sd is (i believe) corrupted. I also tried mounting as USB from CWM, and that also gives an error...
I am clean out of ideas. I'm not sure if this is a completely unfixable problem, or if self repairing is well within the realm of possibility. If someone can shed some light on me that would REALLY be appreciated. Otherwise i might have to send it back to sammy (still under warranty), which i dont mind doing, but if they boot it to find an ICS rom, they probably wont be so keen to repair it...perhaps there's a way to brick it further so they can't tell?
UPDATE 2:
Problem fixed! I still don't have a clue as to what the problem was, but thankfully I managed to escape out of this one. I tried pushing a new ROM via adb, and it worked (apparently), but this just forced me into a boot loop (never hit the homescreen).
As a last ditch effort I pushed the stock ROM, and completely removed root, and it worked. I can now boot up past the spash screen without all all my processes crashing. Really a strange issue, I have my theories, but they're probably blatanly wrong so I'll just keep them to myself. Im just glad I don't have to send it back to sammy... I plan to re-root shortly. I am confident I will get no further issues.
Even though no one helped me directly, it was thanks to the plethora of information available on this forum that I was able to resolve my issue...and for some reason, making a thread where I'm just talking to myself helps a bit too...maybe im just weird. Anyway if anyone's reading this, thanks again xda
.......HOW??
brennanyama said:
UPDATE 2:
Problem fixed! I still don't have a clue as to what the problem was, but thankfully I managed to escape out of this one. I tried pushing a new ROM via adb, and it worked (apparently), but this just forced me into a boot loop (never hit the homescreen).
As a last ditch effort I pushed the stock ROM, and completely removed root, and it worked. I can now boot up past the spash screen without all all my processes crashing. Really a strange issue, I have my theories, but they're probably blatanly wrong so I'll just keep them to myself. Im just glad I don't have to send it back to sammy... I plan to re-root shortly. I am confident I will get no further issues.
Even though no one helped me directly, it was thanks to the plethora of information available on this forum that I was able to resolve my issue...and for some reason, making a thread where I'm just talking to myself helps a bit too...maybe im just weird. Anyway if anyone's reading this, thanks again xda
Click to expand...
Click to collapse
I'm hoping you see this reply as its been quite a while since you've had the issue. I'm working with a Galaxy S2 Skyrocket with the same intenal memory corruption/ files system corruption you were facing. I followed what you did regarding push a rom thru adb and that worked for me, but my question is, how did you get the roms to successfully write if you couldnt write to internal memory? My system is mounted as read only apparently and locked itself with whatever I had on there on August 28th. No matter how many times I format, erase, or wipe it, it returns to the same state as if its a deep lock on it.
Hello,
I've installed CM internal to (2) NT 16GBs without incident, and I got stumbled by the n button not working with 1.4.1 that was on my third. Ultimately - I downgraded to 1.4.0, installed CM7, and then did the dumb thing.
I meant to hit wipe data and cache, and I clicked factory reset in CWM. (And at this point - it is stuck in a state where I can boot to CWM - but cannot get CM7 to boot in any form from the internal rom).
I attempted the following
1) acclaim restore (just tried didn't do anything)
2) backup / restore from alternate nook Tablet 16Gb (man this seemed promising ...)
3) couple of the different unbrick scenarios - but I don't have adb, and it seems like windows 7 is not a happy camper with nook usb devices, (and adb isn't happy either.)
4) meghd00t restores (couple of different variations.)
does anyone have any starter threads that I should start walking down for the same stuff - I have browsed, and it's been a couple of hours and I'm exhausted. will poke back in tommorow, and will get this thing plugged into a linux host.
It didn't seem like adb could be so hard ...
--Adrian
Hmmm interesting... ok first of all doing this "I meant to hit wipe data and cache, and I clicked factory reset in CWM" is not dumb is ok to do but is not good signal the hang actually is very weird. Maybe all you have is a corrupted cwm recovery flash. Now be explicit if you indeed could try some unbrick methods succesfully (the ones running from sdcard) and what methods exactly did you try.
~ Veronica
things I've tried - part 1
1) just try to restore to factory with acclaim_update.zip on non-booting sdcard , (this is the 1.4.0 image) - I get the grey n, a flash of white - (like it's going to boot), and that that "please restart your device and try again..."
(This worked when it was factory), but it seems like the logic to check the sd card and start to recover isn't working.
2) Tried the thread here - http://forum.xda-developers.com/showthread.php?t=1562130 - meghd00tr4-sdimg.zip boots, but first time - get red reverse highlighted line - "booti: bad boot image magic in memory" - s5 in the upper left corner of the cyanoboot screen, and the n button doesn't seem to do anything.
3) same thread different image - repart.img, this runs fine- and after about 30 seconds of boot, I get a green check, (waited a full (2) minutes after that green check before I unplugged it.) - same message after boot.
4) full restore of nook tablet from current good cm7 image (and this is the one that most concerns me) - NT16gbV4_6 based cwm v5.5.04 - attempting restore of backed up alternate nook tablet - and the exact same thing happens at boot - does the image not touch partions that aren't related to the root install -(this seems like maybe there is something the bootloader is looking for in the image that isn't right, and it wedges?)
I am going to work on getting an adb setup going that works and then start working down a couple of fix recovery scenarios today / tonight.
It doesn't seem like this is unrecoverable - and the worst part is -I had cm7 booting fine for a couple of reboots, and then something went awry.
--Adrian
as I think about this ...
I do have (2) differnt backups, and I wonder if that restore was the wrong thing to do.
I got to thinking this as I saw the restore of the .android_secure file, from the ALTERNATE nook. I have the backup from the 1.4.0 "original working" image of this nook before the cm 7 issues- but I put it on an SD card that is safetly out of my reach. (In a friends cell phone.)
I think an easy thing will be to restore that backup as another test.
-Adrian
peril said:
I do have (2) differnt backups, and I wonder if that restore was the wrong thing to do.
I got to thinking this as I saw the restore of the .android_secure file, from the ALTERNATE nook. I have the backup from the 1.4.0 "original working" image of this nook before the cm 7 issues- but I put it on an SD card that is safetly out of my reach. (In a friends cell phone.)
I think an easy thing will be to restore that backup as another test.
-Adrian
Click to expand...
Click to collapse
Right, try that first, dont attempt anything advanced yet. Your problem could be solved easily
Just to make sure you flashed cwm from @Indirect app?
~ Veronica
Sent from my Nook Tablet using xda premium
Wait, can you boot into a CM7 SD ROM? From there you could try reflashing recovery.
Sent from my R800x
FIXED
I used this method - and I was good to go.
http://forum.xda-developers.com/showthread.php?t=1470910
In one of the flashes - must have hit the power prior to something being complete with the recovery.
thanks all for your support - and really appreciate the time in the forum. I'm going to put together a torrent with the recovery stuff in it, and make sure it's available as my little part. (Give me a day or so.)
Thanks again.
--Adrian
The problem with that is that you will lose your original serial ID's and MAC address if you didnt backup your rom partition (mmcblk0p5) first so if you use B&N services you wont be able to register after flash any stock rom.
~ Veronica
Sent from my Nook Tablet using xda premium
I also screwed up...Reverting to 1.4.0
Tried to revert to 1.4.0, and followed all instructions as showned on a youtube video. Unfortunately, as it was reverting back to older version as soon as it finished the process - the tablet wouldn't start back up. Did any one ever have this happen to them.. Fortunately, I had just bought today at WalMart. So, I'm going to replace it...
Was just curious, if it ever happened to any one. If so what did I possibly do wrong....
mr_truevision said:
Tried to revert to 1.4.0, and followed all instructions as showned on a youtube video. Unfortunately, as it was reverting back to older version as soon as it finished the process - the tablet wouldn't start back up. Did any one ever have this happen to them.. Fortunately, I had just bought today at WalMart. So, I'm going to replace it...
Was just curious, if it ever happened to any one. If so what did I possibly do wrong....
Click to expand...
Click to collapse
Hmm i think you have a 8GB Nook Tablet and the acclaim_update.zip is only for 16GB NT.
~ Veronica
ubuntu recovery.
This was strictly for CM7. I have no problem with being locked out of the B&N services. (I use the nook application for that access.)
Wish I would have known the serial number before / after. I was able to login to my B&N account after 1.4.0 was restored from ubuntu.
--Adrian
lavero.burgos said:
The problem with that is that you will lose your original serial ID's and MAC address if you didnt backup your rom partition (mmcblk0p5) first so if you use B&N services you wont be able to register after flash any stock rom.
~ Veronica
Sent from my Nook Tablet using xda premium
Click to expand...
Click to collapse
Hi,
I am using barnes and noble nook tablet, flashed custom recovery cwm based recovery v 6.0.1.9 and the latest nightly : cm-10.1-20130514-NIGHTLY-acclaim.zip, latest gapps: gapps-jb-20130301-signed.zip. I am having few problems, hope I can get some resolution here.
Firstly I am unable to hard rest my tablet, either erase all data in settings or wiping everything from recovery doesn't restore my tablet to the factory state. I have the same wallpaper, lock screen, google account and everything.
The applications I have uninstalled are also shown and I am unable to get rid of them
super user application is not working and crashes on starting the program and also during start up
every application or system process crashes on start up and keeps popping message indefinitely so that the only thing I can do with my tablet is just to press ok for the popup sparing some few second lapses
few error messages are like this:
unfortunately, the process android.process.acore has stopped
unfortunately superuser has stopped
unfortunately, the process com.google.process.gapps has stopped
unfortunately, Exchange services has stopped
unfortunately, Email has stopped
unfortunately, google partner setup has stopped
unfortunately, google play services has stopped
unfortunately, talk has stopped
etc etc, they keep on coming and make me do nothing, I have tried going to recovery and wiping everything including rom cache system factory cache dalvik data etc what all are available, and tried flashing cyanogenmod and gapps again and again, but neither the data is wiped nor are the problems resolved,
Any help is highly appreciated. Thanks in advance..
additional info
i have other problems like settings not getting saved, for example If i enable debugging in developer options, the movement I go back to previous settings and come again to developer options, the setting remains unchecked. Even the about of the tablet is showing older cyanogenmod status like10-20121209-unofficial-acclaim although I flashed it with 10.1 nightly
Please help me. Thank you.
I don't know what went wrong in your installation. It seems very messed up.
If it was me I'd strat from scratch again with the "repart.img" (mentioned in many places here) that restores your device to "fresh out of the box" condition.
It's possible you have messed up ny formatting wiping too much in your desire ti wipe it clean though and if that's the case the repart.img won't work.
asawi said:
I don't know what went wrong in your installation. It seems very messed up.
If it was me I'd strat from scratch again with the "repart.img" (mentioned in many places here) that restores your device to "fresh out of the box" condition.
It's possible you have messed up ny formatting wiping too much in your desire ti wipe it clean though and if that's the case the repart.img won't work.
Click to expand...
Click to collapse
Thanks for reply, dint get time to immediately test, but what happened is I get a green check mark after getting installing new software, after which i am supposed to remove sd card and nook restarts itself, the nook does restart but cyanoboot starts up and cyanogenmod starts up, i am not getting message clearing data. What wrong could i have done?? Thank in advance.
The worst part is even if i load a sd card image with bootable rom also (from succulent), i am getting same errors, everything is crashing, i cant get beyond the start screen...I couldn't understand one thing, if this is a problem with the rom or other formatting, why is sd card image not working and showing the same errors as internal image?? I get the same error messages as described in the first post of this thread even with the sd card image..Any help is highly appreciated..
rammbbs7 said:
The worst part is even if i load a sd card image with bootable rom also (from succulent), i am getting same errors, everything is crashing, i cant get beyond the start screen...I couldn't understand one thing, if this is a problem with the rom or other formatting, why is sd card image not working and showing the same errors as internal image?? I get the same error messages as described in the first post of this thread even with the sd card image..Any help is highly appreciated..
Click to expand...
Click to collapse
It might be that the NT still boots from emmc rather than off SD. Some NTs will only boot off SD from the power-off state and upon insertion of a powered USB cable. If/when the NT successfully boots off SD for the first time it should take you through a series of network and Google account setup screens, that's how you'd know you're running off SD. See http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for more info/pointers on creating bootable SD cards.
Also, if you're going to re-install CM10 down the road, you might want to take a look at http://forum.xda-developers.com/showthread.php?t=2056626.
digixmax said:
It might be that the NT still boots from emmc rather than off SD. Some NTs will only boot off SD from the power-off state and upon insertion of a powered USB cable. If/when the NT successfully boots off SD for the first time it should take you through a series of network and Google account setup screens, that's how you'd know you're running off SD. See http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for more info/pointers on creating bootable SD cards.
Also, if you're going to re-install CM10 down the road, you might want to take a look at http://forum.xda-developers.com/showthread.php?t=2056626.
Click to expand...
Click to collapse
I know clearly that the nook tablet is booting from the sd card, because its asking me to setup new google account etc, but as the keyboard app is crashing, i cant enter my wifi password to continue, also other error messages are also occurring preventing me from doing anything further. Also during start up I am seeing a different version of cyanoboot and recovery which is matching with my sd card's version, further proof that I am booting from my sd card. Could this be any hardware issue other than emmc or rom? Could this be an issue with the RAM or something else. Thanks for support.
Try Albert's way to turn back to stock again
Check out Albert's [Devs] post for making SD card reboot back to BN stock 4.2 and start over...Using the Nightly builds of CM 10 are very UN stable Roms..experimental..If you want clean stable then I recommend using pacman's Rom build or my Favorite build PA Android build I'm currently using now.
Lestwist50 said:
Using the Nightly builds of CM 10 are very UN stable Roms..experimental..If you want clean stable then I recommend using pacman's Rom build or my Favorite build PA Android build I'm currently using now.
Click to expand...
Click to collapse
Strongly disagree, since the current nightly build is in RC5 status, but whatever...
OP: What class of SD card are you booting from? Also, did you flash your touchscreen firmware by any chance?
class 4 sd card, i dont know if i flashed the touchscreen firmware or not, i dint specifically do something like that. I cant even use the repart.img as the its working in the beginning and i getting a green check mark but after booting that, its simply starting the preinstalled cyanogenmod instead of wiping the device. Any further help?? Thanks in advance. It would be nice if any can diagnose whats wrong, whether the hardware or the software. Thank you.
Did you try this? http://forum.xda-developers.com/showthread.php?t=1470910