Develop Bugs

Samsung Galaxy Gio GT-S5660M Discussion - Rooted Stock ROM, Partition Mapping

(Avis aux intéressés, j'ai traduit mon message en français, et reparti une discussion sur Frandroid.)
Hello,
I managed to map the partitions on the Gio 5660M (Bell Canada, 2.3.4, MUGK3) in order to extract an ODIN flashable complete stock backup.
I have also made a stock, rooted ROM backup by working in a hex editor. Other tools that helped the mapping were Winmerge, to do file comparisons with an Euro 5660 ROM, and Notepad++ for string searches.
Those with a 5660M that are experiencing issues after flashing Euro 5660 ROMs that have been posted here now have the possibility of flashing back their original radio and kernel.
ROM development and deployment is going to be safer going forward.
I copied the blocks with the dd command as follows:
dd if=/dev/block/bml1 of=/sdcard/bml1 bs=4096
WARNING!!! DO NOT dd /dev/block/stl5 as there have been multiple reports of bricking following reading it. We already know that this block contains the EFS partition, including the SIM-lock code. You can however dd bml5 without issue from a "live" phone. If you absolutely want stl5, you may get it by using a rooted custom recovery.
From what I've gathered bml is essentially a lower level interface to the same blocks accessed by stl, but the results differ somewhat in resulting file size.
Here are the results:
Code:
/dev/block/bml1 MIBIB
/dev/block/bml2 QCSBL
/dev/block/bml3 OEMSBL
/dev/block/bml4 AMSS
/dev/block/bml6 Essentially empty, with a FSR_STL string at the beginning.
/dev/block/bml7 arm11boot
/dev/block/bml8 boot.img. My initial assumption was based on the .ops file supplied with the Euro ROM I've done my comparisons with. This has since been confirmed with actual flashing.
/dev/block/bml9 recovery.img for the same reasons as above.
/dev/block/bml10 Essentially empty. Mine has a BMC string at the beginning which matches the CSC code on this phone, followed by an ON and an OFF.
/dev/block/bml11 Empty. \xFF all around.
/dev/block/bml12 Seems to contain the same RFS data as stl12, but with an additional 8 megs of data/padding, not readable by MagicISO.
/dev/block/bml13 Like 12 above, but user data
/dev/block/bml14 As above, but the almost empty partition
/dev/block/stl1 cannot open for read
/dev/block/stl2 cannot open for read
/dev/block/stl3 cannot open for read
/dev/block/stl4 cannot open for read
/dev/block/stl6 Empty: contains only \xFF
/dev/block/stl7 cannot open for read
/dev/block/stl8 cannot open for read
/dev/block/stl9 cannot open for read
/dev/block/stl10 cannot open for read
/dev/block/stl11 cannot open for read
/dev/block/stl12 system.rfs - is flashable as-is once tarballed. Also contains the CSC files as we're taking this from a "live" installation, contrary to an OEM provided image. (My image is also rooted for the same reason.)
/dev/block/stl13 data.rfs - User data partition
/dev/block/stl14 cache.rfs - Odin hangs when I try to flash it. Use CWM and dd back into place from the SD card.
From what I see we can't repartition our phones like the GT-I9000 guys do, so there are no PIT files to worry about. Only the OPS files which ODIN uses. We're not able to flash with Heimdall in its current configuration as it requires a PIT file.
GT-S5660M_MUGKG3_stock_rooted_ROM_v2.7z (101.46 MB)
Un7-Zip, flash tarball with Odin using the "One Package" option. Tested working on my phone. I think it goes without saying that flashing this is at your own risk.
(PDA: S5660MUGKG3 PHONE: S5660MUGKG3 CSC: S5660MBMCKG3)
Tutorial on flashing with Odin, with link for the appropriate version for our phone.
I've released my custom 5660M ROM, ArpegGioMod.
Goodbye,
Darkshado

Wow,
Thank you very much. The screen brightness issues and problems connecting to the mobile 3G network were very troublesome.
I will be flashing this ROM back to my s5660m.
THANK YOU!
STATUS UPDATE:
I have successfully flashed the image to my phone, i had to rename factory.rfs to system.rfs in order for ODIN to flash successfully. Also, it may not be important but I noticed that your image is missing the csc.rfs file.
I copied it from another ROM but it still didn't take it.
Even with the CSC.RFS file missing, it SEEMS to work GREAT! No more screen issues or 3G problems so far, I will keep you updated!
Again, thank you for uploading this, Hopefully soon there will be a CM7 for the s5660m!

Cool! Please, pretty please let me know as soon as possible how it turns out. When do you plan on trying this? This afternoon or later tonight?
Depending on how much you feel at ease with experimenting, you might be able to make a modified OPS file and new tar archive to flash only AMSS and boot.img to your system. Boot in recovery to wipe cache and dalvik-cache, then reboot the phone in normal mode. *If* things go according to plan you'd be left with a custom ROM'ed and functional phone. Otherwise just flash the whole thing back to stock.
Good luck,
Darkshado

Coolty said:
STATUS UPDATE:
I have successfully flashed the image to my phone, i had to rename factory.rfs to system.rfs in order for ODIN to flash successfully. Also, it may not be important but I noticed that your image is missing the csc.rfs file.
I copied it from another ROM but it still didn't take it.
Even with the CSC.RFS file missing, it SEEMS to work GREAT! No more screen issues or 3G problems so far, I will keep you updated!
Again, thank you for uploading this, Hopefully soon there will be a CM7 for the s5660m!
Click to expand...
Click to collapse
Great! You just made my day!
About the missing CSC file: CSC is an acronym for Carrier/Country Specific Code. The csc.rfs file is a partition image file that, as far as I can tell, is merged with the contents of the system.rfs partition. In our case, the CSC file would contain the APN settings, as well as the Bell proprietary apps like self-serve and remote PVR.
Instead, since I took the system partition from a live phone, the CSC content is already in the system.rfs partition. I think the idea behind this is that Samsung can release new CSC packages without having to update the whole firmware when "new" carriers add the phone to their lineup.
I'll see if I can edit the RFS partitions, (maybe by mounting them on the phone directly?) if so, I would be able to unroot, and make that separate CSC partition as well. That would make the backup completely stock, as if it came right from Samsung.
Another, simpler solution would be to modify the OPS file to skip the CSC partition.
One question: did you re-tar each file individually for ODIN to take them?
CM7 port: I'd love to have one on that phone as well, but I'm not in a position to tackle that project, yet. The good news is that since we now have a way to bring the phone back to stock, we can experiment safely.
Goodbye,
Darkshado

Depending on how much you feel at ease with experimenting, you might be able to make a modified OPS file and new tar archive to flash only AMSS and boot.img to your system. Boot in recovery to wipe cache and dalvik-cache, then reboot the phone in normal mode. *If* things go according to plan you'd be left with a custom ROM'ed and functional phone. Otherwise just flash the whole thing back to stock.
Click to expand...
Click to collapse
I will try this as well, will let you know the status of that as soon as I get to that. I am pretty confident with flashing phones by now
One question: did you re-tar each file individually for ODIN to take them?
Click to expand...
Click to collapse
No, I use linux so it was an easy process of copying the factory.rfs to my HDD, renaming it to system.rfs, deleting factory.rfs from TAR, and then adding system.rfs to the TAR file.
Let me know if you want me to try anything else, as I have access to linux and am pretty knowledgeable when it comes to things of that nature.

I can confirm that replacing amss and boot.img for 5660m from custom firmware meant for the 5660 works perfectly. I am using this tar: GioPro-1_2-LITE-by_ZimniY-S5660XXKQ6_S5660XXKQ5_S5660SEBKQ1.tar AND the GioPro 1.3 update zip. No screen issues or 3G problems. If you like I can upload the edited ROM for ODIN.

Step by Step guide for Noobs?
Hello,
My Samsung Gio S5660M is on an infinite loop.
Will this method fix the issue?
Can someone kindly give a step-by-step guide to this method (starting from what software/driver needed)?
Thanks a lot.

red02 said:
Hello,
My Samsung Gio S5660M is on an infinite loop.
Will this method fix the issue?
Can someone kindly give a step-by-step guide to this method (starting from what software/driver needed)?
Thanks a lot.
Click to expand...
Click to collapse
Why is your phone stuck in an infinite loop? What did you do to cause this?
did you somehow overwrote stl5(the efs partition afaik) while trying to unlock your phone?

Coolty said:
I can confirm that replacing amss and boot.img for 5660m from custom firmware meant for the 5660 works perfectly. I am using this tar: GioPro-1_2-LITE-by_ZimniY-S5660XXKQ6_S5660XXKQ5_S5660SEBKQ1.tar AND the GioPro 1.3 update zip. No screen issues or 3G problems. If you like I can upload the edited ROM for ODIN.
Click to expand...
Click to collapse
if you could post it, that would be much appreciated!!

steez003 said:
if you could post it, that would be much appreciated!!
Click to expand...
Click to collapse
I am currently in the process of uploading the edited TAR file to megaupload. The file is rather large so it may take another hour or so to complete. I will update this post when it is completed.
EDIT:
Here you go! GioPro 1.2 LITE edited for use with the Samsung Galaxy s5660m
Gio Pro 1.2 LITE updated for canadian s5660m by coolty

Coolty said:
Why is your phone stuck in an infinite loop? What did you do to cause this?
did you somehow overwrote stl5(the efs partition afaik) while trying to unlock your phone?
Click to expand...
Click to collapse
Hello Coolty,
Yes, that's exactly what happened. I tried to unlock it using Andorid Terminal Emulator, and although it gave me the unlock code, it fell into infinite loop upon restart.
Will your uploaded file fix this problem?
What would possibly provide a detailed guide on how to use the file?
Thanks.

red02 said:
Hello Coolty,
Yes, that's exactly what happened. I tried to unlock it using Andorid Terminal Emulator, and although it gave me the unlock code, it fell into infinite loop upon restart.
Will your uploaded file fix this problem?
What would possibly provide a detailed guide on how to use the file?
Thanks.
Click to expand...
Click to collapse
Hi,
I'm not one for explaining things in great detail, but the basic breakdown of the things you need (google is your friend) are:
1) Odin_Multi_Downloader_v4.42
2) The USB drivers for your phone (Hint: Samsung Kies)
3) OPS File (for this phone, I recommend GIO_v1.0.OPS)
4) Either a single TAR file or multiple files (eg, appboot, PDA, etc) For the file I am uploading it will be a single TAR file which is a package that includes all the things needed.
Then, you just remove the battery in your phone, unplug it from USB or wall charger, put battery back in, hold vol down + HOME + power until you see a screen (you may have to press a vol key after that, read the screen to see if you need to) Your screen on the phone should say DOWNLOADING... This is when you:
1) connect phone to computer via USB after installing drivers (kies, usb driver)
2) make sure kies is closed
3) run ODIN
4) choose the proper OPS file
5) click single package
6) choose the TAR file you want to flash to your phone
That's it!
EDIT:
I am providing some forum links that may better explain how to do what you need done:
How to unbrick (for samsung ACE, but applies to the 5660m) http://forum.xda-developers.com/showthread.php?t=1071970
How to use ODIN to flash your phone: http://forum.xda-developers.com/showpost.php?p=16979859&postcount=549
And of course, the great bible of GIO 5660 links and information: http://forum.xda-developers.com/showthread.php?t=1209425

