[Q] Flashing Root de la Vega from a Mac using Heimdall? - Galaxy Note 3 Q&A, Help & Troubleshooting

I can't get Windows to install on Boot Camp for some reason (keeps saying "no image available to install" after I choose languages etc) and I understand running Knox from Windows in a VM isn't a great idea (if that's OK, then please let me know and I'll do that!) I can use the Windows VM to prep the URDLV files in advance, of course.
I've searched, but the only instructions I could find are in http://forum.xda-developers.com/showthread.php?t=2475262 which deals with flashing the recovery and, presumably, tripping Knox.
I don't want to risk bricking a brand new phone by using trial and error, obviously — could somebody please post a set of instructions on how to flash the URDLV files using Heimdall?
Thanks

Tiny Clanger said:
I can't get Windows to install on Boot Camp for some reason (keeps saying "no image available to install" after I choose languages etc) and I understand running Knox from Windows in a VM isn't a great idea (if that's OK, then please let me know and I'll do that!) I can use the Windows VM to prep the URDLV files in advance, of course.
I've searched, but the only instructions I could find are in http://forum.xda-developers.com/showthread.php?t=2475262 which deals with flashing the recovery and, presumably, tripping Knox.
I don't want to risk bricking a brand new phone by using trial and error, obviously — could somebody please post a set of instructions on how to flash the URDLV files using Heimdall?
Thanks
Click to expand...
Click to collapse
Watch "How to Use Heimdall on Mac OSX to Install Kernels and ROMs!" on YouTube
https://www.youtube.com/watch?v=R7u-iUo5C6M&feature=youtube_gdata_player
Don't know if this will help at all

jaythenut said:
Watch "How to Use Heimdall on Mac OSX to Install Kernels and ROMs!" on YouTube
https://www.youtube.com/watch?v=R7u-iUo5C6M&feature=youtube_gdata_player
Don't know if this will help at all
Click to expand...
Click to collapse
Thanks — that's sorted it. I now have root.
Seem to have broken wifi and camera, though, but that's another thread…
For anyone else who passes this way with the same problem, here's what I did:
First time only
Click Detect on the Utilities tab in Heimdall and check the device is detected.
Download the PIT just below and keep in a safe place.
Restart the phone into download mode again. Downloading the PIT seems to stop subsequent downloads from working without a restart.
For each firmware you want to flash
Untar the Vega files
Code:
tar xvf whatever.tar.md5
.
In Heimdall, go to the Flash tab and load the PIT you saved earlier.
Click Add under Partitions. Change the Details type to CACHE and use Browse to load the cache.img.ext4 you extracted earlier.
Repeat the above step but using SYSTEM to load the system.img.ext4 you extracted.
Make sure Repartition is not turned on!
Click the Start button.
Wait for your phone to reboot.

Related

[HOW-TO] Flashing RotoHammers ROM on Out of the Box AT&T Galaxy TAB

