Database Develop

[RECOVERY] ClockworkMod Recovery for Galaxy S (Beta 2!)

WARNING: You must be comfortable using Odin when flashing this. It is very difficult to brick using Odin, but I don't want to handhold people through fixing their devices.
This is Clockwork Recovery beta 2, it is tailored for the Vibrant. Please let me know how it works.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Recovery/Boot TAR download (do NOT extract):
http://koush.tandtgaming.com//test/package1279903787.tar
3e106a2a8828158d334fb70e4874907a
Initramfs source: http://github.com/koush/i9000-leshak-initramfs/tree/koush
Installation instructions:
Install Odin3 v1.0 (MAKE SURE THIS IS THE VERSION YOU USE)
Start Odin3
Press PDA
Select the tar file (do NOT extract)
Start phone into download mode.
Press START to flash.
After 20 seconds or so, phone should automatically reboot.
Please join #koush on irc.freenode.net to report bugs. I can't check all 4 XDA threads

Works for me...but so did the first one...so I guess risk may still remain for others.

Ok so I started ODIN, put my phone into download mode, and opened up the new PDA file.
Now my Odin has been stuck on this message for the last 10 mins.
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> zImage
And my phone is still in download mode. I don't wanna pull the wire or turn the phone off and mess something up hehe.
Also was I suppose to load the .pit file into odin too?

sxfx said:
Ok so I started ODIN, put my phone into download mode, and opened up the new PDA file.
Now my Odin has been stuck on this message for the last 10 mins.
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> zImage
And my phone is still in download mode. I don't wanna pull the wire or turn the phone off and mess something up hehe.
Also was I suppose to load the .pit file into odin too?
Click to expand...
Click to collapse
Yes, when flashing you always need to load the PIT file. I use 512 as it doesnt cause as many problems. Try to hit reset on odin and load the pit file and flash again...As long as you didn't have repartition clicked you should be fine. And without the PIT file it prob didn't even flash anything.

sxfx said:
Ok so I started ODIN, put my phone into download mode, and opened up the new PDA file.
Now my Odin has been stuck on this message for the last 10 mins.
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> zImage
And my phone is still in download mode. I don't wanna pull the wire or turn the phone off and mess something up hehe.
Also was I suppose to load the .pit file into odin too?
Click to expand...
Click to collapse
It'll also stay like that if you forget to check "Force Reboot".

While this didn't brick my phone...it made my brand new out of the box vibrant to where it doesnt boot the stock firmware. Thought it was working fine, but spoke too soon. And now it just boots back to the battery indicator everytime. Nothing a new flash can't fix, but just saying for feedback purposes.
****Edit****
Phone just randomly booted....it seems to be acting erraticly...not sure what the difference that caused the phone to start booting.

Same as fykick if I leave the usb plugged in. If I take the usb out and turn it on it gets to the lock screen and then reboots, continuously.
Edit:
Did a wipe and rebooted the phone a couple of times and now it is running ok

Worked for me, although navigation keys are somewhat strange, have to press vol down key to go up
Have tried to do nand backup, have got md5 checksum error

stillyone said:
Worked for me, although navigation keys are somewhat strange, have to press vol down key to go up
Click to expand...
Click to collapse
Yeah, until the recovery is specifically written for the Vibrant, it still contains the keymappings of the INTL version where the volume buttons are flipped.

Now started to get kernal panic...tried reflashing couple more times ...same thing

I can now boot into clockwork recover, but my phone keeps crashing, I've tried resetting everything, but I get continuous errors like:
Sorry! The process com.android.phone has stopped unexpectedly.
I get them every few seconds. Sometimes the error is for web other times media. These pop up over and over and don't let me do anything. Any ideas?

I was successful in flashing clockwork and successfully created a nandroid.
There were however issues that were present with the 1st build. The phone would loop reboot if the SD card was inserted. If removed the phone would boot and stay functional, however once the card was inserted it would reboot loop again within a couple min. Had "force closes" on the market and file manager.
Oh and the only other thing was the "Home" button acted as a back button.
I posted these on the irc channel Koush, but I do not believe you were in there at the time.
For those of you having huge issues, following this should set you straight.
http://forum.xda-developers.com/showthread.php?t=728698

I'm such an idiot, I tried fixing my phone by flashing it to a stock rom (after repreated crashing after install Clockwork recovery today), not realizing that it was a Captivate rom, and now all my Vibrant will do is load an AT&T World Phone screen over and over. I used the one click Odin/Rom thing from the Captivate forum (obviously not realizing that's where I had ended up).

out of curiousity where is everyone getting this 512 pit file? the only pit file i have is the one that came with odin but it is 513
ok answered my own question....use search first
sorry