I have updated my previous post to include the download link to the fixed rom for use with the s5660m.
(search for "s5660m by coolty" on the forums to find it)

Coolty said:
I am currently in the process of uploading the edited TAR file to megaupload. The file is rather large so it may take another hour or so to complete. I will update this post when it is completed.
EDIT:
Here you go! GioPro 1.2 LITE edited for use with the Samsung Galaxy s5660m
Gio Pro 1.2 LITE updated for canadian s5660m by coolty
Click to expand...
Click to collapse
Thanks! I ended up flashing my phone and I have run into a problem. For some reason Wifi won't work in GioPro. It says 'Turning on...' and then it will say 'Error'. Any ideas?
Thanks

Will this help at at all with a blank IMEI? I assume this would only help for people flashing back to stock firmware or recovering from a non-bootable or reboot loop phone?

steez003 said:
Thanks! I ended up flashing my phone and I have run into a problem. For some reason Wifi won't work in GioPro. It says 'Turning on...' and then it will say 'Error'. Any ideas?
Thanks
Click to expand...
Click to collapse
I'm also running into the same issue
Sent from my Nexus S using XDA App

Thats why i recommend you guys always do a factory reset before and after flashing , these glitches , like gps issue , wifi , stuck on boot logo , won't happen if you properly fectory reset before and after flashing....

Waqasshazad: Maybe wiping the caches will help, but the issues might be due to running a 5660 on a 5660M as well. We know the kernels and modems aren't compatible, it may go a bit further. By the way, it's spelled factory.
MacrossFX: I've seen mentions of people dd'ing their stl5 partition into a file and then back on the phone, but I'm unsure this worked in the end. I'm afraid your only solution might involve a shipment to the service center...

ClockworkMod Recovery for the Samsung Galaxy Gio GT-S5660
http://forum.xda-developers.com/showpost.php?p=16980117&postcount=559
May be this can backup for you , too with s5660m , i have tested on Gt s5660 and it worked perfectly fine..

waqasshahzad1986 said:
Thats why i recommend you guys always do a factory reset before and after flashing , these glitches , like gps issue , wifi , stuck on boot logo , won't happen if you properly fectory reset before and after flashing....
Click to expand...
Click to collapse
I followed your instructional video and did do a factory reset before and after. Maybe i'll try reflashing it again tonight and see what happens.

[SAMSUNG GALAXY S3 UNIFIED TOOLKIT V9] Drivers, Backup, Root, Recovery + MORE [SPR]

INTRODUCING THE SAMSUNG GALAXY S3 UNIFIED TOOLKIT
SUPPORTED MODELS
INTERNATIONAL [GT-I9300] SUPPORT THREAD HERE
AUSTRALIAN MODEL GSM [GT-I9300T]
INTERNATIONAL [GT-I9305/GT-I9305N] SUPPORT THREAD HERE
AUSTRALIAN MODEL LTE [GT-I9305T]
C SPIRE MODEL LTE [SCH-L710]
AT&T US [SGH-I747] SUPPORT THREAD HERE
BELL, ROGERS, SASKTEL, TELUS [SGH-I747M] [SGH-I747M] USE AT&T SUPPORT THREAD
US CELLULAR MODEL LTE [SCH-R530] USE AT&T SUPPORT THREAD
METRO PCS MODEL LTE [SCH-R530M] USE AT&T SUPPORT THREAD
SPRINT US [SPH-L710] SUPPORT THREAD HERE
TMOBILE US [SGH-T999] SUPPORT THREAD HERE
MOBILICITY, VIDEOTRON, WIND [SGH-T999V] USE TMOBILE SUPPORT THREAD
VERIZON US [SCH-I535] SUPPORT THREAD HERE
CHINA ANYCALL CDMA MODEL [SCH-I939] USE GT-I9300 SUPPORT THREAD
Click to expand...
Click to collapse
The Unified Android Toolkit supports a multitude of Nexus and Samsung devices with more devices being added all the time. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT V1.3.4 [9TH JAN 2015]
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader [Nexus]
* Root Stock builds
* Various Root options using insecure boot image or custom recovery
* ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
* Install BusyBox on your device
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
* Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Extras, Tips and Tricks section
* Auto Update ToolKit to latest available version at startup (professional only feature)
* Program up to 10 Quickpick slots and run them very quickly (professional only feature)
* Mods section to automatically perform certain tasks on your device
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
* Check md5 of stock image to make sure downloaded file isn't corrupted before flashing [Nexus]
* Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
* Flash Custom Recovery or Google Stock Image to Device
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
* Flash Custom Recovery to Device
* Boot [Nexus] or Flash .img Files directly from your PC
* Install a single apk or multiple apk's to your device
* Push Files from your PC to your device
* Pull Files from your device to your PC
* Disable forced encryption on Nexus6 and Nexus9 devices
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
* Install EFS/Partition Backup/Restore app by Wanam
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your device
* Open new Command Prompt for manual input
* Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
* Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
* Display Important Information about your device
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: As the exe files are not Digitally Signed with a Microsoft Certificate they 'may' get picked up as potentially harmful by Antivirus Programs and deleted on first run. If this happens restore the file and exclude it from future scans to use it. This seems to happen mostly on AVG Free and Norton which is why I switched to BitDefender which is much better.
Credits: Chainfire for SuperSU, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE YOUR DEVICE. NOTHING IS RESTRICTED.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR 'AUTO UPDATES' DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE 'QUICK PICKS' SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE "ANY BUILD" OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD (USEFUL IF YOUR BUILD IS NOT LISTED).
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
USEFUL INFORMATION
How to get into Recovery Mode
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.

