Database Develop

[SELFKANG AOSP ROM] CyanogenMod 7.1 Alpha Release [UPDATE 11/16 PM]

** [UPDATE 11/16] = Minor update adding Droid3Bootstrap / RomManager support for installs. You DO NOT need Safestrap to install CM7 now. Any Bootstrap will work.
[UPDATE 11/10] = Better audio (still debugging why volume will occassionally fall back down -- if it does go into settings -> sound -> volume and drag the media slider up -- will reset it), fixed bluetooth -- 2nd ota patch .zip for 5.7.894 OTA users
It's an OMAP4 optimized AOSP build using CyanogenMod sources. I used some of the published Moto Source (9/18) where I felt it was appropriate to get the low level services running. You will not see any Blur files in this build.
Download Link Here
If you're running the 5.7.894 OTA, you will also want to apply a 2nd .zip afterward to update the few stock binaries that are in the build. It's under the .zip download links.
Changelog Here
For the most up-to-date information / builds check my blog: http://hash-of-codes.blogspot.com
What is working in this build:
Phone dial and recieve calls (10/18)
Wifi
SD Cards
Audio is getting better
GPS
3G data
Bluetooth
lots I can't list
Feel free to flash gapps and test away. To download GApps go here and select the top "universal CM7 link for GB"
What isn't working:
Camera app doesn't soft reset the phone anymore, but it isn't working yet either.
Phone app FC's on the boot. Just close the notification and it'll restart 3G immediately.
Audio is very funky atm. It's getting better. If you lose volume, try opening Setting -> Sound -> Volume and drag the "media" slider down and then back up.
GSM Users:
I reviewed some changes submitted by XDA's coreless88 and for the moment I'm just not comfortable putting them in the main build. They would default the phone to GSM/WCDMA. I WILL absolutely get the native support for both GSM and CDMA working as this build matures. It just may take a while. If you really want a GSM variant of this build let me know and I'll reproduce a version with his build.prop changes. For me personally, this can't be a daily driver till the audio issues are fixed.

Great I need calling so won't try it yet, but thanks for all your work

will test it out tonight o hell more like as soon as i get a chance lol

So if 3G works can I still get texts? I don't need to talk to anyone.

yeah texts works, gapps works. just a few funny things. and not like "ha ha" funny either!
still BA!

Once installed, can I do a backup of this and flash back and forth using Safestrap?
Edit: Backup of stock rom gives an error when generating a md5. Is that a problem?

Thanks for all you hard work on this.

im bricked. i flashed back to monster, cleared, and now i cannot boot into bp tools. i start in recovery, hit bp tools, and it goes back to bootlooping. i dont have the sbf as the link is down. can anyone help? AND i only had about 40% battery

MrJudylicious said:
im bricked. i flashed back to monster, cleared, and now i cannot boot into bp tools. i start in recovery, hit bp tools, and it goes back to bootlooping. i dont have the sbf as the link is down. can anyone help? AND i only had about 40% battery
Click to expand...
Click to collapse
Did you miss a step?
I just booted up for the first time about 5 seconds ago. Working great.
Thanks Hashcode!

i get to step 9 and at the end of the back up it says Error generating md5 sum! trying to make a different backup to see if i get same error.

Androidsims said:
Once installed, can I do a backup of this and flash back and forth using Safestrap?
Click to expand...
Click to collapse
Good Question! Short answer: yes.
For now, you have to run a backup (MotoBlur), then format /system, wipe data/cache and install the CM7 zip. When you're done with CM7, you can do another backup (if you want to save CM7) and then restore your original MotoBlur. Make sure to toggle the "Safe System" setting afterward.
As soon as I fix some things in the CM7 build so that the phone is usable, I'm going to work on Safestrap some more.
The next version of Safestrap will automatically store and load your userdata when you toggle the "Safe System" setting. So there won't be a need to perform all of the backup/restores. It will just be the 1 toggle and then reboot.
And sometime in the future, I'm going to put up a MotoBlur "ROM" .zip which runs in 2nd-system. SO stuff like SteelDroid or other ROMs can be safer to install/run. Devs can use that MotoBlur ROM as a template for doing theming, and other things.
It really depends on how well received Safestrap is and if the community wants to see more of it.

Androidsims said:
Did you miss a step?
I just booted up for the first time about 5 seconds ago. Working great.
Thanks Hashcode!
Click to expand...
Click to collapse
no no i booted into CM7 just fine. it was when i booted back into recovery, flashed monster1.2, cleared cache, then reboot lead me to bootloop

MrJudylicious said:
im bricked. i flashed back to monster, cleared, and now i cannot boot into bp tools. i start in recovery, hit bp tools, and it goes back to bootlooping. i dont have the sbf as the link is down. can anyone help? AND i only had about 40% battery
Click to expand...
Click to collapse
I have fastboots for both 5.5.959 and 5.6.890. I can do a mediafire share of whichever you need.

Hashcode said:
I have fastboots for both 5.5.959 and 5.6.890. I can do a mediafire share of whichever you need.
Click to expand...
Click to collapse
i was on 890 so i figured i should flash 890. it would be awesome if you could

