Database Develop

[Rom] Liberty3 For The Droidx 11/02 - Its Time For A Revolution!

Liberty 3
Its time for a Revolution!!!
{
"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"
}
Notes:
* Please Wipe Data regardless of what ROM you come from
You must be on at least build .602 to install this..
This is a 1st Init based so use the proper CWM
Team Liberty
Primary Dev’s and project leads - Kejar31, Jurmmy16 and Syaoran12
Dev - Mobile_Sensei
Artist - Koveleski
Thanks:
FABOLOUS for all his help on the DX port!
Thanks to Teamdouche for publicly posting the CM source, which I compiled some of my apps from
Thanks to Superteam and Dustin Jorge as Liberty-Laucher was forked from and based on their work
Everyone else who helped make this ROM possible - you know who you are
Features:
- Most all apps were built from source.... rather that decompiled and hacked apps via APKmanager!!!!! To do this I took the CM7 source tree and reworked the framework to allow apps to properly find resources after they were compiled.
- The only apps left from Blur are the Dialer, Contacts and Camera
- AppWidgetPicker - built byboombuler
- Ads blocked via hosts file -thanks to delta_foxtrot2
- 1% battery increments built in (Icons made by thanks to Nitro)
- Themed Dialer, Contacts, Task Manager by me to integrate into the stock GB look and feel
- Reboot options (Reboot,Recovery and Screenshot)
- DSPManager included
- Custom Launcher2 with extra hotseats and speed tweaks (lightest fastest launcher you will ever use)
- Liberty Customizer (choose to add back blur apps)
- Lockscreen options (rotary, sliding tab and music controls)
- Start-up Tweaks (tool to allow you to manager your start-up tweaks)
- Root Browser (full edtion that normally comes with the pro version of the ROM toolbox - no need for Root explorer any-longer)
- Root Toolbox
Known Issues:
Disclaimer:
I nor anyone in Team Liberty take any responsibility for what this ROM or its tools may do to your phone.
Download:
Liberty3 for the DroidX 1.0
Option #2 - download rom toolbox -> go to rom manager -> liberty
Updates:
Install - CWM only:
make sure you have root and Clockwork recovery installed
-boot into recovery via Recovery
-select "wipe data/factory reset"
-select "Yes -- delete all data"
-go back
-select "install zip from sdcard"
-select "choose zip from sdcard"
-find and select LibertyXX.zip
-reboot
Install Themes:
-boot into recovery via Recovery
-select "install zip from sdcard"
-select "choose zip from sdcard"
-find and select LibertyXthemeX.zip
-reboot
Donate:
Donate to Kejar31
Donate to Jrummy16
Screenshots

so system version 4.5.605 is good right?

Just got driod x to hold me over til g-nex i got couple of ?s
ok sorry if these will be considered noob ?s but i was wondering is .602 gingerbread(i mean can i flash from gingerbread blur rom) also can you flash kernels on dx? and lastly is this a release candidate or is a release? sorry i have one last ? this does not have theme manager right?
ps: i will be putting this on my dx as soon i get my battery in the mail i put froyo liberty on my nieces and it is amazing i bought the tool box for it already and i love liberty's work

JackTheRipper13 said:
so system version 4.5.605 is good right?
Click to expand...
Click to collapse
Yes in fact this is based on .605

Can I flash this if I am on liberty Gingerbread v0. 9?? Obviously I would do a complete wipe just not sure if I have I can come from 0.9
Sent from my DROIDX using XDA App

http://forum.xda-developers.com/showthread.php?p=19050241#post19050241
Liberty 3 settings work around.
Edit:
You can also use SM to install and create SC for com.liberity.activity.commands.
Screenshot will work also just had to push the bin file and change perm. to all(6), at least on my Dx2.

The greatest version of Liberty YET!! I love the feel of this ROM, Not as many features as Liquid 3.1 but still a great achievement. It's a shame that most of us are going to move on to 4.0 and a new phone in the coming weeks. ..
May all our dreams be filled by ICS and be replaced ASAP with something shiny and faster! Google is the sickness that drinks our blood and fills my eyes with sick bright sparks.

a revolution...
sounds great,download for test...
thanks
Sent from my DROIDX using xda premium

Sorry wrong one...

anyone else having issues with most apps in the market saying they are "not compatible with your device"?? Very annoying. Even with LCD Density on default 240. Ideas?

Haven't had a X for a long time now. So trying to do this on a friend's phone. Installed CWM 5.x version from ROM Manager and trying to reboot recovery from the rom manager app, led me back to the OS and not the recovery.
Then installed Droid 2 Bootstrapper, and rebooted, but got a CWM 2.5 recovery. Didn't want to install from there since that didn't seem right. So what am I supposed to do now ?

Installed fine... but wasn't nearly as smooth as the OTA 2.3.3 blur I had on...am I missing something?

Install issue,
I'm reading a lot of positives about Liberty 3 so I gave it a go. Here is what I did and am going to try again. If anyone can see where I am going wrong jump on in and hook a noob up.
I have been rooted for a while and tried several roms. I saw the liberty but it said I had to hace the OTA GB update. so:
1. I SBFd to 2.2.1 and took the OTA and am now on .605
2. rooted via pete (installed root checker just to be sure) im rooted,
3. got bootstrapper 2
4. Got Rom Manager and flashed to DX
5. Intalled Rom tool box and downloaded Liberty 3
6. followed instructions for install
When it re booted all that comes up is the Liberty Eagle spinnin around and absolutely would not do anything else soooo
I repeated steps 1-5 and am ready for another try... Any thoughts suggestions or pleasant comments?

malloneem said:
I'm reading a lot of positives about Liberty 3 so I gave it a go. Here is what I did and am going to try again. If anyone can see where I am going wrong jump on in and hook a noob up.
I have been rooted for a while and tried several roms. I saw the liberty but it said I had to hace the OTA GB update. so:
1. I SBFd to 2.2.1 and took the OTA and am now on .605
2. rooted via pete (installed root checker just to be sure) im rooted,
3. got bootstrapper 2
4. Got Rom Manager and flashed to DX
5. Intalled Rom tool box and downloaded Liberty 3
6. followed instructions for install
When it re booted all that comes up is the Liberty Eagle spinnin around and absolutely would not do anything else soooo
I repeated steps 1-5 and am ready for another try... Any thoughts suggestions or pleasant comments?
Click to expand...
Click to collapse
Did you wipe data/factory reset? I was on the CM7 nightlies, all that I had to do was boot into cwm, wipe data, flash the tbh .605 update, wipe data again, remount system, flash liberty 3 zip, and reboot... first boot scared me but after 10 mins it did load(I was stuck on the spinning logo for a long time) maybe you can try again and see if it will load... just be patient, as the first boot takes a really long time.
Sent from my SGT running CM7

