I know this forum is infested with many such warnings and/or desperate shouts for help. However, after having a quick look at the brick cases, all are having one thing in common- they tried to go to GB ROM via PC odin.
So guys, especially the novices out there, if you do not know what you are doing, may be you should sit tight until things get sorted out. I am telling you because I'd been there done that, so if you are already on LPY, you would rather stay there than try some odd thing and get your phone bricked.
No, this is not fear mongering post. I am more than happy to be proven otherwise. I am just posting my inference after observing for quite sometime.
{
"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"
}
Sent from my GT-N7000 using Tapatalk 2
In the past few days since LPY as come out I went back & forth from LPY to GB via Mobile Odin several times, also after searching the thread I found that most bricks are Cm9 + LPY kernel related
I think that Odin is pretty safe to use but that is just my opinion and if one is not sure then better not try.
P.s
Still can't decide which is better modified GB or stock ics (LPY)
Sent from my GT-N7000 using xda premium
anilisanil said:
I know this forum is infested with many such warnings and/or desperate shouts for help. However, after having a quick look at the brick cases, all are having one thing in common- they tried to go to GB ROM via PC odin.
So guys, especially the novices out there, if you do not know what you are doing, may be you should sit tight until things get sorted out. I am telling you because I'd been there done that, so if you are already on LPY, you would rather stay there than try some odd thing and get your phone bricked.
No, this is not fear mongering post. I am more than happy to be proven otherwise. I am just posting my inference after observing for quite sometime.
Click to expand...
Click to collapse
well i will tell you i went from ics to gb via pc odin without any issues
installed ics via pc odin due to mobile odin not flashing correctly, didnt have root, flashed kj4 (gb rom) and didnt have any issues
Can anyone confirm that in his case, flashing stock LPY to stock GB with PC Odin caused a problem for him?
This migration from LPY to GB, should we use 1 file ROMs from samfirmware.com, or we must use 3 files ROMs? Also do we need a pit file for that?
These three cases of superbricks all have one thing in common, check-
http://forum.xda-developers.com/showthread.php?t=1653290
http://forum.xda-developers.com/showthread.php?t=1649982
http://forum.xda-developers.com/showthread.php?t=1650209
Richy99 said:
well i will tell you i went from ics to gb via pc odin without any issues
installed ics via pc odin due to mobile odin not flashing correctly, didnt have root, flashed kj4 (gb rom) and didnt have any issues
Click to expand...
Click to collapse
well, this shows that results may vary even when using the same method. I did it the same way but used KJ1 instead of KJ4 and, looking back at the symptoms, bricked my device during the first GB reflash.
Ce said:
well, this shows that results may vary even when using the same method. I did it the same way but used KJ1 instead of KJ4 and, looking back at the symptoms, bricked my device during the first GB reflash.
Click to expand...
Click to collapse
did you use the stock or rooted ics?
Richy99 said:
did you use the stock or rooted ics?
Click to expand...
Click to collapse
From a rooted GB to a stock (unrooted) ICS and tried to get back to a stock GB.
Ce said:
From a rooted GB to a stock (unrooted) ICS and tried to get back to a stock GB.
Click to expand...
Click to collapse
is that a wipe rom? its possible its the wiping that kills the device
Richy99 said:
is that a wipe rom? its possible its the wiping that kills the device
Click to expand...
Click to collapse
Sorry, I also used a KJ4 rom (had to look at sammobile to check) and Yes, that was a wipe rom.
Ce said:
Sorry, I also used a KJ4 rom (had to look at sammobile to check) and Yes, that was a wipe rom.
Click to expand...
Click to collapse
thats probably the difference then, the wipe is what seems to be causing the bricks, the one i used was not a wipe rom
edit : just checked and it was kj1 not kj4 i flashed, the version weas the one fromthe chainfire root thread
try AMORA Filemanager.. flash via recovery and you have a file manager,,, take a look on your partitions
just my idea, you got nothing to lose
thelucius said:
Can anyone confirm that in his case, flashing stock LPY to stock GB with PC Odin caused a problem for him?
This migration from LPY to GB, should we use 1 file ROMs from samfirmware.com, or we must use 3 files ROMs? Also do we need a pit file for that?
Click to expand...
Click to collapse
I am the "lucky" member of superbrick team. Hopefully Samsung will not ask for paying for the MoBo replacement. Could any1 suggest me what to put as reason for Samsung to claim warranty successfully? Thanks
Tell them you were upgrading your Note with Kies and a problem occurs but you don't know what. If they want more details, you can say your computer freezed or reboot while upgrading.
(Kies has been proved so unreliable in the past that it should do the trick)
Sorry if my question sound dumb, or I don't say the correct verbiage.
I have the GT-N7000 with the official Samsung ginger bread 2.36 version, and I installed the German Samsung release ICS leak using the Odin software via PC and it worked just fine. The phone has been working fine for few days now without any issues I can notice.
What should I do after knowing about this bug issue in the ICS leak ? Just let the phone be or go back GB 2.36 ? Any input appreciated.
have now flashed from stock ics to stock kj1 a few times have then rooted kj1 and upgraded to either lc1 or ics etc so far so good am on stock german ics with temp root if i need it
mackey77 said:
Sorry if my question sound dumb, or I don't say the correct verbiage.
I have the GT-N7000 with the official Samsung ginger bread 2.36 version, and I installed the German Samsung release ICS leak using the Odin software via PC and it worked just fine. The phone has been working fine for few days now without any issues I can notice.
What should I do after knowing about this bug issue in the ICS leak ? Just let the phone be or go back GB 2.36 ? Any input appreciated.
Click to expand...
Click to collapse
you dont have any issue. you are stock set up.
Thanks for your response, feel a bit relived.
Sine. said:
Tell them you were upgrading your Note with Kies and a problem occurs but you don't know what. If they want more details, you can say your computer freezed or reboot while upgrading.
(Kies has been proved so unreliable in the past that it should do the trick)
Click to expand...
Click to collapse
Thanks but what if they say: "What were you upgrading your Note to?" I mean, what was the reason to try upgrade the Note? And what if they say ...there was not an upgrade for your Note since the time you had bought it. Thanks
Related
Hi all,
Sorry to ask this but with all the various firmware versions I am confused about which is a good Rooting program for the Official JPO Froyo release. Can someone point me in the right direction?
Thank you in advance
search is your friend.
Sent from my GT-I9000 using XDA App
CF root using Odin
Sent from my GT-I9000 using XDA App
Actually I have the same question as was confused about which method to use as well. My phone is JPO/JPP/JP3. I have searched but all the root methods I found were for earlier versions of froyo and users reported problems.
kiwijunglist said:
Actually I have the same question as was confused about which method to use as well. My phone is JPO/JPP/JP3. I have searched but all the root methods I found were for earlier versions of froyo and users reported problems.
Click to expand...
Click to collapse
Thank you glad to hear I am not alone
andrej.marinic:
Search is what started the confusion its hard to read all the threads to find out the end result.
I would also like to know if there is one that you can apply via the recovery method (like copying update.zip to sdcard) so I do not have to use a program like ODIN.
Thank you again in advance,
I did it using the CF method: http://forum.xda-developers.com/showthread.php?t=788108
its very easy and pain free
padlad said:
I did it using the CF method: http://forum.xda-developers.com/showthread.php?t=788108
its very easy and pain free
Click to expand...
Click to collapse
I also saw this but some people have had issues so I am bit reluctant to try it
cf-root works like a charm on JPA. no issues for me.
Sent from my GT-I9000 using XDA App
Cf root but make sure your 3 button download mode works as a failsafe
Sent from my GT-I9000 using XDA App
cenonmin said:
I also saw this but some people have had issues so I am bit reluctant to try it
Click to expand...
Click to collapse
Just make sure you use CF-Root-XX_XEU_JPO-v1.2-Busybox-1.17.1.zip
I have the official Germany Froyo. I will wait for the 3 Button fix and OCLF fix for the official Froyo.
I did tested other things and it made my phone slower and quickly out of memory. So I reset ( all data gone - but I did Backup my apps ) everything and it went normal
Just better wait until they find a solution for the official Froyo and not the unofficial Froyo.
I am using CF-Root-XX_XEU_JPO-v1.2-Busybox-1.17.1.zip flashed via Odin. Took 30 seconds and now I can use stuff like Titanium Backup and other useful apps. All on the official JPO through Kies.
silverstorm said:
I am using CF-Root-XX_XEU_JPO-v1.2-Busybox-1.17.1.zip flashed via Odin. Took 30 seconds and now I can use stuff like Titanium Backup and other useful apps. All on the official JPO through Kies.
Click to expand...
Click to collapse
Did you have any issues with 'un-rooting'??
EDITED:
What I am saying here is Kies totally bricked my phone and as such I won't use it again but instead Odin.
You however mention you are still using Kies. Did you have any issues in un-rooting when using Kies for the next flash... or have you not tried this yet?
Beards said:
Did you have any issues with 'un-rooting'??
Click to expand...
Click to collapse
Erm, not had a reason to un-root yet so haven't tried. But since this is flashed as a Kernel I presume I would have to flash another non-rooted Kernel through Odin in order to un-root. but don't know why I'd want to. If I wanted to upgrade to a newer version of Froyo, the root shouldn't affect it as far as I'm aware, it's only LagFixes really that are required to be disabled.
But to be on the safe side, you could re-flash a stock non-rooted JPO firmware from samfirmware.com through ODIN prior to going ahead with a Kies update, but this will mean you'll lose your data. I always go through this route anyway and then use Titanium backup to restore. (for which you'll require root!)
silverstorm said:
Erm, not had a reason to un-root yet so haven't tried. But since this is flashed as a Kernel I presume I would have to flash another non-rooted Kernel through Odin in order to un-root, but don't know why I'd want to. If I wanted to upgrade to a newer version of Froyo, the root shouldn't affect it as far as I'm aware, it's only LagFixes really that are required to be disabled.
Click to expand...
Click to collapse
Really... I could have sworn you have to take off any root prior to the next flash.
Beards said:
Really... I could have sworn you have to take off any root prior to the next flash.
Click to expand...
Click to collapse
Just lag fixes need to be disabled in order to flash via kies, the last couple of flashes i did had root already on, flashed no problem.
padlad said:
Just lag fixes need to be disabled in order to flash via kies, the last couple of flashes i did had root already on, flashed no problem.
Click to expand...
Click to collapse
Well what do you know...... Something new learned today.
Thanks Guys.
{
"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"
}
To root froyo use simpleoneclick.
Sent from my GT-I9000 using XDA App
tt4079 said:
To root froyo use simpleoneclick.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Links please.
http://forum.xda-developers.com/showthread.php?t=833953
Breaking News: New One Click Root app from RyanZA, the maker of the famous OCLF.
Hello dear friends ,
I am new to this forum and please excuse me if this is a repost. i want to root my device and install the best and stable ICS CFW. i am not knowing which one to install . can anyone advise me on this ? explaining me different features about each CFW . the pros and cons of each . i am using GT - N7000 galaxy note on gingerbread 2.3.6 and i never rooted it or did anything with it till now .i want to use S MEMO with CFW . and i heard that some features doesnt work in some firmwares . i want to have all features with a best and stable CFW. can any one guide me on this ? and give me a tutorial how to do this ? any help would be greatly appreciated.
my kernel version is 2.6.35.7-N7000XXLA1-CL868264 and
Build number : GINGERBREAD.XXLA1
i also tried to install the official ICS from samsung kies but i am getting an error that this device does not support upgrading with kies . i want to have ICS on my device . be it an official or CFW. can anyone tell me if there is any manual way to flash my device with official ICS firmware ?
please kindly help me . thanks a lot . i am waiting for your replies and help .
{
"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"
}
prataptetali said:
Hello dear friends ,
I am new to this forum and please excuse me if this is a repost. i want to root my device and install the best and stable ICS CFW. i am not knowing which one to install . can anyone advise me on this ? explaining me different features about each CFW . the pros and cons of each . i am using GT - N7000 galaxy note on gingerbread 2.3.6 and i never rooted it or did anything with it till now .i want to use S MEMO with CFW . and i heard that some features doesnt work in some firmwares . i want to have all features with a best and stable CFW. can any one guide me on this ? and give me a tutorial how to do this ? any help would be greatly appreciated.
my kernel version is 2.6.35.7-N7000XXLA1-CL868264 and
Build number : GINGERBREAD.XXLA1
i also tried to install the official ICS from samsung kies but i am getting an error that this device does not support upgrading with kies . i want to have ICS on my device . be it an official or CFW. can anyone tell me if there is any manual way to flash my device with official ICS firmware ?
please kindly help me . thanks a lot . i am waiting for your replies and help .
View attachment 1203298
Click to expand...
Click to collapse
It is very long story to give you guide and detail explanation thru post here.
What you can do now is go dr.ketan post and read there carefully. Download the neccessary tools and ics custom rom as well.
But dont rush to flash anything, come back to us if you are not really understand what should do at next step.
Im sure you aware enough of super brickbug issue right? So..just read at try to understand and ask, our xda member will try to assist you as much as we can.
Good luck.
Sent from my GT-N7000 using xda premium
lee yun khong said:
It is very long story to give you guide and detail explanation thru post here.
What you can do now is go dr.ketan post and read there carefully. Download the neccessary tools and ics custom rom as well.
But dont rush to flash anything, come back to us if you are not really understand what should do at next step.
Im sure you aware enough of super brickbug issue right? So..just read at try to understand and ask, our xda member will try to assist you as much as we can.
Good luck.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Thankq sir for prompt reply.and which cfw do you advise me..can you explain why my device is not upgrading officially by kies
prataptetali said:
Thankq sir for prompt reply.and which cfw do you advise me..can you explain why my device is not upgrading officially by kies
Click to expand...
Click to collapse
Samsung kies not going to upgrade due to so many reason. My fren g.note also faced the same prob before. He failed to upgrade thru kies as well. But after 2days tried, kies suddenly appear ugrade available. My another fren using s3 also same, mrn his phone detected update about 93mb available while at office, but he decide update thru kies at home. But nothing happened and kies appeared no update at all.Even he use ota thru his s3 also no more update available. But surprisingly he did manage update his s3 thru kies at second day. Weird right?..ha..
For 2.3.6 custom firmware litening rom will be my best choice.
For ics 4.0.4 custom rom, classic rom will be my choice.
Sent from my GT-N7000 using xda premium
lee yun khong said:
Samsung kies not going to upgrade due to so many reason. My fren g.note also faced the same prob before. He failed to upgrade thru kies as well. But after 2days tried, kies suddenly appear ugrade available. My another fren using s3 also same, mrn his phone detected update about 93mb available while at office, but he decide update thru kies at home. But nothing happened and kies appeared no update at all.Even he use ota thru his s3 also no more update available. But surprisingly he did manage update his s3 thru kies at second day. Weird right?..ha..
For 2.3.6 custom firmware litening rom will be my best choice.
For ics 4.0.4 custom rom, classic rom will be my choice.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Ohhh..i got it..i will try from various laptops ofnmy.friedns..is classic rom for ics stable.and does it have all features and can you please provide me link for classic rom with guide thanks a lot bro
prataptetali said:
Ohhh..i got it..i will try from various laptops ofnmy.friedns..is classic rom for ics stable.and does it have all features and can you please provide me link for classic rom with guide thanks a lot bro
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1765307
About the installation guide you need to give full detail of your existing rom using and root status.
Sent from my GT-N7000 using xda premium
Hello Everyone,
So today i wanted to go to 4.0.3 ICS via ODIN 1.83 / 1.85.
Both won't work, and they keep hanging on '' Factoryfs.img " The phone won't turn, because it says i need to do a firmware recovery.
Im from the Netherlands and use this:
http://forum.xda-developers.com/showthread.php?t=1424997
Hopefully someone can solve my problem.
* I did NOT check Re-Partition *
Hoolz14 said:
Hello Everyone,
So today i wanted to go to 4.0.3 ICS via ODIN 1.83 / 1.85.
Both won't work, and they keep hanging on '' Factoryfs.img " The phone won't turn, because it says i need to do a firmware recovery.
Im from the Netherlands and use this:
http://forum.xda-developers.com/showthread.php?t=1424997
Hopefully someone can solve my problem.
* I did NOT check Re-Partition *
Click to expand...
Click to collapse
{
"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"
}
Hoolz14 said:
Hello Everyone,
So today i wanted to go to 4.0.3 ICS via ODIN 1.83 / 1.85.
Both won't work, and they keep hanging on '' Factoryfs.img " The phone won't turn, because it says i need to do a firmware recovery.
Im from the Netherlands and use this:
http://forum.xda-developers.com/showthread.php?t=1424997
Hopefully someone can solve my problem.
* I did NOT check Re-Partition *
Click to expand...
Click to collapse
Please say you didn't do a factory reset....
Hoolz14 said:
Hello Everyone,
So today i wanted to go to 4.0.3 ICS via ODIN 1.83 / 1.85.
Both won't work, and they keep hanging on '' Factoryfs.img " The phone won't turn, because it says i need to do a firmware recovery.
Im from the Netherlands and use this:
http://forum.xda-developers.com/showthread.php?t=1424997
Hopefully someone can solve my problem.
* I did NOT check Re-Partition *
Click to expand...
Click to collapse
You are super bricked go claim your warranty..
Sent from my GT-N7000 using xda premium
was your phone in working order before yo decided to update? what ROM were you on? did you wipe on a dangerous kernel?
Did you EVER do a wipe on your phone? If yes, did you check emmc integrity afterwards?
I Believe i was on a 2.3.6 ROM, but can't really remember because the phone was laying around and i decided to use it again.
I know there's still a backup on the external SD card from it that i made with CWM, and here it all did go wrong.
I wanted to recover the backup, and the phone rebooted and hanged on '' Galaxy note n7000 screen ".
So, what is the best step for now what i can do ?
msedek said:
You are super bricked go claim your warranty..
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Sent from my GT-N7000 using xda premium
So if i am superbricked, how can i see my flashcounter?
Because otherwise i cannot claim my warranty, and what can i do about this than? i suppose there is a manner to get it up and running again ?
Not sure, but I think you have to flash a Stock ICS kernal before you flash any ICS Rom for the first time.
dohab said:
Not sure, but I think you have to flash a Stock ICS kernal before you flash any ICS Rom for the first time.
There are a lot of good kernals out there.
Click to expand...
Click to collapse
Where could i find those? i'm downloading gingerbread now....
Hoolz14 said:
So if i am superbricked, how can i see my flashcounter?
Because otherwise i cannot claim my warranty, and what can i do about this than? i suppose there is a manner to get it up and running again ?
Click to expand...
Click to collapse
Well, you should know what your flash counter was before. Flashing a stock ROM did not increase it.
Also, if you are really super-bricked Samsung will not be able (or willing) to read it.
Hoolz14 said:
Where could i find those? i'm downloading gingerbread now....
Click to expand...
Click to collapse
you can find them in the development original forum :
http://forum.xda-developers.com/forumdisplay.php?f=1700
for example, check this out :
http://forum.xda-developers.com/showthread.php?t=1371007
or
http://forum.xda-developers.com/showthread.php?t=1673072
but if you are downloading GB, then you have to use a GB kernel instead.
you can check dr.ketan thread for a really Major information:
http://forum.xda-developers.com/showthread.php?t=1424997
I lost my mind in that thread once, but, good luck to you. :good:
Randomwalker said:
Well, you should know what your flash counter was before. Flashing a stock ROM did not increase it.
Also, if you are really super-bricked Samsung will not be able (or willing) to read it.
Click to expand...
Click to collapse
Alright
Monday to vodafone then ...
Put your phone in Odin mode there you can see if you have binary counter diferent from 0 if it's not 0 then get a jig to reset it
Sent from my GT-N7000 using xda premium
---------- Post added at 06:54 PM ---------- Previous post was at 06:52 PM ----------
Randomwalker said:
Well, you should know what your flash counter was before. Flashing a stock ROM did not increase it.
Also, if you are really super-bricked Samsung will not be able (or willing) to read it.
Click to expand...
Click to collapse
Super bricked allows you to go to odin mode and recovery mode but it's the result of damaged emmc(flash memory) chip son you can not flash any OS
Sent from my GT-N7000 using xda premium
msedek said:
Put your phone in Odin mode there you can see if you have binary counter diferent from 0 if it's not 0 then get a jig to reset it
Sent from my GT-N7000 using xda premium
---------- Post added at 06:54 PM ---------- Previous post was at 06:52 PM ----------
Super bricked allows you to go to odin mode and recovery mode but it's the result of damaged emmc(flash memory) chip son you can not flash any OS
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Well so far i understand is this:
In ODIN mode it says:
ODIN MODE (In red)
PRODUCT NAME: GT-N7000
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICAL
is this it?
Never got into android before, but willing to learn it tho, really like it.
Luckely i still have my galaxy s3 that works perfectly fine (Stock)
By the way,
What if my warranty does not cover this, or there would occur a problem that i cannot send it under warranty what steps can i take to get it working again? or is it really dead....
Hoolz14 said:
Well so far i understand is this:
In ODIN mode it says:
ODIN MODE (In red)
PRODUCT NAME: GT-N7000
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICAL
is this it?
Never got into android before, but willing to learn it tho, really like it.
Luckely i still have my galaxy s3 that works perfectly fine (Stock)
Click to expand...
Click to collapse
Wait, So you say
a.) you were on 2.3.6 i,e, Gingerbread,
b.) you had CWM which I assume is again Gingerbread based,
c.) You backed up and restored from CWM (Gingerbread based) and you got stuck at Boot Logo.
d.) You tried flashing stock ICS ROM via ODIN while on a Gingerbread based kernel.
c.) Stuck at FactoryFS.img which translates to a Superbrick. (While on a Gingerbread Kernel?)
Please contact Entropy ASAP before sending the device to samsung.
Please change your thread title to "Galaxy Note stuck at flashing FactoryFS from Gingerbread." or something similar so that your thread can be noticed easily.
If this is indeed true, then it means we are all going to brick at some point.
Are you SURE you were on Gingerbread when you did the restore?
Your symptoms sound like what happens when wiping with older CF-Root ICS versions (Specifically CF-Root 5.5 for ICS kernels).
Entropy512 said:
Are you SURE you were on Gingerbread when you did the restore?
Your symptoms sound like what happens when wiping with older CF-Root ICS versions (Specifically CF-Root 5.5 for ICS kernels).
Click to expand...
Click to collapse
Girlfriend just got home, and she says it was on android 4.0.3 (So thats ICS) Sorry for this one guys, last time i used the phone its like 3 months ago, and she used it till yesterday.
So, the phone was on android 4.0.3
Hi everyone,
I tried to install the new ICS ROM for my P7310.
Had CM10 installed and first tried to install the modified one via CWM.
Worked like a charm, but after screen was off it became messed up just like this guy had it.
Then I tried to flash the Stock ROM via ODIN. Installed just fine, but now I have the same messed up screen.
Problem is: It is messed up in Stock Recovery, too
{
"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"
}
Can I install an older ROM (which one, tab is from Switzerland) or CWM via Odin?
I think I could hit the download mode without seeing what is on the screen
Thanks in advance!
(Edit: for a solution, scroll to end of this post)
I've heard "garbled screen" a few times regarding the ICS update.
Have you seen these posts? They suggest a solution... (and there's even another reference to Switzerland...)
I don't have experience with the issue, and can't comment beyond what I read elsewhere.
rufree2talk said:
I bought the Tab 8.9 in Switzerland recently... am fairly well informed about working around Android devices... updated the firmware on my stock Honeycomb to the US ICS release via Odin... no issues in the process, and the tablet came up smart and zippy running ICS... even got the Play Movies/Books/Music app which normally doesn't feature in devices sold outside USA... although not much use of them unless I use a VPN service...
the problem is that as soon as I lock the device, or the screen times out, on trying to unlock the device I am met by a garbled unworkable screen... there is no option but to hard-reboot the device to get it working again... somebody is having the same issue here, but I can't post in Development forums... have tried reflashing and all, but its always the same thing... even with stock USA Honeycomb its the same behaviour... is there a region limitation to this firmware for proper functionality?
Click to expand...
Click to collapse
gatt088 said:
Same issue here.. As whit every usa stock based version... I have bricked my tab 2 times, i will appreciate that this issue will be mentioned in new threads as not every xda member is from usa. No problems with jb aosp and cm based version. Waiting for some european stock version
Click to expand...
Click to collapse
rufree2talk said:
I managed to workaround this issue... flashed the P7310UELA3 3.2 via Odin, booted into recovery, performed factory reset/data erase, again flashed P7310UELPB 4.0 via Odin, and this time the Tab has no issue! it works like it should and there is no garbled screen on unlocking... if you want to save your app data before you do these steps, use Titanium...
Click to expand...
Click to collapse
Hurrian said:
If you're not on ICS yet but plan on upgrading, flash P7310UELA3 first. It seems that for some, flashing ICS straight gives you the weird screen strobing.
Click to expand...
Click to collapse
Edit: confirmed solution
by now several people have confirmed that flashing the P7310UELA3 is a working solution to screen flickering after resume from standby. (Flash the UELA3 using Odin, then flash again the ROM you really want to run)
You can find UELA3 ROM via any of these links:
http://forum.xda-developers.com/showthread.php?p=24482346#post24482346 (thx nirogu325 - also linked in post #1 same thread)
http://samsung-updates.com/gt-p7310-galaxy-tab-8-9-wi-fi/
http://forum.xda-developers.com/showthread.php?t=1483168
be kind and hit "Thanks" if this helped you
Thanks a lot!
Installed as supposed, everything is fine now
Glad to know it helped. Good to have that confirmed, for others who may have this...
Click thanks to say thanks
fred_be9300 said:
Glad to know it helped. Good to have that confirmed, for others who may have this...
Click thanks to say thanks
Click to expand...
Click to collapse
Sure
You sir saved my day. Should be posted in the top thread.
Guess the search function will do for most ppl
Back to HC and to ICS again?
I've seen this quote a day late.
" If you're not on ICS yet but plan on upgrading, flash P7310UELA3 first. It seems that for some, flashing ICS straight gives you the weird screen strobing."
Now I have screen problems on ICS when I connect a data cable http://forum.xda-developers.com/showpost.php?p=31410065&postcount=21. If I downgrade via Odin to P7310UELA3 and then go back to ICS via Odin, will data be preserved?
Update after flashing:
I flashed the recommended HC version, Tab couldn't get through bootanimation sequence. I turned the Tab off and started download mode again. Reflashed with ICS and all data was still there. Only the homescreens were empty again. My screen problem is fixed though.
this continues to happen (to small minority?) of people moving from HC to ICS, but seems to be hard to find.
(last case: http://forum.xda-developers.com/showthread.php?t=1895361)
(I've included it a new FAQ I posted here)
thanks
thaks all of u u really save my tablet! I thought it was damaged! I applied the above procedure and everything is perfect now
Hi Everyone
I'm doing something wrong here, hope someone can help.
Every time I install a ROM (Jellybean or ICS) I get the garbled screen after standby.
So, I've tried flashing the P7310UELA3 via Odin and I get a fail, do I just upload it to Bootloader or PDA?
My P7310 is a French version and I have tried flashing the French bootloader too, but still get fail.
I am a noob at this, but I am so close to installing a good rom but fail at the final hurdle. Any help would be fantastic.
Cheers
MikeMcGrathXmen said:
Hi Everyone
I'm doing something wrong here, hope someone can help.
Every time I install a ROM (Jellybean or ICS) I get the garbled screen after standby.
So, I've tried flashing the P7310UELA3 via Odin and I get a fail, do I just upload it to Bootloader or PDA?
My P7310 is a French version and I have tried flashing the French bootloader too, but still get fail.
I am a noob at this, but I am so close to installing a good rom but fail at the final hurdle. Any help would be fantastic.
Cheers
Click to expand...
Click to collapse
flash the full rom as PDA
prince93 said:
flash the full rom as PDA
Click to expand...
Click to collapse
Doesn't seem to work for me, i keep getting fail, maybe because its a French version? I really dont know what else to do!
MikeMcGrathXmen said:
Doesn't seem to work for me, i keep getting fail, maybe because its a French version? I really dont know what else to do!
Click to expand...
Click to collapse
you need to UNCHECK the "repartition" option.. have you already done this ?
prince93 said:
you need to UNCHECK the "repartition" option.. have you already done this ?
Click to expand...
Click to collapse
Yeah, mine is defaulted with repartition unchecked. I really dont understand what I'm doing wrong.
MikeMcGrathXmen said:
Yeah, mine is defaulted with repartition unchecked. I really dont understand what I'm doing wrong.
Click to expand...
Click to collapse
do you get the communication port with a yellow color before flashing?
also, make sure you are using the original USB cable that came with your tablet to flash it
I flashed my 7310 with UELA3 using Odin and then used default recovery to install CWM 6.0.0.8.
But now CWM is rolling very fast, not readable.
I found this solution, but it's for the 10.1 tab. http://forum.xda-developers.com/showthread.php?p=27830023#post27830023
Should I try it on my 8.9?
Need ROM P7310UELA3 - hotfile links brokrn
Hi,
Thank you for sharing this solution.
Unfortunately , I could not find a working link to ROM P7310UELA3, since hotfile was shut down.
Could anyone share this ROM with me ?
Thank you, Jacques.
jfy65 said:
Hi,
Thank you for sharing this solution.
Unfortunately , I could not find a working link to ROM P7310UELA3, since hotfile was shut down.
Could anyone share this ROM with me ?
Thank you, Jacques.
Click to expand...
Click to collapse
I think this P7310UELA3 is android 3.2, and the android ICS 4.0.4 is available
so even if you want an android 3.2, I don't think you'll find anyone who can share it with you
If it is OK to use android ICS there is a link I already uploaded to Dev-Host HERE
this is all I got, and this all I have and can share with anyone
Need ROM P7310UELA3 - hotfile links broken
omarainea said:
I think this P7310UELA3 is android 3.2, and the android ICS 4.0.4 is available
so even if you want an android 3.2, I don't think you'll find anyone who can share it with you
If it is OK to use android ICS there is a link I already uploaded to Dev-Host
this is all I got, and this all I have and can share with anyone
Click to expand...
Click to collapse
Thanks. This whole stream is about the problem with the installation of stock ICS ROM which results in screen flickering on some devices. It happened to me after upgrading with KIES: The tablet becomes completely unusable. The solution suggested and tested above is to flash P7310UELA3 before ICS. Unfortunately, I could not find a working link to ROM P7310UELA3, since hotfile was shut down.
Could anyone share this ROM with me ?
Thank you, Jacques.
I'm new to the captivate , I just bought a captivate off ebay with cm 10.1 , i just bought it to learn more about android , and i would like to know how i can
Unroot (which way (one click etc) to use? , because i do not know which way was used to root the phone ? )
Reason i ask this is , coz i was reading some of the stickies , i read somewhere that if u are on CM , then when u restore to stock , i have to do something to the root partition?
ALSO , The phone is running CM 10.1 , i would like to downgrade to 2.1 or 2.1 so that i can sim unlock the phone?.. how do i downgrade?
Here is the Stock One Click Master Collection... http://forum.xda-developers.com/showthread.php?p=18370235
The other Stickied threads in the Dev and Q&A forum will prove useful as well.
Sent from my SAMSUNG-SGH-I747 using xda premium
4-2ndtwin said:
Here is the Stock One Click Master Collection... http://forum.xda-developers.com/showthread.php?p=18370235
The other Stickied threads in the Dev and Q&A forum will prove useful as well.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Thank you so much for your reply
Just to clarify - can i use the odin one click packages found in this post (am not sure whether i have to use with or w/o bootloader?) ? , if i just flash them to my phone via odin one click , everything will go back to stock? (am on cm 10.1 , internal sd card will be partitioned right?) , and will i lose root too?
On a totally different topic , what if i dont want to go back to stock , unroot , but want to keep the root , and try out different roms on other versions (GB,ICS) (i am currently on cm10.1 jb) , what do i have to do?
Sorry for being a pain , but i read through the threads , im just confused , because i read everywhere about the not to flash gb bootloaders etc , so even if the rom is jellybean , its based on a gb bootloader?
galaxys3lover said:
Thank you so much for your reply
Just to clarify - can i use the odin one click packages found in this post (am not sure whether i have to use with or w/o bootloader?) ? , if i just flash them to my phone via odin one click , everything will go back to stock? (am on cm 10.1 , internal sd card will be partitioned right?) , and will i lose root too?
On a totally different topic , what if i dont want to go back to stock , unroot , but want to keep the root , and try out different roms on other versions (GB,ICS) (i am currently on cm10.1 jb) , what do i have to do?
Sorry for being a pain , but i read through the threads , im just confused , because i read everywhere about the not to flash gb bootloaders etc , so even if the rom is jellybean , its based on a gb bootloader?
Click to expand...
Click to collapse
Bootloader: GB = GB, ICS, JB / Eclair = Eclair, Froyo.
Flashing Odin3 one click downloader will flash the Eclair bootloaders, unroot and bring you back to stock. If you want to root on stock 2.1, simply flash a custom kernel in recovery. From 2.2+, they added the signature verification and you'll have to use Odin 1.87 to flash a custom kernel (to get cwm), which will also root your device.
To get back to GB+, you'll have to flash Odin KK4 with bootloaders. From there, follow this guide to get on whichever ROM you want. Remember to always follow the FULL ROM instructions (I'd suggest to avoid ICS due to the EU bug).
For any JB ROM, you'll have to flash the ROM twice as the first time, it has to repartition. Also, a few JB ROM don't include the Gapps so you'll have to flash them after flashing the ROM.
For any ROM, you can use the kernel that is provided or flash another one, just make sure it is compatible with the ROM you're running (2.1, 2.2, 2.3, 4.0, 4.1.2, 4.2.2).
P.S.: The reason why you see not to flash bootloaders everywhere is cause that's the only way to hard brick your phone, if it goes wrong that is (USB unplugs, bad connections, etc.). Also, you'll notice it fast enough but JB is seriously the best you can do to that phone beside Froyo Firefly with Speedmod kernel (less features of course).
P.S.: The reason why you see not to flash bootloaders everywhere is cause that's the only way to hard brick your phone, if it goes wrong that is (USB unplugs, bad connections, etc.). Also, you'll notice it fast enough but JB is seriously the best you can do to that phone beside Froyo Firefly with Speedmod kernel (less features of course).
Click to expand...
Click to collapse
This pretty much sums up what I was going to say. I can honestly say I'd never want this phone to go back to stock after trying out the JB ROMs. The phone doesn't suffer from speed issues at all, you can OC (depending on hardware, mine really can't but some people have theirs clocked at 1.4ghz/140%). Unless you were selling the phone back to AT&T or taking it in for repair or what not, I see no reason to be on 2.2 not-rooted etc.
x0ne215 said:
This pretty much sums up what I was going to say. I can honestly say I'd never want this phone to go back to stock after trying out the JB ROMs. The phone doesn't suffer from speed issues at all, you can OC (depending on hardware, mine really can't but some people have theirs clocked at 1.4ghz/140%). Unless you were selling the phone back to AT&T or taking it in for repair or what not, I see no reason to be on 2.2 not-rooted etc.
Click to expand...
Click to collapse
Thank you so much!!! This helped me and i can see a lot of other people too , Thank you Great support guys Cheers
P.S : Man! am i an aidiot for buying a captivate , everywhere i look it just seems like i see only one word - BRICK BRICK BRICK! , i should have got someother phone
galaxys3lover said:
Thank you so much!!! This helped me and i can see a lot of other people too , Thank you Great support guys Cheers
P.S : Man! am i an aidiot for buying a captivate , everywhere i look it just seems like i see only one word - BRICK BRICK BRICK! , i should have got someother phone
Click to expand...
Click to collapse
If you read carefully and understand everything you're doing before doing it, you won't brick it. That stands for every devices. The problem is that people are too eager (impatient) to hack it and rush into it without knowing what they're doing. And remember, the only way to actually brick it if something goes wrong while flashing the bootloaders and even then, it's recoverable with JTAG service.
galaxys3lover said:
P.S : Man! am i an aidiot for buying a captivate , everywhere i look it just seems like i see only one word - BRICK BRICK BRICK! , i should have got someother phone
Click to expand...
Click to collapse
What are you talking about? You'll need to do something extremely stupid to hard brick the Captivate. And its still repairable even after hard brick. All ROM change procedures are very well documented, just follow the instructions and your Captivate will live long life. Not too many phones have same great support like Captivate.
I love my cappy, there are so many guides here and people with knowledge there should be no reason you brick your phone other than:
1. If you get lazy and try to skip steps
2. You don't ask when you don't know
Check out the rest of the Q/A section, there are step by step guides on rooting/flashing that are pretty much brick proof if you follow along.
galaxys3lover said:
Reason i ask this is , coz i was reading some of the stickies...
Click to expand...
Click to collapse
Please, read carefully all stickies, not just some of them. Many knowledgeable people here put a lot of time to explain everything about Captivate in an easy to understand way. You'll quickly find all the answers to your questions, including different ways to achieve same results. I got my Captivate with stock 2.3 ROM and 2 days later it was rooted, with CWM and running custom JB ROM. I also managed to soft brick it twice (playing with it and trying almost every ROM available) but recovered for minutes using the great info here on XDA.
Val D. said:
Please, read carefully all stickies, not just some of them. Many knowledgeable people here put a lot of time to explain everything about Captivate in an easy to understand way. You'll quickly find all the answers to your questions, including different ways to achieve same results. I got my Captivate with stock 2.3 ROM and 2 days later it was rooted, with CWM and running custom JB ROM. I also managed to soft brick it twice (playing with it and trying almost every ROM available) but recovered for minutes using the great info here on XDA.
Click to expand...
Click to collapse
This ^
And even if you manage to hardbrick one, you can still recover from that. The only thing that might not be fixable is if you run it over in your car
BWolf56 said:
If you read carefully and understand everything you're doing before doing it, you won't brick it. That stands for every devices. The problem is that people are too eager (impatient) to hack it and rush into it without knowing what they're doing. And remember, the only way to actually brick it if something goes wrong while flashing the bootloaders and even then, it's recoverable with JTAG service.
Click to expand...
Click to collapse
Val D. said:
What are you talking about? You'll need to do something extremely stupid to hard brick the Captivate. And its still repairable even after hard brick. All ROM change procedures are very well documented, just follow the instructions and your Captivate will live long life. Not too many phones have same great support like Captivate.
Click to expand...
Click to collapse
x0ne215 said:
I love my cappy, there are so many guides here and people with knowledge there should be no reason you brick your phone other than:
1. If you get lazy and try to skip steps
2. You don't ask when you don't know
Check out the rest of the Q/A section, there are step by step guides on rooting/flashing that are pretty much brick proof if you follow along.
Click to expand...
Click to collapse
Val D. said:
Please, read carefully all stickies, not just some of them. Many knowledgeable people here put a lot of time to explain everything about Captivate in an easy to understand way. You'll quickly find all the answers to your questions, including different ways to achieve same results. I got my Captivate with stock 2.3 ROM and 2 days later it was rooted, with CWM and running custom JB ROM. I also managed to soft brick it twice (playing with it and trying almost every ROM available) but recovered for minutes using the great info here on XDA.
Click to expand...
Click to collapse
{
"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"
}
JUST KIDDING
Yeah i understand , i just thought since everywhere i saw i only read the word BRICK , i must have made a mistake buying the phone , turns out this is one of te few phones that have a lot of solutions if your phone does get 'BRICK'ed , MY BAD ! :cyclops: and also probably one of the few phones , that even after everybodys moved onto other phones , there are so many people giving support to newcomers! Thanks Guys ! :good::good: :laugh::laugh:
x0ne215 said:
This ^
And even if you manage to hardbrick one, you can still recover from that. The only thing that might not be fixable is if you run it over in your car
Click to expand...
Click to collapse
Haha , ! hopefully i dont end up doing that
galaxys3lover said:
JUST KIDDING
Yeah i understand , i just thought since everywhere i saw i only read the word BRICK , i must have made a mistake buying the phone , turns out this is one of te few phones that have a lot of solutions if your phone does get 'BRICK'ed , MY BAD ! :cyclops: and also probably one of the few phones , that even after everybodys moved onto other phones , there are so many people giving support to newcomers! Thanks Guys ! :good::good: :laugh::laugh:
Haha , ! hopefully i dont end up doing that
Click to expand...
Click to collapse
It surprised me too how many people still offer support and help for this phone, it's almost 3 years old now
No problem, and unfortunately I've had the pleasure of doing that to 2 phones I've owned....
Pro tip: Don't wear basketball shorts and put your phone without a rubber case or similar in it....it will most likely fall out and you won't notice
x0ne215 said:
It surprised me too how many people still offer support and help for this phone, it's almost 3 years old now
No problem, and unfortunately I've had the pleasure of doing that to 2 phones I've owned....
Pro tip: Don't wear basketball shorts and put your phone without a rubber case or similar in it....it will most likely fall out and you won't notice
Click to expand...
Click to collapse
Exactly , ! i wasnt expecting even a single reply anytime soon , and i ended up getting so many replies and all of them extremely helpful ! took me by surprise! I Did pick the right phone! 2 phones of yours got run over by carss?!!?! Reallyy?? 2 ? WOw!
Well i m getting the phone with a body glove , so i guess thatll help!
4-2ndtwin said:
Here is the Stock One Click Master Collection... http://forum.xda-developers.com/showthread.php?p=18370235
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
BWolf56 said:
Bootloader: GB = GB, ICS, JB / Eclair = Eclair, Froyo.
Click to expand...
Click to collapse
x0ne215 said:
This pretty much sums up what I was going to say. I can honestly say I'd never want this phone to go back to stock after trying out the JB ROMs. ], I see no reason to be on 2.2 not-rooted etc.
Click to expand...
Click to collapse
Val D. said:
Not too many phones have same great support like Captivate.
Click to expand...
Click to collapse
Hey guys! :laugh::laugh:
JUst got my Cappy , locked with at%t , anybody can help me unlock?.. i tried galaxysimunlock and it keeps sayin unable to read nv_data , am running cm10.1 4.2.2 ... any help guys???
galaxys3lover said:
Hey guys! :laugh::laugh:
JUst got my Cappy , locked with at%t , anybody can help me unlock?.. i tried galaxysimunlock and it keeps sayin unable to read nv_data , am running cm10.1 4.2.2 ... any help guys???
Click to expand...
Click to collapse
I think you have to be on stock to unlock.
BWolf56 said:
I think you have to be on stock to unlock.
Click to expand...
Click to collapse
Crap! alright , so back to stop using odin one click kk4 package without bootloaders , root it using galaxysimunlock and then flash cm 4.2.2 to get back to where i am ? right?
galaxys3lover said:
Crap! alright , so back to stop using odin one click kk4 package without bootloaders , root it using galaxysimunlock and then flash cm 4.2.2 to get back to where i am ? right?
Click to expand...
Click to collapse
Stock with odin kk4 without bootloaders.
Unlock with galaxysimunlock.
Then there's a guide to follow to get back to cm 4.2.2 in the stickied: http://forum.xda-developers.com/showthread.php?t=1350266
【Guide】How To flash ANY Captivate ROM from Stock (including ICS)
Sent from my SGH-I747 using xda app-developers app
BWolf56 said:
Stock with odin kk4 without bootloaders.
Unlock with galaxysimunlock.
Then there's a guide to follow to get back to cm 4.2.2 in the stickied: http://forum.xda-developers.com/showthread.php?t=1350266
【Guide】How To flash ANY Captivate ROM from Stock (including ICS)
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks for being so patient and kind God Bless