**FAQ**
Q. Help me I can't find my build in the Model Selection Screen
The Toolkit includes a selection of Insecure Boot Images to cover all the different builds available. As there are very many different builds it is impossible to include an image for every single build but some builds share the same Boot Image. If you have a build that isnt listed on the Model Selection Screen you can therefore use a similar build. The best way to go is up to the next available build as it should offer more compatibility with the build you are using but if that isn't available then try the next build below your one as it should still be almost identical as long as it is the same version (ie. 4.1.1).
The Model Selection Screen is there so that if a task in the ToolKit requires an insecure kernel [to perform adb root commands] and your phone doesnt already include one, a compatible boot image [with an insecure kernel included] can be flashed to provide adb root access.
If you have a Custom Rom flashed to your phone then it will most probably have an insecure kernel included so it doesn't really matter if your build is not listed on the Model Selection Screen and when asked [by certain functions] if you have an insecure kernel on your phone you can answer 'yes'. However if the function fails then your kernel may not be insecure in which case you can flash one from the ToolKit. If you need to do this make sure the right build [or closest available build] is set so you flash the right image for your phone.
----------------------------------------------------------------------------
Q. What is ADB Shell?
Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF like removing system apps.
----------------------------------------------------------------------------
Q. Why do I need to back up my IMEI/EFS and how do I do it?
There well protected section of your device that is virtually immune to any kind of flashing and manipulation (unless of course you know how to access it). This part of the device contains information such as IMEI (or MEID and ESN in the case of CDMA devices), programming parameters for the device such as your account information (phone number, etc), data provisioning parameters, and a whole bunch of other things that, when not handled properly, can render a device completely useless. All of these are contained in the infamous \EFS folder. If anything messes with your EFS folder, unlike flashing a device (which could potentially lead to bricks as well) it could render your device completely useless as it will no longer be recognized by your carrier. If you are not planning on flashing anything to your device and want to stay on pure Stock then you may never have any problems but it is still advisable to backup this information just in case (better to be safe than sorry). If you have a GT-I9300 GSM Model then you can do this from the Toolkit but if you have an LTE device then it isn't soo easy to do. If you have an LTE device you should go to *THIS* thread by lyriquidperfection and follow the information to save your IMEI/NV Data so that you are covered if anything should happen.
----------------------------------------------------------------------------
Q. Is there currently no way to root the Samsung Galaxy S3 without voiding the warranty?
All methods of rooting will void your warranty in some way as you will have superuser files on your phone that arent supposed to be there. There is a method of rooting your phone without increasing the flash counter which involves flashing a complete rom with root files already added but if anything happens and you need to send it back under warranty you will need to flash a 'proper' Stock Rom back before returning it or your warranty will be void. Flashing a custom kernel or recovery to root will increase the flash counter and also void any warranty. There is currently no method of resetting the flash counter on Snapdragon models but im pretty sure there will be some support for it soon. If you dont want to risk it or you aren't sure then you shouldnt really be flashing your phone and should just leave it alone. Its your choice .
----------------------------------------------------------------------------
Q. Will flashing Stock ROM via odin using the toolkit replace everything that was flashed before? recovery? etc?
Yes a Stock Image flashed via Odin will replace all your key partitions (boot, recovery, system) with the stock firmware. If you want to reset the phone back to an 'out of the box' state then you want to enter recovery and do a wipe first which will reformat your userdata partition.
----------------------------------------------------------------------------
Q. I flashed Custom Recovery but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on certain Stock Android Builds that will reflash the Stock Recovery if you flash CWM on a Stock Rom.
Use Root Explorer to Mount the system folder as R/W (or use a free app from Google Play such as ES File Explorer). Rename the files /system/recovery-from-boot.p and /system/etc/install-recovery.sh (requires root). Now when you flash Custom Recovery it will NOT be overwritten after a reboot. You can also do this via the Toolkit.
----------------------------------------------------------------------------
Q. My AntiVirus program says the Toolkit files may be harmful
The exe compiled files are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton and AVG Free) may pick it up as potentially harmful when it is not. They will pick up ANY file that doesn't contain a purchased Microsoft certificate in the same way. Just Restore the deleted file and exclude it from further scans and it will be fine. Or switch to a better AntiVirus program such as BitDefender.
----------------------------------------------------------------------------
Q. I flashed the Toolkit Boot Image, now my wifi + bluetooth won't work
The boot images are made from Stock with only needed changes made to the insecure boot images [modified adbd, default.prop and rc.local edited] and will work on all stock roms. If you flash them to a custom rom and the rom has been altered or uses a custom boot image then it will boot but certain modules may not load such as wifi or bluetooth. In this case you can use the boot image to root or perform adb root functions but will need to flash back the boot image for the custom rom to get other functions working again. This is not a fault of the Toolkit but a difference to stock in the custom rom.
----------------------------------------------------------------------------
Q. I am having trouble getting adb working with the drivers installed
Try switching your connection type from media (MTP) mode to camera mode (P2P). To do this open the notification area, click where it says connected as and change from MTP to PTP.
----------------------------------------------------------------------------
Q. I want to send my device back for warranty purposes
1. Follow the instructions to reset your flash counter with TriangleAway.
2. Download and flash a Stock Firmware image from the download section.
3. Boot into Stock Recovery and perform a wipe/factory reset
.
Your internal storage will be formatted and data and cache wiped. Your device should now be back to an out-of-the-box FULLY STOCK state with the flash counter [shown if you boot to download mode manually] reset and ready to send back.
----------------------------------------------------------------------------
Q. When connecting the phone I get 'USB Device not Recognized' and no serial number shows in the ToolKit
I actually had this problem recently and what fixed it for me was to make sure that the drivers have been installed, then shut my phone down plug the usb cable in and restart it. The phone booted up and the device was recognized and drivers installed correctly. May not work for everyone but worth trying.

*reserved if needed*

Im in thank you for this I dont know if I need it just yet since I used the odin root method already but I have to the tookit on the desktop now as a goto.

Second! Nice to see you finished it. will try it out after i unbrick later

billard412 said:
Second! Nice to see you finished it. will try it out after i unbrick later
Click to expand...
Click to collapse
Let me know how it goes
Mark.

