yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] DuceTheTruth:
hmmm...no dice still

does it matter which rom Im on to flash this image? Im running the Naked rom while trying this

i wiped cache then factory data reset then...

C:\adb>adb push boot.img /sdcard/boot.img

2521 KB/s (3930112 bytes in 1.522s)

C:\adb>adbshell

'adbshell' is not recognized as an internal or external command,

operable program or batch file.

C:\adb>adb shell

sh-4.2$ su

su

sh-4.2# dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8

dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8

7676+0 records in

7676+0 records out

3930112 bytes transferred in 0.919 secs (4276509 bytes/sec)

sh-4.2#

then wiped cache and factory data reset again and i get stuck on samsung screen.

im gonna try it on stock rom
[Upgrading, Modifying and Unlocking] TheGeekyNimrod:
Search the forums for Mobile Odin Pro. You can use that to flash the boot.img as you would through Odin. That might work. I've never used ADB to push anything but APK files. I always use Mobile Odin or desktop Odin.

And I'm not sure what Naked rom is. Was that a rom built for this device? If not, that could be a big part of the problem. I've gotten stuck flashing roms for devices that were similar to the Discover, and ended up stuck.

You can try the ADB command on stock rom. It might work. But as I said, I've never pushed kernels using ADB, so I'm not the best to advise on that method. Wish I could be more help. My Discover is currently waiting on me to flash the stock firmware back to it as I mucked something up the other day just fooling around with it. DOH! :cyclops:
[Upgrading, Modifying and Unlocking] DuceTheTruth:
you know, now that I'm looking, do you have the "G" variant of the Discover?....I have the "C"

The Naked rom is here....this post help me unbrick mine a while back...

http://xdaforums.com/showthread.php?t=2617484

Here were the directions for me doing what I did......I dont think he ever made that flashable zip though

http://xdaforums.com/showthread.php?p=43030896

post number 68

FitAmp	Old 28th June 2013, 04:12 AM #68

FitAmp's Avatar Senior Member

Thanks Meter 689

Posts: 1,413

Join Date: Mar 2012

Location: Terrace

MORE INFO >

Here it is.

Overclock Step Upto 1000mhz MAX(For now)

put boot.img on sdcard

adb push boot.img /sdcard/boot.img

-THAN from adbshell

su

dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8

then reboot device.

test it out please

I will make a flashable zip soon

ATTACHED FILES

File Type: img	boot.img - [Click for QR Code] (3.75 MB, 176 views)
[Upgrading, Modifying and Unlocking] TheGeekyNimrod:
I think I see what is wrong. The filename itself is listed as "imgboot.img"

So that last step should be

su

dd if=/sdcard/imgboot.img of=/dev/block/mmcblk0p8

See the difference? You have to be pushing the exact file name otherwise it will fail.

I have the "g" variant. They are pretty much the same thing. I think thw differences (other than baseband radio) are slight differences in the mount points.

Try the ADB command again, but use "imgboot.img" instead of "boot.img" and see if that works. Fingers crossed for you.
[Upgrading, Modifying and Unlocking] TheST4RL:
Any working Cyanogenmod (or AOSP roms) roms available for the SGH-S730M?
[Upgrading, Modifying and Unlocking] Matholameu:
So, did anyone ever find a way to unlock the SGH-S730M?
[Upgrading, Modifying and Unlocking] andronald:
LOCATIONS TO BE ADDED AS DISCOVERED:

LOCATIONS OF CSC DATA (or important phone data):

- system/app - if you can deodex the ROM, things would be easier to unlock ;)

- CSC.apk

