Database Users

Let's unbrick your phone - Guide (Soft Brick, Super Brick, Hard Brick, OTA Brick)

BRICKED USERS GUIDE.......
First you need to know that this guide is trying to help you..
I cannot take any responsibility for your brick getting harder ....
.....IGNORE ALL WHO SAID NOT TO WASTE THEIR TIME .....
....... The poll was for a different post related to emmc bug where i suggested a workaround for the emmc bug , which I edited several times....
There are three types of bricks for N7000
a) Soft Brick - Stuck at Samsung Logo [Added BootLoop here]
b) Super Brick - Stuck at flashing Factoryfs.IMG in ODIN . Also called as EMMC Bug....
c) Hard Brick - Sorry Unrecoverable by this guide. Try THIS
d) Dead Brick - No charging battery sign also - Mostly = Hard Brick ; But there is a window of possibility by a JIG.
e) OTA Brick - A rare kind of Soft Brick which people have encountered due to updating OTA on a rooted Stock ROM.
f) CM12 Brick - A Brick I and another XDA Mate encountered when CM12 encountered a /data write error. Worst is ODIN Flashing Fails .....
CM12 Brick
CM12 Brick
Error Details : Flashing JB Kernel in ODIN Fails ...
Received Response from LOKE FLashing Failed ....
a) Download the PIT file
b) Flash in Odin
c) After SUCESSFULLY Flashing Pit File
d) Flash ICS KERNEL (SPEEDMOD KERNEL) USING ODIN
e) Now go to Recovery and Flash your Favorite Philz Kernel
SOFT BRICKS
I will try to describe ways to get Soft Bricked so that you can compare.....
You have messed with the system file. Remember the Blue Screen of windows.
==> 1. Deleting any system file .odex
==> 2. Moving from GB or ICS to CM/AOSP/AOKP Roms without following instructions or vice versa
==> 3. Flashing incomplete ROMS (did not check MD5 - Google it How to check)
==> 4. Flashing an incompetent kernel (oh I didnt read instructions)
==> 5. Many other methods
==> 6. JB BootLoop
Now you have to return to normal state. But beware there is a emmc bug which is going to interfere our correction process. Oops ! It hurts. There is no safe way as on date for ICS except there are Safe Kernels Claimed.
Pray to your favorite god or luck or better pray even if you are an atheist.
RECOVERY STYLE 1 : [ODIN]
GINGERBREAD VERSION
1) Use ODIN
2) Uninstall Samsung KIES. It interferes with the ODIN flashing.
You should have the ADB/USB Drivers
Just in case you don't have them, here are the Samsung USB drivers
3) Download the AbyssKernel 4.2 for ODIN.
Incase it fails u can use 3.9 version too.
4) Wipe Data/Cache/Dalvik.
5) FLASH THE ROOTED KJ4 kernel From PC ODIN - Kernel Link
TRY FLASHING THE STOCK ROM in PDA Try the Oldest Stock ROM - KJ4 click me
Remember to Run ODIN in Admin mode (Right Click and Run even if you are an Admin)
6) Head to Dr Ketan Thread for Rooting...
ICS VERSION
1) Use ODIN
2) Uninstall Samsung KIES. It interferes with the ODIN flashing.
You should have the ADB/USB Drivers
Just in case you don't have them, here are the Samsung USB drivers
3) Download the AbyssKernel 4.2 for ODIN.
Incase it fails u can use 3.9 version too.
4) Wipe Data/Cache/Dalvik
5) FLASH ANY ics rooted rom in Abyss Recovery which has a safe kernel
Remember to Run ODIN in Admin mode (Right Click and Run even if you are an Admin)
RECOVERY STYLE 2 : [CWM]
ICS and GINGERBREAD USERS
a) Go to CWM
b) Flash Abyss Kernel 3.9 or 4.2 [Touch version] or Hydracore latest version.
c) Do data/ factory reset.
d) Flash with your favorite ICS / GB /AOSP/ AOKP/PA/CM9/CM10
[BOOTLOOP JB Leak / Official]
ODIN Version
a) Download Stock JB from Dr Ketans Thread
b) Install Tar file via ODIN in PDA
c) Reboot
d) Root as in Dr Ketans Guide
e) Install Custom ROM from CWM if you need
CWM Version
Understanding the issue now. So Prefer ODIN version now.
END SOFT BRICK
SUPER BRICKS
Hmm ... I understand your despair. My friend forest has written a wonderful guide to retrieve you out.
If you are confirmed that you are a Super Brick
Head to this thread ......
But .... Just before heading to Mr Forests Thread May be you are not a Super brick ...
There are few who had the same symptoms of a Super Brick but successfully recovered without the Forest1971 workaround.
RECOVERY STYLE 1 : START HERE
IMPORTANT NOTE : Remove your SD Card and SIM CARD Please
Run ODIN IN ADMIN Mode
a) Now you have to repartition your Note
b) Download the following (Importantly the .pit file)
PIT: Q1_20110914_16GB.pit (Only for users with 16GB Internal SDCard) 32 GB users Please Google ur file.
PDA: CODE_N7000xxxxx_CL627135_REV02_user_low_ship.tar.m d5
PHONE: MODEM_N7000xxxxx_REV_05_CL1067428.tar.md5
CSC: GT-N7000-MULTI-CSC-Oxxxxx.tar.md5
Thanks PrinceOMI & DuckBoot for the download links (PIT Files)
Stock ROM & Pit File Flashing Thread
c) Check these options: Re-Partition, Auto Reboot, and F. Reset Time.
d) Flash thru PC Odin (All the files, particularly the PIT file)
SUCCESS .... GOOD FOR YOU .... Only 2% reported success using this style (I ask you not to Thank me but to write here in this thread if you are successful. Many users do not care..)
RECOVERY STYLE 2 : START HERE
Working on it .... Not able to proceed. Ideas dropped.
END :angel: SUPER BRICK :angel:
:cyclops: OTA BRICKS :cyclops:
I will try to describe ways to get OTA Bricked (very rare)
a) Installed the OTA for ICS ROM Indian Version LPA on a rooted ROM.
Some thing has messed up with your .odex files and you get force closes or Stuck at Samsung LOGO
1) ODIN Method
a) go to Download Mode (Power Button + Vol down + Home)
b) Flash the ICS ROM posted in Dr.Ketan Thread in the PDA
Remember that options are ticked according to this image.
Donot tick repartition.
You can root it by Heading to Dr Ketans thread.
2) CWM Method (Custom Firmware - Closest to LPA ROM)
a) go to Download Mode (Power Button + Vol up + Home)
b) Flash the ROM close to LPA without any Reset or Wiping.
This will endup with a custom ROM Clea Note (LPA Rooted)
END :highfive: SUPER BRICK :highfive:

Dude, that's really sad. You should've gotten your girl her presents before repairing. It's not her fault you flashed custom ROMs.
Sent from my superior GT-N7000 using Tapatalk

Sure I will gift her my Samsung Galaxy Tab ( which I got it repaired due to water entry; She poured water on it )
She Loves Playing with my Tab.

sorry, i don't mean to criticize your method but...
if your eMMC is already dead or corrupted, how is this method gonna revive the note??

I got my Note connected to PC Odin (when it was superbricked) once which I could not replicate again.
Since I got it connected anybody else would by the above procedure.
I always believe that Software Problems can be solved by tweaking Softwares; not by replacing the motherboard; I did it once but I missed How I did it.

prabhu1980 said:
b) Download the following (Importantly the .pit file)
PIT: Q1_20110914_16GB.pit
Click to expand...
Click to collapse
I had a feeling that the partitions are messed up by the kernel and restoring it by pit would help, as it worked for a few people. Anyway here are the pit files

I like optimists, but I hate to see them when they fail
superbrick is when the portion to which ROM gets written is fried due to the bug.
AND, JTAG JIG is different from micro USB JIG.
While I appreciate your gesture to trying help others, wrong information is unwelcome. Also, even if you are able to connect to PC odin after everything, this method does not tell how to make it flash the ROM.
Thanks anyway.
From a bricked user who tried everything to resurrect the note but failed.

Corrected My Post about JTAG (I am not a perfectionist and please allow unintented mistakes)
But I got connected once to PC Odin.
Were you able to connect it ??
Did you try the method posted above while using the JIG ?
You are right !! This method will be OK till PC Odin.
But once you are able to connect; lets try Step 2 and Step 3 (added after some research)
Lets get it connected first.
Getting Fried
Click to expand...
Click to collapse
- Does Flashing Fry your ROM ? Comeon Man Its a Software BUG and it should be possible to recover.
How many times we have fried Windows and Linux and played with Boot Partitions for Multiple OS.
Something should be possible. Please throw some light and help the Superbrick users. Donot demotivate.
Find Ways to Come out of this bugging bug.
I am not a software developer but ur comments will drive me to become one Thanks !!!
While I appreciate your gesture to trying help others, wrong information is unwelcome.
Click to expand...
Click to collapse
Boss !! What I am doing here is just a try before replacing your motherboard ! Hope it will harm no one.