thisguy23 said:
anyone else having issues with most apps in the market saying they are "not compatible with your device"?? Very annoying. Even with LCD Density on default 240. Ideas?
Click to expand...
Click to collapse
I'm having the same issue, after some googling still cant find an answer. Is this Liberty or something else?

I'm getting freeze/lockups frequently, a few times a day. Usually in text or browser, but could be anywhere. Did a pretty clean install-wiped everything-data/factory resest/dalvik. Any thoughts? Liking it otherwise, but getting frustrated.

OK, I have an epic 4g touch, but a friend has an x and wants this rom. I have tried to learn up on what is required for a custom rom installation, but its. . . Different than Samsung phones and I'm lost. She was able to root the phone herself, so she isn't phone retarded. So we have a rooted Verizon x with 2.3.3, no custom recovery or rom. What is my next step to getting this rom? What are build numbers and how to I get on the correct one? How do I get a working recovery like cwm to make a nandroid and flash this?
If I was helpful, give thanks
Sent from my Epic 4g Touch

The Odom Project said:
OK, I have an epic 4g touch, but a friend has an x and wants this rom. I have tried to learn up on what is required for a custom rom installation, but its. . . Different than Samsung phones and I'm lost. She was able to root the phone herself, so she isn't phone retarded. So we have a rooted Verizon x with 2.3.3, no custom recovery or rom. What is my next step to getting this rom? What are build numbers and how to I get on the correct one? How do I get a working recovery like cwm to make a nandroid and flash this?
If I was helpful, give thanks
Sent from my Epic 4g Touch
Click to expand...
Click to collapse
1. Phone needs to be on one of the versions of the over the air Gingerbread updates from Verizon, definitely at least the .602 update but preferably 4.5.605.MB810.Verizon.en.US. If it's NOT, then look up how to SBF it to the correct version.
2. Root with your favorite method, I used PSouza4's One Click Root
3. Install Koush's Droid 2 Bootstrap (download from Marketplace or his website)
4. Put this ROM on your SD card
5. Use the Bootstrap to... Bootstrap Recovery, then Reboot Recovery
6. Clear everything like you would to flash any other ROM.
7. Install ROM from SD card.
Or that's what I did and it worked.
sonicshaman said:
I'm getting freeze/lockups frequently, a few times a day. Usually in text or browser, but could be anywhere. Did a pretty clean install-wiped everything-data/factory resest/dalvik. Any thoughts? Liking it otherwise, but getting frustrated.
Click to expand...
Click to collapse
I installed from the 605 update with no problems, is that the version that you came from?

funnce said:
1. Phone needs to be on one of the versions of the over the air Gingerbread updates from Verizon, definitely at least the .602 update but preferably 4.5.605.MB810.Verizon.en.US. If it's NOT, then look up how to SBF it to the correct version.
2. Root with your favorite method, I used PSouza4's One Click Root
3. Install Koush's Droid 2 Bootstrap (download from Marketplace or his website)
4. Put this ROM on your SD card
5. Use the Bootstrap to... Bootstrap Recovery, then Reboot Recovery
6. Clear everything like you would to flash any other ROM.
7. Install ROM from SD card.
Or that's what I did and it worked.
Click to expand...
Click to collapse
Thank you. I imagine SBF is a lot like Odin on Samsung so that isn't too hard. The rest I was kind of picking up, but wasn't sure.
If I was helpful, give thanks
Sent from my Epic 4g Touch

thisguy23 said:
anyone else having issues with most apps in the market saying they are "not compatible with your device"?? Very annoying. Even with LCD Density on default 240. Ideas?
Click to expand...
Click to collapse
I ended up changing the density back to 240, clear data for both Market and Google Services Framework, reboot. Market worked after that, but was missing some apps, so I ran the market check from Titanium Backup.
After setting the density back to a custom value, the market still appears to be working properly.

An annoying issue after upgrading to V4.0.4

