Database Users

[HELP] Soft brick ( ? ) with onecosmic's RC2

Hi everybody, i got a nice big problem with Onecosmic's 4.0.3 RC2.
I flash it for the first time some day ago and all works good, yesterday i need to restore as factory by the menu and then..it is witch off!
My smartphone now:
If i plug the device to usb it doesn't do nothing, sometimes the little wheel appears , sometimes no.
If i press the central button appears again.
If touch the back and menu button they switch on.
If i switch on the device appears the logo Galaxy S gt i9000 and the color of picture of boot for 0.01 sec and then switching off, sometimes it reboot endlessly.
And then, i can sent my mobile in Downloading mode (Menu - Vol DWN - PWR) but i can't sent my mobile in the other mode (Menu - Vol UP - PWR).
Please i need help cos i really dont know what i can do
Onestly, is my first big problem with costum mod :s
EDIT: I fix up my phone, i need use Odin for flash stock rom and a .pit file, i think it is a good BUG report for One cosmic's 4.0.3 RC2. I can't post in dev. forum

This is a bootloop not a bug. Way too many people without a clue flashing ICS at the mo.

One moment, i dont like it. I think it is a bug or something becouse i went in setting and the i touch on restore data as factory (oh, i dont know the right translation cos i am italian) and the mobile phone bootlopping.

Its a no wipe rom
So for example you can
wipe
instal rom
use
or
wipe
instal rom
wipe
instal custom kernel
use
and can not
wipe
instal rom
wipe

Im having the same problem as you! I'll keep you posted
Sent from my GT-I9000 using XDA App

qpakao said:
Its a no wipe rom
So for example you can
wipe
instal rom
use
or
wipe
instal rom
wipe
instal custom kernel
use
and can not
wipe
instal rom
wipe
Click to expand...
Click to collapse
Thank you i didnt know that RC2 is a no wipe rom.
josueciz said:
Im having the same problem as you! I'll keep you posted
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Let me know when you have some news I fix up my phone with Odin, flashing a stock rom and original .pit file but, as you can read, i lost ICS. I think i will waiting for a Stable release

This is a good site for troubles
ics.samsung-updates.com/trouble
see:
Phone is in boot loop
can't get to Recovery (I9000)
Put phone in Download mode and use FixRecovery.tar.md5 in Odin as PDA, uncheck auto-reboot option.
After flash reboot to recovery with 3-button-combo and CWM flash proper ICS kernel and reboot
For trouble after follow instructions from HOW TO FLASH section proper for Your device

beardedwonder said:
This is a bootloop not a bug. Way too many people without a clue flashing ICS at the mo.
Click to expand...
Click to collapse
I doubt anyone knows what they are doing until they actually do it.

5nakedoc said:
I doubt anyone knows what they are doing until they actually do it.
Click to expand...
Click to collapse
All you need to do is read the relevant thread or the multiple threads in general and q&a to see a the people that have had the problem and the solution. I've posted the solution at least 5 times already

Reverting back to hc 3.2

Hi,
I wanted to ask if I can revert back to Honeycomb 3.2 if I have Bootloader v3.01?
Thanks.

Fox05 said:
Hi,
I wanted to ask if I can revert back to Honeycomb 3.2 if I have Bootloader v3.01?
Thanks.
Click to expand...
Click to collapse
Short answer...yes...a nand restore is possible...works best with the same recovery image
used for the backup when it was first made...issues I've come across are md5 errors,
missing boot and recovery .img's. I'be done this twice...once with the early leaked ics,
restored just fine.....last nite when I tried with my partners tab we had all sorts of probs,
by the time we realised why it was too l8...thankfully I had an old 3.1 backup we threw on
then OTA'ed up to 3.2 again....same applies going back to ics via nand.
Otherwise its a full downgrade via timmydeans euu or a full package update.zip from vaches thread....
be interested in knowing how u get on, good luck

dibb_nz said:
Short answer...yes...a nand restore is possible...works best with the same recovery image
used for the backup when it was first made...issues I've come across are md5 errors,
missing boot and recovery .img's. I'be done this twice...once with the early leaked ics,
restored just fine.....last nite when I tried with my partners tab we had all sorts of probs,
by the time we realised why it was too l8...thankfully I had an old 3.1 backup we threw on
then OTA'ed up to 3.2 again....same applies going back to ics via nand.
Otherwise its a full downgrade via timmydeans euu or a full package update.zip from vaches thread....
be interested in knowing how u get on, good luck
Click to expand...
Click to collapse
You mean that I can revert back to HC 3.2 by doing a CWM Restore and flashing firmware(s) that vache has provided?

