Database Develop

LPY to GB via PC Odin = super brick?

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

BEST CFW for 2.3.6

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

Messed up screen after ICS update

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.

[Q] Bricked my tablet. Could use some help

Followed this tutorial to the letter and bricked it. I should have known that it would happen, the video it self was rather sketchy to begin with http://youtu.be/fXDvq5SaA70
Anyways, i was hoping maybe someone here could help? The errors im getting are as follows"
E:Failed to mount /efs (invalid argument)
E:check_selective_file:Cant mount /efs
E: Failed to mount /preload (invalid argument)
E: Install_application_for_customer: Cant mount /preload
your storage not prepared yet, please use UI menu for format and reboot actions [my sd card is in the tablet so i dont know why i am getting this error]
E:Failed to mount /efs (invalid argument)
E: multi_csc: Can't mount /efs
Multi-csc applied failed
Dealing with phones seems much simpler... never had a problem rooting other devices.
Does it matter that i did it with odin rather then with heimdall? Im use to odin so i just rather not use heimdall

If you can go to download mode, use overcome method like thousands other.
Follow my signature for the link.
I am assuming yours is P1000 since you didn't say.
Sent from my GT-N7100 using xda app-developers app

I have the verizon one, no idea if that means its the p1000 version.
just got this http://forum.xda-developers.com/attachment.php?attachmentid=835192&d=1325238872
Why is rooting this device so difficult? Never had as much problems with other devices. I'll go ahead and try the overcome method but im willing to bet something goes wrong even then.

The Barron said:
I have the verizon one, no idea if that means its the p1000 version.
just got this http://forum.xda-developers.com/attachment.php?attachmentid=835192&d=1325238872
Why is rooting this device so difficult? Never had as much problems with other devices. I'll go ahead and try the overcome method but im willing to bet something goes wrong even then.
Click to expand...
Click to collapse
Nah..if you try the overcome method..and you download all the needed file and the guide..then follow exactly what the guide told you..nothing going to go wrong..it's foolproof..but verizon..isn't p1000..and i don't remember if overcome method suppot verizon or not..
Edit: just check..overcome don't support SCH-I800..
Correct me if I'm wrong..:thumbup::thumbup:
(҂`☐´)︻╦̵̵̿╤── .:system:.

Confirms not supported
And that video you follow too... For P1000 from the title. I didn't watch.
I guess you flashed a P1000 ROM?
Sent from my GT-N7100 using xda app-developers app

priyana said:
Confirms not supported
And that video you follow too... For P1000 from the title. I didn't watch.
I guess you flashed a P1000 ROM?
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Yeah thats what happened then.
It seems like there's almost no information or love for the sch-i800 haha oh well. If you guys find anything on it though let me know! I'll continue looking tomorrow (about to hit the hay!) but right now it seems like there may not be a solution to my problem :crying: Thank you guys for all the help so far!

The Barron said:
Yeah thats what happened then.
It seems like there's almost no information or love for the sch-i800 haha oh well. If you guys find anything on it though let me know! I'll continue looking tomorrow (about to hit the hay!) but right now it seems like there may not be a solution to my problem :crying: Thank you guys for all the help so far!
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"
}
Here you go..
http://forum.xda-developers.com/showthread.php?p=11601647
It might be old..but that should be a good place to start..
Edit: would you look at that..priyana used to help a similar problem.. and it maybe would help you..
http://forum.xda-developers.com/showthread.php?p=35118206
P/s: try to search the general and Q&A section using "SPH-I800" or "Verizon"
(҂`☐´)︻╦̵̵̿╤── .:system:.

A lot of the links are broken in the original post
Edit: I think the tablet is hard bricked now... wont turn on or display anything

The Barron said:
A lot of the links are broken in the original post
Edit: I think the tablet is hard bricked now... wont turn on or display anything
Click to expand...
Click to collapse
Thats why i told you to "start" from there..
And try to charge it for 4 hour..and try to power on..
Edit: don't just read the op..read other post too..there's might be someone post a working link..
(҂`☐´)︻╦̵̵̿╤── .:system:.

mike_disturbed said:
Thats why i told you to "start" from there..
And try to charge it for 4 hour..and try to power on..
Edit: don't just read the op..read other post too..there's might be someone post a working link..
(҂`☐´)︻╦̵̵̿╤── .:system:.
Click to expand...
Click to collapse
I mean, i tried to start from there and it seemed bricked haha.
Power was dead -.-
Well im gonna see what i can do then with that. Thank you!
Would it matter if i just installed the correct rom of cyanogenmod instead of stock?