MrJudylicious said:
i was on 890 so i figured i should flash 890. it would be awesome if you could
Click to expand...
Click to collapse
I'm going to put the fastboot files on my site for download. It might take a while. Showing 2 hours for the 420M file. I'll update this post with a link in a bit.
Edit:
Unfortunately the nature of flashing ROMs over your live system on a locked bootloader phone means that the hijiack is broken until you can get into the OS and reinstall some sort of Bootstrap. And this was exactly the reason why I developed Safestrap. :/
That being said, you'll likely be able to just flash your /system using the fastboot files and you'll be fine. And don't forget to wipe userdata when swapping ROMs. I've seen countless bootloops from not wipeing userdata. This is ESPECIALLY important for CM7 vs. MotoBlur.

oostah said:
i get to step 9 and at the end of the back up it says Error generating md5 sum! trying to make a different backup to see if i get same error.
Click to expand...
Click to collapse
I got the same error but proceeded anyways.
Man, I forgot how smooth CM is.... Loving the new lockscreen and built in Screenshot features too.

Hashcode said:
As soon as I fix some things in the CM7 build so that the phone is usable, I'm going to work on Safestrap some more.
The next version of Safestrap will automatically store and load your userdata when you toggle the "Safe System" setting. So there won't be a need to perform all of the backup/restores. It will just be the 1 toggle and then reboot.
And sometime in the future, I'm going to put up a MotoBlur "ROM" .zip which runs in 2nd-system. SO stuff like SteelDroid or other ROMs can be safer to install/run. Devs can use that MotoBlur ROM as a template for doing theming, and other things.
It really depends on how well received Safestrap is and if the community wants to see more of it.
Click to expand...
Click to collapse
thanks hashcode, for CM7 work, safestrap, etc...YOU ARE GREATNESS!!!

Hashcode said:
Good Question! Short answer: yes.
For now, you have to run a backup (MotoBlur), then format /system, wipe data/cache and install the CM7 zip. When you're done with CM7, you can do another backup (if you want to save CM7) and then restore your original MotoBlur. Make sure to toggle the "Safe System" setting afterward.
As soon as I fix some things in the CM7 build so that the phone is usable, I'm going to work on Safestrap some more.
The next version of Safestrap will automatically store and load your userdata when you toggle the "Safe System" setting. So there won't be a need to perform all of the backup/restores. It will just be the 1 toggle and then reboot.
And sometime in the future, I'm going to put up a MotoBlur "ROM" .zip which runs in 2nd-system. SO stuff like SteelDroid or other ROMs can be safer to install/run. Devs can use that MotoBlur ROM as a template for doing theming, and other things.
It really depends on how well received Safestrap is and if the community wants to see more of it.
Click to expand...
Click to collapse
So ultimately this will basically dual boot?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Androidsims said:
I got the same error but proceeded anyways.
Man, I forgot how smooth CM is.... Loving the new lockscreen and built in Screenshot features too.
Click to expand...
Click to collapse
OH, I totally forgot that the phone FCs on boot. It reloads 3G data shortly afterward. I have a fix coming for that as well.
You could say.. the OS boots too fast for it.
THe normal boot process for MotoBlur involves the phone coming up as GSM initially, doing a few checks for network, failing and then dropping into a Janky CDMA version of GSM.
CM7 currently boots straight to CDMA.

Hashcode said:
I'm going to put the fastboot files on my site for download. It might take a while. Showing 2 hours for the 420M file. I'll update this post with a link in a bit.
Edit:
Unfortunately the nature of flashing ROMs over your live system on a locked bootloader phone means that the hijiack is broken until you can get into the OS and reinstall some sort of Bootstrap. And this was exactly the reason why I developed Safestrap. :/
That being said, you'll likely be able to just flash your /system using the fastboot files and you'll be fine. And don't forget to wipe userdata when swapping ROMs. I've seen countless bootloops from not wipeing userdata. This is ESPECIALLY important for CM7 vs. MotoBlur.
Click to expand...
Click to collapse
I appreciate it. I have teh file blur_version.5.5.959.xt862.verizon.en.us.zip Is that the fastboot?
nevermind. i found it here http://rootzwiki.com/showthread.php?5103-SBF-Droid-3-Fastboot-files-(5.5.959-and-5.6.890)
i really appreciate you doing that for me though. i just shat a brick (no pun intended)

[USER] JB/ICS/CM10/9 Discussion

Update: We now have official cm nightly support! Congrats to all involved! http://forum.xda-developers.com/showthread.php?t=1941247
Feel free to continue building for yourself.
Also, while your testing and bug reports are very much appreciated, do not WHINE, or feel entitled to anything. These guys have worked hard for YOUR benefit so be grateful and hit the thanks button for everyone involved.
Old OP follows:
This thread is to help clean out the non-development discussions happening in the dev thread. Please post your impressions, problems, fixes, thanks, etc. here.
Refer to this thread for progress on development http://forum.xda-developers.com/showthread.php?t=1370873.
Unofficial CM9 Nightly Builds:
You can get Eyeballers unofficial nightly builds here
You can get Samiam's unofficial nightly builds here
CM10:
Video of CM10 running on Nook Color http://forum.xda-developers.com/showthread.php?p=28844150
Feeling brave? Want the latest and greatest? Build CM10 for yourself. Check out this post to get started http://forum.xda-developers.com/showthread.php?p=29075653
If that feels like a little much you can check out Andbot to help you get started.
http://forum.xda-developers.com/showthread.php?p=29171789
Please do not share your builds. Refer them to these instructions instead.
Keep it clean and remember NO ETA's!!!
Credit and thanks to all involved!