kelmerp said:
I'm such an idiot, I tried fixing my phone by flashing it to a stock rom (after repreated crashing after install Clockwork recovery today), not realizing that it was a Captivate rom, and now all my Vibrant will do is load an AT&T World Phone screen over and over. I used the one click Odin/Rom thing from the Captivate forum (obviously not realizing that's where I had ended up).
Click to expand...
Click to collapse
Check out the link in the post above yours. Should help with your issue. Good luck.

Yes, it did, thanks. Back to a stock-ish ROM. Will retry Clockwork later today once my heart starts beating again... Modding my new baby is like a rollercoaster ride.

kelmerp said:
Yes, it did, thanks. Back to a stock-ish ROM. Will retry Clockwork later today once my heart starts beating again... Modding my new baby is like a rollercoaster ride.
Click to expand...
Click to collapse
No point in trying until he releases an new one. The others will just put you right back were you were before.

I have odin v4.03 from flashing behold II roms wondering if this is the corect version since some of these posts mention odin3. thanks

will clockwork recovery wipe every folder on the phone? or will the /sdcard folder remain? (I believe the /sdcard is the phones memory ~16gb) thanks

Pancake345 said:
will clockwork recovery wipe every folder on the phone? or will the /sdcard folder remain? (I believe the /sdcard is the phones memory ~16gb) thanks
Click to expand...
Click to collapse
In a standard wipe it does not touch sd storage.

[OTA][11/24][SCH-I705] Verizon GTab 2 7" - J1 OTA Update - Pre-Rooted!

This the G3 to J1 OTA. A lot of people are still on the G3 build because of root issues. As some of you may have found out, the hard way, the J1 update does not allow the older root methods and a new method has not been found forcing people to not accept the OTA! This fixes that!
What I have done here is grab the OTA and neutered it so it would not install the "aboot" and not install the "recovery" partitions. On top of that I have pre-rooted it with the latest SuperSU and added my unsecure boot.img. So you get the following...
Features
New Radios / Appropriate firmware
New Kernel
OS changes from G3 to J1
Root will now be in the /system folder so if you wipe data root is still with you :highfive:
You must be on the 100% stock G3 base with root and Clockwork MOD Recovery. If you modified any files you need to restore them because the script checks the files on the /system partition to make sure it has not been tampered with! For example if you installed Gmail from the 4.2 build the script will error out and NOT flash!
If you need to return to stock G3 Base you can do it easy this way: http://forum.xda-developers.com/showthread.php?t=1885558. Thats what I had to do to root the tab so I know for a fact the OTA works 100% off the dump that MrHyde03 made!
Now for the official instructions
Instructions:
Must be at full stock G3 base with no modifications to the system files other than root!
Must have CWM recovery installed, must have the unlocked boot loader installed.
Uninstall Superuser (Yes, uninstall it!)
Copy Patch to Device
Reboot to recovery
Flash Patch. Takes about 3 to 4 minutes to patch.
Profit!
Thanks
Thanks out to MrHyde03 and RevosFTS for testing. Brave souls!
And thanks to other few people who tried but modified the system image therefore could not flash.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DOWNLOAD: HERE
MD5: 6FA20263C6DC961C7F3DFCE554D0BC9A
Please hit Thanks!​

Reserved

Excellent. Also added a reference to here in the root thread under Step 3.

I've been working with scott trying to flash this update..
I fixed the issue with the gmail 4.2 that I put on my tab.. so that is no longer an issue.. (and that was the only thing I changed in my /system partition)..
Now I'm getting an error status 7... with "assert failed: apply_patch_check (" /system/bin/debuggerd")".. when flashing this... not sure what that is? anyone know?
also I'm on the g3 build
Baseband Version: I705VRLG3
Build Number: IMM76D.I705VRALG3

Sounds to me like it's not finding the file at /system/bin/debuggerd. Open root explorer or equivalent and check to see if that file exists. If not, then I'd go through Step 1b (Method 2 - ODIN) on the root thread again to ensure your system is 100% stock.

nexttonomy said:
I've been working with scott trying to flash this update..
I fixed the issue with the gmail 4.2 that I put on my tab.. so that is no longer an issue.. (and that was the only thing I changed in my /system partition)..
Now I'm getting an error status 7... with "assert failed: apply_patch_check (" /system/bin/debuggerd")".. when flashing this... not sure what that is? anyone know?
Click to expand...
Click to collapse
This
|
|
\/
MrHyde03 said:
Sounds to me like it's not finding the file at /system/bin/debuggerd. Open root explorer or equivalent and check to see if that file exists. If not, then I'd go through Step 1b (Method 2 - ODIN) on the root thread again to ensure your system is 100% stock.
Click to expand...
Click to collapse
Agreed. This OTA tested perfect against your Odin stock so if there is an issue when someone tries to flash then they are not 100% stock system hence a quick odin flash will take care of that!