After upgrading from V4.0.3 to V4.0.4 (from kies), the main scheen shows the annoying box (only on the 7 main screes, not elsewhere) with some H/W info as screen shot below, I tried to manually download the ROM, perform double wipe and reload the ROM agian, the issue remains, has any one encountered the same problem, any one has any ideas can help me with this ? :crying:
{
"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 didn't experience this to my DXLR5 4.0.4.
Sent from my GT-N7000 using Tapatalk 2

ryn888 said:
I didn't experience this to my DXLR5 4.0.4.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Thanks, I did surf the internet for a while but not able to find any similar problem as I have, that's why I post here to seek some expert support ...

:crying:
I need some help.
These should be someone/expert can sort this out ..
HELP / HELP !!

This is due to broken EFS
If you have EFS backup, restore it.
Otherwise Reflash GB ROM, someone reported it worked by flashing GB ROM with wipe cache and data.

dr.ketan said:
This is due to broken EFS
If you have EFS backup, restore it.
Otherwise Reflash GB ROM, someone reported it worked by flashing GB ROM with wipe cache and data.
Click to expand...
Click to collapse
Thanks, Ketan,
I don't have EFs backup,,,
But when I read some other articles, it says the lost of EFS will have some symptoms , ie: IMEI gone (I can check my IMEI by "*#06#"), no signal (I am OK to make/receive the call)... etc, it seems I may not have EFS issue ??
Also, I did try to downgrade to V4.0.3 when I encountered the issue on V4.0.4, everything is fine
At first I thought there is something wrong with the V4.0.4 ROM (my first upgrade was from Kies directly), so I manually download the ROM (actually I've compared the ROM from Kies and the one I downloaded, they are identical),,,anyway, I used Odin to upgrade again, and the problem comes up again..
that is to say, with V4.0.3, the phone has no any issues, with V4.0.4, the only issue is the annoying H/W info box shown on the 7 main screens....
Any more ideas or detail instruction would be very much appreciated ...

As i said its just broken efs, where still you dont lose imei. But you can try this
Downgrade to lower version where there is no issue, take efs backup.
Then update to newer version and restore backup when issue appear back.
Sent from my GT-N7000 using xda premium

am getting annoyed by another problem. The WiFi switches off automatically and gets connected when i touch the screen..
This is annoying me as all the updates happen while the display is off and it is getting those using 3G and not the WiFi...
Is it just me ?
I did not install any app after the upgrade form 4.0.3 to 4.0.4

Just go to.setting - wifi -advance - keep wifi on during sleep - Change to 'always.'
Then wifi.wont.auto off.
Sent from my GT-N7000 using xda premium

cool.. almost forgot that .. How the Heck did it change to Never.. does the update change the settings ??
One more thing .. now my Apex launcher restarts everytime .. i remember there was a place where we can change the no.of apps running in the background .. Can you tell me where this is ?

You mean
Setting -development -restrict number of background process?
Sent from my GT-N7000 using xda premium

any option like that in Stock ROM which might have been changed by the upgrade ?

As said above?.i have edited
Sent from my GT-N7000 using xda premium

just checked and it is set to default ... no changes there .. humm.. Thanks Again Ketan.. will look for alternate Launchers.. Any suggestions ?
or should i just take the jump and go for Paranoid Android

dr.ketan said:
As i said its just broken efs, where still you dont lose imei. But you can try this
Downgrade to lower version where there is no issue, take efs backup.
Then update to newer version and restore backup when issue appear back.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Hello, Ketan,
I followed your suggestion to downgrade to V4.0.3, of course, it is problem free menaing no annoying box shown on main screen
Then I root to install HC-Ktool and backup efs
and then unroot and upgrade to V4.0.4 again, the annoying box come up ...
Then I root again to run HC-Ktool and restore EFS, and restart
without luck ,,, the annoying box is still there,.,,, any thoughts ?

easternpig said:
Hello, Ketan,
I followed your suggestion to downgrade to V4.0.3, of course, it is problem free menaing no annoying box shown on main screen
Then I root to install HC-Ktool and backup efs
and then unroot and upgrade to V4.0.4 again, the annoying box come up ...
Then I root again to run HC-Ktool and restore EFS, and restart
without luck ,,, the annoying box is still there,.,,, any thoughts ?
Click to expand...
Click to collapse
tell me the procedure you are following in flashing the roms and please try to downgrade to a safe gingerbread rom then root it or use pre-rooted gb rom from DR.KETAN'S GUIDE.

easternpig said:
Hello, Ketan,
I followed your suggestion to downgrade to V4.0.3, of course, it is problem free menaing no annoying box shown on main screen
Then I root to install HC-Ktool and backup efs
and then unroot and upgrade to V4.0.4 again, the annoying box come up ...
Then I root again to run HC-Ktool and restore EFS, and restart
without luck ,,, the annoying box is still there,.,,, any thoughts ?
Click to expand...
Click to collapse
I read some other user's experience on S2 too. But sorry nothing found that works 100%,
It not happens to everyone, so may be it should have relation with previous ROM(even on OTA update it can happen). May be just try to downgrade to GB ROM, root it , wipe cache, data,delvic cache, and use Mobile odin to update 4.0.4. Thouh this is just speculation on basis of clean install. I dont have review that this will work.

shivg86 said:
tell me the procedure you are following in flashing the roms and please try to downgrade to a safe gingerbread rom then root it or use pre-rooted gb rom from DR.KETAN'S GUIDE.
Click to expand...
Click to collapse
I used PC Odlin to flash the PDA only, the ROM was official ROM from http://samsung-updates.com/device/?id=GT-N7000.
note that I upgraded the version through Kies firstly, previously I was on V4.0.3 official rom (rooted) - without this issue
the issue was appeared after the official (kies) 4.0.4 upgrade
I tried to downgrade to V4.0.3 (obtain the ROM from the link said above), the problem gone ...
then I upgrade to V4.0.4 again (as mentioned in my last note, EFS is not a matter here) - problem back again
during several trials, I aslo tried to reset the phone, (try on double wipe as well al reset to syatem default from system setting menu) and redo all those steps, but still unlucky .. None of any actions can help ...
btw : I read other articals saying to refresh kernal and double wipe ,,, no help as well ...
it drives me crazy ...

easternpig said:
I used PC Odlin to flash the PDA only, the ROM was official ROM from http://samsung-updates.com/device/?id=GT-N7000.
note that I upgraded the version through Kies firstly, previously I was on V4.0.3 official rom (rooted) - without this issue
the issue was appeared after the official (kies) 4.0.4 upgrade
I tried to downgrade to V4.0.3 (obtain the ROM from the link said above), the problem gone ...
then I upgrade to V4.0.4 again (as mentioned in my last note, EFS is not a matter here) - problem back again
during several trials, I aslo tried to reset the phone, (try on double wipe as well al reset to syatem default from system setting menu) and redo all those steps, but still unlucky .. None of any actions can help ...
btw : I read other articals saying to refresh kernal and double wipe ,,, no help as well ...
it drives me crazy ...
Click to expand...
Click to collapse
dr.ketan said:
I read some other user's experience on S2 too. But sorry nothing found that works 100%,
It not happens to everyone, so may be it should have relation with previous ROM(even on OTA update it can happen). May be just try to downgrade to GB ROM, root it , wipe cache, data,delvic cache, and use Mobile odin to update 4.0.4. Thouh this is just speculation on basis of clean install. I dont have review that this will work.
Click to expand...
Click to collapse
Tried on this ROM SGN_XX_OXA_KJ1_FACTORYFS, no issue, then follow the instruction ,,, root it , wipe cache, data,delvic cache, and use Mobile odin to update 4.0.4,, that annoying box still happens ... My Goooooood ....

I had talk with samsung service centre guy(who is really noob, and owner sending his device to me to root ), he said he had email regarding this. I am planning to go to SSC to read mail what exactly he got information, really here in my town very small service centre. he couldn't even find out what set of instruction exactly there on mail
Lets see if anything special. This is likely ROM bug, b'coz some one who have updated from OTA, also get this.

[Q] - Simple route to GB bootloaders from ICS w/Froyo BL

The title pretty much says it all. I've been reading for days and my eyes are burning yet I still haven't found anything exactly like what I'm asking...and I don't want to keep asking stupid questions in the dev section.....
I was on a custom Froyo ROM for a long time and finally got around to trying out SlimICS 4.2 a couple of weeks ago. The instructions called for a CM9 flash first, then SlimICS. It all worked perfectly and I love the ROM.
I've never tried GB and am still on Froyo bootloaders. I would like to switch to GB bootloaders, maybe for no good reason at all. I figure in the long run it will be a good idea. (different rom, kernel, JB, whatever)
I was told that trying to use Odin to simply flash GB bootloaders over an ICS rom and kernel might be a bad idea. I'm hoping someone has successfully done this but most of my reading has got me feeling a bit cautious about bootloaders...
I'm looking for a simple, logical sequence to get me back exactly where I am (ICS) but with GB bootloaders. Perhaps back to a custom Froyo rom/kernel then flash GB bootloaders then back to ICS? I'm guessing that cwm will be able to restore the state of my current rom after all that. I'm so sick of setting up everything from scratch and Titanium can only do so much....
Thanks

Here ya go...
U cannot flash the GB Bootloaders while you are running a Rom that has the mtd/yaffs or yaffs2 partition, that is, a CM, MIUI, ICS, JellyBean and such like. U will need to be on a bml/rfs partition, that is, a Stock Rom or at least a Dev Rom based from a stock firmware.
Do an Nandroid Backup on what you are running currently.
Backup everything you do want to save...apps, contacts, messages, emails, pics, efs folder, etc.
Then you will need to flash back to Stock GB Firmware with Bootloaders included. The i897ucKK4 is the latest official. Here is Stock I897UCKK4 Android 2.3.5 One Clicks. Use the Odin or Heimdall version that includes the GB Bootloaders. If you have a newer Captivate that does not like using the One Clicks, then see this thread for the .tar package of the i897ucKK4... [ROM] I897UCKK4 [17.11.2011][Android 2.3.5]. With this you will probably have to wipedata/factory reset first. Then use regular Odinv3 1.83 or similar to flash it. **Note: Flashing Bootloaders is risky. So be sure you have a trust worthy micro usb/usb cable, constant power source, etc. You don't want to loose power or connection during the few seconds that the bootloaders are being flashed. Bad bootloader flash = hard brick.
Once you are successfully back on Stock KK4, then go to this thread... [KERNEL][KK4][1/28/11] Corn Kernel and use the regular Odin to flash the .tar 7.0A version of this kernel. This will give you the CWM Recovery that you need.
Then reboot into CWM and reinstall the ICS Rom you were on before per that Rom's install instructions.
Once you are booted up on that ICS Rom, reboot into the Recovery of that Rom and then you can Restore your backup that you did at the beginning of this process.
You should be good now.
For issues along the way with connections to the pc, download mode, etc. please see this thread... Captivate Connection Issues and Download Mode Help

The most direct route would be to flash a Gingerbread-based Stock rom with bootloaders from your current setup. This will put you back at stock (including your partitioning), so you'll have to flash as if you're going to CM-based roms for the first time when you go back to ICS/JB.
Obviously, there's all the normal cautions of backing up, bootloader dangers, etc.

@ jmtheiss... I Ninja'd ya by a few minutes. Lol
{
"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"
}

They both said it better than I could have but what it comes down to is there is no "simple" way to go about what you are wanting to do...
Sent from my SGH-I897 using xda app-developers app

I don't think a lousy "thanks" even begins to cover it. I really appreciate when someone puts that much effort into helping somebody out. Cheers!
And that definitely qualifies as "simple" enough...better than something requiring rooting again and getting a functional recovery, etc. A couple of Odin sessions and a couple of cwm flashes are fine.
Thanks again guys.

bcflyfisher said:
I was told that trying to use Odin to simply flash GB bootloaders over an ICS rom and kernel might be a bad idea. I'm hoping someone has successfully done this but most of my reading has got me feeling a bit cautious about bootloaders...
Thanks
Click to expand...
Click to collapse
I have done it successfully a couple of times without any issues. I have only done it when absolutely necessary since they do say there's some risk there.
What I don't understand is how you *could* run ICS without GB bootloaders? I didn't think that was possible.

I'm living proof. I was hesitant but their instructions said if coming from Froyo flash CM9 first then SlimICS. I flipped a coin and it worked fine. The developer of Slim (krarvind) knows I'm on Froyo bootloaders and didn't seem too phased by it. Whether or not I'd be able to jump to JB with whatever kernel is unknown so I'm going to backtrack a little and do what I probably should have in the first place.

Here's an update of what I did just in case it's helpful to someone else down the road.......
I did my best to follow the suggestions given by 4-2ndtwin in the 2nd post. I generally have pretty good backups of everything done but I did new ones just for kicks. Nandroid, Titanium Backup, efs, SMS, call log, APN, and a few other things. I downloaded all the necessary files, and laid them all out sequentially on my screen so I wouldn't get distracted and screw up. In the end I'm pretty much exactly where I wanted to be but of course there were a few unexpected issues.
- The Heimdall One-Click of stock GB with bootloaders was very easy. I had Samsung drivers on the computer already but Heimdall insisted on installing new ones. After that it did its thing and I was on official KK4 with GB bootloaders.
- Next up was regular Odin flash of the Corn Kernel. When I connected the phone in download mode Odin didn't give me a yellow light. If I connected the phone while it was NOT in download mode Odin recognized it. I wasted at least an hour to discover that it was just a driver issue. The drivers that Heimdall wanted weren't "good enough" for Odin. Interestingly, neither was the original package I had on the computer. The one that worked was called "Samsung_USB_Driver_for_Mobile_Phones.zip" from the Samsung website. After installing that Odin saw my phone in download mode and I was able to install the Corn Kernel. Rebooting into recovery gave an option to root the phone.
- At this point everyone in the world decided they needed something from me so between work and phone calls/texts I ended up using the phone on GB for a while.
- My boot screens had been a total mess since my first custom rom so I decided to do the boot screen fix next - http://forum.xda-developers.com/showthread.php?t=1065743 - TRusselo added a bunch of good info to the thread and there's a good post on page 10 from irishvandal that explains the whole sequence of boot screens and what you can and cannot change.
- So the next step should have been to flash CM9 on my way back to SlimICS just like I did a month ago. I figured since I had been using the phone for a couple of hours I should wipe everything ... so I did the cache, data, format system, dalvik cache, and then I went to flash CM9 and noticed that for some reason I didn't have the zip file on the phone any more. I must have deleted it myself because nothing else spontaneously disappeared. When I rebooted normally to plug the phone in and transfer files I discovered that in wiping/formatting I messed something up and I kept getting stuck on the Corn Kernel boot screen. I could get into recovery or download mode just fine, just no normal boot. I was able to mount storage in recovery but when I tried to copy over the CM9 zip it kept hanging. After numerous attempts I decided to just go right back to the beginning.....
- Heimdall once again wanted its own drivers. No problem, I did that, then uninstalled them and reinstalled the drivers Odin likes, then got Corn again, did the boot screen fix again just to try a different image, then downloaded a new CM9 Nightly and copied it to the SD, flashed it with no issues, then flashed SlimICS (which actually has 2 zips plus addon packages) and I was back to ICS with GB bootloaders. It's amazing how fast things can be done when there are no more surprises!
- When the phone was rebooting into Slim ICS I got a message I don't remember seeing before - "Android is upgrading" or something similar. Weird. The next time I booted to recovery to try to restore the nandroid backup I ended up in CWMR Touch v5.5.0.4, which is weird looking and makes me feel strange. When I tried to do a full restore it encountered a few issues such as not being able to restore data normally. I don't recall the details but when I reinstalled Titanium Backup it would just FC so I couldn't restore any of my other apps. The "solution" was to reflash the Slim zips and do a restore of the system only. This set up all the tedious stuff for me. I got TiBu again and restored apps+data and that worked. Chose my launcher and it was back almost the way I wanted it. Interestingly, I had to replace the widgets but the shortcuts were all there in the right places.
- Voice search force closed. Slim doesn't include it in the base rom but it's available as an add-on and I had the zip on the sd from last time but flashing it didn't fix the problem (it had worked the first time I installed Slim). Some random sequence of freezing the Voice Search app, wiping its data, reflashing the Voice zip, unfreezing the app and it worked. In the process I noticed that in TiBu it was originally listed as Voice Search 2.x.x but then it was suddenly 3.x.x with a different icon. Then an hour later after all kinds of restoring (SMS, call log, etc) voice was force closing again. It was also listed as 2.x.x. This time it took me twice as long to randomly do things until it started working again (and at the same time it turned back into 3.x.x. It's been fine since...
So again a huge thanks for the advice! I got to spend the better part of a day fighting my way through minor issues but I learned a lot about my phone and got over my aversion to Odin for the last time. Hopefully someone else can benefit from something I've gone through. If nothing else, I feel a renewed sense of accomplishment.

^
If all ur ics and jb roms have run well...then i see no need to flash the bootloaders.
Sent from my SAMSUNG-SGH-I897 using xda premium

[Q] [HELP !] Bricked my GT-P1000 ?

Hello right here,
Got an big issue on my GT-P1000 :crying:, hope i'll find help and answers around :angel:.
First of all, i'm french, so please apologize my english if it's not as good as i'd like to (and feel free to correct me if necessary, it'll help !)
So, i bought a few years ago a GT-P1000.
Trying to change the rom, the official one was too slow .
First of all, rooting, yet some problems : all the processes i followed told me it was OK, and when i ran Root Checker, it told me the opposite (not root access). After a few tries, i thought Root Checker was the probleme, so news step : CWM installation.
Nickel, all good.
Last step : download and install Cyanogen Mod 10.2 (Android 4.3) following this tuto : computechips (can post a link )
And the result is : the tab won't boot any more. I restored it, and same thing, stays sticked on the "samsung" welcome screen, no more movements.
I still can go to the Recovery Mode, but there are messages telling that no drive can be mounted :
Code:
E: unknown volume for path [/system]
E: Unable process volume ! skipping ..
Checking /data..
E: unknown volume for path [/data]
E: unknown volume for path [/data]
E: Unable process volume ! skipping ..
Checking /cache..
E: unknown volume for path [/cache]
E: unknown volume for path [/cache]
E: Unable process volume ! skipping ..
Done !
And so on ..
Any idea on this issue ?
Thx !
Oliv.

Download the Overcome Recovery http://forum.xda-developers.com/showthread.php?t=1881981
Install the SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe
The Odin3 v1.7 is the Windows Software Flasher for all Samsung Devices.
There will be a number of different Folders each with a different "modem.bin" File in them. Unless you have a very specific version of the P1000 that requires such a unique modem.bin File (i.e. You have a CDMA Phablet). You should just use the standard JPZ (GSM) modem.bin version.
So after you have installed the USB Driver(s)
On your Phablet press the Volume Button DOWN + the Power Button till you see this Screen
{
"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"
}
Then start Odin3 v1.7 and connect your Phablet to your Computer
Pit -> gt-p1000_mr.pit
PDA -> GB_Stock_Safe_v5.tar
Phone -> modem.bin**
This should drop you back to v2.3.3. Gingerbread again.
Word of advice stick to only CM10 Builds! ALL CM10.1, AND CM10.2 BUILDS CONTAIN MASSIVE BUGS IN THEM, that kill off either the (Front) Camera, or the Bluetooth Radio Stack, or in most cases BOTH! Pretty much all of the CM10 Mods I've tried DO NOT have these problems and both the (Front) Camera, and Bluetooth are working.
**VERY IMPORTANT DO NOT FORGET TO ADD THIS FILE OR YOU WILL TRULLY SOFT-BRICK YOUR PHABLET!
If you do this I'm not sure if you can get back to the Download mode anymore or not. I think that I was able to on occasion though. in this case though just assume that you'll need the Heimdall One-Click Unbrick though.
http://forum.xda-developers.com/showthread.php?p=15330252

Ichijoe said:
Download the Overcome Recovery http://forum.xda-developers.com/showthread.php?t=1881981
Install the SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe
The Odin3 v1.7 is the Windows Software Flasher for all Samsung Devices.
There will be a number of different Folders each with a different "modem.bin" File in them. Unless you have a very specific version of the P1000 that requires such a unique modem.bin File (i.e. You have a CDMA Phablet). You should just use the standard JPZ (GSM) modem.bin version.
So after you have installed the USB Driver(s)
On your Phablet press the Volume Button DOWN + the Power Button till you see this Screen
Then start Odin3 v1.7 and connect your Phablet to your Computer
Pit -> gt-p1000_mr.pit
PDA -> GB_Stock_Safe_v5.tar
Phone -> modem.bin**
This should drop you back to v2.3.3. Gingerbread again.
Word of advice stick to only CM10 Builds! ALL CM10.1, AND CM10.2 BUILDS CONTAIN MASSIVE BUGS IN THEM, that kill off either the (Front) Camera, or the Bluetooth Radio Stack, or in most cases BOTH! Pretty much all of the CM10 Mods I've tried DO NOT have these problems and both the (Front) Camera, and Bluetooth are working.
**VERY IMPORTANT DO NOT FORGET TO ADD THIS FILE OR YOU WILL TRULLY SOFT-BRICK YOUR PHABLET!
If you do this I'm not sure if you can get back to the Download mode anymore or not. I think that I was able to on occasion though. in this case though just assume that you'll need the Heimdall One-Click Unbrick though.
http://forum.xda-developers.com/showthread.php?p=15330252
Click to expand...
Click to collapse
Thx Ichijoe, very much !
I try this right now (as soon as all files are dl). Simple question : Odin3 v1.7 ou v 1.85 (the one on the post you gave me), same thing ?

Olif5978 said:
Thx Ichijoe, very much !
I try this right now (as soon as all files are dl). Simple question : Odin3 v1.7 ou v 1.85 (the one on the post you gave me), same thing ?
Click to expand...
Click to collapse
It shouldn't matter, I think latter versions of Odin3 have more options in them that may confuse newer users, (i.e. Bootloaders) besides its not like you have to use the latest version to do this.
Needless to say you do NOT want to go f***ing round with the Bootloaders unless you have a way to recover. You can do almost anything you like to your Phablet. just DO NOT play with the Bootloader otherwise your "Soft-Brick" will instantly turn into a "Hard-Brick", and then you can go and find a JTAG Programer on Fleabay!
So your better off just sticking to Odin3 v1.7 for now.

Thx !
Ichijoe said:
It shouldn't matter, I think latter versions of Odin3 have more options in them that may confuse newer users, (i.e. Bootloaders) besides its not like you have to use the latest version to do this.
Needless to say you do NOT want to go f***ing round with the Bootloaders unless you have a way to recover. You can do almost anything you like to your Phablet. just DO NOT play with the Bootloader otherwise your "Soft-Brick" will instantly turn into a "Hard-Brick", and then you can go and find a JTAG Programer on Fleabay!
So your better off just sticking to Odin3 v1.7 for now.
Click to expand...
Click to collapse
Hello here !
I just wanted to thank you, ichijoe, as i managed to restore my tab following your advice :good:.
I tried once more to pass the 10.2 cyanogen mod rom, unsuccessful, exactly the same issues.
I'll try to pass the 10.1 one of these days ...
Anyway, thanks a lot for your help, i wa sreally afraid to lose my tab ...
Olif

Olif5978 said:
Hello here !
I just wanted to thank you, ichijoe, as i managed to restore my tab following your advice :good:.
I tried once more to pass the 10.2 cyanogen mod rom, unsuccessful, exactly the same issues.
I'll try to pass the 10.1 one of these days ...
Anyway, thanks a lot for your help, i wa sreally afraid to lose my tab ...
Olif
Click to expand...
Click to collapse
My advice is to just stick to the lastest CM10 Release 20130203
for now as this ROM if not, working @ 100%! then most certainly @ 99.9% as far as both the Camera and Bluetooth are concerned!
At this point we're better off waiting for KitKat ROMs then updated Jelly Baean Ones. AFAIK (And, TBH I'm just as new to this "Game"!), these Problems have been around as long as CM10.1, and CM10.2. i.e. for almost a whole Year now!
So I for One am not, holding my breath that this will be fixed soon-ish, at least not for CM's 10 .1 & .2...