Heres a video i made: http://www.youtube.com/watch?v=pK31qFP9iwA
Screenshots:
Homescreen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Left:
Right:
I have no clue what the line by the notifications is for.

succesful upgrade
hi all,
I managed to successfully install ice cream sandwich.
I upgraded from cm7.2 build of mirage.
ics is running flawlessly.
i wiped system partition then data partition and finally cache.
after that i installed ics update.
let it boot once completely.
again went in to recovery,flashed gapps provided by newellj79
http://db.tt/ujcVWK1U
and to be on safer side,wiped dalvik and now I am happily using tablet running ics.
I love this community and its awesome.
feeling so happy.

ICS on Nook is butter smooth!
Compliments and many thanks to Dalingrin, Fat__Tire and any other members of the team.
Even this alpha version of ICS is running like a dream on my Nook.
I am running it of an SD card. I had a small problem with the market downloading at only 1kb/s. Turned out that changing the SD card for another cured this and improved overall responsiveness.
Looking forward to the next version!

Great, I didn't want to contaminate the official thread, so will report a couple bugs I found.
When running dolphin browser HD, it gets in some sort of memory leak and slows down the device, so I need to reboot the NC to solve it.
thanks guys for all your hard work.
tapped from my ancient HTC magic using xda app

Looks great. Great work devs! Can't wait to try this on my Nook color. Going to wait until the first Beta though (Everything works on CM7 so no real need to upgrade, just want ICS to have ICS )
Wanted to say thanks to the devs for all the hard work and that it is appreciated.

This is looking pretty good . Might have to build it and install it on my nook to test it out.

The lack of sound and most video playback means that this isn't really a daily driver, but it is a very nice version for those looking for media-light (e.g., browser, e-reader, productivity app) functionality. If you're just curious about how ICS runs and what it feels like, and you have the time and resources, I heartily suggest trying it out. You don't even have to blow away your stock install to do it, since you can use verygreen's CM7 uSD install method. From start to finish--including download time for the ROM and GApps, formatting a spare uSD, the verygreen install, the ICS install and first run, and the GApps install--it took maybe 40 minutes and I had everything up and running. It's been as stable or even moreso than the HC build (thanks to having full code rather than SDK), and it looks like the overclocking from dalingrin's Nook Tweaks app helps with some speed issues. I only have a couple other apps installed for right now, and the only real problem I have is that Kindle seems to think that it's installed on a phone, and therefore I only get one or two paragraphs of text on the smallest font. Presumably this is related to a screen density setting, but web and OS text (mmmm...Roboto) is just fine.
Anyway, just my $0.02, from someone who's enjoying messing around with it in anticipation for a Galaxy Nexus.

I'm daily driving it now. Loving it. I listen to music on phone and don't watch many vids
Brian

dr_tracker said:
When running dolphin browser HD, it gets in some sort of memory leak and slows down the device, so I need to reboot the NC to solve it.
Click to expand...
Click to collapse
I have that problem with CM7.1 and similar problem with the stock rom. PArt of the problem with these things is you don't have to turn them off. Eventually there are performance issues that creep up and you have to reboot to fix.
At my last job doing IT support for 45 people, the number of people that just logged off their computers drove me nuts. After a while they had to be shut down, I reccomended on the weekends. I recently discovered that sometimes not only do you have to shut computers down, but some errors will continue untill you shut down and unplug the computer. Wake on lan and USB means something has to be waiting for something to happen. I do wonder if this also happens with some of the "Bricked" nooks where the error won't go away until you let the battery die then plug it back in.

bigmacthe2nd said:
Compliments and many thanks to Dalingrin, Fat__Tire and any other members of the team.
Even this alpha version of ICS is running like a dream on my Nook.
I am running it of an SD card. I had a small problem with the market downloading at only 1kb/s. Turned out that changing the SD card for another cured this and improved overall responsiveness.
Looking forward to the next version!
Click to expand...
Click to collapse
How did you install on SD card? can you post the image? thanks

bmaa said:
How did you install on SD card? can you post the image? thanks
Click to expand...
Click to collapse
Check out the following post:
http://forum.xda-developers.com/showpost.php?p=12240928&postcount=1

Got it. It is booting now. Where did you get GAPPS?