Hey Mark,
Good work. Thanks for doing this for us.
I have the Sprint variant and am trying to root it. I followed the steps in your tool kit. I installed the drivers first.
Then I tried to root using method 3. It ran along okay until I was Odin. I selected the file the toolkit told me to and got the point where it said "Reset" In the upper left hand corner. The phone rebooted but Odin never displayed "Pass" like it should. It just rebooted back into the normal mode.
What am I doing wrong?
Phone Specs:
Model SPH-L710
Android Version 4.0.4
Build: IMM76D.L710VPALF9
Thanks in advance.
--------------------
I just tried it again and got the same results. No "Pass" only "Reset!". Below is the message from Odin
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
---------- Post added at 07:13 PM ---------- Previous post was at 06:41 PM ----------
Well nevermind. I left the phone plugged in when I exited Odin and the Toolbox went through the rest of the sequence and alas... it is now root.
Not sure why it never said "Pass" but it is good to go now.
Thanks again for all you do.

you are awesome!
I have to wait for employees to be able to purchase the SGS3 before I get to use this toolkit!
Because I get an upgrade on my Evo 3D line and 200 bucks is way cheaper than 600!
EDIT: mskip... I love you... no homo! ...ok, maybe a little.

We love the British.
Thanks for this awesome tool.
Ian B

kapqh4 said:
Hey Mark,
Good work. Thanks for doing this for us.
I have the Sprint variant and am trying to root it. I followed the steps in your tool kit. I installed the drivers first.
Then I tried to root using method 3. It ran along okay until I was Odin. I selected the file the toolkit told me to and got the point where it said "Reset" In the upper left hand corner. The phone rebooted but Odin never displayed "Pass" like it should. It just rebooted back into the normal mode.
What am I doing wrong?
Phone Specs:
Model SPH-L710
Android Version 4.0.4
Build: IMM76D.L710VPALF9
Thanks in advance.
--------------------
I just tried it again and got the same results. No "Pass" only "Reset!". Below is the message from Odin
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
---------- Post added at 07:13 PM ---------- Previous post was at 06:41 PM ----------
Well nevermind. I left the phone plugged in when I exited Odin and the Toolbox went through the rest of the sequence and alas... it is now root.
Not sure why it never said "Pass" but it is good to go now.
Thanks again for all you do.
Click to expand...
Click to collapse
In case anyone else wants to know, after it resets the first time, wait for it to become recognized in Windows (the dialog box pops up), then if it still says Reset, restart the phone again, and wait again. It worked on both the AT&T and Sprint models I rooted today :good:

I tried the above method...
I get a e: verification failed. (bought the phone on the 3rd of July, applied the updates like an idiot).
I read I could get around this by pulling the battery right when it reboots...
doing so got me out of the e3 recovery and into the cwm recovery
Was able to flash the .zip...
yet... it's not rooted.

The best tool ever, ive been rooting since htc hero, this is the easiest tool ever:thumbup:. Thanks gonna stick with root, factory rom for now.
Message brought to you by my stock GalaxyS3

Thanks a million Mark. Worked like a charm on an S3 for Sprint.

Amazing tool works great. Thanks.
Sent from my SPH-L710 using xda premium

Thistleknot said:
I get a e: verification failed. (bought the phone on the 3rd of July, applied the updates like an idiot).
I read I could get around this by pulling the battery right when it reboots...
doing so got me out of the e3 recovery and into the cwm recovery
Was able to flash the .zip...
yet... it's not rooted.
Click to expand...
Click to collapse
The CWM root zip in the ToolKit is faulty. Try flashing the attached one from cwm and it should root you.
Mark.

Support Forums
Seems like the Link for the sprint Support Forum just loops back to this post, Anyone have problems after using the build.prop mods to remove the screen animations. My phone won't boot now.
Re-flashing stock now, and hoping it solves the problem, but wanted to check to see if anyone else had this problem.

using your 3.0.7
still nogo. I get into the cwm, and flash the zip, but using a root verifier = no root access.
hrmmmm....

jbrianj said:
Seems like the Link for the sprint Support Forum just loops back to this post, Anyone have problems after using the build.prop mods to remove the screen animations. My phone won't boot now.
Re-flashing stock now, and hoping it solves the problem, but wanted to check to see if anyone else had this problem.
Click to expand...
Click to collapse
I will have to look into the build.prop mods as they work fine on the International Edition of the ToolKit but maybe they work differently on Snapdragon models..
If anyone else has had a problem with the build.prop mods then please post as I dont have the Snapdragon version and rely on feedback to fix any bugs.
Flashing a stock Rom back to your phone will fix the problem.
Mark.

Thistleknot said:
still nogo. I get into the cwm, and flash the zip, but using a root verifier = no root access.
hrmmmm....
Click to expand...
Click to collapse
Root verifier isnt the best way to check root access, have you installed a root required app such as SetCPU or adfree and see if it asks for Superuser permission?
Mark.

When I try to launch the tool kit, the box pops up but then it says it cant find something then shuts the window down so fast I cant really read what it says..

[Heimdall One-click] FI27

This is Stock ROOTED deoxed FI27 OTA with agat recovery heimdall one click
Wanna learn more about Heimdall ?
http://www.glassechidna.com.au/products/heimdall/
Wanna learn about how to make your own one-click packages?
http://forum.xda-developers.com/showthread.php?t=1348392
Want AIO tutorial? Ask...
Credit goes toooo crawrj,Agat63,Adamoutler, and Benjamin Dobell, Chris41g,Sextape and anyone else who claims it lol or i forgot
I didnt do anything except know how to read and use a mouse so donate to the people i mentioned and not me . all credit goes to them for the respective files
Heimdall is cross platform compatible and open source this means it works on
LInux/Mac/WIndows
it is superior to ODIN
To run in linux open a Terminal where you downloaded the file and type
java -jar fi27rr.jar (or what ever you named the file)
mac and windows you just double click it
plug in your phone put in Download mode ( from it being off press and hold power+down) till splash or adb reboot download in console while on with adb on.
Caution this wipes data like Odin would and is safe to flash
DOWNLOAD Link:
fi27rr.jar - 352.40 MB
Enjoy!
Got a stupid triangle ? use triangle away. Id make a one click but the author asks to not redistribute. but it comes with a apk version and a tar version. Depending on what chainfire says ill make the next versions with it built in. Anyway heres the link:
http://forum.xda-developers.com/showthread.php?t=1494114

dos
ahhh mod please move this my bad its 6 in teh am here

Thanks again
i guess people should realise how handy these are gonna prove !!!

Thanks! I've been running linux and waitting for oneclicks!

Glad I can be of service if anyone wants anything else made in this manner lmk

As always, thank you for thee hard work.
Sent from my SPH-D710 using xda premium

I'm looking for known good firmware to use in heimdall for the Samsung Galaxy S II Epic 4G Touch by Sprint. It's a CDMA phone and finding firmware compatible with Heimdall is proving near impossible. I am studying my pit file to see if there is a way I can change my build files to output my binary image in the proper tar format for the d710. It's going to be a rather large undertaking, but if I am right, anyone would be able to provide me a pit file and if I'm correct, it would literally modify the manifest for android source, repo init for the flavor the user is looking for and build the heimdall image instead of the standard recovery image... It seems it would be easier though to take the standard flash image and strip from it the necessary stuff and repack it... Has anyone done this?

This is amazing have been waiting for this for a while as a mac user and it works well just tested. I hated switching to crappy windows to use odin thanks again 8D