The Barron said:
I mean, i tried to start from there and it seemed bricked haha.
Power was dead -.-
Well im gonna see what i can do then with that. Thank you!
Would it matter if i just installed the correct rom of cyanogenmod instead of stock?
Click to expand...
Click to collapse
About the power..you shoud try to let it charge for 4 hour..with wall adapter and if that doesn't work try with usb..then try to power it up..
About installing straight with cyanogenmod..that wouldn't work..coz you need custom recovery (eg. clock work mod[cwm]) to install it..and with your device stuck in secondary download mode..which mean you can't even go to stock recovery mode..
cyanogen must be install via custom recovery mode..
With that being said..
It's matters..
(҂`☐´)︻╦̵̵̿╤── .:system:.

Make sense
Alright i will let it charge for a couple of hours it keeps switching back from secondary download mode to not even on!
Also found this, sounds like it will work! http://www.droidforums.net/forum/samsung-galaxy-tab/113084-how-restore-vzw-galaxy-tab-stock-dj11-9.html#post2118311 Thank you Milke!

I hate to double post but it would be nice if someone could help me out a bit here:
So i made some progress, i can get into download mode now and there is a charging screen and a boot noise (no animation). The problem is when i try to go into recovery mode, i get a whole bunch of screen tears and random red and yellow lines appear the screen and then, well i presume it crashes, reboots, and goes back tot he charging screen.
What im thinking is somehow my bootloader got deleted?
Ive been searching nonstop for a boatloader to put into odin or heimdall but to no avail. Do you guys have any ideas?

You are quite right on. The multi coloured bands is usually bad bootloader. Not deleted, but I knew when people patched their GB bootloader ( with patch meant for Froyo), that happens.
You need to find a complete Rom package that is with boot.bin and Sbl.bin
Within its tar file.
I am not knowledgeable in Verizon tab, so can't help much. But there is a thread in dev forum that has stock rooted Verizon or sprint.
Sent from my GT-N7100 using xda app-developers app

Did you try to take stock samsung rom from samfrimware? And then try the rooting proses again?
-----------------------------------
(҂`☐´)︻╦̵̵̿╤── .:system:.
-----------------------------------
-----------------------------------

priyana said:
You are quite right on. The multi coloured bands is usually bad bootloader. Not deleted, but I knew when people patched their GB bootloader ( with patch meant for Froyo), that happens.
You need to find a complete Rom package that is with boot.bin and Sbl.bin
Within its tar file.
I am not knowledgeable in Verizon tab, so can't help much. But there is a thread in dev forum that has stock rooted Verizon or sprint.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Okay so i got both of these things, where do i put them in respect to heimdall? I know one has to go in the primary bootloader slot (im assuming its boot.bin that goes there), but where does the other one go? And should i load all the extra files with it or just these two files by themselves?
Also mike i got the stock samsung rom but not from samfrimware, there was a google doc page with a zip file with all the stock samsung stuff for the cdma/sch-i800 which i downloaded and used to get out of my hard brick. So i believe its the right one but now its just a question of fixing the bootloader