On hc bootie
Yeh restore back
If restore is corrupted then yeh vaches thread

dibb_nz said:
On hc bootie
Yeh restore back
If restore is corrupted then yeh vaches thread
Click to expand...
Click to collapse
But no risk bricking?

Plenty of info here
Post 13 for update.zip method
http://forum.xda-developers.com/showthread.php?t=1626724
Euu downgrade how to
http://forum.xda-developers.com/showthread.php?t=1516012
---------- Post added at 02:18 AM ---------- Previous post was at 02:12 AM ----------
Fox05 said:
But no risk bricking?
Click to expand...
Click to collapse
lol, yeh m8 always a risk but seriously if u can follow instructions u won't have any probs..

But can I download the 3.2/3.1/3.0.1 stock ROM and just flash it in CWM in ICS leak without anything else?

Fox05 said:
But can I download the 3.2/3.1/3.0.1 stock ROM and just flash it in CWM in ICS leak without anything else?
Click to expand...
Click to collapse
yes if you're talking about the stock roms from vaches thread, you need the full rom package - you cant just use an 'update' package as they need a full rom to work properly....
for instance my original HC3.2.1 Stock build is 7.014.15_COM_GEN1
and theres no FULL Rom for 3.2.1, so i have to use the HC 3.2 FULL instead
.....Acer_A500_7.006.03_COM_GEN1.zip
Once flashed, thankfully I recieve the 2 small OTA Updates to get up to 3.2.1 again
Another couple of days the ICS OTA d/l'ed and installed with no probs....
is that clearer or am i making things worse????

dibb_nz said:
yes if you're talking about the stock roms from vaches thread, you need the full rom package - you cant just use an 'update' package as they need a full rom to work properly....
for instance my original HC3.2.1 Stock build is 7.014.15_COM_GEN1
and theres no FULL Rom for 3.2.1, so i have to use the HC 3.2 FULL instead
.....Acer_A500_7.006.03_COM_GEN1.zip
Once flashed, thankfully I recieve the 2 small OTA Updates to get up to 3.2.1 again
Another couple of days the ICS OTA d/l'ed and installed with no probs....
is that clearer or am i making things worse????
Click to expand...
Click to collapse
I'm understanding more but is there a way to find out which ROM was on my tablet out-of-the-box (for the first time I started using my tablet )?

Also vache's thread doesn't have Acer_A500_7.006.01_COM_GEN1 only GEN2. What's the difference between those two? Do you happen to know the build before Acer_A500_7.006.01_COM_GEN1?
Thanks.

Fox05 said:
I'm understanding more but is there a way to find out which ROM was on my tablet out-of-the-box (for the first time I started using my tablet )?
Click to expand...
Click to collapse
.maybe 4.010.24-38 range ??? But I'm guessing ..... depends what region u are...google yr build no. Good way 2 fin out and U may find a full stock rom - then u only need to flash it and wait for the ota
U could go all the way back to 3.0.1 and your tab will update itself to the right ,build.....then
U only need to pick from gen1 or Gen 2.....d/l an euu pkg from the bottom of the post-this will wipe all yr data so be warned.....that's why update.zip is first choice for many d/graders - they get to keep all their crap, lol
but personally, there are issues in Stock ICS, some have and some don't - I dont.- anything i can do to minimize conflicts, then I do it - remember too ICS is a major OS upgrade - not all app are fully optimised for ICS - and Acer are happy to release buggy builds - u can see how those 3 things alone can add up to potential conflicts
I like the idea of being clean, clean , clean and encourage others to stickto build path if ya can to minimize probs further down the line.....
The other thing is, u could just upgrade to ICS full stock Gen 1 as it seems 7.006.01 and 7.006.03 are running on this same build now
Don't ya just love android - u get 2 choose how u want things - then the fun of fixing it when u break it, lol