CM11 KitKat
Ichijoe said:
My advice is to just stick to the lastest CM10 Release 20130203
Click to expand...
Click to collapse
I had a very hard time trying to flash something newer on my TAB, but finally I managed to have CM11 up and running. The latest nightlies now seem quite stable. I have created user profiles for my kids so as they cannot simply download any app and the device, uncluttered by games, is pretty fast now. It feels like a new tablet!

ha5x said:
I had a very hard time trying to flash something newer on my TAB, but finally I managed to have CM11 up and running. The latest nightlies now seem quite stable. I have created user profiles for my kids so as they cannot simply download any app and the device, uncluttered by games, is pretty fast now. It feels like a new tablet!
Click to expand...
Click to collapse
Hello ha5x,
What a good news !
I'm very interested in this solution. Would you mind making me a little how-to, with the good links to DL all it needs ?
Every time i try, there's a corrupted file, or a missing (404) file on the list ...
Regards,
Olivier.

Cannot remember how I did it
Olif5978 said:
Hello ha5x,
What a good news !
I'm very interested in this solution. Would you mind making me a little how-to, with the good links to DL all it needs ?
Every time i try, there's a corrupted file, or a missing (404) file on the list ...
Regards,
Olivier.
Click to expand...
Click to collapse
Hi Olivier,
I do not volunteer to write a how-to. In fact, I cannot remember how I did it. I myself had LOTS of such difficulties, errors, missing files, there were even several hours while I thought I had bricked the device which was responding to anything... It took me nearly three days flashing, cursing and flashing, cursing and flashing and cursing.
But what I have found is that you need to go step by step, flashing one ROM after another until you find one which comes with a recovery compatible with CM... I vaguely remember that a key step was flashing the "Overcome ROM", which then let me great step further.
Sorry.

