as the title states please someone i perfer a smart dev here on xda to compile or get the lollipop offical update to work on the TAB4 10.1 SM-T530NU JUST A REQUEST NOT A DEMAND.
LGMONO said:
as the title states please someone i perfer a smart dev here on xda to compile or get the lollipop offical update to work on the TAB4 10.1 SM-T530NU JUST A REQUEST NOT A DEMAND.
Click to expand...
Click to collapse
There are three different cyanogenmod 12 (lollipop) ROMs listed in the development section compatible with the t530nu which are all better than stock anyway. I have the exact same model as you and have been on lollipop for months now and loving it
i understand that, i love and encourage CM and AOSP roms i have used them quite offen however i prefer stock because stock roms utilize the devices features and because there are so many devices the devs dont have time to port stock based apps in there modifications so there for i use stock roms for a daily driver. but i would always support custom roms to anyone as did you. thanks for the reply, would really like to get a stock based lp on the device.
Thanks
LGMONO said:
i understand that, i love and encourage CM and AOSP roms i have used them quite offen however i prefer stock because stock roms utilize the devices features and because there are so many devices the devs dont have time to port stock based apps in there modifications so there for i use stock roms for a daily driver. but i would always support custom roms to anyone as did you. thanks for the reply, would really like to get a stock based lp on the device.
Thanks
Click to expand...
Click to collapse
^^what he said.
I've been checking the forums throughout the day since the LP update came out hoping that someone ported it to the T530NU. Who knows when the official one will come out since the LP update for the T530 has only been released in Spain so far. I doubt it will be released for the T530NU until the update for the T530 is released in more regions.
Dudash said:
^^what he said.
I've been checking the forums throughout the day since the LP update came out hoping that someone ported it to the T530NU. Who knows when the official one will come out since the LP update for the T530 has only been released in Spain so far. I doubt it will be released for the T530NU until the update for the T530 is released in more regions.
Click to expand...
Click to collapse
and @LGMONO
I imagine it's possible to port the official update, here are my thoughts. Take the LP Odin file (the tar file) and open the tar.md5 file in winrar or 7zip. Extract all the files inside (system.img, boot.img, the modem.bin and everything) and make it into an update zip, (with updater-script and everything) but tailor it to be flashable with FlashFire. No idea if it'll work but that's what I'd try if I preferred touchwiz over cyanogenmod.
Edit: On the files you want to pull, I don't think you want to use cache.img or hidden.img, but yeah everything else.
thisisapoorusernamechoice said:
and @LGMONO
I imagine it's possible to port the official update, here are my thoughts. Take the LP Odin file (the tar file) and open the tar.md5 file in winrar or 7zip. Extract all the files inside (system.img, boot.img, the modem.bin and everything) and make it into an update zip, (with updater-script and everything) but tailor it to be flashable with FlashFire. No idea if it'll work but that's what I'd try if I preferred touchwiz over cyanogenmod.
Edit: On the files you want to pull, I don't think you want to use cache.img or hidden.img, but yeah everything else.
Click to expand...
Click to collapse
T, hey hey, you only want the system.img and the boot.img, the issue though is the kernel, my attempts at getting the firmware running "as-is"
fail, [kernel] while i can access through adb i couldn't get a read on logcat even when invoking with full/absolute path
/system/bin/logcat
the sepolicy is covering adb and as i'm learning , sometimes permission denied actually means no such file or directory
and/or the opposite :silly: gotta love android.
m
moonbutt74 said:
T, hey hey, you only want the system.img and the boot.img, the issue though is the kernel, my attempts at getting the firmware running "as-is"
fail, [kernel] while i can access through adb i couldn't get a read on logcat even when invoking with full/absolute path
/system/bin/logcat
the sepolicy is covering adb and as i'm learning , sometimes permission denied actually means no such file or directory
and/or the opposite :silly: gotta love android.
m
Click to expand...
Click to collapse
I know they got a custom kit Kat kernel going for cm11 NU, did anything come of getting that working for cm12 and would that be of use in this instance? (Yeah I haven't checked the thread in a little while because I'm lazy and inattentive)
thisisapoorusernamechoice said:
I know they got a custom kit Kat kernel going for cm11 NU, did anything come of getting that working for cm12 and would that be of use in this instance? (Yeah I haven't checked the thread in a little while because I'm lazy and inattentive)
Click to expand...
Click to collapse
T
hey, you forgot irrepressibly polysyllabic ! xD
okay seriously though, i'm momentarily stumped as to what's going on with my t330nu but later later tonight i'll run a kernel compile and try the t530 rom again.
m
thisisapoorusernamechoice said:
and @LGMONO
I imagine it's possible to port the official update, here are my thoughts. Take the LP Odin file (the tar file) and open the tar.md5 file in winrar or 7zip. Extract all the files inside (system.img, boot.img, the modem.bin and everything) and make it into an update zip, (with updater-script and everything) but tailor it to be flashable with FlashFire. No idea if it'll work but that's what I'd try if I preferred touchwiz over cyanogenmod.
Edit: On the files you want to pull, I don't think you want to use cache.img or hidden.img, but yeah everything else.
Click to expand...
Click to collapse
i tried that lol it didnt work im a .net dev not an android dev i assure you the android devs are much smarter however i did try that method already i purchased ODIN mobile and the device is not supported, when i did try with odin pc version the erro is the aboot and fails im very sure the system will work on t530nu
LGMONO said:
i tried that lol it didnt work im a .net dev not an android dev i assure you the android devs are much smarter however i did try that method already i purchased ODIN mobile and the device is not supported, when i did try with odin pc version the erro is the aboot and fails im very sure the system will work on t530nu
Click to expand...
Click to collapse
Nah you don't want to try this with Odin it verifies what device you have. I say try flashfire instead (chainfire even said FF is intended to replace mobile Odin as well as safestrap) but we have to figure something out for the kernel (boot.img).
@moonbutt74 I was able to flash t530/1 ROMs before anyone started developing NU specific custom kernels, is it not working here because it's an official build or something? Sorry for my frustratingly persistent dearth of knowledge.
moonbutt74 said:
T
hey, you forgot irrepressibly polysyllabic ! xD
okay seriously though, i'm momentarily stumped as to what's going on with my t330nu but later later tonight i'll run a kernel compile and try the t530 rom again.
m
Click to expand...
Click to collapse
Finally another individual understands my irresistible urge to layer on excess syllables with each successive increment of agitation I am provoked to. Also my father is a lawyer (lmao). I'll try some things for this tonight, I don't really expect success (or really anything other than a soft brick) but my curiosity is officially piqued, I'll make this my project for tonight
LGMONO said:
i tried that lol it didnt work im a .net dev not an android dev i assure you the android devs are much smarter however i did try that method already i purchased ODIN mobile and the device is not supported, when i did try with odin pc version the erro is the aboot and fails im very sure the system will work on t530nu
Click to expand...
Click to collapse
L,
hi, this step carries risk, make a backup !!
what you need, from the full firmware img extract system.img and boot.img
pack system.img for odin flash, this is the tricky part, it's one of the following
A- rename system.img.ext4 to system.img
--- then in linux/cygwin cd to the directory where system.img is located
--- run tar as follows
--- tar -H ustar -c system.img > system.img.tar
--- md5sum -t system.img.tar >> system.img.tar
--- mv system.img.tar system.img.tar.md5
or
B- don't rename system.img.ext4 and run again in linux/cygwin
--- tar -H ustar -c system.img.ext4 > system.img.ext4.tar
--- md5sum -t system.img.ext4.tar >> system.img.ext4.tar
--- mv system.img.ext4.tar system.img.ext4.tar.md5
then attempt attempt odin flash, NOT MOBILE ODIN
do the same for boot.img
m
thisisapoorusernamechoice said:
Nah you don't want to try this with Odin it verifies what device you have. I say try flashfire instead (chainfire even said FF is intended to replace mobile Odin as well as safestrap) but we have to figure something out for the kernel (boot.img).
@moonbutt74 I was able to flash t530/1 ROMs before anyone started developing NU specific custom kernels, is it not working here because it's an official build or something? Sorry for my frustratingly persistent dearth of knowledge.
Finally another individual understands my irresistible urge to layer on excess syllables with each successive increment of agitation I am provoked to. Also my father is a lawyer (lmao). I'll try some things for this tonight, I don't really expect success (or really anything other than a soft brick) but my curiosity is officially piqued, I'll make this my project for tonight
Click to expand...
Click to collapse
can you give me a download link to flashfire please i tried searching for this i cant find it ? please thanks
moonbutt74 said:
L,
hi, this step carries risk, make a backup !!
what you need, from the full firmware img extract system.img and boot.img
pack system.img for odin flash, this is the tricky part, it's one of the following
A- rename system.img.ext4 to system.img
--- then in linux/cygwin cd to the directory where system.img is located
--- run tar as follows
--- tar -H ustar -c system.img > system.img.tar
--- md5sum -t system.img.tar >> system.img.tar
--- mv system.img.tar system.img.tar.md5
or
B- don't rename system.img.ext4 and run again in linux/cygwin
--- tar -H ustar -c system.img.ext4 > system.img.ext4.tar
--- md5sum -t system.img.ext4.tar >> system.img.ext4.tar
--- mv system.img.ext4.tar system.img.ext4.tar.md5
then attempt attempt odin flash, NOT MOBILE ODIN
do the same for boot.img
m
Click to expand...
Click to collapse
Thank you i will try this and thanks to all that is participating in this thread.. i have a lg g3 i just updated to lollipop and i like it, but remember for you guys out there newbees so to say at least try and give support for AOSP and Cyan roms i am a huge fan. Give them devs the credit they work hard for
LGMONO said:
can you give me a download link to flashfire please i tried searching for this i cant find it ? please thanks
Click to expand...
Click to collapse
Chainfire said:
- Join the G+ community using the same Google account as you're using for Play on your phone/tablet here: https://plus.google.com/communities/116661625291346007584
- Sign up to receive the BETA versions from Play here: https://play.google.com/apps/testing/eu.chainfire.flash
- Use the link provided after sign-up to download the app. Note that it may take minutes to even hours before the provided link actually works.
Click to expand...
Click to collapse
Link to Chainfire's FlashFire thread: http://forum.xda-developers.com/showpost.php?p=59959596&postcount=1
LGMONO said:
can you give me a download link to flashfire please i tried searching for this i cant find it ? please thanks
Click to expand...
Click to collapse
Here
But try what moonbutt74 is saying first, he's smarter than I. I'm just thinking aloud about all the (probably almost certainly stupid) stuff I'm going to try to get this working
T,
i have a though about incorrect firmware linking in boot.img and /system/etc scripts in the release
to mount and explore the system.img goto directory where extracted image is located and run
simg2img system.img.ext4 system.img
when thats done
mkdir system
mount -o rw -t ext4 system.img system
for the boot img goto @osm0sis 's AIK thread and get the linux package
use that toolkit to unpack the boot.img and check it out, you'll generate two directories after img unpacking,
ramdisk and split-image in split-image directory you will find the kernel and dtb imgs
m
yeah the link on google play is dead lol
nevermind i got it thanks
moonbutt74 said:
T,
i have a though about incorrect firmware linking in boot.img and /system/etc scripts in the release
to mount and explore the system.img goto directory where extracted image is located and run
simg2img system.img.ext4 system.img
when thats done
mkdir system
mount -o rw -t ext4 system.img system
for the boot img goto @osm0sis 's AIK thread and get the linux package
use that toolkit to unpack the boot.img and check it out, you'll generate two directories after img unpacking,
ramdisk and split-image in split-image directory you will find the kernel and dtb imgs
m
Click to expand...
Click to collapse
^^This guy is very smart ^^ i will try that as well i really wanna get these guys the lp for t530nu here in America we are being neglected with the official lollipop update samsung is slacking here i say less talk and more work for them people lol. we would probably all have our lollipop by now. jk
moonbutt74 said:
T,
i have a though about incorrect firmware linking in boot.img and /system/etc scripts in the release
to mount and explore the system.img goto directory where extracted image is located and run
simg2img system.img.ext4 system.img
when thats done
mkdir system
mount -o rw -t ext4 system.img system
for the boot img goto @osm0sis 's AIK thread and get the linux package
use that toolkit to unpack the boot.img and check it out, you'll generate two directories after img unpacking,
ramdisk and split-image in split-image directory you will find the kernel and dtb imgs
m
Click to expand...
Click to collapse
Thanks M I'll get started once I get back from my daily run (I refuse to be a fat American stereotype :silly: )
Related
This is how I made ROM, I'll try to write the steps as simple as I can. For advanced users only!
Update 22/08/11:
Revised packaging steps.
Update 13/08/11:
Removed unwanted method for ROM cooking.
Update 04/08/11:
Modified extract and repack ROM guide and added extracting system.rfs guide.
Things you need:
Base firmware
Archiver software (7zip recommended)
Any Linux environment to build ROM or Cygwin
APK Manager to optimize and decompile *.apk files
MagicISO (Optional) if you want to extract system.rfs
And the last thing is... You need enough experience in android world
So, here is the steps to cook a ROM:
Flash your phone with your desired base firmware
Make required modifications
Pull system.rfs from your phone by running this command on adb shell or Terminal Emulator:
Code:
dd if=/dev/stl12 of=/sdcard/system.rfs
Extract any *.tar.md5 files from your base firmware to your working folder with 7zip
Replace the current system.rfs with your modified one
EDIT: Pack your ROM by running this code via terminal or just pack it with 7zip/WinRAR as *.tar
Code:
tar -H ustar -c * >> ROMNAME.tar
change ROMNAME to your desired, well, ROM name.
Here is (yet) useful guide to modify your ROM.
Extract system files on system.rfs to make modding easier:
Extract PDA file (*.tar.md5) files with 7zip
Open system.rfs with MagicISO
To extract it, just drag and drop
NOTE: Never edit your ROM with MagicISO because the file permissions will be ignored, use MagicISO only for extracting files from system.rfs
Deodex, and Zipalign (optimize) your ROM apk files:
Ready to use deodex + root for KPN: http://forum.xda-developers.com/showthread.php?t=1196230
Ready to use deodex + root for KPH and other firmware: http://forum.xda-developers.com/showthread.php?t=1118048
Open APK Manager
To zipalign your apk files, in apk manager folder /place-apk-here-to-batch-optimize put your:
framework-res.apk, twframework-res.apk and all system apk
but not these:
AxT9IME, Calculator, Camera, Email, MMS, Phone, Screen Capture, Settings, Swype, Thinkdroid, Voice search
Choose Choose option 15
Then choose both (zp)
Let it run and done.
Now put back the apk files where they belong in the ROM.
How to put these apk files to my ROM? Copy these files to appropriate locations, such as /system/app to your ROM's /system/app, and etc.
Another handy modification guide:
Unpack and repack boot.img - http://forum.xda-developers.com/showthread.php?t=1173427
Convert firmware filesystem to ext4 - http://forum.xda-developers.com/showthread.php?t=1202049
Overscroll glow for any firmware - http://forum.xda-developers.com/showthread.php?t=1215933"
Give thanks to all dev who made that possible!
If you have more guides to put here, please PM me.
Am I pertamax?
hehe..just kidding.
Nice Info....great share.
I would want the Fla.sh Rom :'(
Thats a gr8 share...Thank you...)
saiftheboss7 said:
I would want the Fla.sh Rom :'(
Click to expand...
Click to collapse
sorry... once again, I'm sorry, I can't continue my ROM
Helpful thread man!
Thanks!
Great job taking your time to make this! Unfortunately, i dont even know the basics but now I know where to check when I do
fla.sh said:
sorry... once again, I'm sorry, I can't continue my ROM
Click to expand...
Click to collapse
Hey!
THX man, nice thread. Very useful!
Just PM to MOD, that they close you previous thread, a bout fla.sh.ROM. Or ppl just waiting it and asking.
CHEERS!
i think the most troublesome problem i encounter is to repack system.rfs. yes it can be mounted in magiciso, but howto repack/compile it back?
an0nym0us_ said:
i think the most troublesome problem i encounter is to repack system.rfs. yes it can be mounted in magiciso, but howto repack/compile it back?
Click to expand...
Click to collapse
Just save it.
didnt work when i just save it. my device got bootloop
an0nym0us_ said:
didnt work when i just save it. my device got bootloop
Click to expand...
Click to collapse
What modification you've added to your ROM? Maybe that modification causing the problem...
fla.sh said:
What modification you've added to your ROM? Maybe that modification causing the problem...
Click to expand...
Click to collapse
As Linux, MagicISO read RFS image as a FAT filesystem. File permissions can not be maintained. A better way but need linux:
1. Mount system.rfs as FAT and mount it to /tmp/rfs
2. Make ext4 image, and mount it to /tmp/system
3. Copy /tmp/rfs contents to /tmp/system
4. Make modification inside /tmp/system
5. Fix file permissions inside /tmp/system
6. Umount both image
7. Make ODIN flashable image, contains system.rfs (now in ext4 format) and CF-Root-S5830 boot and recovery image (for ext4 support)
8. Boot to Windows and flash your new firmware using ODIN.
ketut.kumajaya said:
As Linux, MagicISO read RFS image as a FAT filesystem. File permissions can not be maintained. A better way but need linux:
1. Mount system.rfs as FAT and mount it to /tmp/rfs
2. Make ext4 image, and mount it to /tmp/system
3. Copy /tmp/rfs contents to /tmp/system
4. Make modification inside /tmp/system
5. Fix file permissions inside /tmp/system
6. Umount both image
7. Make ODIN flashable image, contains system.rfs (now in ext4 format) and CF-Root-S5830 boot and recovery image (for ext4 support)
8. Boot to Windows and flash your new firmware using ODIN.
Click to expand...
Click to collapse
I use this command to mount rfs:
Code:
mount -o loop system.rfs /some_dir
Can you share us the command?
now thats really informative. thanks
ROM unpacking and repacking gude has been corrected. Tested by me. If you have any problems, just ask here.
Thanks.
I think you should add the date of update in the title, so that everyone can know about the update...
BTW thanks for this amazing guide...
Love it!!!
After making changes to system.rfs, how to save it as .rfs again?
adiles said:
After making changes to system.rfs, how to save it as .rfs again?
Click to expand...
Click to collapse
Please take look at the first page, it's updated, you know?
After I created md5 file and selected it in odin, it says "invalid image type" and "invalid model binary". How to solve that? After that I continued, skipped these errors and flashed, my phone stopped at boot screen with text "Galaxy ACE....". Plz help me
OK . We all i believe find it chaotic to organize in forums now. So this is a thread just for ideas and problem with cwm or twrp on our device.
All that i have found now is that recovery.img is somehow backed with boot.img. So i have to ask if there is any developer that can look inside this.
Help appreciated. We (developers) have already compiled TWRP and CWM ( me via ubuntu and clockworkmod recovery builder) and none of them is booting.
You might want to look at xperia p boot.img??? Same processor u8500 same screen size. I'm a noob. Just said what I felt. Coming from xperia device where our recoveries are always packed inside boot.img
In ramdisk . /sbin/recovery is where our recovery binary is present.
#pitchblack5691#
thanks for help ! i will definetely looo for it
Might be useful
http://forum.xda-developers.com/showthread.php?t=2020895
http://forum.xda-developers.com/showthread.php?t=1903017
#pitchblack5691#
also coming from xperia forum and for My xperia U and have also novathor u8500 and i have asked dev to explain mothod used in XU for port this method to GIII mini but no reply from him now in XU the recovery are in tar and flashable to phone without odin or another flash only by ADB + run me script in commande window inside recovery tar we have unziped recovery ( icone ....) and some files relative to phone ( fstab ..... )
How is it going? Did everyone stop developing or are you guys just moving in silence trying to figure things out?
Sent thru time and space from my s3mini.
silently moving
Shapeshift said:
silently moving
Click to expand...
Click to collapse
Good to know! Give us a shout if we can help somehow.
currently working on cwm 6. dont know why i cant boot
Perhaps need to no only make recovery but also kernel ?
If this 2 filz run together
Sent from my GT-I8190 using xda app-developers app
From what I understand, You just need to write a piece of code in the ramdisk init files to execute the recovery during boot. No need to modify the kernel.
#pitchblack5691#
If any one is interested i got a dumped ram disk also a got it rebuild-ed,
and yes the recovery scripts are there plus the pngs etc.
I also believe that the device has 2 recovery's, they are the same one just acts as a backup.
is an idea
i explain when you make recovery and extract it you find some files inside ( fstab , RC , init , propr ...
now we have also one with CM device info the device have not CM rom and also have not CM kernel her why i posted this comment because when you extract stock recovey you find kernel part and when you extract boot.img find recovery part now this 2 files perhaps have dependency to work together ? is an idea do not yell at me :silly:
spawk said:
is an idea
i explain when you make recovery and extract it you find some files inside ( fstab , RC , init , propr ...
now we have also one with CM device info the device have not CM rom and also have not CM kernel her why i posted this comment because when you extract stock recovey you find kernel part and when you extract boot.img find recovery part now this 2 files perhaps have dependency to work together ? is an idea do not yell at me :silly:
Click to expand...
Click to collapse
They had the internet in 1969?
Take your time. We have root and what roms we have are stable.
Sent from Spaceball One.
Hahaha!
Sent thru time and space from my s3mini.
xd the error is not from me haha i have corect date and time
is new technologie hahahaha retoure backwards in android
and if you see here you can read need new builded kernel to make CWM just read thread 2# and 3# http://forum.xda-developers.com/showthread.php?t=1771347
Help ful apps find on playstore this apps need busybox 2.1 and rooted rom and he let you backup your rom but without boot.img and recovery.img but bacup all system data ..... here is https://play.google.com/store/apps/details?id=com.pommedeterresautee.twoborange3
spawk said:
Help ful apps find on playstore this apps need busybox 2.1 and rooted rom and he let you backup your rom but without boot.img and recovery.img but bacup all system data ..... here is https://play.google.com/store/apps/details?id=com.pommedeterresautee.twoborange3
Click to expand...
Click to collapse
I sent info about device to that developer. That app is now supporting our golden for full backup incl boot & recovery.img with .zip from here. Only problem is we dont have a working custom recovery to flash that .zip with :/
as Faria wrote above should change the recovery that is in the kernel and the same meter and the same rom in it and in the kernel for which you go just tell me that the two are complementary if a move (size , addition, retirees), the other answers are more about the two is that one feature that the other is that we will say to his control as .
now change I believe that both will adjust in any case theoretically
Hello Moto
I've just downloaded Verizon Jelly Bean 4.1.1 by "Firmware Team".
Just to play with it a little, extract apks and test them on Galaxy SII Skyrocket.
The thing is i'm having a hard time opening system.img.
Now i've tried LinuxReader, Unyaffs and ext2explore/read but none of these can open it, they all say that it's an unrecognized image.
Do you guys know how to properly open a stock moto System.img?
lingowistico said:
Hello Moto
I've just downloaded Verizon Jelly Bean 4.1.1 by "Firmware Team".
Just to play with it a little, extract apks and test them on Galaxy SII Skyrocket.
The thing is i'm having a hard time opening system.img.
Now i've tried LinuxReader, Unyaffs and ext2explore/read but none of these can open it, they all say that it's an unrecognized image.
Do you guys know how to properly open a stock moto System.img?
Click to expand...
Click to collapse
Google for a tool called simg2img (I used the python script that appears in get first few results, there should be other versions as well). That will unpack the image into a plain ext4 image that you can mount with any Linux pc (I recommend using a virtual machine if you have windows or mac).
Happy hacking!
Sent from my XT907
aslomagic, did you try this with the firmware lingowistico is talking about? I also tried before to unpack system.img from this package, and system.img.ext4 from ICS package, and another ICS soft for XT897, and all of them give "Bad magic" error in simg2img. All of those softs are published by the same "Firmware Team" - maybe that's the case? I also tried dsixda kitchen (which also uses simg2img, but anyway...) and it also didn't work. Might be also some custom Motorola's approach to system.img....
Could you possibly help? Thanks.
micx_pl said:
aslomagic, did you try this with the firmware lingowistico is talking about? I also tried before to unpack system.img from this package, and system.img.ext4 from ICS package, and another ICS soft for XT897, and all of them give "Bad magic" error in simg2img. All of those softs are published by the same "Firmware Team" - maybe that's the case? I also tried dsixda kitchen (which also uses simg2img, but anyway...) and it also didn't work. Might be also some custom Motorola's approach to system.img....
Could you possibly help? Thanks.
Click to expand...
Click to collapse
Well, I know for a fact that those images are packed ext4, but I haven't tried specifically with that one.
Now that you mention, I think I remember signed images (like those ones) have some additional header, maybe that needs to be removed with an hex editor, or with dd of you like
If I get a chance, I'll try and report back...
Sent from my XT907
aslomagic said:
Well, I know for a fact that those images are packed ext4, but I haven't tried specifically with that one.
Now that you mention, I think I remember signed images (like those ones) have some additional header, maybe that needs to be removed with an hex editor, or with dd of you like
If I get a chance, I'll try and report back...
Click to expand...
Click to collapse
Ok, I tried, and yes, it complains it cannot find the magic (again, I'm using the python script). I modified the script to look for the magic value in the first 50Mb of the file, and if it finds it, it starts unpacking from there. Python scripts are very easy to play with
It seems to work for me, but I don't have a linux vm handy to see if it mounts correctly (I'm currently on a mac). micx_pl, can you give it a try and let me know?
I had to zip the file even though it's very small because the forum won't let me upload a .py file... who knows, just unzip it.
Holy cow! It works! You're the master I was looking for such solution everywhere, and was stunned to see barely few topics with similar problem, and no solution at all. Thanks!
micx_pl said:
Holy cow! It works! You're the master I was looking for such solution everywhere, and was stunned to see barely few topics with similar problem, and no solution at all. Thanks!
Click to expand...
Click to collapse
You're welcome, glad I could help!
Sent from my XT907
aslomagic said:
Ok, I tried, and yes, it complains it cannot find the magic (again, I'm using the python script). I modified the script to look for the magic value in the first 50Mb of the file, and if it finds it, it starts unpacking from there. Python scripts are very easy to play with
It seems to work for me, but I don't have a linux vm handy to see if it mounts correctly (I'm currently on a mac). micx_pl, can you give it a try and let me know?
I had to zip the file even though it's very small because the forum won't let me upload a .py file... who knows, just unzip it.
Click to expand...
Click to collapse
HOLY $#!+ THANKS!!! I've been trying to decompress the moto images for awhile and have never been able to do it until now
Would it be possible to modify make_ext4fs to re-sparse the image and copy the original signature?
Q9Nap said:
Would it be possible to modify make_ext4fs to re-sparse the image and copy the original signature?
Click to expand...
Click to collapse
You're welcome to try ... my guess is that it could be made to work if the image was an official, originally signed image that was unpacked by the script above or equivalent, but if you want to modify it, re-pack it and re-attach the signature, most likely the signature won't match the content. But I may be wrong, so if somebody is willing to try, best of luck to you
If your goal is just to create a packed image, but not necessarily signed (needs bootloader unlock), then I'd say it's definitely possible, search around here.
aslomagic said:
You're welcome to try ... my guess is that it could be made to work if the image was an official, originally signed image that was unpacked by the script above or equivalent, but if you want to modify it, re-pack it and re-attach the signature, most likely the signature won't match the content. But I may be wrong, so if somebody is willing to try, best of luck to you
If your goal is just to create a packed image, but not necessarily signed (needs bootloader unlock), then I'd say it's definitely possible, search around here.
Click to expand...
Click to collapse
i'm sure you're right about the signature not working on a modified image; it was just wishful thinking. the idea of course would be to inject superuser.apk and su, which wouldn't be necessary on a bootloader unlocked device.
for bootloader unlocked devices though, the ability to repack a modified image does give you another way to build custom roms. here's the code to unpack and repack images with simg2img.py and make_ext4fs:
Code:
mkdir system
./simg2img.py system.img.ext4 system.raw
sudo mount -t ext4 -o loop system.raw system/
#make changes, then:
wc -c system.raw #lists size in bytes of system.raw
sudo make_ext4fs -s -l 1234567890 -a system system.img system/ #where 1234567890 is output from wc -c
sudo umount system
rm -rf system
i've used this proecess with samsung system images, should work for moto images now too (bootloader unlocked, of course)
Yep, it's a good cheat sheet reference
Besides, on razr m and hd at least, you can also use this with safestrap without unlocking the bootloader.
aslomagic said:
Besides, on razr m and hd at least, you can also use this with safestrap without unlocking the bootloader.
Click to expand...
Click to collapse
Not sure what you mean by this; do you mean you could mount a modified system.img with safestrap? I guess it's possible since safestrap uses a system.img on the emmc, interesting idea
Q9Nap said:
Not sure what you mean by this; do you mean you could mount a modified system.img with safestrap? I guess it's possible since safestrap uses a system.img on the emmc, interesting idea
Click to expand...
Click to collapse
Yes, that's what I mean, more or less. You don't need safestrap to just mount it (use the terminal and "mount"), but you can use it to boot from it and try it.
I did this to try the Telstra image that pjcons dumped, which is pre-rooted and not signed (there it's no official signed image to date), and with a few tricks it worked without me having to unlock the bootloader.
Sent from my XT907
aslomagic said:
Google for a tool called simg2img (I used the python script that appears in get first few results, there should be other versions as well). That will unpack the image into a plain ext4 image that you can mount with any Linux pc (I recommend using a virtual machine if you have windows or mac).
Happy hacking!
Sent from my XT907
Click to expand...
Click to collapse
hello, i cant find anything on the basics of how this works, could you point me somewhere that explains it step by step or do one here. sorry of the noob question
TheWhiteChallenger said:
hello, i cant find anything on the basics of how this works, could you point me somewhere that explains it step by step or do one here. sorry of the noob question
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1588461
CNexus said:
http://forum.xda-developers.com/showthread.php?t=1588461
Click to expand...
Click to collapse
Thanks for the link I need to go learn Linux now. Lol I dontbgt the virtual machine thing at all. Its basically a Linux emulator right?
Sent from my XT1080 using XDA Premium 4 mobile app
TheWhiteChallenger said:
Thanks for the link I need to go learn Linux now. Lol I dontbgt the virtual machine thing at all. Its basically a Linux emulator right?
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No need to
http://sourceforge.net/projects/androidicsjbext/
CNexus said:
No need to
http://sourceforge.net/projects/androidicsjbext/
Click to expand...
Click to collapse
oh damn it. ok first i do appreciate the help. but that sucked. that was the frist program i tryed and it gives me "unknown file format" have i just been screwing up from the begining?
Hi,
For everyone Using the Samsung Galaxy Grand I9082 Here is a way to Root your Phone without Increasing the BIN Counter. In the Second Post I am posting the Steps for advanced Users on how to do it yourselves.
In the Third Post I am posting a pre-rooted Firmware for people Who just want to root the Phones Without all the Headache for Creating their Own.
Be Advised that even though this will Not increase the Bin Counter it is still advised to Flash a Stock Firmware when Claiming warranty.
For those who want to know the Procedure
Requirements
1) Linux (Preferably Ubuntu)
2) An Official Firmware tar (Search http://www.sammobile.com/firmwares/)
3) SU Binary and Ext4uils (Attached)
4) Patience
5) Windows (To use ODIN)
6) ODIN (To Flash)
Flash the Firmware through ODIN First so that there are no Firmware Mis-matches later.
Steps:
1)Create a "sam" directory in your Home Directory (home/username) folder where username is your linux username.
2)Extract the downloaded firmware, then move system.img and cache.img to home/username/sam dir
3)Extract su.zip and ext4utils.zip in the same folder where you have system.img and cache.img.
4)Open a terminal window, and enter:
Code:
mkdir /home/username/sam/system
sudo –i (this will ask for password..Enter your Root password)
apt-get install zlib1g-dev
cd /home/username/sam
make
mv system.img system2.img
./simg2img system2.img system.img
mount system.img system
Copy the su binary to the mounted folder
Code:
cp su system/bin/su
Give the Binary the Required Permission
Code:
chown root:root system/bin/su
chmod 06755 system/bin/su
Code:
./mkuserimg.sh -s sam ./new_system.img ext4 ./temp 1511M
Now unmount the system File and delete it
Code:
umount system
rm system.img
Rename new_system.img to system.img
Code:
mv new_system.img system.img
Now Create a flashable tar:
Code:
tar cf rooted.tar system.img
Now you need to tar the cache.img file we copied as well.
Code:
tar cf cache.tar cache.img
All Done. Now you can Flash them through ODIN.
In ODIN only Auto reboot and F. Reset Time should be checked
In PDA select: rooted.tar
In CSC select: cache.tar
After the phone Boots Download the Superuser app through Play Store.
Now you have root and No Increase in Bin Counter.
I am not that good at explaining.Incase of Question please ask them here or PM me
Also Please Consider Donating to Support My Work
For those who Just want to root.
Here i am Posting the Pre-Modded Firmware.The firmware is based on I9082XXAMB3_I9082ODDMB2_INU.zip
If you are on a different firmware then please download the firmware and Flash through ODIN.Link for the Official Firmware is:
http://uppit.com/46oxsxob7re3
Also Download the Pre-rooted firmware as well.It is in 3 parts so you need to Download all three.Also Download 7zip to extract the files.
Links for the files are:-
1) https://www.dropbox.com/s/9jh9yi88yuz49hr/Samsung Rooted.7z.001
2) https://www.dropbox.com/s/g1rk1qfuk440839/Samsung Rooted.7z.002
3)https://www.dropbox.com/s/1ej082e1z4ipqwc/Samsung Rooted.7z.003
right click on Samsung Rooted.7z.001 ->7zip ->Extract.
Wait for it to Extract
Open the extracted folder.there will be 2 files:-
1)rooted_system.tar
2)csc.tar
open ODIN:
In PDA select rooted_system.tar
In CSC select csc.tar
and Flash it.Wait for the Phone to start.once it Starts go to the Play Store and download the superuser app.
All done now you have a rooted phone Without increasing the BIN Counter
I am not good at explaining. Incase of any problems post here or Send me a PM.
Also Please Consider Donating to Support My Work
Another one
Just in case
Last Reserve
Does root package.zip refer to su zip???
How do I get CWM??
Also if I already have bin count (5 in my case)..does it reset it or stay as it is??
Sent from my GT-I9082 using xda premium
Ambarishbakre said:
Does root package.zip refer to su zip???
How do I get CWM??
Also if I already have bin count (5 in my case)..does it reset it or stay as it is??
Sent from my GT-I9082 using xda premium
Click to expand...
Click to collapse
I have the same questions.
BTW, thank you. I wish I had this method earlier, before I bumped up my bin counter.
Sent from my GT-I9082 using Tapatalk 2
manasgirdhar said:
Hi,
For everyone Using the Samsung Galaxy Grand I9082 Here is a way to Root your Phone without Increasing the BIN Counter. In the Second Post I am posting the Steps for advanced Users on how to do it yourselves.
In the Third Post I am posting a pre-rooted Firmware for people Who just want to root the Phones Without all the Headache for Creating their Own.
Be Advised that even though this will Not increase the Bin Counter it is still advised to Flash a Stock Firmware when Claiming warranty.
Click to expand...
Click to collapse
Hi,
I have already rooted my device b4, and my if I flash back with original samsung firmware, will it reset bin back to original ?
And then i can i use your procedure, would it work?
Please explain.
Thanks
Ambarishbakre said:
Does root package.zip refer to su zip???
How do I get CWM??
Also if I already have bin count (5 in my case)..does it reset it or stay as it is??
Sent from my GT-I9082 using xda premium
Click to expand...
Click to collapse
Yes root package refers to SU Zip and it is not flashable..it is to be included if creating a pre-rooted firmware.No it wont Flash CWM.And no it wont reset the counter.
This is basically for people who have not yet rooted their Device or for people who dont want to increase their counter.
Hey bro can u provide the link gor multiwindow manager'
Sent from my GT-I9082 using Tapatalk 2
yuvi123456 said:
Hey bro can u provide the link gor multiwindow manager'
Sent from my GT-I9082 using Tapatalk 2
Click to expand...
Click to collapse
Here You go:
http://forum.xda-developers.com/showthread.php?t=2079807
chotu222 method is the best because it also helps in addons of him as well as CWM
It is not about rooting a device, it is about the ROM that we are going to get as well as many other features.I am sure he is going to figure out a way to reset bin counter.
respect
conanFX said:
chotu222 method is the best because it also helps in addons of him as well as CWM
It is not about rooting a device, it is about the ROM that we are going to get as well as many other features.I am sure he is going to figure out a way to reset bin counter.
Click to expand...
Click to collapse
chottus method might be the best , but respect the developer and it is not an easy task...this method allows you too root without voiding the warranty
if this doesn't benefit you.. don't discourage the developer bro:good:
conanFX said:
chotu222 method is the best because it also helps in addons of him as well as CWM
It is not about rooting a device, it is about the ROM that we are going to get as well as many other features.I am sure he is going to figure out a way to reset bin counter.
Click to expand...
Click to collapse
Actually we can have Features without custom recovery as well.At the Moment there is no Custom ROM so it makes no point in Increasing the Counter.And What if someone has to submit his phone at the service center before we can reset BIN Counter?
There are a lot of things to consider when dealing with a samsung Phone.Anyway..If you dont like it then dont use it.
how to unroot galaxy grand??
shahid9695 said:
how to unroot galaxy grand??
Click to expand...
Click to collapse
download frimware from sammobile.com flash with odin 3.04
Sent from my GT-I9082 using xda premium
What about TriangleAway? http://forum.xda-developers.com/showthread.php?t=1494114
Links are not working........
Error (509)
This account's public links are generating too much traffic and have been temporarily disabled!
manasgirdhar said:
For those who want to know the Procedure
Requirements
1) Linux (Preferably Ubuntu)
2) An Official Firmware tar (Search http://www.sammobile.com/firmwares/)
3) SU Binary and Ext4uils (Attached)
4) Patience
5) Windows (To use ODIN)
6) ODIN (To Flash)
Flash the Firmware through ODIN First so that there are no Firmware Mis-matches later.
Steps:
1)Create a "sam" directory in your Home Directory (home/username) folder where username is your linux username.
2)Extract the downloaded firmware, then move system.img and cache.img to home/username/sam dir
3)Extract su.zip and ext4utils.zip in the same folder where you have system.img and cache.img.
4)Open a terminal window, and enter:
Code:
mkdir /home/username/sam/system
sudo –i (this will ask for password..Enter your Root password)
apt-get install zlib1g-dev
cd /home/username/sam
make
mv system.img system2.img
./simg2img system2.img system.img
mount system.img system
Copy the su binary to the mounted folder
Code:
cp su system/bin/su
Give the Binary the Required Permission
Code:
chown root:root system/bin/su
chmod 06755 system/bin/su
Code:
./mkuserimg.sh -s sam ./new_system.img ext4 ./temp 1511M
Now unmount the system File and delete it
Code:
umount system
rm system.img
Rename new_system.img to system.img
Code:
mv new_system.img system.img
Now Create a flashable tar:
Code:
tar cf rooted.tar system.img
Now you need to tar the cache.img file we copied as well.
Code:
tar cf cache.tar cache.img
All Done. Now you can Flash them through ODIN.
In ODIN only Auto reboot and F. Reset Time should be checked
In PDA select: rooted.tar
In CSC select: cache.tar
After the phone Boots Download the Superuser app through Play Store.
Now you have root and No Increase in Bin Counter.
I am not that good at explaining.Incase of Question please ask them here or PM me
Also Please Consider Donating to Support My Work
Click to expand...
Click to collapse
I tried this procedure....flashed it and yes it has no bin count. BUT still showing SYSTEM CUSTOM. Perhaps in the next version this will be solved. Thanks for the effort. I would have donated if not for this.
Futhermore:
./mkuserimg.sh -s sam ./new_system.img ext4 ./temp 1511M
Click to expand...
Click to collapse
sam should be replaced by
/home/username/sam/system
Click to expand...
Click to collapse
TWRP 2.8.7.0 custom recovery
thanx to user @Unjustified Dev we have TWRP custom recovery for our phone.
download HERE
So anyone who download the TWRP should send him a dollar for beer or at least thank him!
Of course you do everything on your own!
To test before installation (linux users need sudo before fastboot):
Code:
fastboot -i 0x1bbb boot twrp-2.8.7.0-idol3.img
To install (linux users need sudo before fastboot):
Code:
fastboot -i 0x1bbb flash recovery twrp-2.8.7.0-idol3.img
!BEFORE YOU START, PLEASE READ THIS!
And don´t forget to thank Famewolf for the tutorial, because this could save your phone when something go bad!
Thanks, tried it. It worked.
I also just installed SU directly, bypassing the previous root thread.
1. Download the .zip package from here: https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
2. Put it on the root of my SD card.
3. In TWRP click install and find the .zip.
Wonderful. Just a question: is this recovery for Idol 3 4.7 (6039) or 5.5 (6045) ?
Gynoid said:
Wonderful. Just a question: is this recovery for Idol 3 4.7 (6039) or 5.5 (6045) ?
Click to expand...
Click to collapse
It's for 6045. For 4.7 TWRP, see this post: http://forum.xda-developers.com/showpost.php?p=61976520&postcount=18
Thanks!
is it functional for backing up our system in TWRP?
@DallasCZ could you please provide the original link to TWRP. That was a bit unfair to upload it elsewhere as I tend to track the number of downloads.
Sent from my LGMS395 using Tapatalk
gecko702 said:
is it functional for backing up our system in TWRP?
Click to expand...
Click to collapse
Yes although to my knowledge noone has actually done a restore yet. He's fixing some minor bugs and will be releasing a new version at some point.
famewolf said:
Yes although to my knowledge noone has actually done a restore yet. He's fixing some minor bugs and will be releasing a new version at some point.
Click to expand...
Click to collapse
i am in touch with the dev and allready downloading the new build..will be soon on my google drive
Unjustified Dev said:
@DallasCZ could you please provide the original link to TWRP. That was a bit unfair to upload it elsewhere as I tend to track the number of downloads.
Sent from my LGMS395 using Tapatalk
Click to expand...
Click to collapse
sorry, i corrected the link...
Convert TWRP Backup into flashable rom zip
I found these instructions that explain how to take a TWRP backup and turn it into a flashable zip file. This would allow someone to create a "factory" rom pre-rooted to be flashed.
For TWRP Backup
Transfer the TWRP backup from Phone to PC.
You’ll see a file named system.ext4.win which is the System partition backup of your device. Rename it to system.ext4.tar (Changing its extension from .win to .tar)
Extract the system.ext4.tar using an archive software like Winrar or 7zip.
If your TWRP backup is not in compression mode, you will directly get the system folder, else you will get a file named system.ext4, which should be renamed again to system.ext4.tar and extract it to get the system folder.
Take the boot.emmc.win file and rename it to boot.img.
Now collect a META-INF folder from any custom ROM which is made for your device. Make sure you get the correct Meta-Inf folder, else the Zip won’t work and might worsen the condition of your device.
Select the META-INF, System folders and the boot.img and right click your mouse and select add to Archive.
In the Archive settings, choose the extension of the compressed file as Zip (Make sure of this part)
Now you can use this Zip file to flash it on your Custom recovery.
we dont have the meta-inf folder...there is one in the update i got, but i dont know if this id the right one.
and we dont have custom rom to get meta-inf from.
also the main thing is, that i cannot unpack the system win file when renamed to .tar i dunno why (i got latest 7-zip app).
DallasCZ said:
we dont have the meta-inf folder...there is one in the update i got, but i dont know if this id the right one.
and we dont have custom rom to get meta-inf from.
also the main thing is, that i cannot unpack the system win file when renamed to .tar i dunno why (i got latest 7-zip app).
Click to expand...
Click to collapse
What they primarily want is the "update-binary" which is device specific. I don't remember if the update had one....I did take apart an update-supersu.zip and it uses a script as it's update binary...thought about trying to convert that. Theoretically you could take a meta-inf for another device's rom...and use it's meta-inf making sure to replace the update-binary. It also has an installer script that tells it to mount system and data....extract files from the zip and where to put them. I learned a bit when I was trying to make an update.zip to fix my build.prop.
It untar'd fine for me on my linux pc:
[email protected]:/workarea/android/idol3/TWRP/BACKUPS/408adcbe/1970-01-01--22-28-53_LRX22G_release-keys/work > tar -xvf ../system.ext4.win000
tar: Removing leading `/' from member names
/system/app/
/system/app/AntHalService/
/system/app/AntHalService/AntHalService.apk
/system/app/AntHalService/arm64/
/system/app/AntHalService/arm64/AntHalService.odex
/system/app/BasicDreams/
/system/app/BasicDreams/BasicDreams.apk
/system/app/BasicDreams/arm64/
/system/app/BasicDreams/arm64/BasicDreams.odex
/system/app/Bluetooth/
/system/app/Bluetooth/Bluetooth.apk
/system/app/Bluetooth/arm/
/system/app/Bluetooth/arm/Bluetooth.odex
famewolf said:
What they primarily want is the "update-binary" which is device specific. I don't remember if the update had one....I did take apart an update-supersu.zip and it uses a script as it's update binary...thought about trying to convert that. Theoretically you could take a meta-inf for another device's rom...and use it's meta-inf making sure to replace the update-binary. It also has an installer script that tells it to mount system and data....extract files from the zip and where to put them. I learned a bit when I was trying to make an update.zip to fix my build.prop.
It untar'd fine for me on my linux pc:
[email protected]:/workarea/android/idol3/TWRP/BACKUPS/408adcbe/1970-01-01--22-28-53_LRX22G_release-keys/work > tar -xvf ../system.ext4.win000
tar: Removing leading `/' from member names
/system/app/
/system/app/AntHalService/
/system/app/AntHalService/AntHalService.apk
/system/app/AntHalService/arm64/
/system/app/AntHalService/arm64/AntHalService.odex
/system/app/BasicDreams/
/system/app/BasicDreams/BasicDreams.apk
/system/app/BasicDreams/arm64/
/system/app/BasicDreams/arm64/BasicDreams.odex
/system/app/Bluetooth/
/system/app/Bluetooth/Bluetooth.apk
/system/app/Bluetooth/arm/
/system/app/Bluetooth/arm/Bluetooth.odex
Click to expand...
Click to collapse
i allready build some roms for my older device, so i know what it is about.
For the proper rom zip you have to make the updater script with all the simlinks and metadata ...in the latest update there were no simlinks in the updater script...
without them you can brick your phone.
for example simlinks from 4.4.2 Os from zte V5
Code:
symlink("/data/misc/audio/mbhc.bin", "/system/etc/firmware/wcd9306/wcd9306_mbhc.bin");
symlink("/data/misc/audio/wcd9320_anc.bin", "/system/etc/firmware/wcd9306/wcd9306_anc.bin");
symlink("/persist/WCNSS_qcom_cfg.ini", "/system/etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini");
symlink("/persist/WCNSS_qcom_wlan_nv.bin", "/system/etc/firmware/wlan/prima/WCNSS_qcom_wlan_nv.bin");
symlink("/system/lib/modules/pronto/pronto_wlan.ko", "/system/lib/modules/wlan.ko");
symlink("Roboto-Bold.ttf", "/system/fonts/DroidSans-Bold.ttf");
symlink("Roboto-Regular.ttf", "/system/fonts/DroidSans.ttf");
symlink("libGLESv2.so", "/system/lib/libGLESv3.so");
symlink("mksh", "/system/bin/sh");
this you cannot copy from another device....
Never mind. I installed the second build.
How do I boot into the custom recovery? Is it power up + power button on the Idol 3?
Acreo Aeneas said:
Never mind. I installed the second build.
How do I boot into the custom recovery? Is it power up + power button on the Idol 3?
Click to expand...
Click to collapse
Reboot or power on till you see the alcatel screen pop up....right away hold down up arrow and it should go into recovery.
Thank you so much...been waiting for this....
so now let ROM's start pouring in )))))))
Hmm odd. I had to reflash it. For some reason it didn't take the first time I flashed the second build TWRP to my Idol 3.
What partitions should I backup using TWRP? I'd assume: Boot, System, and Data? Should I include System Image too?
Acreo Aeneas said:
Hmm odd. I had to reflash it. For some reason it didn't take the first time I flash the second build TWRP to my Idol 3.
What partitions should I backup using TWRP? I'd assume: Boot, System, and Data? Should I include System Image too?
Click to expand...
Click to collapse
The default of boot, system and data should be fine for personal use however if you have not yet rooted please read here first! http://forum.xda-developers.com/idol-3/help/want-to-able-to-install-ota-updates-t3163745
So Awesome! best looking twrp Ive seen yet xD. Also, works well too. I havent tested backing up data, but I did a successful restore of the system and boot So far so good!