Database Users

JMC: *** Flashing Guide ***

READ BEFORE YOU FLASH: THIS FIRMWARE HAS A PROTECTED BOOTLOADER THAT WILL PREVENT YOU FROM FLASHING SAMSUNG OFFICIAL FIRMWARE.
MORE INFO HERE
I don't know if this process actually flash boot and spl because JM6 doesn't seem to have them, but you're on your own and I don't recommend you to do it.
Ok I'm going to make a detailed guide of how this worked for me because succeed depends a lot on which firmware you have in your tab. It's a good idea to start with JM6 since you can flash it completely if you have an older firmware or JMA (I guess you won't be able to flash it in the future if a new firmware is released). You won't lose your internal SD Card data but your phone will be factory reset.
1) Download JM6 from HERE
You'll get Odin 1.7 + PIT + PHONE + PDA + CSC.
2) Download JMA from here: HERE
3) Download JMC from here: HERE
4) Start Odin 1.7 and select:
*PIT P1_SMD_MAP.pit
*REPARTITION YES
*AUTO REBOOT YES
*F. RESET TIME YES
*PDA: CODE_P1000XXJM6.tar.md5
*PHONE: MODEM_P1000XXJM6.tar.md5
*CSC: CSC_P1000OXAJM6.tar.md5
5) Put your TAB in download mode: Turn it off, press POWER + VOL DOWN
6) Press start in ODIN and wait until process is completed. Your tab will REBOOT in download mode.
7) Now press POWER + VOL UP and when you see SAMSUNG logo RELEASE POWER BUT KEEP PRESSING VOL UP in order to enter recovery and let the TAB flash dbdata, it'll reboot and boot into android. (unplug your USB cable because Odin won't recognize it on some systems)
8) Open Odin 1.7 again or press RESET and select:
*PIT: NONE
*REPARTITION NO
*AUTO REBOOT YES
*F. RESET TIME YES
*PDA: JMA.tar (from JMA file obviously)
*PHONE: NONE
*CSC: NONE
9) Repeat 5), 6) and 7)
10) Open Odin 1.7 again or press RESET and select:
*PIT: NONE
*REPARTITION NO
*AUTO REBOOT YES
*F. RESET TIME YES
*PDA: P1000XXJMC_P1000OXAJMC_P1000XXJMA_HOME.tar (from JMC file obviously)
*PHONE: NONE
*CSC: NONE
11) Repeat 5), 6) and 7)
I have an AT&T TAB and this process worked for me.
If you need 850 + 1900 you only have to flash MODEM (PHONE button in ODIN) from HERE (modem_bell_i9000.zip) with No PIT, no repartition, no PDA and no CSC.
I hope this helps anybody and sorry about my english
EDIT: If for some strage reason you get the !!! --- !!! screen in your tab, don't panic. You can start the whole process again, Odin will detect your phone, it's a download mode anyway.
EDIT2: I always choose to wipe all my data. I use Titanium backup and I can get most of my data back from there. It's better to have a functional tab than a brick full of useless data. Wiping will always be safer.
EDIT3: Made some modifications to step 7. What you need to do is to enter recovery and that's it. It wasn't clear. Now I think you'll get it right. I didn't test it without step 7 but some people seems to be doing well without doing step 7. Maybe device is entering recovery automatically and flashing dbdata on its own (this is to be expected but sometimes it just doesn't happen).

What about rooting the device before you flash...?

Working great!!! However, I just didn't do step 7 in any of the 3 updates. What exactly do you mean in step 7? Which of the 4 options should I choose in Step 7?
Thanks

pt4audi said:
What about rooting the device before you flash...?
Click to expand...
Click to collapse
I could root my device with z4root or superoneclick.
lucboucim said:
Working great!!! However, I just didn't do step 7 in any of the 3 updates. What exactly do you mean in step 7? Which of the 4 options should I choose in Step 7?
Thanks
Click to expand...
Click to collapse
When flashing ends your device should install dbdata in recovery mode. Maybe with this procedure dbdata is flashed automatically when flashing JM6 at the beginning it's not necessary to do it manually.
If dbdata is not flashed you will not be able to boot android. Your device should display something like this when that happens (in recovery mode):
E:copy_dbdata_media:cant mount DBDATA: copy default media conent failed.
Click to expand...
Click to collapse
But I guess you're ok
Just ignore step 7 if your device entered recovery mode automatically after flashing ended.

OP , did U enable the voice capabilities ? And what was your initial firmware ?
Do U feel confident to say that you can str8 go from whatever FW you have to JM6 as a full flash , and not anymore move your way up from JJ4 (russian FW ) ?
P

pakalrtb said:
OP , did U enable the voice capabilities ? And what was your initial firmware ?
Do U feel confident to say that you can str8 go from whatever FW you have to JM6 as a full flash , and not anymore move your way up from JJ4 (russian FW ) ?
P
Click to expand...
Click to collapse
If by voice capabilities you mean putting a sim card, yes, I tried and it works fine. I didn't test it that much, just a few calls and a lot of gprs. My initial firmware was jk5.
If I had a firmware older than JJ4 I'd just try to flash JM6 directly. I'm guessing here but I think that flashing JM6 the way I flashed it (following another guide in another forum) is like a full flash, it shouldn't matter what you had before.
Maybe someone with more knowledge could throw a light in here. What I can tell you is that I'd do it. I'm one of those guys that learn the hard way, and I've never bricked a device for good.

You're like me then. I do not even have my Tab yet but my fingers are already so much itching. In the meanwhile I am reading and learning. I am totally new to Samsung but I've had my hands busy for the past year with my Nexus One, so quite confortable playing with rom/kernel/radio world .
P_

Flashing for morons
Monrad, thanks, this is a super post.
Just for me and all the other morons in the world. Can you also please give a basic run through of what you've done. I have the following questions.
1) You have 3 waves of activities in your post: JM6, JMA, JMC. Generally, what is each wave doing?
2) Please would you also explain what the fields in Odin1.7 are for?
*PIT -does this set the partitions on Samsung tab?
*REPARTITION -if PIT file this is automatically selected
*AUTO REBOOT YES -why do I select yes
*F. RESET TIME YES -what's this one for?
*PDA: CODE_P1000XXJM6.tar.md5 -PDA is core PDA firmware?
*PHONE: MODEM_P1000XXJM6.tar.md5 -what does this do? load modem drivers?
*CSC: CSC_P1000OXAJM6.tar.md5 -I'm not sure what CSC stands for and does?
3) With regards to getting my dirty hands on the right firmware, when I go to http://www.samfirmware.com/WEBPROTECT-p1000.htm, I look at the latest firmware for Europe. At the bottom of the list are 3 downloads:
a) JM6, b) JMA, c) JMC. What are the differences between these firmwares. I understand that J = 2010, but don't know how to decrypt last two digits.
4) Which PIT should be used in Step 1 of your sequence? What are the PIT files at the bottom of the page (in Flash Tools Section) of http://www.samfirmware.com/WEBPROTECT-p1000.htm
5) I bricked my tab. I got it alive again, only by loading the JMA via Odin 1.7. Basically I put my Tab in Download Mode. Started Odin1.7. Used the Eur Pit file (referred to in my Step 4), and then loaded JMA.tar (extracted from JMA file mentioned in my Step 3). With all the check marks checked in Odin. That was it, and my Galaxy Tab rebooted and seems to work totally fine. Why would I do the other steps mentioned in your sequence? What benefit is there?
5a) Note when I do *#1234# I get:
PDA: blank
PHONE: P1000XXJMA
CSC: blank
the PDA and CSC show blank....is that why I should first load JM6 and follow your sequence? What functionality do I currently not have because of these blanks?
6) A question on rooting my Tab... what are the benefits to doing this?
Thanks for dealing with my long winded post! I really appreciate what you've done so far.