The Barron said:
Okay so i got both of these things, where do i put them in respect to heimdall? I know one has to go in the primary bootloader slot (im assuming its boot.bin that goes there), but where does the other one go? And should i load all the extra files with it or just these two files by themselves?
Also mike i got the stock samsung rom but not from samfrimware, there was a google doc page with a zip file with all the stock samsung stuff for the cdma/sch-i800 which i downloaded and used to get out of my hard brick. So i believe its the right one but now its just a question of fixing the bootloader
Click to expand...
Click to collapse
Yeah..notice that priyana said..there some rom with gb bootloader..with patch meant for froyo..?
But if you confirm that you got yhe correct stock rom..i recommended that you go to heimdall guide..
Here:
http://forum.xda-developers.com/showthread.php?p=22777739
-----------------------------------
(҂`☐´)︻╦̵̵̿╤── .:system:.
-----------------------------------
-----------------------------------

The thread just tells me a lot of stuff i already know, it doesn't discuss the primary bootloader much though.
So im thinking this would be a good setup. Pretty much the exact thing ive been running except i put the boot.bin in the primary bootloader slot as well.
Also dont mind the progresso bread crumbs i have in my tabs

Status 0 on every Cyanogenmod, help needed.

I've got this phone that I sold to a person, but he couldn't get the camera working and the gallery. Only the contacts and calling worked but before I sold it to him everything worked perfectly fine, now the thing is he says that he got some kind of message and just pressed some buttons.
And now this phone has this issue that the internal SD isn't working or won't see it.
I told him to give the phone to me and I would try and fix it by just wiping it in CWM 6.0.3.2 it was running on Cyanogenmod 10.1 nightly, but now I got this error that it won't install any of the roms anymore of Cyanogen, it gives me this error report :
{
"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"
}
It will just boot to CWM now as I wiped the entire thing so no rom is on it anymore.
Any ideas?
EDIT: Issue has been resolved thanks to xsenman

I have several ideas:
Firstly, you should try mount the phone to PC through 'mounts and storage' option, copy new ROMs and Kernels. You can then try installing different kernel (Semaphore, CyanCore) for JB4.2, reboot to recovery, full wipe and install ROM. If you still get same error, try it with external SD.
If that method won't work, you can try using Odin (but be careful!) - install 3-file JVZ ROM with repartition
Code:
http://forum.xda-developers.com/showthread.php?t=1102881
hotfile. com/dl/136940891/b232b26/I9000XWJVZ_I9000OXAJVT_OXA.rar.html
then JVZ kernel
Code:
www.semaphore. gr/kernels/Semaphore_kernel_JVZ_2.1.1.tar
- and now you should be able to install custom ROMs again.
PS. Remember to take EFS backup if you didn't before.

AreXe said:
I have several ideas:
Firstly, you should try mount the phone to PC through 'mounts and storage' option, copy new ROMs and Kernels. You can then try installing different kernel (Semaphore, CyanCore) for JB4.2, reboot to recovery, full wipe and install ROM. If you still get same error, try it with external SD.
If that method won't work, you can try using Odin (but be careful!) - install 3-file JVZ ROM with repartition
Code:
http://forum.xda-developers.com/showthread.php?t=1102881
hotfile. com/dl/136940891/b232b26/I9000XWJVZ_I9000OXAJVT_OXA.rar.html
then JVZ kernel
Code:
www.semaphore. gr/kernels/Semaphore_kernel_JVZ_2.1.1.tar
- and now you should be able to install custom ROMs again.
PS. Remember to take EFS backup if you didn't before.
Click to expand...
Click to collapse
I'll report back if this method worked.

Solution:- Most likely you have a incompatible CWM, or your Zip files are corrupted or you have mounted /system or /data
Click to expand...
Click to collapse
That's what My Android Solutions say about error "Status 0" in point 26.
For me wiping everything and installing stock rom + kernel with working CWM did a trick when I had similar problems.

Zer0w said:
Any ideas?
Click to expand...
Click to collapse
There are 20 versions of Galaxy S, and their ROMS may not be compatible with each other, so make sure you know which model and which ROM should be used. CWM version 6.0.32 is much advanced version for Gingerbread ROM and used in S3 and S4 models, most likely the reason for your problem
Is your Phone i9000 or i9001? or any of these ?
Galaxy S GT-I9000 Galaxy S International
Galaxy S GT-I9000B Galaxy S Brazil
Galaxy S GT-I9000L Galaxy S Chile
Galaxy S GT-I9000M Vibrant Bell
Galaxy S GT-I9000T Galaxy S Latin America
Galaxy S GT-I9001 Galaxy S Plus International
Galaxy S GT-I9003 Galaxy SL International
Galaxy S GT-I9010 Giorgio Armani International
Galaxy S SCH-I500 Fascinate Verizon
Galaxy S SCH-I510 Droid Charge Verizon
Galaxy S SCH-R910 Galaxy S MetroPCS
Galaxy S SGH-I896 Captivate Rogers
Galaxy S SGH-I897 Captivate At&t
Galaxy S SGH-N013 SC-02B Docomo
Galaxy S SGH-T959 Vibrant T-Mobile (USA)
Galaxy S SGH-T959D Fascinate Telus
Galaxy S SGH-T959V Galaxy S 4G T-Mobile (USA)
Galaxy S SGH-I997 Infuse 4g At&t
Galaxy S SHW-M110S SHW-M110S Korea Telecom
Galaxy S SPH-D700 Epic 4g Sprint
And remember to charge your phone before attempting to Flash.

It's the Galaxy S GT-I9000 Galaxy S International
krzysiekx said:
That's what My Android Solutions say about error "Status 0" in point 26.
For me wiping everything and installing stock rom + kernel with working CWM did a trick when I had similar problems.
Click to expand...
Click to collapse
Can you provide me the files, because I'm searching endlessly here..

Zer0w said:
It's the Galaxy S GT-I9000 Galaxy S International
Click to expand...
Click to collapse
that's good, so you a can follow any of the above recommendations by AreXe or krzysiekx both advising the same thing.

krzysiekx said:
That's what My Android Solutions say about error "Status 0" in point 26.
For me wiping everything and installing stock rom + kernel with working CWM did a trick when I had similar problems.
Click to expand...
Click to collapse
xsenman said:
that's good, so you a can follow any of the above recommendations by AreXe or krzysiekx both advising the same thing.
Click to expand...
Click to collapse
I followed it and now I'm at the point where CWM is no more on the phone, my only last resort is Download mode now. I need the files in order to continue further though, but I have no idea which files I would need for Odin?

Zer0w said:
It's the Galaxy S GT-I9000 Galaxy S International
Can you provide me the files, because I'm searching endlessly here..
Click to expand...
Click to collapse
follow this than downloads links are all there
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.​

xsenman said:
follow this than downloads links are all there
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.​
Click to expand...
Click to collapse
I actually followed that one and it booted up to a password screen, no idea what to do here?
EDIT:
I just entered many wrong passwords to let it wipe a imaginary sd card ._.
But it gave me a list of text, and now it's back
Thanks alot

Zer0w said:
Any ideas?
Click to expand...
Click to collapse
Read over the forum bit more. If you listen the guy who answered you first (AreXe), ask him if he is going to buy you new phone when you brick it, according to his advices. It is nonsense all he wrote you.

tetakpatak said:
Read over the forum bit more. If you listen the guy who answered you first, ask him if he is going to buy you new phone when you brick it, according to his advices. It is nonsense all he wrote you.
Click to expand...
Click to collapse
I fixed it already, and I got it working just fine now.
Gave it back to the guy, he's happy I'm happy.