dibb_nz said:
.maybe 4.010.24-38 range ??? But I'm guessing ..... depends what region u are...google yr build no. Good way 2 fin out and U may find a full stock rom - then u only need to flash it and wait for the ota
U could go all the way back to 3.0.1 and your tab will update itself to the right ,build.....then
U only need to pick from gen1 or Gen 2.....d/l an euu pkg from the bottom of the post-this will wipe all yr data so be warned.....that's why update.zip is first choice for many d/graders - they get to keep all their crap, lol
but personally, there are issues in Stock ICS, some have and some don't - I dont.- anything i can do to minimize conflicts, then I do it - remember too ICS is a major OS upgrade - not all app are fully optimised for ICS - and Acer are happy to release buggy builds - u can see how those 3 things alone can add up to potential conflicts
I like the idea of being clean, clean , clean and encourage others to stickto build path if ya can to minimize probs further down the line.....
The other thing is, u could just upgrade to ICS full stock Gen 1 as it seems 7.006.01 and 7.006.03 are running on this same build now
Don't ya just love android - u get 2 choose how u want things - then the fun of fixing it when u break it, lol
Click to expand...
Click to collapse
Yeah, speaking of problems. I just flashed Acer_A500_4.010.38_COM_GEN1 through CWM (install zip from sdcard) and now my tablet stops at blinking Android logo. Any suggestions what I should flash or anything? And yes, I did a backup of my rom before flashing and I have uid. Also I don't care if my stuff goes I have backed up everything I need.

Fox05 said:
Yeah, speaking of problems. I just flashed Acer_A500_4.010.38_COM_GEN1 through CWM (install zip from sdcard) and now my tablet stops at blinking Android logo. Any suggestions what I should flash or anything? And yes, I did a backup of my rom before flashing and I have uid. Also I don't care if my stuff goes I have backed up everything I need.
Click to expand...
Click to collapse
Oooops.... from vaches site???????
---------- Post added at 12:19 AM ---------- Previous post was at 12:18 AM ----------
Do u still have cwm??

dibb_nz said:
Oooops.... from vaches site???????
---------- Post added at 12:19 AM ---------- Previous post was at 12:18 AM ----------
Do u still have cwm??
Click to expand...
Click to collapse
Yup, from vache's site. I don't think I have CWM because if I insert my external sdcard and press Vol- + Power then it says "Booting custom recovery image" and then Android comes up with gearwheels come up and it starts loading then hangs and finally it restarts and again the blinking Android comes up. When I do it without external sdcard the Android logo shows only an exclamation mark in the middle of Android logo. Any suggestions?

Which one u d/l
Did u extract update.zip and flash
Did it need decrypting first and did u do that
Can try reflash but need answers to these questions first
Don't do anything just yet
Sent from my A500 using XDA Premium HD app

dibb_nz said:
Which one u d/l
Did u extract update.zip and flash
Did it need decrypting first and did u do that
Can try reflash but need answers to these questions first
Don't do anything just yet
Sent from my A500 using XDA Premium HD app
Click to expand...
Click to collapse
I flashed this version: Acer_A500_4.010.38_COM_GEN1
I extracted update.zip and opened it in computer with no problems
I don't think it needed decrypting, but I'm not sure.
Also I did wipes before flashing (data, cache, dalvik and battery).

K m8 try reflash
VolDwn pwr
If that don't work then
Try using hard reset:
1) Turn off your tablet,
2) Rotation lock to your left;
3) Press Vol+ (which is closest to rotation lock) and power on simultaneously
4) As soon as the tablet vibrates you can release the power on button and
you should start to switch rotation lock left and right till you see
Erasing Userdata... Erasing Cache... Vol+ is still pressed;
5) The tablet starts to format
6) Your tablet will be as clean as it can be.

dibb_nz said:
K m8 try reflash
VolDwn pwr
If that don't work then
Try using hard reset:
1) Turn off your tablet,
2) Rotation lock to your left;
3) Press Vol+ (which is closest to rotation lock) and power on simultaneously
4) As soon as the tablet vibrates you can release the power on button and
you should start to switch rotation lock left and right till you see
Erasing Userdata... Erasing Cache... Vol+ is still pressed;
5) The tablet starts to format
6) Your tablet will be as clean as it can be.
Click to expand...
Click to collapse
Ok, will try when I get back. Will reply when I do it.

If hard reset don't work an u still no boot
Have to d/l gen1 EUU at end first post vaches thread
This will take u back to 3.0.1
At present u have stock recovery loaded
What rom u coming from????
It's freakn l8/early here m8, need few zzzzz's
I be back l8r.....good luck