MY ORIGINAL QUESTION:
Does Flashing Straight to RotoHammers ROM on AT&T Tab Add Phone Capabilities?
I''m confused between this posting
http://forum.xda-developers.com/showthread.php?t=895827
and this one
http://forum.xda-developers.com/showthread.php?t=847273
Whats the most current way to get phone capabilities on the AT&T Tab?
Also what is a bootstrapper?
'===========================================================
UPDATE:
For any newbies out there here is the procedure
1. Download Android Sideload Wonder Machine, enable debugging mode, & Sideload z4Root on your AT&T out of the box device. (no ADB knowledge required)
2. Run z4Root Permanent Root
3. Download Root Explorer & Zip System/efs folder , mount your device to USB and keep the zip file on your PC in a safe place
4. Follow the quick tutorial on how to flash the ROTOHAMMER.
http://forum.xda-developers.com/showthread.php?t=895827 ( Just Flash RotoHammer's JME v4 Full .tar via the PDA instead of the file name shown in the screenshot)
http://forum.xda-developers.com/showthread.php?t=894763
6. Once you've reboot your at&t device should now have the Rotohammer Firmware.
7. Enable debugging on the device again.
8. Run RotoHammers script to unlock
http://forum.xda-developers.com/showthread.php?t=843323
You are in Business. If you have any questions shoot me a PM I'll be glad to help.
The only side effect I have right now is that for some reason when I boot my device I do not see the Samsung Boot Screen or Recovery Mode
9. To fix this side effect flash with odin (PDA and NO Repartition) the JJ4 Bootloaders posted by Rotohammer here: http://forum.xda-developers.com/attachment.php?attachmentid=496999&d=1295722186
Flash Roto-JME version 4 following the steps. You will have a phone icon. The best At&t modem is the bell i900. Besides Roto's pit, pda, and phone files, you will need Odin3 1.7.
I also unlocked it using Roto's instructions, so I can use a t-mobile sim card for EDGE data and voice.
I rooted it with z4root.
It was very easy.
Just read everything a few times, and come back here if you're not sure. Good luck.
Yes. I had a basically stock att tab, I followed the first url you put in your post, it just worked.
After the flash, voice service was working as was 3g/3.5g data.
If you review several of the related posts and watch the video, and review the first url, you'll see they are all doing a very similar thing. I started 'simple' by doing the super one click root thing followed by a rotoBAK just to learn abit and develope some confidence. After a day or two, I flashed away.
http://en.wikipedia.org/wiki/Booting#History
Love that reference, but here's the good part:
Wikipedia said:
The computer word boot is short for "bootstrap" (itself short for "bootstrap load"). The term bootstrap derives from the idiom pull oneself up by one's bootstraps. The term refers to the fact that a computer cannot run without first loading software but must be running before any software can be loaded, which seems as impossible as to "pull yourself up by your own bootstraps."
Click to expand...
Click to collapse
i am still not following when it comes to taking a tab and using a tmobile sim card on an att network. edge is att, right? How would you get a SIM card from tmobile?
I am looking to buy a tmobile tab and am trying to figure out the best way of getting phone service. I NEED it to work as a phone, so working out the logistics is paramount. I am still learning, so any info would help.
Can someone repeat the step by step for both unlocking the device & adding ATT voice calling capabilities, with the latest and most current files.
thanks
Jeepsdaddy said:
Can someone repeat the step by step for both unlocking the device & adding ATT voice calling capabilities, with the latest and most current files.
thanks
Click to expand...
Click to collapse
Not necessary! Just take your time to read and learn. Doing these things without doing your own studying is dangerous!
rangercaptain said:
Not necessary! Just take your time to read and learn. Doing these things without doing your own studying is dangerous!
Click to expand...
Click to collapse
I am all set. Unlock + Rooted + Roto Hammer...
For any newbies out there here is the procedure
1. Download Android Sideload Wonder Machine, enable debugging mode, & Sideload z4Root on your AT&T out of the box device.
2. Run z4Root Permanent Root
3. Download Root Explorer & Zip System/efs folder , mount your devide to USB and keep the zip file on your PC in a safe place
4. Follow the quick tutorial on how to flash the ROTOHAMMER.
http://forum.xda-developers.com/showthread.php?t=895827
5. The screen will turn black. Dont Worry. Go back into download mode uncheck Re-Partition & Flash RotoHammer's JME v4 Full .tar via the PDA
http://forum.xda-developers.com/showthread.php?t=894763
6. Once you've reboot your at&t device should now have the Rotohammer Firmware.
7. Enable debugging on the device again.
8. Run RotoHammers script to unlock
http://forum.xda-developers.com/showthread.php?t=843323
You are in Business. If you have any questions shoot me a PM I'll be glad to help.
The only side effect I have right now is that for some reason when I boot my device I do not see the Samsung Boot Screen.
Glad to see the flash worked for you! Your directions seem good. You did do a lot of steps that could be streamlined. I did the partition and firmware application in one step in odin. And using the v4 rotojme; it was rooted upon reboot. I did root the stock firmware, to get a backup. But I don't think this a prerequsite to the jme flash.
I too am missing the samsung startup screen.
But good to see it worked for you.
Question: does the protected bootloaders issue affect this process? I'd like to flash my tab (stock Rogers) to enable the phone capabilities.
You can avoid the whole sideload wonder machine by just using this command in adb: adb install z4root.apk
Also, you should be able to do the entire flashing process in one go - not two.
Your probably right about only need to flash straight to V4.
As per this post:
http://forum.xda-developers.com/showthread.php?t=894763
NO -- JMEv4 has no boot loader.
fwelland said:
I too am missing the samsung startup screen.
Click to expand...
Click to collapse
On another Roto thread this was discussed. Usually you have a black screen and a very thin white line. You wait a few minutes and everything is normal. The cause was given as going from stock to Roto Firmware, with the full wipe and re-partition.
fwelland said:
As per this post:
http://forum.xda-developers.com/showthread.php?t=894763
NO -- JMEv4 has no boot loader.
Click to expand...
Click to collapse
Uh what are you talking about? I went from stock to JMEv4 just fine.
Can I flash it using heimdall ?
fcarmona said:
Can I flash it using heimdall ?
Click to expand...
Click to collapse
I try this:
[email protected]:~/Roto$ heimdall flash --repartition --pit P1_add_hidden.pit --factoryfs factoryfs.rfs --cache cache.rfs --dbdata dbdata.rfs --param param.lfs --kernel zImage --modem modem.bin
and respond this:
If you wish to repartition then factoryfs, cache, dbdata, primary and secondary
bootloaders, param, kernel and a PIT file must all be specified.
which files do I need use in primary, secondary and bootloaders
Fixed boot screen & missing recovery mode issue. See opening post. These files are from the trusted Rotohammer.
Thanks
Thanks for the detailed procedure to flash...
and thanks Roto for the packaging!
I successfuly flashed my Bell Galaxy Tab from stock with the V4 Full!
No problem regarding the boot screen for me!
Great job guys!

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.