slackguru said:
I'm looking for known good firmware to use in heimdall for the Samsung Galaxy S II Epic 4G Touch by Sprint. It's a CDMA phone and finding firmware compatible with Heimdall is proving near impossible. I am studying my pit file to see if there is a way I can change my build files to output my binary image in the proper tar format for the d710. It's going to be a rather large undertaking, but if I am right, anyone would be able to provide me a pit file and if I'm correct, it would literally modify the manifest for android source, repo init for the flavor the user is looking for and build the heimdall image instead of the standard recovery image... It seems it would be easier though to take the standard flash image and strip from it the necessary stuff and repack it... Has anyone done this?
Click to expand...
Click to collapse
thats pretty much what this is i think?
this is a known good firmware im kind of missing your point would you like just a tar package of the firm for just regular heimdall instead of a one click i can package that for you if you like... that is actually a feature of heimdall.. and you can download the pit from your current device as well to use for flashing open it and edit anyway you like. if you decompress the jar i provided you can pull the pit from it also.
you might need to elaborate a bit and ill see if I can help you.

manup456 said:
This is amazing have been waiting for this for a while as a mac user and it works well just tested. I hated switching to crappy windows to use odin thanks again 8D
Click to expand...
Click to collapse
yess meee toooo thats actually my reason for making this

@Dreamlogix
This plus the el29 is all wee need and continuing from here is great.
Quick question is there a way to this without messing with the flash count I have triangle away just would like to know also a data wipe version would be good just thinking also this should be a sticky for sure.

manup456 said:
@Dreamlogix
This plus the el29 is all wee need and continuing from here is great.
Quick question is there a way to this without messing with the flash count I have triangle away just would like to know also a data wipe version would be good just thinking also this should be a sticky for sure.
Click to expand...
Click to collapse
Hm i thought i enabled data wipe.. ill have to re-do it and ill post two versions (sticky on my second contribution? ) that would be amazing If a mod wants to sticky ill maintain it im pretty sure you just have to message them.
to get rid of the triangle i use triangle away here is the link it will reset your flash counter and get rid of the triangle redistribution is not allowed per order of the maker
i messaged chainfire to see if he will allow me to make a one click triangle away heimdall package for convince i can send you that one click privately but i cant post it. id like to integrate it for the later ones.
http://forum.xda-developers.com/showthread.php?t=1494114
but good point ill add that link to the op
thanks for being supportive i knew SOMEBODY could use it.
quick question did you test my el29 everything work out?

@ Dreamlogix
Yeah bro plz do send me that, and yeah i use triangle away just a one click all good it's always a plus. I appreciate this a lot.

manup456 said:
@ Dreamlogix
Yeah bro plz do send me that, and yeah i use triangle away just a one click all good it's always a plus. I appreciate this a lot.
Click to expand...
Click to collapse
cool should be in your pm do you currently got a yellow triangle? id like you to test it out and report back
upon investigation it seems to only remove the triangle image and not reset the flash counter. I inquired in CF' thread im pretty sure ill be able to come up with a package if he allows me

Dreamlogix said:
thats pretty much what this is i think?
this is a known good firmware im kind of missing your point would you like just a tar package of the firm for just regular heimdall instead of a one click i can package that for you if you like... that is actually a feature of heimdall.. and you can download the pit from your current device as well to use for flashing open it and edit anyway you like. if you decompress the jar i provided you can pull the pit from it also.
you might need to elaborate a bit and ill see if I can help you.
Click to expand...
Click to collapse
Great! That was what I meant to say. I am looking for the firmware files. I'm not interested in a one click although I may end up using it one day. I am in learning mode and you might as well say I am from Missouri... So as I said before, I am actually looking for known good "firmware" and it's great news that I can simply extract it from the jar. That sounds pretty straight forward. Does the jar include images, bins, lfs img and all that? I've been doing some study and there are 15 partitions on the SPH-D710, 7 of which are in use during runtime, 2 of which are in use at recovery and I still haven't figured out how to tell whats going on in the download state. No offense intended, but I am really more interested in learning to fish rather than eat from your catch if you know what I mean.
I found a description of what is called EMMC booting where after mapping out the layout of the partitions you build an x-loader appended with RAW eMMC headers, u-boot build system initramfs structure, the kernel's zImage except they called it uImage I guess for the u-boot system and the rest including system.img, userdata.img and cache.img. These instructions are fairly precise but they aren't written for our device even though our device does contain the hardware they refer to, the am37xevm. That's where they stop though. They don't get into the GANG partition, BOOT, EFS, SBL1 and 2 which I believe are the bootloader combined in one logical partition across 2 logical devices. Then there's the hidden partition which is looking for the hidden.img when performing a complete flash.
I am only wanting to be this thorough because I want to learn all I can and I believe that if I could make the serial interface active during boot up I could load this type of OS, external to the phone and make all of the partitions simultaneously available to manipulate. This would solve a lot of people's problems with the triangle and counter. Hell, I believe that with a large enough space your preexisting ROM could be completely backed up prior to flashing and then nothing would be stopping a completely new partition layout.
Just food for thought and I will grab that jar and see what I can't squeeze out of it. Thanks for letting me know. I didn't realize you left the jar open.

Dreamlogix said:
Hm i thought i enabled data wipe.. ill have to re-do it and ill post two versions (sticky on my second contribution? ) that would be amazing If a mod wants to sticky ill maintain it im pretty sure you just have to message them.
to get rid of the triangle i use triangle away here is the link it will reset your flash counter and get rid of the triangle redistribution is not allowed per order of the maker
i messaged chainfire to see if he will allow me to make a one click triangle away heimdall package for convince i can send you that one click privately but i cant post it. id like to integrate it for the later ones.
http://forum.xda-developers.com/showthread.php?t=1494114
but good point ill add that link to the op
thanks for being supportive i knew SOMEBODY could use it.
quick question did you test my el29 everything work out?
Click to expand...
Click to collapse
When I saw this post I said Amen! Dreamlogix, you can include me in that tar ball for the reset counter too!

Totally embarrassed ... RTFF
Dreamlogix said:
This is Stock ROOTED deoxed FI27 OTA with agat recovery heimdall one click
Wanna learn more about Heimdall ?
http://www.glassechidna.com.au/products/heimdall/
Wanna learn about how to make your own one-click packages?
http://forum.xda-developers.com/showthread.php?t=1348392
Want AIO tutorial? Ask...
Credit goes toooo crawrj,Agat63,Adamoutler, and Benjamin Dobell, Chris41g,Sextape and anyone else who claims it lol or i forgot
I didnt do anything except know how to read and use a mouse so donate to the people i mentioned and not me . all credit goes to them for the respective files
Heimdall is cross platform compatible and open source this means it works on
LInux/Mac/WIndows
it is superior to ODIN
Click to expand...
Click to collapse
with the exception of the triggering of the counter
To run in linux open a Terminal where you downloaded the file and type
java -jar fi27rr.jar (or what ever you named the file)
mac and windows you just double click it
plug in your phone put in Download mode ( from it being off press and hold power+down) till splash or adb reboot download in console while on with adb on.
Caution this wipes data like Odin would and is safe to flash
DOWNLOAD Link:
fi27rr.jar - 352.40 MB
Enjoy!
Got a stupid triangle ? use triangle away. Id make a one click but the author asks to not redistribute. but it comes with a apk version and a tar version. Depending on what chainfire says ill make the next versions with it built in. Anyway heres the link:
http://forum.xda-developers.com/showthread.php?t=1494114
Click to expand...
Click to collapse
If the execution of the jar causes a yellow triangle you should build in the functionality of wiping the triangle and counter automatically whether or not Chainfire likes that it's there. If the fix is open source and not given to you by Chainfire what harm can it do, I know Chainfire is selling the Triangle Away app, to make a flash that does not cause the triangle? Isn't that what a flash is supposed to do? Go on the phone without incident? I was thinking to ask for your guidance with this project to further it. I made a "jig" that actually has an SD card recepticle wired to it and I thought that maybe I could get the entire flash to boot "outside" the device so the spanning eMMC parttions could be rendered harmless. We could then at that point extract necessary proprietary code from the phone to integrate into the flash as it builds out on the phone on the fly. I appreciate the respect you gave to Chainfire though in not releasing the code you have to repair the triangle... I know if I look long enough and hard enough I will find it soon too, but it would be nice if both you and Chainfire shared without $ 2.00.
I really am eating my words here. Thanks and heavy shout outs to Chainfire for including TriangleAway-v2.10.apk on another post. I do still think that if the Heimdall Oneclick is known to cause the counter that some obscure coding in it to remove it would be prudent.
Then also, since I haven't done so yet, GREAT JOB on the Oneclick to Dreamlogix. The best idea I've had all day. I much prefer to use the opensource flash utility to ODIN. Thanks for both of your very hard work. It is appreciated.

