Ok, I give (well sort of) stuck at 3 birds screen for gingerbread roms.
Need one of the better brains on this one. I'm not sure if solvable without one of the big guys having one of these troublesome woot tablets.
Story up till now.
I have a G tablet, I have had one since November 2010. (black friday sears).
On my tablet I have never had any issues installing any rom/kernel and it at least booting (ones designed for gtablet)
I impressed work with them so much that during the Woot sale a few weeks back, the university bought 11 of these tablet for other techs.
So I stepped up and decided to flash them all (since tap n tap doesn't support several things such as WPA2 enterprise).
Now on the first 2 tablets I got ahold of they would not load any gingerbread rom on this forum, not vegan experementals, not either one of the asops, nor cm7 .... etc..
But they will run TNT lite and vegan 1 5b11.....
One of the units came to me with fc issues out of the box... that one loaded and ran gingerbread just fine..... (vegan experementals + pershot kernal + gapps)
The one my step father purchased from woot runs gingerbread asop + pershot + gapps fine as well
Got to work today tried a few things on another one of these tablets and it gets stuck at the veiwsonic 3 birds screen.
So these are all the methods broken down by tablet.
Tablet 1 -
Boot to stock
Mount tablet as usb
extract CW internal to device
mount usb
Reboot recovery
Reboot CW recovery
Copy over GB Asop
Copy over gapps
Flash said above
stuck at "viewsonic" screen
Ok...
Partition memory 2048/0
mount
Copy over gb asop, gb experementals, gapps
Try all of them...
Viewsonic screen..
ok
partition
mount
Copy over vegan 5.1 5.11 and pershot kernal
flash
Bingo we have vegan tab....
Hmmm..
2nd tablet
Ok lets try this again
Boot to stock
Mount tablet as usb
extract CW internal to device
mount usb
Reboot recovery
Reboot CW recovery
Copy over GB experementals
flash
stuck at viewsonc screen
partition 2048/0
mount
copy over experementals
flash
stuck at viewsonic
copy over vegan 5.1 / 5.11
flash (no kernal this time)
bingo we have froyo .... still no gb
Tablet 3- Troubled begginings
Set time zone - Force crash here....
Copy over micro sd and extract to micro sd card
Flash CW
lets try again
Copy over asop + gapps + pershot
Bam reboot and were in---- ran perfectly.
So I go... AHHA.. Must be micro SD is the key...
Tablet 4 ---
Bring over same micro sd card with me.
Use it to install CW
Install asop +gapps+pershot
froze at "Viewsonic"
WTF....
hmmmmm
Repartiton 2048/0
stuck
repartition 4096/0
stuck
repartition 4096/32
stuck
etc...
Repartitioned 2048/0
Installed vegan 5.1 / 5.11
bingo we have a live tab....
So I really don't know what is causing this. any thoughts on any of it would be greatly appreciated.
Only thought is hardware revision.. *shrug*
Did you do the stock OTA update before flashing any roms?
Pnuts said:
Did you do the stock OTA update before flashing any roms?
Click to expand...
Click to collapse
On tablet 4 I did.
I got cm7 on my woot gtab finally.
I repartitioned to 4096/256.
NVFlash
booted in to stock > plugged in to pc > usb transferred cm .8
installed cm .8
booted back to stock > usb transferred rom + gapps
boot recovery > formated boot,system,cache,data and wipe davlik cache
mount system & data
install rom then gapps
mount system ( it unmounts after rom install, cache was still mounted)
“wipe data/factory reset”
reboot
on mine- it took 30-60 secs to go from viewsonic screen to the cm boot animation and 1-2 mins it loaded up
bill1253 said:
I got cm7 on my woot gtab finally.
I repartitioned to 4096/256.
NVFlash
booted in to stock > plugged in to pc > usb transferred cm .8
installed cm .8
booted back to stock > usb transferred rom + gapps
boot recovery > formated boot,system,cache,data and wipe davlik cache
mount system & data
install rom then gapps
mount system ( it unmounts after rom install, cache was still mounted)
“wipe data/factory reset”
reboot
on mine- it took 30-60 secs to go from viewsonic screen to the cm boot animation and 1-2 mins it loaded up
Click to expand...
Click to collapse
I'll have to give this a try.
bill1253 said:
mount system ( it unmounts after rom install, cache was still mounted)
Click to expand...
Click to collapse
Hmmm.... May have something on this line. Have to check it out.
Gentlemen -- and others reading this thread:
Please don't get people started re-partitioning the way you have just posted!!!???!!!
I can't pull the reason off the top of my head -- but the 2048 and 0 has been the
standard since last November. I do remember that it will foul things up.
If you want to experiment with it, fine. But if you keep posting and pushing it you
may start another round of problems for folks that don't need problems.
IMHO.
Rev
EDIT, HERE'S THE ANSWER: The 2048 figure has been set for a long time because other values
(particularly 4096) caused issues with the Market. Wouldn't allow downloads.
The second value is a cache and the the understanding is that Android doesn't use it, so
it's just a waste of space.
Android is not well-documented, but that is the wisdom behind 2048/0.
bc
I would agree with butchconner. I am not a developer, but I am a UNIX systems administrator.
In the "old days" when RAM was hideously expensive ($7,000 for 16MB of RAM), we used a rule of thumb that swap should be 1-2.5 times the physical RAM. Disk was cheaper than RAM, hence virtual memory.
Now, memory generally exceeds requirements. I can understand why one would want not to have your swap go to flash nvram, since nvram is slow and has limited write cycles. But, letting the system swap to nvram _and_ to less swap than you have memory for just seems counter productive.
I partitioned mine to 2048/0 and it runs great.
My Archos 70 has only 256MB RAM, and I could see a benefit from 256mb - 512mb of configured swap space, as it appears memory constrained in 256MB RAM.
Hope this helps.
butchconner said:
Gentlemen -- and others reading this thread:
Please don't get people started re-partitioning the way you have just posted!!!???!!!
I can't pull the reason off the top of my head -- but the 2048 and 0 has been the
standard since last November. I do remember that it will foul things up.
If you want to experiment with it, fine. But if you keep posting and pushing it you
may start another round of problems for folks that don't need problems.
IMHO.
Rev
EDIT, HERE'S THE ANSWER: The 2048 figure has been set for a long time because other values
(particularly 4096) caused issues with the Market. Wouldn't allow downloads.
The second value is a cache and the the understanding is that Android doesn't use it, so
it's just a waste of space.
Android is not well-documented, but that is the wisdom behind 2048/0.
bc
Click to expand...
Click to collapse
fine and good and all, but red hering all the same. still can't get gingerbread to work on a large majoity of the woot tablet i have come across.
That's the best I can offer. Sorry I can't help you.
Please remember that Gingerbread is not out for the
G-Tablet and what you are using is experimental.
It may not be perfect!
Good Luck.
Rev
butchconner said:
That's the best I can offer. Sorry I can't help you.
Please remember that Gingerbread is not out for the
G-Tablet and what you are using is experimental.
It may not be perfect!
Good Luck.
Rev
Click to expand...
Click to collapse
Yea I don't think this has to do with experimental some of the bootloaders or something are fowled up on some tabs why does it work on some and not others?
My coworker and I both bought the tabs at the same time and his flash ginger no problem and mine sticks at the birds.
My Woot tablet works great, no problem with Gingerbread. I DID let it do the OTA update before I started hacking - not sure if that made a difference.
chadness said:
My Woot tablet works great, no problem with Gingerbread. I DID let it do the OTA update before I started hacking - not sure if that made a difference.
Click to expand...
Click to collapse
Wish that it did. I tried this on both tablet 4 and tablet 5 (last night) with no effect.
I rolled tablet 3 to stock 3588 from roebeet's recovery mod
Only thing I haven't tried is skipping CW all together and do it all from update.zip s .
May give that a shot today.
It's alive!
bill1253 said:
I got cm7 on my woot gtab finally.
I repartitioned to 4096/256.
NVFlash
booted in to stock > plugged in to pc > usb transferred cm .8
installed cm .8
booted back to stock > usb transferred rom + gapps
boot recovery > formated boot,system,cache,data and wipe davlik cache
mount system & data
install rom then gapps
mount system ( it unmounts after rom install, cache was still mounted)
“wipe data/factory reset”
reboot
on mine- it took 30-60 secs to go from viewsonic screen to the cm boot animation and 1-2 mins it loaded up
Click to expand...
Click to collapse
I skipped the repartition (left it at default), but I was actually able to boot into a Gingerbread ROM! I followed your instructions to the T.
An additional note for the NVFlash, I followed roebeet's instructions to do a restore via NVFlash, although, I did not update to 3588 (it said it was already up-to-date?): http://forum.xda-developers.com/showthread.php?t=861950
Thanks!
EDIT: the Tap UI version that is installed from the NVFlash I performed is 2638. I have completed the steps above again with a different ROM (CM7) and it worked like a champ again.
Do NOT partition to anything other than 2048 and 0. You WILL have market problems otherwise. If you load a Gingerbread rom and it stops at the birds you must nvflash to stock and then you will okay. I have walked about 20 people through this in the last 2 weeks and it works everytime. Something is different in the partitioning on these newer tabs and Gingerbread dont like it. It's not the bootloader and not clockwork
Yeah, I left it at 2048/0; you actually shouldn't have to repartition it with the default settings anyway. I haven't had a problem and haven't needed to repartition it when going between Gingerbread ROMs.
thebadfrog said:
Do NOT partition to anything other than 2048 and 0. You WILL have market problems otherwise. If you load a Gingerbread rom and it stops at the birds you must nvflash to stock and then you will okay. I have walked about 20 people through this in the last 2 weeks and it works everytime. Something is different in the partitioning on these newer tabs and Gingerbread dont like it. It's not the bootloader and not clockwork
Click to expand...
Click to collapse
Any chance you could walk me through it? I'm not quite sure what I'm doing wrong otherwise.
You can join irc but the first thing that will be asked is do you have the drivers installed and can you see the tab from a pc.
Freenode channel #tegratab
Hi everyone,
First time poster but have been reading and browsing for a couple month now and have been able to find fixes for all the issues on my own. I have however had this one issue from the beginning and have not found any fixes or even the issue being mentioned (been using TnTLite the entire time, going up the versions from early 3's to now 4.4).
When my Gtab goes to sleep or even sits idle for a while my WiFi just stops working. The connection is still there and Gtab thinks it's connected but I can't access the net until I turn Wifi off and on and then it works until I let it sit or the screen shuts off. This is annoying at the least and I would love to fix it, even if I have to go to a different ROM (but I do like TnTLite above others).
Does anyone find version 4.4 more laggy than 4.2.5? Gtab is just not as responsive and I seem to have a Flash issue where net videos crash after working for 1-15min.
Also I have CWM 0.8 and when I try to flash with a MicroSD I keep going back into CWM. I changed SDCARD to SDCARD2 in the common file but still my card is not being read. Basically if I want to install the stock ROM and nothing else I can't cause it only boots into CWM and not the SD card. I do have the card formated in FAT32 at 2048. Am I missing something, do I need to uninstall CMW first somehow?
If you re-read the first post in the TnT Lite 4.4 thread, you'll see that you can toggle the CWM back to stock recovery with some built in commands.
Yeah, I saw that as one of the options but I want to be able to patch via the micro SD card and CWM seems to be interfering with that. I mean if I revert to stock with CWM I will still have CWM installed. I want the true original state but more than that I want the MicroSD card recovery to work.
Switching to stock recovery removes CWM and will allow you to use the MicroSD to install. All you have to do is put a file named "command" in the recovery folder on your MicroSD card with the following contents:
--update_package=SDCARD2:/update.zip
When you reboot into recovery it will find that command and execute the update.zip on your MicroSD card.
Thank you!
It was my suspicion that CWM is interfering but I also had recovered from the SD card a couple times even with CWM installed, at least I think so, but it is good to know. I'm also still having issues with net video crashing now and again. The screen goes white and I have to reboot. Started when I installed 4.4 and now that I reverted back to 4.2.5 it is much better but still I had it happen just now and it never did before 4.4. The upgrade to 4.4 also slowed the tablet down which did improve as I went back to 4.2.5.
Try going into CWM and wipe dalvik cache and also do fix permissions, usually cures most of those problems after going from one version to another.
What exactly am I loosing when I wipe delvik cache, do you know? And thanks for the suggestion, haven't tried that yet.
Vigilantys said:
What exactly am I loosing when I wipe delvik cache, do you know? And thanks for the suggestion, haven't tried that yet.
Click to expand...
Click to collapse
Here is a post that explains it
http://forum.xda-developers.com/showpost.php?p=3844295&postcount=5
hi,
this ROM works very nice for me, thanks all the deveopers!
i have few questions:
(1) since this ROM has OTA updater (it seems, from the changelog), next time when the new version is realeased, can i just update the ROM via OTA updater?
(2) i dont really understand what “Wipe cache/dalvik” and “Wipe data / factory reset” really do. my guess is that “Wipe data / factory reset” repartitions the internal flash memory of the original memory, so we can use all the memory for our purpose. (not like original Nook Tablet, in which they dedicate only 1GB for personal usage)
if i understand all these correctly, this means next time if i flash the new ROM and want to keep the old data, i should not do "Wipe data / factory reset", but only need to do "Wipe cache/dalvik"? is this correct?
thanks so much,
Jun
junkoi said:
hi,
this ROM works very nice for me, thanks all the deveopers!
i have few questions:
(1) since this ROM has OTA updater (it seems, from the changelog), next time when the new version is realeased, can i just update the ROM via OTA updater?
(2) i dont really understand what “Wipe cache/dalvik” and “Wipe data / factory reset” really do. my guess is that “Wipe data / factory reset” repartitions the internal flash memory of the original memory, so we can use all the memory for our purpose. (not like original Nook Tablet, in which they dedicate only 1GB for personal usage)
if i understand all these correctly, this means next time if i flash the new ROM and want to keep the old data, i should not do "Wipe data / factory reset", but only need to do "Wipe cache/dalvik"? is this correct?
thanks so much,
Jun
Click to expand...
Click to collapse
Wipe data/factory reset is an option in CWM Recovery. Really all it does (from the screen messages) is format both /data and /cache.
Assuming you have CWM Recovery (though I imagine that there are similar entries in TWRP, I've just never used it), to wipe both of the caches you will first need to go to the entry "Wipe Cache Partition", which I believe is directly below Wipe Data/Factory Reset. Do that 3x (that's always been the recommendation, anyway) then go to Advanced and click on Wipe Dalvik Cache (again, 3x).
Again, assuming CWM Recovery, when you're in the recovery Vol Up/Down goes up and down in the list, the 'n' key is for Enter, and the Pwr button goes back.
I don't know about the OTA Updater. I always download and install ROMs (on both my phone and my NT) via Recovery.
Since this is a CM10 based rom you probably don't want to do the ota updater since that is a Cyanogenmod feature. This rom is optimized for the Nook from the CM10 Source I would presume. I personally tried the ota uldater since i get the notifications all the time but i get an error message something like "can't verify the source with a string of numbers". Stick to the recovery based flash installation.
Sent from my SPH-L710 using xda app-developers app
---------- Post added at 10:48 AM ---------- Previous post was at 10:10 AM ----------
I agree with liquidzoo that you should probably do the wipe cache, wipe dalvik cache and factory reset 3times seems like overkill but you can never be too safe. Also i use twrp recovery and click the system button and wipe system a few times as well.
Sent from my SPH-L710 using xda app-developers app
kobhomye said:
I agree with liquidzoo that you should probably do the wipe cache, wipe dalvik cache and factory reset 3times seems like overkill but you can never be too safe. Also i use twrp recovery and click the system button and wipe system a few times as well.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I wipe /system 3x as well (under Mounts in CWM Recovery) when I'm installing a new ROM.
liquidzoo said:
I wipe /system 3x as well (under Mounts in CWM Recovery) when I'm installing a new ROM.
Click to expand...
Click to collapse
I'm not picking on you personally, but deleting and/or wiping partitions (in the case of /system) or directories (dalvik-cache) three times as opposed to once is completely unnecessary. You'll gain nothing by running the command three times over running it once, assuming you received no errors the first time.
When wiping the dalvik cache, both CM recovery and TWRP perform an "rm -rf /data/dalvik-cache" command using the shell. It's not Windows, and is unlikely to fail when passed the "-f (force)" option along with the "-r (recursive)" option.
In the case of wiping the /system partition, again both CM and TWRP write out zeros to clear the data on the partition. I would be suprised if CWM acted differently from CM and TWRP when wiping dalvik-cache and /system.
The only reason I bothered to look into what these commands actually do is to prevent a user from thinking there's a corellation between a failure to wipe 3x versus a problem they're having. If a 3x wipe "fixes" something for you, whatever the problem was, it's very unlikely that the second or third wipe was what fixed it but instead it was more likely a result of a clean install of the ROM.
References from source:
TWRP Wipe Dalvik - https://github.com/TeamWin/Team-Win...548de276b62c0e9af8661e/extra-functions.c#L986
TWRP Wipe/Format System - https://github.com/TeamWin/Team-Win...8de276b62c0e9af8661e/mtdutils/mtdutils.c#L498
CM Wipe Dalvik - https://github.com/CyanogenMod/andr...aa7ff3d06d5dd115b16c/extendedcommands.c#L1292
CM Wipe/Format System - https://github.com/CyanogenMod/andr...aa7ff3d06d5dd115b16c/mtdutils/mtdutils.c#L498
Have fun modding!
No worries, it's just something I've always done as it's been recommended to me in the past (there are some ROM developers that recommend 5x, actually). I'm not saying that 3x over 1x is any better, but I've never had issues. YMMV, but it doesn't take much more time and I like being thorough.
liquidzoo said:
Wipe data/factory reset is an option in CWM Recovery. Really all it does (from the screen messages) is format both /data and /cache.
Assuming you have CWM Recovery (though I imagine that there are similar entries in TWRP, I've just never used it), to wipe both of the caches you will first need to go to the entry "Wipe Cache Partition", which I believe is directly below Wipe Data/Factory Reset. Do that 3x (that's always been the recommendation, anyway) then go to Advanced and click on Wipe Dalvik Cache (again, 3x).
Click to expand...
Click to collapse
sorry, but can you confirm that when i upgrade to the new ROM (from the same author), it is really necessary to Wipe cache &Dalvik cache?
i am confused because somebody told me that i can just flash the ROM by installing the ZIP file (containing the ROM), and reboot the Nook without having to wipe or clean anything.
thanks,
JK
Flashing a ROM
junkoi said:
sorry, but can you confirm that when i upgrade to the new ROM (from the same author), it is really necessary to Wipe cache &Dalvik cache?
i am confused because somebody told me that i can just flash the ROM by installing the ZIP file (containing the ROM), and reboot the Nook without having to wipe or clean anything.
thanks,
JK
Click to expand...
Click to collapse
I don't know if I am doing it right or wrong but I have flashed numerous ROMs and lately have flashed every version of SGT7+CM10+Cherry Picks,By meghd00t. from 24/09 thru my current installation of 08/10 with only one glitch and that was when I flashed enhancements v2 on top of v1.
I have never had any other issues with the above mentioned ROMs except when I flashed 04/10 with enhancement v2. I didn't have the tablet option.
The way I do it is as follows:
1. format /system
2. format /data
3. Flash ROM
4. Flash CWM emmc
5. Flash GAPPs
6. Reset Factory/format data
7. Remove CWM SD card put in data SD Card with Flash Player (no longer avail on Google Play)
8. Boot from CWM menu
Takes awhile to boot this first time. When booted up I bypass the setup screens.
9. Manually set up wireless (need to access auth web site at work and need wireless to be working to accomplish that)
10. Browse to a web site and get redirected to auth page.
11. Auth
12. Set up Google account and other settings, especially under Security <Install from other locations>
13. Download apps I want from Google.
At this first boot SD card is not mounted.
14. Shut down and do a cold boot.
Now I can see SD Card.
15. Install Flash Player from External SD Card.
16. Install Crackle from Play Store.
Now I check Pandora for Audio, Crackle for Video, other apps I use, utilities, keyboards, launchers, games, etc.
So far since Version 24/09 everything has worked for me with the two exceptions above, tablet mode with 04/10 with enhancement v2 and when I flashed enhancement v2 over enhancement v1.
I am now running 08/10 and am very happy with the performance, battery drain is more than CM7 but that is to be expected from a fairly new ROM but not so bad that it is unacceptable, to me at least.
I have never had a black screen or arbitrary reboot (knock on wood). However I do turn my tablet off when I am finished using it, so don't know about deep sleep. I'm using OnDemand, and three launchers without one being the default....Apex, Nova and Trebucket.
All I can say is these developers really ROCK, way to go guys!
--------------------------------------------------------------------------------
MojoGB said:
The way I do it is as follows:
1. format /system
2. format /data
3. Flash ROM
4. Flash CWM emmc
5. Flash GAPPs
6. Reset Factory/format data
7. Remove CWM SD card put in data SD Card with Flash Player (no longer avail on Google Play)
8. Boot from CWM menu
Click to expand...
Click to collapse
You don't need to re-flash CWM every time you flash a ROM. Also, it doesn't make sense to me why you would do a factory reset/format after flashing the new ROM, I would think it would be done prior to flashing the ROM but maybe it doesn't make a difference, I don't know.
I've got TWRP installed to the emmc so I just download the new ROM to the SD with GooManager, reboot into recovery, do a backup, factory reset, flash new ROM & GApps and reboot. Only takes a few minutes.
Reflash ROM
LifeWOutMilk said:
You don't need to re-flash CWM every time you flash a ROM. Also, it doesn't make sense to me why you would do a factory reset/format after flashing the new ROM, I would think it would be done prior to flashing the ROM but maybe it doesn't make a difference, I don't know.
I've got TWRP installed to the emmc so I just download the new ROM to the SD with GooManager, reboot into recovery, do a backup, factory reset, flash new ROM & GApps and reboot. Only takes a few minutes.
Click to expand...
Click to collapse
Tried it as you mentioned, doing a factory reset before flashing the ROM and got a black screen and wouldn't boot. May have been a fluke but the way I mentioned above gives me a good image and alway boots. Don't know why, but if it works for me, I will continue to do it this way as long as it works for me. I have flashed numerous other ROMs the same way with good results each time.
junkoi said:
sorry, but can you confirm that when i upgrade to the new ROM (from the same author), it is really necessary to Wipe cache &Dalvik cache?
i am confused because somebody told me that i can just flash the ROM by installing the ZIP file (containing the ROM), and reboot the Nook without having to wipe or clean anything.
thanks,
JK
Click to expand...
Click to collapse
For an update, yes it is recommended to clear both caches. To be clear, this is only for an update. If it is a new ROM, or if the author recommends it, you should also wipe /data and /system first.
You can just flash without clearing them, but you might run into unexpected issues, so it's not recommended.
MojoGB said:
Tried it as you mentioned, doing a factory reset before flashing the ROM and got a black screen and wouldn't boot. May have been a fluke but the way I mentioned above gives me a good image and alway boots. Don't know why, but if it works for me, I will continue to do it this way as long as it works for me. I have flashed numerous other ROMs the same way with good results each time.
Click to expand...
Click to collapse
I get a black screen for a while on first boot too, but it only last a couple minutes at the most and if you shine a bright light at the screen you can see the CM logo spinning. Are you sure it was hung?
Sent from my Barnes & Noble Nook Tablet using xda premium
When you clear the Dalvik cache, it clears out data stored in your applications. When you turn on your Nook after clearing the Dalvik, the first thing it does is it rebuilds the Dalvik cache, that's why it seemed like it hung on startup. I believe the long black screen in the beginning is when it rebuilds Dalvik for core Android apps and then when it says "Optimizing Apps", that's for the rest of your applications. The more apps you have, the longer it will take to build the Dalvik. No need to freak out, just a little patience is all you need. Correct me if I'm wrong, however, as I'm still pretty much a noob at this... :laugh:
Flash a Rom
topdawg7793 said:
When you clear the Dalvik cache, it cleares out data stored in your applications. When you turn on your Nook after clearing the Dalvik, the first thing it does is it rebuilds the Dalvik cache, that's why it seemed like it hung on startup. I believe the long black screen in the beginning is when it rebuilds dalvik for core Android apps and then when it says "Optimizing Apps", that's for the rest of your applications. The more apps you have, the longer it will take to build the dalvik. No need to freak out, just a little patience is all you need. Correct me if I'm wrong, however, as I'm still pretty much a noob at this... :laugh:
Click to expand...
Click to collapse
Well fhe screen was black, no light at all and I waited for over five minutes for the Flash Screen to come up and it never did. Yes I know when you are waiting time drags. But due to the ROMS always taking awhile to boot up the first time I actually pay attention to how long it takes. No more then 2 minutes in my experience. I had to hold the power button in for a long time until it finally booted in B&N Recovery. Used my sequence mentioned in earlier post to flash the ROM again and everything worked as it should, GREAT. The number of APPs shouldn't be an issue as these ROMS only have the very basic apps.
I have read this forum and see the various and asundry errors some are getting, so far I have never gotten a major error, except for when I forgot to do the Wipe Data/Factory Reset after flashing.
I also got the "No Tablet Mode Option" with 04/10 with enhancement v2.
But I consider these minor issues and currently am running 08/10 with no issues, works smoother then any version of Microsoft Windows I have dealt with.
These developers are exceptional.
MojoGB said:
I don't know if I am doing it right or wrong but I have flashed numerous ROMs and lately have flashed every version of SGT7+CM10+Cherry Picks,By meghd00t. from 24/09 thru my current installation of 08/10 with only one glitch and that was when I flashed enhancements v2 on top of v1.
I have never had any other issues with the above mentioned ROMs except when I flashed 04/10 with enhancement v2. I didn't have the tablet option.
The way I do it is as follows:
1. format /system
2. format /data
3. Flash ROM
4. Flash CWM emmc
5. Flash GAPPs
6. Reset Factory/format data
7. Remove CWM SD card put in data SD Card with Flash Player (no longer avail on Google Play)
8. Boot from CWM menu
--------------------------------------------------------------------------------
Click to expand...
Click to collapse
oh, so you always reset factory every time you upgrade the ROM? that way will delete all the old data/apps you installed, so you need to install all the apps again?
this is my concern, because i dont want to reinstall apps, or lose my data. so i think i just need flash the new ROM, then Wipe cache/Dalvik cache, and hopefully all the old apps and data are still intact.
thanks.
MojoGB said:
I don't know if I am doing it right or wrong but I have flashed numerous ROMs and lately have flashed every version of SGT7+CM10+Cherry Picks,By meghd00t. from 24/09 thru my current installation of 08/10 with only one glitch and that was when I flashed enhancements v2 on top of v1.
--------------------------------------------------------------------------------
Click to expand...
Click to collapse
i have some questions on the "Enhancements":
(1) the correct way to install them is to flash version 1 first, then immediately flash version 2 right after version 1 (without having to reboot first)?
(2) i am not sure what i will get with this "enhancements". they will make video/audio playing more smoothly? is the quality improvement really noticable? anything else, like they make the battery last longer, for example?
thanks,
Jun
If you're running 08/10, the enhancements are not needed. That's my understanding at least. I had problems with V2 so I decided to not install them while on 04/10.
Sent from my Barnes & Noble Nook Tablet using xda premium
Flash Rom
junkoi said:
i have some questions on the "Enhancements":
(1) the correct way to install them is to flash version 1 first, then immediately flash version 2 right after version 1 (without having to reboot first)?
(2) i am not sure what i will get with this "enhancements". they will make video/audio playing more smoothly? is the quality improvement really noticable? anything else, like they make the battery last longer, for example?
thanks,
Jun
Click to expand...
Click to collapse
If you flash enhancement v2 on top of version 1 you will have problems, UI will stop. If you only flash v2 you will not have the Tablet Mode Option. So my understanding is that you can use either v1 or v2 but not both.
ROM 08/10 does not need either enhancement as indicated by the developer. ROM 08/10 works great by itself is my experience.
If I'm installing a ROM, backup the existing ROM and wipe everything.
If I'm installing a .zip package like GApps or an enhancement, backup the existing ROM, wipe Data/Dalvik.
Folks, these are development ROMS. Thar be bugs in thet thar code. It's going to take you longer than the time you think you're going to save by doing a dirty flash, and then having to restore the thing to stock (worse case) only to start all over.
Don't ask how I know.
wellersl said:
If I'm installing a ROM, backup the existing ROM and wipe everything.
Click to expand...
Click to collapse
so it is possible to back up the existing data/apps, then restore them back after the new ROM is flashed? could you please confirm this?
if so, how & what is the right steps to do the backup? can we still use CWM, or use ROM Manager, or other tools?
thanks
Hello, I have an I-777 that is currently flashed to task650's AOKP ROM (Link to the thread).
I followed the guide at this link:
http://forum.xda-developers.com/showthread.php?t=1311081
I did a full backup with Titanium Backup, then used steps 2c and 3a of the guide linked above, then I flashed the AOKP rom with CWM.
My accounts connect and everything looks good, but my internal SD storage is missing. The external SD is available in the OS, but not any internal or USB storage.
I've wiped cache and user data and reflashed a couple of times, and I see my old storage in a folder called /emmc/, which I can't access through the OS, only through CWM. The ROM and gapps are in that folder and I can flash from them.
I have a feeling that /emmc/ is a storage folder that's used in gingerbread or ics but not in jellybean. I just don't know how to use that information to reach an answer.
I'd like to get access to that data in the OS since it seems to be uncorrupted but I am unsure of how to proceed.
I appreciate any help.
--Jake
I don't ever recall that Task's AOKP actually uses /emmc but /sdcard0.
If nothing there, you can format it and see if it works.
taladel said:
Hello, I have an I-777 that is currently flashed to task650's AOKP ROM (Link to the thread).
I followed the guide at this link:
http://forum.xda-developers.com/showthread.php?t=1311081
I did a full backup with Titanium Backup, then used steps 2c and 3a of the guide linked above, then I flashed the AOKP rom with CWM.
My accounts connect and everything looks good, but my internal SD storage is missing. The external SD is available in the OS, but not any internal or USB storage.
I've wiped cache and user data and reflashed a couple of times, and I see my old storage in a folder called /emmc/, which I can't access through the OS, only through CWM. The ROM and gapps are in that folder and I can flash from them.
I have a feeling that /emmc/ is a storage folder that's used in gingerbread or ics but not in jellybean. I just don't know how to use that information to reach an answer.
I'd like to get access to that data in the OS since it seems to be uncorrupted but I am unsure of how to proceed.
I appreciate any help.
--Jake
Click to expand...
Click to collapse
Are you using another kernel? AJK?
Sent from my SGH-i777 using Tapatalk 2
I had them same issue. Flashed using OTA and then couldn't see my external card. Restored nandroid and everything worked. Tried updating a few different ways still no go. I haven'y had to full wipe in a while, hope I wont this time either. Had to go to work so will try a couple different things today to see if it was somthing I did. Of course it has nothing to do with Task's ROM or his new kernel. LOL
Ken
Update: I tried a number of different ways to flash it. I didn't want to go thru the full wipe process at this time so I restored to last backup for now.
ffltstn said:
I had them same issue. Flashed using OTA and then couldn't see my external card. Restored nandroid and everything worked. Tried updating a few different ways still no go. I haven'y had to full wipe in a while, hope I wont this time either. Had to go to work so will try a couple different things today to see if it was somthing I did. Of course it has nothing to do with Task's ROM or his new kernel. LOL
Ken
Update: I tried a number of different ways to flash it. I didn't want to go thru the full wipe process at this time so I restored to last backup for now.
Click to expand...
Click to collapse
I apologize for not responding to this thread. I just flashed a few more times without doing a full wipe and eventually it took and populated my 'People' app. I didn't know, however, that using the OTA would wipe my contacts again. I have now learned my lesson and done a FULL backup.
My question is (kind of) answered, so I'm going to close this thread.