scrosler said:
This
|
|
\/
Agreed. This OTA tested perfect against your Odin stock so if there is an issue when someone tries to flash then they are not 100% stock system hence a quick odin flash will take care of that!
Click to expand...
Click to collapse
Ok.. I'll do that and try it out again... thanks for the help hyde and scott
EDIT: is this ok to do even though I'm already on G3? also do I need to unlock the bootloader and flash cwm again after doing this?
EDIT 2: I have all the drivers installed and adb recognizes my tab.. but everytime I try to flash this file via ODIN it fails.. this is the error message I get:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> system.ext4.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
EDIT 3: So I checked my /system/bin folder and I have two debuggerd files...
debuggerd which is 364 Bytes
debuggerd.bin which is 29.95K
Do you guys have both these files?

nexttonomy said:
Ok.. I'll do that and try it out again... thanks for the help hyde and scott
EDIT: is this ok to do even though I'm already on G3? also do I need to unlock the bootloader and flash cwm again after doing this?
EDIT 2: I have all the drivers installed and adb recognizes my tab.. but everytime I try to flash this file via ODIN it fails.. this is the error message I get:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> system.ext4.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Did you verify all antivirus and firewall programs on your computer are disabled?

Im thinking locked bootloader?
Did you flash the "aboot" like in Hydes thread?
I think its step #3 or 4?

Love it! Looking forward to more of your work.

Warren87 said:
Love it! Looking forward to more of your work.
Click to expand...
Click to collapse
Worked for ya?

Im on an unlocked bootloader... the samsung splash screen is less than a second like it says in mrhydes thread... but I flashed it again just to make sure...
I've been flashing this stuff since the OG droid.. I'm not a noob on this... i'm not sure what is going wrong..
I appreciate all the help.. I'll just keep playing with it to see if I can figure it out

nexttonomy said:
Im on an unlocked bootloader... the samsung splash screen is less than a second like it says in mrhydes thread... but I flashed it again just to make sure...
I've been flashing this stuff since the OG droid.. I'm not a noob on this... i'm not sure what is going wrong..
I appreciate all the help.. I'll just keep playing with it to see if I can figure it out
Click to expand...
Click to collapse
Hmmm. Odd.
The only time I got that messaage was when the bootloader is locked. I dont know then.
Let us know if you figure it out...
Also can you confirm the status of the current build you are on? And did you try a newer version of Odin? Maybe its just an Odin issue. What ver are you on?