You are a good man, Monrad!
I followed steps and got my AT&T tab updated.
A word about wiping data: I had my Tab fully set up with original AT&T firmware and then I started installation I got into lots of trouble. Instead of recovery mode it went into blank screen with vertical white line (I suspect it did dbdata update behind it though), then it rebooted and my apps started crashing.
The only way to fix it was to get to setting and do factory reset. After that everything went by the book.
So you may want to clarify that data must be wiped from Android, unless you have some other way.
Thanks again

How and where do I find the Dbdata file ?
When I go for step 7 i get the "can´t mount" and "media content failed" messages.
Edit:
alexnoalex said:
So you may want to clarify that data must be wiped from Android, unless you have some other way.
Thanks again
Click to expand...
Click to collapse
I believe this can also be done from recovery.

i used roto-jmc and dont boot into recovery of flash dbdata.rfs seperately and everything is working fine.

kromosto said:
i used roto-jmc and dont boot into recovery of flash dbdata.rfs seperately and everything is working fine.
Click to expand...
Click to collapse
Where did you get the Roto-jmc?

from the link
http://forum.xda-developers.com/showpost.php?p=9989856&postcount=50

Great man. Thanks.
Edit: didn´t help. I still get the same errors.
I now seems to work. But my *#1234# says jm6 even on the jmc firmware?

Anybody knows what is the differences between JMA and JMC ?

You don't need to flash JMA. You can go straight from JM6 to JMC
You can skip oen unnecessary step

Can i do this on my euro Tab from Denmark?
Im on JM6
Sent from my GT-P1000 using XDA App

Just did the update from JMA on a euro tab, I took the firmware from samfirmware not the one on the first post. I don't know the difference but the size is not the same..
Everything works fine, even without doing a factory reset, all my applications are working fine.But I don't see any differences between JMA and JMC

Guys
Currently i have
PDA: P1000JPJJ1
PHONE: P1000JXJJ1
CSC: P1000OJPJJ3
Its currently arabic firmware. Can i use this guide & update to this Euro fimrware? I dont need arabic. I am not rooted as well. Will this guide work for me?