bmaa said:
How did you install on SD card? can you post the image? thanks
Click to expand...
Click to collapse
Check out http://forum.xda-developers.com/showpost.php?p=12240928&postcount=1.
Download generic-sdcard-v1.3.img.gz
Ungzip it, then write it to an SD card (using dd or WinImage)
Download and copy the image from http://forum.xda-developers.com/showpost.php?p=19868762&postcount=2 onto "boot" partition.
Be sure to add the prefix "update-cm-" to the name (i.e. "update-cm-9.0-0-encore-emmc-sneakpeek1-fullofbugs.zip")
Turn off NookColor, Insert SD and bootup. Once it completes, it will turn-off
Turn NookColor back on and wait for the initial boot to complete (this will take a few min / you'll see the shiny animation)
And you're all done
Now, if you want the gapps (of course ...
Completely turn off/ power-down NookColor, remove SD card.
Download http://forum.xda-developers.com/showpost.php?p=20141071&postcount=264 or the "gapps-small" and copy the ZIP to "boot" on the SD card.
Be sure to add the prefix "gapps-gb-" to the name (i.e. "gapps-gb-ics-4.0.1-small.zip")
Insert SD into (powered-off) NookColor
Enter VeryGreen-SD-Recovery (Hold the N button, Press+Hold the POWER button until the logo appears. Let go op power, then press and hold it again until "Booting into Recovery" appears.) -- Sounds complex, but it's pretty easy.
Once it completes, it will turn off, turn it back on and you're all done

iv been running this alpha since it was posted i got everything working very stable and all, but i have had a problem with the stock browser.
i like the stock browser better than dolphin at this point but after using it for a while it will freeze up and get stuck i cant do anything, iv cleared the cache and all that. it seems to be fine after that but it keeps freezing after use. the lack of sound is just a minor inconvenience for me no big deal i love the tablet software GB just didnt make the nook complete compared to this alpha

Thank you fr the details. I got it to work once and only once. But gapps had the NFC. Updated GAPPS. but could not get it to flash. Not sure what I am doing wrong. it looks like it is falshing but no apps. I tried many times even re-formatted SD and tried the steps again. One thing I noticed is SD-recovery, my screen blink the first time and it doesn't show "Loading" until second push of Power, then it shows "boot into recovery". Even once I ended up with a full BOOT screen. Never seen before. Any recommendations?

bmaa said:
Thank you fr the details. I got it to work once and only once. But gapps had the NFC. Updated GAPPS. but could not get it to flash. Not sure what I am doing wrong. it looks like it is falshing but no apps. I tried many times even re-formatted SD and tried the steps again. One thing I noticed is SD-recovery, my screen blink the first time and it doesn't show "Loading" until second push of Power, then it shows "boot into recovery". Even once I ended up with a full BOOT screen. Never seen before. Any recommendations?
Click to expand...
Click to collapse
Try starting over, and use the modified GApps from this post.

Perfect it worked!!. FYI, I found the best to get into recovery, and I am not patient to keep an eye pn power button, is to hold "N", press Power until screen blink, let go of Power, keep holding the "N". Then you have a menu to choose boot into SD and choose Revovery. Thank you. BTW, this thing is pretty smooth for an alpha. I have ICS on my Nexus S as well. Love ICS.

I just got ICS running on my Nook yesterday. I primarily use the tablet as a traveling portfolio of my photography work (using the JustPictures app).
I followed the directions here: http://forum.xda-developers.com/showthread.php?t=1030227, first installing CM7 and gingerbread. It's not a necessary pre-step, but I wanted to do a walkthrough first on something tried and tested.
Then, I followed the same workflow, but used the CM9 from this post http://forum.xda-developers.com/showpost.php?p=19868762&postcount=2 and the gapps mentioned in this post http://forum.xda-developers.com/showpost.php?p=20141071&postcount=264
It worked like a charm. I'm really happy with the results. I was running honeycomb (pre-release 4) earlier, which kept crashing and whatnot all the time. For a first "alpha" release, this is really smooth and well put together.
Thanks again to all those that worked on putting this together.
In other news, I'm trying to get Android/ICS to build from source, but I'm running into a few troubles with the configuration. Only 9 more posts and then I can get my questions onto the developer boards .
Cheers

Is their a way to change the density to something smaller without it looking all messed up?

[ROM] [OFFICIAL UPDATE] LP11 Official ICS Update for VZW 10.1 LTE tab

Hey guys, I pulled the ICS update.bin from my tab and converted it into a flashable zip file. It must be flashed from STOCK recovery, NOT cwm recovery/TWRP etc. This file basically patches every system file on the tab, so the only way to flash this successfully is to go back to stock and update your way up to stock FE01. It doesn't matter how you get to stock FE01 as long as you are on it and are using the FE01 radios. Once you have reached stock FE01, Flash this file in STOCK recovery: https://dl.dropbox.com/u/20070269/FE01a_to_LP11d_update.zip
Now, place this file: http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip on your SD card.
Once you have flashed the update successfully and placed the superuser.zip on your SD card, odin this recovery: http://droidbasement.com/galaxy/recovery/cwm5/p4vzw/5/recovery.tar.md5 and boot directly into recovery right after you odin it so that the tab does not boot fully into the OS and overwrite what you just flashed with the stock recovery. Once you have booted into cwm recovery, navigate to the superuser.zip and flash and then reboot. Congratulations, you're running Official ICS with root. For those that want CWM recovery to persist after reboot, delete /system/etc/install-recovery.sh with a root file manager.
Of course, credit goes to ChainsDD for the superuser.zip used in this guide
And to pershoot for the CWM recovery used in this guide.

Finally!!!
I can confirm that this file does update the VZW to 4.0.4 with baseband LP11. LTE is finally functioning as well as front and rear cameras. The tab has a whole new feel to it. I haven't tried any of the root files here. I first wanted to make sure that its stable/useful before messing around with rooting.
Big thumbs up for posting

Awesome, thanks Kidserious!
Hoping Pershoot's able to pull drivers from this to integrate into CM9/10.

eXiled Killah said:
Finally!!!
I can confirm that this file does update the VZW to 4.0.4 with baseband LP11. LTE is finally functioning as well as front and rear cameras. The tab has a whole new feel to it. I haven't tried any of the root files here. I first wanted to make sure that its stable/useful before messing around with rooting.
Big thumbs up for posting
Click to expand...
Click to collapse
Yea, this is a very nice update. I'm actually very impressed.
muzzy996 said:
Awesome, thanks Kidserious!
Hoping Pershoot's able to pull drivers from this to integrate into CM9/10.
Click to expand...
Click to collapse
That's what I was most excited about...new kernel source and version. Up until now, all AOSP builds for the LTE 10.1 were based on the 2.6.38 honeycomb kernel. This new update brings us 3.1.10 and updated drivers.

Definitely will be cool.
Bah, had to go way back to an older stock image I had but eventually got back to HC 3.1 and upgraded back up.
Definitely an improvement over stock or even overclocked honeycomb 3.2. Going to be nice to get CM 10 someday.

This update is great..I'd say it was worth the wait, but since Jelly Bean is already out and soon to be dated I will not.

Thanks
This worked great! Waiting for a long time to get this on the LTE!

Woot!
Will be working on this today! Can't wait!
Maybe one of the great devs, can pull the modem out into an install file. Maybe the modem and cameras will work with JB!

Do you think we coudl use these files on the ota dowload from VZW?
Also, how did you get back to stock? I know I have Pershoots kernel, rooted and CWM

well, my dumbarse figured it out. for those that are dense like me, I used the Odin file in rylon360's thread on rootswiki.
http://rootzwiki.com/topic/7718-romleakodineg01-factory-stock-odin-image-vzw-lte-tab-101/ to get back to stock, then I did system updates three times. Small one, large one, Small one. to get to stock FE01.
then followed this thread to update.
Thanks so much!!!!
---------- Post added at 11:26 AM ---------- Previous post was at 10:49 AM ----------
anyone else have issue with Tibu restoring apps? I loaded my Tibu folder back onto the device but it wont recognize the apps. Tibu had the latest update too.

Does this wipe the tablet at all?
My fiance's 10.1 is unbearably slow but she's using it for work so I can't root it. Will I be able to run the update from stock recovery and keep everything how it is?

Yes. I updated another that was all stock and it retained everything. My tab however won't see any of the tibu backups I saved to my PC. Sucks
Sent from my SCH-I905 using Tapatalk 2

pickupman66 said:
Yes. I updated another that was all stock and it retained everything. My tab however won't see any of the tibu backups I saved to my PC. Sucks
Sent from my SCH-I905 using Tapatalk 2
Click to expand...
Click to collapse
try going into /data/media/TitaniumBackup with root explorer and change permissions on the titanium backup folder to all checks.
Sent from my Galaxy Nexus using Tapatalk 2

Ill try that tomorrow. It showed the apps with the strike they but no icon and had a ? When I clicked on them. Said no APk found. So sad cause I made the backup b4 flashing.
Sent from my SCH-I905 using Tapatalk 2

pickupman66 said:
Ill try that tomorrow. It showed the apps with the strike they but no icon and had a ? When I clicked on them. Said no APk found. So sad cause I made the backup b4 flashing.
Sent from my SCH-I905 using Tapatalk 2
Click to expand...
Click to collapse
Did you get this working? I did the same -- backup in Titanium, copy folder to PC, ran through the process to upgrade to latest version and then copy Titanium folder back to /sdcard and all was fine. I've done this several times in the past as well.

I need to do some reading and figure out how to get back to 100% stock. I am pretty sure I am just running the OTA rooted HC ROM so i will need to flash the regular stock ROM and then get recovery back.
The tab was sooo darn slow before. Cant wait to see how it does after this.

JewRican said:
I need to do some reading and figure out how to get back to 100% stock. I am pretty sure I am just running the OTA rooted HC ROM so i will need to flash the regular stock ROM and then get recovery back.
The tab was sooo darn slow before. Cant wait to see how it does after this.
Click to expand...
Click to collapse
Thats what I did, wanted to start fresh so what I installed was HC 3.1 and wiped data and all. Then I ran OTA after OTA until I got to ICS. Then I installed CWM from droidbasement (pershoot) and used it to flash superuser. Tab runs MUCH better than before. I'm currently running stock kernel and intend to do a CWM image of my current setup and wait for CM updates with LTE rolled in before doing any further tinkering with the tablet. I don't even feel the need to run an overclocked kernel at this point.

*edited below*
where else can i grab odin? his link seems to be dead.
Do you have it that you can post somewhere? Seen it somewhere else?
*edit* - found it!
http://forum.xda-developers.com/showthread.php?t=1651794

Ectiech. I have flashed my phone so much I can do with eyes closed. I have done tibu this way several times. Something must have happened to the backup I made because I copied the tibu folder from my cell running slimbean jellybean rom and all the apps restored perfectly from there. Sadly I had not played the games on my phone like I did on my tablet.
Sent from my SCH-I905 using Tapatalk 2

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I returned mine to basic Verizon, no root. Took off clockwork when I returned to stock and let it auto upgrade itself a few weeks ago. Figured it needed to be stock
Copied over and then rebooted to standard recovery and let it fly. Didn't wipe anything. Everything is there. Proggies work. Haven't check cameras.
My tab was stripped...so didn't matter if I lost everything.
Hope my pic posts...hit 58 mbs. Download driving last night. I'm town tested speed changing towers, in upper 30s.
I love u guys. THANKS!
Sent from my SCH-I905 using xda app-developers app

[Q] Albinoman CM 11 - Just a couple --important-- problems

Okay, so I'm new to everything Android in general, so all of this is very confusing to me, so I'm going to be as specific and in-depth as possible.
I'm using an HTC Vivid on AT&T and I just recently flashed CM 11, and I absolutely LOVE it, except for two problems.
The first has been widely acknowledged, and it's the problems with MMS. On the stock ROM, MMS was sometimes a problem, but that was usually because the Vivid had mobile data problems in general (problems which I still have not encountered on CM 11, which is good news). It happened that when the Vivid couldn't send or receive MMS, it also couldn't use the mobile data at all, and this was usually fixed by a reboot (which was a pain because ICS had that bug where it would always "optimize apps" every reboot). This was the problem I first suspected, except I tested the use of mobile data in other apps, and they worked perfectly, leading me to believe that this is not the same problem. Data usage works fine, it's a specifically MMS problem.
The second issue is something that I haven't seen addressed yet, so I guess it's a problem that only I have come across. I can't use the camera at all, because every time I try to open it, it says I need to insert an SD card. Now I know nothing about technology, so is it referring to the internal SD card, or the external? I have an external SD card for the phone, and it works with the Apollo music app and such, so I'm not sure if that's where it's supposed to be going. I can't even take pictures or record videos, because it won't let me, since I don't have an SD card apparently. Is there any way to fix this?
Thanks everyone for any help or advice you can offer.
EDIT: I'm guessing the camera problem is an internal storage thing, because my phone registers no internal storage at all. Nor does TWRP, it doesn't register an internal storage either. I'm still at a loss at how to fix this problem.

Did you flash the most recent nightly, or the most recent stable? Probably a useless question, as the latest stable should be fine as far as the internal storage and everything (and I'm on the 1-28 nightly, which is not giving me any internal storage problems). I recommend flashing back to stock and seeing if the problem persists, because if so, then your problem is most likely not the CM11 rom. If the stock rom does not have any problems with your internal storage, then flash to the latest nightly of albinoman's CM11 and see if that does the trick.
Just to be extra careful, you are wiping the "data", "cache", and "dalvik-cache" using TWRP, then rebooting to the bootloader and flashing the boot.img from the zip file through fastboot, then flashing the zip file using TWRP, right? The order of wiping and flashing the boot.img can be switched, but they must be done before flashing the rom to try to prevent weird errors happening. Not trying to sound condescending, I just want to eliminate all possible causes.
teveisboss said:
Okay, so I'm new to everything Android in general, so all of this is very confusing to me, so I'm going to be as specific and in-depth as possible.
I'm using an HTC Vivid on AT&T and I just recently flashed CM 11, and I absolutely LOVE it, except for two problems.
The first has been widely acknowledged, and it's the problems with MMS. On the stock ROM, MMS was sometimes a problem, but that was usually because the Vivid had mobile data problems in general (problems which I still have not encountered on CM 11, which is good news). It happened that when the Vivid couldn't send or receive MMS, it also couldn't use the mobile data at all, and this was usually fixed by a reboot (which was a pain because ICS had that bug where it would always "optimize apps" every reboot). This was the problem I first suspected, except I tested the use of mobile data in other apps, and they worked perfectly, leading me to believe that this is not the same problem. Data usage works fine, it's a specifically MMS problem.
The second issue is something that I haven't seen addressed yet, so I guess it's a problem that only I have come across. I can't use the camera at all, because every time I try to open it, it says I need to insert an SD card. Now I know nothing about technology, so is it referring to the internal SD card, or the external? I have an external SD card for the phone, and it works with the Apollo music app and such, so I'm not sure if that's where it's supposed to be going. I can't even take pictures or record videos, because it won't let me, since I don't have an SD card apparently. Is there any way to fix this?
Thanks everyone for any help or advice you can offer.
EDIT: I'm guessing the camera problem is an internal storage thing, because my phone registers no internal storage at all. Nor does TWRP, it doesn't register an internal storage either. I'm still at a loss at how to fix this problem.
Click to expand...
Click to collapse

teveisboss said:
Okay, so I'm new to everything Android in general, so all of this is very confusing to me, so I'm going to be as specific and in-depth as possible.
I'm using an HTC Vivid on AT&T and I just recently flashed CM 11, and I absolutely LOVE it, except for two problems.
The first has been widely acknowledged, and it's the problems with MMS. On the stock ROM, MMS was sometimes a problem, but that was usually because the Vivid had mobile data problems in general (problems which I still have not encountered on CM 11, which is good news). It happened that when the Vivid couldn't send or receive MMS, it also couldn't use the mobile data at all, and this was usually fixed by a reboot (which was a pain because ICS had that bug where it would always "optimize apps" every reboot). This was the problem I first suspected, except I tested the use of mobile data in other apps, and they worked perfectly, leading me to believe that this is not the same problem. Data usage works fine, it's a specifically MMS problem.
The second issue is something that I haven't seen addressed yet, so I guess it's a problem that only I have come across. I can't use the camera at all, because every time I try to open it, it says I need to insert an SD card. Now I know nothing about technology, so is it referring to the internal SD card, or the external? I have an external SD card for the phone, and it works with the Apollo music app and such, so I'm not sure if that's where it's supposed to be going. I can't even take pictures or record videos, because it won't let me, since I don't have an SD card apparently. Is there any way to fix this?
Thanks everyone for any help or advice you can offer.
EDIT: I'm guessing the camera problem is an internal storage thing, because my phone registers no internal storage at all. Nor does TWRP, it doesn't register an internal storage either. I'm still at a loss at how to fix this problem.
Click to expand...
Click to collapse
Otay...
Try this...
Boot to TWRP
Go to mounts...
Mount USB storage...
Plug phone into computer...
See if windows offers to format your internal...
If yes... Reboot to OS... Problem solved...
DO NOT FACTORY RESET FROM HBOOT
Sent from my Vivid 4G using Tapatalk

projectisaac said:
Did you flash the most recent nightly, or the most recent stable? Probably a useless question, as the latest stable should be fine as far as the internal storage and everything (and I'm on the 1-28 nightly, which is not giving me any internal storage problems). I recommend flashing back to stock and seeing if the problem persists, because if so, then your problem is most likely not the CM11 rom. If the stock rom does not have any problems with your internal storage, then flash to the latest nightly of albinoman's CM11 and see if that does the trick.
Just to be extra careful, you are wiping the "data", "cache", and "dalvik-cache" using TWRP, then rebooting to the bootloader and flashing the boot.img from the zip file through fastboot, then flashing the zip file using TWRP, right? The order of wiping and flashing the boot.img can be switched, but they must be done before flashing the rom to try to prevent weird errors happening. Not trying to sound condescending, I just want to eliminate all possible causes.
Click to expand...
Click to collapse
rignfool said:
Otay...
Try this...
Boot to TWRP
Go to mounts...
Mount USB storage...
Plug phone into computer...
See if windows offers to format your internal...
If yes... Reboot to OS... Problem solved...
DO NOT FACTORY RESET FROM HBOOT
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
Hi guys,
Thanks for the replies, and sorry I'm so late, I had a few things to take care of over the weekend.
Anyway, good news, I solved the problem with internal storage by wiping the internal storage from within TWRP (didn't really know what I was doing, which is probably a bad thing, but it worked so I'm happy). Now the camera app works cleanly and everything.
The MMS problem continues to stump me, however. I've tried different APNs, different solutions that everyone has recommended, no luck. I will continue to search for a way to solve the problem
Thanks again.

projectisaac said:
The order of wiping and flashing the boot.img can be switched, but they must be done before flashing the rom to try to prevent weird errors happening. Not trying to sound condescending, I just want to eliminate all possible causes.
Click to expand...
Click to collapse
Actually, one more question. Was I really supposed to flash the boot.img first? Everything I read said to do it the other way around.... What kind of problems would that have caused? Maybe that's where I made an error, I flashed the rom first and then the boot.img afterwards.

teveisboss said:
Actually, one more question. Was I really supposed to flash the boot.img first? Everything I read said to do it the other way around.... What kind of problems would that have caused? Maybe that's where I made an error, I flashed the rom first and then the boot.img afterwards.
Click to expand...
Click to collapse
Y'know, looking at it again it probably doesn't matter, given the differing instructions here (http://forum.xda-developers.com/showthread.php?t=2423277) and here (http://forum.xda-developers.com/showthread.php?t=2524934). The main reason they would have you flash the boot.img first is because it may not let you boot into the rom, but as long as you go from flashing the rom to flashing the boot.img without booting up the rom, it should be fine.

projectisaac said:
Y'know, looking at it again it probably doesn't matter, given the differing instructions here (http://forum.xda-developers.com/showthread.php?t=2423277) and here (http://forum.xda-developers.com/showthread.php?t=2524934). The main reason they would have you flash the boot.img first is because it may not let you boot into the rom, but as long as you go from flashing the rom to flashing the boot.img without booting up the rom, it should be fine.
Click to expand...
Click to collapse
Ah, okay. Thanks for the help regardless.

won't update to 5.0.1

So I was on 5.0.1 via ota update before I unlocked and put paranoid android, love their roms in the past but not that great yet. Anyways for some reason I flashed 5.0 then locked and set my phone up and now I'm not receiving the 5.0.1 update. Is there something I'm supposed to change to make it update? For example with my HTC one you have a uid and model number. I put it back to stock Saturday and still have yet to receive the update or am I just being inpatient?

onthezone said:
So I was on 5.0.1 via ota update before I unlocked and put paranoid android, love their roms in the past but not that great yet. Anyways for some reason I flashed 5.0 then locked and set my phone up and now I'm not receiving the 5.0.1 update. Is there something I'm supposed to change to make it update? For example with my HTC one you have a uid and model number. I put it back to stock Saturday and still have yet to receive the update or am I just being inpatient?
Click to expand...
Click to collapse
Need more information. By flash did you flash a stock ROM from TWRP? Factory image from fastboot?
If you flashed the factory image why not just flash the 5.0.1 or even on of the 5.1 images?

Curious why you don't just flash 5.1 since you seem comfortable with the process
Sent from my Google N6 on VZ

_Dennis_ said:
Need more information. By flash did you flash a stock ROM from TWRP? Factory image from fastboot?
If you flashed the factory image why not just flash the 5.0.1 or even on of the 5.1 images?
Click to expand...
Click to collapse
I flashed the factory image through fastboot and then setup the phone and noticed I never got an update notice. Every phone I ever had showed the update right away so I didn't think it was a big deal to download the latest. If I flash through fastboot its going to wipe my phone right? Which that's what I want to avoid so I was hoping I was going to get the notification.

DebianDog said:
Curious why you don't just flash 5.1 since you seem comfortable with the process
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
I've always done it to make sure I will get ota since I've already gotten 5.0.1 before.

So other than flashing the stock image through fastboot and locking is there anything else I was supposed to do to make ota to work?

If you would just leave the phone unlocked you don't have to flash over everything you can just flash what you need while retaining user. I've updated this phone 2 times and haven't lost anything. It's that initial fastboot that gets you.
Sent from my Google N6 on VZ

DebianDog said:
If you would just leave the phone unlocked you don't have to flash over everything you can just flash what you need while retaining user. I've updated this phone 2 times and haven't lost anything. It's that initial fastboot that gets you.
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
So let me make sure I understand you, if I leave my phone unlocked and flash the full factory image it won't clear my user info or I have to wait for someone to post the ota to flash with out clearing my phone?

No you have to take the file apart and flash every image but the user. to make it easier to use the tool kit you can type commands or just let it do it for you.
Flash Stock pick your version no wipe mode
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But if you relocked it then yes you're going to lose everything. Why I believe everyone should have a copy of titanium backup.
Sent from my Google N6 on VZ

onthezone said:
So let me make sure I understand you, if I leave my phone unlocked and flash the full factory image it won't clear my user info or I have to wait for someone to post the ota to flash with out clearing my phone?
Click to expand...
Click to collapse
Your in the wrong hobby if u are worried about clearing your phone. I see people daily on xda complaining that their phone isnt working correctly and that they wont clean flash because of the time it takes to redo phone. Seriously? its not that bad of a deal. Set some time before hand to do it and move on. Clean flash and clean install and go from there.

the_rooter said:
Your in the wrong hobby if u are worried about clearing your phone. I see people daily on xda complaining that their phone isnt working correctly and that they wont clean flash because of the time it takes to redo phone. Seriously? its not that bad of a deal. Set some time before hand to do it and move on. Clean flash and clean install and go from there.
Click to expand...
Click to collapse
Let me put it this way, I have to reset my watch every time I redo my phone and reset my Bluetooth on my car which doesn't listen to me but will listen to my wife. Now if I could switch Roms without resetting my watch like what I use to be able to do with beelink then I would be cool with it. I take the time every time to do a clean install, start as a new phone. I'm just making sure this is normal not to get an update that's been out for my phone for a month. I have had a crap load of androids and they have never not giving me an update that's been out.
If google allowed us to switch phones with android wear without clearing, I would be happy to flash Roms again but its just too much of a pain to redo everything right now which is why I'm going back to stock.

DebianDog said:
No you have to take the file apart and flash every image but the user. to make it easier to use the tool kit you can type commands or just let it do it for you.
Flash Stock pick your version no wipe mode
But if you relocked it then yes you're going to lose everything. Why I believe everyone should have a copy of titanium backup.
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
Thanks I'll have to check that program out, I seen it this weekend but all I had on me was my Mac.

onthezone said:
Thanks I'll have to check that program out, I seen it this weekend but all I had on me was my Mac.
Click to expand...
Click to collapse
Yes I bootcamp for this and a few games Titanium backup looks like it will backup you Bluetooth and other settings too. Had the damn program 5 years just noticed lol
Sent from my Google N6 on VZ

DebianDog said:
Yes I bootcamp for this and a few games Titanium backup looks like it will backup you Bluetooth and other settings too. Had the damn program 5 years just noticed lol
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
I bet a lot changed since HTC inspire 4g days but restoring Bluetooth settings just seemed to cause more issues than helped IMO. I use to boot camp but I bought a gaming rig for my other expensive hobby and had to move windows over to it.