scrosler said:
Hmmm. Odd.
The only time I got that messaage was when the bootloader is locked. I dont know then.
Let us know if you figure it out...
Also can you confirm the status of the current build you are on? And did you try a newer version of Odin? Maybe its just an Odin issue. What ver are you on?
Click to expand...
Click to collapse
Odin 3.04 is the version I use and have listed in the instructions. Think it could have something to do with your extra compressed version?
Try downloading the first link again and make sure your using the PDA section. You could even try running Odin "Run as administrator". Also can try rebooting your computer (had a similar issue a while back and a reboot of both my laptop and tablet solved it. Shut down your tablet completely then boot directly into Download (power + vol down). Plug it in AFTER it boots into Download and let us know.

MrHyde03 said:
Odin 3.04 is the version I use and have listed in the instructions. Think it could have something to do with your extra compressed version?
Try downloading the first link again and make sure your using the PDA section. You could even try running Odin "Run as administrator". Also can try rebooting your computer (had a similar issue a while back and a reboot of both my laptop and tablet solved it. Shut down your tablet completely then boot directly into Download (power + vol down). Plug it in AFTER it boots into Download and let us know.
Click to expand...
Click to collapse
No, its the not the file...
<OSM> Checking MD5 finished Sucessfully..
If it was that would have failed.
I am more than sure this is due to some sort of write protection.

Should I still be receiving the OTA install warnings after flashing this? I'm going to freeze SDM for now.

JelloB said:
Should I still be receiving the OTA install warnings after flashing this? I'm going to freeze SDM for now.
Click to expand...
Click to collapse
No, but what you need to do is tell it to check again and it will come back and say that it is already installed and there is no update.

scrosler said:
No, but what you need to do is tell it to check again and it will come back and say that it is already installed and there is no update.
Click to expand...
Click to collapse
I originally postponed it for an hour and then froze SDM. When I unfreeze and go into software update it only gives me the option to install deferred update now.
I'm not terribly concerned about this because I can just leave it frozen but it's curious that I'm receiving the update. All of my software matches those listed on your screenshot above.

JelloB said:
I originally postponed it for an hour and then froze SDM. When I unfreeze and go into software update it only gives me the option to install deferred update now.
I'm not terribly concerned about this because I can just leave it frozen but it's curious that I'm receiving the update. All of my software matches those listed on your screenshot above.
Click to expand...
Click to collapse
You have to ignore it then Select "Check Now"
That's what I had to do... Either that or do a factory reset. I know that will fix it for sure :angel:
And if you did let it go it would just fail immediately so no worries.

Ok cool. I'll check it after the original hour deferment expires and if I have to I'll factory reset.
Thanks for your work on this. Looking forward to future installments.

[GUIDE]Update Samsung Galaxy Music Duos S6012 to Jelly Bean 4.1.2 AND Root it

UPDATE YOUR SAMSUNG GALAXY MUSIC DUOS to OFFICIAL JELLY BEAN 4.1.2
Samsung has started rolling out the long-rumored but never officially-confirmed Jelly Bean update for the Samsung Galaxy Music Duos. Right now, it has been released only for Greece/Baltic region, but users around the world can easily download it and flash their devices.
Below find a complete step-by-step tutorial to update your Samsung Galaxy Music Duos S6012 to Jelly Bean 4.1.2:
[STANDARD DISCLAIMER: THIS IS A FAIRLY EASY GUIDE TO FOLLOW AND YOU SHOULD HAVE NO PROBLEMS UPGRADING YOUR PHONE. HOWEVER, PLEASE NOTE THAT I AM NOT RESPONSIBLE IN THE EVENT THAT SOMETHING GOES WRONG AND/OR YOU 'BRICK' YOUR DEVICE.]
First off, download the following files
ODIN 3.07: https://www.copy.com/s/wSEoPPbzYXmF/AndroidJinn.com_Odin307.zip
Samsung Firmware: NEW: GET THE LATEST (Jan 2014) 4.1.2 SAMSUNG FIRMWARE FOR EUROPE (GREECE) FROM HERE
METHOD TO INSTALL ON YOUR PHONE REMAINS THE SAME
EXTRACT BOTH THESE FILES TO YOUR DESKTOP. YOU SHOULD NOW HAVE TWO NEW FOLDERS ON YOUR DESKTOP.
HOW TO UPDATE:​
Step 1:
Turn off your phone. Wait a few seconds, the phone will vibrate to confirm that it is fully switched off. Connect your Galaxy Music S6012 to a USB port on your PC using the ORIGINAL SAMSUNG USB cable that came with your device.
Step 2:
Go to Odin3 v3.07.exe that you have previously extracted into a folder on your desktop. Right click, and 'Run as Administrator.'
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 3:
Now, press and hold three buttons at the same time: Volume Down + Home + Power button TOGETHER until you see the following warning message:
Press Volume Up button again to enter into Download Mode. Now your phone's screen will show this:
On the computer, you will see 'Added' in Odin’s message box:
You should also see COM port with a number highlighted in Blue if you successfully added your device. (Com 15 in my case)
NOTE: If you don’t get 'Added' then it means you do not have USB drivers installed for your device. Download from here. Install the drivers and try again. If it still does not detect the phone try another USB port or another USB cable.
Step 4:
In the Odin Window, click the PDA Button, and select the .tar.md5 file from the folder where you had previously extracted the Samsung firmware.
Step 5:
In Odin window, make sure Auto Reboot and F. Reset Time checkboxes are only two that are ticked.
Step 6:
Now, to begin the flashing process, hit the START button. The top left box in the Odin window will turn green and the flashing process will start.
On your phone it will look something like this:
Step 7:
After installation of the system your phone will reboot automatically and you will see a PASS message in the top left box of Odin.
You can now safely unplug your device from computer.
Your Galaxy Music S6012 should now upgrade its apps.
When it starts up, it should run Android 4.1.2 Jelly Bean
Go to Settings > About phone to verify.
Congratulations! You now have your Samsung Galaxy Music Duos running on OFFICIAL Jelly Bean!
Note: If you were rooted before, you will have to root again and re-delete the system apps you may have deleted earlier.Your other apps, system settings and files will still be there.​

NOW
ROOT
YOUR SAMSUNG GALAXY MUSIC S6012 JELLY BEAN 4.1.2​
Now that you are enjoying the Jelly Bean goodness,
its time to root your phone so that you can remove all the bloatware,
make it faster and smoother, and customize the look and feel
to your heart's content.
NEW: ROOT THE LATEST (JAN 2014) SAMSUNG OFFICIAL 4.1.2 FIRMWARE FOR GREECE THROUGH THE METHOD PROVIDED BY @saikiransama DETAILED BY HIM HERE
* Thanks to mattanur for discovering the below method*
STEP 1​
Download and unzip Cydia Impactor to a folder on your desktop.
STEP 2​
Enable Developer Options on your phone, if you haven't already done so.
To enable it, click on Settings>About Device and scroll down till you see the "Build number".
Now keep tapping continuously on the Build number
till you see some messages on the screen counting down to enable the Developer options.
After a while, you will see a message informing you that the "Developer mode" is enabled.
Now turn on USB-debugging. Settings>Developer Options>OK>Tick USB debugging
STEP 3​
On your computer, run Cycia Impactor (all the files from the zip should be in the same folder). It will look like this:
STEP 4​
Click on the 'Start' button in Cydia. Wait till the program finishes running.
STEP 5​
Install SuperSU app from Google Play. Open it. Click on 'Continue' when it asks to update binaries.
You're done! Now you can test your phone with the root checker app to make sure it is rooted.
Enjoy!​

Thanks. Works.
I'm from India. This thing works. Thanks.

Apourv said:
I'm from India. This thing works. Thanks.
Click to expand...
Click to collapse
Hello , Instead of waiting for official update and update via this method will i void my warrenty ?

KiranP23 said:
Hello , Instead of waiting for official update and update via this method will i void my warrenty ?
Click to expand...
Click to collapse
No, because this is official firmware from Samsung, only it is not for your region.
It does not increase your flash counter either, so you are perfectly safe. In case you need to give it for warranty or something, just flash your original firmware version again (which is also available from the same site you will get the new one from).
Check your firmware version in Settings>About phone and then download the firmware from here http://samsung-updates.com/device/?id=GT-S6012

itsnotmeatall said:
No, because this is official firmware from Samsung, only it is not for your region.
It does not increase your flash counter either, so you are perfectly safe. In case you need to give it for warranty or something, just flash your original firmware version again (which is also available from the same site you will get the new one from).
Check your firmware version in Settings>About phone and then download the firmware from here http://samsung-updates.com/device/?id=GT-S6012
Click to expand...
Click to collapse
thank you , updated
for others these are the messages Odin shows while flashing
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S6012XXUBME2_S6012OXXBME2_S6012XXUBME2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin.md5
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img.md5
<ID:0/003> recovery.img.md5
<ID:0/003> BcmCP.img.md5
<ID:0/003> system.img.md5
<ID:0/003> dt-blob.md5
<ID:0/003> param.lfs.md5
<ID:0/003> cache.img.md5
<ID:0/003> hidden.img.md5
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

9441Rahul9441 said:
unable to root after updating my s6012
sorry for pm i was unable to post on thread
:crying: :crying::crying:
Click to expand...
Click to collapse
Which method did you try to root with?

cybercuate said:
Hi
I have a Galaxy Music Duos GT-S6012b (region from Brazil)
with:
Android
4.0.4
Base band
S6012BVJLJ3
Kernel
3.0.15-1150912
Compilation number
IMM76D.S6012BVJALJ3
I want to update to 4.1 following your tutorial & I just want to know if is it safe to do it to my cell model?
I mean it is s6012B not only s6012...
your post is awesome & I'd like to try it but please what do you say about this...
Click to expand...
Click to collapse
cybercuate said:
I've followed your tutorial and my phone just keep boot looping
it says PASS! in odin but the phone is bricked I think
it wasnt rooted, just everything original
Click to expand...
Click to collapse
Do a factory reset:
Start your phone by pressing Home+Volume up+Power and you will get the recovery menu. In recovery mode you can use Volume keys to navigate between options and Power key to select an option. Do Wipe data/Factory Reset as well as Wipe Cache Partition before selecting reboot system now.
Now try to start your phone normally. (You will still have Jelly Bean)

cybercuate said:
itsnotmeatall said:
cybercuate said:
I've followed your tutorial and my phone just keep boot looping
it says PASS! in odin but the phone is bricked I think
it wasnt rooted, just everything original
Click to expand...
Click to collapse
Do a factory reset. Start your phone by pressing Home+Volume up+Power and you will get the recovery menu. In recovery mode you can use Volume keys to navigate between options and Power key to select an option. Do Wipe data/Factory Reset as well as Wipe Cache Partition before selecting reboot system now.
Now try to start your phone normally.
Click to expand...
Click to collapse
I did it!!!
I'm running 4.1.2 from ZTA region
Thanks anyway
Click to expand...
Click to collapse
:victory::victory::victory:

Could you please upload it on some torrent or some other website like mediafire(dot)com ?
Tried downloading from the site but failed between 300 - 350 mb twice

rahulsinha said:
Could you please upload it on some torrent or some other website like mediafire(dot)com ?
Tried downloading from the site but failed between 300 - 350 mb twice
Click to expand...
Click to collapse
I have not uploaded, these are collected and uploaded by samsung-updates.com. Try download manager like flashget, internet download manager etc, these will resume your downloads even after they get interrupted. It is not safe to download roms from torrent or mediafire, 4shared etc.

itsnotmeatall said:
I have not uploaded, these are collected and uploaded by that site. Try download manager like flashget, internet download manager etc, these will resume your downloads even after they get interrupted. It is not safe to download roms from torrent or mediafire, 4shared etc.
Click to expand...
Click to collapse
Ohh... alright. Thanks for the info.

jeansebas said:
hey men i've seen your post about updating the galaxy music duos. but i have a problem rooting with the impactor method (when i hit the start button it says "signature bugs unavailable")
can you help me please?
Click to expand...
Click to collapse
Are you rooting the ICS build or the JB build? AFAIK the Impactor method works with the JB build.

Guys any CWM for this phone??

wrick17 said:
Guys any CWM for this phone??
Click to expand...
Click to collapse
AFAIK, no.
No TWRP either.

After the update, when someone makes a call to my phone, the screen shows black with only the receive reject and message buttons.. It neither shows the photo nor the phone number, can't even determine who's calling.. after i receive the call everything is so normal.... any help ??

wrick17 said:
After the update, when someone makes a call to my phone, the screen shows black with only the receive reject and message buttons.. It neither shows the photo nor the phone number, can't even determine who's calling.. after i receive the call everything is so normal.... any help ??
Click to expand...
Click to collapse
There are 3 things you can try in this order:
1. Clear the Contacts and Contacts Storage data (under Applications Manager>All) and resync your contacts with your google account.
2. Try wiping cache from recovery menu to see if it solves the problem.
3. Factory reset the phone (backup your apps, and data using ES Explorer or Titanium Backup first so you can restore your data and apps quickly.)

jeansebas said:
itsnotmeatall said:
jeansebas said:
itsnotmeatall said:
jeansebas said:
hey men i've seen your post about updating the galaxy music duos. but i have a problem rooting with the impactor method (when i hit the start button it says "signature bugs unavailable")
can you help me please?
Click to expand...
Click to collapse
Are you rooting the ICS build or the JB build? AFAIK the Impactor method works with the JB build.
Click to expand...
Click to collapse
i'm trying to root my phone with JB, what can i do to make it work?
Click to expand...
Click to collapse
Are you sure you have JB already installed? What does it say in the Settings>About Device>Android Version?
It is only AFTER you have Jelly Bean 4.1.2 on your phone that you can root it with Cydia Impactor.
Click to expand...
Click to collapse
yes man, my version is 4.1.2.
Click to expand...
Click to collapse
Clear the cache from the recovery menu (check the first post of the thread to see how to go into the recovery menu).
If that does not work, factory reset the phone and try again. (backup your apps and settings using Titanium Backup first)
If even that does not work, do a clean install of 4.1.2 again using Odin. then try.

jeansebas said:
1. i've installed the kies software.
2. how can i do the factory reset without losing my apps and data? ( i tried using the titanium back up but i need to be rooted :/ )
Click to expand...
Click to collapse
Is your USB debugging ticked? (Just checking)
You can use the following methods to back up apps and data before factory reset:
https://play.google.com/store/apps/details?id=com.koushikdutta.backup
http://www.xda-developers.com/android/ultimate-backup-tool-no-root-required/

jeansebas said:
dude i tried all the methods that you suggest but none of the worked , what can i do to root my phone?
Click to expand...
Click to collapse
Have you tried this:
Reinstall 4.1.2 using Odin.
Then immediately root with Cydia (before installing your apps etc)
Just one thing: are you from brazil? I think the phone there is a little different 6012B instead of 6012 in the rest of the world.

FRP LOCK ON Can't ODIN firmware... Lord help me.

Canadian NOTE5 here, I forgot to unclick the OEM Lock in the developer options and now I cannot boot up, I cannot flash ODIN stock firmware from Canada, although only Puerto Rico seems to exist for SM-N920W8 etc... I get the error HIDDEN.IMG then FAIL
I cannot flash TWRP because I get BLOCKED BY FRP LOCK.
Smart Switch does not support my device. So that doesn't work either.
I have tried ODIN TMOBILE firmware, that fails right away.
I have had 10 different rooted devices without a hitch, is this my first brick ever?
Do I have to wait for different firmware?
Anyone? Happy to buy anyone a beer or two who can assist me!
Thanks!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Model Number: N920W8
Please wait..
Checking MD5 finished Sucessfully..
Leave CS..
Odin engine v(ID:3.1100)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
sboot.bin
NAND Write Start!!
cm.bin
boot.img
recovery.img
system.img
cache.img
hidden.img
FAIL!
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)

I guess your best bet is to wait for official Bell firmware. But it's strange that I never came across that. Did you read the instructions on getting the phone rooted? Did you enable the OEM unlock?

Did you try Samsung Kies software.
Sometimes it can restore phone to original.

LouK said:
Did you try Samsung Kies software.
Sometimes it can restore phone to original.
Click to expand...
Click to collapse
jqmalang said:
I guess your best bet is to wait for official Bell firmware. But it's strange that I never came across that. Did you read the instructions on getting the phone rooted? Did you enable the OEM unlock?
Click to expand...
Click to collapse
Solved! I reflashed the firmware and flashed the hidden.img separately in Odin and success!
Sent from my Gorgeous Note5

Brava27 said:
Solved! I reflashed the firmware and flashed the hidden.img separately in Odin and success!
Sent from my Gorgeous Note5
Click to expand...
Click to collapse
how please??

edwardob said:
how please??
Click to expand...
Click to collapse
You need to flash firmware from your provider.

Brava27 said:
You need to flash firmware from your provider.
Click to expand...
Click to collapse
how to flash
" I reflashed the firmware and flashed the hidden.img separately in Odin"
do you remove hidden .img from firmware..
how did you do it please??

edwardob said:
how to flash
" I reflashed the firmware and flashed the hidden.img separately in Odin"
do you remove hidden .img from firmware..
how did you do it please??
Click to expand...
Click to collapse
Why do you want to remove hidden.img? You only have to do this if you get an error message fail hidden.img

Brava27 said:
Why do you want to remove hidden.img? You only have to do this if you get an error message fail hidden.img
Click to expand...
Click to collapse
thats right/........so how do you do it?

heres mine
similiar problem different file
anyone any ideas?

my mobile phone, same as you,how can i do? i am using note 5 n9200,what i need to download? 1,odin,and other?can you tell me the step,thank you very much

same here SM-N920W8
Please theres a step by step guide to flash tru odin ,say solved but no how to thanks

pls help us i have the same on my note 5 N9200 and i tryd evrythink so if its working to you you have me some hoop that i dont loose 800 dollar on my note 5

Ekinz1219 said:
my mobile phone, same as you,how can i do? i am using note 5 n9200,what i need to download? 1,odin,and other?can you tell me the step,thank you very much
Click to expand...
Click to collapse
did u solve the problem? i have the same device as you do, and i have the same situation.
After tried almost every Stock Rom, i still get stuck after boot.img.

This problem is because you forgot to unlock bootloader from developper options.
Reflash the official latest stock firmware with odin, then unlock the bootloader and reflash what ever you want after.

edwardob said:
similiar problem different file
anyone any ideas?
Click to expand...
Click to collapse
Ekinz1219 said:
my mobile phone, same as you,how can i do? i am using note 5 n9200,what i need to download? 1,odin,and other?can you tell me the step,thank you very much
Click to expand...
Click to collapse
TIAR2018 said:
Please theres a step by step guide to flash tru odin ,say solved but no how to thanks
Click to expand...
Click to collapse
andixxqaz said:
pls help us i have the same on my note 5 N9200 and i tryd evrythink so if its working to you you have me some hoop that i dont loose 800 dollar on my note 5
Click to expand...
Click to collapse
danielweng said:
did u solve the problem? i have the same device as you do, and i have the same situation.
After tried almost every Stock Rom, i still get stuck after boot.img.
Click to expand...
Click to collapse
Download the latest stock firmware for your device model, and extract from it the file called hidden.img, rename that file as hidden.img.tar Now open Odin and try to install the firmware you downloaded, when you see the error in Odin, load the file hidden.img.tar on AP and flash it. Now turn on the phone and wait around 5 minutes, it should boot up.
Please note that this will only work if the error shown in Odin is:
hidden.img
FAIL!

Brava27 said:
Solved! I reflashed the firmware and flashed the hidden.img separately in Odin and success!
Sent from my Gorgeous Note5
Click to expand...
Click to collapse
Hi, I had the same issue I tried rooting my note 5 and it failed and now i'm stuck
i'm really freaking out I paid a lot of money for it,
odin says " NAND write failed"
can you please help me ?!

m7mdas3d said:
Hi, I had the same issue I tried rooting my note 5 and it failed and now i'm stuck
i'm really freaking out I paid a lot of money for it,
odin says " NAND write failed"
can you please help me ?!
Click to expand...
Click to collapse
You need the correct firmware for your device from sammobile.com

Brava27 said:
You need the correct firmware for your device from sammobile.com
Click to expand...
Click to collapse
I have the exact one, I have downloaded it before rooting in case something wrong happened, which did :crying: !!!
still fails at the NAND write

m7mdas3d said:
I have the exact one, I have downloaded it before rooting in case something wrong happened, which did :crying: !!!
still fails at the NAND write
Click to expand...
Click to collapse
You need to use the odin Odin3 v3.10.7.1

N950U1UEU5DSC1 and Odin

I'm currently on the Pie beta 3 (sideloaded N950U1UEU5ZSC2) and downloaded N950U1UEU5DSC1 from Sammobile. I am using Odin v3.13B and trying to flash to it but it fails every time. I am able to reboot the phone and get back into Pie beta 3 without any issues after it fails.
I have tried this without and with Kies installed, SmartSwitch, have tried connecting directly into a usb slot on my motherboard, the original cable that came with the phone, reinstalled Samsung drivers and I still can't get it to flash.
Any ideas?
!!!SOLVED!!!
Apparently USB 3.0 is this cutting edge technology but sucks in application of pretty much everything. Use USB 2.0 and if your motherboard only has 3.0 and so does your laptop, good luck.

joncurry94 said:
I'm currently on the Pie beta 3 (sideloaded N950U1UEU5ZSC2) and downloaded N950U1UEU5DSC1 from Sammobile. I am using Odin v3.13B and trying to flash to it but it fails every time. I am able to reboot the phone and get back into Pie beta 3 without any issues after it fails.
I have tried this without and with Kies installed, SmartSwitch, have tried connecting directly into a usb slot on my motherboard, the original cable that came with the phone, reinstalled Samsung drivers and I still can't get it to flash.
Any ideas?
Click to expand...
Click to collapse
What is the error given in Odin?

stonedpsycho said:
What is the error given in Odin?
Click to expand...
Click to collapse
Interestingly enough, sometimes Odin just closes altogether so I lose the logs. Other times, it just says Fail and the log says "<ID:0/001> Odin engine v(ID:3.1301)..
<ID:0/001> File analysis..
<ID:0/001> skip file list for home binary
<ID:0/001> apdp.mbn
<ID:0/001> msadp.mbn
<ID:0/001> persist.img.ext4
<ID:0/001> dqmdbg.img.ext4
<ID:0/001> userdata.img.ext4
<ID:0/001> carrier.img.ext4
<ID:0/001> Home Binary Download
<ID:0/001> Total Binary size: 4503 M
<ID:0/001> SetupConnection..
<ID:0/001> Initialzation.."
it doesn't seem to move past this. I also have to hit Start 2-3 times before it begins. I just redownloaded it again to make sure the file wasn't corrupted.

stonedpsycho said:
What is the error given in Odin?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

joncurry94 said:
Click to expand...
Click to collapse
Maybe try the unpatched Odin? (Never seen that version before, is that for the U models specifically?)
Has Odin worked before? Or is this the first time? ADB and Samsung drivers installed?

stonedpsycho said:
Maybe try the unpatched Odin? (Never seen that version before, is that for the U models specifically?)
Has Odin worked before? Or is this the first time? ADB and Samsung drivers installed?
Click to expand...
Click to collapse
I just downloaded the unpatched version of Odin (newest version). Samsung drivers are definitely installed, where do I get ADB drivers? Not familiar with that. And yes, first time with Odin!

joncurry94 said:
I just downloaded the unpatched version of Odin (newest version). Samsung drivers are definitely installed, where do I get ADB drivers? Not familiar with that. And yes, first time with Odin!
Click to expand...
Click to collapse
You can get ADB drivers here - https://forum.xda-developers.com/showthread.php?t=2588979
Just type "Y" to install all the drivers. Hopefully this will sort it for you.

stonedpsycho said:
You can get ADB drivers here - https://forum.xda-developers.com/showthread.php?t=2588979
Just type "Y" to install all the drivers. Hopefully this will sort it for you.
Click to expand...
Click to collapse
Still no luck. Installed the ADB Drivers, reinstalled Samsung drivers (directly from Samsung's website), used the newest version of Odin (as administrator), rebooted. Still stuck at initializing and then after a few minutes Odin just closes.

joncurry94 said:
Still no luck. Installed the ADB Drivers, reinstalled Samsung drivers (directly from Samsung's website), used the newest version of Odin (as administrator), rebooted. Still stuck at initializing and then after a few minutes Odin just closes.
Click to expand...
Click to collapse
Have nothing else to suggest :-/ Hopefully someone more knowledgeable will be able to help you.

stonedpsycho said:
Have nothing else to suggest :-/ Hopefully someone more knowledgeable will be able to help you.
Click to expand...
Click to collapse
That's okay! Thanks for trying! Maybe I'm missing something.

Just out of curiosity: is sideloading N950U1UEU5DSC1 an alternative to upgrading using Odin?

Did you run it as an administrator? You can right click on Odin and get the administrator chouce.

mikeyk101 said:
Did you run it as an administrator? You can right click on Odin and get the administrator chouce.
Click to expand...
Click to collapse
Yes, I have tried running as administrator as well as Windows 7 compatibility mode on multiple versions of Odin.
Here's logs from most recent attempt:
<ID:0/008> Odin engine v(ID:3.1301)..
<ID:0/008> File analysis..
<ID:0/008> skip file list for home binary
<ID:0/008> apdp.mbn
<ID:0/008> msadp.mbn
<ID:0/008> persist.img.ext4
<ID:0/008> dqmdbg.img.ext4
<ID:0/008> userdata.img.ext4
<ID:0/008> carrier.img.ext4
<ID:0/008> Home Binary Download
<ID:0/008> Total Binary size: 4503 M
<ID:0/008> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
After hitting start three times it makes it past this and to Initialization... before closing.
Since this issue has occurred I have tried the same process on a laptop as well.