- HiddenMenu.apk - network unlock menu is missing :(

- Keystring_factory? Maybe

- Personalization.apk (PERSO)

- Preconfig.apk (use the canadian one)

And problably others

- system/CSCVersion.txt

- system/csc - all files in directory

(also may contain bootlogo data)

- efs - duh

- dev/block/mmcblk0p3 - lots of carrier stuff including usage of UN_Lockcode (if you can find it!).

- Problably other files in dev/block

Im sorry if I missed some, these are the most common ones on the sgh-s730.

Please thank the OP if you used my guide (or files). It really helps me feel that my efforts arent being wasted.

Sent from my SAMSUNG-SGH-I777
[Upgrading, Modifying and Unlocking] Normrdt:
I have been exploring the phone using ES explorer with root access and have seen many different carriers listed. Thinking there must be something that if changed the right file you could boot to a different carrier. I guess it is not that easy.
[Upgrading, Modifying and Unlocking] Normrdt:
I give up. I restored 2.3.3 to the LG P500 to get my voice to text back and it started sending pictures again. and ....... The SGH S730M is also sending picture MMS now. I have no idea.
[Upgrading, Modifying and Unlocking] sparhawk909:
Thank you for your guide and hard work. I got the Samsung Galaxy Discover S730M from Telus. This is my first smartphone and root.

.
[Upgrading, Modifying and Unlocking] x1745:
doctor_evil- Would you please backup and upload your back Rom, I would like to compare it with my Rom where the unlock code hidden?

For tweaking your CPU the software call setCPU for android since it is rooted then is easy to set the Clock speed.
[Upgrading, Modifying and Unlocking] andronald:
If you want a free unlock, you got to work for it. It isn't that easy anymore.

It depends on the phone's kernel. Overclocking apps wont work on the S730M (trust me, Ive tried many). I DO however, use Voltage Control to change my minimum CPU Speed, which makes it "slightly" faster.

If you can make a kernel for this phone that supports overclocking, then it will work.

Can you confirm that setCPU will actually work on the S730M? (Take a screenshot of the setCPU app showing an over clocked frequency).

I am slightly sceptical of your claim.

And in terms of unlocking: Please understand that the nv_data.bin is hidden. And I really mean hidden!

The efs does not show it. The system wont show it.

The bootloader knows everything, we are all just too lazy to look.

Look at the third bootloader file in dev/block. I need someone to actually dump ALL of it as readable text. Every time I try to dump the file as ANSI, it will trim the file because it is so big.

OR, someone find a way to get the UN_Lockcode (so we can make a unlock code)! Please! If online businesses can do it, we can do it too.
[Upgrading, Modifying and Unlocking] neilenore:
wow thank you for this! I can now fix my friend's phone
[Upgrading, Modifying and Unlocking] camvar97:
i think i hard bricked the phone unsure though... flashed a img file to the modem partition by accident and now no boot.... only loop of black screen, no recovery access and no download mode access... have went back to using my lg p500 for now
[Upgrading, Modifying and Unlocking] andronald:
Sorry, wish I could help :(
[Upgrading, Modifying and Unlocking] scaryuncle:
i have been stuck on one step for a week now, and it sorta has nothing to do with the rooting itself.

i've not been able to install unlock root at all. it stalls on the "preparing unlock root" dialog and never goes any further.

has anyone else encountered this? i've disabled anything i thought would be stopping it from working, no luck.

i let it run for almost 24 hours and it does nothing.

is there any other way to root it, or does it have to be done with unlock root?

i am hoping someone can answer this question, as searching everywhere has not helped, and i would really like to root this phone.

any help would be appreciated.
[Upgrading, Modifying and Unlocking] andronald:
Did you install the drivers I linked in the OP?

Sent from my SAMSUNG-SGH-I777
[Upgrading, Modifying and Unlocking] x1745:
Doctor_evil- my phone S730M when I boot to Android system recovery <3e>

Options to select Volum up/down to highligh options

The options:

reboot system now

apply update from external stor, any zip files I select the error E: signature verification failed.

I tried CWM_recovery_S730M.zip error E: failed to mount /System (Invalid argument), can't mount '/system'

wipe data/factory reset

wipe cache partition

apply update from cache

I don't have restore options to select the folders to restore.

Is there another recovery img that I need to flash to have that options?

I backed all files from my phone onto SD card folder by Android Commander/

This program restore only work to when phone is functional mode.

Since my phone is soft brick

I tried all the options you suggested but nothing works

after flashed by ODIN3 26 times now and when it completed and reboot and stuck on Samsung logo. nothing else boot

Question: Is there any software that allow me to restore all these folders I backed up my Android Commander or a way to modify these folder into tar or zip so I can install from SD card?

Is there any steps by steps to recover this phone?

Thanks,

X1745
[Upgrading, Modifying and Unlocking] JohnnyGalto:
x1745, flash the

Clockworkmod Recovery

from original post. It is bundled with Odin Flashing Program.

Follow instructions in that post on how to flash.

Once you flash that recovery you should be able to use the touchscreen and select the options as per the guide to recover from your soft-brick.

Hope this helps,

JohnnyGalto
[Upgrading, Modifying and Unlocking] undead2589:
can this method root the sgh-s730G

hey i was just wondering if this would root the samsung galaxy discover from net10. thats the phone i have. i dont want to try just in case it bricks it.
[Upgrading, Modifying and Unlocking] andronald:
Can you send me a copy of your build.prop file? I need to verify.

I did a quick google search on this phone. It looks pretty much the same as the 730m BUT had the branding on it. I can compare my build.prop with yours to see if they are the same system specs.

If they are, then it might work. Wish I knew for sure.
[Upgrading, Modifying and Unlocking] x1745:
Thanks JohnnyGalto, I have tried that. after rebooting into recover mode and the firmware does not have options for turn off or disable Signature verifications, so when I tried to install software the error I got was e: Signature Verification failed. any program that can remove this would be good.

I am stuck with this option - not sure how to get rid off the E: signature verification failed

I am looking for Clockworkmod to have that options.

I tested repartition with u1_02_20110310_emmc_EXT4.pit in ODIN but failed to boot due to wrong pit model for my phone.

I tested with another pit totoro_0623.pit that also failed too.

Anyone know how to create/edit pit file for this model SGH-S730M?
[Upgrading, Modifying and Unlocking] JohnnyGalto:
x1745,

I am including the SGH-S730M PIT file as well as a CWM 6.0.3.1 custom recovery that I have compiled that fixes the dpi issue. It does not include touchscreen input so use the volume up/down keys to move up or down and the power button to select.

Go into ODIN and select the tar file I have uploaded under PDA and select the unzipped pit file under PIT. Flash these files to your phone and you should now be golden.

From there you will unzip the contents of the backup from the OP to your sdcard, select restore from options, and then restore. Once you have restored this backup you may restore your backup after installing the software.

Take a screen shot of where you get stuck and upload it if this doesn't work for you.

EDIT 1:

Here is a triangleaway script. Just a start but it resets flash counter and resets binary status to official. Might have to do a factory reset to return current status to official.

How to use:

Boot into CWM recovery.

push script to /tmp

chmod 755 script

execute script

enjoy

EDIT 2:

Recovery now MD5 signed for a little extra insurance against bricking.

TWRP Recovery now available. Untested as my touchscreen is wacked out from flashing the wrong kernel. Try it out and let me know. MD5 signed as well.

NB: Use at your own risk. Always make a full backup before playing around with custom flashes.

JohnnyGalto
[Upgrading, Modifying and Unlocking] x1745:
S730M

Thanks JohnnyGalto,

Sorry I haven't have a chance due to try this out, my phone was sent to Samsung for repair for I got this message.

After talking to Samsung support it was a mistaken to sent for repair. They are useless they said for repair without warranty will be $97 plus tax.

I told them forget it just send the phone back.

This phone I paid for $80 bucks but the repair cost more then a new one.

First they said is free of repair because is under warranty.

Then when they got it they said is not under warranty due the phone was rooted.

My phone was hard bricked I couldn't flash the phone to un-rooted.

I will try this when I get my phone back from Samsung repair dealer.

Thanks.
[Upgrading, Modifying and Unlocking] JohnnyGalto:
The PIT file provided is extracted from a stock SGH-S730M. There is no other.

Here's the breakdown(gathered from PIT_Magic_v1.3.10_Release and fdisk):

block_device(id): PARTITION_NAME(Odin_filename)

-----------------------------------------------------------------------------

mmcblk0p1(id 0x4d): CFG_DATA (qcsblhd_cfgdata.mbn)

mmcblk0p2(id 0x45): QCSBL (qcsbl.mbn)

mmcblk0p3(id 0x0c): FAT (fat.bin)

mmcblk0p4(id 0x05): (partition.bin)

mmcblk0p5(id 0x46): OEMSBL (oemsbl)

mmcblk0p6(id 0x47): APPSBL (appsbl)

mmcblk0p7(id 0x5d): SSD ()

mmcblk0p8(id 0x48): APPS (boot.img)

mmcblk0p9(id 0x4a): MODEM_ST1 ()

mmcblk0p10(id 0x4b): MODEM_ST2 ()

mmcblk0p11(id 0x90): PERSIST (persist.img.ext4)

mmcblk0p12(id 0x91): RECOVERY (recovery.img)

mmcblk0p13(id 0x92): PARAMETER ()

mmcblk0p14(id 0x93): SECURE (secure.img.ext4)

mmcblk0p15(id 0x95): PIT (pit.bin)

mmcblk0p16(id 0x82): SYSTEM (system.img.ext4)

mmcblk0p17(id 0x94): CACHE (cache.img.ext4)

mmcblk0p18(id 0x83): USERDATA (userdata.img.ext4)

mmcblk0p19(id 0x65): EFS (efs.img.ext4)

mmcblk0p20(id 0x9a): IMG_BACKUP ()

mmcblk0p21(id 0x63): MISC ()

mmcblk0p22(id 0x67): HIDDEN (hidden.img.ext4)

mmcblk0p23(id 0x58): MODEM_BKP ()

One extra partition type mentioned in PIT not found in image:

(id 0xA0): GROW ()

PIT file is a dd of mmcblk0p15. Unlock code is most likely stored in mmcblk0p1. Loke is mmcblk0p6. Everything else is pretty much self explanatory. If someone could extract all these partitions and just report on whether they contain any data or are blank we could learn more about this phone.

Here's what I get:

PARAMETER, secure.img.ext4, SSD, hidden.img.ext4, IMG_BACKUP, persist.img.ext4, MISC are all zero-data.
[Upgrading, Modifying and Unlocking] JohnnyGalto:
Flashed the wrong kernel and now your touchscreen is unresponsive or way out of calibration? PM me for a solution. It's a crude fix for now but it works great and recalibrates the touchscreen to factory condition. Don't yet want to release it out here as a userland solution will be much easier to perform and may include a few extra goodies.

Managed to compile Samsung's Open Source kernel release quite easily and a forthcoming kernel upgrade as well as CM10.1, AOKP, and PA ROM builds will be coming soon.
[Upgrading, Modifying and Unlocking] clickmorison:
thanks its work :)
[Upgrading, Modifying and Unlocking] igmrlm:
:fingers-crossed: :D

Thats very exciting to hear, I seem to be unable to find any custom roms for this device anywhere.

Also the instructions worked perfectly thanks OP!
[Upgrading, Modifying and Unlocking] doctor_evil:
is there any way to take the necessary bits from the original factory ROM to create the files needed to make a ODIN compatible restore for the Discover? I know it would make it a lot easier to restore the phone to factory if needed in case of a bad rom flash.

It's exciting news that you've been able to compile the kernel, how far along are you currently on the CM10.1, AOKP, and PA rom builds?
[Upgrading, Modifying and Unlocking] jam52633:
Thank you

Was able to root and set up the custom recovery.

I wasn't able to overclock with setcpu, I actually tried with a bunch of different overclock apps, but it would never go over the stock speed. Any tips?
[Upgrading, Modifying and Unlocking] jam52633:
After doing a crap load of reading and testing, I now know, I have to install a custom rom.
[Upgrading, Modifying and Unlocking] mccabet:
Loaded TWRP on SGH-730G

I loaded TWRP on my SGH-730G model of the Samsung Discover. It works fine without any problems I have noted as of yet. The triangleAway script I don't think will work as appears to overwrite parts of the model number. I got rid of my triangle by restoring my copy of mmcblk0p0.

Also note, I did not use the steps here to root my Discover, but I dont see why it would not work.

Do you have a github available so I can get the build files for TWRP or CWM? I want to try to build a fresh AOSP or CM ICS build. Your build files will save me a litle time since you have already created them for the discover.

Thanks!

McCabet
[Upgrading, Modifying and Unlocking] JohnnyGalto:
GitHub: JohnnyGalto/android_device_samsung_amazingtrf

The TriangleAway script modifies the variables in the BootInformation header contained in mmcblk0p1 as described by ChainFire in http://xdaforums.com/showpost.php?p=30249325&postcount=3 as well as others elsewhere. It should not be modifying the model number but rather the flash counter and its backup; however, our exact locations may differ. In order to refine the script and help document this header could you please post the details of a cmp -l on the original mmcblk0p1 that you restored in order to remove the triangle and the first flash you perform after this. This should help in correctly identifying the differing byte locations within the partition.

The GitHub repo is not complete enough to build AOSP or CM yet but it should be a start for you. I haven't updated it in a while but I will as soon as I have time.

Sincerely,

JohnnyGalto
[Upgrading, Modifying and Unlocking] mccabet:
SGH-S730G Triangle

I attached a file with the diff output from the cmp -l.

The flash used to cause the triangle was the odin load of your TWRP image.

If you want, I have partition dumps of all partitions of the SGH-S730G as well. I even have a before and after image set, after unlocking the network. I have not compared all files to see what changed yet.
[Upgrading, Modifying and Unlocking] JohnnyGalto:
mccabet,

network unlock before and after? Wow, very nice been looking for a diff of those two. I have yet to unlock mine and as such am unable to compare a before and after in order to find the lock. If you take a look in one of my previous posts(http://xdaforums.com/showpost.php?p=41282320&postcount=40) I gave out the partition scheme. Going from the relevant partitions namely 1-3, 7, 9, 10, 11, 13,14 , 19-23, could you please diff(cmp -l) them before and after network unlock. Most should not have changed as they seem to be either zero-data for me or executable images but I have a feeling 1, 3, 9 or 10 might be the winner. As well are PARAMETER, secure.img.ext4, SSD, hidden.img.ext4, IMG_BACKUP, persist.img.ext4, MISC, all zero-data for you as well?

Side note: Using the TWRP can you get adb to connect. I am unable to connect to mine as it seems to be unable to spawn a shell? Maybe a symlink got f'ed up because without any modifications to my device_ repo I compiled CWM and am not getting any errors with that one.

Feel free to contact me if you would like to collaborate on a ROM build,

JohnnyGalto
[Upgrading, Modifying and Unlocking] mccabet:
Discover Diffs and dumps

running adb under TWRP gives me:

>adb devices

List of devices attached

????????????	no permissions

I also have two unlocked SGH-S730M Discovers that the daughters use. I have dumps from them as well after they were unlocked. I bought them unloicked.

I'll try an compare the files tonight. The partition scheme is similar to the Gapaxy Appeal (SGH-I827) I actually loaded the Discover kernel I built on the Appeal and messed up the touch screen. Had to make a custom load to fix it.

Interested colaborating. Will do what I can.

Keep you posted on the diffs...
[Upgrading, Modifying and Unlocking] JohnnyGalto:
Ya, that's about what I figured for adb. I got to track down this problem and resolve it when I can.

As well I noticed from your diff that you are running a SGH-S730G which might explain the difference in BootInformation layout for mmcblk0p1. If you open up the mmcblk0p1 in a hex editor and look around offset 19970(dec) you should find the following bytes 0x12 0x00 0x34 0x12 the byte immediately following this will be the boot counter. There appears to be a backup of the previous boot counter/checksum exactly 0x34 bytes after the start of the header. I say checksum as ChainFire mentioned a boot type in header+8 but his definition doesn't match ours and the dissemination at http://xdaforums.com/showpost.php?p=28953690&postcount=67 which seems to be closer to our definition makes reference to a checksum. Some more investigating is warranted on this data.

Anyways, have a look at your copy and see where that header is located as it may just be at a slightly different offset.

JohnnyGalto
[Upgrading, Modifying and Unlocking] mccabet:
Differences between 730M and 730G

NOTE: DISCLAIMER!!! This is a discussion of data located in areas of your phone that can turn it into a BRICK!!! We are NOT responsible for you damaging your phone by using this information! USE this information at YOUR OWN RISK!!

I have compared the 730M and the 730G P1 blocks and they are not the same as we believed. The first 0x12 0x00 0x34 0x12 sequence ( at 0x4E00 ) is in the same location. After the odin load, alot of crap is added.

It appears we can zero the byte at 0x4E04 following the sequence, and then the next 117 bytes starting at 0x4E2B. I'll have to give it a try after I load the CWM you built.
[Upgrading, Modifying and Unlocking] JohnnyGalto:
Just tried a bit of zero-ing out and it appears that zeroing everything but 4E00-4E03(Header) and 4E10-4E18(Model Number) results in 'No' Custom Binary Download, 'Samsung Official' Current Binary and 'Offcial'(sic) System Status even with a CWM Recovery on phone! Phone boots to Download Mode, Recovery Mode and Android without any problems so it appears it resets everything to stock.

Only thing remaining would be to verify the content of p1 on a stock(never flashed) phone to verify the necessary data to return to stock. I also tried copying the data you had provided for the stock phones and it resulted in a 'Custom' Current Binary. The 02 at 4E0C correlates to an Unknown status according to http://xdaforums.com/showpost.php?p=28953690&postcount=67. The other data at 4E28 doesn't have a correlate in the breakdown though. Could this additional data be a type of checksum? Time to find the appsbl entry point and throw it into IDA for the answer.

JohnnyGalto
[Upgrading, Modifying and Unlocking] mccabet:
It is good that zeroing does what I thought it would. I have stock images of the 730G and the 730M. The data I have been working with lately is for the 730G.

My goal is to build a software load that is compatible for both phones.

If you look at the text file I attached to the last post, it has the stock data for both models for comparison, and the custom after odin data.

EDIT: I experimented by comparing a similar phone the Galaxy Appeal, SGH-I827. The partition layouts are the same and I had a custom flag set that also set the triangle. I zeroed the byte after the header, then the bytes after the model number. This caused the custom flag to be cleared, but still showed custom firmware and the triangle was present. Looking at the bytes in the header starting at 4E00, the first byte was an 11h on my device. I changed this byte to 12h, and it cleared the triangle and the odin screen shows official firmware.
[Upgrading, Modifying and Unlocking] mccabet:
Triangle Away

JohnnyGalto,

Here is my triangle away script.

It addresses the issues we discussed where it clears the custom flag, but not the official status.

I found the first byte at 0x4E00 is 0x12 for an official load. the byte following hte header is the count and is set to zero. The remaining 238 bytes following the model are zeroed out to remove traces of an odin load.

You can use your steps above to load, or I just executed:

sh triangleaway.sh

let me know of any issues!

To all who may try an use this script, I suggest you make a backup of mmcblk0p1 just in case you need to restore it.