My bad you cannot extract it out of the jar and Odin triggers the triangle also I and in not allowed to repackage chain fires code solo I can't make that for you guys sorry

Also do you want 100% stock with no root and stock recovery and to answer your question we do not have a gang or efs ( because its a cdma device) but we do have sbl1 and boot no sbl2 and yes they are part of the bootloaders efs is part of where the serial and some modem stuff is stored on gsm phones i believe.
sorry for the poor english been a long night lol
edit update if anyone boot loops at the 4g logo YOU ARE NOT BRICKED dont panic use a oem cable.

FAIL!
Alright, I attempted to flash, my already rooted SPH-D710 by executing sudo java -jar fi27rr.jar and this is what is happening:
First the GUI reports differently than the cli behind the scenes. Here is the out put from the Oneclick screen;
Operating System: Debian Based i686
Found Heimdall Version: Heimdall version is out of date.
Connect your device in Download Mode to procede.
Device Connected. Awaiting package preparation.
FI27+agat kernel+recovery FI27 is ready for your device.
Repartition was requested but bootloaders are not to be flashed.
Omiting Bootloaders.
KERNEL RECOVERY MODEM FACTORYFS HIDDEN
Heimdall v1.4 RC1
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Session begun.
Downloading device's PIT file...
PIT file download successful.
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
Click to expand...
Click to collapse
Immediately following my device reboots. I suspect there is something wrong with the recovery partition itself. I am also experience an error when entering the download recovery that further indicates issues with the recovery partition. The recovery.do file has some specific commands referencing the CSC that can not complete because /system/etc/csc does not exist... another strange note, the GUI thinks PIT failed but the command line says otherwise and even stranger the GUI also says other wise:
View attachment 1415566
Meanwhile, back at Gotham, the CLI is sitting and waiting for the GUI to complete it's job which never happens and this is the output within the CLI:
sudo java -jar fi27rr.jar
[sudo] password for jeffrey:
Operating System: Debian Based i686
Found Heimdall Version:
Connect your device in Download Mode to procede.
Device Connected. Awaiting package preparation.
Total PITEntry Count: 15
Pit Complete.
Partition Targeted:1-BOOT
Partition Targeted:2-SBL1
Partition Targeted:10-FACTORYFS
Partition Targeted:13-HIDDEN
Partition Targeted:9-MODEM
Partition Targeted:6-KERNEL
Partition Targeted:5-PARAM
Partition Targeted:7-RECOVERY
FI27+agat kernel+recovery FI27 is ready for your device.
Total PITEntry Count: 15
Pit Complete.
Partition Targeted:1-BOOT
Partition Targeted:2-SBL1
Partition Targeted:10-FACTORYFS
Partition Targeted:13-HIDDEN
Partition Targeted:9-MODEM
Partition Targeted:6-KERNEL
Partition Targeted:5-PARAM
Partition Targeted:7-RECOVERY
[heimdall, flash, --pit, /tmp/rootHeimdallOneClick2ACBA745/pit.pit, --6, /tmp/rootHeimdallOneClick2ACBA745/zImage, --7, /tmp/rootHeimdallOneClick2ACBA745/recovery.bin, --9, /tmp/rootHeimdallOneClick2ACBA745/modem.bin, --10, /tmp/rootHeimdallOneClick2ACBA745/factoryfs.img, --13, /tmp/rootHeimdallOneClick2ACBA745/hidden.img]
<<<<<<<<<<< this is where the cursor hangs
Click to expand...
Click to collapse
This is the contents of /tmp/rootHeimdallOneClick2ACBA745/ :
drwxr-xr-x 3 root root 4096 Oct 19 14:56 .
drwxrwxrwt 21 root root 12288 Oct 19 17:17 ..
-rw-r--r-- 1 root root 131072 Oct 19 14:54 boot.bin
-rw-r--r-- 1 root root 486481476 Oct 19 14:56 factoryfs.img
-rw-r--r-- 1 root root 878 Oct 19 14:56 firmware.xml
-rwxr--r-- 1 root root 42268 Oct 19 14:55 heimdall_i386.deb
-rw-r--r-- 1 root root 8626468 Oct 19 14:56 hidden.img
-rw-r--r-- 1 root root 9111 Oct 19 14:57 log.txt
-rw-r--r-- 1 root root 15466656 Oct 19 14:56 modem.bin
-rw-r--r-- 1 root root 1060864 Oct 19 14:56 param.lfs
-rw-r--r-- 1 root root 4096 Oct 19 14:56 pit.pit
-rw-r--r-- 1 root root 8387840 Oct 19 14:56 recovery.bin
drwxr-xr-x 2 root root 4096 Oct 19 14:55 ROMPACKAGE
-rw-r--r-- 1 root root 1310720 Oct 19 14:54 Sbl.bin
-rw-r--r-- 1 root root 7476524 Oct 19 14:56 zImage
Click to expand...
Click to collapse
... and the ROMPACKAGE directory is empty. Now, I opted NOT to install the 1.31 Heimdall because I have a newer version. I am currently running 1.4-RC1 compiled from source out at BatMan's website (Benjamin Dobell - https://github.com/Benjamin-Dobell/Heimdall). The phone didn't act like this before I completed my first flash. I played around with the cli and the frontend with the pit file and the likes. It was nice I could load my own pit file and it recognized my device without restarting it. Then comes my first flash... it was StockCWM-EL26.zip that I extracted to a folder and simply flashed Kernel using zImage. The flash took, sort of, CWM showed up but none of my partitions could be recognized, at least none that counted. I couldn't mount internal or external storage... all the system partitions were fine. I downloaded that REPACK from chris41g's repo and that was why I was surprised it didn't work and suspect hardware issues. During this flash this is the PIT i used sph-d710.pit, if you even need it.
My next plan is to see if I can attempt repair of the troubled partitions. I hear that /dev/zero is going to be my friend for a bit, but I'm not looking forward to it. Worse comes to worse I'll be reactivating my crespo4g for a bit. It's been running CM10 reliably for a long while now. I'd be glad to part with contact info if you felt like brainstorming. My gmail should be on my profile page because of jabber... The phone is still working well so feel free to GTalk me if you want. I only hope I'm not truly as incompetent as this post makes me sound.
Fight the good fight, keep the faith!
Slackguru

[Q] Baseband: Unknown, Modem boot timeout, Couldn't find 'rild' socket.