You have to flash CM 7, then CM9, and finally CM 10 or 11. Your choice. Just make sure you have the right recovery installed and CWM version. I would skip the gapps til the last version you flash. Follow the directions for each CM version on xda.
Sent from my SCH-I800 using xda app-developers app

This is how i flash CM11..
Go to download mode
1) Restock using Overcome method..(via Odin) http://forum.xda-developers.com/showthread.php?t=1881981
-just the stock safe with my support modem..which is JPZ modem..no need to flash the Overcome Rom
-let it boot
Go to download mode again
2) Flash the Overcome Kernel..for root access and custom recovery..(via Odin)
-let it boot
(Step 1 and 2 is not necessary if you already using custom rom..but i like to do a clean flash..and if you still using the official firmware..step 1 and 2 is necessary..)
Go to Recovery
Do a clean wipe..(data,partition,dalvik,cache ect)
3) Flash CM10.2 for Kernel 3.0.x...(via custom recovery) Any CM10.2 With Kernel 3.0.X
-3x flash (first for CMW recovery..second for partition layout..third for CM10.2 Rom)
-let it boot
Go to Recovery
Do a clean wipe..(data,partition,dalvik,cache ect)
4) Flash the CM11..
5) Flash gapps..
6) Reboot
done..my p1 is running CM11..
and i did it without any problem..no crash or anything..
and i'm using storm31 CM1120131203..
with a few bug like front camera ect.(newer build already fix some of the bug)
or you can always go to the CM11 thread and read the OP for their instruction..
but always remember..
CREATE BACKUP
READ THE OP..and maybe a few comment first before you try to flash any rom..
just to make sure what are you going to experience..
i even read the whole thread before i start to flash any rom..
with that being said..
DO AT YOUR OWN RISK.. and Good Luck..:good:

[Q&A] [ROM]SGT7 CM11.0 UNOFFICIAL [4.4.4][P1/L/N][Kernel 3.0.x][2015-01-15]

Q&A for [ROM]SGT7 CM11.0 UNOFFICIAL [4.4.4][P1/L/N][Kernel 3.0.x][2015-01-15]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM]SGT7 CM11.0 UNOFFICIAL [4.4.4][P1/L/N][Kernel 3.0.x][2015-01-15]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

I wanted to install this room but now im stuck at CWM. I already flash CWM 3.0.0.5 with odin3 1.7, all went well. I put the zipped rom file in sd card, after I went into cwm menu, i cannot seem to install it from sd card. it seems that I cant mount the sdcard. anyone can help me please?

I was on twrp when i flashed my sgt to cwm. Can i install this rom with twrp in the bootloader? I am concerned i will be bricking my device.

Not boot
I install 15.01.2015 rom but my phone not reboot. Only Galaxy Tab Samsung screen stay.

atoygarh said:
I install 15.01.2015 rom but my phone not reboot. Only Galaxy Tab Samsung screen stay.
Click to expand...
Click to collapse
Which bootloader do you use?

I'm also stuck.
I started out with Overcome 4.1 which has been on this thing for a couple years now at least. So it had recovery and root already, has for a long time. All I did was copy the latest CM11 nightly which was 1-19-2015, and the Banks Gapps Standard 4.4.2 signed.
Since Overcome required recovery, I just hit the power button and told it to reboot into recovery. I had both the above zips installed on my microSD. Told recovery to wipe data/factory reset.
Then told recovery to install the CM zip. Install completed. Rebooted to what looks like a NEW recovery with the hat logo. Told me I didn't have root installed (which is weird, this was rooted, used Root Explorer so I'm not crazy) so I said sure and selected "Yes."
Told recovery to install the Gapps zip. Install shows the new look with the animated android guy's guts open while it installs zip.
Told recovery to reboot. Saw the Cyanogen boot screen after the Samsung one. Scroll bar on Cyanogen finishes, but................. Then it bounces me straight into recovery. Rebooted. Same thing two more times.
I just reinstalled both zips again and tried it. And still keeps bouncing me into recovery.
So I guess the good news is I'm still in recovery. The bad news is my amateur knowledge isn't sure where to go next after a couple hours straight of reading threads.
Help very much appreciated. Gonna charge up the battery while I wait for assistance here.
---------- Post added at 05:27 PM ---------- Previous post was at 05:22 PM ----------
Quick update:
Moments later I rebooted it for yet a third time. Got past the CM progress bar boot screen, and now in some sort of animated screen with the cyanogen logo and an arrow rotating around it (says "cyanogenmod" at the bottom). I am assuming it's doing something so I will leave it and keep and eye on it....
Is that normal? Is this some sort of automated setup point?