i have a problem, all ok till JM6
and tab after start fine
but for JMA or JMC no dbdata in recovery
help me (for now i'm back to JM6)

Problem when trying to root phone

Hi, I was following this guide http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S:_Full_Update_Guide found on http://forum.xda-developers.com/showthread.php?t=1298691.
I got as far as the Installing the ClockworkMod Recovery, when I got to step 8 'Click Start on the Heimdall Frontend. A blue transfer bar will appear on the phone showing the kernel being transferred. The device will reboot automatically.' BUT when the phone tried to reboot it gets stuck on the first Galaxy S screen. I could get in to download mode and recovery mode but nothing else. Does this mean my mobile is bricked? What do I do know?
Thanks in advance

You have flashed a rom, not only root your device. And cyanogenmod is not based on samsung firmware.
Think you shold read some more.
But, how long do you wait on the s logo? It thakes some time to boot up first time when catche is wiped.
If you only want to root you shold search for cf root for your stock rom. If you want to go back, you have to download a stock rom. Found att samfirmware.com
Sent from my GT-I9000 using Tapatalk

No not bricked (nowhere near)............ Reflash...
I have read many times that re-flashing will do the trick. If you have download mode, you can flash any rom onto it, i would use odin as it may be the safest whilst you being in limbo. Then if you want to follow a link for CM 7.1 that is both v.entertaining (my opinion) and clear i suggest you click on the link in my sig...

Robert - Sorry I did mean flash as well as root. I waited around 15-20 minutes, isnt that long enough?
Talon - I have tried to re-flash using the guide method I was originally using but get the same problem. To be honest from looking at Odin information on this forum, it has confused me quite a bit (lot of different advice), not sure if I am doing the right thing.
I did make the mistake of jumping into trying to flash & root my phone. Any help of what to do to get my phone to a working state, would be very much appreciated.

@OP: as long as you can put phone in Download mode - it is not bricked.
ALWAYS, you can restore everything by flashing stock ROM with repartition.
If you will not be able to go to download mode - well... then you have something to worry about

spamtrash said:
@OP: as long as you can put phone in Download mode - it is not bricked.
ALWAYS, you can restore everything by flashing stock ROM with repartition.
If you will not be able to go to download mode - well... then you have something to worry about
Click to expand...
Click to collapse
I'm a bit confused, what would be the best way to do that?

Well find stock FW from below, then flash it using the guides..
Generally now days you get 2 files, Pit either 512 513 or 813 (or something similar). And you get a .tar file or other zip type extension and put that in pda. Then flash
you may get 3 files and a pit file in which case you put it in the appropriate places....
Ive written this guide and telling you it is a GUIDE. Wherever you get your files from there should be instructions as to what to do.
For example you may need to do a factory reset before (unlikely but still) More likely is that you will have to disable lagfix, but you shoudnt have to worry about that. Main thing read the guide and follow the guide from where you get the files. The thread you get it from...read the first and last 5 pages, more if you want to be safe.
Now files, i have links to stock FW below, guide are usually present within them. If not read the thread, but also read the thread and search th thread for answers or the section or the SGS forum.

IF before you were on 2.2.x - try some Froyo from sammfirmware. If you were on Ginger - try Click
Of course, you can search for EAzyBase... but it is more advanced, start from the basics...

OMG, there are tons of tutorials and how to's in here about flashing and rooting phones... who uses heimdall? get Odin for flashing:
1. Install KIES for drivers (you might already have done this).
2. Get a rom from samfirmware/sammobile, I recommend JVP because it has gingerbread bootloaders: http://www.sammobile.com/threads/17-Samsung-I9000-Galaxy-S-Firmwares
3. Get Odin (sorry I coudn't find a link)
4. Get your phone in download mode (VolDown, Home, Power).
5. Connect your phone to PC with USB cable.
6. Set the PDA, CSC and MODEM files in Odin from the firmware you downloaded from step2.
7. Make sure you have "re-partition" enabled and set the .PIT file to use the *512.pit also included in the firmware from step 2.
8. click start.
9. Start your phone and set up the startup wizard.
9. For rooting, get the CF-root for your firmware from here: http://forum.xda-developers.com/showthread.php?t=788108
10. Get your phone into download again.
11. DON'T check repartition in odin, only select the CF-Root file as PDA (you have to use the CF-Root-***.TAR, important to use .TAR and not .ZIP.
12. Flash again, now you are rooted!!

[TOOL] Samsung Galaxy Rescue Kit

After running into a bit of trouble myself and seeing how many people ran into the same thing, namely bricking, i decided to create a quick and easy toolkit for unbricking which did the trick for me. The one i'm posting is for SGS I9000 Intl Version, using latest european firmware from this thread: http://forum.xda-developers.com/showthread.php?t=846913.
However you can create your own custom kit by replacing the files in the kit and modifying the batchfile i've included. Just make sure to read the readme file included for details.
What it does:
- unbricks
- flashes
- flashes with format
- does not use ****ty Odin.
This kit uses the 1click unbrick solution & Heimdall. For those, credit goes to Adam Outler for making the 1click unbrick and to Benjamin Dobell for making Heimdall. It's nothing out of the ordinary. It's just ingeniously flexible. That's all. Anyone with a bit of brain and 5 minutes of spare time can make himself one for his phone and it will get him out of the sticky situation of reverting from ics to gingerbread.
Basically this is all you need to get from broken to working. All of this took me roughly ~10 hours or more of grueling testing and experimenting on my own till 5 in the morn. If you use this or make your own, just credit me & gimme a thanks.
Download the kit from here (240 Mbs):
http://hotfile.com/dl/146355868/42dfea1/SGS_Rescue_kit-13-1-2012.rar.html

Hi. Does that mean I just need my USB cable and your soft to unbrick any SGS without download mode ?
Downloading, and gonna try it.

Sanael said:
Hi. Does that mean I just need my USB cable and your soft to unbrick any SGS without download mode ?
Downloading, and gonna try it.
Click to expand...
Click to collapse
I doubt. You will need usb jig for that. I think this is for softbrick and not for totally bricked SGS.
Sent from my GT-I9000 using xda premium

Hi guys, this is only for the case in which your phone is still able to enter download mode.

ldq said:
Hi guys, this is only for the case in which your phone is still able to enter download mode.
Click to expand...
Click to collapse
So not for bricked, just for softbricked phones.
Sent from my GT-I9000 using xda premium

Seems like a good idea I'll check it out later.

I've updated the download link with a new, working one.

ldq said:
Hi guys, this is only for the case in which your phone is still able to enter download mode.
Click to expand...
Click to collapse
Thanks for this post! I will be studying this closely in the coming days.
A quick question: when people cannot enter download mode, is that the situation when the button sequence doesn't work? in that scenario, i used "adb reboot download" -- worked well. after flashing via odin, it seems my button sequence works again.

It worked even on Linux!
Thanks alot for your link.
Unfortunately I use Linux as main OS. Your approach is more MS based but it saved my day anyway.
Had just to paste this shell command after compyling Heimdall for my ubuntu x64 distribution.
sudo heimdall flash --repartition --pit s1_odin_20100512.pit --factoryfs factoryfs.rfs --cache cache.rfs --dbdata dbdata.rfs --primary-boot boot.bin --secondary-boot Sbl.bin --param param.lfs --kernel zImage --modem modem.bin
Hope my donation may pay you a beer

Thanks a lot dude ! and hey, glad i could help !
PS: Feel free to create a linux based version as well , if the same batchfile principle applies... why not ?

tanclo said:
Thanks for this post! I will be studying this closely in the coming days.
A quick question: when people cannot enter download mode, is that the situation when the button sequence doesn't work? in that scenario, i used "adb reboot download" -- worked well. after flashing via odin, it seems my button sequence works again.
Click to expand...
Click to collapse
In short yes, but it may also be because you're nervous and/or for some reason cannot press to button combo correctly, or if they are broken by hardware.
hmm... Its also possible to include a batch command to adb into download mode for extra comfort at the push of 2 buttons. I'll have to update the kit asap.

ldq said:
In short yes, but it may also be because you're nervous and/or for some reason cannot press to button combo correctly, or if they are broken by hardware.
hmm... Its also possible to include a batch command to adb into download mode for extra comfort at the push of 2 buttons. I'll have to update the kit asap.
Click to expand...
Click to collapse
Thanks for working so tirelessly on this script. I might give it a go on a windows box or look into your bash to use it on ubuntu. I'm afraid that Heimdall doesn't work on my device yet, though.
And yes, there is a big chance that it was me doing it wrong. on my device, the sequence seems to change with new Kies update too. Entering recovery is just crazy take a look here for further amusement
way simpler to just "adb reboot recovery" and keep the button pressing party for that inevitable rainy day

Hey my cell has been USB Bricked. That means the computer and Odin doesn't detect the cell even when it is in download mode. And not charges either. Will this still work? Can you please give me step-by-step instructions?

Can somebody please explain me the simple point of this software.
As far as I understood this can only be used, if you failed to enter download mode using your phone and you would like to re-instal a rom .. Or is this just a rom install manager?
Sorry confused

1337SereniTyx3 said:
Hey my cell has been USB Bricked. That means the computer and Odin doesn't detect the cell even when it is in download mode. And not charges either. Will this still work? Can you please give me step-by-step instructions?
Click to expand...
Click to collapse
Well, for starters you could try to bring it into download mode, use batchfile included and select the option of unbricking it. If that does not work, you may want to try and install the included drivers then attempt to unbrick again.
Can somebody please explain me the simple point of this software.
As far as I understood this can only be used, if you failed to enter download mode using your phone and you would like to re-instal a rom .. Or is this just a rom install manager?
Sorry confused
Click to expand...
Click to collapse
the point of this kit is to bring your phone from softbrick status into working condition (bootable). So no matter how bad you screw up with the rom installations, you can revert to this, re-root, and you're back on your feet.
Which reminds me: i gotta include a already rooted SGS EU rom. )
tanclo said:
Thanks for working so tirelessly on this script. I might give it a go on a windows box or look into your bash to use it on ubuntu. I'm afraid that Heimdall doesn't work on my device yet, though.
And yes, there is a big chance that it was me doing it wrong. on my device, the sequence seems to change with new Kies update too. Entering recovery is just crazy take a look here for further amusement
way simpler to just "adb reboot recovery" and keep the button pressing party for that inevitable rainy day
Click to expand...
Click to collapse
) Saw that. Ticks me off every time I gotta do the button juggle thinggie. I also tend to use adb console, because its far simpler ! )
Do you happen to know of any good batch scripting guides ? I've been looking for some indepth guide but can't find any. What I'd like to do is use a command which takes some parameters (like where you got your android sdk) and turn it into the path for the adb console (since you need to start it up with parameters like adb reboot recovery, that means that i have to actually tell the script to go into that folder via cd and run the app.). But if you know of alternative ways of starting it up, I'm all ears