dibb_nz said:
If hard reset don't work an u still no boot
Have to d/l gen1 EUU at end first post vaches thread
This will take u back to 3.0.1
At present u have stock recovery loaded
What rom u coming from????
It's freakn l8/early here m8, need few zzzzz's
I be back l8r.....good luck
Click to expand...
Click to collapse
Ok I come from Taboonay ICS leak ROM.

[Guide] How to root Stock ICS rom without binary count

I'm no longer providing support for this thread due to time constrains with school, thank you for your support and it been nice sharing this method with you all. I may be gone but this method has still been reported as working, but it is possible that the next updates pushed to your phone might break the rooting and this method might not work anymore. But there is no harm in trying, at most you get an error in recovery saying file is invalid.
This method works on the released ICS rom from Germany and I would expect it to work for the rest of the ICS roms due for release..
This method does not increase the binary counter or causes a yellow exclamation mark
Update :
Due to rising numbers of phone being bricked based on rumors and stuff, I strongly suggest NOT trying to use any nandroid backup or restore on this CWM and it is best we keep CWM out of our devices to do major I/O stuff. So far I have never seen anyone bricked their devices on this small rooting/unrooting process but JUST DO NOT MAKE BACKUPS OR RESTORES!
Rooting
Download the Files first and put in your EXTERNAL SD
Reboot to stock recovery. - Shutdown your device completely, press and hold Vol Up + Power button + Home, releasing the power buttons once you see the Samsung GALAXY Note N7000 screen but continue to hold the Vol Up and Power buttons still until you enter recovery
Choose apply update from external storage. - Touch the screen as if you are using the phone to choose the options.
Choose CWM.zip and wait until CWM recovery appear.
( From this point on, the volume rockers and power buttons do not work! It is now a Touch interface like how you use the phone normally )
Choose install zip from external SD
Choose and Install SU-Busybox-Installer.zip
Reboot
You are done and now your device is Rooted
Unroot
Download this File first and put in your EXTERNAL SD
Reboot to recovery.- Shutdown your device completely, press and hold Vol Up + Power button + Home, releasing the power buttons once you see the Samsung GALAXY Note N7000 screen but continue to hold the Vol Up and Power buttons still until you enter recovery
Choose apply update from external storage.- Touch the screen as if you are using the phone to choose the options
Choose CWM.zip and wait until CWM recovery appear.
( From this point on, the volume rockers and power buttons do not work! It is now a Touch interface like how you use the phone normally )
Choose install zip from External SD
Choose and Install SU-Uninstaller-Signed.zip
Reboot
You are done and now your device is Unrooted
Partial Root
Alright i managed to obtain partial root myself and a fix for the Partial root is quite simple. You can install SuperSU by Chainfire and update the root. would fix the Partial root. Once you install this.. DO NOT USE the Superuser app and DO NOT uninstall the SuperUser app. Use SuperSU from now.
SuperSU - https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
MOD Edit: cwm.zip removed from the attachments, read Entropy512's post.

Thanks, but does this install CWM as well? id like to know so that I can go straight to flashing roms from it

are you sure this works ? can anyone confirm ?

nightfox11 said:
are you sure this works ? can anyone confirm ?
Click to expand...
Click to collapse
Works perfectly. Just rooted stock ICS.

Got a brand new Note in the box here.....
Trying to get things straight. Seems like I have two options now for rooted official ICS.
1. This method. Update official ICS Via PC odin (no binary counter, ect) and then follow above instructions.
2. Root stock gb via old method (not sure what that is yet) and then use the mobile odin proceedures w/ new ICS CF kernel?
Is the end result gonna be the same?
Bonus question for noob: what is binary counter and red triangle/exclamation point?
Sent from my SPH-D700 using xda premium

kvanlier said:
Works perfectly. Just rooted stock ICS.
Click to expand...
Click to collapse
thanks man!

Did you just copy this thread?
Oh well. No harm done I guess. Of course it works. It's a method for all android phones. Temporary cwm so you can copy busybox to /system.

Yeah it looks like it, but since it actually works i can't see why that would be a bad thing. But i would give the original author credits in the first post; that is if you copied it.