Hello all and a good day.
Device: Samsung Galaxy Note 8.0 GT-N5100 (3G) - XME (Malaysia)
What I did: Nothing unusual! Device mainly used for text reading and some writing. After updated to Android 4.2.2 (PDA: N5100XXCMI1, CSC: N5100OLBCMH2, MODEM: N5100XXCMI1) via ODIN, the symptom # 1 appeared. The firmware for Malaysia was downloaded from the sammobile.com.
Same time I came to know the importance of /efs backup, so rooted (1st time) the device, backed-up /efs via EFS Pro, used Triangle Away, unroot, and flashed the stock. Since the symptom # 1 continued, I did a factory reset, and then all other symptoms appeared.
Symptoms:
1) Tablet doesn’t vibrate.
2) Kies is unable to detect the tablet.
3) SIM Cards are not detected. A prohibition sign is shown at the cell signal (left to the battery indicator) (see image 1).
4) In “Settings > About device”, and in “Settings > About device > Status”, many fields are stated as “Unknown”, e.g.:
Baseband and IMEI (see image 1 and image 2). Incorrect Serial number (/efs has the correct one as in the back cover).
5) Camera view is upside down.
6) Proximity sensor doesn’t work. In the *#0*# Test mode, Proximity value is 1.0. If exit and check again value becomes 0.0.
7) Regardless of Flight mode or not Cell standby drains the battery a lot. Once activated, Flight mode turns grey (see image 3).
8) [SOLVED, see 5th post] Several times (not always), a white screen appeared at the boot screen (model name), and also when plugged to power source while the tablet switched off. I guess something to do with param partition.
9) [SOLVED, see 5th post] "No command" error message in the stock recovery (3e).
9) “Modem boot timeout” and “Couldn't find 'rild' socket” errors in logcat -b radio.
10) When tried to use the tablet as a modem from Windows 7, it gives an Error 692, and the diagnostics states, “Timed out waiting for response from modem”.
Solutions tried (no success): As many, I too tried various /efs based solutions mentioned in XDA, and flashed all the five firmwares available for the device, but the problem stays same. I tried to solve this without troubling others much, but now I am lost.
Help needed: Is this problem can be fixed by me with some guidance, which would be great since to claim warranty the tablet need to be send to another country. Or is it a hardware problem, therefore I should send it straight to Samsung service without wasting more time?
Attached files, if they help:
1) Outputs of the following commands
logcat -b radio
logcat *:E
dmesg
ls -la /efs
ls -la
mount
cbd -t xmm626x -o t
2)
- recovery log from - CivZ_rev1.1-PhilZ 5.1.1 (touch)
- build.prop file
Thank you for reading. Greatly appreciate any help and guidance. Sorry, if I violate any XDA rules in this post. Kind regards!

New Problem: "There is no PIT partition."
Last night managed to fix a part of the problem (customer.xml error in logcat) in the above post thanks to the guidance from civato. In an attempt to fix other problems, last night I had mistakenly executed the following cmd in ADB while in recovery.
Code:
dd if=/data/media/0/efs.img of=/dev/block/[B]mmcblk0[/B]
The correct one should have used is mmcblk0p3 (/efs partition in Note 8.0). At least I managed to do some damage, otherwise all the credit goes to Samsung.
Now I can go to download mode only. A white screen flashes if try recovery mode or normal boot or even connect to a power source to recharge. Since charging or not also unsure (before this happened battery was 100%), I have a limited time to use the device to get it to work properly. Other problem is, if fail, can’t claim warranty as there’s no way to use the Triangle Away in this situation.
Now when try to flash via ODIN:
1) normal way - it failed stating, "There is no PIT partition." (see image 1).
2) with kona3g.pit I have - it failed stating, "Re-partition operation failed." (see image 2).
Even when the device was working properly, 2nd option never worked for me.
My kona3g.pit read well by PIT Magic 1.3.10.
Can anyone provide me a working .pit for Note 8 GT-N5100. Thinking of trying Heimdall Suite 1.4.0 tonight, but need some reading as I never used it and limited battery time for flashing.
Any advice to recover my device is highly welcome.
King regards.

Here you go, unzip it and in Odin select repartition and then Odin a new stock rom. (PDA)
Or look here for the 5110 pit file it should alos work on the 5100 as the modem partition is also created.
reinstall your csc also after rom onstallation
PS try the included Odin

Working kona3g.pit for GT-N5100
civato said:
Here you go, unzip it and in Odin select repartition and then Odin a new stock rom. (PDA)
Or look here for the 5110 pit file it should alos work on the 5100 as the modem partition is also created.
reinstall your csc also after rom onstallation
PS try the included Odin
Click to expand...
Click to collapse
Brilliant and thank you! The Odin3_v3.07.exe you provided missing an Odin3.ini (see image). I used an Odin3.ini (see attached files) that I have (for the same version) together with your Odin3_v3.07.exe and kona3g.pit, and the flashing went perfectly without any errors. So your kona3g.pit is a genuine working one. Thank you
I’ll continue further tonight and post here. My friend share his laptop with me, therefore I have limited time.
EDIT: When looked from the PIT Magic 1.3.10, the GT-N5110.pit is same as the GT-N5100 one (kona3g.pit). But when looked from the HxD - Hexeditor 1.7.7.0, the signatures at the end of the files are different, so it might not work on the sister device. Also, your GT-N5110.pit has trailing zeros after the signature, somewhere I read that these zeros must be deleted from a hexeditor for it to work.
Kind regards!
Image:

Solutions for symptoms 8 & 9
Solution for symptom 8:
Googled for a param.bin for Note 8.0, but only found one for Galaxy S3. Anyway, being fed up with the white screen, I copied S3 param.bin to the mmcblk0p4 partition of Note 8.0, surprise it worked. But the boot screen became S3 . Later among my backups, I found a param backup of mmcblk0p4 that I took via EFS Pro. Unfortunately couldn't restore it via EFS Pro as I had renamed the tar.gz to keep things tidy. So I extracted it to get a file called param. Since this param didn't work after copying, I compared it in the hex editor with the working S3 param, and noticed EFS Pro add some data to the beginning of the file. I removed this begining data and also the trailing zeros, and renamed it to param.bin (to go along with the name in kona3g.pit, perhaps not necessary). Finally, copied it by "dd if=/sdcard/param.bin of=/dev/block/mmcblk0p4" command, after couple of reboots white screen disappeared.
Solution for symptom 9:
Difficult to say this is a solution but it disappeared after this. In order to send for warranty claim, I restored the device to clean stock. First used Triangle Away to reset the counter. Booted and fully unroot via SuperSU. Then flashed the stock rom with the pit file, and without restart option. Shut down the device and boot into the recovery to do a full wipe, and the "No command" error wasn't there.
I must say, since my modem not working, capslock66's Android Reverse Tethering 3.15 saved my day to download the required Triangle Away add-on via laptop's broadband connection.
Since all other symptoms couldn't be solved my me after much effort, I sent the tablet for Samsung service.

Custom Binary Blocked by FRP Lock - How I Fixed It Without Data Loss