So I got it loaded up, but Gapps won't let me sign in with my gmail account. Says "There was a problem communicating with the Google servers. Try again later."
???

Suleeto said:
So I got it loaded up, but Gapps won't let me sign in with my gmail account. Says "There was a problem communicating with the Google servers. Try again later."
???
Click to expand...
Click to collapse
So you said you already have recovery. What recovery do you use?
If yours works, i might as well try it. I was on twrp before this, then i read somewhere it should be on cwm with this rom. So i installed cwm then this is where the problem starts.

I tried a different Gapps and now all is well with that. Now, no FC's that I can see, camera snaps pics. Probably eventually find something but it feels like everything is working presently except for something dock related...
Now, one issue, one concern, one question.
ISSUE: On Overcome, official Samsung dock with HDMI and aux audio worked. I used it on a big stereo. I just set the Tab in the cradle and the sound switched to the cradle audio port (and out to the big stereo). This does not work with the latest CM. Is there something I need to add to restore functionality to the cradle? I hate plugging in my heavy duty audio connector to the top of the Tab while it's in the cradle. Looks terrible and just something to easily get snapped off in a moment of clumsiness. How do I get my cradle to work again?
CONCERN: This thing is.... slower! Yep. I haven't installed a lot... ADW and Pandora and Smart Keyboard. And... Chrome. Which is stupid slow. And as soon as I install Facebook and Facebook Messenger, it's even slower. It was never like this on Overcome. Which is of course Gingerbread, but I figured the main reason to upgrade to Kit Kat was a performance advantage. Did I misunderstand this?
QUESTION: The resolution is a tad bit small. I haven't decided what I think. What is this CM dpi set at to begin with, and what are the safe dpi's and safe way to change them on THIS particular ROM?
---------- Post added at 12:45 PM ---------- Previous post was at 12:08 PM ----------
To be specific, I'm talking about the Samsung Multimedia Dock:
{
"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"
}
And this is the audio port that isn't working. As far as I can tell the HDMI isn't, either:
If there is some sort of additional APK package I need to flash to restore the use of this, please let me know how and where to get it.

vaah said:
So you said you already have recovery. What recovery do you use?
If yours works, i might as well try it. I was on twrp before this, then i read somewhere it should be on cwm with this rom. So i installed cwm then this is where the problem starts.
Click to expand...
Click to collapse
You shouldn't have problems with twrp so far.. Which rom you have current on your tab?
Suleeto said:
I tried a different Gapps and now all is well with that. Now, no FC's that I can see, camera snaps pics. Probably eventually find something but it feels like everything is working presently except for something dock related...
Now, one issue, one concern, one question.
ISSUE: On Overcome, official Samsung dock with HDMI and aux audio worked. I used it on a big stereo. I just set the Tab in the cradle and the sound switched to the cradle audio port (and out to the big stereo). This does not work with the latest CM. Is there something I need to add to restore functionality to the cradle? I hate plugging in my heavy duty audio connector to the top of the Tab while it's in the cradle. Looks terrible and just something to easily get snapped off in a moment of clumsiness. How do I get my cradle to work again?
CONCERN: This thing is.... slower! Yep. I haven't installed a lot... ADW and Pandora and Smart Keyboard. And... Chrome. Which is stupid slow. And as soon as I install Facebook and Facebook Messenger, it's even slower. It was never like this on Overcome. Which is of course Gingerbread, but I figured the main reason to upgrade to Kit Kat was a performance advantage. Did I misunderstand this?
QUESTION: The resolution is a tad bit small. I haven't decided what I think. What is this CM dpi set at to begin with, and what are the safe dpi's and safe way to change them on THIS particular ROM?
---------- Post added at 12:45 PM ---------- Previous post was at 12:08 PM ----------
To be specific, I'm talking about the Samsung Multimedia Dock:
And this is the audio port that isn't working. As far as I can tell the HDMI isn't, either:
If there is some sort of additional APK package I need to flash to restore the use of this, please let me know how and where to get it.
Click to expand...
Click to collapse
The resolution on all CM versions for our Tab is 160dpi, problems with hdmi and aux audio weren't solved for cm 11.0 and aries kernel. For performance problems: have you tried same apps with Gingerbread? What's the expirience with Gingerbread?