akenis said:
Got a brand new Note in the box here.....
Trying to get things straight. Seems like I have two options now for rooted official ICS.
1. This method. Update official ICS Via PC odin (no binary counter, ect) and then follow above instructions.
2. Root stock gb via old method (not sure what that is yet) and then use the mobile odin proceedures w/ new ICS CF kernel?
Is the end result gonna be the same?
Bonus question for noob: what is binary counter and red triangle/exclamation point?
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Yes you will end up with the same result if you take either one of the 2 ways to root
Binary counter is a Samsung measurement of how many times you flashed custom firmwares using PC Odin, and the yellow (not red ) triangle is just a logo to further show that you indeed flashed custom firmware
However, the binary counter will not increase (and therefore no yellow triangle will appear) if you:
1. Flash stock firmware with PC Odin
2. Flash using Mobile Odin app by ChainfireXDA
3. Flash using CWM recovery

I got binary counted to 1 with yellow triangle after flashing ics stock from alba.can i use this method to erase counter and triangle?
Sent from my GT-N7000 using Tapatalk 2

So this gives cwm too looks easy
Sent from my GT-N7000 using Tapatalk 2

Drat?
I didn't have GB root because my previous version had root, but I $%*^ screwed
up and let KIES update it to 2.3.6 and I've got too much work to screw around with back flashing wiping etc.
I went ahead and let kies update to ics, now, my question, will this method work, or will I still have to go though all the other to get it to work.
I see it works on stock ICS, but is that after kies, or after you update via pc odin?

victorator said:
Did you just copy this thread?
Oh well. No harm done I guess. Of course it works. It's a method for all android phones. Temporary cwm so you can copy busybox to /system.
Click to expand...
Click to collapse
LordManhattan said:
Yeah it looks like it, but since it actually works i can't see why that would be a bad thing. But i would give the original author credits in the first post; that is if you copied it.
Click to expand...
Click to collapse
Not many ways to have a drastic difference from the method but hey it works well.
p51d007 said:
I didn't have GB root because my previous version had root, but I $%*^ screwed
up and let KIES update it to 2.3.6 and I've got too much work to screw around with back flashing wiping etc.
I went ahead and let kies update to ics, now, my question, will this method work, or will I still have to go though all the other to get it to work.
I see it works on stock ICS, but is that after kies, or after you update via pc odin?
Click to expand...
Click to collapse
This method works as long as you are on Stock ICS.. Can't really go wrong really.

so i did and have root and root works..
now my question is....
given that we get temp CWM..can i use the temp CWM to flash radios?
AND so if i want to flash LP6 radio via CWM will the steps be.
load Stock recovery
flash CWM.zip in stock recovery
load CWM
flash lp6 radio
will that work?
=============================
After no one answered i took the plunge...
Yes
so can confirm that the above procedure will work
PS: Am amazed how this is not in the sticky
Can anyone tell me any issues with using the CWM offered in this thread??? as in any issues with flashing other roms?? etc??
I fail to see?
The only issue is that CWM is not permanent but u can easily re-enable it by flashing it again...
again..dont understand why ppl are not paying attention to this thread as is great!

how come i only got partial root? i cannot paste into system

deathst said:
This method works as long as you are on Stock ICS.. Can't really go wrong really.
Click to expand...
Click to collapse
You are right, finally got my root back ICS, after the 2.3.6 update, been a while, now I have to remember how to use the freeze program, LBE security etc...all over again LOL. THANKS!

elijahtan said:
how come i only got partial root? i cannot paste into system
Click to expand...
Click to collapse
Try rooting again.. Are you sure your file manager app was given permission? Cause this thing is practically fool proof.
nandihno said:
so i did and have root and root works..
now my question is....
given that we get temp CWM..can i use the temp CWM to flash radios?
AND so if i want to flash LP6 radio via CWM will the steps be.
load Stock recovery
flash CWM.zip in stock recovery
load CWM
flash lp6 radio
will that work?
=============================
After no one answered i took the plunge...
Yes
so can confirm that the above procedure will work
PS: Am amazed how this is not in the sticky
Can anyone tell me any issues with using the CWM offered in this thread??? as in any issues with flashing other roms?? etc??
I fail to see?
The only issue is that CWM is not permanent but u can easily re-enable it by flashing it again...
again..dont understand why ppl are not paying attention to this thread as is great!
Click to expand...
Click to collapse
Glad it works for you Yes I wonder why is not many people taking notice.. :S