Need help
i need some help here
i'm stuck, my phone was working well but i wanted to revert it to stock rom and followed instructions, but something goes bad
now i'm able just to enter in download mode, i can't enter recovery mode or even turn on my phone

jaskoooo said:
i need some help here
i'm stuck, my phone was working well but i wanted to revert it to stock rom and followed instructions, but something goes bad
now i'm able just to enter in download mode, i can't enter recovery mode or even turn on my phone
Click to expand...
Click to collapse
Just flash the stock rom again with odin, and cf-root if you want recovery. Good luck!

Nicely packaged up. However, after I ran:
Code:
heimdall flash --repartition --pit s1_odin_20100512.pit --factoryfs factoryfs.rfs --cache cache.rfs --dbdata dbdata.rfs --primary-boot boot.bin --secondary-boot Sbl.bin --param param.lfs --kernel zImage --modem modem.bin
The reboot presents me with "Confirm password". Got a bit confused, but it appears the trick is to just enter any password about 5 times until prompted that this will wipe the card. Then you're back in.
Just in case someone runs into the same situation and was as confused as I was.

ldq said:
After running into a bit of trouble myself and seeing how many people ran into the same thing, namely bricking, i decided to create a quick and easy toolkit for unbricking which did the trick for me. The one i'm posting is for SGS I9000 Intl Version, using latest european firmware from this thread: http://forum.xda-developers.com/showthread.php?t=846913.
However you can create your own custom kit by replacing the files in the kit and modifying the batchfile i've included. Just make sure to read the readme file included for details.
What it does:
- unbricks
- flashes
- flashes with format
- does not use ****ty Odin.
This kit uses the 1click unbrick solution & Heimdall. For those, credit goes to Adam Outler for making the 1click unbrick and to Benjamin Dobell for making Heimdall. It's nothing out of the ordinary. It's just ingeniously flexible. That's all. Anyone with a bit of brain and 5 minutes of spare time can make himself one for his phone and it will get him out of the sticky situation of reverting from ics to gingerbread.
Basically this is all you need to get from broken to working. All of this took me roughly ~10 hours or more of grueling testing and experimenting on my own till 5 in the morn. If you use this or make your own, just credit me & gimme a thanks.
Download the kit from here (240 Mbs):
http://hotfile.com/dl/146355868/42dfea1/SGS_Rescue_kit-13-1-2012.rar.html
Click to expand...
Click to collapse
Just used this, I was able to flash my Rom (Replacing with my files) all went well, I did a cache wipe partition and factory data reset in the 3e recovery, just before rebooting it said "unable to mount /data REBOOTING..." and rebooted, and then it rebooted and hangs at the I9000 Logo and waits for ever keeps cycling..
Any idea?
Edit : Before touching the 3e recovery this error shows up : (straight after flashing)
ASSERT FAILED : getprop("ro.product.device") == " GT-P1000" ||.... etc
E: Error in /cache/recovery/sec_csc.zip (STATUS7) Installation aborted