storm31 said:
The resolution on all CM versions for our Tab is 160dpi, problems with hdmi and aux audio weren't solved for cm 11.0 and aries kernel. For performance problems: have you tried same apps with Gingerbread? What's the expirience with Gingerbread?
Click to expand...
Click to collapse
Gingerbread on Overcome 7 4.1.0 was fast for apps and I had a lot more running in the background than CM11 does now, so.... make of that what you will. If you read around on Gingerbread ROMs you will quickly find out Overcome is the most complete, stable ROM out there in GB for our p1000 Tabs. Everything works, and works well.
Is there a good app to benchmark device performance? I could use that and then maybe compare to GB on Overcome. Also would be nice if there was a way to see what processes were taxing the processor like you can do in Windoze.
Also, if CM is 160dpi, what was the original dpi for p1000? 120? Overcome GB used whatever was on the original Froyo OEM ROM. What are the safe resolutions and a good app to change them with on CM11?
Ok, so..... if CM11 doesn't work with multimedia dock stuffs.... what about CM Jelly Bean or ICS? Hell, I just wanted Chrome and you can't run Chrome until ICS or higher if I understand right. If this can't be resolved... considering how piss-poor the performance seems to be... I may be reflashing Overcome again. I bought the dock for the outputs (especially audio). Not to look pretty with a tab in it.

storm31 said:
You shouldn't have problems with twrp so far.. Which rom you have current on your tab?
Click to expand...
Click to collapse
I changed my recovery from twrp humberos(if i'm not mistaken) to cwm, then I did full data wipe, that's where the problem start. I had the rom file in the sd card but my cwm doesn't want to mount the sd card. So now i am stuck at boot.
Previously I have CM rom...but i can't remember what version. It had been far too long.
Can you tell me which twrp i should get? I had the files sometime ago but now its nowhere to be found.

vaah said:
I changed my recovery from twrp humberos(if i'm not mistaken) to cwm, then I did full data wipe, that's where the problem start. I had the rom file in the sd card but my cwm doesn't want to mount the sd card. So now i am stuck at boot.
Previously I have CM rom...but i can't remember what version. It had been far too long.
Can you tell me which twrp i should get? I had the files sometime ago but now its nowhere to be found.
Click to expand...
Click to collapse
Have you now a running Tab or it can't boot now?
I have made restock (and cm reflash) for some time ago with these steps:
1. flash stock rom with odin from here: http://www.androidfilehost.com/?fid=9390225151984927194 (thread: http://forum.xda-developers.com/showthread.php?t=1881981 and thanks to sos_sifou)
2. reboot, copy cm-11.0 rom to internal sd then again download mode
3. flash CF root kernel from here: http://forum.xda-developers.com/showthread.php?t=885734 or overcome kernel (http://forum.xda-developers.com/showthread.php?t=1881981)
4. reboot to cwm, flash cm rom, your tab does reboot to cwm again (kernel and cwm will updated), then again rom and gapps
5. mission completed

I can not.boot. All I did was change recovery to cwm. I can get into cwm but somehow it doesnt want to mount my sdcard. Hence I cannot proceed to install rom.
I'll try your method later when I got home.
Sent from my GT-I9300 using Tapatalk

storm31 said:
Have you now a running Tab or it can't boot now?
I have made restock (and cm reflash) for some time ago with these steps:
1. flash stock rom with odin from here: http://www.androidfilehost.com/?fid=9390225151984927194 (thread: http://forum.xda-developers.com/showthread.php?t=1881981 and thanks to sos_sifou)
2. reboot, copy cm-11.0 rom to internal sd then again download mode
3. flash CF root kernel from here: http://forum.xda-developers.com/showthread.php?t=885734 or overcome kernel (http://forum.xda-developers.com/showthread.php?t=1881981)
4. reboot to cwm, flash cm rom, your tab does reboot to cwm again (kernel and cwm will updated), then again rom and gapps
5. mission completed
Click to expand...
Click to collapse
Where do i get the cwm files?

vaah said:
Where do i get the cwm files?
Click to expand...
Click to collapse
Sorry forget about it, i follow hpyour instruction sxactly and it was great now im running cm 11 smoothly so far, just need to get gapps.
Thanks again for the help

vaah said:
Sorry forget about it, i follow hpyour instruction sxactly and it was great now im running cm 11 smoothly so far, just need to get gapps.
Thanks again for the help
Click to expand...
Click to collapse
I am curious what you consider to be "smoothly". I have everything working (well except Multimedia dock), but it's reeeeeally laggy when you try to do anything.

Yes smoothly meaning can open preloaded app by cm11 no problem. But as mentioned before i havent got the gapps. So i haven't downloaded anything from google play.
Oh also the camera does not work. But i wont take picture with this so i am okay. I wanted to revive my sgt so i was happy when it did.
So what makes your tab laggy? Opening anything is laggy?
Sent from my GT-I9300 using Tapatalk

About laggy opening. Have you moved your apps to the sd card? What type of sd card you have? A slow card? Have you set the type of acces protocol for the sd card in the performance settings or tested one of the settings?
Next thing is the internal one. There are 8, 16 and 32 giga byte tab types from samsung. Also the used type which are used from samsung and the speed of them is very different. Samsung plays so as everyone the cheap joker to get the max price of the product.
Next point is how much you have flashed a new rom. Not every ram chip can handle that with the same precice procedure and lifetime. From one point on the chip is damaged around 15%. I have written my doctor based on all that.
So please provide us with some infos.

I've got a small problem, I installed everything like it should, wiped all data e etc, installed the update twice (I was on 2.36, installed, CWM updated sort of, and I had to install again), installed gapps. But there's one small problem...MY touch screen doesn't work.
Model: GT P1000L