...and i thought I was screwed
THANKS MAN. works perfect. much faster than having to redownload the odex vrs

Worked perfectly thanks !
Sent from my HTC One X using xda premium

hmmm.... didn't work for me. CWM looks for update.zip so i renamed it as such. installed and rebooted to CWMR, no touch menu. same old blue colored menu. install su-binary, stuck at unmounting /system = not rooted.

Need help changing ROM Criskelo 5 to liquid smooth 3.2

Hi Guys,
I am trying to change my ROM from Criskelo 5.1 (has speedmod kernel but dont think that should make a difference) to LiquidSmooth 3.2. Usually this is a pretty straight froward process but for some reason I just cant get past CWM. Here is what I've done so far.
Reboot into recovery.
Flash AbyssNote 3.2 (redtouch) and reboot into AybssNote.
Wipe everyting (inlcuding dalvik and battery)
Flash LiquidSmooth 3.2
On doing this the phone restarts - as is expected - but then it just reboots in CWM. I've tried various permutations of this (even tried wipes from CWM before going into Abyss) in the hope that it might work but nothing seems to work. Before this I tried to go Criskelo 5 to 8 and got stuck on boot screen.
Thanks God for nandroid or this would have become an extremely frustrating experience. Any ideas ?
EDIT: Used AbyssNote 4.2 and not 3.2 .... sorry about that

tariqsaleem said:
Hi Guys,
I am trying to change my ROM from Criskelo 5.1 (has speedmod kernel but dont think that should make a difference) to LiquidSmooth 3.2. Usually this is a pretty straight froward process but for some reason I just cant get past CWM. Here is what I've done so far.
Reboot into recovery.
Flash AbyssNote 3.2 (redtouch) and reboot into AybssNote.
Wipe everyting (inlcuding dalvik and battery)
Flash LiquidSmooth 3.2
On doing this the phone restarts - as is expected - but then it just reboots in CWM. I've tried various permutations of this (even tried wipes from CWM before going into Abyss) in the hope that it might work but nothing seems to work. Before this I tried to go Criskelo 5 to 8 and got stuck on boot screen.
Thanks God for nandroid or this would have become an extremely frustrating experience. Any ideas ?
Click to expand...
Click to collapse
Bump .... anyone ?

Get a stock gb rom and flash via pc odin.
Sent from my GT-N7000 using xda app-developers app

tariqsaleem said:
Bump .... anyone ?
Click to expand...
Click to collapse
Have you try other ROM besides LiquidSmooth? Since it stuck in CWM, I suspect the installation script for LiquidSmooth is not compatible with Abyss 3.2 CWM.