Can't flash, can't root, can't sleep

I have been at this for a week now. I've tried Heimdall 1.1.1, 1.3.2, AND Odin3 v1.83, v1.85, to reflash the stock Verizon firmware on my Galaxy Tab SCH-i800. I was an idiot and flashed U.S. Cellular firmware, which changed the boot animation and the cell service text. I've scoured the internet on how to do this and everything I've tried has failed. With Heimdall, whenever I plug in the stock files to the program (in 1.1.1 only, I can't figure out 1.3.2 for the life of me) and hit Start, I get "Failed to access device. Error: -12" I'm getting my files from SCH-I800_VZW_stock.zip, it's been extracted. When trying to flash a .tar file with Odin, it works successfully, then my phone goes into bootloop. I can get back to Download mode, but every time I try flashing a stock .tar, I get the same results. I'm starting to go crazy. Anyone help?
maybe you have missed with your partions? if so, i think you need a specific pit file for this stock rom, i dont know where it is, but you might start looking for it.
edit : look in this thread, you might find it useful http://forum.xda-developers.com/archive/index.php/t-940046.html
and this is also important http://theunlockr.com/2012/06/28/ho...axy-tab-sch-i800-back-to-stock-and-unroot-it/
last one http://gizmoninja.com/2011/04/how-to-root-latest-samsung-galaxytab-verizon-update-ec02/
best regards ^_^
Sifou
chrispysaid said:
....With Heimdall, whenever I plug in the stock files to the program (in 1.1.1 only, I can't figure out 1.3.2 for the life of me) and hit Start, I get "Failed to access device. Error: -12"
Anyone help?
Click to expand...
Click to collapse
Did you properly install the Samsung drivers on your PC using the heimdall utility? And you put your Tab in download mode?
The Problem may lie with youe Heimdall setup.
Make sure you have Keis installed. Then make sure you activate the drivers for Heimdall.
This is a great rom to flash to your VZW Tab. follow this thread http://forum.xda-developers.com/showthread.php?t=1325469

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

Categories

Resources