YMMV.
Proceed to read at your own risk. This is intended for informational purposes only. I am not responsible for anything here.
So my wife's Sprint S6 displayed the error of "Custom binary blocked by FRP Lock". This was caused by Developer Options being turned off, then the device was rebooted.
In order to fix it, I tried so many things, including making an attempt to install 6 different versions of the ROM for this phone. I tried 4 different USB cords, tried all of the USB ports on my computer, and even went and grabbed the newest Odin, 3.12.3. None of the flashes worked, because they all failed, as shown below:
Code:
Added!!
Enter CS for MD5..
Binary Check MD5.. Do not unplug the cable..
Please wait..
Checking MD5 finished Sucessfully..
Leave CS..
Odin engine v(ID:3.1100)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
I did loads of research and found out that you (obviously) can't install a version lower than the currently installed version, and I couldn't remember what the current version was on her phone. However, I found many success stories telling how the currently installed version was successfully Odin flashed onto a device exhibiting the same issue as mine, but it never worked for me.
I spent a few more hours this morning researching this issue because I did not want to lose the data that was on my wife's phone, because I care about keeping her happy Amazingly, I tried something I read on a whim, expecting it to not work.
Using Odin 3.12.3, I downloaded QB1 from koop1955's thread. I verified the MD5 before doing anything else with the file. Then, I unzipped that download to produce a file ending in .tar.md5. I then deleted the extension .md5 from that filename, and put it into the AP slot in Odin. Odin didn't give any output (because it didn't do the md5 check that it would normally do). I then clicked Start. The flash worked!! The phone successfully flashed, and no data was lost at all. I am so damn happy!
tl;dr
0. Put phone into download mode. From an off state, press and hold Volume Down, Home, and Power til you get the blue screen, then press Volume Up to enter download mode. Plug it into your computer using a good USB cable.
1. Download QB1 from koop1955's thread
2. Unzip that download once.
3. Put the unzipped file into the folder in which Odin exists.
4. Delete .md5 from the filename. It should end in .tar now.
* If you don't see .md5 on the end of the filename:
* If you do not see file extensions, on W10, go to Control Panel\Appearance and Personalization. click File Explorer Options. Click the View tab. Place a check mark by the line labeled "hide extensions for known filetypes". Boom.
5. Click the AP button in Odin, then select that file you just renamed.
6. Click start in Odin. Let it flash. It should work.

"1. Download QB1 from koop1955's thread"
Yeah, that koop1955 character is one heck of a guy...or so I hear.
Glad this worked out for you.

koop1955 said:
"1. Download QB1 from koop1955's thread"
Yeah, that koop1955 character is one heck of a guy...or so I hear.
Glad this worked out for you.
Click to expand...
Click to collapse
He's crazy if you ask me
Sent from my SM-G920P using Tapatalk

I have the same problem with my samsung galaxy sm-j120f and I can't seem to fix it

fentezi said:
I have the same problem with my samsung galaxy sm-j120f and I can't seem to fix it
Click to expand...
Click to collapse
First off, you should probably post in the correct forum.
Secondly, did you try flashing the firmware for your phone: https://www.sammobile.com/firmwares/galaxy-j1/SM-J120F/

I fixed it
All i had to do is change the firmware extension to .tar instead of .tar.md5 and flash it:laugh:

My SAMSUNG G928P was flashed a 3rd firmware. l have a same issue which cause the device can't boot the system. And now still the same way appears red on the left conner 'custom binary blocked by frp lock'. I tried officiall firmware as you did, it can flashed successfully, just stuck in the SAMSUNG logo. HELP ME PLEASE, Dont want to lose the data.

THANK YOU
I just wanted to say thanks. This post helped me out a lot. I spend about 4 hours trying to fix this issue then found your post and had it done in a matter of minuets. I used to do this a lot back in days and I'm getting back into this. I got a lot of reading to do. Thanks for the post again!

killroot said:
I just wanted to say thanks. This post helped me out a lot. I spend about 4 hours trying to fix this issue then found your post and had it done in a matter of minuets. I used to do this a lot back in days and I'm getting back into this. I got a lot of reading to do. Thanks for the post again!
Click to expand...
Click to collapse
Hey! Glad it helped. I was really active back in the HTC Hero days and around 2013 I slowed down. I like to keep my phones rooted but i getting more and more worried about manufacturer warranty being denied over being rooted... Fortunately I was able to iron this whole thing out with some meticulous research and some help from awesome people here, and it's still satisfying knowing I've helped at least one person who appreciated it enough to say thanks!
Sent from my SM-N920P using Tapatalk

finalc said:
My SAMSUNG G928P was flashed a 3rd firmware. l have a same issue which cause the device can't boot the system. And now still the same way appears red on the left conner 'custom binary blocked by frp lock'. I tried officiall firmware as you did, it can flashed successfully, just stuck in the SAMSUNG logo. HELP ME PLEASE, Dont want to lose the data.
Click to expand...
Click to collapse
Sorry, not sure what the g928p is and unfortunately I can't help with your issue. I just wrote what I did to fix this issue and if you're still having problems I recommend doing some very in depth research to make sure you didn't miss some tiny but crucial step.
Sent from my SM-N920P using Tapatalk

fentezi said:
All i had to do is change the firmware extension to .tar instead of .tar.md5 and flash it[emoji23]
Click to expand...
Click to collapse
That's what the instructions said to do [emoji6]
Glad it worked.
Sent from my SM-N920P using Tapatalk

Same issue on my Samsung A%
The file is not there anymore bro. Where do i get the file for my device please(Samsung A5) ? i found a way to solve this using kies 3 and wiping the phone. But u did it without data loss? amazing ! glad if you can help. thanks!
jerry43812 said:
YMMV.
Proceed to read at your own risk. This is intended for informational purposes only. I am not responsible for anything here.
So my wife's Sprint S6 displayed the error of "Custom binary blocked by FRP Lock". This was caused by Developer Options being turned off, then the device was rebooted.
In order to fix it, I tried so many things, including making an attempt to install 6 different versions of the ROM for this phone. I tried 4 different USB cords, tried all of the USB ports on my computer, and even went and grabbed the newest Odin, 3.12.3. None of the flashes worked, because they all failed, as shown below:
Code:
Added!!
Enter CS for MD5..
Binary Check MD5.. Do not unplug the cable..
Please wait..
Checking MD5 finished Sucessfully..
Leave CS..
Odin engine v(ID:3.1100)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
I did loads of research and found out that you (obviously) can't install a version lower than the currently installed version, and I couldn't remember what the current version was on her phone. However, I found many success stories telling how the currently installed version was successfully Odin flashed onto a device exhibiting the same issue as mine, but it never worked for me.
I spent a few more hours this morning researching this issue because I did not want to lose the data that was on my wife's phone, because I care about keeping her happy Amazingly, I tried something I read on a whim, expecting it to not work.
Using Odin 3.12.3, I downloaded QB1 from koop1955's thread. I verified the MD5 before doing anything else with the file. Then, I unzipped that download to produce a file ending in .tar.md5. I then deleted the extension .md5 from that filename, and put it into the AP slot in Odin. Odin didn't give any output (because it didn't do the md5 check that it would normally do). I then clicked Start. The flash worked!! The phone successfully flashed, and no data was lost at all. I am so damn happy!
tl;dr
0. Put phone into download mode. From an off state, press and hold Volume Down, Home, and Power til you get the blue screen, then press Volume Up to enter download mode. Plug it into your computer using a good USB cable.
1. Download QB1 from koop1955's thread
2. Unzip that download once.
3. Put the unzipped file into the folder in which Odin exists.
4. Delete .md5 from the filename. It should end in .tar now.
* If you don't see .md5 on the end of the filename:
* If you do not see file extensions, on W10, go to Control Panel\Appearance and Personalization. click File Explorer Options. Click the View tab. Place a check mark by the line labeled "hide extensions for known filetypes". Boom.
5. Click the AP button in Odin, then select that file you just renamed.
6. Click start in Odin. Let it flash. It should work.
Click to expand...
Click to collapse

i just had the same problem on my mothers phone and your method worked perfectly thank you so much i didnt want to do a stock flash and have her loose everything so thanks for your knowledgeable and easy to follow post

Hello @jerry43812 and @koop1955 that file has been deleted from android file host, would any of you please care to upload it again? Thanks very much. I have a Samsung Galaxy Note 5 btw, I think it works right?

I dont even remember making this thread, I definitely dont have the file you're looking for. Maybe koop can help.Sorry!

@koop1955 I don't have knowledge about any of the android OS. But I have an issue and it still is an issue from 2016 to 2022. I have an android phone launched in 2016. I rooted it using SuperSU binary. By turning ON all the necessary features required for making custom recovery (TWRP) installed and installing SuperSU binary as well.
Therefore my developer options were turned ON and OEM unlocking was ON aswell. My phone name was Samsung J2 2016 (SM-J210F). I by mistake disabled OEM unlocking switch. And restarted the phone and it never
rebooted after that.
I need the data it is very precious to me. I don't need root privileges back or anything like that.
I just need the data and state of operating system the way it was before restarting.
Please help me @koop1955.
I will be very thankful to you.

I have no idea. Good luck.