praetorius said:
Get a stock gb rom and flash via pc odin.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
I was hoping you wouldn't say that .... I have a really slow net connection at the moment and don't have any GB stock roms saved (next time I'll think twice before I delete stuff ). Is there any other way I can do this or is this the only option I have ?

lenrek said:
Have you try other ROM besides LiquidSmooth? Since it stuck in CWM, I suspect the installation script for LiquidSmooth is not compatible with Abyss 3.2 CWM.
Click to expand...
Click to collapse
I tried to update to Criskelo v8 and in that case I got stuck on the boot screen. Had to do a hard reset and get back into recovery manually.
Sorry about the confusion, I actually used Abyss 4.2 (which I got from the Liquid Smooth thread) so I don't think there should be any compatibility issues.

Go back to abyss42 and factory reset from within abyss42 (red menu). Also do cache and dalvik wipe.
Reinstall your custom rom.
And since you have a slow connection, there is a chance your files are corrupt.
Sent from my GT-N7000 using xda app-developers app

Do a unzip -t <zipfile> to verify the file is not corrupted. As above post stated, it maybe a corrupted zip file.

praetorius said:
Go back to abyss42 and factory reset from within abyss42 (red menu). Also do cache and dalvik wipe.
Reinstall your custom rom.
And since you have a slow connection, there is a chance your files are corrupt.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Did all of that i.e Factory reset from within Abyss42, clear cache and dalvik wipe.
I guess I'll try downloading again but why I doubt that would fix anything since this is the 2nd ROM I've had the same issue with. Well not exactly same, in the case of Criskelo 8 it gets stuck on boot screen where as with liquid smooth 3.2 it keeps going back into CWM . Still worth a try though. will update tonight once I get to download again.
Anyway of verifying whether my files are corrupt or not ?

lenrek said:
Do a unzip -t <zipfile> to verify the file is not corrupted. As above post stated, it maybe a corrupted zip file.
Click to expand...
Click to collapse
Thanks...I'll give that a go later today. Currently the rom in on my phone. Can I do something similar via the terminal on my mobile ?

tariqsaleem said:
Thanks...I'll give that a go later today. Currently the rom in on my phone. Can I do something similar via the terminal on my mobile ?
Click to expand...
Click to collapse
Is a zip file, so just get one of those app that can open zip/compressed file from the Google Play. I use AndroZip, FYI. I believe there are more choices in Google Play.

lenrek said:
Is a zip file, so just get one of those app that can open zip/compressed file from the Google Play. I use AndroZip, FYI. I believe there are more choices in Google Play.
Click to expand...
Click to collapse
Tried to open it with ES Zip Viewer and it opens up without any issues, so does that mean that the file is not corrupted ?

tariqsaleem said:
Anyway of verifying whether my files are corrupt or not ?
Click to expand...
Click to collapse
check for MD5 checksum

try abyss 3.9
my phone stuck on bootanimation endlessly with Liquid black 3.2, i was using abysss 4.2 with red interface, i moved on to asylum

rraaka said:
try abyss 3.9
my phone stuck on bootanimation endlessly with Liquid black 3.2, i was using abysss 4.2 with red interface, i moved on to asylum
Click to expand...
Click to collapse
Tried flashing with abyss 3.9 but still have the same issue. The phone reboots into CWM

For the benefit of others....went back to stock Samsung GB image and flashed paranoid android from there and it worked
Sent from my GT-N7000 using xda app-developers app

Does JB or ICS improve touch sensitivity

My number 1 complaint with the 10.1 is that i get finger ache trying to use the tab for an extended period
I just had a play with an IPAD and i'm SOOOO jealous how little you have to touch the screen to make it move etc
will a software update to JB or ICS improve the touch sensitivity of the tab?
Thanks

m.r.davies said:
My number 1 complaint with the 10.1 is that i get finger ache trying to use the tab for an extended period
I just had a play with an IPAD and i'm SOOOO jealous how little you have to touch the screen to make it move etc
will a software update to JB or ICS improve the touch sensitivity of the tab?
Thanks
Click to expand...
Click to collapse
Yeah that's also an issue for me it's responsiveness for touch are not that great...
Hope they fixed this with project butter since it guess where are you gonna touch the screen and react milliseconds before the touch happens
Sent from my GT-N7000 using xda premium

I agree, hopefully Project Butter on JB will solve it.
If you are rooted or know how to, try this.

ICS sensitivity and responsiveness is night and day over HC..
But now after running JB, it is night and day over ICS

force1stiptopped said:
ICS sensitivity and responsiveness is night and day over HC..
But now after running JB, it is night and day over ICS
Click to expand...
Click to collapse
I take it JB is better than ics then!?
Which rom you using? Stable enough to use as an everyday OS?

m.r.davies said:
I take it JB is better than ics then!?
Which rom you using? Stable enough to use as an everyday OS?
Click to expand...
Click to collapse
It really is like night and day and my WiFi tab is as smooth as my Galaxy note check this ROM out if rooted.
http://forum.xda-developers.com/showthread.php?t=1765254#

mobileguynz said:
It really is like night and day and my WiFi tab is as smooth as my Galaxy note check this ROM out if rooted.
http://forum.xda-developers.com/showthread.php?t=1765254#
Click to expand...
Click to collapse
Thanks man
I'm not currently rooted, and have never done such things
I dare not ask too many questions in fear of being flammed, i've read a lot and i'm a bit overwhelmed.
to use this rom, shall i root my device using the tutorial here:
http://forum.xda-developers.com/showthread.php?t=1239185
and do i need to bother with clockwork thing? or just follow the above tutorial?
Cheers

m.r.davies said:
Thanks man
I'm not currently rooted, and have never done such things
I dare not ask too many questions in fear of being flammed, i've read a lot and i'm a bit overwhelmed.
to use this rom, shall i root my device using the tutorial here:
http://forum.xda-developers.com/showthread.php?t=1239185
and do i need to bother with clockwork thing? or just follow the above tutorial?
Cheers
Click to expand...
Click to collapse
Yeah I know what you mean but the best advice is read everything and you need to be prepared for issues and dig under the bonnet so to speak.
This is off topic so don't ask anymore about root here
yes cmw is required which is recovery and Backup everything.
Lots of posts scrolling screens and I used the recovery from here using Odin to flash. http://droidbasement.com/db-blog/
guides here http://forum.xda-developers.com/showthread.php?t=1462961

Thanks man
So back on topic, I really want the smoothness! and
I've read that build is alpha, but are you happy it's stable enough?
smooth scrolling will be amazing, but a tab that keeps crashing is a lot more annoying and I will wait a while otherwise
Otherwise i'll go for the root, and then install that app mentioned above
Cheers for all your advice guys

m.r.davies said:
Thanks man
So back on topic, I really want the smoothness! and
I've read that build is alpha, but are you happy it's stable enough?
smooth scrolling will be amazing, but a tab that keeps crashing is a lot more annoying and I will wait a while otherwise
Otherwise i'll go for the root, and then install that app mentioned above
Cheers for all your advice guys
Click to expand...
Click to collapse
Latest build is up and mine is WiFi only this is suitable for daily use. JB mixed in with CM 10 is really smooth and once Samsung puts out the drivers for camera 3G etc this ROM really does make the tab buttery smooth. Things are so much more fluid. JB ROM has given my tablet and experience as good as the iPad 2. There are things to fix and alpha meet early days but the dev has worked really hard on this and to a lot of us forgotten by Samsung tab owners a huge WOW.

Great, I want to try this
Can I ask, does CM mean clockwork mod or cyanogen mod?

m.r.davies said:
Great, I want to try this
Can I ask, does CM mean clockwork mod or cyanogen mod?
Click to expand...
Click to collapse
Sorry I typed wrong I meant ClockworkMod Recovery
Cyanogen is CM 9 or CM10 whole ROM
See. http://forum.xda-developers.com/wiki/ClockworkMod_Recovery
I use http://droidbasement.com/db-blog/

m.r.davies said:
Great, I want to try this
Can I ask, does CM mean clockwork mod or cyanogen mod?
Click to expand...
Click to collapse
Usually, clockwork mod is abbreviated by CWM and cyanogen mod is abbreviated by CM
Sent from my GT-P7510 using xda app-developers app

1. Download Odin from available threads
2. Download a recovery for Odin flashing (like cwm), be sure to get the correct one for your tab (if you have WiFi only its 7510 or p4wifi, for 3g its p4 or 7500)
2.a you can start downloading the ROM you want right now as well, so you don't have to wait later on.
2.b download appropriate gapps (for ICS or jb)
3. In Odin make sure nothing besides the auto reboot and the thing the right if it is checked
4. Put your tab in download mode: turn it off. Turn it on while holding volume down, you'll get a screen with two icons on it. The right one should already be selected so press volume up to select, if not then press volume down to switch then volume up to check. The tab will tell you to press volume up to continue, do it. Congrats, now you are in download mode.
5. Connect your tab to your computer. One iPod the empty squares above should turn yellow and something written in it*
6. Click PDA for file selection. Select the recovery.tar.md5 you downloaded.
7. Press start, when finished your tab should reboot.
8. Get the downloaded ROM on the tab, however you wish.
8.a backup everything you want backed up. Photos mucpsic and other stuff won't be deleted if its on the "sdcard"
9. Turn off tab. Turn on again while holding volume down.
10. Enter recovery by pressing volume down then using volume up to select (you want the left icon)
11. Navigation in CWM: volume keys=up/down, power button=confirms selection
You want to wipe data, wipe cache and then to into advanced and wipe dalvik cache, return to the top
14. Select apply update, select choose zip, find ROM you downloaded, confirm.
14.b sometimes it might not be best to flash gapps at the same time as ROM, so it may be better to reboot phone then when started reboot again into recovery then flash gapps like you flashed the ROM.
For future ROMs only 8+ is needed, sometimes 8a and wiping data in 11 is not needed, this is usually for small updates of the same ROM (like cm night lies) however you can always try not to wipe data then if you have problems reboot into recovery and do the three wipes.
* if nothing turns yellow make sure you have drivers. You can install lies to get drivers(but make sure no lies process is running when you start odi ) or search for drivers and download them

The touch sensitivity is much better but still has its moments but that could be the ROM its self