prabhu1980 said:
Did you try the method posted above while using the JIG ?
Click to expand...
Click to collapse
I did when my Note got bricked, and it didn't help one little bit.

I wrote this because I got connected to PC Odin after the Black Screen.
Did you got connected and still unable to recover ??
We should somehow be able to connect it to PC.
Any alternate suggestions Chasmodo .
We have to find a way out of this Brick Issue.
Please help !! (I dont think I can brick to find a way out
If required please make a bounty for the developers to revive from this situation.
My Feeling is "Whatëver bad happened to me should never occur to anyone else"

prabhu1980 said:
I wrote this because I got connected to PC Odin after the Black Screen.
Click to expand...
Click to collapse
I understand your intenstions, but eMMC is fried (i/o bug which might allow excess voltage while wiping or corrupting NAND) no one knows what the reason is yet, but all we know is the partition where the ROM gets written to get corrupted and hence you cannot flash any ROM onto it, no matter what you do!

eMMC Bug which will allow excess voltage damaging the ROM . Thats Frying ....
Thats Poor Hardware right ??
But we dont know what's the BUG. Coz had we known we could have corrected it.
Were you able to connect to PC Odin when you had a blackscreen ??

prabhu1980 said:
I wrote this because I got connected to PC Odin after the Black Screen.
Did you got connected and still unable to recover ??
We should somehow be able to connect it to PC.
Any alternate suggestions Chasmodo .
We have to find a way out of this Brick Issue.
Please help !! (I dont think I can brick to find a way out
If required please make a bounty for the developers to revive from this situation.
My Feeling is "Whatëver bad happened to me should never occur to anyone else"
Click to expand...
Click to collapse
You found your way out of a situation caused by the Repack Rom, not by the LPY one.
LPY bricks seem to do physical damage to your EMMC chip, so connecting your
Note to the PC will do no good. PC Odin flash will fail because of the damaged EMMC blocks.
There's a lot of bricked users who can get into Download and/or Recovery mode,
but ALL their flashes still fail. See this: http://forum.xda-developers.com/showthread.php?t=1653290
I fear the Note community will be remembering this LPY debacle for a long, long time. There's no known cure for now.

LPY bricks seem to do physical damage to your EMMC chip
Click to expand...
Click to collapse
It seems or Is it confirmed damage ??
Please dont think I am pulling too hard. May be if Emmc is getting damaged why not replace Emmc chip instead of the whole motherboard. I got my Motherboard replaced..
If Partitions are getting fried then Why cant we re partition it ?

anilisanil said:
I understand your intenstions, but eMMC is fried (i/o bug which might allow excess voltage while wiping or corrupting NAND) no one knows what the reason is yet, but all we know is the partition where the ROM gets written to get corrupted and hence you cannot flash any ROM onto it, no matter what you do!
Click to expand...
Click to collapse
Did you re-partition your ROM ??
If you had done it. Can we have a re partition (modified PIT) for LPY to overcome the area corrupted ??
There are ways to repartition . Included Step 3 in my post.
You may be right !! But I am just looking for a solution like you ....
But since you are using words like MIGHT and MAY I m still guessing solutions may exist.
Please read this Thread http://forum.xda-developers.com/showthread.php?p=26167317#post26167317

anyone tested yet?
Sent from my GT-N7000 using XDA Premium HD app

Looks like there is one success case jpturibio
Please look into this. Try Try until u succeed.

prabhu1980 said:
Looks like there is one success case jpturibio
Please look into this. Try Try until u succeed.
Click to expand...
Click to collapse
I really have no idea. Samsung service guys even tried JTAG my device, but the whole thing conked off while JTAG and they replaced my device under warranty.
So if a JTAG could not restore my phone, how would I know if flashing repetitively would help. Anyway, I am glad it worked for someone, and I get a feeling that we would soon be finding some solution to this plague!

Please watch this thread and Post your success / parted snapshots here.

Please look into this !! Factory.RFS users.
Dont get demotivated. Many have gone past this in several forums (Google it and See)
Many have success cases.
We have to evolve a method , so please post to help me solve this issue.

[GUIDE] Upgrading and modding NTT DoCoMo SC-01C (Japanese P1000)

Kind of a niche guide, but at least non-Japanese people owning an SC-01C have some sort of guidelines.
Before we begin
The SC-01C is the rebranded Japanese version of the P1000, locked exclusively to NTT DoCoMo. If you have this model and want to upgrade and/or flash custom ROMs with it, this guide may be able to help you.
Before beginning, you have to check your firmware version. What you'll have to download will depend on it. If you have Android 2.2 Froyo, read on, otherwise, if you're already running Android 2.3 Gingerbread skip to the Gingerbread Users section.
Also, based on experience, if you want to upgrade to other ROMs in the future you will have to keep your stock GB ROM file, your gt-p1000_mr.pit, the dbdata.tar and the entire Overcome kit (kernel and ROM). You will need all of them in the future because I've found that to install a new ROM you have to repeat the entire process of restocking to GB, then installing Overcome Kernel and ROM, then installing whatever ROM you want. It sucks, but it's the only way I've seen so far.
Froyo Users
If you're planning to install a custom ROM, you can't do it on Froyo straight away, at least not on a stock ROM with a protected bootloader. If you don't know if your bootloader is protected or not, the safest thing to do is to first upgrade your firmware to the stock Japanese Android 2.3 Gingerbread. Then you can follow the Gingerbread guide afterwards.
Froyo Users Will Need
Stock Japanese GB ROM (you can get it from here or from SamFirmware.com). The ROM is a .tar archive file, so you will also need 7-Zip or another file extracting utility to extract files from the tar file.
Odin 1.7 (higher versions will likely not hurt either)
Heimdall (in case Odin doesn't work or you aren't running Windows)
Upgrading to Gingerbread
Make sure your PC has the drivers for your Tab. If you've already connected your PC to the Tab before, you already have them. Otherwise, plug your Tab into your PC and let the drivers install automatically. This works even if you're in Download Mode. If they don't install automatically, you might need to download Samsung Kies or just the Samsung USB Driver for Mobile Phones to get the driver to install.
[FOR HEIMDALL USERS]
You will need to plug in your Tab and run zadig.exe for your drivers, which is found either in the same folder as your Heimdall.exe or in the Drivers folder in that same folder, depending on which version you have. From there, select Options -> List All Devices, then select Gadget Serial or Android USB Composite Interface, then click Install Driver.
After getting the drivers, unplug your Tab (you can keep the PC end plugged in). Turn off your Tab and plug your USB Interface cord into your PC (not the Tab just yet), then put your Tab into Download Mode. You can do this by either holding down the Power and Volume Down keys while the Tab is off, or simply holding down the Volume Down key while plugging in the cord to your Tab. If done correctly, you should see a screen with a yellow Android with a shovel, together with the words "DOWNLOAD MODE, DO NOT TURN OFF TARGET!"
If you're running Windows and using Odin, extract the gt-p1000_mr.pit from the .tar archive into the same folder as the archive. Otherwise, if you're running Heimdall, extract the entire archive into the same folder as your Heimdall.exe.
Plug your Tab back in if you haven't already. The next step will vary for Odin and Heimdall users.
[FOR ODIN USERS]
Open Odin and check if there is a yellow box amongst all the white ones which says [COM4] or something like that, it doesn't matter as long as the box is yellow.
Click PIT and select the gt-p1000_mr.pit you extracted from the stock Japanese GB .tar file, then click Start. This will re-partition the device, and it is absolutely critical that this is done first, as missing this step can cause a brick.
After the PIT flashing is successful, click Reset, then click PDA and select the stock Japanese GB .tar file, and click Start. You will have to wait for a few minutes while the ROM flashes. Progress bars will appear both on the Tab screen and Odin.
NOTE: If after flashing you boot into Recovery Mode and you get the following error:
Code:
E: part(1) DATA Checksum Error
E: part(1) Checksum Error
Internal MMC checksum verify failed.
Then you will have to download and flash dbdata.tar as PDA (Google "P1000 dbdata.tar"; it's about 1.25MB or so). That should solve it.
[FOR HEIMDALL USERS]
Since you already extracted the contents of the stock Japanese GB .tar file into the same folder as your Heimdall.exe, all you have to do is run the following command from a Terminal window (or Command Prompt if you're running Windows):
Code:
heimdall flash --repartition --primary-boot boot.bin --cache cache.rfs --dbdata dbdata.rfs --factoryfs factoryfs.rfs --pit gt-p1000_mr.pit --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage --verbose
Wait a few minutes while Heimdall flashes the ROM. It should inform you when the flashing is successful.
After the flashing is successful, you should now be running stock Android 2.3 Gingerbread. You can stop here or continue on to the Gingerbread Users section for flashing a custom ROM.
Gingerbread Users
Since you're already on Gingerbread, which is the latest stock Android version you have, you're probably reading this guide to find out how to install custom ROMs. Personally I've found, after bricking my Tab a couple of times, that trying to flash custom ROMs from the stock Japanese GB ROM doesn't work unless you flash the Overcome kernel and ROM first.
Hence, the first step to getting a custom ROM running on an SC-01C is to flash the Overcome kernel. For instructions on how to do this, go to the guide thread at the end of the paragraph. You can skip the restocking part, as you're already running stock GB. Instead, follow the instructions from Step 7 of the guide, found on Page 10. After following the instructions there and flashing the Overcome kernel and ROM, you should now be able to flash any other custom ROM you want, following the instructions for the regular P1000.
Getting the Overcome kernel and ROM: http://forum.xda-developers.com/showthread.php?t=1881981
Questions, Answers and Possible Issues
My SC-01C is stuck at boot logo after trying (and failing) to flash custom ROM.
Solving this issue depends on your firmware version and whether or not you can still get into Download Mode. If you can, just follow the instructions in this guide exactly and the problem should be solved.
My SC-01C is stuck at phone-exclamation mark!-computer screen.
This is also likely because of a failed ROM flashing or firmware upgrade. In that case, you can use Heimdall OneClickUnbrick to fix it. A guide to do so can be found here.
My SC-01C isn't detected by Odin, and/or Heimdall produces a "Claiming interface failed" error.
Your drivers aren't being detected and either need to be installed or reinstalled. To force a driver reinstall on Windows, plug in your Tab, go to the System Tray, right-click Safely Remove Hardware and Eject Media, then select Open Devices and Printers. Find your Tab's device name from there, then right-click it and select Remove Device, then unplug your Tab and plug it in again. The drivers should reinstall automatically. If they still don't reinstall, download Samsung Kies or the Samsung USB Driver for Mobile Phones and try again.
For other possible questions or concerns, please reply to this thread.

After successful repair, No Network/ No service
I followed the first method and recovered a bricked P1000 docomo
But No network/service
Any ideas ?

dannyogolo said:
I followed the first method and recovered a bricked P1000 docomo
But No network/service
Any ideas ?
Click to expand...
Click to collapse
You'll need to modify it further to get it to work with other providers. I'm personally not sure if it's a hardware or a software hack, because I paid someone to unlock my Tab back when I didn't know jack **** about modding. If it was already unlocked prior to being bricked, try to flash a new ROM over it. Either way, please hit back if you find the answer so I can add it to the FAQ section.

Hi! I just got the SC-01C & it was already loaded with a custom ICS firmware. Would it be ok to flash another custom firmware DIRECTLY? or Do I still need to flash the GB first?

only root
how to root without change stock rom?
It is possible ?
Thank you

zmeus said:
how to root without change stock rom?
It is possible ?
Thank you
Click to expand...
Click to collapse
Yes it's possible, just Google "how to root galaxy tab". There's a few methods, so just pick one.
Sent from my GT-P1000 using xda app-developers app

Thank you
This it will help me for sure.
Sent from my GT-I9100 using Tapatalk 4

"Hi im a noob and i hate myself"
finally found a thread that that covers japanese p1000.
I have a one it was given to me and still on android froyo 2.2 it is been unlocked by software and i don't know if its been rooted or not.
for the past days i've been looking over the net for this particular device to be upgrade to the latest jellybean rom.this will be very helpful for me since i dont know anything about flashing. been reading threads over and over bec i dont want to brick this device for i use it as a secondary phone
Will flashing to the original docomo GB 2.3... stock firmware make the tab in an locked state again? and is the new rom like the cyanogenmod 10.1 or 10.2 have a built in unlock?

joevinz said:
"Hi im a noob and i hate myself"
finally found a thread that that covers japanese p1000.
I have a one it was given to me and still on android froyo 2.2 it is been unlocked by software and i don't know if its been rooted or not.
for the past days i've been looking over the net for this particular device to be upgrade to the latest jellybean rom.this will be very helpful for me since i dont know anything about flashing. been reading threads over and over bec i dont want to brick this device for i use it as a secondary phone
Will flashing to the original docomo GB 2.3... stock firmware make the tab in an locked state again? and is the new rom like the cyanogenmod 10.1 or 10.2 have a built in unlock?
Click to expand...
Click to collapse
No, 2,3 has an unlocked bootloader. Just follow the guide carefully step by step and you should be fine.

geno93n0 said:
No, 2,3 has an unlocked bootloader. Just follow the guide carefully step by step and you should be fine.
Click to expand...
Click to collapse
ok that's good to know, i'll prep up first before having a go. just be patient with me pls. bec from time to time i'll be asking you alot if i mess up. . thank in advance. thank button has been used.:good:

joevinz said:
ok that's good to know, i'll prep up first before having a go. just be patient with me pls. bec from time to time i'll be asking you alot if i mess up. . thank in advance. thank button has been used.:good:
Click to expand...
Click to collapse
No problem, ask away. I made a lot of mistakes by experimenting on my own, so I made this guide to make the process easier for people with our model.

Hi i have a problem with SC-01C Gingerbread OMKE2, ive been stuck in boot.bin and it fails to flash the overcome using ODIN, what should i do? pls help

Help I think I am bricked
I have a sc-01c bought in japan...I tried flashing and now all i get is the docomo screen...I think i may have deleted everything on the tab...I can get into dl mode but whether flashing with odin or heimdall i get errors...Is there a way to wipe totally and reinstall from scratch....

WILLIEFRANCE said:
I have a sc-01c bought in japan...I tried flashing and now all i get is the docomo screen...I think i may have deleted everything on the tab...I can get into dl mode but whether flashing with odin or heimdall i get errors...Is there a way to wipe totally and reinstall from scratch....
Click to expand...
Click to collapse
What are you Trying to do? and what errors?

SC-01C
rence.slvdr said:
What are you Trying to do? and what errors?
Click to expand...
Click to collapse
I am trying to install the stock rom using odin. I flash the pit then reboot go back to dl mode and flash the tar(stock) i think i hosed the device...Odin says it passed and it reset...but all i get is docommo screen then after the samsung galaxy screen and it keeps blinking ever few minutes like it cant reboot...I ALSO tried flashing the newer Stock 2.3? and the same issue...
I think I may have mucked up the software but can get into DL mode...any ideas?
I followed the directions but still no joy....Perhaps I am dense...
But basically
Flash pit
reboot
Flash stock
Blinking samsung
Odin says reset and no errors...

WILLIEFRANCE said:
I am trying to install the stock rom using odin. I flash the pit then reboot go back to dl mode and flash the tar(stock) i think i hosed the device...Odin says it passed and it reset...but all i get is docommo screen then after the samsung galaxy screen and it keeps blinking ever few minutes like it cant reboot...I ALSO tried flashing the newer Stock 2.3? and the same issue...
I think I may have mucked up the software but can get into DL mode...any ideas?
I followed the directions but still no joy....Perhaps I am dense...
But basically
Flash pit
reboot
Flash stock
Blinking samsung
Odin says reset and no errors...
Click to expand...
Click to collapse
This happened to me as well, it's why I wrote this guide. Try the Overcome method that I posted in the guide, or search for it in this forum. Also, are you using the stock Japanese GB ROM or just a normal stock ROM? You need to use the stock Japanese Gingerbread ROM. I provided links in the guide.

rence.slvdr said:
Hi i have a problem with SC-01C Gingerbread OMKE2, ive been stuck in boot.bin and it fails to flash the overcome using ODIN, what should i do? pls help
Click to expand...
Click to collapse
Don't flash them all at once. Look at the Overcome guide carefully.

pls help
hi.. im new here and i have a problem with modding my sc01c tab. im already running on official gingerbread SC01COMKE2 firmware and im also rooted. i followed all the steps but always ended up with a soft brick. heres what i did.. i downloaded overcome files from http://forum.xda-developers.com/showthread.php?t=1881981 and followed step by step guide. i flashed Overcome_Kernel_v4.0.0.tar and boot into recovery mode.. then flashed Overcome_7_Series_v4.1.0_Wipe.. but it says cannot open BAD FILE. i redownload even the no wipe version but same happens. i tried to restock using GB-Stock-Safe-v5 but it failed in odin.. whats weird is that when i flashed my tab with official firmware it succeeded without a problem.. can you guys help me here? what did i miss or do wrong? pls dont hate me much im just a noob.

geno93n0 said:
No problem, ask away. I made a lot of mistakes by experimenting on my own, so I made this guide to make the process easier for people with our model.
Click to expand...
Click to collapse
ah finally had the time to modd my docomo tab, heres what happened, fashing the pit file went ok, but flashing the rom went haywire ended up brick. i did everything to the letter but to no success. i manage to unbrick the tab and redo the whole thing but i always end up bricking it. rom fails to flash. any ideas? should i be rooted in froyo before doing this?

ah finally after countless trial and error finally updated my tab to gingerbread, now next step is to root and install clockwork recovery mod. i will not rst until my tab gets the lates jellybean rom hahahah,

[q] need help please

I am quiet a noob at rooting and using odin. Well, my problem is i tried to unroot using odin and I was flashing L720VPUFNAE_L720SPTFNAE_SPR using PDA but then my phone accidentally disconnected and now I cannot flash that..I am really scared I soft bricked my phone. Kies will not download due to some stupid errors..I REALLY NEED HELP. I rooted and unrooted and unflashed and flashed numerous times.. But now it's not letting me do the basic PDA flash. I was flashing the stock rom. I don't mess with roms they are unstable and buggy at least cyanogen was. I fixed that error easy but now I am stuck in "Firmware upgrade encountered an issue. Please select recovery in kies & try again". I cannot download kies and when I do it asks to delete previous versions and then fails and asks the same thing a million times, stupid kies. Well, I can get in download mode without a problem I just don't know what I would need to do now. I am kinda trippy. MY phone an fyi is running 4.4.2 Kitkat if that matters.

mattgraal said:
I am quiet a noob at rooting and using odin. Well, my problem is i tried to unroot using odin and I was flashing L720VPUFNAE_L720SPTFNAE_SPR using PDA but then my phone accidentally disconnected and now I cannot flash that..I am really scared I soft bricked my phone. Kies will not download due to some stupid errors..I REALLY NEED HELP. I rooted and unrooted and unflashed and flashed numerous times.. But now it's not letting me do the basic PDA flash. I was flashing the stock rom. I don't mess with roms they are unstable and buggy at least cyanogen was. I fixed that error easy but now I am stuck in "Firmware upgrade encountered an issue. Please select recovery in kies & try again". I cannot download kies and when I do it asks to delete previous versions and then fails and asks the same thing a million times, stupid kies. Well, I can get in download mode without a problem I just don't know what I would need to do now. I am kinda trippy. MY phone an fyi is running 4.4.2 Kitkat if that matters.
Click to expand...
Click to collapse
Uninstall kies from your pc if you have it installed already. All you need is latest Samsung USB drivers. You can find them on google and after that strictly follow the below guide :-
http://forum.xda-developers.com/showthread.php?t=2265477
Please make sure you have all the necessary files required to flash a new firmware according to the model of your phone. The guide above is just for helping you follow the right steps !

AbhiLP said:
Uninstall kies from your pc if you have it installed already. All you need is latest Samsung USB drivers. You can find them on google and after that strictly follow the below guide :-
http://forum.xda-developers.com/showthread.php?t=2265477
Please make sure you have all the necessary files required to flash a new firmware according to the model of your phone. The guide above is just for helping you follow the right steps !
Click to expand...
Click to collapse
Okay, I got that..I'll just find kies and wipe it X)

Also, make sure you are using a newer version of Odin while flashing the new Stock Tar files. Recommended is odin 3.07 or 3.09 for fewer problems.

Please Help... Samsung Galaxy Core 2 (SM-G355H) Soft Brick problem...

Hi all... Sorry for barging in.. I would like to ask for help about my samsung galaxy core 2 (SM-G355H). About 3 days ago, this phone suddenly restart and all settings just exactly like new factory settings. Almost all my applications gone and the internal memory only have 100 MB left. Theres around 2 GB files inside my internal memory, yet I cannot find it anywhere. I've tried ES File explorer, unhidden the files, windows explorer, and all... But I can still couldn't find the files.
So, I decided to let things over and flash my phone using official stock ROM from sammobile via Odin. After I finished the procedure, this warning comes out:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again
The condition is:
1. Whenever I try recovery mode, it will show the above sign (not working at all..)
2. Download mode is working
What I've tried until today:
1. Flash using Odin+stock ROM. When it's done & reboot, it will comes back to 'Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again'. not even samsung logo ever appear again
2. Flash using recovery.tar > Same result when reboot
3. Flash using Odin+stock ROM+PIT files > Same result when reboot
4. Kies recovery. It's done, reboot and the warning sign is the same..
Can anyone give me any suggestion? I'm already at desperate stage right now... I've searched in this forums for few days, yet I haven't found any solution yet (mostly because I'm a noob i guess.... :silly: )please help......
Thank you for all your help
Nb: I'm sorry if this thread is in the wrong place.... Please notify me and I'll fix it...

huv u fixed ur problem

Nadeem1122 said:
huv u fixed ur problem
Click to expand...
Click to collapse
i have nearly the same problem. any ideas?

Also too
And i tray by adb ..........also i can,t solve this FU** problem >>>>>>IF someone know how to fix it ,pleas tell us !!! :crying::crying::crying:

Brick
When i flaahed cm 12. Phne has been bricked showing no sim card. I tried to insatall firmware data cable is not supporting otherwise phone is charging well. When i cheked EMI No. Showing NULL.
SO WHAT I SHOULD TO DO ???
AT SERVICE CENTER FOUND SAME PROBLEM THEY CAN'T RECOGNISED THEM.

Attach screen shot if possible...may i can figure out the problem...but first u need to install recovery via adb or ODIN...Uncheck reboot option in ODIN...waiting for u replay

Best official stock rom
motomuzieq said:
Hi all... Sorry for barging in.. I would like to ask for help about my samsung galaxy core 2 (SM-G355H). About 3 days ago, this phone suddenly restart and all settings just exactly like new factory settings. Almost all my applications gone and the internal memory only have 100 MB left. Theres around 2 GB files inside my internal memory, yet I cannot find it anywhere. I've tried ES File explorer, unhidden the files, windows explorer, and all... But I can still couldn't find the files.
So, I decided to let things over and flash my phone using official stock ROM from sammobile via Odin. After I finished the procedure, this warning comes out:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again
The condition is:
1. Whenever I try recovery mode, it will show the above sign (not working at all..)
2. Download mode is working
What I've tried until today:
1. Flash using Odin+stock ROM. When it's done & reboot, it will comes back to 'Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again'. not even samsung logo ever appear again
2. Flash using recovery.tar > Same result when reboot
3. Flash using Odin+stock ROM+PIT files > Same result when reboot
4. Kies recovery. It's done, reboot and the warning sign is the same..
Can anyone give me any suggestion? I'm already at desperate stage right now... I've searched in this forums for few days, yet I haven't found any solution yet (mostly because I'm a noob i guess.... :silly: )please help......
Thank you for all your help
Nb: I'm sorry if this thread is in the wrong place.... Please notify me and I'll fix it...
Click to expand...
Click to collapse
Try this Official Firmware with Odin : https://firmwarefile.com/samsung-sm-g355h :fingers-crossed::good:

how to update all partitions right?

Hello
first of all i am searching for solutions for 2 days and i dont find some normal expl. for my problem.
So a friend gave me his s5 so i can use it. i have restored to factorysettings.
i want to flash a never rom on it and decidet to flash LineAgeOs.
So with Odin i flashed TWRP and then from the S5 i installed Lineage and gapps... btw i wanted root acces but havent figuret out how 2 (but thats not my problem i know just install some SU apk...)
so is used phone for some days until lineage have again get an update to 16 and without root i have to install it manualy via Odin and i did.
what i saw in lineage15 in Sequrity Trust Options is that my Vendor is not uptodate.
so i dont want to use phone if security is old.
Im trying to understand how to update this to never safe versions. (and maybe all the other systempartitions) without bricking my phone.
looks like i have to update all the fields(BL,CP,CSC) in Odin and not just the AP field.<-- and here i need help
i know there must be answer out there but im sooo tired searching.
pls if someone can give me complete instructions and not just a mass of shortcuts, this woud be rly cool
i have win7 and win10
on win7 my phone cant install MTP (so i have to remove sdcard to SDadapter... to get files on sdcard) [but odin still worked flashing TWRP]
on win10 i cant install USBdrivers it give me no permission idk and odin dont find my phone
i switching, plug, repluging the hell out and nothing works.
i think i have to restore factory somehow and then somehow get the BL CP CSC updated so i can start with TWRP LIneAge and rooting
I found this sammobile site and tried to find out what kind G900F this is but didnt know. then is saw a detailed modelnumber on twrp boot and searched on sammobile. looks like its the T-Mobile one BUT i dont use T MobileSIM. I use Alditalk its a mix of 02 an Eplus i think.
Do i need to install specific for my SIM? omg im so tired of all this
Info:
Model: SM-G900F
Germany
win7 / win 10
ty