MaTSuNg said:
Just used this, I was able to flash my Rom (Replacing with my files) all went well, I did a cache wipe partition and factory data reset in the 3e recovery, just before rebooting it said "unable to mount /data REBOOTING..." and rebooted, and then it rebooted and hangs at the I9000 Logo and waits for ever keeps cycling..
Any idea?
Edit : Before touching the 3e recovery this error shows up : (straight after flashing)
ASSERT FAILED : getprop("ro.product.device") == " GT-P1000" ||.... etc
E: Error in /cache/recovery/sec_csc.zip (STATUS7) Installation aborted
Click to expand...
Click to collapse
Honestly I have no ideea mate. I can only guarantee for the files I supplied in my zip file. If you changed them with yours, it might indicate some of them might be corrupted or not working. I've only used the recovery kit to pull myself out of bricking and revert to stock rom. I didn't try installing a custom rom. Not sure what you were trying to do.
I advise you to try and debrick (should work), and do a format and then install.
If that doesn't work, dunno what to say. As I said above, for me it worked each time.

[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,

Need help unbricking my Galaxy S7 edge SM-G935P phone

I flashed the firmware from here https://forum.xda-developers.com/tmobile-s7-edge/how-to/6-8-t-mobile-935u-firmware-qe2-t3619151 along with the Tmobile radio via Odin 3.13.1, it failed in Odin and now the phone is stuck on the samsung logo. I used the BL and the AP from the zip, the CP I used from the separate tmobile download link. For the CSC I first tried the CSC that is in the package and when that failed I tried the HOME CSC even that failed. the User data I kept blank both times.. Then I tried it a third time same as above except in the CSC I put the CSC file from the zip and in Userdata I put the Home CSC file, it failed again. Am i doing something wrong ?
Update: I have been trying to flash the stock firmware from samobile, but I am unable to do even that. It keeps failing. I downloaded the firmware from here https://www.sammobile.com/firmwares/...S5BRA1/206887/, extracted it, added just the AP and as per instructions went in to download mode, clicked on start and it keeps failing. In Options only auto reboot and f reset is clicked.
I would really appreciate any help to unbrick this device, it is stuck on an exclamation mark saying " An error has occurred while updating the device software. Use the emergency recovery function in the smart switch PC software". Smartswitch is not recognizing this device saying it's an unsupported device so emergency restore software wont work from there. I can get it into download mode but as I said flashing the firmware via Odin is not working. I can also get it into recovery mode but it keeps endlessly trying to update, fail and loop back to trying to update.
Thanks in advance.

Firstly I would check your use cable, I have a bunch and not all of them work. Secondly, make sure that your phone is being recognized on PC, hence the cable check. and third, make sure you are flashing the correct firmware. You said TMB, but I see you are flashing 3 different company files. Hi back to full G935P firmware , you front need to flash TMB on t, it should be fine cause I have a g935p with TMB sim in it
Anything else I'll be glad to help
bothambhai said:
I flashed the firmware from here https://forum.xda-developers.com/tmobile-s7-edge/how-to/6-8-t-mobile-935u-firmware-qe2-t3619151 along with the Tmobile radio via Odin 3.13.1, it failed in Odin and now the phone is stuck on the samsung logo. I used the BL and the AP from the zip, the CP I used from the separate tmobile download link. For the CSC I first tried the CSC that is in the package and when that failed I tried the HOME CSC even that failed. the User data I kept blank both times.. Then I tried it a third time same as above except in the CSC I put the CSC file from the zip and in Userdata I put the Home CSC file, it failed again. Am i doing something wrong ?
Update: I have been trying to flash the stock firmware from samobile, but I am unable to do even that. It keeps failing. I downloaded the firmware from here https://www.sammobile.com/firmwares/...S5BRA1/206887/, extracted it, added just the AP and as per instructions went in to download mode, clicked on start and it keeps failing. In Options only auto reboot and f reset is clicked.
I would really appreciate any help to unbrick this device, it is stuck on an exclamation mark saying " An error has occurred while updating the device software. Use the emergency recovery function in the smart switch PC software". Smartswitch is not recognizing this device saying it's an unsupported device so emergency restore software wont work from there. I can get it into download mode but as I said flashing the firmware via Odin is not working. I can also get it into recovery mode but it keeps endlessly trying to update, fail and loop back to trying to update.
Thanks in advance.
Click to expand...
Click to collapse

just checking... are you using the edited princecomsy odin? http://d-h.st/gsDA or use the link here https://forum.xda-developers.com/att-s7-edge/help/princes-odin-t3545104
find the correct rom here https://forum.xda-developers.com/sprint-s7-edge/how-to/odin-stock-nougat-firmware-s7-edge-t3569834
just use files from one rom at a time. get good at that first. maybe you are careful but it really looks like you were guessing what goes where at the end of your post.
i just have tips on what helped me. passing along the info and the link.

epikroms said:
Firstly I would check your use cable, I have a bunch and not all of them work. Secondly, make sure that your phone is being recognized on PC, hence the cable check. and third, make sure you are flashing the correct firmware. You said TMB, but I see you are flashing 3 different company files. Hi back to full G935P firmware , you front need to flash TMB on t, it should be fine cause I have a g935p with TMB sim in it
Anything else I'll be glad to help
Click to expand...
Click to collapse
What is your APN settings ? With the sprint firmware I could either get LTE data or calls and text not both at the same time.
Thanks.

bothambhai said:
What is your APN settings ? With the sprint firmware I could either get LTE data or calls and text not both at the same time.
Thanks.
Click to expand...
Click to collapse
Im actually on the G935U rom from jrkruse. If you are on the latest firmware just skip the flashing of the stock U firmware. Just flash eng boot, root it, and follow his process in his t-mobile thread for flashing in flashfire. When aroma starts it asks you what kernel to flash just choose tmobile and it works instantly. But fo APN settings whatbi had was this:
Name
T-Mobile US LTE
Apn
fast.t-mobile.com
Mmsc
http://mms.msg.eng.t-mobile.com/mms/wapenc
Apn Type
default,supl,mms or Internet+MMS

epikroms said:
Im actually on the G935U rom from jrkruse. If you are on the latest firmware just skip the flashing of the stock U firmware. Just flash eng boot, root it, and follow his process in his t-mobile thread for flashing in flashfire. When aroma starts it asks you what kernel to flash just choose tmobile and it works instantly. But fo APN settings whatbi had was this:
Name
T-Mobile US LTE
Apn
fast.t-mobile.com
Mmsc
http://mms.msg.eng.t-mobile.com/mms/wapenc
Apn Type
default,supl,mms or Internet+MMS
Click to expand...
Click to collapse
I managed to flash back the Sprint firmware. I feel the problem is Sprint is probably the only one with an upgraded baseband due to their last update. Both the TMO and U firmwares are based on the 4 baseband G930TUVS4BRA1 and the last Sprint update put it on a 5 baseband G935PVPS5BRA1. That is what is causing for it to fail, I feel. Do you think if I follow the eng.boot method I should be able to overcome the problem ?

bothambhai said:
I managed to flash back the Sprint firmware. I feel the problem is Sprint is probably the only one with an upgraded baseband due to their last update. Both the TMO and U firmwares are based on the 4 baseband G930TUVS4BRA1 and the last Sprint update put it on a 5 baseband G935PVPS5BRA1. That is what is causing for it to fail, I feel. Do you think if I follow the eng.boot method I should be able to overcome the problem ?
Click to expand...
Click to collapse
Okay the problem you are having is that you are actually on bootloader 5 not baseband 5. So that number represents the bootloader and there is no way of downgrading as of yet. Samsung does this thing with fuses on the phone being blown as the bootloader upgrades, well as far as i know from the s8&s8+. So your problem you are having is that you are trying to flash a previous bootloader which isn't going to happen. Flashing the QK5 or the BRA1 firmware will work. Cause it's on bootloader 5. I'd you do what I said a couple posts ago you'll be fine I'm still running the U series tom with tmo kernel installed and I have actually had 0 issues so far. It's been completely solid and everything works, data, sms, Wi-Fi calling, etc...... it works after flashing and boot. With the Sprint tom I got headache after headache and the activating thing is annoying. Just do what I said and you'll see a that what jrkruse then did is probably going to be the only best thing the Sprint variant gets. Try it

epikroms said:
Okay the problem you are having is that you are actually on bootloader 5 not baseband 5. So that number represents the bootloader and there is no way of downgrading as of yet. Samsung does this thing with fuses on the phone being blown as the bootloader upgrades, well as far as i know from the s8&s8+. So your problem you are having is that you are trying to flash a previous bootloader which isn't going to happen. Flashing the QK5 or the BRA1 firmware will work. Cause it's on bootloader 5. I'd you do what I said a couple posts ago you'll be fine I'm still running the U series tom with tmo kernel installed and I have actually had 0 issues so far. It's been completely solid and everything works, data, sms, Wi-Fi calling, etc...... it works after flashing and boot. With the Sprint tom I got headache after headache and the activating thing is annoying. Just do what I said and you'll see a that what jrkruse then did is probably going to be the only best thing the Sprint variant gets. Try it
Click to expand...
Click to collapse
Thanks for your reply. If it is not too much can you please break down the steps a bit more because I don't want to guess and mess it up again and also if you could please kindly point me to the other thread as well so I can download the appropriate stuff from there and read a bit more about it. I am right now unable to use the phone with the sprint firmware on it on TMo, it's super annoying.
Thanks in advance.

https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3572739
Don't mind all the instructions there .
1. Download the flashfire zip file and place it in your phone.
2. Download the Ufirm_multi_carrier.zip and unzip it and place the AP or TaR on your phone(the file that's inside the zip)
3. Make sure to use the eng boot and the root provided in this thread and root your phone.(root is a pain but it's worth doing for this room.)
(Note, if you have flashfire stuck on enumerating partitions you can try rebooting or Google flashfire latest app or flashfire 0.73 app and download and install it)
4. In flashfire allow root permissions and select zip and choose flashfire flashable.zip and select mount system read/write,
5. In flashfire select firmware and select the AP or TaR that you downloaded and it should have all partitions checked. Leave it and press the check mark.
6. Make sure that SuperSU is not injected. MNow click on wipe and select dalvik/cache format cache .
7. The order should be firmware then zip then wipe in flashfire.
8. Click the flash tab at bottom in flashfire.
9. In aroma, select the wipe SuperSU image, I think it's selection 2, and the rest of it is entirely up to you for what carrier you are on and so forth.
There is no need to download the Ufirmware stock for Odin because it won't stick because if the new software you have on your phone. Please make sure you know what you are doing to apply these things. These instructions worked for me and if you choose to do otherwise that's on you. I claim no responsibility for bricked devices or what you create . Flashing is a risk that we all take and it's entirely up to you.
Any more questions I'll be glad to answer. Trying to get the oreo working but having issues.
---------- Post added at 10:49 AM ---------- Previous post was at 09:58 AM ----------
May have been the wrong link sorry here is the correct one:
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3637375

Did you get it sorted out? Hopefully you are on the rom and haven't bricked your device. I attached a picture so you could see that I am on what I say I am on.

epikroms said:
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3572739
Don't mind all the instructions there .
1. Download the flashfire zip file and place it in your phone.
2. Download the Ufirm_multi_carrier.zip and unzip it and place the AP or TaR on your phone(the file that's inside the zip)
3. Make sure to use the eng boot and the root provided in this thread and root your phone.(root is a pain but it's worth doing for this room.)
(Note, if you have flashfire stuck on enumerating partitions you can try rebooting or Google flashfire latest app or flashfire 0.73 app and download and install it)
4. In flashfire allow root permissions and select zip and choose flashfire flashable.zip and select mount system read/write,
5. In flashfire select firmware and select the AP or TaR that you downloaded and it should have all partitions checked. Leave it and press the check mark.
6. Make sure that SuperSU is not injected. MNow click on wipe and select dalvik/cache format cache .
7. The order should be firmware then zip then wipe in flashfire.
8. Click the flash tab at bottom in flashfire.
9. In aroma, select the wipe SuperSU image, I think it's selection 2, and the rest of it is entirely up to you for what carrier you are on and so forth.
There is no need to download the Ufirmware stock for Odin because it won't stick because if the new software you have on your phone. Please make sure you know what you are doing to apply these things. These instructions worked for me and if you choose to do otherwise that's on you. I claim no responsibility for bricked devices or what you create . Flashing is a risk that we all take and it's entirely up to you.
Any more questions I'll be glad to answer. Trying to get the oreo working but having issues.
---------- Post added at 10:49 AM ---------- Previous post was at 09:58 AM ----------
May have been the wrong link sorry here is the correct one:
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3637375
Click to expand...
Click to collapse
First up, thanks a lot for your help. After a lot of tries I managed to root the phone or so I thought and that's what the phone said after I ran the root.bat file on the computer and the phone rebooted. I downloaded the flashfire app but when I turned it on it says "root access could not be acquired, are you rooted ?".
After I ran the root.bat file and the phone rebooted the phone clearly said it was rooted. How do I go ahead now ?

bothambhai said:
First up, thanks a lot for your help. After a lot of tries I managed to root the phone or so I thought and that's what the phone said after I ran the root.bat file on the computer and the phone rebooted. I downloaded the flashfire app but when I turned it on it says "root access could not be acquired, are you rooted ?".
After I ran the root.bat file and the phone rebooted the phone clearly said it was rooted. How do I go ahead now ?
Click to expand...
Click to collapse
Get the root from the thread in the link I provided .
In the file there should be something OS something flash the bat file in there it kills all Sprint stuff. Then do the root.batch file and don't worry when it removes all the SuperSU, flashfire, and so on, it's normal okay do on to the painful part......
In the command screen or terminal, it'll say to press a button when your phone has registered on the PC., this is probably where you are messing up. Watch your computer screen until the s7 pips up and watch your phone when it says Allow, MAKE SURE YOU TAP ALLOW! wait for your phone to click off on the PC and then click back on( it takes a while) then press whatever button you like and watch the terminal, if it has errors then it's not rooted if it is rooted then the terminal will close and your phone will reboot. Then proceed to flashfire and do it's thing. For good measure when your phone is booted open SuperSU app first and you'll know if your rooted. Let me know if you need more help

thats pretty interesting being on the binary 5 baseband and binary 4 rom. to clarify, you were on the binary 5 rom and reverted? or were you on the baseband 4 and upgraded just the baseband? thanks for the info.

epikroms said:
Get the root from the thread in the link I provided .
In the file there should be something OS something flash the bat file in there it kills all Sprint stuff. Then do the root.batch file and don't worry when it removes all the SuperSU, flashfire, and so on, it's normal okay do on to the painful part......
In the command screen or terminal, it'll say to press a button when your phone has registered on the PC., this is probably where you are messing up. Watch your computer screen until the s7 pips up and watch your phone when it says Allow, MAKE SURE YOU TAP ALLOW! wait for your phone to click off on the PC and then click back on( it takes a while) then press whatever button you like and watch the terminal, if it has errors then it's not rooted if it is rooted then the terminal will close and your phone will reboot. Then proceed to flashfire and do it's thing. For good measure when your phone is booted open SuperSU app first and you'll know if your rooted. Let me know if you need more help
Click to expand...
Click to collapse
I odined the AP_Nougat_S7_Edge_EngBoot.tar.md5 then ran the root.bat file from Nougat_S7_Root_2_82_All_Carriers_V2 , I chose the options to install the fingerprint fix and install the root without any gpu tweaks. I watched the whole process complete and the cmd prompt close, my phone never asked my permission to ALLOW anything, everything was on the computer. I ran the root.bat from cmd as an administrator and the program ran evidently because it asked me about the fingerprint fix and root with or without tweaks etc. I noticed the phone reboot and there was a notification, the phone was rooted but no SU and flashwire says no root access. I tried it back from square one a couple of tries more right back from flashing stock sprint firmware and trying the whole rooting process again, same results except the next two times the phone doesn't reboot after running the root.bat file. I notice now when the phone boots up there is a sign saying "CUSTOM" beneath the samsung logo on the screen. I don't know where I am going wrong in the process though. I don't know if it is because I am on the binary 5 however I also read somewhere that people have been successful in rooting their binary 5 sprint S7 edges. I have rooted many devices before and installed roms etc, this has been, by far, the most perplexing phone in every which way.

Fownt know what to say,but, you are saying that you are on binary 5 and have successfully downgraded bootloader's by flashing stock vzw firmware which is on binary 4? I don't think downgrading is possible yet?? The way I explained it to you is exactly how I did mine numerous times. I can no longer assist you though because, I kinda bricked my s7edge,
Here's something for everyone to note on a DONT DO!!!!
Do not flash the latest ENG_BOOT AND COMBO FIRMWARE.
I think it was the binary 5 QK1 eng boot and combo I forget, but after flashing back to stock firmware you will get a SBL ERROR in upload mode and let me tell you....... It is not fun at all. I had all the files necessary for unbricking, the complete restore files, I tried the z3x box, I tried octoplus, and I tried the uni-android tools and nothing flashes it over. It's insane. But I ended up sort of destroying the body of the phone but not the internal, so I now have a skeleton phone and no screen or mid frame.
So I wish you luck and probably a final goodbye to Samsung and their insaniy with phones.

epikroms said:
Fownt know what to say,but, you are saying that you are on binary 5 and have successfully downgraded bootloader's by flashing stock vzw firmware which is on binary 4? I don't think downgrading is possible yet?? The way I explained it to you is exactly how I did mine numerous times. I can no longer assist you though because, I kinda bricked my s7edge,
Here's something for everyone to note on a DONT DO!!!!
Do not flash the latest ENG_BOOT AND COMBO FIRMWARE.
I think it was the binary 5 QK1 eng boot and combo I forget, but after flashing back to stock firmware you will get a SBL ERROR in upload mode and let me tell you....... It is not fun at all. I had all the files necessary for unbricking, the complete restore files, I tried the z3x box, I tried octoplus, and I tried the uni-android tools and nothing flashes it over. It's insane. But I ended up sort of destroying the body of the phone but not the internal, so I now have a skeleton phone and no screen or mid frame.
So I wish you luck and probably a final goodbye to Samsung and their insaniy with phones.
Click to expand...
Click to collapse
Bummer about your phone. On a glad note I managed to root and flash my phone and everything works great now. I was taking the hard nerdy way to do it by running cmd as an administrator and having that run the root.bat file. I read somewhere else you could just double click the file and it worked for me . From there on the aroma part was pretty straightforward. I am grateful to you for pointing me in this direction and breaking it down for me, I seriously doubted me being able to achieve this on my binary 5 phone but it turned out to be smooth.
I do wish you the best and thanks once again.