Related
Hi,
With the release of Galaxy Tab Gingerbread 2.3.3 by Chainfire
( http://forum.xda-developers.com/show....php?t=1073854 ), I intend to update my Galaxy Tab (running Froyo 2.2) to Gingerbread. Since I use only Linux in my computer, the only option to flash my Tab is to use Heimdall ( http://www.glassechidna.com.au/products/heimdall/ ).
What I wish to know is:
1. The procedure using Odin calls for repartitioning. Is it okay to repartition using Heimdall?
2. There is a file called hidden.rfs in the official stock rom provided by Chanifire. How do I flash this hidden.rfs using Heimdall? Heimdall accepts only the following arguments as per it's man page:
action: flash
[--pit <filename>] [--factoryfs <filename>] [--cache <filename>]
[--dbdata <filename>] [--primary-boot <filename>]
[--secondary-boot <filename>] [--secondary-boot-backup <filename>]
[--param <filename>] [--kernel <filename>] [--recovery <filename>]
[--efs <filename>] [--modem <filename>]
(Nowhere is any mention of hidden.rfs. I am confused as how to include it while flashing my Galaxy Tab).
3. Do I flash dbdata.tar in the first shot along with the firmware? Or do I need to flash dbdata.tar after rebooting the Galaxy Tab as instructed by Chainfire?
If someone can help me, I would very much appreciate it.
Thanks in advance.
1st of all. Im a windows user, my answers would relate to my experience using heimdall under windows and not under linux. Though i believe they would behave jjust the same.
1. From my experience uaing heimdall. Heimdall does partitioning juat as good as odin.
2. I don't know how it behaves in linux, butwhen i used heimdall to flash my tab i just put all the files in the same folder and the hidden.rfs seems to have been flashed as well.
3. You could flash the dbdata.rfs with the other firmware files in one flashing.
Cheers.
noxxious said:
1st of all. Im a windows user, my answers would relate to my experience using heimdall under windows and not under linux. Though i believe they would behave jjust the same.
1. From my experience uaing heimdall. Heimdall does partitioning juat as good as odin.
2. I don't know how it behaves in linux, butwhen i used heimdall to flash my tab i just put all the files in the same folder and the hidden.rfs seems to have been flashed as well.
3. You could flash the dbdata.rfs with the other firmware files in one flashing.
Cheers.
Click to expand...
Click to collapse
Thank you noxxious for your help.
Heimdall being a multiplatform open source program, it is supposed to behave consistently in all platforms (Linux/Windows/Mac).
I was told by user jkurl15 in thegalaxytabforum (sorry XDA won't allow me to post the link) not to repartition using Heimdall as it might brick the Galaxy Tab. Can you please throw some light on this?
Did you use the repartition option in Heimdall when you flashed your Galaxy Tab?
As regards to the hidden.rfs file, from what I noticed after concatenating the gt-p1000_mr.pit, is that it contains a mention of hidden.rfs inside it. Don't know if it helps.
Thank you once again.
If done correctly repartioning via heimdall will not cause a brick. Especially if all files that you would use is from 1 tar package in this case the gingerbread package.
Ive done repartioning via heimdall on my tab way back when i was still on jk2. It did a pretty good job restoring my tab.
Thanks for your insight. It was really a great help. I will give heimdall a try to flash my galaxy tab.
What is your opinion regarding the bootloaders present in the gingerbread rom? I have an unbranded unlocked galaxy tab and don't want to restrict myself by flashing any signed bootloader. Do you think I can flash my tab with gingerbread rom without the bootloaders?
Sent from my GT-P1000 using XDA App
Hi, did you succeed? If so, any news on how to upgrade?
I've done: heimdall flash --pit gt-p1000_mr.pit --factoryfs factoryfs.rfs --cache cache.rfs --param param.lfs --kernel zImage --modem modem.bin
Using http://www.samfirmware.com/WEBPROTECT-p1000.htm and both 1_EUR pit and gt-1000_m I can't load the firmware.
I get Optional PIT check failed! To disable this check don't use the --pit parameter.Ending session...
Rebooting device...
Re-attaching kernel driver...
Any ideaS?
SO.. Just to clarify for all Linux users..
Am I correct in thinking :-
1) Back everything up.
2) Extract The base 2.3 GB-stock-safe.zip into a folder, and the .tar file you should use in ODIN (GB_Stock_Safe_v1.tar) , that one comes from the Overcome 2.0 BETA2 download.
3) Copy the gt-p1000_mr.pit and the correct modem.bin into the extracted .tar folder aswell.
4) Plug Tab in to computer and do
Code:
adb reboot download
5) (Once in downlaod mode) run this function from the folder where the .tar file extracted
Code:
heimdall flash --repartition --primary-boot boot.bin --cache cache.rfs --dbdata dbdata.rfs --factoryfs factoryfs.rfs --pit gt-p1000_mr.pit --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage --verbose
6) basically the movinand.mst and hidden .rfs files are ignored?
Just want to be sure..
Hi.
I need to restore my Galaxy Tab P1010 with the old rom "FROYO.UEKC6 android 2.2.1 Kernel 2.6.32.9 [email protected]#1". I have all needed files except one : hidden.rfs
If someone has this ROM installed ("Settings->About..."), and it's rooted ( GingerBreak-v130 e.g. ), the follow sentente in the device (with "adb shell")
dd if=/dev/block/mmcblk0p3 of=/sdcard/hidden.rfs bs=4096
creates a file name hidden.rfs (about 300Mb; next steps: get into PC , compress it with winzip or 7z and shared it).
¿ Could anyone extract this file ?
Thank you.
iguana0335 said:
Hi.
I need to restore my Galaxy Tab P1010 with the old rom "FROYO.UEKC6 android 2.2.1 Kernel 2.6.32.9 [email protected]#1". I have all needed files except one : hidden.rfs
If someone has this ROM installed ("Settings->About..."), and it's rooted ( GingerBreak-v130 e.g. ), the follow sentente in the device (with "adb shell")
dd if=/dev/block/mmcblk0p3 of=/sdcard/hidden.rfs bs=4096
creates a file name hidden.rfs (about 300Mb; next steps: get into PC , compress it with winzip or 7z and shared it).
¿ Could anyone extract this file ?
Thank you.
Click to expand...
Click to collapse
I need it too. When I was uninstalling BusyBox, it made the Wifi non-functional. Even if I did a restart from Options > Privacy, I still can't get Wifi to work. Does anyone have the original rom for it?
Has anyone found the ROM for this one??? :crying:
Hi,
I'd like to know something when flashing modem whith Odin.
My GT-I9305 isn't Root so...
I get the <modem.bin> file exctract from my one package carrier's ROM (I9305XXALK5_I9305SFRALK2_I9305AEALK2_HOME.tar.md5)
with 7zip
Can I use this modem (from a 4.1.1 ROM) as if I'm in 4.1.2 (I9305XXBLL5_I9305DBTBLL4_I9305XXBLL5_HOME.tar.md5)
in Odin3 (v3.04), where should I put the <modem.bin> file? Phone,PDA?
The flash counter will be incremented?
What about the OTA or Kies update?
Thx..
Re: [Q]How to Flash <modem.bin> file with Odin?
You need to convert it from a bin file to a. tar file for Odin.
Sent from my GT-I9305 using xda app-developers app
Obagleyfreer said:
You need to convert it from a bin file to a. tar file for Odin.
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
I'd read on that post
[Q] How can i extract modem driver from official firmware
we can flash a .bin file with Odin..
...and flash via Odin using the "Phone" entry, not "PDA".
Click to expand...
Click to collapse
Warring of an other thread I'd read (but can't find again ) about Phone and PDA entry..
Hi all,
So any idea?
kanzi83 said:
Hi all,
So any idea?
Click to expand...
Click to collapse
Hello kanzi83, I'm new in the forums but I decided to register so I could help you.
I had the exact same problem and came with a solution, after reading yewsiong's instructions on his post:
http://forum.xda-developers.com/showthread.php?t=1658809
Modifying them so they match your situation, you have to do the following:
1. Install Cygwin and start the Cygwin terminal
2. Put the .tar.md5 firmware into C:\baseband
3. In Cygwin, type the following commands (pressing enter after each line):
Code:
cd /cygdrive/c/baseband
tar -xvf firmware_name.tar.md5 modem.bin
tar -H ustar -c modem.bin > baseband.tar
Example: If the firmware_name.tar.md5 is I8150DXLM3_I8150OLBLD1_I8150DXLM2_HOME.tar.md5
Then the code will be:
Code:
cd /cygdrive/c/baseband
tar -xvf I8150DXLM3_I8150OLBLD1_I8150DXLM2_HOME.tar.md5 modem.bin
tar -H ustar -c modem.bin > baseband.tar
After generating your .tar file, you can use Odin or Odin Mobile (I used Odio Mobile Pro and worked excellent) to flash the Modem.
There you go! Please let me know if you have any questions. Good luck.
kanzi83 said:
Hi all,
So any idea?
Click to expand...
Click to collapse
It's not that hard. Google is your friend.
Please read the following link.
http://forum.xda-developers.com/showthread.php?t=927568
You can just simplely flash modem.bin file via Odin.
Sent from my GT-I9305 using xda app-developers app
Thx for your answers. ..
I'd flash modem.bin file 2 month ago with odin v 3.04 in phone entry and works well
Envoyé depuis mon GT-I9305 avec Tapatalk
Procedure for changing the modem.bin
Hello all,
I am a newbie and want to know to how can I change the modem.bin file of my phone using ODIN...
Kindly help
Try reading this thread answer given in post 6 .
Aldo6 said:
Hello kanzi83, I'm new in the forums but I decided to register so I could help you.
I had the exact same problem and came with a solution, after reading yewsiong's instructions on his post:
http://forum.xda-developers.com/showthread.php?t=1658809
Modifying them so they match your situation, you have to do the following:
1. Install Cygwin and start the Cygwin terminal
2. Put the .tar.md5 firmware into C:\baseband
3. In Cygwin, type the following commands (pressing enter after each line):
Code:
cd /cygdrive/c/baseband
tar -xvf firmware_name.tar.md5 modem.bin
tar -H ustar -c modem.bin > baseband.tar
Example: If the firmware_name.tar.md5 is I8150DXLM3_I8150OLBLD1_I8150DXLM2_HOME.tar.md5
Then the code will be:
Code:
cd /cygdrive/c/baseband
tar -xvf I8150DXLM3_I8150OLBLD1_I8150DXLM2_HOME.tar.md5 modem.bin
tar -H ustar -c modem.bin > baseband.tar
After generating your .tar file, you can use Odin or Odin Mobile (I used Odio Mobile Pro and worked excellent) to flash the Modem.
There you go! Please let me know if you have any questions. Good luck.
Click to expand...
Click to collapse
Thank you!
Is this file checked against md5 when flashing with Odin? (Or when tar-ing?)
How to install modem.bin in my galaxy siii having android 4.3
[QUOTE=kanzi83;40365571Would you please let me know step by step guide to install my modem file (modem.bin) into my GT-I9300 using Odin. Your help in this regard will be highly appreciated.
I am very new to Android world. Need help
when I flash modem.bin via phone with odin 3.07
it fails
yasser86 said:
when I flash modem.bin via phone with odin 3.07
it fails
Click to expand...
Click to collapse
zip the file to .tar
Successful flash with Odin 3.10 & I9305
At first got errors when tried to flash modem.tar which I compressed with 7-zip from modem.bin
Odin just stopped at flashing modem.bin, so unplugged USB and cold restart (everything was still working fine with my phone, even the old modem)
Then successfully flashed modem.BIN via ticking it to CP (Phone?)
So... Somehow Odin couldn't flash my compressed .tar file of the modem..
Maybe I did something wrong with the compression
But now I have a working modem from the latest samsung firmware for my country and signal feels much more reliable now and even got a little bit better speedtest results too
How to flash Modem.bin file with Odin
hi,i had read all posts but i did not get any satisfying result,.....the Solution is
you have to select Odin V3.9 .in 3.9 in CP you can flash modem.bin
Regards
[email protected] said:
hi,i had read all posts but i did not get any satisfying result,.....the Solution is
you have to select Odin V3.9 .in 3.9 in CP you can flash modem.bin
Regards
Click to expand...
Click to collapse
Confirmed with Odin3.10. Don't make it too complicated, folks!
mightysween said:
Confirmed with Odin3.10. Don't make it too complicated, folks!
Click to expand...
Click to collapse
Worked for me also. Thanks OP
hello
raonizal said:
zip the file to .tar
Click to expand...
Click to collapse
This works with newer versions of ODIN.
hi,
i own a galaxy s3 mini i8190 i was trying to flash reovery with heimdall and i used pit to get partition layout i flashed recovery.img on MBR,GPT partition and my phone got hardbricked
because recovery.img in s3 mini should be flashed on kernel2 partition and i flashed it on totally wrong partition after i used jtag to flash it and i unbricked it successfully my phone turned on but my internal memory is corrupted it is showing 0.00b and my phone's efs is also corrupted my s3 mini is in factory mode network is not working i am unable to install any app either from playstore or directly apk because my internal memory is messed up
i think i need to flash GPT.img to repair internal memory layout because it contains layout which is corrupted on my phone then i need efs backup in .img format to exit factory mode and run 3g network please please someone help me
upload GPT.img and EFS.img or if you think this solution is incorrect help me
plz plz plz someone help me i am in a big problem and also my warranty is over plz plz help
give me GPT and efs so i can flash it through heimdall
:crying::crying::crying::crying::crying:
Yor text is to big to read, so I give up of reading it. Anyway take a look here or search on XDA. Good luck with that
P.S: & next time post your questions on Q&A section, thanks.
In efs there's imei. If you don't have a backup i'm afraid it's just gone. You can't use mine
---------- Post added at 06:22 PM ---------- Previous post was at 06:07 PM ----------
AFAIK gpt is read only for s3 mini so i dont think you can flash it. You may just need to repartition with a pit file. This will not solve all of yours problems if efs is corrupted, in that case you have to bring the phone to samsung service to restore your Imei.
as i flashed the MBR,GPT partition in heimdall screen shot
by using jtag only MBR master boot record is repaired which unbricked my phone now GPT which was also corrupted along MBR need to be flashed so my partition layout will be corrected and internal sd will work
i also tried pit to flash firmware 4.1.2 with odin but no any change
it is an option in heimdall and i think it can be flashed partition id is 1 so for now i left efs to solve it i am trying to solve internal memory first
i ended up google but found no solution
If you flashed recovery on first partition i think your /efs is ok, because its first sector starts at 10MB from beginning of /dev/block/mmcblk0
recovery images are smaller
You need following images:
Code:
PIT Entry Name filename
00 MBR,GPT
01 MasterTOC
02 PIT goldenxx.pit
03 MD5HDR md5.img
04 STEboot1 STE_boot1.img
05 STEboot2 STE_boot2.img
06 Dnt dnt.ssw
07 reserved
08 CSPSAFS cspsa.img
09 CSPSAFS2 cspsa2.img
I have i8190N so my images can't help you
you have i8190n and its partitiion layout is different for i8190 so these images are so called GB images
also i think if GPT will be corrected the efs will also be fine
does anyone have same model which i have?
plz help me
also when i try to format it in recovery it says
invalid argument failed to mount /data and /efs
and efs and data is not corrupted in mine case my partition layout is corrupted
qasim799 said:
you have i8190n and its partitiion layout is different for i8190 so these images are so called GB images
...
Click to expand...
Click to collapse
I dont think so. PIT files for both versions are identical, so partition layout is the same on both phones
If you want you can try to use my images of first three partitions, MBR,GPT, MasterTOC and PIT
Images were created with dd command from adb
STEboot1and STEboot2 images are available in stock ROMs
piskor said:
I dont think so. PIT files for both versions are identical, so partition layout is the same on both phones
If you want you can try to use my images of first three partitions, MBR,GPT, MasterTOC and PIT
Images were created with dd command from adb
STEboot1and STEboot2 images are available in stock ROMs
Click to expand...
Click to collapse
thank you so much you helped me
you are a good guy:good:
piskor said:
I dont think so. PIT files for both versions are identical, so partition layout is the same on both phones
If you want you can try to use my images of first three partitions, MBR,GPT, MasterTOC and PIT
Images were created with dd command from adb
STEboot1and STEboot2 images are available in stock ROMs
Click to expand...
Click to collapse
any guarantee about theses images I'm afraid to flash them because they are of different model
they will not brick my device?
sure me so i will flash them
qasim799 said:
any guarantee about theses images I'm afraid to flash them because they are of different model
they will not brick my device?
sure me so i will flash them
Click to expand...
Click to collapse
No guarantee, but you can try.
Your phone, as you said is hardbricked, and if you flashed recovery img on first partition, few of them are also overwritten.
You can wait of course for i8190 dump, what i recommend
Any one plz help me
i want images of i8190 only
take a backup of your GPT,MBR.img
still no help i heard about XDA that they help very fastly nut no one is helping me
plz for GOD SAKE help me i am in a big and weird kind of problem
qasim799 said:
still no help i heard about XDA that they help very fastly nut no one is helping me
plz for GOD SAKE help me i am in a big and weird kind of problem
Click to expand...
Click to collapse
But remember, that no one is obligated to help you on XDA I see that many people tried to help you (including me), so if we can't help, what you want more!? Anyway, really hope that someone pops up with a solution for you Have a nice day
I would if I could, but I have a 8910N....
that is what i am saying who trys to help me have different model from me.
i am requesting to those who have gt-i8190
after all it is s3 mini forum
nobody have this phone who has plz help me just take a backup of MBR,GPT.img partition id is 1
it is just a less then 1 MB file which i need to my whole phone
Clostry said:
I would if I could, but I have a 8910N....
Click to expand...
Click to collapse
piskor gave me backup of n model but i am afraid to flash it as it is from a different phone it will hard brick it again .you can see their layout then sure me i can flash them or not and remember the MBR also it matches
no help yet !
To all I8190 users
If somebody want to help to qasim799 please execute this commands from adb or terminal emulatror app on your phone and attach to the post resulting images:
Code:
su
dd if=/dev/block/mmcblk0p1 of=/storage/sdcard1/mmcblk0p1.img
dd if=/dev/block/mmcblk0p2 of=/storage/sdcard1/mmcblk0p2.img
dd if=/dev/block/mmcblk0p3 of=/storage/sdcard1/mmcblk0p3.img
Resulting image files will be available in root of external storage card
mmcblk0p1.img - image MBR,GPT partition
mmcblk0p2.img - MasterTOC partition
mmcblk0p3.img - PIT partition
Here you go @qasim799, hope that works. Thanks piskor, for the noobish "how to":laugh:
UPDATE 09/20/2016 - Root is now available for the SM-T285 (custom ROM and SM-T280 to follow) see post for details (http://forum.xda-developers.com/showpost.php?p=68777842&postcount=27)
After some work I've managed to debloat my Galaxy Tab A(6) 7.0 LTE (SM-T285/T280). We all know that with a locked bootloader we
can at least do customizations with the system partition:
Here is a simple guide with hopes that more people with the device can continue to allow for more ROM customizations:
Tools/Requirements:
================
- Ubuntu as my OS
- make sure you have adb installed and running (See the android developers guide on how to do this)
- Heimdall 1.4.1
- A copy of the stock firmware zip from samsung for your device
- 7zip to be able to unzip the firmware from above
- Android AOSP fsutils simg2img and make_ext4fs (Attached) (note that your make_ext4fs needs to be patched to be able to generate samsung patches easily see gist) for some reason samsung chose to use a slightly different sparse file layout for this device. Using the stock make_ext4fs to generate an image will cause heimdall ( ad Odin) to stop data uploads after the first packet stream.
Or if you still want to use stock make_ext4fs you can try using Chainfire's sgs4ext4fs and run this after you generate your system.img, I haven't tried this route personally myself.
Step By Step (Part 1 - Mount stock system.img for modification)
==========
1. Create a folder to do your work like samsing_kitchen for example. Place your
stock firmware package there
Code:
mkdir samsung_kitchen
cd samsung_kitchen
2. Extract your stock firmware's system.img using 7zip
Code:
7z x XTC-T285XXU0APCN-20160421170750.zip
7z x T285XXU0APCN_T285OLB0APC6_T285XXU0APCN_HOME.tar.md5
Should see a couple of image files, one of them is system.img.
3. Create mount point and convert from sparse image to mountable image and then mount it
Code:
mkdir system
simg2img system.img system.img.raw
sudo mount -t ext4 -o loop system.img.raw ./system
The contents of the system image should now be visible inside the system folder you
just created. You can now proceed to modifiying it (e.g. remove apps)
(Part 2 - Repackage image for flashing to device)
=================================================
DISCLAIMER: As always make sure you backup your important files in case
something goes wrong! I will not be responsible for any losses resulting from this
activity. Also this activity may void your warranty.
Prequisites:
- Make sure you have heimdall properly working.
- Make sure you have oem unlock. This should be visible in developer settings
To know if it is enabled/disable FRP protection should be disabled when you go
in Odin mode.
1. pull the file_contexts file from .your device ( or download the attached in this post).
Code:
adb pull file_contexts
on a connected device in developer mode. You will need this file so that the permissions are properly set when building the image
2. Exit from system back to your working folder (e.g. samsing_kitchen ) and run
the following:
Code:
sudo make_ext4fs -s -l 2147483648 -S file_contexts -a system new_system.img ./system
This should create a flashable image called new_system.img
3. Restart your SM-T285 into Odin Mode (Power-off, then hold home vol-down + power until Odin Mode shows up)
4. Flash using Heimdall
Code:
heimdall flash --SYSTEM new_system.img
Your device should automatically restart after this. If something goes wrong you can always flash the original system image back.
Making an ODIN flashable image
----------------------------------------
To create an image compatible with ODIN (tar.md5) make sure you have a copy of the stock image zip from samsung and extract (using 7zip) its contents to a folder:
An extracted file should look like this:
Code:
boot.img
cache.img
hidden.img
nvitem.bin
recovery.img
SPRDCP.img
SPRDGDSP.img
SPRDLTEDSP.img
SPRDWDSP.img
system.img
replace the stock system.img with the one you created from above:
Code:
cp ../new_system.img system.img
tar and md5 it:
Code:
tar -H ustar -c boot.img cache.img hidden.img recovery.img SPRDCP.img SPRDGDSP.img SPRDLTEDSP.img SPRDWDSP.img system.img >T285_CUSTOM.tar
md5sum -t T285_CUSTOM.tar > T285_CUSTOM.tar
mv T285_CUSTOM.tar T285_CUSTOM.tar.md5
as per ashyx this should also work as well:
Code:
tar -H ustar -c system.img > system.tar
md5sum -t system.tar > sytem.tar
mv system.tar system.tar.md5
Optionally Zip it if you want:
Code:
7z a T285_CUSTOM.zip T285_CUSTOM.tar.md5
This guide should work for the T280 as well, though I can't confirm it since I don't have access to that model.
Petition for samsung to unlock the device:
https://www.change.org/p/samsung-unlock-the-bootloader-for-the-samsung-galaxy-tab-a-7-0-2016?recruiter=286570213&utm_source=petitions_share&utm_medium=copylink
Custom ROM to enable move apps to sd (apps2sd like support):
http://forum.xda-developers.com/android/development/rom-samsung-galaxy-tab-7-0-lte-2016-sm-t3455788
@jedld
Nice guide, just a few things though.
I don't think it's really necessary to use the file contexts as we're building a system image and all permissions should remain intact.
Regarding the chunk size, Chainfire created sgs4ext4fs to deal with this, it just needs to be run afterwards on the sparse image to patch the headers.
What is the source for the make_ext4fs patch or did you create this patch?
Lastly some people may prefer to use ODIN to flash.
So maybe you could add to the guide that the image can be repacked into a ODIN flashable tar using 7-zip.
By the way the guide will work for the T280 too, so you may want to add that.
Thanks.
ashyx said:
@jedld
Nice guide, just a few things though.
I don't think it's really necessary to use the file contexts as we're building a system image and all permissions should remain intact.
Regarding the chunk size, Chainfire created sgs4ext4fs to deal with this, it just needs to be run afterwards on the sparse image to patch the headers.
What is the source for the make_ext4fs patch or did you create this patch?
Lastly some people may prefer to use ODIN to flash.
So maybe you could add to the guide that the image can be repacked into a ODIN flashable tar using 7-zip.
By the way the guide will work for the T280 too, so you may want to add that.
Thanks.
Click to expand...
Click to collapse
I don't think it's really necessary to use the file contexts as we're building a system image and all permissions should remain intact.
Click to expand...
Click to collapse
I remember encountering a boot loop without that, let me check again and I'll update the guide.
What is the source for the make_ext4fs patch or did you create this patch?
Click to expand...
Click to collapse
Just applied the following patch on latest aosp sources:
https://gist.github.com/jedld/4f388496bda03b349f5744f367749a67
There is a magic number used which I can't figure out, the value is different between SM-T285 ROMS coming from different regions.
Nice to hear about sgs4ext4fs though, probably wouldn't be able to know based on the problem I encountered that the tool also applies unless someone pointed it out.
https://www.change.org/p/samsung-unl...edium=copyLink
Petition for unlocked bootloader for samsung, please sign
http://samsung4android.ru/?ipub=422
any thoguth on this?
klemen241 said:
http://samsung4android.ru/?ipub=422
any thoguth on this?
Click to expand...
Click to collapse
ashyx already tried everything. CF-auto root requires an unlocked recovery, the tablet won't even accept a repacked recovery image. Besides the guy in the video wasn't even using a SM-T285, if you look closely the files he used were for the SM-T550.
klemen241 said:
https://www.change.org/p/samsung-unl...edium=copyLink
Petition for unlocked bootloader for samsung, please sign
Click to expand...
Click to collapse
link is broken though, you must have used the auto truncated link, use this instead:
https://www.change.org/p/samsung-un...edium=copylink&recuruit_context=copylink_long
What about those custom roms? As far as i can see we can use modified stock rom. Can we go anywhere with that? And can someone explain how to make external storage bigger with SD?
SM-T285M with locked bootloader - research ...
First, I have a SM-T285M which is a Galaxy Tab A6 7.0 LTE with a COO CSC. and is factory unlocked (UB as Samsung notates it these days. It's got North and South America LTE bands, and unfortunately it also has a locked bootloader just like the T285 and the T280.
Hear me out on this theory I have come up with ....
I recently stumbled across mention of Samsung pushing out an OTA at some point that broke root at the kernel level forever. I read Chainfire has created a patch that fixes this on some models. Unfortunately not the T28x's due to the locked BL.
While looking for stock ROMS, I discovered differences in the pit files and the size of hidden.img that occurred between 3/2016 and 4/2016 releases leading me to believe that's when they locked the bootloader and pushed the root killing kernel ota to the T285M. The hidden.img was shrunk to a little more than the boot.img and the PIT was modified beginning with the 4/26 release
My T285M was built on 4/7/2016 and now having the new pit and hidden.img, any attempts at ODIN flashing of the 3/23 factory rom (3/10 build) crashes out at hidden.img. I figure I will be unable to go back to the 3/10 build unless I use the pit for that 3/10 build - I'm not ready to play that deep on this .... yet, I don't even know if I am on to anything at this point. but maybe someone else wants to ....
Take a peek at the contents of the three released roms for the T285M in the capture below and if anyone thinks theres hope in getting to root by going back to 3/10 build and PIT I can point you to the three files for experimentation, or even better to get to chainfire if this is doable.
BTW jedid GREAT debloat for the T285. I'm using the system.img on my T285M , I hated Touchwiz so much, now all we need is root. see if these tell you anything.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
klemen241 said:
What about those custom roms? As far as i can see we can use modified stock rom. Can we go anywhere with that? And can someone explain how to make external storage bigger with SD?
Click to expand...
Click to collapse
There are a number of things we can already do with a custom system.img like debloat, enable universal sd r/w, customizing apps, probably theming and fonts are also possible. Hopefully more people can come up with mods.
Unfortunately we need root/unlocked boot.img to do important things to fix the weakness of this device like changing partition sizes, enable apps2sd support, xposed framework, having customizable cpu performance governors/overclocking etc.
TopTongueBarry said:
First, I have a SM-T285M which is a Galaxy Tab A6 7.0 LTE with a COO CSC. and is factory unlocked (UB as Samsung notates it these days. It's got North and South America LTE bands, and unfortunately it also has a locked bootloader just like the T285 and the T280.
Hear me out on this theory I have come up with ....
I recently stumbled across mention of Samsung pushing out an OTA at some point that broke root at the kernel level forever. I read Chainfire has created a patch that fixes this on some models. Unfortunately not the T28x's due to the locked BL.
While looking for stock ROMS, I discovered differences in the pit files and the size of hidden.img that occurred between 3/2016 and 4/2016 releases leading me to believe that's when they locked the bootloader and pushed the root killing kernel ota to the T285M. The hidden.img was shrunk to a little more than the boot.img and the PIT was modified beginning with the 4/26 release
My T285M was built on 4/7/2016 and now having the new pit and hidden.img, any attempts at ODIN flashing of the 3/23 factory rom (3/10 build) crashes out at hidden.img. I figure I will be unable to go back to the 3/10 build unless I use the pit for that 3/10 build - I'm not ready to play that deep on this .... yet, I don't even know if I am on to anything at this point. but maybe someone else wants to ....
Take a peek at the contents of the three released roms for the T285M in the capture below and if anyone thinks theres hope in getting to root by going back to 3/10 build and PIT I can point you to the three files for experimentation, or even better to get to chainfire if this is doable.
BTW jedid GREAT debloat for the T285. I'm using the system.img on my T285M , I hated Touchwiz so much, now all we need is root. see if these tell you anything.
Click to expand...
Click to collapse
i was wondering the same thing, if ther is any chance of unlocking it on earlier versions.
Also i sent email to samsung support again, maybe they will be sick of us begging and release the lock
klemen241 said:
i was wondering the same thing, if ther is any chance of unlocking it on earlier versions.
Also i sent email to samsung support again, maybe they will be sick of us begging and release the lock
Click to expand...
Click to collapse
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=t285m
---------- Post added at 02:46 AM ---------- Previous post was at 02:36 AM ----------
TopTongueBarry said:
First, I have a SM-T285M which is a Galaxy Tab A6 7.0 LTE with a COO CSC. and is factory unlocked (UB as Samsung notates it these days. It's got North and South America LTE bands, and unfortunately it also has a locked bootloader just like the T285 and the T280.
Hear me out on this theory I have come up with ....
I recently stumbled across mention of Samsung pushing out an OTA at some point that broke root at the kernel level forever. I read Chainfire has created a patch that fixes this on some models. Unfortunately not the T28x's due to the locked BL.
While looking for stock ROMS, I discovered differences in the pit files and the size of hidden.img that occurred between 3/2016 and 4/2016 releases leading me to believe that's when they locked the bootloader and pushed the root killing kernel ota to the T285M. The hidden.img was shrunk to a little more than the boot.img and the PIT was modified beginning with the 4/26 release
My T285M was built on 4/7/2016 and now having the new pit and hidden.img, any attempts at ODIN flashing of the 3/23 factory rom (3/10 build) crashes out at hidden.img. I figure I will be unable to go back to the 3/10 build unless I use the pit for that 3/10 build - I'm not ready to play that deep on this .... yet, I don't even know if I am on to anything at this point. but maybe someone else wants to ....
Take a peek at the contents of the three released roms for the T285M in the capture below and if anyone thinks theres hope in getting to root by going back to 3/10 build and PIT I can point you to the three files for experimentation, or even better to get to chainfire if this is doable.
BTW jedid GREAT debloat for the T285. I'm using the system.img on my T285M , I hated Touchwiz so much, now all we need is root. see if these tell you anything.
Click to expand...
Click to collapse
UPDATE: I was able to get the 3/10 stock factory rom flashed without changing the pit. Replaced the hidden.img file in this rom with a renamed copy of the boot.img from the same rom. Flashing does fail in the very end, but it completes before failing so I simply rebooted immediately into Odin mode again to flash jedid's debloated system.img for the T285. Done this a couple times now and the device comes up just fine. About device and Phone Info Samsung confirm it is running the 3/10 build.
Bad news is the bootloader is locked in this build too. No hope unless someone can do something with the source. See prior post.
is open source same for t280? i have 280 not 285
klemen241 said:
is open source same for t280? i have 280 not 285
Click to expand...
Click to collapse
not sure how having the kernel source would help since we can't even change the kernel on the device which is kinda awkward for samsung. Besides I remember ashyx having compilation issues with spreadtrum kernel sources by samsung and not just for this device.
TopTongueBarry said:
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=t285m
---------- Post added at 02:46 AM ---------- Previous post was at 02:36 AM ----------
UPDATE: I was able to get the 3/10 stock factory rom flashed without changing the pit. Replaced the hidden.img file in this rom with a renamed copy of the boot.img from the same rom. Flashing does fail in the very end, but it completes before failing so I simply rebooted immediately into Odin mode again to flash jedid's debloated system.img for the T285. Done this a couple times now and the device comes up just fine. About device and Phone Info Samsung confirm it is running the 3/10 build.
Bad news is the bootloader is locked in this build too. No hope unless someone can do something with the source. See prior post.
Click to expand...
Click to collapse
I remember flashing an earlier build thinking the same thing and yep the bootloader is still locked. Aside from that I ran kingroot to see if there was anything exploitable... did'nt work. What I haven't tried is to see if superuser is disabled in this kernel though.
jedld said:
After some work I've managed to debloat my Galaxy Tab A(6) 7.0 LTE (SM-T285/T280). We all know that with a locked bootloader we
can at least do customizations with the system partition:
Here is a simple guide with hopes that more people with the device can continue to allow for more ROM customizations:
Tools/Requirements:
================
- Ubuntu as my OS
- make sure you have adb installed and running (See the android developers guide on how to do this)
- Heimdall 1.4.1
- A copy of the stock firmware zip from samsung for your device
- 7zip to be able to unzip the firmware from above
- Android AOSP fsutils simg2img and make_ext4fs (Attached) (note that your make_ext4fs needs to be patched to be able to generate samsung patches easily see gist) for some reason samsung chose to use a slightly different sparse file layout for this device. Using the stock make_ext4fs to generate an image will cause heimdall ( ad Odin) to stop data uploads after the first packet stream.
Or if you still want to use stock make_ext4fs you can try using Chainfire's sgs4ext4fs and run this after you generate your system.img, I haven't tried this route personally myself.
Step By Step (Part 1 - Mount stock system.img for modification)
==========
1. Create a folder to do your work like samsing_kitchen for example. Place your
stock firmware package there
Code:
mkdir samsung_kitchen
cd samsung_kitchen
2. Extract your stock firmware's system.img using 7zip
Code:
7z x XTC-T285XXU0APCN-20160421170750.zip
7z x T285XXU0APCN_T285OLB0APC6_T285XXU0APCN_HOME.tar.md5
Should see a couple of image files, one of them is system.img.
3. Create mount point and convert from sparse image to mountable image and then mount it
Code:
mkdir system
simg2img system.img system.img.raw
sudo mount -t ext4 -o loop system.img.raw ./system
The contents of the system image should now be visible inside the system folder you
just created. You can now proceed to modifiying it (e.g. remove apps)
(Part 2 - Repackage image for flashing to device)
=================================================
DISCLAIMER: As always make sure you backup your important files in case
something goes wrong! I will not be responsible for any losses resulting from this
activity. Also this activity may void your warranty.
Prequisites:
- Make sure you have heimdall properly working.
- Make sure you have oem unlock. This should be visible in developer settings
To know if it is enabled/disable FRP protection should be disabled when you go
in Odin mode.
1. pull the file_contexts file from .your device.
Code:
adb pull file_contexts
on a connected device in developer mode. You will need this file so that the permissions are properly set when building the image
2. Exit from system back to your working folder (e.g. samsing_kitchen ) and run
the following:
Code:
sudo make_ext4fs -s -l 2147483648 -S file_contexts -a system new_system.img ./system
This should create a flashable image called new_system.img
3. Restart your SM-T285 into Odin Mode (Power-off, then hold home vol-down + power until Odin Mode shows up)
4. Flash using Heimdall
Code:
heimdall flash --SYSTEM new_system.img
Your device should automatically restart after this. If something goes wrong you can always flash the original system image back.
Making an ODIN flashable image
----------------------------------------
To create an image compatible with ODIN (tar.md5) make sure you have a copy of the stock image zip from samsung and extract (using 7zip) its contents to a folder:
An extracted file should look like this:
Code:
boot.img
cache.img
hidden.img
nvitem.bin
recovery.img
SPRDCP.img
SPRDGDSP.img
SPRDLTEDSP.img
SPRDWDSP.img
system.img
replace the stock system.img with the one you created from above:
Code:
cp ../new_system.img system.img
tar and md5 it:
Code:
tar -H ustar -c boot.img cache.img hidden.img recovery.img SPRDCP.img SPRDGDSP.img SPRDLTEDSP.img SPRDWDSP.img system.img >T285_CUSTOM.tar
md5sum -t T285_CUSTOM.tar > T285_CUSTOM.tar
mv T285_CUSTOM.tar T285_CUSTOM.tar.md5
Optionally Zip it if you want:
Code:
7z a T285_CUSTOM.zip T285_CUSTOM.tar.md5
This guide should work for the T280 as well, though I can't confirm it since I don't have access to that model.
Click to expand...
Click to collapse
Anyway to do this on a windows machine?????
lohtse said:
Anyway to do this on a windows machine?????
Click to expand...
Click to collapse
Not sure though since you need to be able to mount an ext4 image, make modifications to it and then write it back. Plus the tools required to write the image back properly are only available in linux so I doubt there will be one for windows unless someone puts in effort to make something for it. The best I can do is to make a docker image where you can run it under windows with those tools if anyone is interested.
Just a note regarding the guide, it's not really necessary to add all the other partition images when creating the ODIN flashable tar.
All that is required is:
tar cvf system.tar system.img
jedld said:
Not sure though since you need to be able to mount an ext4 image, make modifications to it and then write it back. Plus the tools required to write the image back properly are only available in linux so I doubt there will be one for windows unless someone puts in effort to make something for it. The best I can do is to make a docker image where you can run it under windows with those tools if anyone is interested.
Click to expand...
Click to collapse
is there no way to create a set of files(zip etc) we windows users could flash using odin? would be a huge help if that could be done! also anyone have a link to a stock rom??
and finally I noticed that the US samsung site has a pdf manual for this tablet that refers to marshmallow!!!!!
http://www.samsung.com/us/business/support/owners/product/SM-T280NZWAXAR
lohtse said:
is there no way to create a set of files(zip etc) we windows users could flash using odin? would be a huge help if that could be done! also anyone have a link to a stock rom??
and finally I noticed that the US samsung site has a pdf manual for this tablet that refers to marshmallow!!!!!
http://www.samsung.com/us/business/support/owners/product/SM-T280NZWAXAR
Click to expand...
Click to collapse
I highly doubt this thing will get mm. [emoji52]